ATIS 0800051-2011 Test Cases for Remote Management of Consumer Domain Devices and QoS Metric Reporting.pdf

1、 ATIS-0800051 TEST CASES FOR REMOTE MANAGEMENT OF CONSUMER DOMAIN DEVICES AND QOS METRIC REPORTING 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 committ

2、ed to the rapid development of global, 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 Technologi

3、es, Quality of Service, Billing 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 Sec

4、urity, Policy Management and Network 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 Int

5、er-American Telecommunication Commission (CITEL). ATIS is accredited by the American National Standards Institute (ANSI). For more information, please visit . Notice of Disclaimer therefore, for clarity, a simplified network configuration diagram is detailed at the beginning of each scenario. 4 SCEN

6、ARIO 4 TEST CASES: REMOTE MANAGEMENT OF CONSUMER DOMAIN DEVICES AND QOS METRIC REPORTING 4.1 Scenario 4a: Software Download Management Software download management is part of the remote device management service to download or update required software from the Remote Configuration and Management Ser

7、ver (RCMS) and/or Software Download Server (SDS) to the managed devices. Software to be downloaded includes the following: An executable (image) running on the device. Updates to certain modules of the executable. Applications/modules running on top of the basic executable image. Profile files for t

8、he customization of certain features and services on the managed device. The test cases are to verify the protocol usage, processes, and content for software download to DNG. There are four sub-test cases for scenario 4a: Test case 4a1: Software download for mobile devices. Test case 4a2: Software d

9、ownload for TR-069 devices unicast download. Test case 4a3: Software download for TR-069 devices multicast download with unicast control. Test case 4a4: Software download for TR-069 devices multicast download with multicast control. Software download architecture and the basic configuration for Scen

10、ario 4a are shown in Figure 1 and Figure 2. ATIS-0800051 4 Figure 1: Software Download Architecture The CPE software download reference points map to ATIS-0800009, Remote Management of Devices in the Consumer Domain for IPTV Services 5 (shown in Figure 1), and to corresponding interfaces in ETSI TS

11、102 824 17 as follows: Table 1: Reference Point Mappings Physical Scenarios Interfaces ATIS-0800009 ETSI DVB H4 i1 H6 i2 H7 e1 5 H8 f1 6 H9 e2 5 H10 f2 6 T2 d 4 ATIS-0800051 5 Figure 2: Scenario 4a Basic Configuration Scenario 4a test cases follow the procedures shown in the sequence diagram in Figu

12、re 3. Figure 3: Software Download Sequence ATIS-0800051 6 4.1.1 Test Case 4a1: Software Download for Mobile Devices Software download for mobile devices will follow Open Mobile Alliance Device Management (OMA-DM) specifications 1213. The IPTV Terminal Function (ITF) component of the mobile device wi

13、ll still be managed by the RCMS for software download. 4.1.1.1 Test Setup Transport & Access NetworksTransport Processing FunctionsSDSSoftware DL ManagerMobile DeviceITFNACFRCMSH6H9H10T2Figure 4: Scenario 4a1 Basic Configuration for Mobile Devices 4.1.1.2 Resources Required The following components

14、are required for this scenario: Transport Network Elements (Access Node, Edge Router). One RCMS. One SDS. One mobile device with embedded ITF. 4.1.1.3 Test Pre-Conditions 1. The ITF and DNG are initialized, authenticated, and operating in the network. 2. The device learns the RCMS URL and gets initi

15、al provisioning. 4.1.1.4 Procedure The software download procedure follows the sequence for OMA-DM devices in Figure 3. See also the message flow in Figure 5. 4.1.1.5 Observable Results The following results may be observed: ATIS-0800051 7 1. Verify that the protocols permit a connection between the

16、 RCMS and the ITF and between the SDS and the ITF. 2. The availability of new software version is advertised by the RCMS or requested by the ITF. 3. The new software version is updated on the ITF. 4. The RCMS queries or receives information that the software is updated on the ITF. 4.1.1.6 Pass/Fail

17、Criteria Pass: RCMS receives confirmation that the software is updated on the ITF. Fail: o Software is not updated. o Software is updated but the RCMS does not receive confirmation. 4.1.1.7 Message Flow Figure 5: OMA FUMO Software Download for Scenario 4a 1. OMA FUMO PUSH Initiation sent by the RCMS

18、 as the OMA-DM server over H6 (i2). 2. The device exchanges information with the RCMS over H6 (i2). 3. The RCMS writes/updates the download object on the device which include the image URL. ATIS-0800051 8 4. The RCMS commands the device to execute the download operation. 5. The device downloads the

19、software image from the download server using OMA-DM FUMO protocol. 6. The device acknowledges to the RCMS the results of the download operation using the Generic Alert message for OMA-DM. 4.1.1.8 Trace Capture The main focus of this test case is the interaction between the ITF and the RCMS/SDS. The

