ITU-T X 780-2001 TMN guidelines for defining CORBA managed objects (Study Group 4)《定义CORBA管理目标的TMN指南 X系列 数据和开放网络通信-OSI管理-管理功能和ODMA功能》.pdf

《ITU-T X 780-2001 TMN guidelines for defining CORBA managed objects (Study Group 4)《定义CORBA管理目标的TMN指南 X系列 数据和开放网络通信-OSI管理-管理功能和ODMA功能》.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 780-2001 TMN guidelines for defining CORBA managed objects (Study Group 4)《定义CORBA管理目标的TMN指南 X系列 数据和开放网络通信-OSI管理-管理功能和ODMA功能》.pdf（82页珍藏版）》请在麦多课文档分享上搜索。

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T X.780 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2001) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OSI management Management functions and ODMA functions TMN guidelines for defining CORBA managed objects ITU-T Recommendation X.780 (For

2、merly CCITT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities X.1X.19 Interfaces X.20X.49 Transmission, signalling and switching X.50X.89 Network aspects X.90X.149 Maintenance X.150X.179 Administrative arrangement

3、s X.180X.199 OPEN SYSTEMS INTERCONNECTION Model and notation X.200X.209 Service definitions X.210X.219 Connection-mode protocol specifications X.220X.229 Connectionless-mode protocol specifications X.230X.239 PICS proformas X.240X.259 Protocol Identification X.260X.269 Security Protocols X.270X.279

4、Layer Managed Objects X.280X.289 Conformance testing X.290X.299 INTERWORKING BETWEEN NETWORKS General X.300X.349 Satellite data transmission systems X.350X.369 IP-based networks X.370X.399 MESSAGE HANDLING SYSTEMS X.400X.499 DIRECTORY X.500X.599 OSI NETWORKING AND SYSTEM ASPECTS Networking X.600X.62

5、9 Efficiency X.630X.639 Quality of service X.640X.649 Naming, Addressing and Registration X.650X.679 Abstract Syntax Notation One (ASN.1) X.680X.699 OSI MANAGEMENT Systems Management framework and architecture X.700X.709 Management Communication Service and Protocol X.710X.719 Structure of Managemen

6、t Information X.720X.729 Management functions and ODMA functions X.730X.799 SECURITY X.800X.849 OSI APPLICATIONS Commitment, Concurrency and Recovery X.850X.859 Transaction processing X.860X.879 Remote operations X.880X.899 OPEN DISTRIBUTED PROCESSING X.900X.999 For further details, please refer to

7、the list of ITU-T Recommendations. ITU-T X.780 (01/2001) i ITU-T Recommendation X.780 TMN guidelines for defining CORBA managed objects Summary This Recommendation specifies guidelines for defining CORBA-based interfaces to software objects representing manageable resources in a TMN. It covers infor

8、mation modelling guidelines, rules for translating models from GDMO, and IDL style conventions. It also provides an IDL module defining data types, superclasses, and notifications to be used in CORBA-based information model specifications. Source ITU-T Recommendation X.780 was prepared by ITU-T Stud

9、y Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 19 January 2001. Keywords Abstract Syntax Notation One (ASN.1), Common Object Request Broker Architecture (CORBA), Distributed Processing, Guidelines for the Definition of Managed Objects (GDMO), Interface Definition Languag

10、e (IDL), Managed Objects, TMN Interfaces. ii ITU-T X.780 (01/2001) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is resp

11、onsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the

12、ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborat

13、ive basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementat

14、ion of this Recommendation may involve the use of a claimed Intellectual Property Right. 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 o

15、f the date of approval of this Recommendation, ITU had not received notice 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 t

16、o consult the TSB patent database. ITU 2001 All 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 ITU. ITU-T X.780 (01/2001) iii CONTENTS Page 1 Sc

17、ope. 1 1.1 Purpose 1 1.2 Application 2 1.3 Roadmap . 3 1.4 Conventions 4 1.5 Compiling the IDL 4 2 References. 5 2.1 Normative References. 5 3 Definitions and Abbreviations 5 3.1 Definitions from ITU-T X.701 . 5 3.2 Definitions from ITU-T X.703 . 5 3.3 Abbreviations 6 4 CORBA Modelling Goals and Req

18、uirements. 7 4.1 Goals . 7 4.1.1 Application Interoperability 7 4.1.2 Common Usage of CORBA Common Object Services 7 4.1.3 Information Model Transparency 7 4.2 Entities 8 4.2.1 Access Granularity 8 4.3 Principles of Containment and Naming 8 4.3.1 Naming 9 4.3.2 Entity Identification. 9 4.4 Managed O

19、bject Classes. 10 4.5 Packages 10 4.6 Attributes 10 4.6.1 GET and SET. 10 4.6.2 Generic Attribute Get 10 4.6.3 Set-valued Attributes . 10 4.7 Creation and Deletion of Managed Objects 10 4.7.1 Creation . 11 4.7.2 Deletion . 12 4.8 Inheritance 12 5 The Object Model IDL Module 12 5.1 The Base (Top) Man

20、aged Object Interface. 13 5.1.1 The nameGet() Operation 14 iv ITU-T X.780 (01/2001) Page 5.1.2 The objectClassGet() Operation 14 5.1.3 The packagesGet() Operation 14 5.1.4 The creationSourceGet() Operation 14 5.1.5 The deletePolicyGet() Operation. 14 5.1.6 The attributesGet() Operation . 15 5.1.7 Th

21、e destroy() Operation. 15 5.2 The Managed Object Factory . 16 5.3 The Notifications Interface . 16 5.4 The Data Type Definitions . 18 5.5 Exceptions. 18 5.5.1 The ApplicationError Exception . 18 5.5.2 The CreateError Exception. 19 5.5.3 The DeleteError Exception . 20 5.6 Macro Definitions. 20 5.7 Th

22、e Constant Definitions 21 6 Information Modelling Guidelines . 21 6.1 Modules 21 6.2 Interfaces. 21 6.3 Attributes 22 6.3.1 Readable Attributes . 22 6.3.2 Settable Attributes . 23 6.3.3 Set-valued Attributes . 23 6.3.4 Exceptions . 23 6.3.5 Standard Attributes 23 6.4 Actions 24 6.5 Notifications 25

23、6.6 Conditional Packages 25 6.7 Behaviour 26 6.8 Name Binding Information. 26 6.9 Factories 28 6.9.1 Create Operations 28 6.9.2 Factory Finder 30 6.10 Managed Object Class Value Types. 30 6.11 Constants. 31 6.12 Registration. 32 6.13 Versioning of CORBA/IDL Specifications 33 7 GDMO Translation . 34

24、ITU-T X.780 (01/2001) v Page 7.1 Managed Object Classes. 34 7.2 Packages 34 7.3 Attributes 35 7.4 Attribute Groups . 36 7.5 Actions 36 7.6 Notifications 36 7.7 Behaviours 37 7.8 Name Bindings . 37 7.9 Parameters. 38 7.9.1 ACTION-INFO and ACTION-REPLY. 38 7.9.2 EVENT-INFO and EVENT-REPLY. 39 7.9.3 Co

25、ntext-Keyword 40 7.9.4 SPECIFIC-ERROR . 40 7.10 ASN.1 Data Types 41 7.10.1 Basic Types 41 7.10.2 Sequence 41 7.10.3 Sequence of 41 7.10.4 Set of 41 7.10.5 Choice 42 7.10.6 Object Identifier (OID) 42 7.10.7 Object Instance 42 7.10.8 BIT STRING . 42 8 Style Idioms for CORBA IDL Specifications 44 8.1 U

26、se Consistent Indentation . 44 8.2 Use Consistent Case for Identifiers 45 8.3 Follow JIDM Approach for IMPORT 45 8.4 Use JIDM Approach for OPTIONAL and CHOICE 45 8.5 Use a Consistent Type Suffix . 46 8.6 Use a Consistent Suffix for Sequence Types 46 8.7 Use a Consistent Suffix for Set Types 46 8.8 U

27、se a Consistent Suffix for Optional Types . 46 8.9 Arrange Operation Parameters in a Consistent Manner . 46 8.10 Assume No Global Identifier Spaces 46 8.11 Module Level Definitions. 47 8.12 Use of Exceptions and Return Codes . 47 8.13 Explicit vs. Implicit Operations 47 8.14 Dont Create a Large Numb

28、er of Exceptions 47 vi ITU-T X.780 (01/2001) Page 9 Compliance and Conformance 47 9.1 Standards Document Compliance. 47 9.2 System Conformance 48 9.3 Conformance Statement Guidelines . 48 Annex A The Object Model CORBA IDL Module 48 Annex B Network Management Constant Definitions . 70 Appendix I Bib

29、liography 73 ITU-T X.780 (01/2001) 1 ITU-T Recommendation X.780 TMN guidelines for defining CORBA managed objects 1 Scope The TMN architecture defined in ITU-T M.3010 introduces concepts from distributed processing and includes the use of multiple management protocols. The initial TMN interface spec

30、ifications for intra- and inter-TMN interfaces were developed using the Guidelines for the Definition of Managed objects (GDMO) notation from OSI Systems Management with Common Management Information Protocol (CMIP) as the protocol. The inter-TMN interface (X) included both CMIP and CORBA GIOP/IIOP

31、as possible choices at the application layer. CORBA, a distributed processing technology, is being considered for use in the TMN communication architecture primarily due to its acceptance by the Information Technology industry. This acceptance is expected to enhance the availability of CORBA-based i

32、nterfaces due to better development tools and wide-spread expertise in developing CORBA-based interfaces. This technology, developed by the Object Management Group (OMG), is also being considered by multiple industries. Specifications using this technology provide support for standard application pr

33、ogramming interfaces (APIs) and language bindings to programming languages, and they also facilitate software portability. The interoperability solutions offered by the object request broker combined with the Inter-ORB protocol address interoperability between client and server. While CMIP and infor

34、mation models provide solutions for interoperability between manager and agent systems, CORBA defines inter-object interactions where the objects may be distributed. 1.1 Purpose Several groups are developing network management specifications that use CORBA modelling techniques with IDL as the notati

35、on along with CORBA services. The scope of this Recommendation is to define guidelines suitable for use in the specification of interoperable CORBA-based network management interfaces. The demands placed on “X“ interfaces are different from those used “inside“ an administration, “Q“ interfaces. The

36、scope of this Recommendation covers all interfaces in the TMN where CORBA may be used. It is expected that not all capabilities and models defined here are required in all TMN interfaces. This implies that the framework can be used for interfaces between management systems at all levels of abstracti

37、ons (inter and intra-administration) as well as between management systems and network elements. ITU-T Q.816 1 defines a set of services that are required for CORBA-based TMN interfaces. This Recommendation defines guidelines for specifying information models written in CORBA IDL to which the servic

38、es are applicable. It also provides rules for translating existing GDMO models to IDL. Finally, it defines some base IDL code for use by all CORBA-based TMN information models. The combination of this Recommendation and ITU-T Q.816 form a framework for defining and implementing CORBA-based TMN inter

39、faces. Use of a common framework on telecommunications management interfaces has several advantages. Some examples are: facilitating reuse of models that are developed to meet the generic requirements of telecommunications; profiling CORBA services for use by the telecommunications industry; easing

40、the definition of new services for TMN; reusing the semantics of the existing rich set of models; and harmonizing the modelling approach across groups using a single source similar to ITU-T X.720, X.721 and X.722 for CMIP. Reusing a common approach to modelling resources and reusing a generic inform

41、ation model for a variety of network technologies and network management applications will speed the introduction of new network services while keeping network management system development costs down. 2 ITU-T X.780 (01/2001) The telecommunications industry has invested a great deal of time and ener

42、gy in the development of information models for the CMIP network management protocol. A primary goal of the TMN CORBA framework is the reuse of these information models by enabling their translation to CORBA Interface Definition Language (IDL) with little change in semantics. As a result, initial ID

43、L information models are expected to be derived from CMIP models. 1.2 Application ITU-T M.3020 defines three phases in the development of a TMN specification. The three phases are Requirements, Analysis and Design. Figure 1 shows this process and the scope of this Recommendation for developing CORBA

44、-based interface specification relative to this process. T0414410-00(a) (b)(c)Requirements SpecificationParadigm Independent SpecificationParadigmindependentParadigmspecificCMIP-basedSpecificationCORBA-basedSpecificationOther Paradigm-basedSpecificationFigure 1/X.780 CORBA-based Specification The re

45、quirements and analysis are specified using an approach that is not specific to a network management technology paradigm. The output from the analysis phase, the paradigm independent specification, is used as input to the paradigm specific design phase. In the design phase, network management paradi

46、gm specific features are used to define information models. These paradigm specific specifications incorporate both behaviour (normally in natural language) and formal interface signatures (e.g. GDMO, IDL). The arrows marked as (a) and (b) show that the analysis output is mapped to GDMO/ASN.1 based

47、model to use with CMIP or IDL models to use with CORBA/IIOP, respectively. There are no prescriptive rules available at this time to generate these models. It may be possible to develop such rules in the future in ITU-T M.3020. This Recommendation addresses the reuse of existing models developed in

48、the CMIP paradigm if CORBA/IIOP is to be used instead of CMIP. The arrow shown as (c) is addressed by this Recommendation. In developing the transformation from GDMO/ASN.1 definitions to CORB/IDL, two approaches are possible. In the first approach, every element of the syntax is translated to CORBA/

49、IDL using a well-specified algorithm or a prescriptive definition. This approach is the one taken with Joint Inter-Domain Management (JIDM) where a gateway can be used to support interoperability. ITU-T X.780 (01/2001) 3 The second approach (used in this Recommendation) does not prescriptively translate every element of the syntax. Rather, the elements are translated from the existing GDMO in a way that preserves the semantics and also uses the features of CORBA. This approach is not used for inter-working via gateways but to preserve the r