ITU-T X 227 AMD 1-1996 Information Technology - Open Systems Interconnection - Connection-Oriented Protocol for the Association Control Service Element Protocol Specification - Amers.pdf

《ITU-T X 227 AMD 1-1996 Information Technology - Open Systems Interconnection - Connection-Oriented Protocol for the Association Control Service Element Protocol Specification - Amers.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 227 AMD 1-1996 Information Technology - Open Systems Interconnection - Connection-Oriented Protocol for the Association Control Service Element Protocol Specification - Amers.pdf（11页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZfITION SECTOR OF ITU X.227 Amendment I (I 0/96) SERIES X: DATA NETWORKS AND OPEN SYSTEM COM M U N I CATI ON Open System Interconnection - Connection-mode protocol specificat ions Information technology - Open Systems Interconnec

2、tion - Connection-oriented protocol for the association con t ro I servi ce e le ment : P rot oco I spec fi ca t i on Amendment I : Incorporation of extensibility markers . ITU-T Recommendation X.227 - Amendment I (Previously CCITT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPE

3、N SYSTEM COMMUNICATION PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenance Administrative arrangements OPEN SYSTEM INTERCONNECTION Model and notation X.l-X.199 X.1-X. 19 X.20-X.49 X.50-X.89 X.90-X. 149 X.150-X.179 X.180-X.199 X.2

4、00-X.299 X.200-X.209 X.2 1 O-X.2 19 Service definitions Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing INTERWORKING BETWEEN NETWORKS General Satellite data transmission systems MESSAGE HANDLING SYSTEMS D

5、IRECTORY OS1 NETWORKING AND SYSTEM ASPECTS Networking Efficiency Naming, Addressing and Registration Abstract Syntax Notation One (ASN.l) OS1 MANAGEMENT Systems Management framework and architecture Management Communication Service and Protocol Structure of Management Information Management function

6、s SECURITY OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.230-X.239 X.240-X.259 X.260-X.269 X.270-X.279 X.280-X.289 X.290-X.299 X.300-X.399 X.300-X.349 X.350-X.399 X.400-X.499 X.500-X.599 X.600-X.699 X.600-X.629 X.630-X.64

7、9 X.650-X.679 X.680-X.699 X.700-X.799 X.700-X.709 X.710-X.719 X.720-X.729 X.730-X.799 X.800-X.849 X.850-X.899 X.850-X.859 X.860-X.879 X.880-X.899 X.900-X.999 For firther details, please refer to ITU-T List of Recommendations. STD.1TU-T RECMN X-227 AND L-ENGL 177b 48b2571 Ob37004 028 D FOREWORD ITU (

8、International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. Some 179 member countries, 84 telecom operating entities, 145 scientific and industrial organi

9、zations and 38 international organizations participate in ITU-T which is the body which sets world telecommunications standards (Recommendations). The approval of Recommendations by the Members of ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, 1993). In addition, the

10、 World Telecommunication Standardization Conference (WTSC), which meets every four years, approves Recommendations submitted to it and establishes the study programme for the following period. In some areas of information technology which fall within ITU-T?s purview, the necessary standards are prep

11、ared on a collaborative basis with IS0 and IEC. The text of ITU-T Recommendation X.227, Amendment 1, was approved on 5th of October 1996. The identical text is also published as ISO/IEC International Standard 8650-1. NOTE In this Recommendation, the expression ?Administration? is used for concisenes

12、s to indicate both a telecommunication administration and a recognized private operating agency. O ITU 1997 All rights reserved. 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 i

13、n writing from the ITU. ITU-T Rec. X.227 (1995)/Amd.l (1996 E) I CONTENTS Page 1) Subclause 2.1 1 2) Subclause 9.1 1 ii ITU-T Rec. X.227 (1995)/Amd.l (1996 E) STD*ITU-T RECMN X.227 AND 1-ENGL L77b D 48b2571 Ob3700b 7TO = Summary This amendment to the connection-oriented ACSE protocol specification i

