1、 International Telecommunication Union ITU-T X.780.2TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2007) SERIES X: DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY OSI management Management functions and ODMA functions TMN guidelines for defining service-oriented CORBA managed objects and
2、 faade objects ITU-T Recommendation X.780.2 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS, OPEN SYSTEM COMMUNICATIONS AND SECURITY 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
3、Administrative arrangements 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 Secu
4、rity Protocols X.270X.279 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.379 MESSAGE HANDLING SYSTEMS X.400X.499DIRECTORY X.500X.599 OSI NETWORKING AND SYSTEM ASP
5、ECTS Networking X.600X.629 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.7
6、19 Structure of Management 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.889 Generic applications of ASN.1 X.890X.899 OPEN DISTR
7、IBUTED PROCESSING X.900X.999 TELECOMMUNICATION SECURITY X.1000 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. X.780.2 (03/2007) i ITU-T Recommendation X.780.2 TMN guidelines for defining service-oriented CORBA managed objects and faade objects Summary This Recomme
8、ndation defines a set of TMN CORBA managed object and faade object modelling guidelines required to support service-oriented interfaces. It specifies how service-oriented CORBA TMN interfaces are to be defined. It covers IDL repertoire, information modelling in IDL and IDL style conventions. It also
9、 provides guidelines on redesigning fine-grained and coarse-grained interfaces to service-oriented interfaces. An IDL module is provided defining basic data types, exceptions, notification constructs, a base CORBA struct to be included by every service-oriented managed object and a base CORBA interf
10、ace to be inherited by every service-oriented CORBA interface. This Recommendation and ITU-T Recommendation Q.816.2 together compose a framework for CORBA-based service-oriented TMN interfaces with a wide range of applications. Source ITU-T Recommendation X.780.2 was approved on 16 March 2007 by ITU
11、-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. Keywords Common Object Request Broker Architecture (CORBA), CORBA services, distributed processing, faade, Interface Definition Language (IDL), lightweight object, managed object, managed system, managing system, service orie
12、ntation, service-oriented faade object, TMN interface. ii ITU-T Rec. X.780.2 (03/2007) 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 o
13、f ITU. 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 Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topi
14、cs for study by the 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 prep
15、ared on a collaborative 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. Compliance with this Recommendation is voluntary. However, the Recommendation ma
16、y contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to exp
17、ress requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Pro
18、perty 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 of approval of this Recommendation, ITU had not received notice o
19、f intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2008
20、All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. X.780.2 (03/2007) iii CONTENTS Page 1 Scope 1 1.1 Purpose . 2 1.2 Application . 2 2 References. 2 3 Definitions 4 3.1 Terms defined elsewhere 4 4 Abbre
21、viations and acronyms 5 5 Conventions 8 6 Service-oriented interface design considerations . 8 6.1 Flexible use of faade design pattern . 9 6.2 Lightweight use of ORB. 10 6.3 Naming of managed objects and service-oriented faade objects 11 6.4 Creation and deletion of objects. 11 6.5 Inheritance and
22、containment. 12 6.6 Exceptions 12 6.7 Retrieval and modification of objects and attributes 12 6.8 Notifications . 12 6.9 Conditional capabilities and supported capabilities . 12 6.10 Additional service-oriented interface design considerations 13 7 Service-oriented framework and requirements overview
23、. 13 7.1 Framework overview 13 7.2 Framework constituents overview 13 8 Service-oriented object model IDL 16 8.1 IDL repertoire and foundation IDL 17 8.2 Use of name/value pairs with string values 22 8.3 Single-valued, multi-valued and tagged parameters 22 8.4 Modelling of transmission technologies.
24、 24 8.5 Common attributes Common_T of service-oriented managed objects . 25 8.6 Exceptions 27 8.7 Notifications . 28 9 Providing service-oriented faade interfaces 49 9.1 Faade instantiation 49 9.2 Getting and setting objects and attributes. 50 9.3 Service-oriented faade interface base class Common_I
25、 . 52 9.4 Iterator interfaces 55 iv ITU-T Rec. X.780.2 (03/2007) Page 10 Service-oriented CORBA modelling guidelines 59 10.1 Rules and conventions 61 10.2 Superclasses of service-oriented managed objects and faade objects 62 10.3 Naming conventions for managed objects and faade objects. 62 10.4 Serv
26、ice-oriented modelling of transmission technologies 69 10.5 Modelling of IDL extensions 80 10.6 Additional CORBA modelling guidelines and principles 88 11 Style guide for lightweight CORBA IDL modelling 90 12 Guidelines for redesigning fine-grained and coarse-grained models to service-oriented . 90
27、13 Service-oriented compliance and conformance 90 13.1 Standards document compliance 91 13.2 System conformance 91 13.3 Conformance statement guidelines. 97 Annex A (Normative) Service-oriented modelling IDL. 98 A.1 Module globaldefs. 100 A.2 Module common. 105 A.3 Module transmissionParameters. 110
28、 A.4 Module notifications. 112 Bibliography. 132 ITU-T Rec. X.780.2 (03/2007) 1 ITU-T Recommendation X.780.2 TMN guidelines for defining service-oriented CORBA managed objects and faade objects 1 Scope The TMN architecture defined in ITU-T M.3010 introduces concepts from distributed processing and i
29、ncludes the use of multiple management protocols. ITU-T Q.816 and ITU-T 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. ITU-T Q.816 and ITU-T X.780 use an approach where each man
30、ageable resource is addressable with a unique interoperable object reference (IOR) and have become known as “fine-grained“ interfaces. ITU-T Q.816.1 and ITU-T X.780.1 extend the CORBA-based TMN interface framework so that not every manageable resource needs to have an IOR. The extension has become k
31、nown as “coarse-grained“ interfaces. At a coarse-grained TMN interface, a CORBA object (with an IOR), which is used to access manageable resources having no IOR and invoke operations on them, is referred to as a faade, while an object that is accessed through a faade is referred to as a lightweight
32、object. All managed objects that are accessible through a particular coarse-grained faade are required to be of the same class and, for each managed object class, (at least) one faade interface shall be provided. Managed objects accessed through a faade still have a CORBA name even though they may n
33、ot (but nevertheless could) have an individual CORBA interface. To support the ability to determine a managed objects faade based on only its name, the CORBA names of managed objects accessible through a coarse-grained faade are extended slightly beyond the names of managed objects not accessible th
34、rough a faade. This Recommendation, along with ITU-T Q.816.2, further extends the framework to enable it to support a different style of interaction between managing systems and managed systems. This style of interaction is termed “service-oriented“. The “service-oriented“ style introduces the so-ca
35、lled “service-oriented faade objects“ in the managed systems and relieves a managing system from having to retrieve the location information for each manageable resource or type of manageable resource it wishes to access. This Recommendation provides the IDL-related service-oriented modelling guidel
36、ines, including the superclasses of the service-oriented managed objects and faade objects, rules and conventions, naming of managed objects and service-oriented faade objects, IDL repertoire and style guide for use by IDL modellers, modelling of transmission technologies according to ITU-T Q.805 an
37、d ITU-T G.809, and standardized modelling of IDL extensions. The companion Recommendation ITU-T Q.816.2 specifies the lightweight use of built-in CORBA system services of ORB products and of certain OMG common object services, and introduces a new ITU-T TMN support service, the session service, whic
38、h allows for the implementation of a very high degree of lightweight object. The scope of this Recommendation is the same as the original TMN CORBA framework in the Q.816-series and X.780-series of ITU-T Recommendations. The framework and these extensions cover all interfaces in the TMN where CORBA
39、may be used. These interfaces are OS-OS interfaces according to ITU-T M.3010, where one OS takes a client/manager role (e.g., an NMS) and the other OS takes a server/agent role (e.g., an EMS). To be concrete, the service-oriented modelling IDL of Annex A refers to an NML-EML interface but it can be
40、applied to any managing system and managed system. 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 interfaces between management systems at all levels of abstractions (inter- and intra-ad
41、ministration at various logical layers) as well as between management systems and network elements. 2 ITU-T Rec. X.780.2 (03/2007) 1.1 Purpose The purpose of this Recommendation and the companion Recommendation ITU-T Q.816.2 is to extend the TMN CORBA framework to enable it to be used in a wider ran
42、ge of applications. The extensions enable a lightweight mode of interaction between the managing and managed systems which may be preferred in many situations. They also enable the endorsement of de facto CORBA services and information models usage which are recognized in the telecommunications indu
43、stry. Thus, this Recommendation is intended for use by various groups specifying network management interfaces. 1.2 Application ITU-T Q.816.2 accompanies this Recommendation and extends the framework ORB usage, the OMG common services usage and the ITU-T TMN framework support services defined in ITU
44、-T Q.816 and ITU-T Q.816.1. Collectively, ITU-T Q.816.2 and this Recommendation define a framework for CORBA-based service-oriented TMN interfaces. The fine-grained, coarse-grained and service-oriented choices of the CORBA-based TMN interface framework are used in Amendment 1 to ITU-T M.3010 to prov
45、ide conformance definitions for TMN interfaces between operations systems. Refer to ITU-T Q.816.2 for details. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of
46、publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list
47、of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T G.805 ITU-T Recommendation G.805 (2000), Generic functional architecture of transport network
48、s. ITU-T G.809 ITU-T Recommendation G.809 (2003), Functional architecture of connectionless layer networks. ITU-T G.852.2 ITU-T Recommendation G.852.2 (1999), Enterprise viewpoint description of transport network resource model. ITU-T G.8010 ITU-T Recommendation G.8010/Y.1306 (2004), Architecture of
49、 Ethernet layer networks. ITU-T M.3010 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3017 ITU-T Recommendation M.3017 (2003), Framework for the integrated management of hybrid circuit/packet networks. ITU-T M.3100 ITU-T Recommendation M.3100 (2005), Generic network information model. ITU-T Q.816 ITU-T Recommendation Q.816 (2001), CORBA-based TMN services. ITU-T Q.816.1 ITU-T Recommendation Q.816.1 (2001), CORBA-ba
