ITU-T X 703 AMD 1-1998 Information Technology - Open Distributed Management Architecture - Amendment 1 Support Using Common Object Request Broker Architecture (CORBA) - Series X DaOS.pdf

1、 STD-ITU-T RECMN X.703 AND 1-ENGL 1778 98b2571 Ob53780 O10 INTERNATIONAL TELECOMMUNICATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.703 Amendment 1 (06/98) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OS1 management - Systems Management framework and architecture Info

2、rmation technology - Open Distributed Management Architecture Amendment 1 : Support using Common Object Request Broker Architecture (CORBA) ITU-T Recommendation X.703 - Amendment 1 (Previously CCIlT Recommendation) STD-ITU-T RECMN X-703 AMD 1-ENGL 1778 = YBb257L Ob53781 T57 9 ITU-T X-SERIES RECOMMEN

3、DATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities Transmission, signalling and switching Administrative arrangements Model and notation X.200-X.209 Service definitions Connection-mode protocol specifications X.220-X.229 Connectionless-mode protocol spe

4、cifications Protocol Identification Security Protocols Layer Managed Objects Conformance testing OPEN SYSTEMS INTERCONNECTION INTERWORKING BETWEEN NETWORKS Satellite data transmission systems X.350-X.399 MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS X.630-X.639 Quality of serv

5、ice X.640-X.649 Naming, Addressing and Registration X.650-X.679 Abstract Syntax Notation One (ASN.l) Structure of Management Information Management functions and ODMA functions X.800-X.849 OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED

6、 PROCESSING For further details, please refer to ITU-T List of Recommendations. INTERNATIONAL STANDARD 13244 ITU-T RECOMMENDATION X.703 INFORMATION TECHNOLOGY- OPEN DISTRIBUTED MANAGEMENT ARCHITECTURE AMENDMENT 1 Support using Common Object Request Broker Architecture (CORBA) Source The IT-T Recomme

7、ndation X.703, Amendment 1, was approved on the 26th of June 1998. The identical text is also published as ISO/IEC International Standard 13244. ITU-T Rec. X.703 (1997)/Amd.l(1998 E) 1 FOREWORD IT (International Telecommunication Union) is the United Nations Specialized Agency in the field of teleco

8、mmuni- cations. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the . The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World T

9、elecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the IT-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down

10、 in WTSC Resolution No. 1. In some areas of information technology which fall within IT-T?s purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression ?Administration? is used for conciseness to indicate both a telecommunicati

11、on 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 Property Right. The ITU takes no position concerning the evidence, val

12、idity 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 notice of intellectual property, protected by patents, which may be

13、 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 1998 All rights reserved. No part of this publication may be reproduced or utilized in any for

14、m or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 ITU-T Rec. X.703 (1997)/Arnd.l(1998 E) CONTENTS Page 1) Clause 1 1 2) Clause 2 1 3) New subclause 2.3 1 4) Clause 4 2 5) New clause 8 . 2 6) New Annexes G and H 6 . ITU-T

15、 Rec. X.703 (1997)/Arnd.l(1998 E) iii ISO/IEC 13244 : 199WAmd.l: 1999 (E) INTERNATIONAL STANDARD ITU-T RECOMMENDATION INFORMATION TECHNOLOGY- OPEN DISTRIBUTED MANAGEMENT ARCHITECTURE AMENDMENT 1 Support using Common Object Request Broker Architecture (CORBA) 1) Clause 1 Update the scope clause to ch

16、ange potential amendment to amendment (in Figure 1). 2) Clause 2 Add a reference by alphanumerical order to the ODMA Noti,fication Selection and Dispatch Function: - ITU-T Recommendation X.770 (199x) I ISOAEC 15427-1:199x, Information technology - Open Distributed Management Architecture - Notificat

17、ion Selection and Dispatch Function 3) New subclause 2.3 Add a new subclause for PAS references: 2.3 Publicly available specification references All references in this subclause were correct at the time of approval of this Recommendation I International Standard. The provisions of the references spe

