BS ISO IEC 14753-1999 Information technology - Open distributed processing - Interface references and binding《信息技术 开放式分布型处理系统 界面基准和绑定》.pdf

《BS ISO IEC 14753-1999 Information technology - Open distributed processing - Interface references and binding《信息技术 开放式分布型处理系统 界面基准和绑定》.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC 14753-1999 Information technology - Open distributed processing - Interface references and binding《信息技术 开放式分布型处理系统 界面基准和绑定》.pdf（42页珍藏版）》请在麦多课文档分享上搜索。

1、BRITISH STANDARD BS ISO/IEC 14753:1999 Information technology Open Distributed Processing Interfacereferences and binding ICS 35.100.01BSISO/IEC 14753:1999 This British Standard, having been prepared under the directionof the DISC Board, waspublished under the authorityof the Standards Committee and

2、 comes into effect on 15October1999 BSI 04-2000 ISBN 0 580 35327 3 National foreword This British Standard reproduces verbatim ISO/IEC14753:1999 and implements it as the UK national standard. The UK participation in its preparation was entrusted to Technical Committee IST/15, Software Engineering, w

3、hich has the responsibility to: aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep the UK interests informed; monitor related international and European developments and promulgate t

4、hem in the UK. A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international or European publications referred to in this document may be found in the BSI Standards Catalogue under the section e

5、ntitled “International Standards Correspondence Index”, or by using the “Find” facility of the BSI Standards Electronic Catalogue. A British Standard does not purport to include all the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Comp

