1、 ATIS-0800047 SCENARIOS FOR ATIS IIF IPTV INTEROPERABILITY TESTING ATIS is the leading technical planning and standards development organization committed to the rapid development of ATIS is the leading technical planning and standards development organization committed to the rapid development of g
2、lobal, market-driven standards for the information, entertainment and communications industry. More than 200 companies actively formulate standards in ATIS Committees, covering issues including: IPTV, Cloud Services, Energy Efficiency, IP-Based and Wireless Technologies, Quality of Service, Billing
3、and Operational Support, Emergency Services, Architectural Platforms and Emerging Networks. In addition, numerous Incubators, Focus and Exploratory Groups address evolving industry priorities including Smart Grid, Machine-to-Machine, Networked Car, IP Downloadable Security, Policy Management and Net
4、work Optimization. ATIS is the North American Organizational Partner for the 3rd Generation Partnership 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 Co
5、mmission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit . Notice of Disclaimer and a second approach that adds Core IMS to the service control. The IMS and non-IMS approaches use common functional elements, interfaces, and metadata
6、 where possible. This facilitates the coexistence of non-IMS and IMS-based IPTV service in the same network, and the migration from non-IMS to IMS-based IPTV with minimal obsolescence. The ATIS IIF functional architecture is well aligned with the ITU-T IPTV functional architecture as specified in Y.
7、1910 16. The ATIS IIF IPTV High Level Architecture is shown in Figure 1. The functions and interconnections in black are common to the IMS and non-IMS approaches. Functions and interconnections in green apply only to non-IMS IPTV networks. Functions and interconnections in red apply only to IMS-base
8、d IPTV networks. It is important to recognize that a network may offer non-IMS IPTV service but still use IMS for other services such as voice services. A network may use non-IMS IPTV service for some customers such as those that received IPTV service prior to Core IMS being deployed, and use IMS-ba
9、sed IPTV service for customers with an expanded service offering, located in a different serving area, or using a mobile service. Coexistence of IMS and non-IMS IPTV service and architectural evolution are important considerations in the ATIS IIF. ATIS-0800047 2 Figure 1: ATIS IIF IPTV High Level Ar
10、chitecture Notes: 1) Boxes with black outlines and black interconnections: common for non-IMS and IMS based IPTV service. 2) Boxes with green outlines and green interconnections: only apply to non-IMS IPTV service. 3) Boxes with red outlines and red interconnections: only apply to IMS based IPTV ser
11、vice. 4) The blue line is the media path. Building on the IPTV High-Level Architecture, the ATIS IIF has produced several documents focused on particular aspects of the IPTV service, such as network and service attachment, and other documents focused on particular services, such as Linear TV and Con
12、tent on Demand (CoD) services. Figure 2 shows the architecture based on the Linear TV functional architecture in ATIS-0800018, IPTV Linear TV Service 10, and ATIS-0800042, IPTV Content on Demand Service 15. The reference point designations used by the ATIS IIF align with those used by the ITU-T in Y
13、.1910. ATIS-0800047 3 C6C5IPTV ApplicationNACFS4E0E1 (XML)Ud, Md, E5A8E3iS1Transport Authorization; Subscriber mobility; Location; and Presence. IPTV CF (IPTV Control Function). The IPTV Control Functions are the set of functions to request and release the network and system resources needed to supp
14、ort the required application functionality. The IPTV CF may validate the requests against the service user profile. The IPTV CF provides signal interworking such that the control interface to the content delivery system is the same for IMS-based and non-IMS IPTV networks. CD and the other on RTP ret
15、ransmission. ATIS-0800047 8 Ru. The Ru reference point between the NACF and RACF allows the RACF to interact with the NACF for checking on CPE transport subscription profile information and the binding information of the logical/physical port address to an assigned IP address. R*. R* represents all
16、reference points between RACF and transport functions. This includes the ITU-T reference points Rc, Rn, Rp, and Rw, depending on the resource management implementation. S1. The S1 reference point is between the IPTV Control Function and the Location Control Function within the CD Universal Mobile Te
17、lecommunications System (UMTS); Network Architecture (3GPP TS 23.002), V9.3.0, June 2010.531. ETSI TS 123 228, Cellular Telecommunications System (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS) Stage 2 V9.3.0, March 2010.532. 3GPP TS 23.228, IP Multimedia
18、 Subsystem (IMS) V8.12.0, March 2010.62This document is available from the International Telecommunications Union. 3RFC text is available at . 4This document is available from the Broadband Forum. 5This document is available from the European Telecommunications Standards Institute (ETSI). ATIS-08000
19、47 11 33. 3GPP TS 24.229, IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3, V9.4.0, June 2010.634. 3GPP TS 29.228, IP Multimedia (IMS) Subsystem Cx and Dx Interfaces; Signalling flows and message contents V8.10.0, Septembe
20、r 2010.635. 3GPP TS 29.229, Cx and Dx Interfaces based on the Diameter protocol, Protocol details V8.11.0, September 2010.636. 3GPP TS 29.328, IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents V8.10.0, September 2010.637. 3GPP TS 29.329, Sh interface based on Diameter
21、 protocol; Protocol details V8.7.0, September 2010.63 ACRONYMS & ABBREVIATIONS AAA Authentication, Authorization, and Accounting APF Asset Preparation Function ARF Access Relay Function ATIS Alliance for Telecommunications Industry Solutions AUP Application User Profile CD&DF Content Distribution an
22、d Delivery Functions CD&LCF Content Distribution and Location Control Functions CF Control Function CoD Content on Demand CPE Customer Premise Equipment CVC Code Verification Certificate DHCP Dynamic Host Configuration Protocol DNG Delivery Network Gateway DNS Domain Name Service EPG Electronic Prog
23、ram Guide FEC Forward Error Correction FLUTE File Delivery over Unidirectional Transport FQDN Fully Qualified Domain Name GBA Generic Bootstrapping Architecture IIF IPTV Interoperability Forum IMS IP Multimedia System IPTV CF IPTV Control Function ITF IPTV Terminal Function NACF Network Attachment C
24、ontrol Functions NPT Normal Play Time 6This document is available from the Third Generation Partnership Project (3GPP) at . ATIS-0800047 12 OMA Open Mobile Alliance P-CSCF Proxy Call Session Control Function RACF Resource and Admission Control Function RCMS Remote Configuration and Management System
25、 RTP Real-Time Transport Protocol RTSP Real-Time Streaming Protocol SCPA Service and Content Protection and Authorization S-CSCF Serving Call Session Control Function SI Service Information SIP Session Initiation Protocol SP Service Provider SP&SD Service Provider and Services Discovery SUP Subscrib
26、er User Profile TLS Transport Layer Security URI Uniform Resource Identifier WAN Wide Area Network 4 TESTING SCENARIO 1: NETWORK ATTACHMENT, SERVICE PROVIDER DISCOVERY AND SELECTION, & SERVICES DISCOVERY These scenarios detail the initial set of activities that prepare devices in the consumer domain
27、 to receive and consume IPTV services. This section addresses the initialization and attachment phases for the Delivery Network Gateway (DNG) and the IPTV Terminal Function (ITF), covering network attachment, service provider discovery, service provider attachment, and services discovery procedures.
28、 DNG network attachment refers to the activities associated with the DNG establishing Layer 3 connectivity to an IP network. Once the network attachment activities have been completed, the DNG will be capable of transmitting and receiving IP packets and establishing a management session with an RCMS
29、. Subsequently, the RCMS is used to provision the DNG with access-network specific parameters. The ATIS IIF uses DHCP as a mechanism for network attachment. Using this protocol, the DNG acquires its WAN IP address and can also learn the address of the RCMS. After the DNG attaches to the network, the
30、 ITF follows at path from top to bottom through the following figure to attach to the network, discover service providers, attach to service providers and query specific servers, and discover services. For each phase in the process, there are several alternative methods. The outcome of each method i
31、s the same. ATIS-0800047 13 1-Network Attachment2-Service Provider DiscoveryFor IMS Services based on DHCP Option 120For Non-IMS Services3-Attach to SP and Query Specific Servers4-Services Discovery and Selection5-Service Attachment and OperationNot in scope of this specification documentPhase/Outco
32、me Method / ProcedureUsing pre-configured informationPer ATIS-0800009Remote Management of Devices in the Consumer Domain for IPTV ServicesThe ITF gets services data such as EPG and SIThe ITF attaches to a Service Provider and queries specific serversThe ITF learns the means for attaching to a Servic
33、e ProviderThe ITF gets its IP address and the IP address of the RCMS, performs remote configuration procedure, and attaches to the networkVia DHCP Container OptionViaTFTPVia BBF TR-069Via known multicast streamIMS registrationand authenticationNo action required when SP equals NPOptional discovery o
34、f “Service Discovery Application Server”Attachment via SIP Notification Package(s)Network Attachment via DHCP ProcedureRemote Configuration ProcedureWeb Services based transactionsAuthentication and AuthorizationProvided through authentication responseService Specific MethodMulticast Push WS PullSIP
35、 Notification Package(s)Figure 3: Phases of ITF Device Attachment & Initialization Sequence 4.1 Physical Scenario The architecture for the network attachment service provider discovery and attachment and services discovery and selection test cases is shown in the figure below. ATIS-0800047 14 Transp
36、ort & Access NetworksTransport FunctionsNACFE0Md, E5E3iCore IMSP-CSCApplication FunctionsS-CSC I-CSCSUPVideoHeadendMdT1RCMSAAADNGH4H6H5H1SP&S Disc. FunctionsKeyNot in scope at this timeIn scopeA0S2S4ARFIPTV ApplicationE1 (XML)AUPA4ITFDNGITFFigure 4: Scenario 1 Physical Architecture 4.2 Network Compo
37、nents 4.2.1 Scenario 1a: DNG Network Attachment The following components are required for this scenario: Transport Network Elements (Access Node, Edge Router). One AAA (DHCP) server. One Domain Name Service (DNS) server. One DNG. 4.2.2 Scenario 1b: ITF Network Attachment The following components are
38、 required for this scenario: Transport Network Elements (Access Node, Edge Router). One AAA (DHCP) server. One DNS server. One DNG. One ITF. 4.2.3 Scenario 1c: Non-IMS Service Provider Discovery and Attachment The following components are required for this scenario: Transport Network Elements (Acces
39、s Node, Edge Router). ATIS-0800047 15 One AAA (DHCP) server. One DNS server. One DNG. One ITF. One RCMS. One source of the multicast atis-iif-service-locator.xml file. One IPTV Application Server including the authentication server function. One Client Authentication Server. 4.2.4 Scenario 1d IMS-ba
40、sed Service Provider Discovery and Attachment The following components are required for this scenario: Transport Network Elements (Access Node, Edge Router). One AAA (DHCP) server. One DNS server. One DNG. One ITF. One Core IMS. One Service Discovery Application Server. One IPTV Application Server (
41、Electronic Program Guide EPG, Service Information SI). One Generic Bootstrapping Architecture (GBA) Server. One Authentication Proxy. 4.2.5 Scenario 1e Services Discovery The following components are required for this scenario: Transport Network Elements (Access Node, Edge Router). One AAA (DHCP) Se
42、rver. One DNS Server. One DNG. One ITF. One IPTV Application Server (EPG, SI). ATIS-0800047 16 4.3 Protocols and Reference Points The following reference points will be included in this scenario: Table 1: Scenario 1 Protocols and Reference Points Interface Protocol Sub Scenario H1 DHCP 1a T1 DHCP 1a
43、, 1bH5 DHCP 1b H6 CWMP (TR-069), DVB TS 102 034 1c Md RTP, MPEG2 TS 1c E5 IGMPv3 1c, 1e E0 HTTP 1.1 1c, 1d E3i SIP (Gm) 1d S4 DIAMETER 1d A0 ISC 1d E1 HTTP 1.1 1e 4.4 Test Cases 4.4.1 Scenario 1a: DNG Network Attachment DNG network attachment refers to the activities associated with the DNG establis
44、hing Layer 3 connectivity to an IP network. Once the network attachment activities have been completed, the DNG will be capable of transmitting and receiving IP packets and establishing a management session with an RCMS. Subsequently, the RCMS is used to provision the DNG with access-network specifi
45、c parameters. The test cases in this section are to verify the protocol usage, processes, and message content for DNG network attachment. DNG network attachment may be considered as four steps: 1. Establish layer 1 and layer connectivity (out of scope). 2. Issue a DHCP DISCOVER message. 3. Receive a
46、 DHCP OFFER providing: o DNG IP address and network mask. o DNS and default gateway IP addresses. o Information from which the IP address of the RCMS is determined. 4. DHCP protocol sequence is completed. Test cases: 1. DNG attaches to the network and establishes connectivity with the RCMS after bei
47、ng offered the IP address of RCMS. 2. DNG attaches to the network and establishes connectivity with the RCMS after being offered the RCMS Fully Qualified Domain Name (FQDN). ATIS-0800047 17 3. DNG attaches to the network and establishes connectivity with the RCMS after being offered neither RCMS IP
48、address nor FQDN. 4.4.2 Scenario 1b: ITF Network Attachment ITF device network attachment refers to activities associated with the ITF device establishing Layer 3 connectivity to an IP network and obtaining network configuration information data. Once the network attachment activities have been comp
49、leted, the ITF will be capable of transmitting and receiving IP packets and establishing a management session with an RCMS. The test cases in this scenario verify the protocol usage, processes, and message content for ITF network attachment. ITF network attachment may be considered as a four step sequence: 1. Establish layer 1 and layer connectivity with the DNG (out of scope). 2. Issue a DHCP DISCOVER message. 3. Receive a DHCP OFFER providing: o ITF IP address and network mask.
