These specifications define specific means for enabling and managing the delivery of alternative content in TV services that are delivered over IP transport.
This group contains two specifications:
- Event Scheduling and Notification Interface (ESNI) - defines a functional method for allowing programmers to notify cable operators of upcoming alternative content (e.g., regional sports blackouts), which will require a subscriber's device to access alternate content during a specific time frame. The Event Scheduling and Notification Interface (ESNI) is a web interface facilitating the notification of these events.
- Event Signaling and Management API (ESAM) specification - details the APIs for processing real-time signals (e.g., SCTE 35 and others) and enables real-time manifest generation. These APIs are used by MSOs to recognize and respond to network signaling and create downstream client signaling or other manifest data in support of ad insertion, alternative content, and other related uses.
Guide to Specs
| Specification—The normative interface specification document. |
| Schema Documentation—An HTML representation of the Schema. |
| Schema—An XSD file that provides a complete definition of both the message and data model structure and constraints. |
| XML Examples—Illustrative XML examples that conform to the XSD and specification rules. |
ESNI
| COMPONENT | DATE | DESCRIPTION |
| ESNI I01 Specification | 11/16/12 | OC-SP-ESNI-I01-121116.pdf |
| ESNI Schema | 11/16/12 | OC-SP-ESNI-I01-121116.xsd |
ESAM
| COMPONENT | DATE | DESCRIPTION | |
| ESAM I01 Specification | 09/10/12 | OC-SP-ESAM-API-I01-120910.pdf | |
| ESAM Signaling XML Schema | 09/10/12 | OC-SP-ESAM-API-I01-Signal.xsd | |
| ESAM Manifest XML Schema | 09/10/12 | OC-SP-ESAM-API-I01-Manifest.xsd | |
| Metadata 3.0 signalling XML schema (as of EC-0089) |
09/10/12 | MD-SP-SIGNALING-EC0089.xsd | |
| Metadata 3.0 core XML schema (as of EC-0089) |
09/10/12 | MD-SP-CORE-EC0089.xsd | |
| To submit an Engineering Change Request (ECR) against a CableLabs specification, please complete and submit the appropriate CableLabs Engineering Change Request Form. If you have a DocZone account, click here to obtain the form. If you do not have a DocZone account, click here to request the form. | |||
These CableLabs documents are the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc., for the benefit of the cable industry and its customers. These documents may contain references to other documents not owned or controlled by CableLabs. Use and understanding of these documents may require access to other documents. Designing, manufacturing, distributing, using, selling, or servicing products, or providing services, based on these documents may require intellectual property licenses from third parties for technology referenced in this document.
Neither CableLabs nor any CableLabs member company is responsible to any party for any liability of any nature whatsoever resulting from or arising out of use or reliance upon these documents, or any documents referenced herein. Documents are furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, non-infringement, or fitness for a particular purpose of any documents, or any documents referenced herein.
Neither CableLabs nor any CableLabs member company is responsible to any party for any liability of any nature whatsoever resulting from or arising out of use or reliance upon these documents, or any documents referenced herein. Documents are furnished on an "AS IS" basis and neither CableLabs nor its members provides any representation or warranty, express or implied, regarding the accuracy, completeness, non-infringement, or fitness for a particular purpose of any documents, or any documents referenced herein.