6、liance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, theISO/IEC title page, pages ii to vi, pages 1 to 31, and a back cover. This standard has been updated (see copyrig

7、ht date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Amendments issued since publication Amd. No. Date CommentsBSISO/IEC14753:1999 BSI 04-2000 i Contents Page National foreword Inside front cover Foreword iv Text of ISO/IEC 14753

8、 1ii blankBSISO/IEC 14753:1999 ii BSI 04-2000 Contents Page Foreword iv Introduction vi 1 Scope and Field of application 1 1.1 Scope 1 1.2 Field of Application 1 2 References 1 2.1 Identical Recommendations|International Standards 2 2.2 Specifications of the Object Management Group 2 3 Definitions 2

9、 3.1 Definitions in this Recommendation|International Standard 2 3.2 Definitions from other Recommendations|International Standards 2 4 Abbreviations 3 5 Conventions 4 6 Overview of interface references and binding 4 6.1 Rationale 4 6.2 Overview of the binding process 4 6.2.1 Obtaining interface ref

10、erences 4 6.2.2 Binding process 5 6.2.3 Negotiating the properties of the binding 5 6.2.4 Renegotiating the properties of the binding 5 6.2.5 Quality monitoring and control 5 6.2.6 Destroying a binding 6 7 Enterprise viewpoint 6 7.1 Communities 6 7.2 Roles 6 7.2.1 Binding initiator 6 7.2.2 Unbinding

11、 initiator 6 7.2.3 Binding controller 6 7.2.4 Target interface creator 6 7.2.5 Target interface 7 7.2.6 Binding factory 7 7.2.7 Binding liaison 7 7.2.8 Channel 7 7.3 Activities 7 7.3.1 Interface creation 7 7.3.2 Binding 7 7.3.3 Unbinding 8 7.3.4 Binding management 8 7.3.5 Event notification 8 7.4 Po

12、licies 8 7.5 Rules 9 8 Information viewpoint 9 8.1 Binding contract 11 8.2 Environment contracts 11 8.3 Binding type 11 8.4 Channel type 11 8.5 Channel template 11 8.6 Interface references 12 8.6.1 General interpretation 12 8.6.2 Definition of structures 13BSISO/IEC14753:1999 BSI 04-2000 iii Page 8.

13、6.3 Definition of fields 13 8.6.4 Structuring interface types 15 8.6.5 Reducing the size of the interface reference representation 16 8.7 Schemata 16 8.7.1 Invariant schemata 16 8.7.2 Static schemata 17 8.7.3 Dynamic schemata 13 9 Computational Viewpoint 17 9.1 Computational activities related to bi

14、nding 17 9.2 Binding establishment 18 9.2.1 Notations 18 9.2.2 Binding protocol 18 9.3 Channel establishment 20 9.4 Channel optimizations 20 9.4.1 Pre-allocation of channel resources 20 9.4.2 Re-binding 20 9.4.3 Use of recursive binding 20 9.4.4 Elimination of unnecessary channel components 21 9.5 R

15、educing amount of interface reference related data 21 9.6 Security 21 9.7 Failures 21 9.8 Functions 21 10 Federation 22 10.1 Transfer of interface references 22 10.2 Name resolution and locating the endpoints of the binding 23 10.3 Construction of the binding and resource allocation 23 11 Compliance

16、 24 Annex A Mapping of interface reference abstract syntax to CORBA IIOP-IOR format 25 A.1 Direct interface references 25 A.2 Non-interpreted interface references 25 A.3 Binding procedures 26 A.3.1 DIRECT 26 A.3.2 NON_INTERPRETED_IN_OBJECT_KEY 26 A.3.3 NON_INTERPRETED_IN_OPAQUE_INFO with an interpre

17、ter which is within the ORB 27 A.3.4 NON_INTERPRETED_IN_OPAQUE_INFO with an interpreter which is a CORBA object 27 A.4 Marshalling 27 A.5 Unmarshalling 27 Annex B Binding interpreter interface 28 Annex C Bibliography 29 Annex D Examples 30 Index 31 Figure 1 Information viewpoint overview 10 Figure 2

18、 Binding protocol 19 Figure D.1 Example of binding stream interface 30 Table A.1 CORBA mapping of interface references 26BSISO/IEC 14753:1999 iv BSI 04-2000 Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized

19、system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committee

20、s collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3. In the field of informa

21、tion technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC1. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least75% of the national bodi

22、es casting a vote. International Standard ISO/IEC 14753 was prepared by Joint Technical Committee ISO/IEC JTC1, Information technology, Subcommittee SC7, Software engineering, in collaboration with ITU-T. The identical text is published as ITU-T Recommendation X.930. Annex A and Annex B form an inte

23、gral part of this International Standard. Annex C is for information only.v blankBSISO/IEC 14753:1999 vi BSI 04-2000 Introduction The rapid growth of distributed processing has led to a need for a coordinating framework for the standardization of Open Distributed Processing (ODP). The Reference Mode

24、l of ODP provides such a framework. It creates an architecture within which support of distribution, interworking and portability can 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 channel

25、s across autonomous systems in order to support interworking and communication between objects. An interface reference embodies the information needed to establish bindings and further embodies the information required to maintain bindings between computational objects in the presence of distributio

26、n.BSISO/IEC14753:1999 BSI 04-2000 1 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 information needed to establish bindings, including binding to objects at n

27、odes 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 bindings between computational objects in the presence of distribution transp

28、arencies such as migration transparency. They are the foundation of ODP location and relocation transparency. This Recommendation|International Standard includes: a framework for binding interfaces and a generic binding protocol (for both stream and operational interfaces); a specification of the ge

29、neric 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 management and transfer of interface references with respect to individual

30、transparencies; identification of node management interfaces related to binding and federation which create or transform interface references; identification of requirements for quality of service information and for invocation of QoS or related measurement procedures. This Recommendation|Internatio

31、nal 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 within the scope of this Recommendation|International Standard. 1.2 Field of Applica

32、tion This Recommendation|International Standard enables interworking between ODP systems. 2 References The following Recommendations and International Standards contain provisions which, through reference in this text, constitute provisions of this Recommendation|International Standard. At the time

33、of publication, the editions indicated were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this Recommendation|International Standard are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and Sta

34、ndards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of the currently valid ITU-T Recommendations.BSISO/IEC 14753:1999 2 BSI 04-2000 2.1 Identical Recommendations|Internatio

35、nal Standards ITU-T Recommendation X.901 (1997)|ISO/IEC 10746-1:1998, Information technology Opendistributed processing Reference Model: Overview. ITU-T Recommendation X.902 (1995)|ISO/IEC 10746-2:1996, Information technology Opendistributed processing Reference Model: Foundations. ITU-T Recommendat

36、ion X.903 (1995)|ISO/IEC 10746-3:1996, Information technology Opendistributed processing Reference Model: Architecture. ITU-T Recommendation X.910 (1998)|ISO/IEC 14771:1999, Information technology Opendistributed processing ODP Naming framework. ITU-T Recommendation X.931 (1998)|ISO/IEC 14752:1999,

37、Information technology Opendistributed processing Protocol Support for Computational Interactions. ITU-T Recommendation X.950 (1997)|ISO/IEC 13235-1:1998, Information technology Opendistributed processing Trading function: Specification. ITU-T Recommendation X.960 1) |ISO/IEC 14769 1) , Information

