ITU-T X 780 CORR 1-2001 TMN Guidelines for Defining CORBA Managed Objects Series X Data Networks and Open System Communications OSI Management - Management Functions and ODMA Funct.pdf

《ITU-T X 780 CORR 1-2001 TMN Guidelines for Defining CORBA Managed Objects Series X Data Networks and Open System Communications OSI Management - Management Functions and ODMA Funct.pdf》由会员分享，可在线阅读，更多相关《ITU-T X 780 CORR 1-2001 TMN Guidelines for Defining CORBA Managed Objects Series X Data Networks and Open System Communications OSI Management - Management Functions and ODMA Funct.pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.780 Corrigendum I (1 0/2001) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMU NI CATIONS OS1 management - Management functions and ODMA functions TMN guidelines for defining CORBA managed objects Corrigendum I

2、 ITU-T Recommendation X.780 (2001) - Corrigendum I (Formerly CCIlT Recommendation) INTERNATIONAL TELECOMMUN CATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.780 Corrigendum 1 (10/2001) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OS1 management - Management functions a

3、nd ODMA functions TMN guidelines for defining CORBA managed objects Corrigendum 1 ITU-T Recommendation X.780 (2001) - Corrigendum 1 (Formerly CCITT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities Interfaces Tran

4、smission, signalling and switching Network aspects Maintenance Administrative arrangements Model and notation Service definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identication Security Protocols Layer Managed Objects Conforma

5、nce testing General Sateliite data transmission systems IP-based networks MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS Networking Efficiency Quality of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN. 1) Systems Management Wework and architecture

6、 Management Communication Service and Protocol Structure of Management Mormation OPEN SYSTEMS INTERCONNECTION INTERWORKING BETWEEN NETWORKS OS1 MANAGEMENT OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING x. l-x. 19 X.20-X.49 X

7、.50-X.89 X.90-X. 149 X.150-X.179 X.180-X.199 X.200-X.209 X.21 0-X.2 19 X.220-X.229 X.230-X.239 X.240-X.259 X.260-X.269 X.270-X.279 X.280-X.289 X.290-X.299 X.300-X.349 X.350-X.369 x.370-x.399 X.400-X.499 X.500-X.599 X.600-X.629 X.630-X.639 x.640-x.649 X.650-X.679 X.680-X.699 X.700-X.709 X.710-X.719 X

8、.720-X.729 .79 X.800-X.849 X.850-X.859 X.860-X.879 X.880-X.899 x.900-x.999 ForfUrther details, please refm to the list of ITU-T Recommendations. ITU-T Recommendation X.780 TMN guidelines for defining CORBA managed objects CORRIGENDUM 1 Source Corrigendum 1 to IT-T Recommendation X.780 (2001) was pre

9、pared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 7 October 2001. ITU-T Rec. X.780 (2001)/Cor.l (10/2001) i FOREWORD The International Telecommunication Union is the United Nations specialized agency in the field of telecommunications. The ITU Telecommuni

10、cation Standardization Sector (ITU-T) is a permanent organ of 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 Assembl

11、y (WTSA), which meets every four years, establishes the topics 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

12、fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Aministration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY

13、 RIGHTS IT draws attention to the possibility that the practice or implementation 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

14、 members or others outside of the Recommendation development process. As of 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 m

15、ay not represent the latest information and are therefore strongly urged to consult the TSB patent database. o 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 microflm, without p

16、ermission in writing from ITU. . 11 ITU-T Rec. X.780/Cor.l (10/2001) CONTENTS Subclause 2.1 Subclause 5.1.3 . Subclause 5.5 Subclause 6.3 New Subclause 6.3.6 . 6.3.6 Common types . Subclause 6.4 Subclause 6.6 Subclause 6.9.1 . 6.9.1 Create Operations Subclause 6.9.1.2 New subclause 6.9.1.3 Subclause

17、 6.9.1.4 Subclause 9.1 Annex A New Annex C Annex C . The common types CORBA IDL module . Page 1 1 1 1 2 2 2 2 2 2 3 3 3 3 3 5 5 . IT-T Rec . X.780 (2001)/Cor.l (10/2001) 111 ITU-T Recommendation X.780 TMN guidelines for defining CORBA managed objects CORRIGENDUM 1 1) Subclause 2.1 Add a new referenc

18、e: 8 ITU-T X.739 (1993) I ISO/IEC 10164-11 (1994), Information technology - Open Systems Interconnection - Systems management: Metric objects and attributes. 2) Subclause 5.1.3 Aper the second sentence in the first paragraph, add the following sentence: String constants are defined for each conditio