14、ncludes the ASN. 1 extensibiliy marker in the module describing the protocol. ITU-T Rec. X.227 (1995)/Amd.l(1996 E) . 111 ISO/IEC 8650-1 : 199WAmd.l : 1997 (E) INTERNATIONAL STANDARD ITU-T RECOMMENDATION INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - CONNECTION-ORIENTED PROTOCOL FOR THE ASS

15、OCIATION CONTROL SERVICE ELEMENT: PROTOCOL SPECIFICATION AMENDMENT 1 Incorporation of extensibility markers 1) Subclause 2.1 Add the following reference. - ITU-T Recommendation X.501 (1993) I ISO/IEC 9594-2:1995, Information Technology - Open Systems Interconnection - The Directory: Models. 2) Subcl

16、ause 9.1 Replace the ASN I module with the following: ACSE-1 joint-so-tu-t association-control(2) modules(0) apdus(0) versionl(1) ) - ACSE-i refers to ACSE version I DEFINITIONS := BEGIN EXPORTS awe-as-id, ACSE-apdu, aCSE-id, Application-context-name, AP-title, AE-qualifier, AE-title, AP-invocation-

17、identifier, AE-invocation-identifier, Mechanism-name, Authentication-value, ACSE-requirements; IMPORTS Name, RelativeDistinguishedName FROM InformationFramework joint-so-ccitt ds(5) module(1) informationFramework(1) 2 ; - The data types Mame and RelativeDistinguishedMame are importedfrom ISOIEC 9594

