Information technology — Telecommunications and information exchange between systems — WS-Session — Web services for application session services

ISO/IEC 25437:2009 specifies Web Services (in WSDL) and a SOAP binding for the Application Session Services defined in ISO/IEC 22534. The Application Session Services allow Applications to create and maintain a 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. It builds upon and imports the 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 ISO/IEC 25437:2009. The ApplicationSessionTerminated operation of ISO/IEC 25437:2009 is an outbound asynchronous event notification that Service Requesters receive from the Service Provider. Service Requester may also receive the event notification from web services, e.g. ECMA-348, that use ISO/IEC 25437:2009 for session management. ISO/IEC 25437:2009 specifies the event subscription and notification behaviors supported by the two defined Options. Additionally it specifies the event subscription mechanism using WS-Eventing, specifies the event subscription mechanism using WS-BaseNotification, specifies the asynchronous subscription response Option for the two event subscription mechanisms, shows an example WS-Session WSDL binding with SOAP/HTTP, lists SOAP XML Templates for ISO/IEC 22534 messages, lists some SOAP XML Templates for WS-Eventing messages, lists some SOAP XML Templates for WS-BaseNotification messages, and provides a summary of changes from the previous edition (ISO/IEC 24537:2006).

Technologies de l'information — Télécommunications et échange d'information entre systèmes — Session WS — Services web pour services de session d'application

General Information

Status
Withdrawn
Publication Date
29-Jul-2009
Withdrawal Date
29-Jul-2009
Current Stage
9599 - Withdrawal of International Standard
Start Date
16-Nov-2012
Completion Date
16-Nov-2012
Ref Project

RELATIONS

Buy Standard

Standard
ISO/IEC 25437:2009 - Information technology -- Telecommunications and information exchange between systems -- WS-Session -- Web services for application session services
English language
26 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

INTERNATIONAL ISO/IEC
STANDARD 25437
Second edition
2009-08-15
Information technology —
Telecommunications and information
exchange between systems —
WS-Session — Web services for
application session services
Technologies de l'information — Télécommunications et échange
d'information entre systèmes — Session WS — Services web pour
services de session d'application
Reference number
ISO/IEC 25437:2009(E)
ISO/IEC 2009
---------------------- Page: 1 ----------------------
ISO/IEC 25437:2009(E)
PDF disclaimer

This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but

shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In

downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat

accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.

Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation

parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In

the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2009

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,

electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or

ISO's 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@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2009 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 25437:2009(E)
Contents Page

Foreword ............................................................................................................................................................iv

Introduction.........................................................................................................................................................v

1 Scope......................................................................................................................................................1

2 Conformance .........................................................................................................................................1

3 Normative references............................................................................................................................2

4 Terms, definitions and namespaces ...................................................................................................2

5 Service Provider WSDL Abstract Definitions .....................................................................................4

6 Service Provider WSDL SOAP Binding...............................................................................................6

7 Event Subscription and Notification ...................................................................................................8

Annex A (normative) Subscription Using WS-BaseNotification Option ......................................................9

Annex B (normative) Asynchronous Response to Subscription Request Option....................................10

Annex C (informative) Event Subscription Using WS-Eventing...................................................................11

Annex D (informative) Service Provider WSDL with SOAP/HTTP Binding ................................................14

Annex E (informative) SOAP XML Templates for ISO/IEC 22534 (ECMA-354) Messages..........................15

Annex F (informative) WS-Eventing SOAP XML Message Templates.........................................................20

Annex G (informative) WS-BaseNotification SOAP XML Message Templates ...........................................23

Annex H (informative) Summary of Changes.................................................................................................26

© ISO/IEC 2009 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 25437:2009(E)
Foreword

ISO (the International Organization for Standardization) and IEC (the International Electrotechnical

Commission) form the specialized system for worldwide standardization. National bodies that 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 international 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 the 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 least 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 International (as ECMA-366) and was adopted, under a special “fast-

track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, in parallel with its

approval by national bodies of ISO and IEC.

This second edition cancels and replaces the first edition (ISO/IEC 25437:2006), which has been technically

revised.
iv © ISO/IEC 2009 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 25437:2009(E)
Introduction

ISO/IEC 22534, Application Session Services, specifies XML protocols that can be used to create and

manage application sessions that are independent of the transport layer protocols. This International Standard

(WS-Session) specifies Web services for ISO/IEC 22534.

The ApplicationSessionTerminated operation of this International Standard is an outbound asynchronous

event notification. For the Service Requester to receive the event notification from the Service Provider and

