1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T X.780.1 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2001) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OSI management Management functions and ODMA functions TMN guidelines for defining coarse-grained CORBA managed object interfaces ITU-
2、T Recommendation X.780.1 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 arrangements X
3、.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 Lay
4、er 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.629 E
5、fficiency 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 Management I
6、nformation 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 the
7、 list of ITU-T Recommendations. ITU-T Rec. X.780.1 (08/2001) i ITU-T Recommendation X.780.1 TMN guidelines for defining coarse-grained CORBA managed object interfaces Summary This Recommendation defines extensions to the set of TMN CORBA managed object modelling guidelines required to support coarse
8、-grained interfaces. It specifies how coarse-grained CORBA TMN interfaces are to be defined. It also provides guidelines on converting fine-grained interfaces to coarse-grained. A CORBA IDL module defining the base interface types to be extended is provided. Source ITU-T Recommendation X.780.1 was p
9、repared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 13 August 2001. Keywords Common Object Request Broker Architecture (CORBA), Distributed Processing, Guidelines for the Definition of Managed Objects (GDMO), Interface Definition Language (IDL), Managed O
10、bjects, TMN Interfaces. ii ITUT Rec. X.780.1 (08/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 responsible for
11、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 ITU-T study
12、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 collaborative basis wi
13、th 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 implementation of this
14、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 of the date o
15、f 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 to consult th
16、e TSB patent database. ITU 2002 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 Rec. X.780.1 (08/2001) iii CONTENTS Page 1 Scope.
17、1 1.1 Purpose 1 1.2 Application 1 1.3 Recommendation roadmap . 2 2 Normative references 2 3 Definitions 3 3.1 Definitions from ITU-T X.701 . 3 3.2 Definitions from ITU-T X.703 . 3 3.3 Additional definitions . 3 4 Abbreviations 3 5 Conventions 4 5.1 Conventions 4 5.2 Compiling the IDL 4 6 Coarse-grai
18、ned interface design considerations . 5 6.1 Coarse-grained object creation and deletion. 5 6.2 Attributes 5 6.3 Notifications 5 6.4 Coarse-grained access to all managed resources 5 6.5 Exceptions. 5 6.6 Support for all operations . 5 6.7 Prescriptive mapping 5 6.8 Retrieval of attributes from multip
19、le objects 6 7 Framework and requirements overview . 6 7.1 Framework overview 6 7.2 Coarse-grained extensions overview 7 7.2.1 The facade design pattern 8 7.2.2 Managed object name extension 9 7.2.3 Support services for facade-accessible managed objects 9 7.2.4 Facade modelling. 9 8 Providing facade
20、 interfaces for accessing managed objects. 10 8.1 Facade instantiation 11 8.2 The facade interface base class. 11 8.2.1 Managed object facade basic capabilities 12 8.2.2 Managed object facade IDL 12 iv ITUT Rec. X.780.1 (08/2001) Page 8.2.3 The objectClassGet() operation. 12 8.2.4 The packagesGet()
21、operation. 13 8.2.5 The creationSourceGet() operation . 13 8.2.6 The deletePolicyGet() operation 13 8.2.7 The attributesGet() operation 13 8.2.8 The attributesBulkGet() operation. 14 8.2.9 The destroy() operation . 16 8.3 The AttributesBulkGet iterator interface. 16 8.4 Factory instantiation . 17 9
22、Coarse-grained CORBA modelling guidelines. 17 10 Guidelines for translating fine-grained models to coarse-grained 17 11 Coarse-grained IDL compliance and conformance 19 11.1 Standards document compliance 19 11.2 System conformance. 19 11.3 Conformance statement guidelines. 19 Annex A Coarse-grained
23、modelling IDL. 19 ITU-T Rec. X.780.1 (08/2001) 1 ITU-T Recommendation X.780.1 TMN guidelines for defining coarse-grained CORBA managed object interfaces 1 Scope The TMN architecture defined in ITU-T M.3010 (2000) introduces concepts from distributed processing and includes the use of multiple manage
24、ment protocols. ITU-T Q.816 and X.780 subsequently define within this architecture a framework for applying the Common Object Request Broker Architecture (CORBA) as one of the TMN management protocols. This Recommendation, along with ITU-T Q.816.1, adds specifications to the framework to enable it t
25、o support a slightly different style of interaction between managing systems and managed systems than that specified in the original framework documents. This style of interaction has certain benefits, the main one being that it relieves a managing system from having to retrieve an object-oriented s
26、oftware address for each manageable resource it wishes to access. These software addresses could number in the millions on large systems. It also changes somewhat the way software is structured on the managed systems, which some managed system suppliers may prefer. The scope of this Recommendation i
27、s the same as the original TMN CORBA framework. The framework and these extensions cover all interfaces in the TMN where CORBA may be used. It is expected, however, that not all capabilities and services defined here are required in all TMN interfaces. This implies that the framework can be used for
28、 interfaces between management systems at all levels of abstractions (inter and intra-administration) as well as between management systems and network elements. 1.1 Purpose The purpose of this Recommendation is to extend the TMN CORBA framework to enable it to be used in a wider range of applicatio
29、ns. The extensions enable a slightly different mode of interaction between the managing and managed systems which may be preferred in many situations. Thus, this Recommendation is intended for use by various groups specifying network management interfaces. 1.2 Application The approach taken in the C
30、ORBA TMN framework Recommendations is to model manageable network resources as software objects accessible using CORBA. Information models written in the CORBA Interface Definition Language (IDL) describe the object interfaces. CORBA provides location-transparency, enabling one software object to in
31、teract with another regardless of its location. A software object is accessed using what CORBA refers to as an Interoperable Object Reference (IOR). The original CORBA TMN framework models each manageable resource as an independent CORBA object, each with its own unique IOR. This approach flexibly a
32、llows each object to reside anywhere. It does, however, require that managing systems have on hand an IOR for each object they wish to access. This is a burden that many companies and administrations in the telecommunications industry have sought to avoid. It also could require a managed system to s
33、upport large numbers of IORs, which some managed system suppliers would like to avoid. This Recommendation, along with ITU-T Q.816.1, defines how the TMN CORBA framework is to be extended to avoid the need for large numbers of IORs. 2 ITUT Rec. X.780.1 (08/2001) CORBA-based interfaces using the appr
34、oach where each manageable resource is addressable with a unique IOR have become known as “fine-grained“ interfaces. Alternatively, those where an IOR is not assigned to each manageable resource are known as “coarse-grained“ interfaces. Because this Recommendation defines a slightly different approa
35、ch to modelling manageable resources on coarse-grained interfaces, interface model specifications will be slightly different for the fine-grained and coarse-grained approaches. 1.3 Recommendation roadmap This Recommendation has the following structure: Clause 1 Introduction, roadmap and updates. Cla
36、use 2 References. Clauses 3 and 4 Definitions and abbreviations used throughout this Recommendation. Clause 5 Conventions. Clause 6 Design considerations that must be addressed as support for coarse-grained interfaces is added to the framework. Clause 7 TMN CORBA framework and coarse-grained require
37、ments overview. Clause 8 Providing facade interfaces for accessing managed objects. This clause covers the model-specific interfaces that must be implemented on coarse-grained interfaces. Clause 9 Guidelines for defining coarse-grained CORBA interfaces. Clause 10 Guidelines for translating fine-grai
38、ned CORBA interface specifications to coarse-grained interface specifications. Clause 11 Compliance and conformance guidelines. Annex A The IDL module for the coarse-grained modelling guidelines specification. This annex is normative. 2 Normative references The following ITU-T Recommendations and ot
39、her references contain provisions which, through 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; users of this Recommendation are therefore encourage
40、d to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. 1 ITU-T X.780 (2001), TMN guidelines for defining CORBA managed objects. 2 ITU-T Q.816 (2001), CO
41、RBA-based TMN services. 3 ITU-T Q.816.1 (2001), CORBA-based TMN services: Extensions to support coarse-grained interfaces. 4 OMG Document formal/99-10-07, The Common Object Request Broker: Architecture and Specification, Revision 2.3.1. ITU-T Rec. X.780.1 (08/2001) 3 3 Definitions 3.1 Definitions fr
42、om ITU-T X.701 The following terms used in this Recommendation are defined in the Systems Management Overview (ITU-T X.701): managed object class; manager; agent. 3.2 Definitions from ITU-T X.703 The following terms used in this Recommendation are defined in the Open Distributed Management Architect
43、ure (ITU-T X.703): notification. 3.3 Additional definitions 3.3.1 facade: An object interface defined to provide access to a set of managed objects, all of which are of the same class. 4 Abbreviations This Recommendation uses the following abbreviations: CMIP Common Management Information Protocol C
44、ORBA Common Object Request Broker Architecture COS Common Object Services DN Distinguished Name EMS Element Management System GDMO Guidelines for the Definition of Managed Objects ID Identifier IDL Interface Definition Language IIOP Internet Interoperability Protocol IOR Interoperable Object Referen
45、ce ITU-T International Telecommunication Union Telecommunication Standardization Sector MO Managed Object NE Network Element NMS Network Management System OAM;5.2 Compiling the IDL An advantage of using IDL to specify network management interfaces is that IDL can be “compiled“ into programming code
46、by tools that accompany an ORB. This actually automates the development of some of the code necessary to enable network management applications to interoperate. Annex A contains code that implementers will want to extract and compile. Annex A is normative and should be used by developers implementin
47、g systems that conform to this Recommendation. The IDL in this Recommendation has been checked with two compilers to ensure its correctness. A compiler supporting the CORBA version specified in ITU-T Q.816 must be used. Annex A has been formatted to make it simple to cut and paste into plain text fi
48、les that may then be compiled. Below are tips on how to do this. 1) Cutting and pasting seems to work better from the MicrosoftWordversion of this Recommendation. Cutting and pasting from the AdobeAcrobatfile format seems to include page headers and footers, which cannot be compiled. ITU-T Rec. X.78
49、0.1 (08/2001) 5 2) All of Annex A, beginning with the line “/* This IDL code“ through the end should be stored in a file named “itut_x780_1.idl“ in a directory where it will be found by the IDL compiler. 3) The headings embedded in Annex A need not be removed. They have been encapsulated in IDL comments and will be ignored by the compiler. 4) Comments that begin with the special sequence “/*“ are recognized by compilers that convert IDL to HTML. These comments often have special formatting instructions for these compiler