18、-2. - object identijer assignments acse-as-id OBJECT IDENTIFIER := - may be used to reference the abstract syntax of the ACSE APDUs aCSE-id OBJECT IDENTIFIER := joint-so-tu-t association-control(2) abstract-syntax(1) apdus(0) versionl(1) ) ( joint-so-tu-t association-control(2) ase-id(3) acse-ase(1)

19、 version(1) - may be used to identrfl the Association Control ASE. LTU-T Rec. X.227 (1995)/Amd.l(1996 E) 1 STD*ITU-T RECMN X-227 AMD 1-ENGL 199b M 48b259L Ob37008 773 ISOIIEC 8650-1 : 1996lAmd.l : 1997 (E) - top level CHOICE ACSE-apdu := CHOICE aarq AARQ-apdu, aare AARE-apdu, rlrq RLRQ-apdu, rlre RL

20、RE-apdu, abrt ABRT-apdn, . 1 AARQ-apdu := APPLICATION O 1 IMPLICIT SEQUENCE protocol-version O IMPLICIT BIT STRING versionl (O) DEFAULT versionl , application-context-name i Application-context-name, called-AP-title 2 AP-title OPTIONAL, called-AE-qualifier 3 AE-qualifier OPTIONAL, called-AP-invocati

21、on-identifier 4 AP-invocation-identifier OPTIONAL, called-AE-invocation-identifier SI AE-invocation-identifier OPTIONAL, calling-AP-title 6 AP-title OPTIONAL, calling-AE-qualifier 7 AEqualifier OPTIONAL, calling-AP-invocation-identifier SI AP-invocation-identifier OPTIONAL, calling-AE-invocation-ide

22、ntifier 9 AE-invocation-identifier OPTIONAL, - The followingfieldshall not be present if only the Kernel is used. sender-acse-requirements 1101 IMPLICIT ACSE-requirements - The following field shall only be present if the Authentication functional unit is selected. OPTIONAL, mechanism-name il IMPLIC

23、IT Mechanism-name OPTIONAL, - The following field shall onb be present if the Authentication functional unit is selected. calling-authentication-value i21 EXPLICIT Authentication-value application-context-name-list 131 IMPLICIT Application-context-name-list OPTIONAL, OPTIONAL, - The above field shal

24、l only be present if the Application Context Negotiation functional unit is selected implementation-information 1291 IMPLICIT Implementation-data OPTIONAL, ., ., user-information 30 IMPLICIT Association-information OPTIONAL I AARE-apdu := APPLICATION 1 IMPLICIT SEQUENCE protocol-version O IMPLICIT B

25、IT STRING versionl (O) DEFAULT versionl , application-context-name i Application-context-name, result 2 Associate-result, result-source-diagnostic 3 Associate-source-diagnostic, responding-AP-title 4 AP-title OPTIONAL, responding-AE-qualifier 5 AE-qualifier OPTIONAL, responding-AP-invocation-identif

26、ier 6 AP-invocation-identifier OPTIONAL, responding-AE-invocation-identifier 7 AE-invocation-identifier OPTIONAL, responder-acse-requirements SI IMPLICIT ACSE-requirements - The following field shall only be present if the Authentication functional unit is selected. - The following field shall not b

27、e present if only the Kernel is used. OPTIONAL, mechanism-name 9 IMPLICIT Mechanism-name OPTIONAL, - This following field shall only be present if the Authentication functional unit is selected. responding-authentication-value lo EXPLICIT Authentication-value application-context-name-list li IMPLICI

28、T Application-context-name-list - The above field shall only be present if the Application Context Negotiation functional unit is selected implementation-information 1291 IMPLICIT Implementation-data OPTIONAL, OPTIONAL, OPTIONAL, 2 ., .I ITU-T Rec. X.227 (1995)/Amd.l (1996 E) AMD 1-ENGL user-informa

29、tion 1301 RLRQ-apdu := APPLICATION 2 IMPLICIT SEQUENCE reason I01 ., ., user-information 1 URE-apdu := APPLICATION 3 IMPLICIT SEQUENCE reason I01 ., ., user-information 1 ABRT-apdu := APPLICATION 4 IMPLICIT SEQUENCE abort-source IO1 a bort-diagnostic I11 - Thisfield shall not be present ifonly the K

30、ernel is used. ISO/IEC 8650-1 : 1996/Amd.l : 1997 (E) IMPLICIT Association-information OPTIONAL IMPLICIT Release-request-reason OPTIONAL, IMPLICIT Association-information OPTIONAL IMPLICIT Release-response-reason OPTIONAL, IMPLICIT Association-information OPTIONAL IMPLICIT ABRT-source, IMPLICIT ABRT

31、-diagnostic OPTIONAL. ., ., user-information 30 IMPLICIT Association-information 1 ABRT-diagnostic := ENUMERATED no-reason-given (i), protocol-error (2), authentication-mechanism-name-not-recognized (3), authentication-mechanism-name-required (4), authentication-failure (5), authentication-required

32、(6), . I ABRT-source := INTEGER ( acse-service-user (O), acse-service-provider (1) (Ol, .) ACSE-requirements := BIT STRING authentication (O), application-context-negotiation(1) Application-context-name-list := SEQUENCE OF Application-context-name Application-context-name := OBJECT IDENTIFIER - Appl

33、ication-enti title productions follow (not in alphabetical order) AP-title := CHOICE aptitle-form1 AP-title-forml, ap-title-form2 AP-title-ford, . ) ae-qualifier-form 1 AE-qualifier-forml, ae-qualifier-form2 AE-qualifier-formt, . ) AE-qualifier := CHOICE When both AP-title and AE-qualifier data valu

34、es are present in an AARQ or AARE APDU, both must have the same form to allow the construction of an AE-title as discussed in CCITT Rec. X. 665 I ISO/IEC 9834-6. AP-title-form1 :=Name - The value assigned to AP-title-forml is The Directory Name of an application-process title. AE-qualifier-form1 :=

35、RelativeDistinguishedName - The value assigned to AE-qualijier-forml is the relative distinguished name of a particular - application-enti of the application-process identiJied by AP-title-forml. AP-title-form2 := OBJECT IDENTIFIER AE-qualifier-form2 := INTEGER AE-title := CHOICE ae-title-forml ae-t

36、itle-form2 . I AE-title-forml, AE-title-form2, OPTIONAL ITU-T Rec. X.227 (1995)/Amd.l(1996 E) 3 STD-ITU-T RECMN X.227 AMD 1-ENGL 177b H LiBb2591 Ob370LO 32L ISO/IEC 8650-1 : 1996/Amd.l : 1997 (E) - As defined in CCITT Rec. X. 650 I IS0 7498-3, an application-entity title is composed of an applicatio

37、n- - process title and an application-entity qualifier. The ACSE protocol provides for the transfer of an - application-entity title value by the transfer of its component values. However, the following data type - is provided for international Standars that reference a single syntactic structure fo

