1、 ETSI TS 102 440 V1.1.1 (2005-08)Technical Specification WS-Session;Web Services for Application Session ServicesETSI ETSI TS 102 440 V1.1.1 (2005-08) 2 Reference DTS/ECMA-00344 Keywords CSTA, SDSL, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 F
2、ax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than
3、 one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network
4、drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the prese
5、nt document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. Europe
6、an Telecommunications Standards Institute 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark
7、 of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 3 Contents Intellectual Property Rights4 Foreword.4 Brief history4 1 Scope 5 2 Conformance 5 3 References 5 4 Definitions5 4.1 Namespaces6 5 Service Provider WSDL Abstrac
8、t Definitions .6 6 Service Provider WSDL SOAP Binding7 Annex A (informative): Service WSDL with SOAP/HTTP Binding9 Annex B (informative): SOAP XML Templates for ECMA-354 Messages 10 B.1 StartApplicationSession request message template10 B.1.1 StartApplicationSession Positive response message templat
9、e10 B.1.2 StartApplicationSession negative response message template.10 B.2 StopApplicationSession request message template10 B.2.1 StopApplicationSession positive response message template 10 B.2.2 StopApplicationSession negative response message template .11 B.3 ResetApplicationSessionTimer reques
10、t message template.11 B.3.1 ResetApplicationSessionTimer positive response message template.11 B.3.2 Reset Application Session Timer negative response message template.11 B.3.3 ApplicationSessionTerminated.11 Annex C (informative): WS-Session Events.12 C.1 Event Sink of Application Session Terminate
11、d Service.12 C.2 Event Sink WSDL Specification12 C.2.1 Generic Event Sink Interface for WS-Session13 C.2.2 Typed Event Sink Interface for WS-Session13 C.3 Event Subscription SOAP Messages14 C.3.1 SOAP Message for ApplicationSessionTerminated Event Subscription14 C.4 WS-Session Event SOAP XML message
12、 templates 14 C.4.1 ApplicationSessionTerminated Event Subscription SOAP message template .14 C.4.2 Template of positive response to the event subscription 15 C.4.3 Template of negative response (fault) to event subscription 15 C.4.4 Template of Unsubscribe message .16 C.4.5 Template of positive res
13、ponse to Unsubscribe message.16 C.4.6 Template of ApplicationSessionTerminated event notification to typed event sink 16 C.4.7 Template of ApplicationSessionTerminated event notification to generic event sink .17 C.5 WS-Session Event supporting documents17 History 18 ETSI ETSI TS 102 440 V1.1.1 (200
14、5-08) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual
15、Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation,
16、 including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (
17、TS) has been produced by ECMA on behalf of its members and those of the European Telecommunications Standards Institute (ETSI). Brief history ECMA-354 1, Application Session Services, specifies XML protocols that can be used to create and manage application sessions that are independent of the trans
18、port layer protocols. The present document (WS-Session) specifies Web services for ECMA-354 1. The present document has been adopted by the General Assembly of June 2005. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 5 1 Scope The present document specifies Web Services (in WSDL) and a SOAP binding for the
19、Application Session Services defined in ECMA-354 1. The Application Session Services allow Applications to create and maintain a relationship with Servers termed Application Session. The Web services specified herein, allow Service Subscribers (Applications in ECMA-354 1) and Service Providers (Serv
20、ers in ECMA-354 1) to create and maintain such Application Sessions. The present document builds upon and imports the XML schema definitions from ECMA-354 1. Although the present document only specifies the abstract WSDL definitions and its SOAP binding, annex A shows an example WSDL binding with SO
21、AP/HTTP. Annex B lists SOAP XML Templates for ECMA-354 1 Messages. Annex C illustrates how WS-Eventing can be used to establish event channels to receive ApplicationSessionTerminated messages. 2 Conformance Conforming implementations support the port type and the WSDL to SOAP binding as specified in
22、 the present document. To support the port type, conforming implementations support all operations in the port type. For each operation, conforming implementations also satisfy all the requirements that ECMA-354 1 specifies for the corresponding service definition. 3 References 1 ECMA-354: “Applicat
23、ion Session Services, June 2004“. NOTE: See http:/www.ecma-international.org/publications/standards/Ecma-354.htm. 2 SOAP 1.1: “Simple Object Access Protocol 1.1, W3C Note 08 May 2000 “. 3 WSDL 1.1: “ Web Service Description Language 1.1, W3C Note 15 March 2001“. 4 XML Schema 1.0: “XML Schema Languag
24、e Part 1: Structure, W3C Recommendation 28 October 2004“. 5 XML Schema 1.0: “ XML Schema Language Part 2: Data Types, W3C Recommendation 28 October 2004“. 4 Definitions Consult ECMA-354 1 for Application Session Services specific terms. The present document refers to these two main Web services conc
25、epts: 1) Service Subscriber - provides the following major functions: 1) queries a Service Provider for services, and 2) binds and interacts with a Service Provider. 2) Service Provider - provides the following major functions: 1) publishes its services (e.g. WSDL document), and 2) interacts with a
26、Service Subscriber. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 6 4.1 Namespaces The present document uses these two Ecma namespaces: 1) aps: http:/www.ecma-international.org/standards/ecma-354/appl_session: This Standard imports all XML messages defined in ECMA-354 from the aps namespace. 2) tns: http:/w
27、ww.ecma-international.org/standards/ecma-366/ws-session: The target namespace for this Standard. The present document refers to these other namespaces: 1) http:/schemas.xmlsoap.org/wsdl/: This contains the W3C WSDL 1.1 schema. 2) http:/www.w3.org/2001/XMLSchema: This contains the W3C XML Schema defi
28、nition. 3) http:/schemas.xmlsoap.org/wsdl/soap: This contains the W3C SOAP bindings for WSDL 1.1. 5 Service Provider WSDL Abstract Definitions This clause specifies the abstract WSDL definitions to support the services specified in ECMA-354 1. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 7 6 Service Provid
29、er WSDL SOAP Binding This clause specifies the binding of the abstract WSDL definitions in clause 5 with SOAP Messages. ECMA-354 1 requires Applications to include the aps:sessionID in some service requests, in these cases, the corresponding Service Subscribers shall include the aps:sessionID as a h
30、eader block in the application SOAP message. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 8 ETSI ETSI TS 102 440 V1.1.1 (2005-08) 9 Annex A (informative): Service WSDL with SOAP/HTTP Binding This annex provides an example WSDL binding with SOAP/HTTP. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 10Annex B (informa
31、tive): SOAP XML Templates for ECMA-354 Messages B.1 StartApplicationSession request message template aps:StartApplicationSession B.1.1 StartApplicationSession Positive response message template aps:StartApplicationSessionPosResponse B.1.2 StartApplicationSession negative response message template ap
32、s:StartApplicationSessionNegResponse B.2 StopApplicationSession request message template aps:StopApplicationSession B.2.1 StopApplicationSession positive response message template aps:StopApplicationSessionPosResponse ETSI ETSI TS 102 440 V1.1.1 (2005-08) 11B.2.2 StopApplicationSession negative resp
33、onse message template aps:StopApplicationSessionNegResponse B.3 ResetApplicationSessionTimer request message template aps:ResetApplicationSessionTimer B.3.1 ResetApplicationSessionTimer positive response message template aps:ResetApplicationSessionTimerPosResponse B.3.2 Reset Application Session Tim
34、er negative response message template aps:ResetApplicationSessionTimerNegResponse B.3.3 ApplicationSessionTerminated ApplicationSessionTerminated operation is discussed in annex C. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 12Annex C (informative): WS-Session Events C.1 Event Sink of Application Session
35、Terminated Service The ApplicationSessionTerminated operation defines an outbound asynchronous event notification. The Service Subscriber should subscribe to receive the ApplicationSessionTerminated event from the Service Provider according to WS-Eventing WS-Eventing. It should provide to the Servic
36、e Provider the URI of the event sink, so that it can receive the event notification. The Service Subscriber should subscribe to receive the ApplicationSessionTerminated event immediately after the successful completion of the StartApplicationSession operation. The subscription message must include t
37、he mandatory elements of WS-Addressing (i.e. , , and ) and the unique aps:sessionID obtained from the StartApplicationSession operation. Message header processing should follow the conformance requirement of WS-Addressing, e.g. the in the Service Subscriber subscription message should be copied back
38、 in the field of the response message from the Service Provider. The aps:sessionID element should be the first level child element of the subscription endpoint reference parameters WS-Addressing. The subscription message from the Service Subscriber must provide at least one event sink endpoint refer
39、ence WS-Addressing to the Service Provider. The Service Provider should use the push delivery mode to deliver the event notification. The Service Provider should send event notification to each of the event sink endpoint declared in the event subscription message. The Service Provider shall copy the
40、 endpoint reference from the Service Subscriber to the header block of the notification. The event notification message from the Service Provider should include the sink endpoint reference parameters, so that the Service Subscriber can correlate the event notification obtained from the Service Provi
41、der with the corresponding session and event operation. If the application session abnormally terminated, before the ApplicationSessionTerminated event can be subscribed, the subsequent subscription of ApplicationSessionTerminated event by the Service Subscriber will result in a SOAP faultstring inv
42、alidSessionID and the faultcode is wse:EventSouceUnableToProcess. The Service Provider should only send the notifications for valid event subscriptions. When a session terminates, any subscription associated with the session is deemed invalid. C.2 Event Sink WSDL Specification The event sink interfa
43、ce specified by the Service Subscriber in the event subscription message should provide a one-way Web service event notification operation to receive the notification of ApplicationSessionTerminated event from the Service Provider. The generic event sink described in this annex should be the default
44、 event sink, and the additional typed event sink described in this annex is optional. But if it has a typed event sink, Service Subscriber should declare it in the ApplicationSessionTerminated event subscription message to the Service Provider; and the Service Provider should send the notification o
45、f ApplicationSessionTerminated event to the typed event sink of the Service Subscriber. In this case, the generic event sink should still be used as the default event sink for other event notifications within the session. ETSI ETSI TS 102 440 V1.1.1 (2005-08) 13C.2.1 Generic Event Sink Interface for
46、 WS-Session The generic event sink described in this annex can be used as a default event sink for all subscriptions within the session. The WSDL specification below contains a generic event notification operation NotifyEvent in the event sink. C.2.2 Typed Event Sink Interface for WS-Session The Ser
47、vice Subscriber can declare an additional typed event sink interface. It contains a typed operation derived from the Service Providers WSDL which is a “reversal“ of the outbound operation of ApplicationSessionTerminated event operation of the Service Provider. The WSDL for the typed event sink inter
48、face of WS-Session is specified as follows: ETSI ETSI TS 102 440 V1.1.1 (2005-08) 14C.3 Event Subscription SOAP Messages C.3.1 SOAP Message for ApplicationSessionTerminated Event Subscription The event subscription message from the Service Subscriber for ApplicationSessionTerminated Service contains
49、 the unique aps:sessionID element obtained from the StartApplicationSession operation. The unique aps:sessionID is bound to the SOAP message as a header block. The Service Subscriber should declare the event sink type (i.e. generic or typed+generic) using WS-Addressing Endpoint Reference. The event subscription message should include mandatory aps:sessionID element in the SOAP header, and other mandatory elements of WS-Addressing. The XML Schema definition of the event sink type elements (generic or typed+generic) of the sink interfac
