1、 ATIS-0800050.v002 TEST CASES FOR NON-IMS CONTENT ON DEMAND SERVICE ATTACHMENT AND SERVICE USE 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 ind
2、ustry. 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 and Operational Support, Emergency Services, Architectural Platforms and Emerging Networ
3、ks. In addition, numerous Incubators, 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 Gen
4、eration 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 Commission (CITEL). ATIS is accredited by the American National Standards Institute (A
5、NSI). For more information, please visit . Notice of Disclaimer reg-name specified in section 3.2.2 of RFC 3986 5. Example C5 URIs: ATIS-0800050.v002 7 http:/ ;for create, delete and get functions http:/ list function 3. C6 download request Table 2: HTTP Method for C6 Function Name Method Request Me
6、ssage Information Status Code Response Message Information download GET URI: C6 Asset Preparation Functions URI provided in the C5 create request message body 200 OK 302 redirect 404 not found Link Header: Media Resource Metadata URI Body: requested content NOTE Status codes also include failure res
7、ponses for convenience. 4. C1 create request Table 3: HTTP Methods for C1 Function Name Method Request Message Information Status Code Response Message Information create PUT Path: ATIS-IIF-Assets/OriginContentId Body: Distribution Policy 201 created 202 accepted The C1 URI is specified as follows:
8、C1URI = C1scheme “:/“ DCF-host “/“ “ATIS-IIF-Assets“ (“/“ OriginContentId / “?“ C1query ) C1scheme = “http“ / “https“ C1query = ”max=” 1* “ reg-name specified in section 3.2.2 of RFC 3986 5. Example C1 URIs: http:/ ;for create, delete and get functions. http:/ list functionA3 list request. 5. A3 lis
9、t response. 6. A3 get request. 7. A3 get response. ATIS-0800050.v002 8 The A3 URI is specified as follows: A3URI = A3scheme “:/“ APF-host “/“ “ATIS-IIF-Assets“ “/“ CreatorAssetId “?“ A3query A3scheme = “http“ / “https“ A3query = query ; query specified in section 3.4 of RFC 3986 5. APF-host = reg-na
10、me ; reg-name specified in section 3.2.2 of RFC 3986. Example A3 URIs: http:/ ; for list function http:/ ; for get function Table 4: HTTP Request and Response Methods for A3 Function Name Method Request Message Information Status Code Response Message Information list GET Path: ATIS-IIF-Assets 200 O
11、K Body: list of A3 URIs get GET Path: ATIS-IIF-Assets/CreatorAssetId (A3 URI) 200 OK 404 not found Body: metadata (including asset encryption elements) NOTE Status codes include failure responses for convenience. 8. A6 get request. 4.1.1.9 Known Issues None. 4.1.2 3a1.2 Content Distribution and Stor
12、age after a Cache Miss The third option (option C, Real Time Unicast Retrieval after Cache Miss), shown in 4.1.2.7, represents a real-time delivery of content from the Content Origin Function to the Content Delivery and Storage Functions (CD reg-name specified in section 3.2.2 of RFC 3986 5. path-ab
13、solute is specified in section 3.3 of RFC 3986 5. Example Origin URIs: http:/ http:/ The OriginContentId, used to refer to an asset, can be translated into an Origin URI by prepending the http scheme to the OriginContentId. The CD query specified in section 3.4 of RFC 3986 5. IPTV-SCF-host = reg-nam
14、e ; reg-name specified in section 3.2.2 of RFC 3986 5. ATIS-0800050.v002 17 The path component of an E1 URI is a specific instance of a path as defined in section 3.3 of RFC 3986 5, and is composed of the OriginContentId. Example E1 URI: http:/iptv- 4.2.1.8 Known Issues Authentication details have n
15、ot been specified by the ATIS IIF and therefore will not be included in the CoD Test Cases. 4.3 Scenario 3c: CoD Session Management 4.3.1 Test Case 3c1: Non-IMS Proxy COD Session Establishment RTSP In this case, a non-IMS RTSP SETUP request is sent by the ITF to establish a control session between t
16、he Content Delivery Client function and the IPTV Control Function. The Content Delivery Control Function proxies the request via S5. The PLAY request results in delivery of content via Ud. ATIS-0800050.v002 18 4.3.1.1 Test Setup NGN Transport StratumTransport FunctionsControl FunctionsEnd-User Funct
17、ionsConsumer TransportApplication ComponentsService Control FunctionsContent Distribution reg-name specified in section 3.2.2 of RFC 3986 5. 3. S6 Profile Data request (Optional and not specified by the ATIS IIF). 4. S6 Profile data response (Optional and not specified by the ATIS IIF). 5. A8 Author
18、ization request (Table 4). ATIS-0800050.v002 22 6. A8 Authorization response (content protection information, Provider AssetID, bit rate). Table 8: A8 HTTP GET request and Response Function Name Method Request Message Information Status Code Response Message Information Function Name Method authoriz
19、ation GET Path: OriginContentId Query: E3nqueryor S5query Authorization: scheme* 200 OK 401 unauthorized Body: Allocated session bandwidth Body: ECM* Body: NPT* authorization GET * See Appendix A. A8URI = A8scheme “:/“ COD-AF-host “/ OriginContentId “?” E3nquery / S5query A8scheme = “http“ / “https“
20、 COD-AF-host = reg-name ; reg-name specified in section 3.2.2 of RFC 3986 5. Example A8 URI: http:/cod- subscriber-scheme = “http“ / “https“ as indicated in E3n URI. ;IPv4address and IPv6address specified in section 3.2.2 of RFC 3986 5. CD reg-name specified in section 3.2.2 of RFC 3986 5. Example S1 URI: http:/ ATIS-IIF-Subscriber-Scheme=http ATIS-0800050.v002 23 reg-name specified in section 3.2.2 of RFC 3986 5. Example E6 URIs: rtsp:/ http:/
