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

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

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.2 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 2: Web services interoperability: Health Part 2: Web Services Interoperability. HFS Receiver (Version 1.5, 2017-03-14), that was developed by the Personal Connected Health Alliance. A number of versi

3、ons 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 Editi

4、on Recommendation Approval Study Group Unique ID* 1.0 ITU-T H.832 2015-01-13 16 11.1002/1000/12250 1.0 ITU-T H.830.2 2015-01-13 16 11.1002/1000/12588 2.0 ITU-T H.830.2 2016-07-14 16 11.1002/1000/12922 3.0 ITU-T H.830.2 2017-04-13 16 11.1002/1000/13202 Keywords Conformance testing, Continua Design Gu

5、idelines, e-health, Health Part 2: Web Services Interoperability. HFS Receiver (Version 1.5, 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. Ve

6、rsion Date 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

7、 the 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

8、 health 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 (PI

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

10、ad certified 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 p

11、ersonal 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 B

12、P OASIS/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 M

13、essaging) 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 Ho

14、sting Device ATNA Audit Trail and Node Authentication ATS Abstract Test Suite CDG Continua Design Guidelines CGM Continuous Glucose Monitor DUT Device Under Test GUI Graphical User Interface HFS Health M Test purpose Check that: An HFS receiver must generate a fault if they encounter an envelope who

15、se document element is not soap:Envelope Applicability C_REC_000 AND C_REC_GEN_003 Other PICS Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message b-SOAP 1.2 whose document element is not a soap:Envelope, ready to be sent Test procedu

16、re 1. The simulated HFS sender sends the SOAP message. 2. The HFS receiver generates a fault. Pass/Fail criteria Check that the HFS receiver generates a fault and does not discard the message. Notes TP Id TP/HFS/REC/WSI/BP/BV-000 TP label SOAP Envelopes Structure Coverage Spec OASIS/WS-I BP Testable

17、 items BP-R9980; M BP-R9981; M BP-R1014; M BP-R1008; M BP-R1009; M BP-R1033; R BP-R1017; M BP-R1032; M Test 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 el

18、ement AND the children of the soap:body element in an Envelope must be namespace qualified AND an Envelope must not contain a Document Type Declaration (DTD) nor Processing Instructions AND an Envelope should not contain the namespace declaration xmlns:xml=”http/www.w3.org/XML/1998/namespace AND An

19、HFS receiver must not mandate the use of the xsi:type attribute in envelopes except as required in order to indicate a derived type AND the soap:envelope, soap:header and soap:body elements in an Envelope must not have attributes in the namespace “http:/schemas.xmlsoap.org/soap/envelope/” Applicabil

20、ity C_REC_000 AND C_REC_GEN_003 Other PICS 10 Rec. ITU-T H.830.2 (04/2017) Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message ready to be sent. Test procedure 1. The simulated HFS sender sends a SOAP message to the HFS receiver unde

21、r test. 2. The HFS receiver responds with another SOAP message. Check that the captured message has the following structure . The children of the soap:envelope are here where soap:Header is optional and it is recommended that the namespace is not “http:/www.w3.org/XML/1998/namespace“. Pass/Fail crit

22、eria Check that: the message contains, in this order, an envelope, an optional header and a body. each namespace that appears in the soap message is qualified. the soap:envelope, soap:header and soap:body do not have attributes in the namespace “http:/schemas.xmlsoap.org/soap/envelope/“. there is no

23、 DTD or processing instructions in the envelope. an xsi:type is used only if a derived type is indicated (see b-XML Schema Part 1, clause 2.6.1) the namespace is “http:/www.w3.org/2003/05/soap-envelope“ to support SOAP 1.2. Notes BP-R2201 and BP-R2210 imply that there may be at most one child elemen

24、t of the soap:Body. The referenced errata, NE05, would not be allowed by Continua (as it is not compliant with the WS-I Basic Profile). TP Id TP/HFS/REC/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 Che

25、ck that: An Envelope must not contain soap:encodingStyle 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 rp

26、c-literal binding must not contain soap:encodingStyle attribute on any element that is a grandchild of soap:Body Applicability C_REC_000 AND C_REC_GEN_003 Other PICS C_REC_WSI_003 Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message,

27、with a correct soap:encodingStyle attribute in one of the elements, ready to be sent. Rec. ITU-T H.830.2 (04/2017) 11 Test procedure 1. The simulated HFS sender sends the SOAP message. 2. The HFS receiver responds with another SOAP message: a. If a soap:encodingStyle attribute is present in any elem

28、ent: Namespace is not “http:/schemas.xmlsoap.org/soap/envelope/“ The element is not a child of soap:Body If PICS C_REC_WSI_003 is declared, the element is not a grandchild of soap:body Pass/Fail criteria In step 2, if the soap:encodingStyle attribute is present, it is as specified. Notes TP Id TP/HF

29、S/REC/WSI/BP/BV-002 TP label Use of SOAP in HTTP Coverage Spec OASIS/WS-I BP Testable items BP-R1127; M BP-R1140; M CommonReq1; M Test purpose Check that: An HFS receiver must not rely on the value of the SOAPAction HTTP header to correctly process the message. AND A Message shall be sent using HTTP

30、/1.1 Applicability C_REC_000 AND C_REC_GEN_003 Other PICS Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS sender has a SOAP message ready to be sent that contains a SOAPAction field not quoted in its HTTP header. Test procedure 1. The simulated HFS sender

31、 sends a message using HTTP/1.1 with a SOAPAction HTTP Header field not quoted without using security. 2. The HFS receiver processes the message (it responds with the fault wsse:InvalidSecurity). Pass/Fail criteria Check that in step 2 the message has been processed. Notes TP Id TP/HFS/REC/WSI/BP/BV

32、-003 TP label HTTP Status Codes Coverage Spec OASIS/WS-I BP Testable items BP-R1124; M BP-R1111; R BP-R1112; R BP-R1125; M BP-R1113; R BP-R1114; R BP-R1115; R Test purpose Check that: An instance must use a 2xx HTTP status code on a response message that indicates the successful outcome of a HTTP re

33、quest AND An instance should use a “200 OK“ HTTP status code on a response message that contains an envelope that is not a fault AND An Instance should use either a “200 OK“ or “202 Accepted“ HTTP status code for a response message that does not contain a SOAP envelope but indicates the successful 1

34、2 Rec. ITU-T H.830.2 (04/2017) outcome of a HTTP request AND An instance must use a 4xx HTTP status code for a response that indicates a problem with the format of a request AND An instance should use a “400 Bad Request“ HTTP status code, if a HTTP request message is malformed AND An instance should

35、 use a “405 Method not Allowed“ HTTP status code if a HTTP request messages method is not “POST“. AND An instance should use a “415 Unsupported Media Type“ HTTP status code if a HTTP request messages Content-Type header field-value is not permitted by its WSDL description Applicability C_REC_000 AND

36、 C_REC_GEN_003 Other PICS Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send a HTTP request with an envelope permitted by the SUT Test procedure 1. The simulated HFS sender sends a HTTP request to the HFS receiver under test with an e

37、nvelope permitted by the SUT. 2. The HFS receiver responds with “2xx“ as status code, which is recommended to be: “200 OK“ if the response contains an envelope that is not a fault; and “200 OK“ or “202 Accepted“ if the response does not contain a SOAP envelope but indicates the successful outcome of

38、 the HTTP Request. 3. The simulated HFS sender sends a HTTP request with a malformed message. 4. The HFS receiver responds with “4xx“ as status code. It is recommended to be “400 Bad Request“. 5. The simulated HFS sender sends a HTTP request with a method that is not “POST“ 6. The HFS receiver respo

39、nds with “4xx“ as status code. It is recommended to be “405 Method not Allowed“. 7. The simulated HFS sender sends a HTTP request with a Content-Type header field not permitted by the HFS receivers WSDL description. 8. The HFS receiver responds with “4xx“ as status code. It is recommended to be “415

40、 Unsupported Media Type“. Pass/Fail criteria Check that status codes are as specified. Notes TP Id TP/HFS/REC/WSI/BP/BV-004 TP label Messages using WSDL descriptions 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 descri

41、bed 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 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

42、-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 soap:Body element Rec. ITU-T H.830.2 (04/2017) 13 AND in a rpc-literal description where the value of the parts attribute of soapbind:body i

43、s an empty string, the corresponding envelope must have no part accessor elements. Applicability C_REC_000 AND (C_REC_WSI_003 OR C_REC_WSI_004) AND C_REC_GEN_003 Other PICS Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS sender is ready to send any SOAP m

44、essage. Test procedure 1. The simulated HFS sender sends a SOAP message. 2. The HFS receiver under test responds with another SOAP message. 3. Look into the WSDL of the service and check in the captured message that: If C_REC_WSI_003: a. If the value of the parts attribute of the soapbind:body eleme

45、nt of the description is an empty string, there is no part accessor element. b. If the value of the parts attribute of the soapbind:body element of the description is not empty, check that the part accessor of the envelope is present and that the value of the xsi:nil attribute, if it is present, is

46、not “1“ or “true“. If C_REC_WSI_004: a. If the value of the parts attribute of the soapbind:body is an empty string, the envelope does not have element content in the soap:Body element. Pass/Fail criteria Check that the envelope is as specified in step 3. Notes TP Id TP/HFS/REC/WSI/BP/BV-005 TP labe

47、l 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:Body 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 correspond

48、ing soapbind:body element Applicability C_REC_000 AND C_REC_GEN_003 Other PICS Initial condition The HFS receiver under test has a WebService enabled and the simulated HFS Sender is ready to send any SOAP message. Test procedure 1. The simulated HFS Sender sends a SOAP message to the HFS receiver un

49、der test. 2. The HFS receiver under test responds with a SOAP message. 3. Check the wsdl:parts elements in the wsdl:message of the WSDL of the HFS receiver under test. 4. Compare them with the soap:Body elements. Pass/Fail criteria In step 4, check that the order of the wsdl:parts are the same as the order of the elements in the soap:Body Notes TP Id TP/HFS/REC/WSI/BP/BV-006 TP label SOAP Binding Coverage Spec OASIS/WS-I BP Testable BP-R2742; O BP-R2743; O 14 Rec. I