`
`OpenCable™ Specifications
`ETV
`
`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`ISSUED
`
`Notice
`
`This OpenCable specification is 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. This document may
`contain references to other documents not owned or controlled by
`CableLabs. Use and understanding of this document may require
`access to such other documents. Designing, manufacturing, distributing,
`using, selling, or servicing products, or providing services, based on this
`document may require intellectual property licenses from third parties for
`technology referenced in the document.
`
`Neither CableLabs nor any member company is responsible to any party
`for any liability of any nature whatsoever resulting from or arising out of
`use or reliance upon this document, or any document referenced herein.
`This document is furnished on an "AS IS" basis and neither CableLabs
`nor its members provides any representation or warranty, express or
`implied, regarding the accuracy, completeness, or fitness for a particular
`purpose of this document, or any document referenced herein.
`
`© Copyright 2004-2009 Cable Television Laboratories, Inc.
`All rights reserved.
`
`Superseded by a later version of this document.
`
`i
`
`Charter Ex. 1153
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`Document Status Sheet
`
`Document Control Number: OC-SP-ETV-AM1.0-I05-091125
`
`Document Title: Enhanced TV Application Messaging Protocol 1.0
`
`Revision History:
`
`I01 - Issued April 18, 2005
`
`I02 - Issued July 27, 2005
`
`I03 - Issued July 14, 2006
`
`I04 - Issued September 21, 2007
`
`I05 - Issued November 25, 2009
`
`Date: November 25, 2009
`
`Status:
`
`Work in
`Progress
`
`Draft
`
`Issued
`
`Closed
`
`Distribution Restrictions:
`
`Author Only
`
`CL/Member
`
`CL/ Member/
`Vendor
`
`Public
`
`Key to Document Status Codes:
`
`Work in Progress An incomplete document, designed to guide discussion and generate feedback,
`that may include several alternative requirements for consideration.
`
`Draft
`
`Issued
`
`Closed
`
`
`Trademarks:
`
`A document in specification format considered largely complete, but lacking review
`by Members and vendors. Drafts are susceptible to substantial change during the
`review process.
`
`A stable document, which has undergone rigorous member and vendor review and
`is suitable for product design and development, cross-vendor interoperability, and
`for certification testing.
`A static document, reviewed, tested, validated, and closed to further engineering
`change requests to the specification through CableLabs.
`
`CableLabs®, DOCSIS®, EuroDOCSIS™, eDOCSIS™, M-CMTS™, PacketCable™, EuroPacketCable™,
`PCMM™, CableHome®, CableOffice™, OpenCable™, OCAP™, CableCARD™, M-Card™, DCAS™, tru2way™,
`and CablePC™ are trademarks of Cable Television Laboratories, Inc.
`
`ii
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`Contents
`
`1
`
`SCOPE..................................................................................................................................................................1
`1.1
`INTRODUCTION AND OVERVIEW.....................................................................................................................1
`1.2
`PURPOSE OF DOCUMENT .................................................................................................................................1
`1.3 ORGANIZATION OF DOCUMENT.......................................................................................................................1
`1.4
`REQUIREMENTS ..............................................................................................................................................2
`2 REFERENCES ....................................................................................................................................................3
`2.1 NORMATIVE REFERENCES ..............................................................................................................................3
`2.2
`INFORMATIVE REFERENCES............................................................................................................................3
`2.3
`REFERENCE ACQUISITION...............................................................................................................................3
`3 TERMS AND DEFINITIONS............................................................................................................................4
`
`4 ABBREVIATIONS AND ACRONYMS............................................................................................................5
`
`5 ENHANCED TELEVISION APPLICATION MODEL..................................................................................6
`5.1
`ETV APPLICATIONS .......................................................................................................................................6
`5.2
`ETV AUTHORING PROCESS ............................................................................................................................6
`5.2.1
`Production Team ...................................................................................................................................6
`5.2.2
`Network Broadcaster.............................................................................................................................6
`5.2.3
`Cable Operators ....................................................................................................................................7
`5.2.4
`Application Servers................................................................................................................................7
`5.3
`ENHANCED TELEVISION COMPONENTS...........................................................................................................7
`5.4 MEDIA TIMELINE............................................................................................................................................8
`6 ENHANCED TELEVISION APPLICATION SIGNALING........................................................................10
`6.1
`INTRODUCTION.............................................................................................................................................10
`6.2
`PROGRAM MAP TABLE DESCRIPTORS...........................................................................................................10
`6.2.1
`ETV Registration Descriptor ...............................................................................................................10
`6.2.2
`ETV Integrated Signaling Descriptor..................................................................................................11
`6.2.3
`ETV-BIF Platform Descriptor .............................................................................................................11
`6.3 APPLICATION SIGNALING FOR ANALOG SERVICES .......................................................................................13
`7 ENHANCED TELEVISION SYNCHRONIZATION SIGNALING............................................................14
`7.1
`EISS TABLE .................................................................................................................................................14
`7.2
`EISS DESCRIPTORS ......................................................................................................................................16
`7.2.1
`ETV Application Information Descriptor ............................................................................................16
`7.2.2
`ETV Media Time Descriptor................................................................................................................19
`7.2.3
`ETV Stream Event Descriptor .............................................................................................................19
`7.3
`SYNCHRONIZATION IN ANALOG SERVICES ...................................................................................................20
`8 CARRIAGE OF ETV APPLICATION RESOURCE DATA .......................................................................21
`8.1 DSM-CC DATA CAROUSEL..........................................................................................................................21
`8.2 ALTERNATE CONSTRAINED DATA CAROUSELS ............................................................................................22
`9 APPLICATION SIGNALING AND SYNCHRONIZATION FOR LIMITED CAPABILITY DEVICES
`24
`
`INTRODUCTION.............................................................................................................................................24
`9.1
`9.2 ALL OTHER SET-TOP SPECIFIC BEHAVIORS ..................................................................................................25
`9.3 OPENCABLE HOST SPECIFIC BEHAVIORS .....................................................................................................25
`
`11/25/09
`
`CableLabs®
`
`iii
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`APPENDIX I REVISION HISTORY ..................................................................................................................26
`
`
`
`List of Figures
`FIGURE 1 - ENHANCEMENT DISTRIBUTION PROCESS ......................................................................................................7
`FIGURE 2 - ENHANCED TELEVISION COMPONENTS..........................................................................................................8
`FIGURE 3 - PMT SIGNALING MOTOROLA DCT-2000 SPECIFIC BEHAVIORS .................................................................24
`
`
`List of Tables
`TABLE 1 - ETV REGISTRATION DESCRIPTOR SYNTAX..................................................................................................10
`TABLE 2 - ETV INTEGRATED SIGNALING DESCRIPTOR SYNTAX ..................................................................................11
`TABLE 3 - ETV-BIF PLATFORM DESCRIPTOR SYNTAX ................................................................................................12
`TABLE 4 - ETV-BIF PLATFORM ID SYNTAX ................................................................................................................12
`TABLE 5 - EISS SECTION SYNTAX................................................................................................................................15
`TABLE 6 - APPLICATION TYPES ....................................................................................................................................16
`TABLE 7 - ETV APPLICATION INFORMATION DESCRIPTOR SYNTAX.............................................................................17
`TABLE 8 - ETV-BIF APPLICATION CONTROL CODE VALUES .......................................................................................17
`TABLE 9 - ETV-BIF APPLICATION VERSION ................................................................................................................17
`TABLE 10 - ETV-BIF APPLICATION FLAGS..................................................................................................................18
`TABLE 11 - ETV MEDIA TIME DESCRIPTOR SYNTAX ...................................................................................................19
`TABLE 12 - ETV STREAM EVENT DESCRIPTOR SYNTAX ..............................................................................................20
`TABLE 13 - ABS_PATH ..................................................................................................................................................21
`TABLE 14 - AUTHORITY ................................................................................................................................................22
`TABLE 15 - DCII DATA CAROUSEL MESSAGE SYNTAX................................................................................................22
`
`
`
`
`
`
`iv
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`1 SCOPE
`
`1.1
`
`Introduction and Overview
`
`Broadcasters and network operators around the world are deploying interactive applications by creating
`enhancements to a broadcast video stream. These Enhanced Television (ETV) applications rely on embedding
`various types of data in the video stream, including programs, images, and triggers.
`
`This document specifies the synchronization and signaling mechanisms to be used by ETV applications, regardless
`of the target receiver or middleware environment. ETV mechanisms must be implementable by legacy set-top
`boxes as well as OpenCable (OCAP) host devices, and this implementation requirement implies that more than one
`option must exist for the physical transmission of the signaling and trigger data. This document addresses those
`various options and describes how a set-top box should interpret signals and triggers delivered via each of those
`methods.
`
`1.2 Purpose of document
`
`The purpose of this document is to specify ETV application signaling and synchronization mechanisms that meet all
`of the objectives/requirements of North American cable systems for delivering video-synchronous ETV
`applications, whether they are broadcast or delivered on-demand.
`
`The intent is to propose a uniform method of inserting signals and triggers that is independent of application
`environments and software/technology vendors. That said, it is understood that accommodations must be made for
`the support of specific legacy set-top boxes such as the DCT-2000 and Explorer 2000, while also supplying a
`standard rich enough to work with advanced set-top boxes based on the OpenCable Host 2.0 Core Functional
`Requirements [HOST2.1].
`
`In some cases, the need to support a range of devices may result in the need to have more than one signaling packet
`delivered through the network for the same application. As the number of legacy set-top boxes drops to zero, in any
`given division over the next several years, this requirement would be relaxed.
`
`This document does not attempt to impose a selection of a particular vendor for implementation. The design of the
`system is largely based on open industry standards with an objective to leverage currently existing equipment and
`tools available for implementing such a system.
`
`1.3 Organization of document
`
`This document is divided into four parts:
`•
`a description of the type of applications to be addressed by this specification,
`•
`application signaling and life-cycle management,
`•
`application synchronization and timeline management,
`•
`platform-specific constraints imposed by legacy environments.
`
`11/25/09
`
`CableLabs®
`
`1
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`1.4 Requirements
`
`Throughout this document, the words that are used to define the significance of particular requirements are
`capitalized. These words are:
`
`“SHALL”
`
`This word means that the item is an absolute requirement of this specification.
`
`“SHALL NOT”
`
`This phrase means that the item is an absolute prohibition of this specification.
`
`“SHOULD”
`
`This word means that there may exist valid reasons in particular circumstances to
`ignore this item, but the full implications should be understood and the case carefully
`weighed before choosing a different course.
`
`“SHOULD NOT” This phrase means that there may exist valid reasons in particular circumstances when
`the listed behavior is acceptable or even useful, but the full implications should be
`understood and the case carefully weighed before implementing any behavior
`described with this label.
`
`“MAY”
`
`This word means that this item is truly optional. One vendor may choose to include
`the item because a particular marketplace requires it or because it enhances the
`product, for example; another vendor may omit the same item.
`
`2
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`2 REFERENCES
`
`2.1 Normative References
`
`In order to claim compliance with this specification, it is necessary to conform to the following standards and other
`works (or portions thereof as indicated in this specification), in addition to the other requirements of this
`specification. Notwithstanding, intellectual property rights may be required to use or implement such normative
`references.
`[IEC 13818-1]
`
`ISO/IEC 13818-1:2000, Information technology—Generic coding of moving pictures and
`associated audio information: Systems, 2000.
`ISO/IEC 13818-6:1998(E), Information technology—Generic coding of moving pictures and
`associated audio information: Extensions for DSM-CC, 1998.
`OC-SP-OCAP1.1.2-090930, OpenCable Application Platform Specification, Profile 1.1,
`September 30, 2009, Cable Television Laboratories, Inc.
`ETSI TS 101 812 V1.3.1 (2003-06), DVB Multimedia Home Platform (MHP) 1.0.3.
`OC-SP-ETV-BIF1.0-I05-091125, OpenCable Enhanced Television (ETV) Binary Interchange
`Format 1.0, November 25, 2009, Cable Television Laboratories, Inc.
`[SMPTE343M] SMPTE 343M-2002, Declarative Data Essence – Local Identifier (lid:) URI Scheme.
`
`[IEC 13818-6]
`
`[OCAP1.1]
`
`[MHP]
`[ETV-BIF]
`
`Informative References
`2.2
`[HOST2.1]
`OC-SP-HOST2.1-CFR-I09-090904, OpenCable Host 2.1 Core Functional Requirements,
`September 4, 2009, Cable Television Laboratories, Inc.
`
`2.3 Reference Acquisition
`
`CableLabs Specifications:
`• Cable Television Laboratories, Inc., 858 Coal Creek Circle, Louisville, CO 80027;
`Phone 303-661-9100; Fax 303-661-9199; Internet: http://www.cablelabs.com
`
`ETSI Specifications:
`• European Telecommunications Standards Institute, http://www.etsi.org
`
`ISO Specifications:
`International Organization for Standardization, http://www.iso.org
`•
`
`
`11/25/09
`
`CableLabs®
`
`3
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`3 TERMS AND DEFINITIONS
`
`This specification uses the following terms:
`
`Application Signal
`
`Enhanced Television
`(ETV)
`Enhancement
`Trigger
`
`Stream Event
`
`User Agent
`
`A broadcast message that provides information to a receiver necessary to acquire,
`launch, and terminate an ETV application.
`A general term that refers to interactive services and applications provided in
`conjunction with video programming.
`
`A software application that executes in conjunction with video programming.
`
`A broadcast message that provides a synchronization mechanism to an
`enhancement. Triggers may be embedded in the associated video program, or
`delivered via another means such as OOB. Triggers may also be used for the
`delivery of unsolicited data to an enhancement. Triggers may include application
`signals and stream events.
`A type of Trigger that conveys application defined messages to an enhancement.
`ETV stream events are normatively defined within this specification.
`An application running on a receiver that decodes and executes the enhancement.
`
`4
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`4 ABBREVIATIONS AND ACRONYMS
`
`This specification uses the following abbreviations:
`
`AIT
`bslbf
`DCII
`DSM-CC
`DTD
`DVR
`EBIF
`ETV
`EISS
`IB
`NPT
`OOB
`PMT
`PTS
`rpchof
`uimsbf
`URI
`VBI
`
`
`
`Application Information Table
`
`bit-string left bit first
`
`DigiCipher II
`
`Digital Storage Module - Command and Control
`
`Document Type Definition
`
`Digital Video Recorder
`
`ETV Binary Interchange Format
`
`Enhanced Television
`
`ETV Integrated Signaling Stream
`
`In-band
`
`Normal Play Time
`
`Out-of-Band
`
`Program Map Table
`
`Presentation Time Stamp
`
`remainder polynomial coefficients, highest order first
`
`unsigned integer most significant bit first
`
`Uniform Resource Identifier
`
`Vertical Blanking Interval
`
`11/25/09
`
`CableLabs®
`
`5
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`5 ENHANCED TELEVISION APPLICATION MODEL
`
`5.1 ETV Applications
`
`This specification is intended to support a wide variety of program synchronous applications, such as:
`•
`Interactive Advertising
`• Game Shows
`• News
`• Sports Events
`• Voting applications
`•
`Impulse upgrade promotions
`• E-commerce applications
`This specification addresses both live broadcasts and pre-recorded programs and supports “real-time” viewing as
`well as time-shifted (DVR) viewing and interaction.
`
`5.2 ETV Authoring Process
`
`There are several important factors in the creation and deployment of ETV applications:
`• Production Team
`• Cable Operator
`• Network Broadcaster
`• Application Server
`Figure 1 provides a graphical illustration of the relationships between these functional groups.
`
`5.2.1 Production Team
`
`Application production teams generate the interactive enhancements in conjunction with the studios that produce the
`video. Applications are often built around templates for the triggers and data that are inserted by a production team.
`
`For pre-recorded shows, the application signaling and triggers are mastered during the video post-production
`process before the show is broadcast. Throughout the production process, the production team uses a media
`timeline based on SMPTE time codes, which are used for synchronization of video tape.
`
`For live shows, the application itself may be prepared in advance, but the actual data to feed the application is
`inserted dynamically—for example: Who just won the Oscar for Best Director?
`
`5.2.2 Network Broadcaster
`
`Enhancements cannot be bound to a program until after the video has been digitized for final broadcast.
`Furthermore, the video feeds from the major networks are often converted back to analog by a local network
`affiliate and then re-digitized for use by the local cable company, losing many enhancements along the way. Cable
`channels have the advantage of staying in the digital domain and so can insert all enhancements at the digital
`encoding stage.
`
`Applications and triggers must be inserted into the video stream by the broadcaster using synchronization triggers
`and play lists that are appropriate for the type of equipment used in the broadcast environment. At the same time,
`broadcasters may have to rely on sending those enhancements across a broadband connection to cable companies
`and affiliates who do not preserve the full digital signal from beginning to end. Some enhancements can be sent
`
`6
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`ahead of time for automatic insertion on a given schedule. Others may be transmitted in real time and synchronized
`to live events—either by production teams directly, or via the broadcasters or the cable operators.
`
`5.2.3 Cable Operators
`
`Some cable operators generate their own programming and enhancements. Again, they are responsible for
`obtaining the enhancement from the Production Team and inserting the application, signaling and triggers into the
`video streams, adding to or replacing video segments received from the satellite. At this point, cable operators may
`be working in either the analog or digital domain, because the video may be in either state before final transmission
`to the subscriber. Unfortunately, analog and digital video place different requirements on the data insertion
`equipment.
`
`5.2.4 Application Servers
`
`Although it probably does not signal a base enhancement directly, a polling or score server MAY be used to
`dynamically process subscriber votes or quiz answers and send responses back to particular client receivers.
`Messages sent from the polling server MAY require routing or insertion by the cable operator back into either an IB
`or OOB data stream to a client.
`
`Video +
`Enhancement
`
`Network/
`Broadcaster
`
`Enhancements &
`RT Data
`
`Internet
`
`SD
`
`SD
`
`Cable HE
`
`TALK / DATA
`TALK
`
`RS CS TR RD TD CD
`
`Receiver
`
`Video
`
`Enhancement
`
`Production
`Team
`
`Real-time Data
`
`App Server
`- Polling
`- Scoring
`- Data Collection
`
`SD
`
`Video
`
`Enhancement
`
`Figure 1 - Enhancement Distribution Process
`
`
`
`5.3 Enhanced Television Components
`
`An enhanced television application is made up of several components:
`• Broadcast Audio/Visual program
`• ETV Application Program and Resource Data
`• Application Signaling
`• Stream Events/Triggers
`• Media Timeline
`In addition, an ETV application MAY send data to an application server. Responses from the server MAY come in
`the form of new application resources or stream events.
`
`11/25/09
`
`CableLabs®
`
`7
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`These components are illustrated in Figure 2.
`
`Figure 2 - Enhanced Television components
`
`
`
`While all of these components together complete the ETV application, it helps to look at them separately in the
`context of discussing their delivery and formats:
`• The ETV application is the subject of other specifications, such as OpenCable Enhanced Television
`(ETV) [ETV-BIF], although this specification will discuss the delivery and encapsulation of the ETV
`application data.
`• Signaling commands defined in this specification tell the ETV User Agent in the client receiver to start and
`stop the application, and identify how to find and load the primary elements of the application.
`• Stream Events deliver “unsolicited” data to an application, synchronized with the video stream.
`• The Media Timeline provides the basic timing references to which stream events are synchronized.
`• ETV Application Servers are used for collecting the results of an ETV application, such as requests for
`additional information or storing poll or voting responses.
`One advantage of separating the ETV application format from this signaling specification is that this specification
`can be used to signal a number of different types of applications, including ones written to OpenCable Enhanced
`Television (ETV) [ETV-BIF], as well as to other specifications yet to be written. In general, the problems of
`signaling and media synchronization are universal, regardless of the type of application being signaled.
`
`5.4 Media Timeline
`
`A Media Timeline is a continuous timeline over the duration of an event. An event is defined in ISO/IEC 13818.1 as
`a collection of elementary streams with a common time base, an associated start time, and an associated end time. A
`typical, but not normative example, is the video and audio for a single television show.
`
`The Media Timeline refers to the real time of the event. For example, when an event is presented in reverse, the
`timeline counts down rather than up; and when an event is presented at 10 times the normal rate, the timeline
`progresses at 10 times the normal rate. In this way, the Media Timeline increases and decreases in a way similar to a
`counter on a video tape recorder and provides an absolute timeline to which references can be made for operations
`such as jumping to a particular point in the event.
`
`8
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`Media timelines can be paused, for example, during a commercial break which occurs interstitially between two
`segments of the event. Media timelines can also be nested, for example, if the commercial itself contains an
`enhancement.
`
`11/25/09
`
`CableLabs®
`
`9
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`6 ENHANCED TELEVISION APPLICATION SIGNALING
`
`6.1
`
`Introduction
`
`This section defines the data formats and transmission mechanisms that enable receivers to discover, download,
`launch, and terminate ETV applications.
`
`6.2 Program Map Table Descriptors
`
`The following PMT descriptors are defined by this specification:
`• ETV registration descriptor
`• ETV integrated signaling descriptor
`• ETV-BIF platform descriptor
`
`6.2.1 ETV Registration Descriptor
`
`The etv_registration_descriptor is defined for use in the elementary stream information loop of the
`PMT. The ETV registration descriptor [IEC 13818-1], table 2-46 – Registration Descriptor, clause 2.6.8) is defined
`to identify unambiguously the programs that comply with this specification. The ETV registration descriptor
`SHALL be carried in the elementary stream information loop of the PMT for each program component that conveys
`an ETV integrated signaling stream or ETV application resource stream. The presence of the registration descriptor
`uniquely and unambiguously identifies the formats of the private data used within this specification, including
`private use fields and identifiers within user private ranges such as descriptor tags and MPEG private section table
`ids.
`The etv_registration_descriptor is defined in Table 1.
`
`Table 1 - ETV Registration Descriptor Syntax
`Syntax
`Bits
`
`etv_registration_descriptor() {
`8
` descriptor_tag
`8
` descriptor_length
`32
` etv_format_identifier
`
`}
`
`Mnemonic
`
`uimsbf
`uimsbf
`bslbf
`
`
`
`descriptor_tag
`descriptor_length
`
`etv_format_identifier
`
`
`
`
`
`10
`
`This 8-bit integer with value 0x05 identifies this descriptor.
`This 8-bit integer indicates the number of bytes following the descriptor length
`field.
`CableLabs has assigned a value of 0x45545631 (ASCII “ETV1”) to this 4-byte
`field to identify the program component (within a multiplex) in which it is
`carried as complying with this specification.
`Note: This value must be registered with the SMPTE Registration Authority,
`LLC and is subject to change. SMPTE is authorized by the International
`Organization for Standardization (ISO) to register MPEG-2 format identifiers
`per [IEC 13818-1]:2000 Annex O: Registration procedure [for
`"format_identifier"].
`
`CableLabs®
`
`11/25/09
`
`

`

`Enhanced TV Application Messaging Protocol 1.0
`
`OC-SP-ETV-AM1.0-I05-091125
`
`6.2.2 ETV Integrated Signaling Descriptor
`
`The etv_integrated_signaling_descriptor is defined for use in the elementary stream information
`loop of the PMT. This descriptor indicates that the associated elementary stream contains an ETV integrated
`signaling stream, as defined in Section 7 of this specification. Only one elementary stream signaled by the PMT
`SHALL contain an etv_integrated_signaling_descriptor. In the event that more than one PMT entry
`contains an etv_integrated_signaling_descriptor, the behavior of the ETV receiver is undefined.
`
`A PMT entry with an etv_integrated_signaling_descriptor MAY be associated with a stream_type
`of 0xC0 or 0x05.
`
`The etv_integrated_signaling_descriptor is defined in Table 2.
`
`Table 2 - ETV Integrated Signaling Descriptor Syntax
`Syntax
`Bits
`
`etv_integrated_signaling_descriptor() {
`8
` descriptor_tag
`8
` descriptor_length
`8
` platform_id_length
`
` for (i=0; i<platform_id_length; i++){
`
` etv_bif_platform_ids()
`
` }
`
` for (i=0; i<n; i++) {
`8
` private_use
`
` }
`
`}
`
`Mnemonic
`
`uimsbf
`uimsbf
`uimsbf
`
`
`
`
`bslbf
`
`
`
`
`descriptor_tag
`descriptor_length
`
`This 8-bit integer with value 0xA2 identifies this descriptor.
`This 8-bit integer indicates the number of bytes following the descriptor length
`field.
`This 8-bit integer specifies the number of bytes of the
`etv_bif_platform_ids field immediately following this
`platform_id_length field. This value MAY be zero.
`This field contains zero or more platforms, each identified by an
`etv_bif_platform_id as defined in Table 4. If the associated elementary
`stream is NOT intended to be decoded on all platforms, this descriptor SHALL
`list all supported etv_bif_platform_ids.
`If the platform_id_length is zero (i.e., there are no etv_bif_platform_ids
`listed by this descriptor), the associated elementary stream SHALL be decoded
`on ALL platforms.
`This field may be used to carry private data to a receiver or user agent which
`interprets this signaling stream. Its use is not defined by this specification.
`6.2.3 ETV-BIF Platform Descriptor
`
`platform_id_length
`
`etv_bif_platform_ids
`
`
`
`private_use
`
`The etv_bif_platform_descriptor is defined for use in the elementary stream information loop of the
`PMT. This descriptor indicates to a receiver that the associated elementary stream carries ETV-BIF application
`resources for one or more hardware/software platforms (as identified by [ETV-BIF]) each of which SHALL be
`listed in this descriptor.
`
`11/25/09
`
`CableLabs®
`
`11
`
`

`

`OC-SP-ETV-AM1.0-I05-091125
`
`OpenCable™ Specifications
`
`Resources that target baseline receivers SHALL be transmitted on a single elementary stream. Resources that target
`other receivers MAY be transmitted across multiple elementary streams. In this case, an
`etv_bif_platform_descriptor, which identifies the targeted platform, SHALL be included in the PMT
`entry that corresponds