19、nal package string name. 3) Subclause 5.5 In the IDL, delete the following lines: valuetype CreateErrorInfoType : ApplicationErrorInfoType public MOSetType relatedobjects; public AttributeSetType attributelist; 1; valuetype DeleteErrorInfoType : ApplicationErrorInfoType public MOSetType relatedobjec

20、ts; public AttributeSetType attributeList; 1; and replace them with the following: valuetype CreateErrorInfoType : ApplicationErrorInfoType public MONameSetType relatedobjects; public AttributeSetType attributelist; 1; valuetype DeleteErrorInfoType : ApplicationErrorInfoType public MONameSetType rel

21、atedobjects; public AttributeSetType attributelist; 1; 4) Subclause 6.3 Delete the last line of the first paragraph: Future versions of CORBA plan to allow user-defined exceptions on attribute access, and these guidelines may change to take advantage of this. AJter the $rst paragraph, add the follow

22、ing paragraph: The definition of attributes containing references to managed objects should be avoided. Instead, managed object names should be used. ITU-T Rec. X.780 (2001)/Cor.l(10/2001) 1 5) New subclause 6.3.6 Add a new subclause 6.3.6 entitled “Common Types“ as follows: 6.3.6 Commontypes A modu

23、le dening common types is found in Annex C. These types are used by more than one Recommendation. This module is used to provide a single place for the definition of these types. Additional types will be added to this module as needed. 6) Subclause 6.4 In the$rst paragraph, aJter the second sentence

24、, add the following sentence: The use of parameters containing references to managed objects, however, should be avoided. Instead, managed object names should be used 7) Subclause 6.6 After the third paragraph, add the following paragraph: In addition, for each defined conditional package, there sha

25、ll be defined a constant string that can be used in the packages attribute for managed object instances using that conditional package. To differentiate packages from different IDL files, this string must be fully qualified. For example: const string administrativestatepackage = 1itut-m3120:administ

26、rativeStatePackage11; 8) Subclause 6.9.1 Replace subclause 6.9.1 with the following: 6.9.1 Create Operations Each factory interface shall define a single operation for clients to use to create objects. The name of this operation shall be “create“ and it shall return a ManagedObject reference. This s

27、hall be used to return a reference to the newly created object, which may then be “narrowed“ by the client to the specific interface type for that object, or used directly for base class operations. The first five parameters to every create operation are always the same. Mer these come parameters fo

28、r each writeable or set-by-create attribute defined for the managed object. (A set-by-create attribute is one for which the object has no “set“ operation, but for which a value is specified on the create operation.) The names of these parameters are the same as the name of the attribute. (This is th

29、e name of an attribute accessor operation minus the ending “Get“ or “Set“.) Each create operation also has to accept parameters to set the values of any writeable or set-by-create attributes of all super- classes of the object created by the factory. Here is equipment factory: ManagedObject create(

30、in NameBindingType nameBinding, / / in MONameType superiorobject, / in string reqID, / / out MONameType name, / in StringSetType packages, / . / / . / / an example of a create operation for an module name containing Name Binding info. Name of containing object. Requested ID value for name, will be e

31、mpty if auto-naming is to be used. Entire name of newly created object. List of packages requested. Writeable and set-by-create values for Equipment superclass attributes. Writeable and set-by-create values for Equipment attributes. ITU-T Rec. X.780/Cor.l(10/2001) 9) Subclause 6.9.1.2 In the first s

32、entence of the jrst paragraph, replace the words “is a reference to“ with “is the name of.“ In the third sentence of the first paragraph, replace the words “supplied reference“ with “superior object.“ In the last sentence of the second paragraph, replace the words “reference would be null“ with “nam

33、e would be an empty string.“ 10) New subclause 6.9.1.3 Insert a new subclause 6.9.1.3 entitled “Requested ID“ and renumber the existing subclause 6.9.1.3 and subsequent subclauses. 6.9.1.3 Requested ID The third parameter is the ID requested to be assigned to the new object. This string will become

34、the ID field of the COIU3A Name Binding created in the COBA naming service for the new object. Thus, this ID string, along with the kind field contained in the name binding module, names the new object relative to the superior object. If the client supplies an empty string for this parameter, the fa

35、ctory shall automatically choose an ID value. The factory raises a dupliCateName CreateError exception if the supplied ID is a duplicate. (This means both the ID and kind fields match an existing object contained by the superior object.) 11) Subclause 6.9.1.4 Replace the contents of subclause 6.9.1.

