ITU-T X 882 AMD 1-1995 Information Technology - Remote Operations OSI Realizations - Remote Operations Service Element (Rose) Protocol Specification Amendmenmt 1 Mapping TO A-Unit-d .pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1 X.882 (I 1 /95) DATA NETWORKS AND OPEN SYSTEM COMM UN ICATIONS OS1 APPLICATIONS - REMOTE OPERATIONS INFORMATION TECHNOLOGY - REMOTE OPERATIONS: OS1 REALIZATIONS - REMOTE OPERATIONS SERVICE ELEMENT

2、 (ROSE) PROTOCOL SPECIFICATION AMENDMENT I: MAPPING TO A-UNIT-DATA AND BUILT-IN OPERATIONS Amendment 1 to ITU-T Recommendation X.882 (Previously “CCITT Recommendation”) IPN= 4862591 0691 402 934 FOREWORD IT (International Telecommunication Union) is the United Nations Specialized Agency in the field

3、 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 indusaial organizations and 38 international organizations participate in ITU-T which is the body which sets

4、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 World Telecommunication Standardization Conference (WTSC), which meets every four years, app

5、roves Recommendations submitted to it and establishes the study programme for the foilowing period. In some areas of information technology which fali within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. The text of ITU-T Recommendation X.882, Amendm

6、ent 1, was approved on 21st of November 1995. The identical text is also published as ISO/IEC International Standard 13712-3. NOTE in this Recommendation, the expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized private operating ag

7、ency. O ITU 1996 Ail 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 in writing from the ITU. IPN= 4862591 0691 403 870 ITU-T X-SERIES RECOMMENDATIONS DATA NETWO

8、RKS AND OPEN SYSTEM COMMUNICATIONS (February 1994) ORGANIZATION OF X-SERIES RECOMMENDATIONS Subject area PUBLIC DATA NETWORKS Recommendation Series I X.l-X.19 I Services and Facilities I Interfaces Transmission, Signalling and Switching X.20-X.49 X.50-X.89 I Network Aspects I X.90-X. 149 I Maintenan

9、ce Administrative Arrangements X.150-X. 179 X.180-X.199 I OPEN SYSTEMS INTERCONNECTION I I Model and Notation Service Definitions X.200-X.209 X.2 1 O-X.2 19 I Connection-mode Protocol Specifications I X.220-X.229 I Connectionless-mode Protocol Specifications PICS Proformas Protocol Identification X.

10、23 O-X.23 9 X.240-X.259 X.260-X.269 I Secwity rotocots I X.270-X.279 I Layer Managed Objects Conformance Testing INTERWORKING BETWEEN NETWORKS X.280-X.289 X.290-X.299 I General I X.300-X.349 I Mobile Data Transmission Systems Management X.350-X.369 X.370-X.399 MESSAGE HANDLING SYSTEMS DIRECTORY OS1

11、NETWORKING AND SYSTEM ASPECTS I Networking I X.600-X.649 I X.400-X.499 X.500-X.599 Naming, Addressing and Registration Abstract Syntax Notation One (ASN.1) I OSIMANAGEMENT I X.700-X.799 I X.650-X.679 X.680-X.699 - SECURITY OS1 APPLICATIONS X.8 00-X. 849 IPN= 4862591 0691404 707 Commitment, Concurren

12、cy and Recovery Transaction Processing Remote Operations X.850-X.859 X.860-X.879 X.880-X.899 LUIF 1 J3lF 13 Page Clause 1 Subclause 2.1 Subclause 6.2 Subclause 6.3 Clause 8 Built-in operations Clause 9 Subclause 9.3.2 . Clause 10 Clause 10 Clause 1 1 Subclause A.l . Subclause A.4 . Subclause AS . An

13、nex C . Annex D . 1 1 1 2 2 2 3 3 3 4 4 4 5 5 6 6 U ITU-T Rec . X.882 (1994)/Amd.l (1995 E) IPN= 4862591 0691 405 643 Summary This amendment to Rec. X.882 I ISODEC 13712-3 provides the protocol procedures for the mapping of ROSE APDUs onto the A-UNIT-DATA service, and the inclusion of three built-in

