ITU-T H 830 1-2017 Conformance of ITU-T H 810 personal health system Services interface Part 1 Web services interoperability Health & Fitness Service sender (Study Group 16).pdf

《ITU-T H 830 1-2017 Conformance of ITU-T H 810 personal health system Services interface Part 1 Web services interoperability Health & Fitness Service sender (Study Group 16).pdf》由会员分享，可在线阅读，更多相关《ITU-T H 830 1-2017 Conformance of ITU-T H 810 personal health system Services interface Part 1 Web services interoperability Health & Fitness Service sender (Study Group 16).pdf（46页珍藏版）》请在麦多课文档分享上搜索。

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.830.1 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 (HR

2、N, PAN, LAN, TAN and WAN) Conformance of ITU-T H.810 personal health system: Services interface Part 1: Web services interoperability: Health Part 1: Web Services Interoperability. HFS Sender (Version 1.6, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of version

3、s of this specification existed before transposition. 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. History Edition

4、 Recommendation Approval Study Group Unique ID* 1.0 ITU-T H.831 2015-01-13 16 11.1002/1000/12249 1.0 ITU-T H.830.1 2015-01-13 16 11.1002/1000/12587 2.0 ITU-T H.830.1 2016-07-14 16 11.1002/1000/12921 3.0 ITU-T H.830.1 2017-04-13 16 11.1002/1000/13201 Keywords Conformance testing, Continua Design Guid

5、elines, e-health, Health Part 1: Web Services Interoperability. HFS Sender (Version 1.6, 2017-03-14), that was developed by the Personal Connected Health Alliance. The table below shows the revision history of this test specification; it may contain versions that existed before transposition. Versio

6、n Date Revision history 1.2 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

7、 currently 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 hea

8、lth systems. ITU-T H.812 Recommendation ITU-T H.812 (2016), Interoperability design guidelines for personal health systems: Services interface: Common certified capability class. _ 1 This Recommendation includes an electronic attachment with the protocol implementation conformance statements (PICS)

9、and the protocol implementation extra information for testing (PIXIT) required for the implementation of Annex A. 2 Rec. ITU-T H.830.1 (04/2017) ITU-T H.812.1 Recommendation ITU-T H.812.1 (2016), Interoperability design guidelines for personal health systems: Services interface: Observation upload c

10、ertified capability class. ITU-T H.812.2 Recommendation ITU-T H.812.2 (2016), Interoperability design guidelines for personal health systems: Services interface: Questionnaires certified capability class. ITU-T H.812.3 Recommendation ITU-T H.812.3 (2016), Interoperability design guidelines for perso

11、nal health systems: Services interface: Capability exchange certified capability class. ITU-T H.812.4 Recommendation ITU-T H.812.4 (2016), Interoperability design guidelines for personal health systems: Services interface: Authenticated persistent session certified capability class. OASIS/WS-I BP OA

12、SIS/WS-I (2006), Basic Profile Version 1.1. http:/www.ws-i.org/Profiles/BasicProfile-1.1.html OASIS/WS-I BSP OASIS/WS-I (2007), Basic Security Profile Version 1.0. http:/www.ws-i.org/Profiles/BasicSecurityProfile-1.0.html OASIS WS-I RM OASIS (2007), Web Services Reliable Messaging (WS-Reliable Messa

13、ging) Version 1.1. http:/docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.1-spec-cs-01.pdf 3 Definitions 3.1 Terms defined elsewhere None. 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: AHD Application Hostin

14、g Device ATS Abstract Test Suite ATNA Audit Trail and Node Authentication CDG Continua Design Guidelines CGM Continuous Glucose Monitor DUT Device Under Test EPR Endpoint Reference GUI Graphical User Interface HFS Health M BP-R9981; M BP-R1014; M BP-R1008; M BP-R1009; M BP-R1033; R BP-R1032; M Test

15、purpose Check that: An Envelope must conform to the structure specified in SOAP1.2 Section 5.1, “SOAP Envelope” AND an Envelope must have exactly zero or one child elements of the soap:Body element AND the children of the soap:body element in an Envelope must be namespace qualified AND An Envelope m

16、ust not contain a Document Type Declaration (DTD) or Processing Instructions AND an Envelope should not contain the namespace declaration xmlns:xml=”http/www.w3.org/XML/1998/namespace AND the soap:envelope, soap:header and soap:body elements must not have attributes in the namespace “http:/schemas.x

17、mlsoap.org/soap/envelope/” Applicability C_SEN_000 AND C_SEN_GEN_003 Other PICS Initial condition The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs. Test

18、procedure 1. The HFS sender under test sends the SOAP message to the HFS receiver. 2. Check that the captured message has the following structure: . Here are the children of soap:Envelope where soap:Header is optional and it is recommended that the namespace is not http:/www.w3.org/XML/1998/namespac

19、e. Pass/Fail criteria Check that: The message has, in this order, an envelope, an optional header and a body. The namespaces that appear in the soap message are qualified. Soap:envelope, soap:header and soap:body do not have attributes in the namespace “http:/schemas.xmlsoap.org/soap/envelope/“. The

20、re is no DTD or processing instructions in the envelope. The SOAP envelopes namespace is “http:/www.w3.org/2003/05/soap-envelope“ to 10 Rec. ITU-T H.830.1 (04/2017) support SOAP 1.2 b-SOAP 1.2. Notes BP-R2201 and BP-R2210 imply that there may be at most one child element of the soap:Body. The refere

21、nced errata, NE05, would not be allowed by Continua (not compliant with the WS-I Profile). TP Id TP/HFS/SEN/WSI/BP/BV-001 TP label SOAP encodingStyle Attribute Coverage Spec OASIS/WS-I BP Testable items BP-R1005; M BP-R1006; M BP-R1007; M Test purpose Check that: An Envelope must not contain soap:en

22、codingStyle attributes on any of the elements whose namespace name is “http:/schemas.xmlsoap.org/soap/envelope/” AND an Envelope must not contain soap:encodingStyle attributes on any element that is a child of soap:body. AND an Envelope described in an rpc-literal binding must not contain soap:encod

23、ingStyle attribute on any element that is a grandchild of soap:Body Applicability C_SEN_000 AND C_SEN_GEN_003 Other PICS Initial condition The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respect

24、ive service according to its needs. Test procedure 1. Make the HFS sender under test send a SOAP message. 2. Check within the captured message: a. If the soap:encodingStyle attribute is present, that the envelope contains: a namespace which is not “http:/schemas.xmlsoap.org/soap/envelope/“ an elemen

25、t that is not a child of soap:Body. If an rpc-literal binding is used, check that the element is not a grandchild of soap:body. Pass/Fail criteria If present, the soap:encodingStyle attribute is as specified within the test procedure above. Notes TP Id TP/HFS/SEN/WSI/BP/BV-002 TP label Use of SOAP i

26、n HTTP Coverage Spec OASIS/WS-I BP Testable items BP-R1132; M BP-R1140; M Test purpose Check that: A HTTP request message must use the HTTP POST method. AND A Message shall be sent using HTTP/1.1 Applicability C_SEN_000 AND C_SEN_GEN_003 Other PICS Initial condition The simulated HFS receiver has a

27、WebService enabled and the HFS sender under test is ready to send an HTTP request. Rec. ITU-T H.830.1 (04/2017) 11 Test procedure 1. Make the HFS sender under test send a message to the simulated HFS receiver using the HTTP protocol. 2. Check in the HTTP header of the captured message that: a. the H

28、TTP version is 1.1 b. POST method is used. Pass/Fail criteria Check that all values are as specified in the HTTP header. Notes TP Id TP/HFS/SEN/WSI/BP/BV-003 TP label HTTP Status Codes Coverage Spec OASIS/WS-I BP Testable items BP-R1131; O Test purpose Check that: A consumer may automatically redire

29、ct a request when it encounters a “307 Temporary Redirect” HTTP status code in a response Applicability C_SEN_000 AND C_SEN_GEN_003 Other PICS C_SEN_WSI_001 Initial condition The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has an HTTP re

30、quest ready to be sent to the respective service according to its needs. Test procedure 1. Make the HFS sender under test send an HTTP request to the HFS receiver. 2. The simulated HFS receiver responds with “307 Temporary Redirect“ as the status code. 3. If C_SEN_WSI_001=TRUE, the HFS sender redire

31、cts the request, or else the HFS sender does not redirect the request. Pass/Fail criteria If C_SEN_WSI_001=TRUE, the HFS sender redirects the request to the http address indicated in the “307 Temporary Redirect“ HTTP response. Notes TP Id TP/HFS/SEN/WSI/BP/BV-004 TP label Messages using wsdl descrip

32、tions Coverage Spec OASIS/WS-I BP Testable items BP-R2211; M BP-R2212; M BP-R2213; M BP-R2214; M Test purpose Check that: An Envelope described with an rpc-literal binding must not have the xsi:nil attribute with a value of “1” or “true” on the part accessors AND an Envelope must contain exactly one

33、 part accessor element for each of the wsdl:parts in the same wsdl:message that are referred to by its soapbind:body element(s) AND in a doc-literal description where the value of the parts attribute of soapbind:body is an empty string, the corresponding envelope must have no element content in the

34、soap:Body element AND in a rpc-literal description where the value of the parts attribute of soapbind:body is an empty string, the corresponding envelope must have no part accessor elements. 12 Rec. ITU-T H.830.1 (04/2017) Applicability C_SEN_000 AND C_SEN_GEN_003 Other PICS C_SEN_WSI_021 Initial co

35、ndition The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs. Test procedure 1. Wait until the HFS sender under test sends a SOAP message or, if necessary, f

36、orce it to send a SOAP message. 2. Take the WSDL description of the web service using its URL and check the soap envelope of the captured message: If an rpc-literal binding is used: a. If the soapbind:body element of the description is an empty string, there is no part accessor elements. b. If the s

37、oapbind:body element of the description is not empty, check that the part accessor of the envelope is present and that there is no xsi:nil attribute with a value of “1“ or “true“. If doc-literal binding is used: a. If the value of the parts attribute of soapbind:body is an empty string, the envelope

38、 does not have element content in soap:Body element. Pass/Fail criteria Check that the envelope is as specified in step 2. Notes TP Id TP/HFS/SEN/WSI/BP/BV-005 TP label Port Types Coverage Spec OASIS/WS-I BP Testable items BP-R2301; M Test purpose Check that: The order of the elements in the soap:Bo

39、dy of an envelope must be the same as that of the wsdl:parts in the wsdl:message that describes it for each of the wsdl:part elements bound to the envelopes corresponding soapbind:body element Applicability C_SEN_000 AND C_SEN_GEN_003 Other PICS C_SEN_WSI_021 Initial condition The simulated HFS rece

40、iver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs. Test procedure 1. Wait until the HFS sender under test sends a SOAP message or, if necessary, force it to send a SOAP message

41、. 2. Take the WSDL description of the web service using its URL and check the wsdl:parts elements in the wsdl:message. 3. Compare their order with the soap:Body elements order. Pass/Fail criteria In step 3, check that the order of the wsdl:parts are the same as the order of the elements in the soap:

42、Body. Notes TP Id TP/HFS/SEN/WSI/BP/BV-006 TP label SOAP Binding Coverage Spec OASIS/WS-I BP Testable items BP-R2742; O BP-R2743; O Rec. ITU-T H.830.1 (04/2017) 13 Test purpose Check that: An envelope may contain fault with a detail element that is not described by a soapbind:fault element in the co

43、rresponding WSDL description AND An envelope may contain the details of a header processing related fault in a SOAP header block that is not described by a soapbind:headerfault element in the corresponding WSDL description Applicability C_SEN_000 AND C_SEN_WSI_034 AND C_SEN_GEN_003 Other PICS C_SEN_

44、WSI_021 Initial condition The simulated HFS receiver has a WebService enabled with many different services and the HFS sender under test has a SOAP message ready to be sent to the respective service according to its needs. Test procedure 1. Wait until the HFS sender under test sends a SOAP message o

45、r, if necessary, force it to send a SOAP message. 2. The simulated HFS receiver responds with a message that will cause that HFS sender to generate a fault. 3. The HFS sender under test sends a fault message. 4. Check the envelopes fault detail element and the SOAP header blocks header processing fa

46、ult. Pass/Fail criteria In step 2, verify that the detail element cannot be described by the soapbind:fault element of the WSDL description, and that the header block cannot be described by a soapbind:headerfault element of the WSDL description. Notes TP Id TP/HFS/SEN/WSI/BP/BV-006_B TP label SOAP B

47、inding 2 Coverage Spec OASIS/WS-I BP Testable items BP-R2712; M BP-R2735; M BP-R2755; M BP-R2737; M BP-R2738; M BP-R2739; O BP-R2752; O BP-R2753; O Test purpose Check that: A document-literal binding must be serialized as an envelope with a soap:Body whose child element is an instance of the global

48、element declaration referenced by the corresponding wsdl:message part AND An envelope described with an rpc-literal binding must place the part accessor elements for parameters and return value in no namespace AND The part accessor elements in a message described with an rpc-literal binding must hav

49、e a local name of the same value as the name attribute of the corresponding wsdl:part element AND An envelope described with an rpc-literal binding must namespace qualify the descendants of part accessor elements for the parameters and the return value, as defined by the schema in which the part accessor types are defined AND An envelope must include all soapbind:headers specified on a wsdl:input or wsdl:output of a wsdl:operation of a wsdl:binding that describes it AND A