ISO IEC 22534-2005 Information technology - Telecommunications and information exchange between systems - Application session services《信息技术 系统间远程通信和信息交换 应用会话服务》.pdf

《ISO IEC 22534-2005 Information technology - Telecommunications and information exchange between systems - Application session services《信息技术 系统间远程通信和信息交换 应用会话服务》.pdf》由会员分享，可在线阅读，更多相关《ISO IEC 22534-2005 Information technology - Telecommunications and information exchange between systems - Application session services《信息技术 系统间远程通信和信息交换 应用会话服务》.pdf（26页珍藏版）》请在麦多课文档分享上搜索。

1、 Reference number ISO/IEC 22534:2005(E) ISO/IEC 2005INTERNATIONAL STANDARD ISO/IEC 22534 First edition 2005-05-01Information technology Telecommunications and information exchange between systems Application session services Technologies de linformation Tlcommunications et change dinformation entre

2、systmes Services de session dapplication ISO/IEC 22534:2005(E) PDF disclaimer This PDF file may contain embedded typefaces. In accordance with Adobes 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

3、the computer performing the editing. In downloading this file, parties accept therein the responsibility of not infringing Adobes 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

4、 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 in

5、form the Central Secretariat at the address given below. ISO/IEC 2005 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

6、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 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO/IEC 2005 All rights reservedISO/IEC 22

7、534:2005(E) ISO/IEC 2005 All rights reserved iiiContents Page Foreword iv Introduction v 1 Scope 1 1.1 Overview 1 1.2 Template Description 1 2 Conformance. 2 2.1 Application Conformance 2 2.2 Server Conformance. 2 3 Normative references. 2 4 Service Definitions 3 4.1 Start Application Session. 3 4.1

8、.1 Service Request 3 4.1.2 Service Response. 4 4.1.3 Functional Requirements. 4 4.2 Stop Application Session. 5 4.2.1 Service Request 5 4.2.2 Service Response. 5 4.2.3 Functional Requirements. 6 4.3 Reset Application Session Timer 6 4.3.1 Service Request 6 4.3.2 Service Response. 6 4.3.3 Functional

9、Requirements. 7 4.4 Application Session Terminated. 7 4.4.1 Service Request 7 4.4.2 Service Response. 7 4.4.3 Functional Requirements. 8 5 Schema Definitions. 8 5.1 Start Application Session. 8 5.2 Stop Application Session. 10 5.3 Reset Application Session Timer 11 5.4 Application Session Terminated

10、. 12 Annex A (informative) Examples. 14 Annex B (informative) CSTA Usage Notes. 18 Bibliography . 19 ISO/IEC 22534:2005(E) iv ISO/IEC 2005 All rights reservedForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies).

11、The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-g

12、overnmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2

13、. The main task of technical committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a

14、vote. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/IEC 22534 was prepared by Ecma International (as ECMA-354) and was adopted, under a special

15、 “fast-track procedure”, by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 6, Telecommunications and information exhange between systems, in parallel with its approval by national bodies of ISO and IEC. ISO/IEC 22534:2005(E) ISO/IEC 2005 All rights reserved vIntrodu

16、ction This International Standard defines Ecma Application Session Services a set of XML-based services used to establish and maintain an application session for exchanging application messages. The application session established by this International Standard is independent of the underlying trans

17、port protocol (TCP, HTTP, etc.) for exchanging application messages. Sessions for application protocols such as CSTA-XML (ECMA-323) may be established using this International Standard. INTERNATIONAL STANDARD ISO/IEC 22534:2005(E) ISO/IEC 2005 All rights reserved 1Information technology Telecommunic

18、ations and information exchange between systems Application session services 1 Scope The services defined in this International Standard are used to establish and maintain a relationship between an application and a server for the purpose of exchanging application messages. For the purpose of this I

19、nternational Standard this relationship is called an application session. Application protocols, such as ECMA-323, require that an application session is established before application messages are exchanged. ECMA-269 specifies several mechanisms for establishing an application context. One possible

20、 mechanism is ACSE (ISO/IEC 8649) but since ASCE uses ASN.1 encoding for its services, it is not desirable for use with XML based protocols such as ECMA-323. This International Standard provides an XML-based alternative for establishing application sessions. 1.1 Overview The Ecma Application Session

21、 Services consist of the following services: Start Application Session. This service is used by an application to establish an application session with a server. A globally unique sessionID is returned by the server in the response message. The sessionID is used in other services to address the sess

22、ion as long as the session exists. Stop Application Session. This service is used by an application to stop an application session. Reset Application Session Timer. This service is used by an application to reset the timer associated with an application session. If the application timer is not reset

23、 before it expires, the application session will be terminated. Application Session Terminated This service is used by the server to indicate that the application session has been abnormally terminated (i.e. not via the Stop Application Session service). 1.2 Template Description The services specifi

24、ed in Clause 4 include tables that contain the following columns: Parameter Name the name that is used to reference the parameter. This corresponds to the XML element name specified in Clause 5. Type the format of the parameter. This corresponds to the XML element type used in the XML schema definit

25、ion in Clause 5. M/O the Mandatory/Optional aspect of the parameter. Mandatory parameters must be included in the corresponding XML instance document while optional parameters may be omitted. Description Describes the purpose of the parameter. ISO/IEC 22534:2005(E) 2 ISO/IEC 2005 All rights reserved