14、 operations - Probe, Acknowledge and Cancel - which are of general utility to designers of ROSE-based applications. IPN= 4862591 0691 406 58T ITU-T Rec. X.882 (1994)IAmd.l(1995 E) . 111 INFORMATION TECHNOLOGY - REMOTE OPERATIONS: OS1 REALIZATIONS - REMOTE OPERATIONS SERVICE ELEMENT (ROSE) PROTOCOL S

15、PECIFICATION AMENDMENT 1 Mapping to A-UNIT-DATA and buiit-in operations 1) Clause 1 Rewrite the third sentence of the first paragraph as follows (with the changes underlined): The ROSE services, defined in IT-T Rec. X.881 I ISO/IEC 13712-2, are provided in conjunction with the Association Control Se

16、rvice Element (ACSE) services (ITU-T Rec. X.217 I ISO/IEC 8649) and the ACSE protocol (ITU-T Rec. X.227 I ISO/IEC 8650-1 and ITU-T Rec. X.237 1 ISO/IEC 10035-11, optionally the Reliable Transfer Service Element (RTSE) services (ITU-T Rec. X.218 1 ISODEC 9066-1) and the RTSE protocol (ITU-T Rec. X.22

17、8 1 ISO/IEC 9066-2), and the Presentation service (IT-T Rec. X.216 I ISOAEC 8822 ). 2) Subclause 2.1 Add the following references: - ITU-T Recommendation X.237 (1995) 1 ISO/IEC 10035-1:1995, Information technology - Open Systems Interconnection - Connectionless protocol for the Association Control S

18、ervice Element: Protocol specgcation. ITU-T Recommendation X.880 (1994)/Amd.l (1995) I ISO/IEC 13712-1:1995/Amd.l:1996, Information technology - Remote Operations: Concepts, model and notation - Amendment I: Built-in operations. ITU-T Recommendation X.881 (1994)/hd.l (1995) I ISO/IEC 13712-2:1995/Am

19、d.1:1996, Information technology - Remote Operations: OSI realizations - Remote Operations Service Element (ROSE) service definition -Amendment 1: Mapping to A-UNIT-DATA and built-in operations. - - 3) Subclause 6.2 Rewrite the last paragraph as follows (with additions underlined and deletions struc

20、kthrough): Two specific association realizations are included, one based upon ACSE and one on RTSE. Pue- specific transfer realizations are included, based respectively on the use of P-DATA, A-UNIT-DATA and RT-DATA to transfer the APDUs. ITU-T Rec. X.882 (1994)/Amd.l (1995 E) 1 IPN= 4862591 0691408

21、352 41 3UUEllUSt: 0.3 Replace the existing Figure I with the following figure: a O of v Basic ROPM - - .r ml ROSE Built-in F supporting ASEs Basic ROPM v - a - ASE ROSE Built-in operations T - ASE CI. - ASE - C - ASE PRESENTATION-SERVICE PROVI DER a - ASE -ASE ASE providing infmation transfer ROPM R

22、emote Operations protocol machine ASE providing association establishment and release 0 -ASES OperatiOn-SpeCifiC ASES Figure 1 - Protocol model 5) Clause 8 Change clause 8 to 9, and similarly for all subclauses contained therein. Add the following new clause 8: 8 Built-in operations 8.1 Probe and ac

23、knowledge If the probe or acknowledge operation is included in the application context, then a ROPM, having sent a ReturnResult or RetunBrror APDU for a non-idempotent operation retains that APDU until it has been acknowledged. While retained, that APDU is re-sent if a probe takes place during that

24、period. As a local matter, the APDU may also be re-sent periodically. A retained ReturnResuit or ReturnError APDU is considered acknowledged, and can be deleted, if: a) b) c) the operation to which the retained APDU was a reply is synchronous, and a synchronous operation is subsequently invoked by t