from web services (e.g. ECMA-348) that use this International Standard for session management, it

standardized the WS-BaseNotification Option and illustrated the use of WS-Eventing.

© ISO/IEC 2009 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 25437:2009(E)
Information technology — Telecommunications and information
exchange between systems — WS-Session — Web services for
application session services
1 Scope

This International Standard specifies Web Services (in WSDL) and a SOAP binding for the Application

Session Services defined in ISO/IEC 22534. The Application Session Services allow Applications to create

and maintain a 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 the 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 ApplicationSessionTerminated operation of this International Standard is an outbound asynchronous

event notification that Service Requesters receive from the Service Provider. Service Requester may also

receive the event notification from web services, e.g. ECMA-348, that use this International Standard for

session management.

This International Standard specifies the event subscription and notification behaviors.

Annex A specifies the event subscription mechanism using WS-BaseNotification Option.

Annex B specifies the asynchronous subscription response Option for the two event subscription mechanisms.

Annex C illustrates the event subscription mechanism using WS-Eventing.
Annex D shows an example WS-Session WSDL binding with SOAP/HTTP.
Annex E lists SOAP XML Templates for ISO/IEC 22534 messages.
Annex F lists some SOAP XML Templates for WS-Eventing messages.
Annex G lists some SOAP XML Templates for WS-BaseNotification messages.
Annex H provides a summary of changes.
2 Conformance

The Service Requester 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 Clauses 5, 6 and 7 respectively.

The Service Provider may implement the WS-BaseNotification event subscription Option as specified in

Annex A.
© ISO/IEC 2009 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 25437:2009(E)

The Service Provider's WSDL shall include the implemented event subscription operations in the WSDL

specified in Clause 5.
The Service Requester shall itself initiate or delegate event subscription.

The Service Provider supports synchronous responses to event subscriptions and may implement the

asynchronous response Option specified in Annex B.
3 Normative references

The following referenced documents are indispensable for the application of this document. For dated

references, only the edition cited 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, W3C Note 08 May 2000
WSDL 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 October 2004

WS-Addressing 1.0 Web Services Addressing 1.0 – Core W3C Recommendation 9 May 2006

Web Services Addressing 1.0 - SOAP Binding W3C Recommendation 9 May 2006
Web Services Addressing 1.0 – Metadata, W3C Recommendation
4 September 2007

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 following terms and definitions 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.1.3
Application Session
association between an application and a server
2 © ISO/IEC 2009 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 25437:2009(E)
4.2 Namespaces
This International Standard uses these Ecma prefixes and namespaces:

