1、 CTA Standard OpenEPG A Specification for Electronic Program Guide Data Interchange CTA-2033 R2016 (Formerly ANSI/CEA-2033) March 2008 NOTICE Consumer Technology Association (CTA) Standards, Bulletins and other technical publications are designed to serve the public interest through eliminating misu
2、nderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for his particular need. Existence of such Standards, Bulletins and other technical publicatio
3、ns shall not in any respect preclude any member or nonmember of the Consumer Technology Association from manufacturing or selling products not conforming to such Standards, Bulletins or other technical publications, nor shall the existence of such Standards, Bulletins and other technical publication
4、s preclude their voluntary use by those other than Consumer Technology Association members, whether the standard is to be used either domestically or internationally. Standards, Bulletins and other technical publications are adopted by the Consumer Technology Association in accordance with the Ameri
5、can National Standards Institute (ANSI) patent policy. By such action, the Consumer Technology Association does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard, Bulletin or other technical publication. This document does not p
6、urport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this document to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. This docume
7、nt is copyrighted by the Consumer Technology Association (CTA) and may not be reproduced, in whole or part, without written permission. Federal copyright law prohibits unauthorized reproduction of this document by any means. Organizations may obtain permission to reproduce a limited number of copies
8、 by entering into a license agreement. Requests to reproduce text, data, charts, figures or other material should be made to the Consumer Technology Association (CTA). (Formulated under the cognizance of the CTA R7 Consumer Electronics Networking Committee.) Published by CONSUMER TECHNOLOGY ASSOCIAT
9、ION 2016 Technology to video on demand (VOD) services; and to content stored locally on a home networked device. OpenEPG allows for aggregation of metadata provided by multiple sources such as various metadata service providers (MSPs,) including small and local MSPs (such as churches, schools, etc.)
10、, and personal metadata for content provided by a user. This standard defines the format and structure of OpenEPG data fields, and it defines methods of querying OpenEPG metadata services to request subsets of the available data. Electronic versions of the complete OpenEPG XML schemas and example fi
11、les can be obtained from CEA 24. This standard leverages the field structures used in the TVAnytime field set, but extends their use for the North American broadcast, cable and satellite infrastructure and conventions. This standard uses other common field structures, such MPEG-7, to the fullest ext
12、ent possible. 1.2 General Capabilities This standard enables the following capabilities: Enables devices to communicate using messages based upon IP protocols. Provides mechanisms that enable applications to tune to content. Provides mechanisms that enable applications to record content. Limits comp
13、lexity to allow small providers to create and define program metadata elements. Provides alignment with existing DLNA architecture for in-home network device interaction. Provides methods of filtering EPG data for a particular geographical area (“localization”) Provides optional methods for user and
14、/or device authentication and secure data communications with the EPG MSP. The following capabilities have been identified for future consideration. OpenEPG is a trade mark owned by the Consumer Electronics Association (CEA). Use of this term in descriptions of products or services conforming to thi
15、s standard is permissible as long as it is accompanied by attribution. CTA-2033 R2016 2 Methods that facilitate alternate business models for EPG MSPs, e.g. a method of preserving advertising content. 1.3 Background and Usage Models The OpenEPG specification enables the exchange of media-content met
16、adata between MSPs and CE equipment, and between devices on a home network through standardized formats and protocols. The goal of the OpenEPG initiative is to stimulate innovation in the applications and user experiences that utilize this metadata and to encourage the development of a robust set of
17、 products and services that can help users navigate and enjoy the increasingly diverse media content that is now becoming available to them. In formulating the requirements for this specification, two classes of OpenEPG use-case were considered Direct Access and Indirect Access. Figure 1 illustrates
18、 a typical Direct Access scenario: Figure 1 - Typical Direct Access Scenario Terrestrial TV Broadcaster A Broadcaster BCATV Service OpenEPG Service Metadata Service Provider Internet OpenEPG CTA-2033 R2016 3 The user owns multiple digital televisions (DTVs), subscribes to a Cable TV service, and rec
19、eives over-the-air television programming from multiple broadcasters. The DTVs are IP-enabled and are connected to a broadband Internet service via a home network. The user has also subscribed to an OpenEPG metadata service provided by a Metadata Service Provider (MSP). The user can access the MSP s
20、ervice directly from each DTV in the home. (Subscription mechanisms are outside the scope of this standard.) The MSPs OpenEPG service delivers detailed EPG metadata for content available from the Cable TV service or the OTA broadcasts. Additional content sources, delivery technologies, and types of
21、CE device can be accommodated, and the user may subscribe to more than one OpenEPG metadata service. (In this case, another application would aggregate the metadata for display to the user). The user browses the received EPG metadata to make current and future viewing decisions, and may use it to fa
22、cilitate scheduled recording of selected programs. Figure 2 shows a typical Indirect Access scenario: Figure 2 Typical Indirect Access Scenario SATV Provider Supporting OpenEPG Content and OpenEPG Compatible Metadata Service SATV over the Home Network w/ OpenEPG Service Multi-stream, Network-Enabled
23、 Receiver/Server w/ OpenEPG Support CTA-2033 R2016 4 In this particular scenario, the user owns multiple digital televisions (DTVs), and subscribes to a digital satellite service (DSS) that supports home networking features and OpenEPG. The DTVs are IP-enabled and are connected to the DSS receiver v
24、ia the home network. Both media content and metadata flows from the service provider to the DSS receiver and is delivered to each of the DTVs via IP transport over the home network. The user browses the metadata to make current and future viewing decisions and optionally uses the metadata to facilit
25、ate scheduled recording of selected programs. The OpenEPG metadata service provides event information as well as detailed metadata. Note that additional content receivers (renderers and/or storage devices), delivery technologies (additional satellite, OTA, or cable), and other types of CE devices co
26、uld also be accommodated, and the user could receive metadata from more than one MSP. In the latter case, an application would aggregate the metadata for display to the user. Scenarios that combine direct and indirect access methodologies can also be envisioned where applications on the CE device ag
27、gregate the metadata to provide a rich user experience. 1.4 Principles of Operation See Figure 3 for an illustration of how OpenEPG is used in both direct and indirect access scenarios. CTA-2033 R2016 5 Figure 3 Flow of Direct and Indirect Access Scenarios CTA-2033 R2016 6 2 References 2.1 Normative
28、 References The following standards contain provisions that, through reference in this text, constitute normative provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are en
29、couraged to investigate the possibility of applying the most recent editions of the standards listed. 1 ATSC Standard A/65C Program and System Information Protocol for Terrestrial Broadcast and Cable, Rev. C, with Amendment No. 1, May 9, 2006 (http:/www.atsc.org/standards/a_65cr1_with_amend_1.pdf) 2
30、 CEA-CEB16 Active Format Description (AFD) Part 2: System Description, January 2006 7 ETSI TS 102 822-3-1 Title: Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems (“TV-Anytime“); Part 3: Metadata; Sub-part 1: Phase 1 - Metadata schemas, January 2
31、006 8 ETSI TS 102 822-6-1 Title: Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems (“TV-Anytime Phase 1“); Part 6: Delivery of metadata over a bi-directional network; Sub-part 1: Service and transport, January 2006 9 ETSI TS 102 822-6-2 (2006-01)
32、 Title: Broadcast and On-line Services: Search, select, and rightful use of content on personal storage systems (“TV-Anytime Phase 1“); Part 6: Delivery of metadata over a bi-directional network; Sub-part 2: Service discovery, January 2006 10 IETF RFC 2616, HyperText Transfer Protocol HTTP 1.1, June
33、 1999 11 IETF RFC 2617 HTTP Authentication: Basic Digest Access Authentication, June 1999 12 IETF RFC 4646 Tags for Identifying Languages, February 2006 13 IETF RFC 4078 The TV-Anytime Content Reference Identifier (CRID), May 2005 14 IETF RFC 4246 International Standard Audio Visual Number (ISAN) UR
34、N Definition, February 2006 15 ISO 15706:2002 Information and Documentation - International Standard Audiovisual Number (ISAN) 16 ISO 639-1:2002 Codes for the representation of names of languages - Part 1: Alpha-2 code, CTA-2033 R2016 7 17 ISO 639-2:2007 Codes for the representation of names of lang
35、uages - Part 2: Alpha-3 code for comprehensive coverage of languages 18 ISO/IEC 15938:2005 Information technology - Multimedia Content Description Interface, Parts 1-10 (MPEG-7) 19 ISO/IEC 15938-5:2003, Information Technology - Multimedia Content Description Interface - Part 5: Multimedia Descriptio
36、n Schemes. 20 W3C Recommendation 24 December 1999, HTML 4.01 specification, http:/www.w3c.org/TR/1999/REC-html401-19991224 21 W3C Recommendation 24 June 2003, SOAP Version 1.2 Part 1: Messaging Framework 22 “Extensible Markup Language (XML) 1.0 (Fourth Edition) W3C Recommendation 16 August 2006, edi
37、ted in place 29 September 2006” http:/www.w3.org/TR/2006/REC-xml-20060816/ 2.2 Informative References 23 ETSI EN 300 468, Edition: 1.7.1(2006-05) Specification for Service Information (SI) in DVB systems (DVB SI) (http:/webapp.etsi.org/action/PU/20060523/en_300468v010701p.pdf) 24 Electronic versions
38、 of the complete OpenEPG XML Schemas and Example Files 2.3 Reference Acquisition ATSC Standards: 1750 K Street, NW, Suite 1200, Washington DC, 20006 USA, Phone: +1-202-872-9160, Fax: +1-202-872-9161, Internet: Email: http:/www.atsc.org/, atscatsc.org CEA Standards: Global Engineering Documents, Worl
39、d Headquarters, 15 Inverness Way East, Englewood, CO USA 80112-5776; Phone 800-854-7179; Fax 303-397-2740; Internet http:/ ; E-mail CEA-2033 OpenEPG XML Schemas and Example files: Consumer Electronics Association, 1919 South Eads Street, Arlington, VA USA 22202; Phone 703-907-7625; Fax 703-907-7693
40、; Internet www.CE.org ; E-mail standardsCE.org DLNA Documents: Digital Living Network Alliance (DLNA) Administration, C/O VTM, Attn: Membership Services. 5440 SW Westgate Drive, Suite217, Portland, OR 97221 USA Phone: 503.297.0426, Fax: 503.297.1090, Internet: http:/www.dlna.org/ , Email: admindlna.
41、org ETSI Standards: CTA-2033 R2016 8 ETSI Secrtariat, 650, route des Lucioles, 06921 Sophia-Antipolis Cedex, FRANCE, Tel.: +33 (0)4 92 94 42 00, Fax: +33 (0)4 93 65 47 16, Internet: http:/www.etsi.org/#, Email: helpdesketsi.org IETF Documents: Internet Engineering Task Force (IETF) Secretariat, c/o
42、Corporation for National Research Initiatives, 1895 Preston White Drive, Suite 100, Reston, VA 20191-5434, USA; Phone 703- 620-8990; Fax 703-620-9071; Internet www.ietf.org, IETF RFCs may be downloaded from www.ietf.org/rfc.html, IETF Internet drafts may be downloaded from www.ietf.org/ID.html ISO S
43、tandards ISO Central Secretariat: International Organization for Standardization (ISO); 1, rue de Varemb, Case postale 56; CH-1211 Geneva 20, Switzerland; Telephone +41 22 749 01 11; Fax +41 22 733 34 30; http:/www.iso.org W3C Documents: World Wide Web Consortium (W3C); Internet: http:/www.w3.org/ 3
44、 Conventions and Definitions 3.1 Conventions Several keywords are used to differentiate levels of requirements and optionality, as follows: MAY: A keyword that indicates flexibility of choice with no implied preference. SHALL: A keyword that indicates a mandatory requirement. Designers are required
45、to implement all such mandatory requirements to assure interoperability with other products conforming to this standard. SHOULD: A keyword that denotes flexibility of choice with a strongly preferred alternative. Equivalent to the phrase “is recommended.” Occurs: Mandatory elements defined in types,
46、 that is Occurs equals 1 or more, are dependent upon the use of the type in another element. A child element is only mandatory if its type is instantiated in another element where actual data exists. In addition XML 22 establishes mandatory requirements that are equivalent to SHALL. 3.2 Definitions
47、CTA-2033 R2016 9 For the purposes of this standard, the following definitions apply: Content Service Provider (CSP): A service that provides actual Audio/Video content. The service MAY also provide MetaData related to the content they provide. General Queries: Any OpenEPG data query. Particularly th
48、at does not conform to one of the predefined Template Queries. A Metadata Service Provider that indicates that it will accept General Queries SHALL accept all legal query expressions. Metadata Service Provider (MSP): A service that provides MetaData for Audio/Video content provided by other services
49、. OpenEPG A standard defining a language and access protocol for expressing Electronic Program Guide information. OpenEPG Web Services OpenEPG access protocols over the WAN (?) Request Template a predefined query format for data requests. Response Template a predefined list of fields that MAY be returned by a data request. Service can come from MSP or CDS 3.2.1 Abbreviations/Acronyms For the purposes of this standard, the following abbreviat
