1、STD-ITU-T RECMN Xeb39-ENGL L97b 4Ab2571 Ob278q3 127 W INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.639 (1 0/96) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATION OS1 networking and system aspects - Efficiency Basic connection-oriented requirements
2、 for ROSE-based profiles ITU-T Recommendation X.639 (Previously CCITT Recommendation) STD-ITU-T RECMN X=b37-ENGL L97b = 48b257L Ob27844 Ob3 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATION PUBLIC DATA NETWORKS X.l-X.199 Services and facilities X.1-X.19 X.20-X.49 Transmissio
3、n, signalling and switching X.50-X.89 X.90-X. 149 X.150-X.179 X. 1 80-X. 199 OPEN SYSTEM INTERCONNECTION X.200-X.299 Model and notation X.200-X.209 Service definitions X.210-X.219 Connection-mode protocol specifications X.220-X.229 Connectionless-mode protocol specifications X.230-X.239 X.240-X.259
4、Protocol Identification X.260-X.269 Security Protocols X.270-X.279 Layer Managed Objects X.280-X.289 Conformance testing X.290-X.299 INTERWORKING BETWEEN NETWORKS X.300-X.399 X.300-X.349 Administrative arrangements Satellite data transmission systems x.350-x.399 MESSAGE HANDLING SYSTEMS x.400-x.499
5、DIRECTORY x.500-x.599 Abstract Syntax Notation One (ASN. 1) X.680-X.699 OS1 MANAGEMENT X.700-X.799 Systems Management framework and architecture X.700-X.709 Management Communication Service and Protocol X.7 10-X.719 Structure of Management Information X.720-X.729 SECURITY X.800-X.849 OS1 APPLICATION
6、S X.850-X.899 Commitment, Concurrency and Recovery X.850-X.859 Transaction processing X.860-X.879 Remote operations X.880-X.899 OPEN DISTRIBUTED PROCESSING x.900-x.999 Management functions x.730-x.799 Forfirther details, please refer to ITU-TList of Recommendations. STD-ITU-T RECMN Xmb39-ENGL L97b 4
7、8b257L Ob27845 TTT FOREWORD The ITU-T (Telecommunication Standardization Sector) is a permanent organ of the International Telecommunication Union (IT). The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommen- dations on them with a view to standardizing
8、telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Membe
9、rs of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1 (Helsinki, March 1-12, 1993). IT-T Recommendation X.639 was prepared by IT-T Study Group 7 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 5th of October 1996. NOTE In this Recommendation, th
10、e expression “Administration” is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. O IT 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 photo
11、copying and microfilm, without permission in writing from the ITU. Recommendation X.639 (10/96) i STD-ITU-T RECMN XDb39-ENGL L97b 48b257L Ob2784b 73b CONTENTS Scope 1.1 General 1.2 Scenario Normative references . 2.1 2.2 2.3 Additional references Definitions 3.1 Support level . Abbreviations . Ident
12、ical ITU-T Recommendations I International Standards Paired Recommendations I International Standards equivalent in technical content Remote Operations Service Element (ROSE) Presentation layer . Session layer Association Control Service Element (ACSE) . Compliance 9.1 Compliance statement . 9.2 9.3
13、 Relationship with Recommendation X.638 Relationship with base standards Annex A . Profile Requirements Lists for ROSE. ACSE. Presentation and Session . A.l General A.2 References A.4 AS ROSE PRL A.6 ACSE PRL A.7 Presentation PRL A.8 Session PRL A.9 List of conditional statements . Annex B - Profile
14、 ICs Proforma for ROSE implementations B.l General B.2 Classification of requirements B.3 Supported roles . B.4 Support of BiNDhJNBIND parameters . A.3 Classification of requirements Value of the Role-Variables used in Annex A, B and C of Recommendation X.638 . Page 1 1 1 1 2 2 2 2 3 3 3 3 3 3 5 5 5
15、 6 6 6 6 6 7 8 8 8 8 8 9 9 9 9 9 B.5 Support of Operations . 10 11 Recommendation X.639 (10196) - STD-ITU-T RECMN X-bI7-ENGL L77b L18b257L 0b278L17 872 SUMMARY This Recommendation describes the common upper layer requirements above and beyond those specified in Recommendation X.637 to support ROSE-b
16、ased profiles which do not use the services of the RTSE. These common elements are specified by reference to the OS1 connection-mode Recommendations for the ROSE protocol, the ACSE protocol, the Presentation layer protocol and the Session layer protocol. This is one of a series of Recommendations to
17、 support the minimal OS1 functions in the upper layers. It is technically aligned with ISO/IEC ISP 11 188-2. . Recommendation X.639 (10196) 111 - STD-ITU-T RECMN Xmb39-ENGL 1996 LiAb2.591 Ob27848 707 Recommendation X.639 ACSE I ROSE Presentation Session BASIC CONNECTION-ORIENTED REQUIREMENTS FOR ROS
18、E-BASED PROFILES ACSE 1 ROSE Presentation Session (Geneva, 1996) 1 1.1 Thi Scope General Recommendation specifies the common upper 1 yer elements f ROSE-b sed A-profiles, which do not use RTSE. It documents ROSE-specific upper layer requirements -over and above the common upper layer requirements sp
19、ecified in Recommendation X.638. The common elements are specified by reference to OS1 connection-mode standards for the ROSE protocol, the ACSE protocol, the presentation layer protocol, and the session layer protocol. A specification defining a ROSE-based A-profile may reference Recommendation X.6
20、38 and this Recommendation as the common basis for the selection of elements of the upper layer protocols (ROSE, ACSE, presentation and session) that it uses. The use of this Recommendation is supplemented by a statement of the referencing specifications specific upper layer requirements for the use
21、 of ROSE, ACSE, presentation and session protocol standards. The rest of an A-profile definition, including, for instance, its use of standards for Application Service Elements (ASE, see also Figure 1), follows the general rules of ISO/IEC TR 10 000-1. 1.2 Scenario The model used is one of two-end s
22、ystems running an end-to-end association using the ROSE, ACSE, presentation and session services and protocols (see Figure 1). FIGURE 1K.639 Model of the supportive layers for ROSE-based ASES 2 Normative references The following Recommendations and other references contain provisions which, through
23、reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision: all users of this Recommendation are therefore encouraged to investigate the possibility of applying
24、the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. Recommendation X.639 (1 0196) 1 STD-ITU-T RECMN Xmb37-ENGL L77b = iBb259L Ob27850 3b7 2.1 Identical ITU-T Recommendations I International Stan
25、dards - ITU-T Recommendation X.225 (1995) 1 ISOAEC 8327-1:1996, Information technology - Open Systems Interconnection - Connection-oriented session protocol: Protocol specification. ITU-T Recommendation X.226 (1994) I ISOAEC 8823-1:1994, Information technology - Open Systems Interconnection - Connec
26、tion-oriented presentation protocol: Protocol specification. ITU-T Recommendation X.227 (1995) 1 ISOAEC 8650-1:1996, Information technology - Open Systems Interconnection - Connection-oriented protocol for the association control service element: Protocol specification. IT-T Recommendation X.245 (19
27、95) I ISOflEC 8327-2:1996, Information technology - Open Systems Interconnection - Connection-oriented session protocol: Protocol Implementation Conformance State- ment (PICS) proforma. ITU-T Recommendation X.246 (1996) I ISOAEC 8823-2:1997, Information technology - Open Systems Interconnection - Co
28、nnection-oriented presentation protocol: Protocol Implementation Conformance Statement (PICS) proforma. ITU-T Recommendation X.247 (1996) I ISOAEC 8650-2:1997, Information technology - Open Systems Interconnection - Protocol specifcation for the association control service element: Protocol Implemen
29、tation Conformance Statement (PIC$) proforma. - - - - - 2.2 Paired Recommendations I International Standards equivalent in technical content - CCITT Recommendation X.219 (1988), Remofe operations: Model, notation and service definition. ISOLIEC 9072- 1: 1989, Information processing systems - Text co
30、mmunication - Remote Operations - Part 1: Model, notation and service definition. CCITT Recommendation X.229 (1988), Remote operations: Protocol specifcation. ISO/IEC 9072-2: 1989, Information processing systems - Text communication - Remote Operations - Part 2: Protocol specification. ITU-T Recomme
31、ndation X.637 (1 996), Basic connection-oriented common upper layer requirements. ISOAEC ISP 1 11 88-1:1995, Information technology - International Standardized Profile - Common upper layer requirements - Part 1: Basic connection oriented requirements. ITU-T Recommednation X.638 (1996), Minimal OSI
32、facilities to support basic communications applications. ISOAEC ISP 1 1188-3:1996, Information technology - International Standardized Profile - Common upper layer requirements - Part 3: Minimal OSI upper layer facilities. - - - 2.3 Additional references - ISOLIEC 9072-41, Information technology - R
33、emote Operations Service Element (ROSE) - Part 4: Protocol Implementation Conformance Statement (PICS) proforma. NOTE - This Recommendation makes detailed references to subciauses of the specified editions of some of the above references. 3 Definitions The definitions in IT-T Recommendation X.638 ar
34、e also valid for this Recommendation. 1) Presently at the stage of cirafi. 2 Recommendation X.639 (10/96) STD-ITU-T RECMN X=b37-ENGL L77b VBb259L Ob27851 2T3 B 3.1 Support level To speciQ the support level of protocol features for this Recommendation the following terminology is defined: Column 1 of
35、 Table 1 lists the support level identifiers for a profile used in this Recommendation; Column 2 of Table 1 defines the use of these requirements classifications of column 1 by a referencing specification; a) b) c) Column 3 of Table 1 defines the use of the requirements classifications by an impleme
36、ntation. 4 Abbreviations in addition to the abbreviations defined in Recommendation X.638, the following abbreviations are used in this Recommendation. ROSE Remote Operations Service Element RTSE Reliable Tranfer Service Element Support level for protocol features: m supported o optionally supported
37、 * open x excluded c conditionally supported i outofscope - not applicable 5 Remote Operations Service Element (ROSE) The support of functions and parameters for the Remote Operations Service Element is as specified in AS and in the Specific Upper Layer Requirements section of the referencing specif
38、ication. 6 Association Control Service Element (ACSE) The support of functions and parameters for the Association Control Service Element is as specified in A.6 and in the Specific Upper Layer Requirements section of the referencing specification. 7 Presentation layer I The support of functions and
39、parameters for the presentation protocol is as specified in A.7 and in the Specific Upper Layer Requirements section of the referencing specification. 8 Session layer The support of functions and parameters for the session protocol is as specified in A.8 and in the Specific Upper Layer Requirements
40、section of the referencing specification. Recommendation X.639 (10/96) 3 1 Meaning when referenced by a specification Identifier 2 Meaning when referenced by an implementation m - O Mandatory - The feature shall be required for support. The status of the feature shall remain mandatory in a referenci
41、ng specification (Note). Optional - The choice of whether this feature is supported or it is not supported is made by the implementation. The status of the feature shall remain optional in a referencing specification. Open -The status of this feature shall be decided by the referencing specification
42、. The referencing specification shall indicate that the status of the feature is mandatory, optional, or out of scope. Alternately, the referencing specification may keep the feature open. Excluded - The feature shall not be used in a referencing specification. The status of the feature shall remain
43、 excluded in a referencing specification. Mandatory -The implementation shall support the feature, i.e. its syntax and procedures shall be implemented as specified in the base standard or in this Recommendation. However, it is not a requirement that the feature shall be used in all instances of comm
44、unication unless mandated by the base standard or stated otherwise in this Recommendation. The feature shall be the subject of an ISP conformance test (Note). Optional -The implementation may decide either to support or to not support the feature. Supporting a feature means that the feature shall be
45、 handled as if it was mandatory. Not supporting a feature depends on receiving or sending : For sending, the features capability is not used; For receiving an optional parameter, the syntax shall be implemented and the parameter may be ignored. The feature shall be the subject of an ISP conformance
46、test. * Not applicable -The feature is not relevant where mentioned in a table. Support for the feature is either meaningless, logically impossible, or physically impossible, after some conditions are evaluated. The status of the feature shall remain not applicable in a referencing specification. Co
47、nditionally supported - Support for the feature is further defined in this Recommendation by condition (“n”) annexed to the table. The value evaluated from the condition evaluates to one of the following values defined in this Table: “m”; “o”; “ 39 i ,or “-”. X Si Open - same as optional. Excluded -
48、The implementation shall not support the feature. When completing the associated PICS Proforma table, the answer for the support column shall be that the feature has not been implemented. The implementation shall abort if the feature is received. The exclusion should be the subject of an ISP conform
49、ance test. Out of scope - The requirement for the support of this feature is not covered by this Profile. The status of the feature shall remain out of scope in a referencing specification. Out of scope - Support for a feature shall follow the guidelines outlined for optional above with the exception that this feature shall not be the subject of an ISP conformance test. Not applicable - The feature is not defined by the base standard in the context where it is mentioned in a table. A support answer is not required from the implementor. Condition
