1、STDmITU-T RECMN X-730-ENGL 1978 rair 48b259L Ob57070 bT2 RII INTERNATIONAL TELECOMMUNICATION UNION ITUWT TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.930 (09/98) SERIES X: DATA NETWORKS AND OPEN SYSTEM COM M U N I CATI ON S Open distributed processing Information technology - Open distributed p
2、rocessing - Interface references and binding ITU-T Recommendation X.930 (Previously CCITT Recommendation) STD-ITU-T RECMN X-930-ENGL 3978 m Yb2573 Ob5707L 539 D PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenance Administrative a
3、rrangements OPEN SYSTEMS INTERCONNECTION Model and notation Service definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing General Satellite data transmission
4、systems MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS i INTERWORKING BETWEEN NETWORKS Networking Efficiency Quality of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN. i) Systems Management framework and architecture Management Communication Servi
5、ce and Protocol Structure of Management Information Management functions and ODMA functions OS1 MANAGEMENT SECURITY OS1 APPLICATIONS Commitment, Concurrency and Recovery ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS X. 1 -X. 19 X.20-X.49 X.50-X.89 X.90-X. 149 X. 150-X.
6、179 X.180-X. 199 X.200-X.209 X.210-X.219 X .220-X .229 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.349 X.350-X.399 X.400-X.499 X.500-X.599 X.600-X.629 X.630-X.639 X.640-X.649 X.650-X.679 X.680-X.699 X.700-X.709 X.7 10-X.719 X.720-X.729 X.730-X.799 X.800-X. 849 X.8
7、50-X.859 X.860-X.879 Remote operations X.880-X.899 Il For further details, please refer to ITU-T List of Recommendations. STDmITU-T RECMN X.930-ENGL L778 I 48b257L Ob57072 Y75 I INTERNATIONAL STANDARD 14753 ITU-T RECOMMENDATION X.930 INFORMATION TECHNOLOGY - OPEN DISTRIBUTED PROCESSING - INTERFACE R
8、EFERENCES AND BINDING Summary Interface references are crucial to interworking between ODP systems and federation of groups of ODP systems. An interface reference embodies the information needed to establish bindings, including binding to objects in different management domains. An interface referen
9、ce further embodies information required for the engineering mechanism to maintain computational bindings in the presence of distribution transparencies, such as migration transparency. (Example: keywords to keep include “engineering mechanism“, “computational binding“, “information“, and “distribut
10、ion transparency“.) This Recommendation I International Standard includes: a framework for binding interfaces and a generic binding protocol (for both stream and operational interfaces); a specification of the generic information structure of interface references (for both stream and operational int
11、erfaces); representation(s) for interface references when transferred using standardized protocols; identification of procedures for the management and transfer of interface references with respect to individual transparencies; identification of node management interfaces related to binding and fede
12、ration which create or transform interface references. 0 Source The ITU-T Recommendation X.930 was approved on the 25th of September 1998. The identical text is also published as ISO/IEC International Standard 14753. ITU-T Rec. X.930 (1998 E) 1 FOREWORD ITU (International Telecommunication Union) is
13、 the United Nations Specialized Agency in the field of telecommuni- cations. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to st
14、andardizing 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
15、by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administr
16、ation“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Prope
17、rty Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU had not received no
18、tice of intellectual property;protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1999 I All rights reserved. No
19、 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. 11 ITU-T Rec. X.930 (1998 E) CONTENTS 1 2 3 4 5 6 7 8 Scope and Field of application . 1.1 Scope . 1.2 Fiel
20、d of Application References 2.1 Identical Recommendations I Intemational Standards . 2.2 Specifications of the Object Management Group Definitions 3.1 Definitions in this Recommendation I International Standard . 3.2 Definitions from other Recommendations I International Standards . Abbreviations .
21、Conventions Overview of interface references and binding 6.1 Rationale 6.2 Overview ofthe binding process . 6.2.1 Obtaining interface references . 6.2.2 Binding process . Negotiating the properties of the binding Renegotiating the properties of the binding Quality monitoring and control . 6.2.6 Dest
22、roying a binding . 6.2.3 6.2.4 6.2.5 Enterprise viewpoint . 7.1 7.2 7.3 7.4 7.5 Communities . Roles 7.2.1 Binding initiator 7.2.2 Unbinding initiator 7.2.3 Binding controller . 7.2.4 Target interface creator . 7.2.5 Target interface . 7.2.6 Binding factory 7.2.7 Binding liaison 7.2.8 Channel Activit
23、ies . 7.3.1 Interface creation . 7.3.2 Binding 7.3.3 Unbinding 7.3.4 Binding management . 7.3.5 Event notification Policies Rules Information viewpoint 8.1 Binding contract 8.2 Environment contracts . 8.3 Binding type 8.4 Channel type 8.5 Channel template . 8.6 Interface references . 8.6.1 General i
24、nterpretation 8.6.2 Definition of structures 8.6.3 Definition of fields 8.6.4 Structuring interface types . 8.6.5 Reducing the size of the interface reference representation IT-T Rec . X.930 (1998 E) Page 1 1 1 1 2 2 2 2 2 3 4 4 4 4 4 5 5 5 5 6 6 6 6 6 6 6 6 7 7 7 7 7 7 7 8 8 8 8 9 9 11 11 11 11 11
25、12 12 13 13 15 16 . 111 . . STD-ITU-T RECMN X-930-ENGL 1798 I 48b259L Ob57075 184 II Puge 8.7 Schemata . 8.7.1 Invariant schemata . 8.7.2 Static schemata 8.6.3 Dynamic schemata . 9 Computational Viewpoint . 9.1 9.2 9.3 9.4 9.5 9.6 9.7 9.8 Computational activities related to binding . Binding establi
26、shment . 9.2.1 Notations . Channel establishment . Channel optimizations . 9.4.1 Pre-allocation of channel resources . 9.4.3 9.4.4 9.2.2 Binding protocol 9.4.2 Re-binding . Use of recursive binding . Reducing amount of interface reference related data Elimination of unnecessary channel components Se
27、curity Failures Functions 10 Federation . Transfer of interface references . 10.1 10.2 10.3 Name resolution and locating the endpoints of the binding Construction of the binding and resource allocation . 11 Compliance . A.l Direct interface references . A.3 Binding procedures . A.3.1 DIRECT A.3.3 NO
28、N-INTERPRETED-IN-OPAQUE-INFO with an interpreter which is within the ORB . A.3.4 NON-INTERPRETED-IN-OPAQUE-INFO with an interpreter which is a COMA object . A.4 Marshalling Annex A - Mapping of interface reference abstract syntax to CORBA IIOP-IOR format . A.2 Non-interpreted interface references .
29、A.3.2 NON-INTERPRETED-IN-OBJECT-KEY A.5 Unmarshalling . Annex B - Binding interpreter interface Annex C - Bibliography Annex D - Examples . : iv ITU-T Rec . X.930 (1998 E) 16 16 17 17 17 17 18 18 18 20 20 20 20 20 21 21 21 21 21 22 22 23 23 24 25 25 25 26 26 26 27 27 27 27 28 29 30 Introduction The
30、rapid growth of distributed processing has led to a need for a coordinating framework for the standardization of Open Distributed Processing (ODP). The Reference Model of ODP provides such a framework. It creates an architecture within which support of distribution, interworking and portability can
31、be integrated. One of the components of the architecture is the ODP binding function. The binding function provides the means to establish liaisons and create channels across autonomous systems in order to support interworking and communication between objects. An interface reference embodies the in
32、formation needed to establish bindings and further embodies the information required to maintain bindings between computational objects in the presence of distribution. ITU-T Rec. X.930 (1998 E) V STD-ITU-T RECMN X-930-ENGL 1998 48b259L Ob57077 T57 ISO/IEC 14753 : 1999 (E) INTERNATIONAL STANDARD ITU
33、-T RECOMMENDATION INFORMATION TECHNOLOGY - OPEN DISTRIBUTED PROCESSING - INTERFACE REFERENCES AND BINDING 1 Scope and Field of application 1.1 Scope Interface references are crucial to interworking between ODP systems and federation of groups of ODP systems. An interface reference embodies the infor
34、mation needed to establish bindings, including binding to objects at nodes that support several different communication protocols and binding to objects in different management domains. An interface reference further embodies the information required for the engineering mechanism to maintain binding
35、s between computational objects in the presence of distribution transparencies such as migration transparency. They are the foundation of ODP location and relocation transparency. This Recommendation I International Standard includes: 0 a fiamework for binding interfaces and a generic binding protoc
36、ol (for both stream and operational interfaces); 0 a specification of the generic information structure of interface references (for both stream and operational interfaces); representation(s) for interface references when transferred using standardized protocols; identification of procedures for the
37、 management and transfer of interface references with respect to individual transparencies; identification of node management interfaces related to binding and federation which create or transform interface references; 0 9 identification of requirements for quality of service information and for inv
38、ocation of QoS or related measurement procedures. This Recommendation I International Standard provides an engineering description of the functionality needed to support the computational binding of objects in ODP systems. Security and support for group communication are important issues, but not wi
39、thin the scope of this Recommendation I International Standard. 1.2 Field of Application This Recommendation I International Standard enables interworking between ODP systems. 2 References The following Recommendations and International Standards contain provisions which, through reference in this t
40、ext, constitute provisions of this Recommendation I International Standard. At the time of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation I International Standard are encouraged to inve
41、stigate the possibility of applying the most recent edition of the Recommendations and Standards listed below. Members of IEC and IS0 maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of the currently valid ITU-T R
42、ecommendations. ITU-T Rec. X.930 (1998 E) 1 STDoITU-T RECMN X.9IO-ENGL 3778 111 4862571 Ob57078 993 II ISODEC 14753 : 1999 (E) 2.1 Identical Recommendations I International Standards - ITU-T Recommendation X.901 (1997) I ISO/IEC 10746-1:199 - template; - action; - activity; - behaviour; - binding; -
43、 compliance; - configuration; - conformance point; - contract; To be published. 2 ITU-T Rec. X.930 (1998 E) STD.ITU-T RECMN X.930-ENGL 1998 m 4b2591 b57079 82T ISOBEC 14753 : 1999 (E) - contractual context; - distribution transparency; - environment contract; - epoch; - failure; interaction point; i
44、nterface; interworking reference point; liaison; location; notification; policy; quality of service; role; subtype; type (of an X). This Recommendation I International Standard makes use of the following terms defined in ITU-T X.903 I ISO/IEC 10746-3: federation; announcement; basic engineering obje
45、ct; binder; channel; compound binding; engineering interface reference; explicit binding; implicit binding; interceptor; node; operation interface; protocol object; signal; signature; stub; - stream interface. 4 Abbreviations For the purpose of this Recommendation I International Standard the follow
46、ing abbreviations apply: QOS Quality of Service ODP Open Distributed Processing IIOP-IOR Internet Inter-ORB Protocol - Interoperable Object Reference 3 ITU-T Rec. X.930 (1998 E) 5 Conventions The following conventions are specific to this Recommendation I Intemational Standard. In diagrams: objects
47、are represented as ovals or circles; 0 the symbol 1 protruding from an object represents an interface; the symbol 0 represents a containment of objects; the symbol represents dependent containment between objects; 0 the symbol n * denotes that the cardinality of an association must exceed n. 6 Overv
48、iew of interface references and binding 6.1 Rationale The objective of ODP standardization is to develop standards that realize the benefits of distributing information processing services in a heterogeneous environment of IT resources and multiple organizational domains. These standards address con
49、straints on system specifications and provide a system infrastructure that addresses difficulties inherent in the design and programming of distributed systems. Distributed systems are important because of a growing need to interconnect information processing systems. This need arises because of organizational trends (such as downsizing), which demand the exchange of information not only between groups within an organization but also between cooperating organizations. Technological advances make it possible to respond to these trends giving increased importance to info
