Advertising & Interactive Services Specifications

IP TV Services: These specifications define specific means for enabling and managing the delivery of alternative content (e.g., advertising, sports blackouts) in TV services that are delivered over IP transport. Event Scheduling and Notification Interface (ESNI) defines a functional method for allowing programmers to notify cable operators of upcoming alternative content. Event Signaling and Management API (ESAM) details the APIs for processing real-time signals (e.g., SCTE 35 and others) and enables real-time manifest generation.

CoDF: The Content Definition Format (CoDF) specification is a CableLabs specification which defines a format by which interactive TV applications may be distributed to content delivery platforms. CoDF specifies the format for defining the file system content, application signaling, and carousel configuration of applications. It also specifies deployment instructions for those applications, including their timing and destinations. For example, a programmer who has authored an ETV application can also write a CoDF XML document which describes the locations of application resources (EBIF resources, images, etc.), as well as the bandwidth allocations and timing of when those resources should be placed on carousels for delivery to the the viewer's set top box. When the application streamer receives and processes the CoDF document, it will then know how and when to build the carousels.

ETV: The ETV specification is a CableLabs specification for interactivity that can be implemented on millions of digital set-top boxes deployed by cable operators. ETV, based on the Enhanced Television Binary Interchange Format or "EBIF," is part of the OCAP specification so advertising applications written for ETV can run on OCAP (OpenCable™ Applications Platform), enabling developers of interactive television services and applications to design products so that they can run successfully on any cable television system in North America.

VOD Metadata 3.0: The VOD Metadata 3.0 specification is a CableLabs specification for descriptive data associated with a package of VOD content, whether a movie or a long-form advertisement. This metadata is used in MSO and programmer VOD systems today, but in the future will assist in the delivery of prospective ad products for the VOD space, or in adding greater addressability to different types of ads.

SCTE 35 and 130: These are relevant SCTE standards that the CableLabs Working Group has determined should be supported as part of the Advanced Advertising 1.0 spec.

  • SCTE 35 enables measurement, enhanced applications and ad placement on linear and on-demand content—includes related support from SCTE 30 / 67 / 104.
  • SCTE 130 separates new addressable ad delivery systems from ad decision systems that allow for dynamic ad selection for interactive, linear and on-demand content.
To learn more about SCTE and its relevant standards, visit www.scte.org where you can learn about the organization and how to become a member, which will give you access to detailed standards information.

SAFI: Stewardship and Fulfillment Interfaces: The SaFI interfaces are part of the Advanced Advertising 1.0 spec. The SaFI 2.0 release extends version 1.1 by providing support for many advanced advertising concepts. This includes support for either predefined or dynamic placements of ads in traditional linear and in stored programming, allows selection of placed ads based on metadata, and introduces facilities for preflight asset management. As a major release, 2.0 is not backwards compatible with the 1.1 version. In particular, it introduces a new CIP document organization that has been planned to be extensible to many new business products and platforms.

Note, however, that SaFI 2.0 does not include CIP structures for supporting interactive applications. The application management structures are expected to be reintroduced in the next release. In the meantime, it is expected that operations presenting interactive applications will continue to use SaFI version 1.1.

The distributions for all releases are available at these links:

REC API: The Recommendations API specification provides a standard way for delivering recommendations for content viewing. It creates the foundation for communicating recommendations between a consumer and the recommendation services available in a cable network. This definition includes operations for both video or audio content, employs HTTP RESTful practices, and offers extensions for MSOs and vendors to innovate and differentiate the service.

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.
icon-print