ATIS 0800059-2013 Test Plan Scenarios for MultiScreen Video Services.pdf

1、 ATIS-0800059 TEST PLAN SCENARIOS FOR MULTISCREEN VIDEO SERVICES As a leading technology and solutions development organization, ATIS brings together the top global ICT companies to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies addr

2、ess cloud services, device solutions, emergency services, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations, and more. These priorities follow a fast-track development lifecycle from design and innovation through solutions that include st

3、andards, specifications, requirements, business use cases, software toolkits, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North American Organizational Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner

4、of oneM2M, 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). For more information, visit . Notice of Disclaimer Signalling flows and message contents.10

5、12 3GPP TS 23.228, IP Multimedia Subsystem (IMS).1013 3GPP TS 29.228, IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signaling flows and message contents.1014 3GPP TS 29.229, Cx and Dx Interfaces based on the Diameter protocol; Protocol details.1015 3GPP TS 24.229, IP multimedia call control pro

6、tocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP).1016 RFC 3261, SIP: Session Initiation Protocol.917 ITU-T Y.2111, Resource and Admission Control Functions in Next Generation Networks.113 Definitions, Acronyms, reg-name specified in section 3.2.2 of RFC 3986 10

7、. Example C5 URIs: http:/ ; for create, delete and get functions. http:/ for list function. 3. C6 download request. Table 2: HTTP Method for C6 Function Name Method Request Message Information Status Code Response Message Information download GET URI: C6 Asset Preparation Functions URI provided in t

8、he C5 create request message body. 200 OK 302 redirect 404 not found Link Header: Media Resource Metadata URI Body: requested content 4. A3 list (request and response) and A3 get (request and response) The A3 URI is specified as follows: A3URI = A3scheme “:/“ APF-host “/“ “ATIS-IIF-Assets“ “/“ Creat

9、orAssetId “?“ A3query A3scheme = “http“ / “https“ A3query = query ; query specified in section 3.4 of RFC 3986 10. APF-host = reg-name ; reg-name specified in section 3.2.2 of RFC 3986 10. Example A3 URIs: http:/ (for list function) http:/ (for get function) Table 3: HTTP List and Get Methods for A3

10、 Function Name Method Request Message Information Status Code Response Message Information list GET Path: ATIS-IIF-Assets 200 OK 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) 4.1.3.4.2 Content Sel

11、ection query specified in section 3.4 of RFC 3986 10. IPTV-SCF-host = reg-name ; reg-name specified in section 3.2.2 of RFC 3986 10. The path component of an E1 URI is a specific instance of a path as defined in section 3.3 of RFC 3986 10, and is composed of the OriginContentId. Example E1 URI: http

12、:/iptv- 4.1.3.4.3 Non-IMS Redirect COD Session Establishment RTSP (On-Net Portion) 1. Through user interaction, preset recording instructions, or other means, OriginContentId is available to the ITF. 2. E3 setup request including OriginContentId. Table 4: RTSP Redirect Methods for E3 Function Name M

13、ethod Request Message Information Status Code Response Message Information setup SETUP Path: OriginContentId Authorization: scheme* Transport Header: destination = ITF IP client_port = ITF port 302 redirect 401 unauthorized 404 not found Location Header: E6URI * See section 5.5 of ATIS-0800042 4. Ta

14、ble 5: RTSP Methods and Compliance for E3 RTSP Method Direction:C = Client (ITF) S = Server (SCF) SETUP CS The E3 URI is specified as follows: E3n URI = subscriber-scheme “:/“ IPTV-SCF-host “/“ OriginContentId “?“ E3nquery subscriber-scheme = “rtsp“ E3query = E1query “ reg-name specified in section

15、3.2.2 of RFC 3986 10. ATIS-0800059 13 Example E3nURIs: rtsp:/iptv- 3. Optionally, S6 requests S-User profile. 4. Optionally, S6 returns user profile data. 5. S1 locate requests location request. 6. S1 locate response. Table 6: HTTP Methods for S1 Function Name Method Request Message Information Stat

16、us Code Response Message Information locate GET Path: OriginContentId Query: ATIS-IIF-Subscriber-Scheme Query: ATIS-IIF-ITF-IP-Address 200 OK 404 not found Body: CD subscriber-scheme = “http“ / “https“ as indicated in E3n URI. ; IPv4address and IPv6address specified in section 3.2.2 of RFC 3986 10.

17、CD reg-name specified in section 3.2.2 of RFC 3986 10. Example S1 URI: http:/ Scheme=http reg-name specified in section 3.2.2 of RFC 3986 10. Example E6 URI: rtsp:/ 9. S5 access request. Table 8: HTTP Methods for S5 Function Name Method Request Message Information Status Code Response Message Inform