26、2 Conformance This Clause specifies the conformance requirements for an application and a server to conform to this International Standard. 2.1 Application Conformance In order to conform to this International Standard an application shall: 1) Support the following services as follows: b) Sending th

27、e Start Application Session service and all of the mandatory aspects of this service as specified in Clause 4. c) Sending the Stop Application Session service and all of the mandatory aspects of this service as specified in Clause 4. d) Sending the Reset Application Session service and all of the ma

28、ndatory aspects of this service as specified in Clause 4. e) Receiving the Application Session Terminated service and all of the mandatory aspects of this service as specified in Clause 4. 2) Send and receive XML Instance documents according to the XML Schema specified in Clause 5 in this Internatio

29、nal Standard for the services listed in item 1. 2.2 Server Conformance In order to conform to this International Standard a server shall: 1) Support the following services as follows: a) Receiving the Start Application Session service and all of the mandatory aspects of this service as specified in

30、Clause 4. b) Receiving the Stop Application Session service and all of the mandatory aspects of this service as specified in Clause 4. c) Receiving the Reset Application Session service and all of the mandatory aspects of this service as specified in Clause 4. d) Sending the Application Session Term

31、inated service and all of the mandatory aspects of this service as specified in Clause 4. 2) Send and receive XML Instance documents according to the XML Schema specified in Clause 5 in this International Standard for the services listed in item 1. 3 Normative references This Clause has no content i

32、n this document. ISO/IEC 22534:2005(E) ISO/IEC 2005 All rights reserved 34 Service Definitions 4.1 Start Application Session The Start Application Session service is used to initiate an application session between an application and a server. A globally unique identifier, called a sessionID, is retu

33、rned in the positive service response that identifies the application session. Once an application session is established, the server must maintain information associated with the application session. When the application session is terminated, the application context information is cleared. The app

34、lication session exists until: it is stopped by using a Stop Application Session service the session is abnormally terminated by the server as indicated by the Application Session Terminated service (e.g., due to the session timer expiry) etc. 4.1.1 Service Request Table 4-1 Start Application Sessio

35、n Service Request Parameter Name Type M/O Description applicationInfo Sequence M Specifies information associated with the application requesting the application session. This information consists of: applicationID (M) a character string that identifies the application requesting the application ass

36、ociation. applicationSpecificInfo (O) this consists of a list of one or more implementation specific attributes associated with the application requesting the application association. requestedProtocolVersions List of character strings M Specifies one or more application protocol versions that the a

37、pplication wishes to use for the application association. The list is ordered by highest priority protocol version first. The server shall choose the highest priority protocol version that it supports and return the chosen protocol version in the positive response. The character string specifying a

38、specific protocol must be a globally unique string (e.g., a standardized namespace (URI) that indicates a given protocol version). requestedSessionDuration Value O Specifies the length of time (in seconds) that the application session should be maintained. The sessionDuration timer can be periodical

39、ly refreshed via the Reset Application Session Timer service. If the requestedSessionDuration is not provided the server will choose a default sessionDuration value. extensions Sequence O Specifies non-standardized information. ISO/IEC 22534:2005(E) 4 ISO/IEC 2005 All rights reserved4.1.2 Service Re

40、sponse 4.1.2.1 Positive Acknowledgement Table 4-2 Start Application Session Positive Service Response Parameter Name Type M/O Description sessionID Character String M Specifies the globally unique identifier associated with the application session that has been created. actualProtocolVersion Charact

41、er String M Specifies the protocol version that is being used for the application session. This protocol version shall be one of the protocol versions specified in the service request. actualSessionDuration Value M Specifies the value for the length of time (in seconds) that the application session

42、will be maintained by the server. This value may be less than or equal to the requestedSessionDuration in the service request. If the requestedSessionDuration is not provided in the service request, the server shall provide a default value which shall be used for the application session. extensions

43、Sequence O Specifies non-standardized information. 4.1.2.2 Negative Acknowledgement Table 4-3 Start Application Session Negative Service Response Parameter Name Type M/O Description errorCode Character String M Specifies the type of error. Either a standardized error or an application specific error

44、 may be used. The standardized set of errors are: invalidApplicationInfo the server is unable to establish an application session due to invalid or unrecognized information in the applicationInfo parameter. requestedProtocolVersionNotSupported none of the requested protocol versions specified in the

45、 service request are supported. serverResourcesBusy the server cannot establish an application session due to internal resource constraints. maxNumberSessions the server cannot create an application session because it has reached the maximum number of allowed application sessions (e.g. license/provi

46、sioning limitations). extensions Sequence O Specifies non-standardized information. 4.1.3 Functional Requirements 1. The sessionID returned in the response is used in other Ecma Application Session services to manage the application session. 2. The positive response includes the actual value of the

47、sessionDuration used for the specified application session. This value may be less than what the application requested in the service request. ISO/IEC 22534:2005(E) ISO/IEC 2005 All rights reserved 53. For an existing session, an application can restart the sessionDuration timer by using the Reset A

48、pplication Session Timer service. 4. Once the sessionDuration timer expires the server shall terminate the application session and clear any application context information associated with the application session. 5. Mechanisms defined outside of this International Standard may be used to authentica

49、te a user before an application session is started. 4.2 Stop Application Session The Stop Application Session service is used by the application to terminate an existing application session. 4.2.1 Service Request Table 4-4 Stop Application Session Service Request Parameter Name Type M/O Description sessionID Character String M Specifies the globally unique identifier associated with the application session that is being stopped. sessionEndReason Character