25、he same invoker; or the acknowledge operation is invoked by the same invoker, citing the operation invocation to which the operation invocation to which the retained APDU was the return; or having re-sent the APDU, a Reject APDU is received, citing the operation invocation to which the retained APDU

26、 was the return, and indicating, if the retained APDU was a ReturnResult, returnResult : resultResponseUnexpected or, if the retained APDU was a ReturnError, returnError : errorResponseUnexpected. 2 IT-T Rec. X.882 (1994)/Amd.l(1995 E) IPN= 4862591 0691 409 299 a) if the operation to which the recei

27、ved APDU was a reply is synchronous, by subsequently invoking a synchronous operation; or by invoking the acknowledge operation, citing the operation invocation to which the received AFDU was a return. The acknowledge operation, which is idempotent, can be invoked repeatedly until it produces a resu

28、lt. b) TWSFER user-data 6) Clause 9 A-UNIT-DATA User information Renumber clause 9 as 1 O. and similarly for all subclauses contained therein. Renumber subclause 9.1 as 10.1 and modifv the first paragraph as shown below (with additions underlined and deletions struckthrough): A transfer realization

29、may require the inclusion in the application context of an ASE which provides services for the transfer of information. Alternatively, the realization may involve direct use of the presentation service. The realization may require a number of supporting ASES to be present. %vem transfer realizations

30、 are specified in this clause. The P-DATA realization is specified in %?u, and uses the connection-oriented services of the Presentation service directly. The A-UNIT-DATA realization uses the connectionless-mode OS1 uuuer laver services and is specified in 10.3. The RT-TRANSFER realization is Specif

31、ied in Mu. Renumber 9.2 as 10.2. Renumber 9.3 as 10.4. 7) Subclause 9.3.2 Renumber the existing Table 18 as Table 19. 8) Clause 10 Add a new subclause 10.3 as shown below: 10.3 103.1 103.2 1033 103.4 A-UMT-DAT A This subclause specifies a transfer realization employing the A-UNIT-DATA service of ACS

32、E. The TMSFER service assumed by ROSE is provided as shown in Table 18. Table 18 - Actual transfer primitives for the A-UNIT-DATA realization Pseudo-primitive Actual pnmitive(s) This realization imposes a maximum size of the APDU which can be transferred. NOTE - The value of this maximum size is for

33、 further study. This realization permits several TRANSFER requests arising close to one another in time to be combined into a single A-UNIT-DATA request. Each TRANSFER request conveys a single ROSE AFDU, a presentation data value (PDV). The A-WT-DATA carries all the concatenated PDVs. IT-T Rec. X.88

34、2 (1994)/Amd.l(1995 E) 3 IPN= 4862591 0691 41 O TOO 1vd.a iiic icaiiLauui1 pcLiilcu u1 us auuuauac cia11 uc iiiuuucu aa uic oiiacnciuuaiuii 111 “I ml APPLICATION-CONTEXT by referencing the definition aunitData: aunitData REALIZATION := RealjzationParameter (WITH COMPONENT (realization-type(transfer-

35、sedce) IDENTIFIED BY (joint-iso-ccitt associationcontrol(2) abstract-syntax(1) apdus(1) version(1) ROPM binding state 9) Clause 10 Renumber clause 1 O as clause 11 and similarly for all its subclames. ROPM operating state 10) Clause 11 Renumber clause 11 as clause 12. Renumber 11.1 as subclause 12.

36、I, and modh as fillows (with additions underlined and deletions struckthrough): An implementor shall state the following: a) the application context for which conformance is claimed, including whether the system supports the mapping of ROSE onto RTSE, onto the Presentation service, or A-UNIT-DATA or

37、 be or the acknowledge operation is invoked by the same invoker, citing the operation invocation to which the operation invocation to which the retained APDU was the return; or having re-sent the APDU, a Reject APDU is received, citing the operation invocation to which the retained APDU was the retu

