ISO IEC 25437-2012 Information technology - Telecommunications and information exchange between systems - WS-Session - Web services for application session serv.pdf

1、 Reference number ISO/IEC 25437:2012(E) ISO/IEC 2012INTERNATIONAL STANDARD ISO/IEC 25437 Third edition 2012-11-15 Information technology Telecommunications and information exchange between systems WS- Session Web services for application session services Technologies de linformation Tlcommunications

2、 et change dinformation entre systmes Session WS Services web pour services de session dapplication ISO/IEC 25437:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,

3、electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyright

4、iso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2012 All rights reservedISO/IEC 25437:2012(E) ISO/IEC 2012 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Scope 1 2 Conformance . 1 3 Normative references 1 4 Terms, definitions and namespaces . 2 4.1 Terms and definiti

5、ons . 2 4.2 Prefixes and namespaces 2 5 Abstract WSDL Definitions . 3 5.1 Provider WSDL 3 5.2 Notification WSDL . 4 6 SOAP Binding 4 6.1 SOAP Binding for Provider WSDL . 5 6.2 SOAP Binding for Notification WSDL 5 6.3 SOAP Binding of sessionID 5 6.4 SOAP Fault Messages . 6 7 Event Subscription and No

6、tification . 7 Annex A (normative) Event Subscription Using WS-Eventing 8 A.1 General . 8 A.2 Subscription Fault . 8 Annex B (normative) Subscription Using WS-BaseNotification Option . 9 B.1 General . 9 B.2 Subscription Fault . 9 Annex C (normative) Asynchronous Response to Subscription Request Opti

7、on . 10 Annex D (informative) Example WS-Session WSDL binding with SOAP/HTTP . 11 D.1 Service Provider WSDL with SOAP/HTTP Binding 11 D.2 Notification WSDL with SOAP/HTTP Binding . 12 Annex E (informative) SOAP XML Templates for ISO/IEC 22534 (ECMA-354) Messages . 13 E.1 StartApplicationSession requ

8、est message template 13 E.1.1 StartApplicationSession Positive response message template 13 E.1.2 StartApplicationSession negative response message template 13 E.2 StopApplicationSession request message template . 14 E.2.1 StopApplicationSession positive response message template . 14 E.2.2 StopAppl

9、icationSession negative response message template 14 E.3 ResetApplicationSessionTimer request message template . 14 E.3.1 ResetApplicationSessionTimer positive response message template . 15 E.3.2 Reset Application Session Timer negative response message template . 15 E.4 ApplicationSessionTerminate

10、d 15 E.4.1 Template of ApplicationSessionTerminated event notification for unwrapped event sink which applies to both WS-Eventing and WS-BaseNotification options 15 E.4.2 Template of ApplicationSessionTerminated event notification to wrapped event sink of WS-Eventing 16 E.4.3 Template of Application

11、SessionTerminated event notification to wrapped event sink of WS-BaseNotification . 16 ISO/IEC 25437:2012(E) iv ISO/IEC 2012 All rights reservedAnnex F (informative) WS-Eventing SOAP XML Message Templates .17 F.1 ApplicationSessionTerminated Event Subscription SOAP message template 17 F.2 Template o

12、f positive response to the event subscription .17 F.3 Template of negative response (fault) to event subscription .18 F.4 Template of Unsubscribe message .18 F.5 Template of positive response to Unsubscribe message .18 Annex G (informative) WS-BaseNotification SOAP XML Message Templates .19 G.1 Appl

13、icationSessionTerminated Event Subscription SOAP message template 19 G.2 Template of positive response to the event subscription .19 G.3 Template of negative response to the event subscription 20 G.4 Template of Unsubscribe message .20 G.5 Template of positive response to Unsubscribe message .21 Ann

14、ex H (informative) Summary of Changes .22 ISO/IEC 25437:2012(E) ISO/IEC 2012 All rights reserved vForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that

15、are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other internati

16、onal organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in t

17、he ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare International Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at l

18、east 75 % of the national bodies casting a vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights. ISO/IEC 25437 was prepared by Ecma Internati

19、onal (as ECMA-366) and was adopted, under a special “fast- track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information exchange between systems, in parallel with its approval by national bodies of ISO and IEC. This third