18、cifications, as identified in this subclause, are valid within the context of this Recommendation I International Standard. The reference to a specification within this Recommendation I International Standard does not give it any further status within ITU-T or ISODEC; in particular, it does not give

19、 the referenced specification the status of a Recommendation I international Standard. Temporary Note -A reference explanatory report is circulated with the DAM ballot on this specification. - CORBA: The Common Object Request Broker: Architecture and Spec$cation, Revision 2.1, Object Management Grou

20、p, August 1997 (OMG Doc Number: FormaU97-09-01). - CORBA Services: Common Object Services Specification, Object Management Group, November 1997 (OMG Doc Number: Fomal/97-12-02). - CORBA Facilities: Common Object Facilities Specification, Object Management Group, Revision 4, November 1995 (OMG Doc Nu

21、mber: FomaU97-06-15). ITU-T Rec. X.703 (1997)/Amd.l(1998 E) 1 STD-ITU-T RECMN X-703 AMD 1-ENGL 1778 = 48b2571 Ob5378b 537 = ISOIIEC 13244 : 199WAmd.l : 1999 (E) 4) Clause 4 Add the following abbreviations by alphabetical order: bmos base management-operation server DII Dynamic Invocation Interface G

22、IOP General Inter Orb Protocol IR Interface Repository JIDM OMG Object Management Group ORB Object Request Broker SNMP Simple Network Management Protocol WOpen - NMF Joint Inter-Domain Management 5) New clause 8 Add the following clause amendment text: 8 COBA support for ODMA Mechanisms to realize O

23、DMA systems are not unique, and there may be multiple approaches. OS1 Systems Management, as described in clause 7, is one approach. This clause describes another approach, using OMG CORBA. The OMG CORBA a distributed processing infrastructure. This clause describes how COMA can be used to support O

24、DMA. NOTE - OMG is a consortium recognized internationally as a major contributor to information technology. ODP IDL, as defined in IT-T Rec. X.920 I ICO/IEC 14750, is technically aligned with the OMG IDL defined in CORBA. It is envisaged that CORBA-based technology has the potential to progress dev

25、elopment in the following areas: - - CORBA isolates the engineer from the Operating System and language dependencies. The development of management systems can internally make substantial use of implementations of the currently defined CORBA Services and COBA Facilities. Facilitating interoperabilit

26、y between management systems. CORBA is a standard middleware component supporting programming language independent interface definition, standard language mappings, and has multi-vendor support. The publication of interfaces to application functions supported by management systems in ODP IDL should

27、facilitate interworking between such management systems. CORBA-based infrastructure may facilitate the development of purely COMA-based management systems with standard “off the shelf components. It is intended (where appropriate) to reuse the knowledge and specifications generated as a result of ac

28、tivities within traditional OS1 Systems Management. There is also a general realisation that many of the advantages offered by distributed object computing in general, and specifically by CORBA, will enhance the features of systems developed in this context. - - The enterprise and information viewpo

29、int descriptions of CORBA support for ODMA are the same as the corresponding enterprise and information viewpoint in clause 6, General framework. 8.1 Computational viewpoint The functions introduced by the ODMA should complement the more general CORBA services and CORBA facilities. The complete set

30、of service specifications will be fundamental to providing a framework for developing distributed telecommunications management applications. 8.1.1 CORBA managed objects In this subclause, the term “CORBA managed object“ is used to refer to a managed role computational object which is realized in a

31、CORBA environment. 2 ITU-T Rec. X.703 (1997)/Amd.l(1998 E) STD-ITU-T RECMN X.703 AMD II-ENGL 1978 Y8b2591 Ob53787 975 ISO/IEC 13244 : 199WAmd.l : 1999 (E) There is a need to define a commonly agreed base management-operation server (bmos) interface type, which COBA managed objects should support. Th

32、e widespread support of this bmos interface type by CORBA managed objects will provide commonality between the various groups defining services for CORBA-based open distributed management. NOTE - The term base interface is used to imply that other interface types may be derived from it using inherit