38、r AE titles. - For access to The Directory (ITU-T Rec. X.500-Series 1 ISO/IEC 9594), an AE title has AE-title-formi. - This value can be constructedfrom AP-title-form I and AE-qualifier-form I values contained in an - AARQ or AARE APDU. A discussion offorming an AE-title-forml from AP-title-forml an

39、d AE-qualijer- - form I may be found in CCIT Rec. X 665 I ISO/IEC 9834-6. AE-title-form2 := OBJECT IDENTIFIER - A discussion of forming an AE-title-form2 from AP-titlegorm2 and AE-qualifier-form2 may be - found in CCITT Rec. X.665 I ISO/IEC 9834-6. AE-invocation-identifier := INTEGER AP-invocation-i

40、dentifier := INTEGER - End of Application-entity title productions Associate-result := INTEGER AE-title-forml := Name ( accepted (O), rejected-permanent (i), rejected-transient (2) (0.2, .) Associate-source-diagnostic := CHOICE acse-service-user i INTEGER nuIl (01, no-reason-given (i), application-c

41、ontext-name-not-supported (2), calling-AP-title-not-recognized (3), calling-AP-invocation-identifier-not-recognized (4), calling-AE-qualifier-not-recognized (5), calling-AE-invocation-identifier-not-recognized (6), called-AP-title-not-recognized (7), called-AP-invocation-identifier-not-recognized (S

42、), called-AE-qualifier-not-recognized (9), called-AE-invocation-identifier-not-recognized (lo), authentication-mechanism-name-not-recognized (1 i), authentication-mechanism-name-required (12), acse-sewice-provider 1 authentication-failure (13), authentication-required (14) (014, .), 2 INTEGER null (

43、01, no-reason-given (l), no-common-acse-version (2) (02 , .) Association-information := SEQUENCE SIZE (1, ., O I 2MAX) OF EXTERNAL Authentication-value := CHOICE charstring O IMPLICIT Graphicstring, bitstring i IMPLICIT BIT STRING, external 2 IMPLICIT EXTERNAL, other 3 IMPLICIT SEQUENCE ( other-mech

44、anism-name MECHANISM-NAME.&id (Objectset), other-mechanism-value MECHANISM-NAME.&Type (ObjectSet(.other-mechanism-name) 1 1 - The abstract syntax of (calling/responding) authentication-value is determined by the authentication - mechanism used during association establishment. The authentication mec

45、hanism is either explicitly - denoted by the &idfield (of type OBJECTIDENTIFIER) for a mechanism belonging to the class - MECHANISM-NAME, or it is known implicitly by - prior agreement between the communicating partners. Ifthe “other” component is chosen, then - the “mechanism-name ” component must

46、be present in accordance with - ITU-T Rec. X. 680 I ISO/iEC 8824. If the value “mechanism-name ” occurs in the AARQ-apdu or the - AARE-apdu, then that value must be the same as the value for “other-mechanism-name” 4 ITU-T Rec. X.227 (1995)/Amd.l(1996 E) STD-ITU-T RECMN X-227 AMD 1-ENGL 199b qBb2571

47、Ob37011 2bB ISODEC 8650-1 : 1996/Amd.l : 1997 (E) Implementation-data := Graphicstring Mechanism-name := OBJECT IDENTIFIER MECHANISM-NAME :=TYPE-IDENTIFIER Objectset MECHANISM-NAME := I. Release-request-reason := INTEGER normal (O), urgent (1) , user-defined (30) (O I 1 130, .) Release-response-reas

48、on := INTEGER ( normal (O), not-finished (1) , user-defined (30) (O I 1 I 30, .) END ITU-T Rec. X.227 (1995)/Amd.l (1996 E) 5 Series A Series B Series C Series D Series E Series F Series G Series H Series I Series J Series K Series L Series M Series N Series O Series P Series Q Series R Series S Ser

49、ies T Series U Series V Series X Series Z ITU-T RECOMMENDATIONS SERIES Organization of the work of the ITU-T Means of expression: definitions, symbols, classification General telecommunication statistics General tariff principles Overall network operation, telephone service, service 0perat.m anL .&uman factors Non-telephone telecommunicat