20、 edition cancels and replaces the second edition (ISO/IEC 25437:2009), which has been technically revised. ISO/IEC 25437:2012(E) vi ISO/IEC 2012 All rights reservedIntroduction ISO/IEC 22534, Application Session Services, specifies XML protocols that can be used to create and manage application sess

21、ions that are independent of the transport layer protocols. This International Standard (WS-Session) specifies Web services for ISO/IEC 22534. For Service Requester to receive the event notification from the Service Provider and from web services (e.g. ECMA-348) that use this International Standard

22、for session management, this International Standard introduces WS-Eventing as the mandatory mechanism and WS-BaseNotification as an Option to manage the event channel. This International Standard uses the approach in A.2 of WS-Eventing to specify the ApplicationSessionTerminated as an operation in t

23、he Notification WSDL. Since WS-Eventing has advanced to a W3C Proposed Recommendation at W3C, the 3 rdedition of this International Standard incorporates and complies with the latest edition of WS-Eventing. Heeding the guidance in the WS-I Profiles that WS-Eventing adopted, this Standard only uses a

24、 subset of WSDL Services, in particular, this Standard does not use the WSDL 1.1 Notification and Solicit- response operations. INTERNATIONAL STANDARD ISO/IEC 25437:2012(E) ISO/IEC 2012 All rights reserved 1Information technology Telecommunications and information exchange between systems WS-Session

25、 Web services for application session services 1 Scope This International Standard specifies Web Services (in WSDL, in Clause 5) and SOAP bindings (in Clause 6) for the Application Session Services defined in ISO/IEC 22534. The Application Session Services allow Applications to create and maintain a

26、 relationship with Servers termed Application Session. The Web services specified herein, allow Service Requesters (Applications in ISO/IEC 22534) and Service Providers (Servers in ISO/IEC 22534) to create and maintain such Application Sessions. This International Standard builds upon and imports th

27、e XML schema definitions from ISO/IEC 22534. The method of making the WSDL description of the specified services available to Service Provider and Requester is out of the scope of this International Standard. The Notification WSDL specifies the ApplicationSessionTerminated operation. The operation s

28、pecifies one input message for the event notification that Service Requesters receive from the Service Provider. Service Requesters may also receive the event notifications from web services, e.g. ECMA-348, that use this International Standard for session management. 2 Conformance The Service Reques

29、ter and Service Provider conform to the Application and Server conformance specified in ISO/IEC 22534, using the WSDL definitions, SOAP bindings, and event subscription and notification specified in Clause 5, 6 and 7 respectively. The Service Provider implements and publishes the operations in the P

30、rovider WSDL in 5.1 and the Notification WSDL in 5.2. The Service Provider implements and publishes the required operations from Annex A and it may additionally implement and publish operations from Annex B. The Service Requester implements the operation in the Notification WSDL in 5.2. The Service

31、Provider supports synchronous responses to Event Subscriptions and may also implement the asynchronous response Option specified in Annex C. 3 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited

32、applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 22534:2005 (ECMA-354), Information technology Telecommunications and information exchange between systems Application session services SOAP 1.1 Simple Object Access Protocol 1.1

33、, W3C Note 08 May 2000 ISO/IEC 25437:2012(E) 2 ISO/IEC 2012 All rights reservedWSDL 1.1 Web Service Description Language 1.1, W3C Note 15 March 2001 XML Schema 1.0: XML Schema Language Part 1: Structure, W3C Recommendation 28 October 2004 XML Schema Language Part 2: Data Types, W3C Recommendation 28

34、 October 2004 WS-Addressing 1.0 Web Services Addressing 1.0 Core W3C Recommendation (ISO/IEC 40240:2011) Web Services Addressing 1.0 - SOAP Binding W3C Recommendation (ISO/IEC 40250:2011) Web Services Addressing 1.0 Metadata, W3C (ISO/IEC 40260:2011) Web Services Eventing (WS-Eventing), W3C Recommen

35、dation 13 December 2011, http:/www.w3.org/TR/ws- eventing/ WS-BaseNotification 1.3 Web Services Base Notification 1.3 (WS-BaseNotification) OASIS Standard, 1 October 2006 4 Terms, definitions and namespaces 4.1 Terms and definitions For the purposes of this document, the terms and definitions given