18、ation access POST Path: OriginContentId Query: ATIS-IIF-MinBandwidth Query: ATIS-IIF-MaxBandwidth Query: ATIS-IIF-Subscriber-Scheme Query: ATIS-IIF-SourceIP Query:ATIS-IIF-SourcePort Query: ATIS-IIF-DestIP Query:ATIS-IIF-DestPort Authorization: scheme* 201 created 401 unauthorized 453 not enough ban

19、dwidth Location Header: COD-SCF Session URI Body: allocated session bandwidth Body: ECM* * Optional * See section 5.5 of ATIS-0800042 4. The S5 URI is created from the E6 URI by replacing the rtsp scheme with http and replacing the E6 URI hostname with the CoD SCF hostname and appending the ATIS-IIF

20、-MinBandwidth and ATIS-IIF-MaxBandwidth tags to the query. Example S5 URI: S5URI = http:/cod- ATIS-IIFMinBandwidth= ATIS-0800059 15 3750000 subscriber-scheme = “http“ / “https“ as indicated in E3n URI. ;IPv4address and IPv6address specified in section 3.2.2 of RFC 3986 10. CD reg-name specified in s

21、ection 3.2.2 of RFC 3986 10. Example S1 URI: http:/ reg-name specified in section 3.2.2 of RFC 3986 10. Example E3n URI: http:/iptv- 9. E9 download request HTTP GET. Table 18: HTTP Methods for E9 Function Name Method Request Message Information Status Code Response Message Information download GET P

22、ath: CD reg-name specified in section 3.2.2 of RFC 3986 10. Example E9 URI: http:/ 10. Check signed URI. 11. Caching proxy check for content internally. 12. E10 download request. ATIS-0800059 19 Table 19: HTTP Methods for E10 Function Name Method Request Message Information Status Code Response Mess

23、age Information download GET Path: OriginContentId 200 OK 302 Redirect 401 unauthorized 404 not found Body: requested content 13. Check signed URI. 14. E10 download response. 15. E9 download response. 16. Session termination with end of file. 4.1.3.5 Known Issues Asset preparation and distribution.

24、o None. Content selection and acquisition (On-Net portion). o Authentication details have not been specified by the ATIS IIF and therefore will not be included in the CoD Test Cases. Non-IMS redirect COD session establishment RTSP (On-Net portion). o None. Non-IMS redirect COD session termination RT

25、SP (On-Net portion). o None. Content selection and acquisition (Off-Net portion). o Authentication details have not been specified by the ATIS IIF and therefore will not be included in the CoD Test Cases. Off-Net delivery COD session HTTP (Off-Net portion). o None. 4.2 Content Provider & Service Pro

26、vider hosted Content Origin, Off-Net & On-Net The second multiscreen service use case is also for content delivery involving an On-Net ITF and an Off-Net ITF, based on the architecture described in Figure 8 of ATIS-0800042 4. In this case, however, the Content Origin Function is hosted by both the C

27、P and SP. Content and metadata are kept at the CP Content Origin Function and CP Application Functions for Off-Net delivery, and same content and metadata are ingested into the SP through A7 for On-Net delivery. The architecture shown in Figure 3 below applies specifically to the use case where ITF

28、#1 is connected to an NGN managed network and ITF #2 is using an unmanaged CDN, such as the Internet or an unmanaged mobile network (e.g., Wi-Fi). The configuration for the On-Net portion is defined in section 11.1.1 of ATIS-0800042 4 and the configuration for the Off-Net part is defined in section