38、technology Open distributed processing Type repository function. ISO/IEC 9075-1, Information technology Database language SQL Part 1: Frame 1) . 2.2 Specifications of the Object Management Group CORBA: The Common Object Request Broker: Architecture and Specification, Revision 2.1, Object Management

39、Group, August1997 (OMG Doc Number Formal/97-09-01). TEMPORARY NOTEA reference explanatory report is circulated with the DIS ballot on this specification. 3 Definitions 3.1 Definitions in this Recommendation|International Standard This Recommendation|International Standard defines the following terms

40、. 3.2 Definitions from other Recommendations|International Standards This Recommendation|International Standard makes use of the following terms defined in ITU-T Rec. X.902|ISO/IEC10746-2: domain; template; action; activity; behaviour; binding; compliance; configuration; conformance point; contract;

41、 1) To be published.BSISO/IEC14753:1999 BSI 04-2000 3 contractual context; distribution transparency; environment contract; epoch; failure; interaction point; interface; interworking reference point; liaison; location; notification; policy; quality of service; role; subtype; type (of an X). This Rec

42、ommendation|International Standard makes use of the following terms defined in ITU-T X.903|ISO/IEC10746-3: federation; announcement; basic engineering object; binder; channel; compound binding; engineering interface reference; explicit binding; implicit binding; interceptor; node; operation interfac

43、e; protocol object; signal; signature; stub; stream interface. 4 Abbreviations For the purpose of this Recommendation|International Standard the following abbreviations apply: QoS Quality of Service ODP Open Distributed Processing IIOP-IOR Internet Inter-ORB Protocol Interoperable Object ReferenceBS

44、ISO/IEC 14753:1999 4 BSI 04-2000 5 Conventions The following conventions are specific to this Recommendation|International Standard. In diagrams: objects are represented as ovals or circles; the symbol “” protruding from an object represents an interface; the symbol “” represents a containment of ob

45、jects; the symbol “ ” represents dependent containment between objects; the symbol “n *” denotes that the cardinality of an association must exceed n. 6 Overview of interface references and binding 6.1 Rationale The objective of ODP standardization is to develop standards that realize the benefits o

46、f distributing information processing services in a heterogeneous environment of IT resources and multiple organizational domains. These standards address constraints on system specifications and provide a system infrastructure that addresses difficulties inherent in the design and programming of di

47、stributed 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 betw

48、een cooperating organizations. Technological advances make it possible to respond to these trends giving increased importance to information networks and personal workstations, and enabling distributed applications to be constructed across large configurations of interconnected systems. In order to

49、set up cooperation between organizations and their information systems, the parties must define and agree on a relationship and then maintain it. This relationship is often defined as a contract in commercial environments. To achieve cooperation between systems, after some initial contact, agreements must be made, contracts negotiated and interfaces defined, created and made available. Interworking