1. aps (http://www.ecma-international.org/standards/ecma-354/appl_session): This International

Standard imports all XML messages defined in ECMA-354 (ISO/IEC 22534) from the aps

namespace.

2. wss (http://www.ecma-international.org/standards/ecma-366/ws-session/ed2): The WSDL target

namespace for this International 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): This contains the W3C SOAP bindings for WSDL 1.1.

4. wsa (http://www.w3.org/2005/08/addressing): The namespace for WS-Addressing 1.0.

5. wsnt (http://docs.oasis-open.org/wsn/b-2.xsd): The target namespace for WS-BaseNotification 1.3.

© ISO/IEC 2009 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 25437:2009(E)
5 Service Provider WSDL Abstract Definitions

This clause specifies the abstract WSDL definitions to support the services specified in ISO/IEC 22534.

xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:aps="http://www.ecma-international.org/standards/ecma-354/appl_session"
xmlns:wss="http://www.ecma-international.org/standards/ecma-366/ws-session/ed2"

targetNamespace="http://www.ecma-international.org/standards/ecma-366/ws-session/ed2">



schemaLocation="http://www.ecma-international.org/standards/ecma-354/appl_session/start-application-session.xsd"/>

schemaLocation="http://www.ecma-international.org/standards/ecma-354/appl_session/stop-application-session.xsd"/>

schemaLocation="http://www.ecma-international.org/standards/ecma-354/appl_session/reset-application-session-timer.xsd"/>

schemaLocation="http://www.ecma-international.org/standards/ecma-354/appl_session/application-session-terminated.xsd"/>

































4 © ISO/IEC 2009 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 25437:2009(E)




















© ISO/IEC 2009 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 25437:2009(E)
6 Service Provider WSDL SOAP Binding

This clause specifies the binding template of the abstract WSDL definitions in Clause 5 with SOAP Messages

without a specific transport protocol. The binding template uses XML Schema data types instead of values for

some attributes. Any actual SOAP binding to a transport shall contain elements and attributes in this binding

template where the attributes shall be substituted by permitted values.
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:aps="http://www.ecma-international.org/standards/ecma-354/appl_session"
xmlns:wss="http://www.ecma-international.org/standards/ecma-366/ws-session/ed2"

targetNamespace="http://www.ecma-international.org/standards/ecma-366/ws-session/ed2">

location="http://www.ecma-international.org/standards/ecma-366/ws-session/ed2/ws-session-wsdl-

abstract-definitions.wsdl" />










































6 © ISO/IEC 2009 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 25437:2009(E)

ISO/IEC 22534 requires Applications to include the aps:sessionID in the service requests that address the

established session. To standardize this requirement in Web services that exchange messages, the

placement of aps:sessionID shall follow these rules.

1. For any service message (e.g. Subscribe) addressed to an endpoint with WS-Addressing Endpoint

Reference, the aps:sessionID element is treated as an extension to the Endpoint Reference. When

the message is bound to SOAP, the aps:sessionID element shall be added to the SOAP message

as a header block.

2. Other SOAP messages within a session shall include the aps:sessionID as a header block.

The negative responses from Service Providers shall be bound to the SOAP 1.1 fault properties: faultcode,

faultstring and detail, using the following template.
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:aps="http://www.ecma-international.org/standards/ecma-354/appl_session">


[faultcode]
[faultstring]
[detail]



The contents of fault properties are defined by the following table for each type of negative response.

Table 1 — Fault names and properties for WS-Session services
Fault Name StartFault
ISO/IEC 22534 defined standard error names: invalidApplicationInfo,
faultcode
requestedProtocolVersionNotSupported, serverResourcesBusy, maxNumberSessions, or
application error name.

For ISO/IEC 22534 standard errors, it is the Description of corresponding error in Table 4-3

faultstring

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 be provided.
Element aps:StartApplicationSessionNegResponse.
detail
StopFault
Fault Name

ISO/IEC 22534 defined standard error names: invalidSessionID, or application error name.

faultcode

For ISO/IEC 22534 standard errors, it is the Description of corresponding error in Table 4-6

faultstring

of ISO/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.
Element aps:StopApplicationSessionNegResponse.
detail
ResetFault
Fault Name
ISO/IEC 22534 defined standard error names: invalidSessionID,
faultcode
serverCannotResetSessionDuration, or application error name.

ISO/IEC 22534 standard errors, it is the Description of corresponding error in Table 4-9 of

faultstring

ISO/IEC 22534. Additonal text can be provided to elaborate the error message, for example,

the duration allowed by the service provider. For application errors, a proper English

description shall be provided.
Element aps:ResetApplicationSessionTimerNegResponse.
detail
© ISO/IEC 2009 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 25437:2009(E)
7 Event Subscription and Notification

The ApplicationSessionTerminated operation is an outbound asynchronous event notification.

The Service Requester shall subscribe to receive the event notification from the Service Provider according to

the event subscription mechanism of the Service Provider. It shall provide the notification consumer URI as

defined in Annex A and B, and shall make the said notification consumer WSDL available to the Service

Provider.

The Service Requester shall subscribe to receive the ApplicationSessionTerminated event immediately after

the successful completion of the StartApplicationSession operation.

The Service Provider and Requester shall implement WS-Addressing defined by [WS-Addressing 1.0].

The subscription message shall include the unique aps:sessionID obtained from the StartApplicationSession

operation. The aps:sessionID element shall be the first level child element of the subscription endpoint

reference parameters [WS-Addressing 1.0], and the element is bound to the SOAP message as a header

block as defined in Clause 6.

The Service Requester and Provider shall support the push mode to deliver the event notification. The Service

Provider shall send event notifications to each of the valid notification consumer endpoints declared in the

event subscription message.

The event notification message from the Service Provider shall include the notification consumer endpoint

reference parameters, if any, so that the Service Requester can correlate the event notification obtained from

the Service Provider using those parameters.

If the application session terminates abnormally, before the ApplicationSessionTerminated event can be

subscribed to, the subsequent subscription of ApplicationSessionTerminated event by the Service Requester

shall result in a SOAP fault message as defined by the subscription protocol.

When a session terminates, any subscription associated with the session is deemed invalid.

8 © ISO/IEC 2009 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 25437:2009(E)
Annex A
(normative)
Subscription Using WS-BaseNotification Option

The Service Provider shall implement the wsnt:Subscribe operation defined in the NotificationProducer

portType of WS-BaseNotification WSDL and may implement other operations, such as wsnt:Unsubscribe,

defined in the SubscriptionManager portType [WS-BaseNotification 1.3].

The Service Requester shall use wsnt:Subscribe operation to subscribe to the events of Service Provider. The

subscription request for wrapped or unwrapped (a.k.a. raw in WS-BaseNotification) event delivery mode shall

follow WS-BaseNotification specification.

If the Service Provider does not support the requested event delivery mode, it shall return the fault message

wsnt:UnsupportedPolicyRequestFault as specified by WS-BaseNotification.

If the aps:sessionID [sessionID] in the request is invalid, the Service Provider shall return a SOAP 1.1 fault

message with these properties:
• [faultcode]=”wsrf-rw:ResourceUnknownFault”
• [faultstring]=”The session [sessionID] is invalid”
• [detail]=invalidSessionID:[sessionID]
A.1 Wrapped Delivery Mode Notification Consumer WSDL for Service Requester and
Its SOAP Binding

Service Requesters shall implement WS-BaseNotification wrapped Notification Consumer WSDL and its

SOAP binding to specify its wrapped notification consumer interface.
A.2 Unwrapped Delivery Mode Notification Consumer WSDL for Service Requester
and Its SOAP Binding

Service Requesters shall implement unwrapped notification consumer WSDL and its SOAP binding specified

in this annex to specify its unwrapped notification consumer interface.
© ISO/IEC 2009 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/IEC 25437:2009(E)
Annex B
(normative)
Asynchronous Response to Subscription Request Option

The Service Provider and Requester shall follow WS-Addressing [WS-Addressing 1.0] to annotate and

correlate event subscription messages for asynchronous message exchange. The request SOAP message

from Service Requester intended for an asynchronous response shall include at least the following WS-

Addressing headers: wsa:To, wsa:Action, wsa:MessageID, and wsa:ReplyTo (wsa:FaultTo) whose value is

defined by the Service Requester. In particular, the Service Requester shall provide a valid non-anonymous

URI in wsa:ReplyTo field in its service request messages.

The asynchronous response or fault SOAP message shall include at least the following WS-Addressing

headers: wsa:To, wsa:Action, and wsa:RelatesTo, whose values shall be formulated according to WS-

Addressing specificiation [WS-Addressing 1.0 Core]. If the Service Provider only supports synchronous

response, it shall return a SOAP fault message with faultcode set to wsa:OnlyAnonymousAddressSupported

[WS-Addressing 1.0 SOAP Binding].
An asynchronous event subscription SOAP message template is shown below.
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:aps="http://www.ecma-international.org/standards/ecma-354/appl_session">

xs:anyURI
xs:string
[message_id]
[reply_address]
xs:anyURI
xs:any*



The template for the reply message (response or fault) is shown below.
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:wsa="http://www.w3.org/2005/08/addressing"
xmlns:aps="http://www.ecma-international.org/standards/ecma-354/appl_session">

[reply_address]
[message_id]
xs:anyURI
xs:any*



10 © ISO/IEC 2009 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 25437:2009(E)
Annex C
(informative)
Event Subscription Using WS-Eventing
WS-Eventing can be found at http://www.w3.org/Submission/WS-Eventing/.
wse is the target namespace prefix for WS-Eventing at
http://schemas.xmlsoap.org/ws/2004/08/eventing.

WS-Eventing uses “event sink” to mean “notification consumer” defined in WS-BaseNotification. For

consistency, we use “notification consumer” throughout this Standard.
The target namespace of the wrapped notification consumer WSDL: gsk

(http://www.ecma-international.org/standards/ecma-366/ws-session/ed2/generic_sink).

The Service Provider may implement the wse:SubscribeOp operation defined in the EventSource portType of

WS-Eventing WSDL and may implement other operations, such as wse:UnsubscribeOp, defined in the

SubscriptionManager portType. The Service Provider should use WS-Addressing 1.0 with WS-Eventing.

The Service Requester shall use wse:SubscribeOp operation to subscribe to the events. The subscription

message from the Service Requester shall conform to the requirements of WS-Eventing.

To request wrapped event delivery mode, the Service Requester shall use the following URI in its event

subscription request according to WS-Eventing:
http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryModes/Wrap

To request unwrapped event delivery mode, the Service Requester shall use the following URI in its event

subscription request according to WS-Eventing:
http://www.ecma-international.org/standards/ecma-366/ws-session/ed2/typed_sink

If the Service Provider does not support the requested event delivery mode, it shall return the fault message

wse:DeliveryModeRequestedUnavailable as specified by WS-Eventing.
If the aps:sessionID [sessionID] in the request is invalid, the Service Provider
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.