ATIS 0800042-2012 IPTV Content on Demand Service (Version 3 0).pdf

1、 ATIS-0800042.v003 IPTV CONTENT ON DEMAND SERVICE 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 than 200 companies actively formu

2、late standards in ATIS Committees and Forums, 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 addition, numerous Incubato

3、rs, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Connected Vehicle, IP Downloadable Security, Policy Management and Network Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP)

4、 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 more information, please

5、 visit . Notice of Disclaimer made several corrections and added enumerated requirements. ATIS-0800042.v003 3/06/2012 Third release; adds support for Internet-sourced content, off-net content delivery, multiscreen services, and adaptive HTTP streaming. ATIS-0800042.v003 iii Table of Contents 1 PURPO

6、SE refer to ATIS-0800020, IPTV Electronic Program Guide (EPG) Metadata Specification 16. The IPTV CoD Service delivers content that may be either secured or unsecured. Where content encryption is required to ensure confidentiality of the content and constrain its further usage or distribution, appro

7、priate Digital Rights Management (DRM) mechanisms are to be used. These mechanisms are out of the scope of this specification. This specification provides architecture, protocols, and use cases for the CoD Service. The content to be distributed on demand is restricted to be delivered over a unicast

8、transport to the ITF. The content may be sourced either within the service provider network or external to the service provider network. When externally sourced, it is referred to as Internet-sourced content. In addition, content may be delivered to the ITF via either a managed network or an unmanag

9、ed network (e.g., a 3rdParty Content Delivery Network CDN). Multicast or broadcast IP service infrastructures are considered out of scope for CoD service delivery to the ITF in this specification. This standard addresses content in multiple streaming formats and protocols delivered to multiple devic

10、e types implementing the ITF. It also includes capabilities for nomadic service access by the ITF at multiple locations. This specification is agnostic of infrastructures below the IP layer. 2 Normative References The following standards contain provisions which, through reference in this text, cons

11、titute provisions of this ATIS Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this ATIS Standard are encouraged to investigate the possibility of applying the most recent editions of the standards ind

12、icated below. ATIS-0800042.v003 2 1 3GPP TS 23.228, IP Multimedia Subsystem (IMS).12 3GPP TS 24.229, IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3.23 3GPP TS 29.228: IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Si

13、gnalling flows and message contents.24 3GPP TS 29.229, Cx and Dx Interfaces based on the Diameter protocol; Protocol details.25 3GPP TS 29.328, IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents.26 3GPP TS 29.329, Sh interface based on the Diameter protocol; Protocol d

14、etails.27 ANSI/SCTE 35 2007, Digital Program Insertion Cueing Message for Cable, January 2007.28 ATIS-0800001.v003, IPTV DRM Interoperability Requirements, 2012.39 ATIS-0800002, IPTV Architecture Requirements, May 2006.310 ATIS-0800003, IPTV Architecture Roadmap, August 2006.311 ATIS-0800007, IPTV H

15、igh Level Architecture, April 2007.312 ATIS-0800009.v002, Remote Management of Devices in the Consumer Domain for IPTV Services, September 2009.313 ATIS-0800013.v002, Media Formats and Protocols for IPTV Services, 2012.314 ATIS-0800017.v002, Network Attachment and Initialization of Devices and Clien

16、t Discovery of IPTV Services, April 2009.315 ATIS-0800018, IPTV Linear TV Service, January 2009.316 ATIS-0800020.v002, IPTV Electronic Program Guide Metadata Specification, April 2011.317 ATIS-0800022.v002, IPTV Consumer Domain Device Configuration Metadata, April 2011.318 ATIS-0800037, IPTV Device

17、and Authentication Identity Interoperability Specification, January 2012.319 ATIS-0800043, Content on Demand Metadata Schema and Metadata Transactions, October 2011.320 ATIS-0800044, IPTV Media Bookmark Specification, April 2011.321 ISO/IEC 13818-1, Information technology Generic coding of moving pi

18、ctures and associated audio information: Systems, 2007.422 ISO/IEC 13818-6, Information technology - Generic coding of moving pictures and associated audio information - Part 6: Extensions for DSM-CC, 1998.623 ITU-T Y.1541, Network Performance Objectives for IP-based Services, February 2006.524 ITU-

19、T Y.1910, IPTV Functional Architecture, September 2008.725 ITU-T Y.2014, Network Attachment Control Functions in Next Generation Networks, May 2008.726 ITU-T Y.2111, Resource and Admission Control Functions in Next Generation Networks, November 2008.727 RFC 2326, Real Time Streaming Protocol (RTSP),

20、 April 1998.628 RFC 2616, Hypertext Transfer Protocol - HTTP/1.1, June 1998.829 RFC 2617, HTTP Authentication: Basic and Digest Access Authentication, June 1999.830 RFC 2965, HTTP State Management Mechanism, October 2000.831 RFC 3261, SIP: Session Initiation Protocol, June 2002.832 RFC 3305, Uniform

21、 Resource Identifiers (URIs), URLs, and Uniform Resource Names (URNs): Clarifications and Recommendations, August 2002.833 RFC 3986, Uniform Resource Identifier (URI): Generic Syntax, January 2005.81This document is available from the Third Generation Partnership Project (3GPP) at . 2This document i