29、11.2.4 of ATIS-0800042 4. For example, content could be delivered by the SP in HD quality to a Set-Top Box (STB) (ITF #1) when On-Net, while it would be delivered by the CP through a 3rdparty CDN using ATIS-DASH to a mobile device (ITF #2) when Off-Net. In this scenario, content delivered to ITF #2

30、is expected to be delivered in a different media format and protocol than when On-Net (ITF #1). ATIS-0800059 20 Figure 3: CP and SP hosted Content Origin Multiscreen Configuration 4.2.1 Resource Required The following components are required for this scenario: CP and SP Asset Preparation Function. C

31、P and SP Content Origin Function. CP and SP CoD Application Function. IPTV Control Functions. ATIS-0800059 21 CD&SF. ITF with CoD Application Client, Session Client, and Content Delivery Client Functions (2). 4.2.2 Message Flow Figure 4 represents the example when the subscriber navigates the catalo

32、g and purchases content using a device outside the home connected through a 3rdparty CDN i.e., through the Internet or mobile network (ISC Use Case 3 On-Net 4). He then continues to view the content using a STB when returning to the home (ISC Use Case 1 On-Net 4). ATIS-0800059 22 Figure 4: SP and CP

33、 hosted Content Origin Multiscreen Message Sequence ATIS-0800059 23 Steps 1 through 3 ingest both content and metadata from the Asset Source of the Internet CP to the SP Asset Preparation Functions. These content preparation steps are described in details in section 6.1 of ATIS-0800042 4, which incl

34、udes the related Figure 10. Steps 2 and 6 in section 6.1 of ATIS-0800042 4 are only applicable if encrypted content is used. It should also be noted that pull distribution via C5 and C6 (steps 3A and 4A) is used for this test scenario. Then, ITF #2 (which is outside the home and connected through a

35、3rd party CDN) interacts with the SP CoD Application Function for authentication, authorization, and access to content catalog through E1, which corresponds to step 4. In steps 5 to 7, ITF #2 is directed to the CP Application Function to access a particular CP content catalog for content selection a

36、nd acquisition via E8. Refer to Figure 14 in section 6.2.1 of ATIS-0800042 4 for steps 4 to 7. The test should cover both cases describe in section 6.2.1 of ATIS-0800042 4 i.e., subscriber viewing content already purchased (either from the beginning or from a bookmarked position in the content), as

37、well as subscriber actually buying content (steps 15 to 19). Steps 8 through 14 in Figure 4 above describe ITF #2 interaction with the IPTV Control Functions for session control followed by interaction with CD&SF #2 through the Off-Net Caching Proxy (3rdParty CDN) for Off-Net HTTP content download.

38、Refer to Figure 26, Case B, in section 6.13 of ATIS-0800042 4 for more details related to a download through a single HTTP GET transaction. Alternatively, refer to Figure 29, Case B, in section 6.16 of ATIS-0800042 4 for details of when the content is delivered in fragments using an adaptive HTTP st

39、reaming method such as DASH. Steps 4 and 5 of both Figure 26 and Figure 29 in ATIS-0800042 4 are not mandatory, but it is encouraged to include them in the test. It should also be noted that step 11 on Figure 4 above assumes the caching proxy does not have the requested content in its storage cache

40、and therefore content is retrieved in real time from the CP Content Origin Function (refer to Case B in section 6.1.2 of ATIS-0800042 4 for further details). When the subscriber returns home and wants to playback the entire content already purchased in step 7 or continue playback from the bookmarked

41、 position in step 14, ITF #1 interacts with the SP CoD Application Function for authentication, authorization, and content selection and obtains the E1 URI for the purchased content from step 15 through E1. Refer to Figure 13 in section 6.2 of ATIS-0800042 4 for the details of step 15. In this step,

42、 the SP CoD Application Function may show the list of selected content purchased in step 7 and authorized for viewing on ITF #1. Note that some content may not be allowed to be distributed to the different profile (or device type) of ITF #1 and this has to be taken into account in the test. The sele

43、cted content for ITF #1 (E1 URI) may include a different OriginContentId from that the one used for ITF #2 in step 7 (e.g., same title but in different format to allow viewing on ITF #2). The bookmark information (e.g., NPT playout position) may also be sent to ITF #1, which is used when continuing

44、playback from the point where terminated in step 14. Steps 8 and 10 of Figure 13 in ATIS-0800042 4 are not mandatory, but it is encouraged to include them in the test. It should also be noted that since the current use case considers previously purchased content, steps 9 to 11 in Figure 13 of ATIS-0

45、800042 4 are skipped. Steps 16 through 23 show ITF #1 interacting with the IPTV Control Functions for session control and then interacting with CD&SF #1 for content delivery using the RTSP method. Refer to Figure 21 of section 6.8 of ATIS-0800042 4 for details on these steps. Steps 3, 4, 10, 11, 14,

46、 and 15 of Figure 21 in ATIS-0800042 4 are not mandatory, but it is encouraged to include them in the test. Steps 18 and 19 are only applicable if encrypted content is used. It should also be noted that step 19 in Figure 4 above assumes the SP CD&SF does not have the requested content in its storage

47、 cache and therefore content is retrieved in real time from the SP content origin function (refer to section 6.1 of ATIS-0800042 4 for further details). Steps 24 through 29 describe ITF #1 interaction with CD&SF #1 for session termination using the RTSP method. Refer to Figure 23 of section 6.9 of ATIS-0800042 4 for the details of steps 24 to 29. Steps 4 and 5 in Figure 23 of ATIS-0800042 4 are not mandatory, but it is encouraged to include them in the test. 4.2.3 Test