1、 ATIS-0800022.v002 IPTV CONSUMER DOMAIN DEVICE CONFIGURATION METADATA REQUIREMENTS ATIS is the leading technical planning and standards development organization committed to the rapid development of global, market-driven standards for the information, entertainment and communications industry. More
2、than 200 companies actively formulate standards in ATIS 17 Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In ad
3、dition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partn
4、ership Project (3GPP), a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications Sectors, and a member of the Inter-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For mor
5、e information, please visit . Notice of Disclaimer updated and extended to provide support for Content on Demand applications and pay-per-view programming. ATIS-0800022.v002 4/21/2011 Correction to error in a namespace in Appendix A. ATIS-0800022.v002 ATIS Standard on IPTV CONSUMER DOMAIN DEVICE CON
6、FIGURATION METADATA Alliance for Telecommunications Industry Solutions Approved March 1, 2011 Abstract This document complements ATIS-0800017, Network Attachment and Initialization of Devices and Client Discovery of IPTV Services, by specifying the data structures (metadata) and transactions that ar
7、e necessary to implement network attachment of IPTV Delivery Network Gateway (DNG) devices and IPTV Terminal Function (ITF) devices and the processes for service provider discovery, service provider attachment, and services discovery. NOTE - Annex B, ATIS IIF Consumer Domain Device Configuration Met
8、adata Schema, of this Standard has also been formatted as a separate zip file and electronically packaged with this standard. ATIS-0800022.v002 iii TABLE OF CONTENTS 1 BACKGROUND, PURPOSE, Transport of MPEG-2 Based DVB Services over IP Based Networks, October 2007.516 ETSI EN 300 468 v1.4.1, Digital
9、 Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems, November 2000.517 IANA, Audio Media Types, .61This document is available at the Society for Cable Telecommunications Engineers (SCTE). . 2This document is available from the Alliance for Telecommunications Industry
10、 Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 3This document is available from the Advanced Television Systems Committee. 4This document is available from the Broadband Forum. 5This document is available from the European Telecommunications Standards Institute (ETSI). ATIS-
11、0800022.v002 3 18 IETF RFC 3261, SIP: Session Initiation Protocol, June 2002.719 IETF RFC 3265, Session Initiation Protocol (SIP) - Specific Event Notification, June 2002.720 IETF RFC 3489, STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs), March 2003
12、.721 IETF RFC 5280, Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, May 2008.722 ISO/IEC 11172-3:1993, Coding of moving pictures and associated audio for digital storage media at up to about 1,5 Mbit/s - Part 3: Audio, 1993.823 ISO/IEC 13818-2:2000
13、, Information technology Generic coding of moving pictures and associated audio information Part 2: Video, 2000.824 ISO/IEC 13818-3:1998, Information technology - Generic coding of moving pictures and associated audio information - Part 3: Audio, 1998.825 ISO/IEC 14496-3:2005, Information Technology
14、 Coding of audio-visual objects Part 3: Audio, 2005.826 ISO/IEC 14496-3:2005 Amendment 2, Information Technology Coding of audio-visual objects Part 3: Audio, 2005.827 ISO/IEC 15938-5:2003, Information technology - Multimedia content description interface Part 5: Multimedia description schemes, 2003
15、.828 ITU-R Recommendation BT.470-6, Conventional Analogue Television Systems, November 1998.929 ITU-T Recommendation H.264, Advanced Video Coding for Generic Audiovisual Services, November 2007.1030 SCTE 65, Service Information Delivered Out-of-Band for Digital Cable Television, 2008.131 SMPTE 421M-
16、2006, Television VC-1 Compressed Video Bitstream Format and Decoding Process, 2006.1132 SMPTE 2022-1, Forward Error Correction for Real-Time Video/Audio Transport Over IP Networks, 2007.1133 W3C Recommendation, XML Schema Part 2: Datatypes Second Edition, October 2004.1234 W3C Recommendation, Extens
17、ible Markup Language (XML) 1.0 (Fourth Edition), August 2006.126This document is available from the Internet Assigned Numbers Authority. 7RFC text is available at . 8This document is available from the International Organization for Standardization. 9This document is available from the International
18、 Telecommunications Union. 10This document is available from the International Telecommunications Union. 11This document is available from the Society of Motion Picture and Television Engineers (SMPTE). 12This document is available from the World Wide Web Consortium (W3C). ATIS-0800022.v002 4 35 ATI
19、S-0800027, IPTV Glossary, July 2009.236 Universal Plug and Play Forum, UPnP-QoS Architecture:3, November 2008.133 DEFINITIONS, ACRONYMS, most importantly, it serves as the “phone book” for the Internet by translating human-readable computer hostnames (e.g., ) into IP addresses (e.g., 208.77.188.166)
20、, which networking equipment needs to deliver information. 3.1.5 EPG Full Profile: EPG metadata model as defined in section 5 of ATIS-0800020 7. 3.1.6 EPG List Profile: Scaled down profile of the EPG metadata model, as defined in section 6 of ATIS-0800020 7, intended to support rapid acquisition by
21、ITF devices of just enough information to support simple searches (on title, key words, and genre) and simple listings of the available content. 3.1.7 EPG Lite Profile: EPG metadata model suitable for light weight devices, as defined in ATIS-0800046 10. 3.1.8 Initialization: A consumer device setup
22、and initial configuration phase that is performed either at manufacturing time or manually entered by the user. This stage is outside the scope of the ATIS IIF. However, the data elements such as identity and authentication credentials and their default values are in scope for the ATIS IIF. 3.1.9 IT
23、F Capabilities: CPU processing power and other hardware resources, as well as software functionality (e.g., QoS management and NAT/media relay), available within an ITF Device. 3.1.10 Network Attachment: The process by which a network entity (such as the activities associated with the ITF Device or
24、DNG) establishes Layer 3 connectivity to an IP-network and obtains network configuration data. 3.1.11 Remote Configuration and Management Server (RCMS): Server utilized by ITF Device and DNG to acquire needed configuration parameters, per ATIS-0800009, Remote Configuration of Devices in 13This docum
25、ent is available from the UPnP. ATIS-0800022.v002 5 the Consumer Domain for IPTV Services, and ATIS-0800017, Network Attachment and Initialization of Devices and Client Discovery of IPTV Services. 3.1.12 SD Server Function: The server side logic of the “Services Discovery” process, which can either
26、be implemented by a dedicated server or it can reside on an IPTV Application server (thus be collocated with other IPTV functions). 3.1.13 Service Package: A service package represents a grouping of one or more TV channels. Service packages can be used for multiple purposes, such as being a unit of
27、subscription, policy download in RACF, etc. Each service package is assigned an identity. The actual grouping of channels within a service package is under control of the IPTV Service Provider. A TV channel can be included in more than one Service Package. 3.1.14 Service Provider Discovery: The proc
28、ess by which an ITF Device becomes aware of the available IPTV Service Provider(s) and learns the means for attaching to a Service Provider over a secure managed network. 3.1.15 Services Discovery: The process by which an ITF Device receives the necessary data elements which enable the ITF Device to
29、 access the available IPTV Services. 3.1.16 Service Information (SI): The information that is necessary for the ITF Device to locate and access the content. 3.1.17 Master SI Table: Provides three functions to an ITF Device: 1) Contains locations for each Virtual Channel Map. 2) Contains versioning i
30、nformation for each Virtual Channel Map. 3) An identifier for each Virtual Channel Map. 3.1.18 Virtual Channel Map: A list of virtual channels, containing for each virtual channel a service identifier and a pointer to service description information for the virtual channel. A Virtual Channel Map con
31、sists of multiple Virtual Channel Descriptions. An ITF Device is assigned to one Virtual Channel Map. Note that if a-la-carte programming is desired, this is to be accomplished utilizing entitlements. 3.1.19 Virtual Channel Description: Contains the parameters necessary to acquire and display partic
32、ular AV content. A Virtual Channel Description is made up of one or more Programming Sources. In addition, where possible, a priori knowledge is given of certain parameters required to receive and decode the virtual channel. This may include video and audio codecs. 3.1.20 Virtual Channel Service: A
33、television service in which a continuous stream flows in real time from the Service Provider to the terminal device and where the user cannot control the temporal order in which contents are delivered. Also known as a Linear TV Service. 3.1.21 Programming Sources: Each Virtual Channel Description co
34、ntains one or more Programming Sources. It is anticipated that the content is the same for each source, but that the resolution, encoding, and type for each is different. In addition, there is an optional source that is the Barker Source. The Barker Source is to be tuned by the ITF Device if the sec
35、urity mechanism indicates that the ITF Device is not entitled to the content. 3.1.22 Version Operation: There is a version element associated with each Virtual Channel Description, Virtual Channel Map, and Master SI table. A version is changed when any element, attribute, or linked file is modified.
36、 Since it is expected that the System Information is stable once a network has been established, this allows for the ITF Device to monitor only one file, the Master SI ATIS-0800022.v002 6 Table, to know that a value has changed. It will then be a simple matter to follow the version chain to find out
37、 what parameter has changed. Note that this implies that the Master SI Table is multicast pushed to the ITF devices. As an example, a change to any Virtual Channel Description will cause the associated version to increment by one, and all Virtual Channel Maps which link to that Virtual Channel Descr
38、iption version element to increase by one, and the Master SI Table version number element to increment by one. 3.2 Acronyms & Abbreviations Please refer to the IPTV Glossary 35 for all acronyms and abbreviations. ATIS Alliance for Telecommunications Industry Solutions ABNF Augmented BackusNaur Form
39、CAS Conditional Access System CDDC Consumer Domain Device Configuration COD Content on Demand DHCP Dynamic Host Configuration Protocol DNG Delivery Network Gateway DNS Domain Name System DRM Digital Rights Management EAS Emergency Alert System EPG Electronic Program Guide FEC Forward Error Correctio
40、n FLUTE File Delivery over Unidirectional Transport HD High Definition HTTP(S) HyperText Transfer Protocol (over SSL) IIF IPTV Interoperability Forum IMS IP Multimedia Subsystem IP Internet Protocol ISS/A IPTV Security Solution/Authentication ITF IPTV Terminal Function NP Network Provider NSP Networ
41、k Service Provider PSI Public Service IdentifierRCMS Remote Configuration and Management Server RF Radio Frequency SD Service Discovery SI Service (or System) Information SP Service Provider SSL Secure Sockets Layer STUN Session Traversal Utilities for NAT TFTP Trivial File Transfer Protocol ATIS-08
42、00022.v002 7 URI Uniform Resource Identifier URL Uniform Resource Locator VOD Video on Demand XML eXtensible Markup Language 4 CONSUMER DOMAIN DEVICE CONFIGURATION METADATA DISTRIBUTION ARCHITECTURE (INFORMATIVE) Figure 1 below illustrates the architectural framework for distribution of metadata for
43、 Consumer Domain Device Configuration (CDDC). During the configuration process, a DNG gets information from a network DHCP server and from Service Provider (SP)/Network Provider (NP) DNS servers, and an ITF device gets information from the local DHCP server, from SP/NP DNS servers, from SP authentic
44、ation and provisioning servers (collectively represented by an “SD Server”), and possibly from a Remote Configuration and Management Server (RCMS). Figure 1: Architectural Framework for CDDC Metadata Distribution 5 CDDC METADATA XML FRAMEWORK 5.1 XML Scheme The CDDC Metadata XML Description Scheme t
45、hat has been developed by ATIS is associated with the IIF “cddc:” XML namespace. The full CDDC XML Description Scheme is in the form of an “.xsd” file, which is contained in a “zip” file that accompanies the present document. In the event of any conflict, this “.xsd” file takes precedence over the X
46、ML schema definitions in the present document. The formal definition of the ATIS IIF cddc: metadata namespace is: xmlns:cddc=“http:/www.atis.org/ServiceDelivery/IPTV/CDDC/2/schema“ ATIS-0800022.v002 8 The ATIS CDDC XML scheme imports XML Description Schemes from the W3C XML specification 33, the MPE
47、G-7 multimedia description schemes standard 27, and the ATIS IPTV Emergency Alert System (EAS) Metadata Specification 3, IPTV EPG Metadata Specification 6, Media Formats and Protocols Specification 4, and Global XML Types definition, some of which are included as part of the release package of this
48、document (see Annex B). The namespaces of these schemes are: xmlns=“http:/www.w3.org/2001/XMLSchema“ xmlns:mpeg7=“urn:tva:mpeg7:2005“ xmlns:eas=”http:/www.atis.org/schemas/0800012/eas/1” xmlns:epg=”http:/www.atis.org/ServiceDelivery/IPTV/EPG/2/schema” xmlns:mps=”http:/www.atis.org/schemas/0800013/mp
49、s/1” xmlns:gt=”http:/www.atis.org/ServiceDelivery/IPTV/GlobalTypes/3/schema” 5.2 Identifiers The XML type gt:IIFIDType is used for identifiers for a number of XML elements in the present document. The values of gt:IIFIDType identifiers shall be globally unique. The values of gt:IIFIDType identifiers shall conform to the syntax of the anyURI XML data type. The XML type gt:IIFIDRef is used for references to such elements, whereby the identifier of the referenced el