22、s available at the Society for Cable Telecommunications Engineers (SCTE) at . 3This document is available from the Alliance for Telecommunications Industry Solutions (ATIS), 1200 G Street N.W., Suite 500, Washington, DC 20005. 4This document is available from the International Organization for Stand

23、ardization. 5This document is available from the International Telecommunications Union. 6RFC text is available at . ATIS-0800042.v003 3 34 RFC 4145, TCP-Based Media Transport in the Session Description Protocol (SDP), September 2005.735 RFC 5988, Web Linking, October 2010.836 World Wide Web Consort

24、ium (W3C), Media Fragments URI 1.0, January 2011.737 CableLabs Asset Management Interface Version 3.0, MD-SP-AMIv3.0-D01-101209, December 9, 2010, Cable Television Laboratories, Inc.838 CableLabs Content 3.0 Specification, MD-SP-CONTENTv3.0- I01-110411, April 11, 2011.939 ITU-T Y.2091, Terms and def

25、initions for Next Generation Networks, February 2008.740 CableLabs Authentication and Authorization Interface 1.0 Specification, CL-SP-AUTH1.0-I02-110324, March 24, 2011.941 RFC 4648, The Base16, Base32, and Base64 Data Encodings, October 2006.842 RFC 2104, HMAC: Keyed-Hashing for Message Authentica

26、tion, February 1997.843 ISO/IEC (DIS) 23009-1, Dynamic adaptive streaming over HTTP (DASH), 2012.63 Definitions, Acronyms, includes forward and backward directions as well as pause. 3.1.25 Trick Play Media Resource: A Media Resource that contains trick play information used for trick mode operations

27、 3.1.26 Uniform Resource Identifier (URI): A string of characters used to identify a name or a resource. A URI may be either a Uniform Resource Locator (URL) or a Uniform Resource Name (URN) and it is partitioned into both subspaces. See 33. 3.1.27 Uniform Resource Locator (URL): A type of URI that

28、 specifies the primary access mechanism of a resource by representing its location. See 32. 3.1.28 Uniform Resource Name (URN): A form of URI that describes a resource using a namespace independent of its location. See 32. 3.2 Identifiers 3.2.1 ControlSessionId: The ControlSessionId is used only in

29、the RTSP Proxy case (see sections 6.3-6.7). The ControlSessionId is originated by the IPTV Service Control Function for the RTSP session between the ITF and the IPTV Service Control Function. The ControlSessionId is conveyed to the ITF over the E3 reference point in the 200 OK RTSP SETUP response me

30、ssage. The ITF uses the ControlSessionId to initiate RTSP TEARDOWN. 3.2.2 CreatorAssetId: The CreatorAssetId is a globally unique identifier for an asset and is the concatenation of CreatorId and AssetId as follows: ATIS-0800042.v003 5 CreatorId / AssetId The CreatorId is a string that is a register

31、ed Internet domain name (e.g., contentOnD or ) or a sub-domain of a registered Internet domain name (e.g., abc.contentOnD or xyz.contentOnD). The AssetId is equivalent to the path component of a URI as defined in section 3.3 of RFC 3986 33. AssetIds are assigned by the entity that is the creator of

32、the asset (as identified by the CreatorId) and must be unique within the realm of the creator. 3.2.3 DeviceId: The DeviceId is a globally unique identifier for a device and is the concatenation of IPTVMfgID identifier and MfgAssignedID. The DeviceId is defined in ATIS-0800037, IPTV Device and Authen

33、tication Identity Interoperability Specification. 3.2.4 MediaSessionId: This MediaSessionId is used only in the RTSP Proxy case (see sections 6.3-6.7). The MediaSessionId is originated by the Content Delivery and Storage Functions (CD see ATIS-0800001 8) from the CAS/DRM Functions. 4.3.2 Application

34、 Functions The Application Functions provide the server-side functions necessary for the end-user to browse, search, select, and where applicable purchase content. Included here are functional elements used in the preparation and storage of content for distribution to Content Delivery and Storage Fu

35、nctions (CD it is also used for the DNG and ITF to obtain necessary information (e.g., IP address, etc.) from the NACF when the DNG and ITF attach to the network. T1 corresponds to the TC-T1 reference point in ITU-T Y.2014 25 and is based on DHCP as described in ATIS-0800017 14. This reference point

36、 is out of scope for this specification. 4.4.29 Reference Point Ud The Ud reference point is between the CD&SF and the Unicast Transport Functions. This reference point is used by the CD&SF to deliver content streams in unicast mode. CoD content can be delivered to ITFs using RTP streaming or HTTP.

37、For HTTP, the response to an E6 HTTP download request is delivered via the Ud reference point. Encoded media formats and constraints are specified in sections 9.1 and 9.2. The encoded media may be encapsulated in MPEG2 transport streams. MPEG2 transport streams may be encapsulated in RTP or HTTP. ATIS-0800042.v003 20 4.5 Deployment Architectures 4.5.1 Geographically Distributed Functional Architecture Figure 4: Geographically Distributed Functional Architecture for non-IMS CoD