20、 traces of the messages exchanged on the H6, H9, and H10 interfaces should be captured during the testing and validated against the test case descriptions. 4.1.1.9 Known Issues None. 4.1.2 Test Case 4a2: Unicast Software Download for TR-069 Devices 4.1.2.1 Test Setup Figure 6: Test Case 4a2 Configur

21、ation 4.1.2.2 Resource Required Transport Network Elements (Access Node, Edge Router). One RCMS. One SDS. One DNG. One ITF. ATIS-0800051 9 4.1.2.3 Test Pre-conditions 1. The ITF and DNG are initialized, authenticated, and operating in the network. 2. The device learns RCMS URL and gets initial provi

22、sioning. 4.1.2.4 Procedure See the sequence diagram in Figure 3. 1. The device establishes a TR-069 session with the RCMS. 2. The RCMS directs the device to initiate a software download operation and provides the SDS URL via TR-069 14. 3. The device downloads the software image from the SDS using HT

23、TP(S) protocol. Optionally, FTP, SFTP, or TFTP may also be used. 4. The device acknowledges the results of the download operation to the RCMS using the Inform message. 4.1.2.5 Observable Results The following results may be observed: 1. Verify that the protocols permit a connection between the RCMS

24、and the DNG and ITF and between the SDS and the DNG and ITF. 2. The availability of the new software version is advertised by the RCMS or requested by the DNG or ITF. 3. The new software version is updated on either the DNG or ITF. 4. The RCMS queries or receives information that the software is upd

25、ated on either the DNG or ITF. 4.1.2.6 Pass/Fail Criteria Pass: RCMS receives confirmation that the software is updated on either the DNG or ITF. Fail: o Software is not updated. o Software is updated but the RCMS does not receive confirmation. ATIS-0800051 10 4.1.2.7 Message Flow SDSITF/ DNGRCMSSof

26、tware Download ManagerExternal Firmware Update SystemSend TR-69 RPCTR-69 Response:DL server URL providedHTTP Request via H8 (DNG) or H10 (ITF)Request new softwareDownload softwareTR-69 InformInitiate software updateFigure 7: Unicast Software Download for TR-69 Devices 4.1.2.8 Trace Capture The main

27、focus of this test case is the interaction between the DNG/ITF and the RCMS/SDS. The traces of the messages exchanged on the H8 and H10 interfaces should be captured during the testing and validated against the test case descriptions. 4.1.2.9 Known Issues None. ATIS-0800051 11 3.1.3 Test Case 4a3: M

28、ulticast Software Download for TR-069 Devices with Unicast Control 3.1.3.1 Test Setup Figure 8: Test Case 4a3 Configuration 4.1.3.2 Resource Required Transport Network Elements (Access Node, Edge Router). One RCMS. One SDS. One DNG. One ITF. 4.1.3.3 Test Pre-conditions 1. The ITF and DNG are initial

29、ized, authenticated, and operating in the network 2. The device learns the RCMS URL and gets initial provisioning and required parameters, as specified in ATIS-0800013 6 and ATIS-0800017 8. 4.1.3.4 Procedure See the sequence diagram in Figure 3. 1. The device establishes a TR-069 session with the RC

30、MS. 2. The RCMS directs the device to initiate a software download operation, and provides the URL for file atis-iif-resourcelocator.xml 9. 3. The device retrieves the atis-iif-resourcelocator.xml file and determines the multicast channel group to join. 4. The device uses IGMP to join the download m

31、ulticast channel group and downloads the software image using FLUTE. The usage of IGMP and FLUTE is as specified in ATIS-0800013 6. 5. The device leaves the multicast group. ATIS-0800051 12 6. The device acknowledges the results of the download operation to the RCMS using the Inform message. 4.1.3.5

32、 Observable Results The following results may be observed: 1. Verify that the protocols permit a connection between the RCMS and the DNG and ITF and between the SDS and the DNG and ITF. 2. The availability of new software version is advertised by the RCMS or requested by the DNG or ITF. 3. The new s

33、oftware version is updated on either the DNG or ITF. 4. The RCMS queries or receives information that the software is updated on either the DNG or ITF. 4.1.3.6 Pass/Fail Criteria Pass: RCMS receives confirmation that the software is updated on either the DNG or ITF. Fail: o Software is not updated.

34、o Software is updated but the RCMS does not receive confirmation. 4.1.3.7 Message Flow Send TR-69 RPCTR-69 Response:Provide URL for atis-iif-resorcelocator.xmlRetrieve atis-iif-resorcelocator.xmlSDSITF/ DNGRCMSSoftware Download ManagerExternal Firmware Update SystemTR-69 Inform Multicast Join IGMP v