36、4 (entitled “Name,“ and newly renumbered by the item above) with the following: The fourth parameter shall be used by the factory to return the entire name of the newly created managed object to the client. 12) Subclause 9.1 After the 8th list item, add the following list item: 9) The subsequent ite

37、ms should be renumbered. Adhere to the conditional package string constant conventions specified in 6.6. 13) Anna A In the IDL, delete the following lines: /* A SuspectObject identifies an object that may be the cause of a failure. It is usually a component of a SuspectObjectList. member obj ectClas

38、s Object class of the suspect object member cuspectObjectInstance Object instance of the suspect member failureprobability Optional failure responsibility */ object probability from 1 to 100 struct SuspectObjectType Obj ectClassType ManagedObj ect UnsignedShortTypeOpt 1; and in theirplace insert the

39、 following lines: obj ectClass ; suspectObjectInstance; failureprobability; /* A SuspectObject identifies an object that may be the cause of a ITU-T Rec. X.780 (2001)/Cor.l (10/2001) 3 failure. It is usually a component of a SuspectObjectList. member obj ectClass Object class of the suspect object m

40、ember suspectObject Name of the suspect object member failureprobability Optional failure responsibility probability from 1 to 100 */ struct SuspectObjectType Obj ectClassType MONameType UnsignedShortTypeOpt 1; Delete the following lines: ob j ectClass ; suspectOb j ect ; failureprobability; valuety

41、pe CreateErrorInfoType : ApplicationErrorInfoType public MOSetType relatedobjects; public AttributeSetType attributelist; 1; and in theirplace insert the following lines: valuetype CreateErrorInfoType : ApplicationErrorInfoType public MONameSetType relatedobjects; public AttributeSetType attributeli

42、st; 1; Delete the following lines: valuetype DeeteErrorInfoType : ApplicationErrorInfoType public MOSetType relatedobjects; public AttributeSetType attributelist; 1; and in their place insert the following lines: valuetype DeleteErrorInfoType : ApplicationErrorInfoType public MONameSetType related0b

43、jects; public AttributeSetType attributelist; 1; Delete the following lines: /* Forward declaration. CORBA uses object references of type l1objecttt to identify objects. These are used instead of ASN.1 object instances. For network management interfaces, all objects will inherit from the “ManagedObj

44、ect“ interface. */ interface ManagedObject; /* MO Set is a set of ManagedObject references. */ typedef sequence eManagedObject MOSetType; /* MO Seq is a sequence of ManagedObject references. */ typedef sequence MOSeqType; and in theirplace insert the following lines: /* A sequence of names is define

45、d as just a sequence of names. */ typedef sequence NameSeqType; AJter these lines: /* A set of names is definded as a sequence of names. */ typedef sequence CNameTypes NameSetType; 4 IT-T Rec. X780/Cor.l(10/2001) insert the following lines: /* A managed object name is just a name */ typedef NameType

46、 MONameType; /* A sequence of managed object names is defined as just a sequence of names. */ typedef NameSeqType MONameSeqType; /* A set of managed object names is defined as just a set of names. */ typedef NameSetType MONameSetType; 14) NewAnnexC Add the following new annex dejning common types. A

47、NNEX c The common types CORBA IDL module #ifndef -itut-x780ct-idl- #define -itut-x780ct-idl- #include #include #pragma prefix “itu. int“ /* */ I* This IDL code is intended to be stored in a file named 1itut-x780ct.idl located in the search path used by IDL compilers on your system. This module, itut

48、x780ct, contains common data type for ITU-T CO= framework based information model. This module can be extended by adding new data type. module itutx780ct */ I I/ Imports /* */ Types imported from itutx780 typedef itutx780:GeneralizedTimeType GeneralizedTimeType; typedef itutx780:PerceivedSeveritflyp

49、e PerceivedSeverityType; I/ Data Types (X.721) struct CounterThresholdType long comparisonlevel; long offsetvalue; boolean notificationOnOff; 1; ITU-T Rec. X780 (2001)/Cor.l(10/2001) 5 struct NotifyThresholdType float threshold; boolean notifyonoff; 1; struct GaugeThresholdType NotifyThresholdType notifylow; NotifyThresholdType notifyHigh; I 1; typedef sequencecGaugeThresholdType GaugeThresholdSetType; enum TideMarkChoice tideMarkChoiceMax, tideMarkChoiceMin 1; union TideMarkType switch (TideMarkChoice) case tideMa