36、in ISO/IEC 22534 and the following apply. 4.1.1 Service Requester Web Service equivalent of Application in ISO/IEC 22534 4.1.2 Service Provider Web Service equivalent of Server in ISO/IEC 22534 4.2 Prefixes and namespaces This International Standard uses the following Ecma prefixes and namespaces. 1

37、. aps (http:/www.ecma-international.org/standards/ecma-354/appl_session): This International Standard imports all XML messages defined in ISO/IEC 22534 from the aps namespace. 2. wss (http:/www.ecma-international.org/standards/ecma-366/ws-session/ed3): The WSDL target namespace for this Internationa

38、l Standard. This International Standard refers to these other prefixes and namespaces. 1. wsdl (http:/schemas.xmlsoap.org/wsdl/): This contains the W3C WSDL 1.1 schema. 2. xs (http:/www.w3.org/2001/XMLSchema): This contains the W3C XML Schema definition. 3. S (http:/schemas.xmlsoap.org/wsdl/soap): T

39、his contains the W3C SOAP 1.1 bindings for WSDL 1.1. 4. wsa (http:/www.w3.org/2005/08/addressing): The namespace for WS-Addressing 1.0. 5. wse (http:/www.w3.org/2011/03/ws-evt): The target namespace for WS-Eventing. 6. wsnt (http:/docs.oasis-open.org/wsn/b-2): The target namespace for WS-BaseNotfica

40、tion 1.3. ISO/IEC 25437:2012(E) ISO/IEC 2012 All rights reserved 35 Abstract WSDL Definitions This Clause specifies the abstract WSDL definitions to support the services specified in ISO/IEC 22534. There are two abstract WSDL definitions and both of them are specified by the Service Provider: 1) “Pr

41、ovider WSDL” that specifies the interface the Service Provider shall implement; 2) “Notification WSDL” that specifies the interface the Service Requester shall implement in order to receive the event in a particular format using Annex A and the Option in Annex B. 5.1 Provider WSDL ISO/IEC 25437:2012

42、(E) 4 ISO/IEC 2012 All rights reserved5.2 Notification WSDL 6 SOAP Binding This Clause specifies the binding templates of the abstract WSDL definitions in Clause 5 with SOAP Messages without a specific transport protocol. Any SOAP binding to transport shall contain elements and attributes in this bi

43、nding template. ISO/IEC 25437:2012(E) ISO/IEC 2012 All rights reserved 56.1 SOAP Binding for Provider WSDL 6.2 SOAP Binding for Notification WSDL 6.3 SOAP Binding of sessionID The aps:sessionID element shall be included as a direct child element of the SOAP header for each application SOAP message,

44、such as event notification message, exchanged over the application session. The recipient (Service Provider or Requester) of the application message shall verify that the sessionID is valid; otherwise it shall ignore the message or send a fault. ISO/IEC 25437:2012(E) 6 ISO/IEC 2012 All rights reserv

45、ed6.4 SOAP Fault Messages The negative responses from Service Providers shall be bound to the SOAP 1.1 fault properties: faultcode, faultstring and detail, using the following template. faultcode faultstring detail The contents of fault properties are defined by the following table for each type of

46、negative response. Table 1 Fault names and properties for WS-Session services Fault Name StartFault faultcode ISO/IEC 22534 defined standard error names: invalidApplicationInfo, requestedProtocolVersionNotSupported, serverResourcesBusy, maxNumberSessions, or application error name. faultstring For I

47、SO/IEC 22534 standard errors, it is the Description of corresponding error in Table 4-3 of ISO/IEC 22534. Additonal text can be provided to elaborate the error message, for example, the maximal session number allowed by the service provider. For application errors, a proper English description shall

48、 be provided. detail Element aps:StartApplicationSessionNegResponse. Fault Name StopFault faultcode ISO/IEC 22534 defined standard error names: invalidSessionID, or application error name. faultstring For ISO/IEC 22534 standard errors, it is the Description of corresponding error in Table 4-6 of ISO

49、/IEC 22534. Additonal text can be provided to elaborate the error message, for example, the valid session ID format allowed by the service provider. For application errors, a proper English description shall be provided. detail Element aps:StopApplicationSessionNegResponse. Fault Name ResetFault faultcode ISO/IEC 22534 defined standard error names: invalidSessionID, serverCannotResetSessionDuration, or application error name. faultstring For ISO/IEC 22534 standard errors, it is the Description o