1、 ATIS-0800002 IPTV Architecture Requirements The Alliance for Telecommunications Industry Solutions (ATIS) is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards for the communications and related inform
2、ation technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 23 industry committees and its Incubator Solutions Program. ATIS-0800002 Effective September 12, 2006 Issued March 31, 2006 Impl
3、emented September 12, 2006 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other
4、professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO R
5、EPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL A
6、TIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0800002, IPTV Architecture Requirements Is an ATIS standard developed by the Architectur
7、e Task Force of the ATIS IPTV Interoperability Forum (IIF). Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2006 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be r
8、eproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America. ii ATIS-0800002 ATIS-0800002 IPTV Architecture Requirements Secreta
9、riat Alliance for Telecommunications Industry Solutions Approved April 2006 Abstract IPTV is a suite of secure, reliable, managed video-related services. This document provides an initial industry consensus view on the requirements for an end-to-end architecture to support these services. iii ATIS-0
10、800002 CONTRIBUTORS Dipan Patel, Accenture Uche Ojeh, Accenture Kevin Schneider, ADTRAN Ken Biholar, Alcatel Raj Jagannathan, Alcatel Randy Sharpe, Alcatel Tim Barrett, Alcatel Amit Kleinmann, Amdocs Al Morton, AT so prior to defining the architecture, the IIF decided to gather a list of the functio
11、nal requirements the architecture should support. 1.2 Purpose The purpose of the IPTV Requirements document is to define, in broad terms, the scope of IPTV services and identify the high level requirements that will guide the development of architecture specifications over time. Considering the very
12、 broad set of issues that need to be addressed by the IPTV reference architecture, it will be necessary to further partition these issues into smaller work items, in order to achieve timely progress in the future work items. 1.3 Scope To define what should be encompassed in the overall architectural
13、 reference model, the Architecture Task Force has decided to focus on the following areas: The services that qualify as IPTV services. The functions necessary for content providers to provide content to the service providers. The functions required by the Service Providers to offer the IPTV services
14、. The functions required by the Network Provider to deliver the IPTV services. 1 ATIS-0800002 The functions in the home networking environment that are necessary for the consumer to receive the IPTV services, which also includes the ITF functions that are necessary to render the service. 1.4 Termino
15、logy 1.4.1 Requirements Terminology The word shall will be understood as denoting a mandatory requirement. “Shall“ will be used wherever the criterion for conformance with the specific recommendation requires that there be no deviation. The word should will denote a recommendation. “Should“ shall to
16、 be used wherever noncompliance with the specific recommendation is permissible. The words Conditional Manadatory will denote a requirement for which the implementation is optional, but if it is implemented, shall be implemented in the exact manner specified. The word may will denote an optional cap
17、ability that may augment the standard. The standard is fully functional without the incorporation of this optional capability. For a more detailed guideline to the terminology and labeling of requirements reference the Requirements Labeling Guideline appendix. 1.4.2 Contextual Text Terminology 1.4.2
18、.1 Account: Non-normative. Typically corresponds 1-to-1 to Subscriber. 1.4.2.2 Consumer: The domain where the IPTV services are consumed. In the consumer domain, a single terminal may be used for service consumption, but also a network of terminals and related devices may be present for this purpose
19、. The domain may also be a mobile end device in this case the delivery system of a network provider is a wireless Wide Area Network (WAN). 1.4.2.3 Customer: Non-normative. 1.4.2.4 Delivery Network: A set of physical transport/access networks. 1.4.2.5 (User) Device: Also known as Home Network End-Dev
20、ices (HNED), Home Network Device (HND), Consumer Equipment (CE), terminal, and physical device. A piece of HW equipment running its SW and attached to a Home Network and being identified by a GUID e.g., a MAC address. A single Device can be used by one or more Users. 1.4.2.6 (Service) Domain: A logi
21、cal administrative domain interacting with the networks, HW devices, SW components, protocols and data infrastructure as required for proper Service operation, management, billing. 1.4.2.7 Home Network (HN): A physical network segment situated on the users premises; comprised of devices and intercon
22、nection between devices, and supporting governing protocols with the premises for IPTV. 1.4.2.8 IPTV Terminal Function: Also known as ITF, represents the functionality within the consumer network that is responsible for terminating the IP signal, and converting the content into a renderable format -
23、 e.g., a STB. 1.4.2.9 Provider: Non-normative. 1.4.2.10 Service: A set of functionality enabled by a provider for consumers - e.g., providing IP with QoS connectivity, providing an IPTV service, providing IM public connectivity. In order to get a Service, a consumer needs at least to become a Subscr
24、iber to the Service and implement one or more IPTV Device Classes as scoped by the provider for the Service. 2 ATIS-0800002 1.4.2.11 Subscriber: Also known as customer, account, household, and business. A provider point of view for representing an account eligible for certain Service consumption. A
25、Subscriber can correspond to one or more Users. 1.4.2.12 User: Also known as viewer. It denotes the representation of a human or automata IPTV consumer by a set of its configuration and management data - e.g., application views, profiles, passwords, or preferences. A single User has access to one or
26、 more Devices. 1.4.3 Acronyms and Abbreviations ABNF Augmented Backus-Nauer Form ADA Americans with Disabilities Act AM Amplitude Modulation ANI Application-to-Network Interface ARU Automatic Response Unit ASI Asynchronous Serial Interface ATF Architectural Task ForceATIS Alliance for Telecommunicat
27、ions Industry Solutions ATU-C ADSL Transmission Unit, Central office ATU-I ADSL Transmission Unit, Intermediate ATU-R ADSL Transmission Unit, Remote A/V Audio/Video BNF Backus-Nauer Form BPON Broadband PONCBF Charging and Billing Functions CDR Charging Data Records CE Computer Equipment CoD Content
28、on Demand CoS Class of Service COT Central Office Terminal CPU Central Processing Unit CSP Content Service Provider CSR Customer Service Representative DAI Digital Ad Insertion DHCP Dynamic Host Configuration Protocol DLC Digital Loop Carrier DLNA Digital Living Network Alliance DMA Demographic Mark
29、et Area DN Delivery Network DNG Delivery Network Gateway DNGF Delivery Network Gateway Function 3 ATIS-0800002 DNS Domain Name System DoS Denial of Service DRM Digital Rights Management DSCP Differentiated Services Code Point DTD Document Type Declaration DTH Direct To Home DVB Digital Video Broadca
30、sting DVB-RC Digital Video Broadcasting - Return Channel DVB-S Digital Video Broadcasting - Satellite DVBSTP DVB SD Transport of MPEG-2 Based DVB Services over IP Based Networks, ETSI 102 034. 10. 3GPP, 2005, Network architecture, 23.002 11. International Telecommunications Union (ITU), 2004, Genera
31、l principles and general reference model for next generation networks, ITU-T Recommendation Y.2011. 12. International Telecommunications Union (ITU), 2006, Functional Architecture and Requirements for Resource and Admission Control Functions in Next Generation Networks, TR-RACF. 13. International Te
32、lecommunications Union (ITU), 2002, Telecommunications Markup Language (tML) framework, ITU-T Recommendation M.3030. 14. 3GPP, 2005, Telecommunication management; Charging management; Charging architecture and principle (Release 6), TS 32.240. 15. International Telecommunications Union (ITU), 2005,
33、Principles for Management of Next Generation Networks, ITU-T Recommendation M.3060. 2 IPTV CONTEXT IPTV is defined as a managed service providing the secure and reliable delivery to customers of entertainment video and related services. It provides a framework for a variety of services to be played
34、out or displayed on an end device. This is shown in Figure 1. These services are delivered across an access agnostic, packet-switched network that employs the IP protocol to transport the audio, video, and control signals. Figure 1: IPTV Context 8 ATIS-0800002 2.1 IPTV Domains Cooperation amongst a
35、number of different participants in various domains may be necessary for the delivery of IPTV services; this is shown in Figure 2. As an example, an IPTV infrastructure may be used to deliver to customers an experience akin to live television traditionally distributed via broadcast or cable networks
36、. The video content may be delivered between the content provider and the service provider via satellite or by other means. The service provider may utilize one or more delivery networks to deliver the IPTV content either to the home network where the end device can display it or directly to a mobil
37、e end device. Of course, by leveraging IP technology, the IPTV infrastructure can provide additional capabilities beyond the emulation of live broadcast television services. In contrast to video over the public Internet, IPTV deployments have their network security and performance tightly managed to
38、 ensure a superior entertainment experience, resulting in a compelling business environment for content providers, advertisers, and customers alike. Content Provider Service Provider Network Provider ConsumerFigure 2: IPTV Logical Domains The four communicating domains are briefly described as follo
39、ws: 1. Content Provider: The entity that owns or is licensed to sell content or content assets. Although the Service Provider is the primary source for the customer at Home, a direct logical information flow may be set up between Content Provider and Home customer - e.g., for rights management and p
40、rotection. 2. Service Provider: The entity providing a service to the subscriber. Different types of service providers may be relevant for television services on IP - e.g., simple Internet Service Providers (ISPs) and Content Service Providers (CSPs). In the context of television services on IP, the
41、 CSP acquires/licenses content from Content Providers and packages this into a service. In this sense, the Service Provider is not necessarily transparent to the application and content information flow. 3. Network Provider: The entity connecting customers and Service Providers. The delivery system
42、usually is composed of access networks and core or backbone networks, using a variety of network technologies. The delivery network is transparent to the IP traffic, although there may be timing and packet loss issues relevant for IPTV content streamed on IP. 4. Consumer: The domain where the IPTV s
43、ervices are consumed. In the consumer domain, a single terminal may be used for service consumption, but also a network of terminals and related devices may be present for this purpose. The domain may also be a mobile end device in this case the delivery system of a network provider is a Wireless Wi
44、de Area Network (WAN). 2.1.1 Service Provider Types As mentioned above, the Service Provider entity covers various kinds of Service Provider types, especially broadband ISPs (network providers) and CSPs (IPTV service providers). It should be noted 9 ATIS-0800002 that although we treat these two busi
45、ness roles separately, a single company could very well act in both roles. In such a case, the consumer could be offered a single subscription covering both the ISP and the CSP service offerings (see section 3). It is noted that todays Internet business models often involve so called virtual SPs, wh
46、ich means that the SP relies on some other party - typically a wholesale IP network operator - to implement and run all (or parts) of the service production platform. However, in the present document we do not distinguish any virtual SP roles - whether the SP owns the service production platform or
47、“out-sources“ the platform is irrelevant for this model, since we simply look at the services and functions of each domain. It is also noted that in some countries, the network provider and the ISP may be different parties. In this context, however, those are also not treated separately; the ISP is
48、the only party covered. The network provider could for example provide the end device with the IP address. 2.1.2 Domain Relationships and Sub-Domains The operation of an IPTV service requires many relationships between each of the domains, not just a linear flow as shown in Figure 2. From a consumer
49、s perspective their main relationship will normally be with the Service Provider. The scope of each domain is large and therefore the main domains need to be divided into sub-domains. This is shown in Figure 3. The Service Providers domain is decomposed by functionality whereas the Network Providers domain also includes decomposition by geography. Figure 3: IPTV Sub-Domains The functions within the sub-domains are listed in the following subsections. 10 ATIS-0800002 2.1.2.1 Consumer sub-domain The consumer sub-domain can be further broken down