38、rn, and indicating, if the retained APDU was a ReturnResult, returnResult : resultResponseUnexpected or, if the retained APDU was a ReturnError, returnError : errorResponseUnexpected. 2 ITU-T Rec. X.882 (1994)/Amd.l(1995 E) ISO/IEC 13712-3 : 1995/Amd.l : 1996 (E) TRANSFER user-data If probe or ackno

39、wledge is included in the application context, then an ROPM having received a ReturnResult or ReturnError APDU for a non-idempotent operation shall acknowledge such receipt either: a) if the operation to which the received APDU was a reply is synchronous, by subsequently invoking a synchronous opera

40、tion; or by invoking the acknowledge operation, citing the operation invocation to which the received APDU was a return. The acknowledge operation, which is idempotent, can be invoked repeatedly until it produces a result. b) A-UNIT-DATA User information 6) Clause 9 Renumber clause 9 as 1 O, and sim

41、ilarly for all subclauses contained therein. Renumber subclause 9.1 as 10.1 and modfy the first paragraph as shown deletions struckthrough): ?low (with additions underlined and A transfer realization may require the inclusion in the application context of an ASE which provides services for the trans

42、fer of information. Alternatively, the realization may involve direct use of the presentation service. The realization may require a number of supporting ASES to be present. %vem transfer realizations are specified in this clause. The P-DATA realization is specified in %u, and uses the connection-or

43、iented services of the Presentation service directly. The A-UNIT-DATA realization uses the connectionless-mode OS1 upper layer services and is specified in 10.3. The RT-TRANSFER realization is specified in Mu. Renumber 9.2 as 10.2. Renumber 9.3 as 10.4. 7) Subclause 9.3.2 Renumber the existing Table

44、 18 as Table 19. 8) Clause 10 Add a new subclause 10.3 as shown below: 10.3 A-UNIT-DATA 10.3.1 10.3.2 This subclause specifies a transfer realization employing the A-UNIT-DATA service of ACSE. The TRANSFER service assumed by ROSE is provided as shown in Table 18. Table 18 - Actual transfer primitive

45、s for the A-UNIT-DATA realization Pseudo-primitive Actual primitive( s) 10.3.3 This realization imposes a maximum size of the APDU which can be transferred. NOTE The value of this maximum size is for further study. 10.3.4 This realization permits several TRANSFER requests arising close to one anothe

46、r in time to be combined into a single A-UNIT-DATA request. Each TRANSFER request conveys a single ROSE APDU, a presentation data value (PDV). The A-UNIT-DATA carries all the concatenated PDVs. IT-T Rec. X.882 (1994)/Amd.l (1995 E) 3 ISO/IEC 13712-3 : 1995/Amd.l : 1996 (E) RO-RESU LT RO-ERROR RO-REJ

47、ECT RO-BIND RO-UNBI ND services 10.3.5 The realization specified in this subclause can be included as the b) No Connection package involved Figure A.l- Components of the ROPM state 4 ITU-T Rec. X.882 (1994)/Amd.l(1995 E) ISO/IEC 13712-3 : 1995/Amd.l : 1996 (E) Abbreviated name TAUO 1 TAU02 12) Subcl

48、ause A.4 Modify the itemized list of tables at the end of A.4 as follows (with additions underlined, and deletions struckthrough): AS Transfer state table - A-UNIT-DATA realization MM Transfer state table - RT-TRANSFER realization Name and description inactive active 13) Subclause A.5 Add the follow

49、ing new tables numbered A.5 and renumber existing Table A.5 as A.6: Abbreviated name TRANSind PDV Table A.5(q - Transfer state - A-UNIT-DATA realization Target Name and description primary TRANSFER indication ACSE PDV carried on an A-UNIT-DATA request Name and description I Source I I Abbreviated name TRANSreq PDV start stop primary ACSE association association TRANSFER request PDV carried within an A-UNIT-DATA indication. start the transfer state machine stop the transfer state machine Table A.S(ST) - Transfer state - A-UNIT-DATA realization Table