35、2/v3 Network Provider Multicast ServerMulticast Transport FunctionFLUTE file DL protocolSoftware multicastFLUTE file DL protocolSoftware multicastFigure 9: Multicast Software Download for TR-69 Devices with Unicast Control ATIS-0800051 13 4.1.3.8 Trace Capture The main focus of this test case is the

36、 interaction between the DNG/ITF and the RCMS/SDS. The traces of the messages exchanged on the H7 and H9 interfaces should be captured during the testing and validated against the test case descriptions. 4.1.3.9 Known Issues None. 4.1.4 Test Case 4a4: Multicast Software Download for TR-069 Devices w

37、ith Multicast Announcement 4.1.4.1 Test Setup Figure 10: Test Case 4a4 Configuration 4.1.4.2 Resource Required Transport Network Elements (Access Node, Edge Router). One RCMS. One SDS. One DNG. One ITF. One multicast source of the announcement (not shown). 4.1.4.3 Test Pre-Conditions 1. The ITF and

38、DNG are initialized, authenticated, and operating in the network. 2. The device learns the RCMS URL and gets initial provisioning. ATIS-0800051 14 4.1.4.4 Procedure 1. The network provider advertises to the devices the need to download a new image and the multicast group to join. 2. The device uses

39、IGMP to join to the multicast group and downloads the software image using FLUTE. 3. The device leaves the multicast group. 4. The device acknowledges the results of the download operation to the RCMS using the Inform message. 4.1.4.5 Observable Results The following results may be observed: 1. The

40、protocols permit a connection between the RCMS and the DNG and ITF and between the SDS and the DNG and ITF. 2. The availability of the new software version is advertised by the RCMS or requested by the DNG or ITF. 3. The new software version is updated on either the DNG or ITF. 4. The RCMS queries o

41、r receives information that the software is updated on either the DNG or ITF. 4.1.4.6 Pass/Fail Criteria Pass: RCMS receives confirmation that the software is updated on either the DNG or ITF. Fail: o Software is not updated. o Software is updated but the RCMS does not receive confirmation. 4.1.4.7

42、Message Flow SDSITF/ DNGRCMSSoftware Download ManagerExternal Firmware Update SystemTR-69 InformNetwork Provider Multicast ServerMulticast Transport FunctionMulticast Join IGMP v2/v3 FLUTE file DL protocolSoftware multicastFLUTE file DL protocolSoftware multicastMulticast AnnouncementFigure 11: Mult

43、icast Download for TR-69 Devices with Multicast Announcement ATIS-0800051 15 4.1.4.8 Trace Capture The main focus of this test case is the interaction between the DNG/ITF and the RCMS/SDS. The traces of the messages exchanged on the H7 and H9 interfaces should be captured during the testing and vali

44、dated against the test case descriptions. 4.1.4.9 Known Issues None. 4.2 Scenario 4b: Remote Device Management Remote device management is the process with which service providers can provision and configure a mobile device, DNG, or ITF. Test cases for this scenario are to verify that the device is

45、initialized. Live video is present on its display. The RCMS queries and receives confirmation of the devices configuration parameters. There are three test cases for scenario 4b: Test case 4b1: Configuration and Provisioning for OMA-Compliant Mobile Device. Test case 4b2: Configuration and Provision

46、ing for TR-069 Compliant DNG. Test case 4b3: Configuration and Provisioning for TR-069 Compliant ITF. 4.2.1 Test Case 4b1: Configuration and Provisioning for OMA-Compliant Mobile Device 4.2.1.1 Test Setup Transport Processing FunctionsMobile DeviceITFNACFRCMSH6Figure 12: Test Case 4b1 Configuration

47、4.2.1.2 Resources Required Transport Network Elements. One RCMS. ATIS-0800051 16 One mobile device with embedded ITF. 4.2.1.3 Test Pre-Conditions User is logged in to the mobile device. 4.2.1.4 Procedure 1. The RCMS queries the mobile device. 2. The mobile device sends the configuration parameters a

48、s requested. 4.2.1.5 Observable Results 1. The mobile device is configured. 2. The RCMS queries and receives confirmation of the devices configuration parameters. 4.2.1.6 Pass/Fail Criteria Pass: The mobile device is configured and verified. Fail: o The mobile device is not configured. o The mobile

49、device is configured but cannot be verified. 4.2.1.7 Message Flow Figure 13: Configuration and Provisioning for OMA-Compliant Mobile Device ATIS-0800051 17 4.2.1.8 Trace Capture The main focus of this test case is the interaction between the RCMS and the mobile device. The traces of the messages exchanged on the H6 interface should be captured during the testing and validated against the test case descriptions. 4.2.1.9 Known