ITU-T X 780 CORR 2-2002 TMN Guidelines for Defining CORBA Managed Objects Corrigendum 2 Series X Data Networks and Open System Communications OSI Management - Management Functions .pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.780 Corrigendum 2 (052002) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMM UN ICATIONS OS1 management - Management functions and ODMA functions TMN guidelines for defining CORBA managed objects Corrigendum 2 I

2、TU-T Recommendation X.780 (2001) - Corrigendum 2 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS PUBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maintenance Administrative arrangements Model and notation Servi

3、ce definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing General Satellite data transmission systems P-based networks MESSAGE HANDLING SYSTEMS DIRECTORY OS1 N

4、ETWORKING AND SYSTEM ASPECTS Networking Efficiency Quality of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN. 1) Systems Management fi-amework and architecture Management Communication Service and Protocol OPEN SYSTEMS INTERCONNECTION INTERWORKING BETWEN NETWORKS OS1 M

5、ANAGEMENT X. 1-X.19 X.20-X.49 X.50-X.89 X.90-X.149 X.150-X. 179 X.180-X.199 X.200-X.209 X.210-X.219 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.

6、699 X.700-X.709 X.710-X.719 Structure of Management Information X.720-X.729 SECURIY X.800-X.849 OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.850-X.859 X.860-X.879 X.880-X.899 X.900-X.999 Il For further details, please re

7、fer to the list of ITU-T Recommendations. ITU-T Recommendation X.780 TMN guidelines for defining COMA managed objects Corrigendum 2 Source Corrigendum 2 to ITU-T Recommendation X.780 (2001) was prepared by ITU-T Study Group 4 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 May 2

8、002. ITU-T Rec. X.780 (2001)/Cor.2 (05/2002) 1 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 studying

9、 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 groups w

10、hich, 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 with IS0 a

11、nd 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 Recommen

12、dation 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 of approv

13、al 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 the TSB pa

14、tent database. O ITU 2002 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. 11 ITU-T Rec. X.780 (2001)/Cor.2 (092002) ITU-T Recommendation X.780 TMN guidelines for defining CORBA managed objects Corrigendum 2 1)

15、Subclause 5.1.6 In the second paragraph, replace the fourth sentence: On invocation, the client may submit a list of the names of the attributes in which it is interested, with a null list having the special meaning that all supported attributes should be returned. with this sentence: On invocation,

16、 the client may submit a list of the names of the attributes in which it is interested, with an empty list having the special meaning that all supported attributes should be returned. Also in the secondparagraph, replace the last two sentences: The object must always return an accurate list, even if

17、 the submitted list was null or had invalid names. If all the names on the submitted list are invalid, the object should return a null list and an empty value type. with these two sentences: The object must always return an accurate list, even if the submitted list was empty or had invalid names. If

18、 all the names on the submitted list are invalid, the object shall return an empty list and an empty value type. In the third paragraph, replace the third sentence: Thus, null values should be returned for strings, references, and lists of any kind. with this sentence: Thus, null values shall be ret

19、urned for references, strings shall be zero-length, and lists of any kind shall be empty. 2) Subclause 6.10 Add the following paragraph a$er the fourth paragraph, counting the IDL example as a paragraph. Thus, this paragraph comes immediately before the paragraph beginning Tode on the client side wi

20、shing to retrieve the attribute values for an equipment object might look something like this:“ The value type definition may include the IDL key word “truncatable.“ This tells the ORB to slightly change the way the value type is encoded when sent to another system, making it possible for the receiv

21、ing system to use only the inherited part of the value type. This will help enable a managing system to interact with managed objects about which it is unfamiliar, but that inherit from managed objects with which it is familiar, to perform some level of management. Network technology specific manage

22、d object value types, revisions of managed object value types, and in general any subclass that extends the capabilities of a framework or generic model (i.e. Rec. ITU-T M.3 120) value type should include this key word. For example: valuetype SpecialEquipmentValueType : truncatable EquipmentValueTyp

23、e . / new attributes 1; ITU-T Rec. X.780 (2001)/Cor.2 (05/2002) 1 3) Subclause 7.10.1 Add the following new paragraph to the end of the subclause: CORBA IDL does not define a null type. To accommodate the translation of ASN.l NULL types, the type NullType has been defined. ASN.l NULL types should be

24、 translated to this type. The definition of NullType is simply a typedef of the type char. Systems sending NullType parameters should always set the value to zero (O), and systems receiving it should always ignore the value. 4) Annex A In the IDL, in the section defning forward declarations and type

25、defs, after this line: typedef sequence NotifIDSetType; add these lines: /* Since CORBA IDL does not provide a null type, the type NullType is defined for cases in unions in which no data type should be defined. Since char really is a data type, though, it should always be set to /O and always ignor

26、ed. */typedef char NullType ; 2 ITU-T Rec. X.780 (2001)/Cor.2 (0512002) SERIES OF ITU-T RECOMMENDATIONS Series A Series B Series C Series D Series E Series F Series G Series H Series I Series J Series K Series L Series M Series N Series O Series P Series Q Series R Series S Series T Series U Series

27、V Series X Series Y Series Z Organization of the work of ITU-T Means of expression: definitions, symbols, classification General telecommunication statistics General tariff principles Overall network operation, telephone service, service operation and human factors Non-telephone telecommunication se

28、rvices Transmission systems and media, digital systems and networks Audiovisual and multimedia systems Integrated services digital network Cable networks and transmission of television, sound programme and other multimedia signals Protection against interference Construction, installation and protec

29、tion of cables and other elements of outside plant TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits Maintenance: international sound programme and television transmission circuits Specifications of measuring equipment Tele

30、phone transmission quality, telephone installations, local line networks Switching and signalling Telegraph transmission Telegraph services terminal equipment Terminals for telematic services Telegraph switching Data communication over the telephone network Data networks and open system communications Global information Sastructure and Internet protocol aspects Languages and general software aspects for telecommunication systems Printed in Switzerland Geneva, 2002