33、ance, or other forms of subtyping. Each CORBA managed object has at least one interface, defined in ODP IDL, for the attributes and operations which it supports. A bmos interface type in this context would include all of the basic common features associated with any CORBA managed object. This could

34、include information about the interface types supported by the CORBA managed object, the identifier for a CORBA managed object instance. This bmos interface type could then be specialized for each type of COBA managed object in the system. ODP IDL offers facilities to define interfaces. The same int

35、erface definition is used by both the client and the server. It is equally important to design distributed managed systems so that new CORBA managed object types (with corresponding new interface types) may be installed in the system during run time, without rebuilding the system software to work wi

36、th the new definitions. The Dynamic Skeleton Interface is a mechanism which may be used to build such flexible systems, but other mechanisms may also be employed. When a bmos interface type is used for a CORBA managed object, a limited set of management operations can be invoked by the managing syst

37、em without knowledge of the specific features of a specialized CORBA managed object type. 8.1.2 Handling of notifications ODMA notifications are treated as operation invocations from managed entities onto an event distribution mechanism which is based on the extension of the CORBA event service (COR

38、BA Services). Each defined ODMA notification results in the specification of sets of operations in notification server interfaces. These notification server interfaces may be supported by notification dispatcher binding objects (e.g. CORBA event channel) or destination objects. The handling of ODMA

39、notifications, in the CORBA environment as defined in the CORBA Event Service specification (CORBA Services), may be accomplished using either CORBA typed or untyped events, and using either the push or pull models for delivery of event reports. In the CORBA Event Service: - the push model implies t

40、hat the sender of an event report invokes an operation on the receiving object (with the event report contents contained in the invocation); while, the pull model implies that the receiver of an event report invokes an operation on the sending object (with the event report contents in the terminatio

41、n message). - The ODMA definition of notification, and all the figures in this Specification, assume that the push model is being used for notification delivery. In the case of the pull model, the notification client and notification server roles are reversed, but this is not explicitly shown in thi

42、s Recommendation I International Standard. There is a need for a CORBA-based event distribution mechanism (such as that provided by ITU-T Rec. X.770 I ISOAEC 15427-1) which allows notifications emitted from a single CORBA managed object to be delivered to multiple destination computational objects w

43、hich subscribe to particular types of notifications. The definition of ODMA notification, which is intended to allow distribution to multiple destinations, does not allow any information, other than acknowledgement of receipt, to be returned in the reply to the notification delivery operation in the

44、 push model (either from the COMA managed object to the event distribution object, or from the event distribution object to the destination). NOTE - The pull mode of delivery makes acknowledgement of receipt unnecessary from the point of view of the notification receiver. There is a need for event d

45、istribution mechanisms which can be configured for various quality of service levels, including the ability for the event distribution computational object to queue notifications for delivery when the ultimate destination becomes available for delivery. 8.1.3 Handling of linked replies In CORBA, lin

46、ked replies are realized by the client of the original operation (Le. computational object in the managing role) providing an input parameter in the operation signature, which gives a reference to the Irs interface to be used for invoking the linked replies. NOTE - This is sometimes referred to as a

47、 callback. ITU-T Rec. X.703 (1997)/Arnd.l(1998 E) 3 STD-ITU-T RECMN X.703 ADD 1-ENGL 1998 m il8b257L Ob53988 301 ISO/IEC 13244 : 1998lAmd.l : 1999 (E) 8.1.4 Handling of scoping Multiple object access via scoping can be handled either directly by the CORBA managed object (through operations in one of

48、 its management-operation server interfaces), or by a scoping mechanism (existing on another object outside of the CORBA managed object) that presents a generic management interface that supports scoping parameters. 8.1.5 Handling of filtering The handling of filtering can be supported directly by t

49、he COREIA managed object (through parameters of operations in its management-operation server interfaces), or through the use of specialized filter objects placed between the managing role computational object and the CORBA managed object. 8.2 Engineering viewpoint 8.2.1 Support for access transparency In ODMA we are distributing the intelligence of the management applications between the managing and the managed system. A managing system provides management functions by using objects in the managing role, which invoke operations which ultimately affect objects in the manage