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 (04/2017) 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 system: Personal Health Devices interface: 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 SER
3、VICES General H.200H.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
4、architecture for audiovisual 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, de
5、finitions, protocols 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 application
6、s and services H.540H.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.62
7、9 Ubiquitous sensor network 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 app
8、lication frameworks H.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 Multim
9、edia e-health data exchange services H.860H.869 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T H.840 (04/2017) i Recommendation ITU-T H.840 Conformance of ITU-T H.810 personal health system: Personal Health Devices interface: USB host Summary Recommendation ITU-T
10、H.840 provides a test suite structure (TSS) and the test purposes (TP) for the universal serial bus (USB) host in the Personal Health Devices (PHD) interface, based on the requirements defined in the Recommendations of the ITU-T H.810 sub-series, of which Recommendation ITU-T H.810 (2016) is the bas
11、e Recommendation. The objective of this test specification is to provide a high probability of interoperability at this interface. Recommendation ITU-T H.840 is a transposition of Continua Test Tool DG2016, Test Suite Structure it may contain versions that existed before transposition. Version Date
12、Revision history 1.1 2012-10-05 Initial release for Test Tool DG2011. It is the same version as “TSS 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 curren
13、tly valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T H.810 (2016) Recommendation ITU-T H.810 (2016), Interoperability design guidelines for personal health sys
14、tems. ISO/IEEE 11073-10419 ISO/IEEE 11073-10419:2016, Health informatics - Personal health device communication - Part 10419: Device specialization - Insulin pump. https:/www.iso.org/standard/69528.html ISO/IEEE 11073-10424 ISO/IEEE 11073-10424:2016, Health informatics -Personal health device commun
15、ication - Part 10424: Device specialization - Sleep apnoea breathing therapy equipment (SABTE). https:/www.iso.org/standard/68906.html ISO/IEEE 11073-10425 ISO/IEEE 11073-10425:2016, Health informatics - Personal health device communication - Part 10425: Device specialization - Continuous glucose mo
16、nitor (CGM). https:/www.iso.org/standard/67821.html ISO/IEEE 11073-20601-2015A ISO/IEEE 11073-20601:2010, Health informatics Personal health device communication Part 20601: Application profile Optimized exchange protocol, including ISO/IEEE 11073-20601:2010 Amd. 1:2015. https:/www.iso.org/standard/
17、54331.html with https:/www.iso.org/standard/63972.html ISO/IEEE 11073-20601-2016C ISO/IEEE 11073-20601:2016, Health informatics Personal health device communication Part 20601: Application profile Optimized exchange protocol, including ISO/IEEE 11073-_ 1 This Recommendation includes an electronic at
18、tachment 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 (04/2017) 20601:2016/Cor.1:2016. https:/www.iso.org/standard/66717.html with https:/www.iso.org
19、/standard/71886.html USB DevClass USB Implementers Forum (2007-11), Universal Serial Bus Device Class Definition for Personal Healthcare Devices, Release 1.0, plus Errata (15 February 2008), Personal Healthcare section. http:/www.usb.org/developers/docs/devclass_docs/Personal_Healthcare_1.zip USB 2.
20、0 USB Implementers Forum (2000), Universal Serial Bus Specification 2.0. http:/www.usb.org/developers/docs/usb20_docs/usb_20_112614.zip 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 agent ISO/IEEE 11073-20601-2016C: A node that collec
21、ts and transmits personal health data to an associated manager. 3.1.2 manager ISO/IEEE 11073-20601-2016C: A node receiving data from one or more agent systems. Some examples of managers include a cellular phone, health appliance, set top box, or a computer system. 3.2 Terms defined in this Recommend
22、ation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: ATS Abstract Test Suite CDG Continua Design Guidelines CESL Continua Enabling Software Library DUT Device Under Test GUI Graphical User Interface INR International Normalized Ratio IP Insulin
23、Pump IUT Implementation Under Test MDS Medical Device System PAN Personal Area Network PCT Protocol Conformance Testing PCO Point of Control and Observation PHD Personal Health Device PHDC Personal Healthcare Device Class PHG Personal Health Gateway Rec. ITU-T H.840 (04/2017) 3 PICS Protocol Impleme
24、ntation Conformance Statement PIXIT Protocol Implementation extra Information for Testing SDP Service Discovery Protocol SABTE Sleep Apnoea Breathing Therapy Equipment SCR Static Conformance Review SOAP Simple Object Access Protocol SUT System Under Test TCRL Test Case Reference List TCWG Test and C
25、ertification Working Group TP Test Purpose TSS Test Suite Structure USB Universal Serial 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 t
26、o must or it is required to. SHALL NOT is equivalent to must not or it is not allowed. SHOULD is equivalent to it is recommended to. SHOULD NOT is equivalent to it is not recommended to. MAY is equivalent to is permitted. MAY NOT is equivalent to it is not required that. NOTE The above-mentioned key
27、 words are capitalized for illustrative purposes only and 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 u
28、sed in this Recommendation is provided in Table 1. 4 Rec. ITU-T H.840 (04/2017) Table 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
29、bugs b-CDG 2016. 2016 6.0 Release 2016 of the CDG including maintenance updates of the CDG 2015 and additional guidelines that cover new functionalities. Iris 2015 plus errata b-ITU-T H.810 (2015) 5.1 Release 2015 plus errata noting all ratified bugs b-CDG 2015. The 2013 edition of H.810 is split in
30、to eight parts in the H.810-series. 2015 5.0 Release 2015 of the CDG including maintenance updates of the CDG 2013 and additional guidelines that cover new functionalities. Genome 2013 plus errata b-ITU-T H.810 (2013) 4.1 Release 2013 plus errata noting all ratified bugs b-CDG 2013. 2013 4.0 Release
31、 2013 of the CDG including maintenance updates of the CDG 2012 and additional guidelines that cover new functionalities. Endorphin 2012 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 add
32、itional guidelines that cover new functionalities. Catalyst 2011 plus errata 2.1 CDG 2011 integrated with identified errata. 2011 2.0 Release 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
33、 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 additional guidelines that cover new functionalities b-CDG 2010. 1.5 1.0 1.0 First released version of the CDG b-CDG 1.0. Rec. ITU-T H.840 (04/2017) 5 6 Test suite struc
34、ture (TSS) The test purposes (TPs) of this Recommendation are found in Annex A and have been divided into two main groups: Group 1: Descriptors (DESC) Group 2: Metadata message preamble (MDMP) Subgroup 2.1: Metadata message preamble feature (FEAT) Subgroup 2.2: Get data status before setting/clearin
35、g metadata message preamble feature (GDS) Subgroup 2.3: Set/Clear Metadata message preamble feature (SC) Subgroup 2.4: Metadata message preamble transfer (TRANS) Subgroup 2.5: Metadata message preamble feature error conditions (ERR) 7 Electronic attachment The protocol implementation conformance sta
36、tements (PICS) and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A can be downloaded 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
37、 between “PICS“ and “PIXIT“ respectively during testing. If the cell is empty, the corresponding PICS is “independent“. If the field contains 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
38、(SCR) is used in the test tool to assert whether the PICS selection is consistent. 6 Rec. ITU-T H.840 (04/2017) Annex A Test purposes (This 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:
39、 This is a unique identifier (TP/ ). It is specified according to the naming convention defined below: Each test purpose identifier is introduced 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 tes
40、t. 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 test 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 sequenti
41、al number that identifies the test purpose. TP label: This is the TPs title. Coverage: This contains the specification reference and clause 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. Tes
42、table Item: This contains the testable items to be checked by the TP. Test purpose: This is a description of the requirements to be tested. 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 i
43、t means that it applies to the device under test within that scope of the test (specialization, transport used, etc.). Other PICS: This contains 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
44、verdict. When this row is empty, it means that only the PICS specified in the Applicability row are used within the test case implementation. 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 b
45、e followed in order to execute the test case. Pass/Fail criteria: This provides criteria to decide whether the DUT passes or fails the test case. Rec. ITU-T H.840 (04/2017) 7 A.2 Group 1: Descriptors (DESC) TP Id TP/PHDC/HOS/DESC/BV-000_A TP label Device class in interface descriptor Coverage Spec U
46、SB DevClass Testable items DeviceDesc 1; M Test purpose Check that: USB Host acknowledges the simulated device descriptors AND It recognizes 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 plugge
47、d into the host under test. Test procedure 1. Connect the host under test and simulated device, then the enumeration 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 de
48、vice descriptor is set to 00h and bInterfaceClass of the interface descriptor is set to 0Fh. 2. The simulated device 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
49、 “Association Abort“ message. Pass/Fail criteria In step 3, the host under test replies with an “Association Response“(accepted, accepted-unknown-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
