1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T H.840 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2016) SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS E-health multimedia services and applications Interoperability compliance testing of personal health systems (HRN,
2、 PAN, LAN, TAN and WAN) Conformance of ITU-T H.810 personal health devices: PAN/LAN/TAN: USB host Recommendation ITU-T H.840 ITU-T H-SERIES RECOMMENDATIONS AUDIOVISUAL AND MULTIMEDIA SYSTEMS CHARACTERISTICS OF VISUAL TELEPHONE SYSTEMS H.100H.199 INFRASTRUCTURE OF AUDIOVISUAL SERVICES General H.200H.
3、219 Transmission multiplexing and synchronization H.220H.229 Systems aspects H.230H.239 Communication procedures H.240H.259 Coding of moving video H.260H.279 Related systems aspects H.280H.299 Systems and terminal equipment for audiovisual services H.300H.349 Directory services architecture for audi
4、ovisual and multimedia services H.350H.359 Quality of service architecture for audiovisual and multimedia services H.360H.369 Telepresence H.420H.429 Supplementary services for multimedia H.450H.499 MOBILITY AND COLLABORATION PROCEDURES Overview of Mobility and Collaboration, definitions, protocols
5、and procedures H.500H.509 Mobility for H-Series multimedia systems and services H.510H.519 Mobile multimedia collaboration applications and services H.520H.529 Security for mobile multimedia systems and services H.530H.539 Security for mobile multimedia collaboration applications and services H.540H
6、.549 Mobility interworking procedures H.550H.559 Mobile multimedia collaboration inter-working procedures H.560H.569 BROADBAND, TRIPLE-PLAY AND ADVANCED MULTIMEDIA SERVICES Broadband multimedia services over VDSL H.610H.619 Advanced multimedia services and applications H.620H.629 Ubiquitous sensor n
7、etwork applications and Internet of Things H.640H.649 IPTV MULTIMEDIA SERVICES AND APPLICATIONS FOR IPTV General aspects H.700H.719 IPTV terminal devices H.720H.729 IPTV middleware H.730H.739 IPTV application event handling H.740H.749 IPTV metadata H.750H.759 IPTV multimedia application frameworks H
8、.760H.769 IPTV service discovery up to consumption H.770H.779 Digital Signage H.780H.789 E-HEALTH MULTIMEDIA SERVICES AND APPLICATIONS Personal health systems H.810H.819 Interoperability compliance testing of personal health systems (HRN, PAN, LAN, TAN and WAN) H.820H.859 Multimedia e-health data ex
9、change services H.860H.869 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.840 (07/2016) i Recommendation ITU-T H.840 Conformance of ITU-T H.810 personal health devices: PAN/LAN/TAN: USB host Summary Recommendation ITU-T H.840 is a transposition of Continua Test
10、Tool DG2013, Test Suite Structure users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The referen
11、ce to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T H.810 (2015) Recommendation ITU-T H.810 (2015), Interoperability design guidelines for personal health systems. ITU-T H.810 (2016) Recommendation ITU-T H.810 (2016), Interop
12、erability design guidelines for personal health systems. IEEE 11073-20601A IEEE 11073-20601A-2010, IEEE Health informatics Personal health device communication Part 20601: Application profile Optimized Exchange Protocol Amendment 1. USB DevClass USB Implementers Forum (2007-11), Universal Serial Bus
13、 Device Class Definition for Personal Healthcare Devices, Release 1.0, plus Errata (15 February 2008), Personal Healthcare section. USB 2.0 USB Implementers Forum (2000), Universal Serial Bus Specification 2.0. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms de
14、fined elsewhere: 3.1.1 agent IEEE 11073-20601A: A node that collects and transmits personal health data to an associated manager. 3.1.2 manager IEEE 11073-20601A: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box,
15、or a computer system. _ 1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. 2 Rec. ITU-T H.840 (07/2016) 3.2 Terms defi
16、ned in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ATS Abstract Test Suite CDG Continua Design Guidelines DUT Device Under Test GUI Graphical User Interface IUT Implementation Under Test MDS Medical Device System PAN Perso
17、nal Area Network PCT Protocol Conformance Testing PCO Point of Control and Observation PCHA Personal Connected Health Alliance PHD Personal Healthcare Device PHDC Personal Healthcare Device Class PHM Personal Health Manager PICS Protocol Implementation Conformance Statement PIXIT Protocol Implementa
18、tion extra Information for Testing SDP Service Discovery Protocol SABTE Sleep Apnoea Breathing Therapy Equipment SOAP Simple Object Access Protocol SUT System Under Test TCRL Test Case Reference List TCWG Test and Certification Working Group TP Test Purpose TSS Test Suite Structure USB Universal Ser
19、ial Bus WDM Windows Driver Model 5 Conventions The key words “SHALL“, “SHALL NOT“, “SHOULD“, “SHOULD NOT“, “MAY“, “MAY NOT“ in this Recommendation are to be interpreted as in b-ETSI SR 001 262. SHALL is equivalent to must or it is required to. SHALL NOT is equivalent to must not or it is not allowed
20、. SHOULD is equivalent to it is recommended to. SHOULD NOT is equivalent to it is not recommended to. Rec. ITU-T H.840 (07/2016) 3 MAY is equivalent to is permitted. MAY NOT is equivalent to it is not required that. NOTE The above-mentioned key words are capitalized for illustrative purposes only an
21、d they do not appear capitalized within this Recommendation. Reference is made in the ITU-T H.800-series of Recommendations to different versions of the Continua Design Guidelines (CDG) by a specific designation. The list of terms that may be used in this Recommendation is provided in Table 1. Table
22、 1 List of designations associated with the various versions of the CDG CDG release Transposed as Version Description Designation 2016 plus errata ITU-T H.810 (2016) 6.1 Release 2016 plus errata noting all ratified bugs ITU-T H.810 (2016). 2016 6.0 Release 2016 of the CDG including maintenance updat
23、es of the CDG 2015 and additional guidelines that cover new functionalities. Iris 2015 plus errata ITU-T H.810 (2015) 5.1 Release 2015 plus errata noting all ratified bugs ITU-T H.810 (2015). 2015 5.0 Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines tha
24、t cover new functionalities. Genome 2013 plus errata ITU-T H.810 (2013) 4.1 Release 2013 plus errata noting all ratified bugs b-ITU-T H.810 (2013). 2013 4.0 Release 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. Endorphin 2012
25、plus errata 3.1 Release 2012 plus errata noting all ratified bugs b-CDG 2012. 2012 3.0 Release 2012 of the CDG including maintenance updates of the CDG 2011 and additional guidelines that cover new functionalities. Catalyst 2011 plus errata 2.1 CDG 2011 integrated with identified errata. 2011 2.0 Re
26、lease 2011 of the CDG including maintenance updates of the CDG 2010 and additional guidelines that cover new functionalities b-CDG 2011. Adrenaline 2010 plus errata 1.6 CDG 2010 integrated with identified errata 2010 1.5 Release 2010 of the CDG with maintenance updates of the CDG Version 1 and addit
27、ional guidelines that cover new functionalities b-CDG 2010. 1.5 1.0 1.0 First released version of the CDG b-CDG 1.0. 4 Rec. ITU-T H.840 (07/2016) 6 Test suite structure (TSS) The test purposes (TPs) of this Recommendation are found in Annex A and have been divided into two main groups: Group 1: Desc
28、riptors (DESC) Group 2: Metadata message preamble (MDMP) Subgroup 2.1: Metadata message preamble feature (FEAT) Subgroup 2.2: Get data status before setting/clearing metadata message preamble feature (GDS) Subgroup 2.3: Set/Clear Metadata message preamble feature (SC) Subgroup 2.4: Metadata message
29、preamble transfer (TRANS) Subgroup 2.5: Metadata message preamble feature error conditions (ERR) 7 Electronic attachment The protocol implementation conformance statements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be d
30、ownloaded from http:/handle.itu.int/11.1002/2000/12067. In the electronic attachment, letters “C“ and “I“ in the column labelled “Mandatory“ are used to distinguish between “PICS“ and “PIXIT“ respectively during testing. If the cell is empty, the corresponding PICS is “independent“. If the field con
31、tains a “C“, the corresponding PICS is dependent on other PICS, and the logical expression is detailed in the “SCR_Expression“ field. The static conformance review (SCR) is used in the test tool to assert whether the PICS selection is consistent. Rec. ITU-T H.840 (07/2016) 5 Annex A Test purposes (T
32、his annex forms an integral part of this Recommendation.) A.1 TP definition conventions The test purposes (TPs) are defined according to the following rules: TP Id: This is a unique identifier (TP/ ). It is specified according to the naming convention defined below: Each test purpose identifier is i
33、ntroduced by the prefix “TP“. : This is the test tool that will be used in the test case. PHDC: USB host personal health device class : This is the device under test. HOS: PHDC host DEV: PHDC device (not used because it is out of the scope of the developed test tool) : This identifies a group of tes
34、t cases. : This identifies a subgroup of test cases. : This identifies the type of testing. BV: valid behaviour test BI: invalid behaviour test : This is a sequential number that identifies the test purpose. TP label: This is the TPs title. Coverage: This contains the specification reference and cla
35、use to be checked by the TP. Spec: This indicates the earliest version of the specification from which the testable items to be checked by the TP were included. Testable Item: This contains testable items to be checked by the TP. Test purpose: This is a description of the requirements to be tested.
36、Applicability: This contains the PICS items that define if the test case is applicable or not for a specific device. When a TP contains an “ALL“ in this field it means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). Other PICS: This cont
37、ains additional PICS items (apart from the PICS specified in the Applicability row) which are used within the test case implementation and can modify the final verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation
38、. Initial condition: This indicates the state to which the DUT needs to be moved at the beginning of TC execution. Test procedure: This describes the steps to be followed in order to execute the test case. Pass/Fail criteria: This provides criteria to decide whether the DUT passes or fails the test
39、case. 6 Rec. ITU-T H.840 (07/2016) A.2 Group 1: Descriptors (DESC) TP Id TP/PHDC/HOS/DESC/BV-000_A TP label Device class in interface descriptor Coverage Spec USB DevClass Testable items DeviceDesc 1; M Test purpose Check that: USB Host acknowledges the simulated device descriptors AND It recognizes
40、 PHDC device class when it is set in device descriptor Applicability C_MAN_OXP_038 AND C_MAN_OXP_000 Other PICS Initial condition The simulated device is plugged into the host under test. Test procedure 1. Connect the host under test and simulated device, then the enumeration process shall start aut
41、omatically. During this process the host will issue a GetDescriptor() request to the test tool device. On the test tool device the bDeviceClass field of the device descriptor is set to 00h and bInterfaceClass of the interface descriptor is set to 0Fh. 2. The simulated device issues an “Association R
42、equest“ message to the host under test. 3. The host under test shall reply with an “Association Response“ (accepted, accepted-unknown-config or rejected) or an “Association Abort“ message. Pass/Fail criteria In step 3, the host under test replies with an “Association Response“(accepted, accepted-unk
43、nown-config or rejected) or an “Association Abort“ message. Notes TP Id TP/PHDC/HOS/DESC/BV-000_B TP label Device class in device descriptor Coverage Spec USB DevClass Testable items DeviceDesc 1; M Test purpose Check that: USB Host acknowledges the simulated device descriptors AND It recognizes PHD
44、C device class when it is set in interface descriptor Applicability C_MAN_OXP_038 AND C_MAN_OXP_000 Other PICS Initial condition The simulated device is plugged into the host under test. Rec. ITU-T H.840 (07/2016) 7 Test procedure 1. Connect the host under test and simulated device, then the enumera
45、tion process shall start automatically. During this process the host will issue a GetDescriptor() request to the test tool device. On the test tool device the bDeviceClass field of the device descriptor is set to 0Fh and bInterfaceClass of the interface descriptor is set to 00h. 2. The simulated dev
46、ice issues an “Association Request“ message to the host under test. 3. The host under test shall reply with an “Association Response“ (accepted, accepted-unknown-config or rejected) or an “Association Abort“ message. Pass/Fail criteria In step 3, the host under test replies with an “Association Resp
47、onse“ (accepted, accepted-unknown-config or rejected) or an “Association Abort“ message. Notes TP Id TP/PHDC/HOS/DESC/BV-001_A TP label Verify class-defined USB descriptors (no PHDC metadata descriptor, data format code defined by vendor) Coverage Spec USB DevClass Testable items ClassFunDesc 1; M C
48、lassFunDesc 2; M ClassFunDesc 3; M ClassFunDesc 4; M ClassFunDesc 6; M ClassFunExtDesc 1; M ClassFunExtDesc 3; M ClassFunExtDesc 4; M ClassFunExtDesc 5; M ClassFunExtDesc 7; M ClassFunExtDesc 8; M ClassFunExtDesc 9; M MetaDataDesc 1; M MetaDataDesc 2; M MetaDataDesc 3; M MetaDataDesc 4; M Test purpo
49、se Check that: USB Host acknowledges the simulated device descriptors AND It recognizes PHDC device class if PHDC Meta-Data Descriptor is not sent and data format code is defined by vendor. Applicability C_MAN_OXP_038 AND C_MAN_OXP_000 Other PICS Initial condition The simulated device is plugged into the host under test. Test procedure 1. Connect the hos
