ITU-T M 3160-2008 Generic protocol-neutral management information model (Study Group 2)《一般与协议无关的管理信息模型 2号研究组》.pdf

《ITU-T M 3160-2008 Generic protocol-neutral management information model (Study Group 2)《一般与协议无关的管理信息模型 2号研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3160-2008 Generic protocol-neutral management information model (Study Group 2)《一般与协议无关的管理信息模型 2号研究组》.pdf（226页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T M.3160TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2008) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Generic, protocol-neutral management information model Recommendation ITU-T

2、 M.3160 ITU-T M-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channe

3、l signalling systems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International public telephone n

4、etwork M.1200M.1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599Integrated services digital networks M.3600M.3999 Common channel signalling syste

5、ms M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3160 (11/2008) i Recommendation ITU-T M.3160 Generic, protocol-neutral management information model Summary Recommendation ITU-T M.3160 provides a generic network information model. The model describ

6、es information object classes (IOCs) and their properties that are generic and useful to describe information exchanged across all interfaces defined in Recommendation ITU-T M.3010 TMN architecture. These generic managed object classes are intended to be applicable across different technologies, arc

7、hitecture and services. The managed object classes in this Recommendation may be specialized to support the management of various telecommunications networks. This Recommendation follows Recommendation ITU-T M.3020, management interface specification methodology on the analysis phase. The informatio

8、n models provided in this Recommendation are in a protocol-neutral manner, and can be mapped to multiple protocol-specific information models (design phase). Source Recommendation ITU-T M.3160 was approved on 13 November 2008 by ITU-T Study Group 2 (2009-2012) under Recommendation ITU-T A.8 procedur

9、es. Keywords Information model, protocol-neutral, protocol-specific, technology independent, technology-specific, TMN. ii Rec. ITU-T M.3160 (11/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and

10、communication technologies (ICTs). The ITU Telecommunication 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 basi

11、s. The World Telecommunication Standardization Assembly (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 Resolu

12、tion 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared 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 a

13、nd a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may 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 m

14、et. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express 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 possi

15、bility 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 ITU members or others outside of the R

16、ecommendation 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, implementers are cautioned that this may not represent the latest informa

17、tion and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2010 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T M.3160 (11/2008) iii CONTENTS Page 1

18、 Scope 1 1.1 Purpose . 1 1.2 Field of application . 1 2 References. 2 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 3 4 Abbreviations 3 5 Conventions 4 6 Concepts and background . 4 7 Information object classes 5 7.1 Imported information entities and local

19、labels . 5 7.2 Class diagram . 5 7.3 Information object class definitions . 30 7.4 Information relationship definitions . 123 8 Common information definitions . 181 8.1 Attributes 181 8.2 Notifications . 214 Appendix I 215 Bibliography. 218 Rec. ITU-T M.3160 (11/2008) 1 Recommendation ITU-T M.3160 G

20、eneric, protocol-neutral management information model 1 Scope This Recommendation provides a generic network information model. It identifies TMN object classes that are common to managed telecommunication networks, or are of a generic type that can be used to manage a network at a technology-indepe

21、ndent level, or are super-classes of technology-specific managed objects in a telecommunication network, or management support objects that are required for the management of the telecommunication network. These objects are relevant to information exchanged across standardized interfaces defined in

22、the b-ITU-T M.3010 TMN architecture. This Recommendation addresses generically the abstractions of those aspects of telecommunication resources (e.g., equipments, telecommunication services) required to manage the network. It also includes the abstractions related to the management services. b-ITU-T

23、 G.805, on the generic functional architecture of the connection-oriented transport network, and b-ITU-T G.809, on the functional architecture of connectionless layer networks, are used as the basis in developing the transport aspects of this model. The generic information model provided in this Rec

24、ommendation follows the ITU-T M.3020 interface methodology on the analysis phase, and they are developed in a protocol-neutral manner, which can be mapped to multiple protocol-specific information models. This Recommendation does not address abstractions relevant to technology-specific areas or impl

25、ementation-specific details. 1.1 Purpose 1.1.1 Interoperability There will be a variety of TMN conformant management systems and managed systems concerning many technology-specific areas, such as switching and transmission. One purpose of this Recommendation is to provide a vehicle for management in

26、teroperability between such systems. 1.1.2 Technology-independent management By introducing the concept of technology-independent management, it is possible to perform management of diverse equipment using common communication interfaces. In this manner, an “abstract“ view over a set of network-elem

27、ents can be achieved. 1.1.3 Facilitating information model development This Recommendation also provides a framework from which technology-specific information models may be developed. 1.2 Field of application This Recommendation captures the generally applicable requirements of the technology-indep

28、endent and technology-specific information models, as well as information relating to TMN management services. Through specialization, this Recommendation is applicable to technology-specific TMN information models. The mechanism for specialization is inheritance. 2 Rec. ITU-T M.3160 (11/2008) Even

29、though technology-specific models may be derived from this Recommendation, some of the generic managed object classes in this Recommendation are instantiable in order to provide interoperability between equipment supporting information models derived from this Recommendation and equipment that only

30、supports the information model in this Recommendation. 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 publication, the editions indicated were valid. All Reco

31、mmendations 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 of the currently valid ITU-T Recommendations is regularl

32、y 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 E.410 Recommendation ITU-T E.410 (1998), International network management General information. ITU-T M.1400 Recommendation ITU-T M.1400 (2006), Desig

33、nations for interconnections among operators networks. ITU-T M.1401 Recommendation ITU-T M.1401 (2006), Formalization of interconnection designations among operators telecommunication networks. ITU-T M.3020 Recommendation ITU-T M.3020 (2008), Management interface specification methodology. ITU-T X.7

34、31 Recommendation ITU-T X.731 (1992) | ISO/IEC 10164-2:1993, Information technology Open Systems Interconnection Systems management: State management function. ITU-T X.734 Recommendation ITU-T X.734 (1992) | ISO/IEC 10164-5:1993, Information technology Open Systems Interconnection Systems Management

35、: Event report management function. ISO 3166-1 ISO 3166-1:2006, Codes for the representation of names of countries and their subdivisions Part 1: Country codes. Additional non-normative references can be found in the Bibliography. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses th

36、e following terms defined elsewhere: 3.1.1 aggregate audible/visual indicators b-ITU-T M.3100: An audible/visual alarm indicator that reflects information about a set of managed resources. 3.1.2 alarm reporting b-ITU-T M.3100: Process of alerting, for the purposes of management, external systems and

37、 users regarding alarms. 3.1.3 ALarM reporting (ALM) b-ITU-T M.3100: Alarm Reporting is turned on. 3.1.4 alarm reporting control b-ITU-T M.3100: Involves the turning off of alarm reporting which includes inhibiting new autonomous alarm indication notification, and inhibiting the use of managed resou

38、rce-specific/unit alarm information for the determination of aggregate audible/visual indicators. Autonomous alarm clear notification for previously reported alarms will not be suppressed. Alarm reporting “on“ is supported by the “ALM“ state. Alarm reporting “off“ is supported by the “NALM-QI“, “NAL

39、M-TI“, and “NALM“ states. Rec. ITU-T M.3160 (11/2008) 3 3.1.5 ARC interval b-ITU-T M.3100: Generic term that applies to both the persistence and timed intervals. 3.1.6 inhibited b-ITU-T M.3100: This term is used throughout this feature description to identify that reporting is off (or in other words

40、, is not allowed). 3.1.7 managed entity b-ITU-T M.3100: A managed entity may be a managed system, a managed application, or a managed resource. This definition is dependent upon the context in which it is used. 3.1.8 managed resource b-ITU-T M.3100: A specific component of a managed system/managed a

41、pplication (e.g., a specific circuit pack, termination point). 3.1.9 managed resource-specific/unit audible/visual indicator b-ITU-T M.3100: An audible/visual alarm indicator that is specific to a single managed resource. 3.1.10 management interface b-ITU-T M.3100: Any managed entity interface that

42、is defined for the purpose of management (e.g., OS interface, craft interface, LED indicator). 3.1.11 No ALarM reporting (NALM) b-ITU-T M.3100: Alarm Reporting is turned off. 3.1.12 No ALarM reporting, CountDown (NALM-CD) b-ITU-T M.3100: This is a substate of NALM-QI and performs the persistence tim

43、ing countdown function when the managed entity is qualified problem-free. 3.1.13 No ALarM reporting, NotReady (NALM-NR) b-ITU-T M.3100: This is a substate of NALM-QI and performs a wait function until the managed entity is qualified problem-free. 3.1.14 No ALarM reporting, Qualified Inhibit (NALM-QI

44、) b-ITU-T M.3100: Alarm Reporting is turned off until the managed entity is qualified problem-free for a specified persistence interval. 3.1.15 No ALarM reporting, Timed Inhibit (NALM-TI) b-ITU-T M.3100: Alarm Reporting is turned off for a specified timed interval. 3.1.16 persistence interval b-ITU-

45、T M.3100: A period of time for which a managed entity must be free of qualified problems. 3.1.17 qualified problem b-ITU-T M.3100: A problem that affects the operability of the managed entity and used to qualify transitions between the “NALM-NR“ and “NALM-CD“ states. Additional detail for this defin

46、ition is managed resource specific and is to be defined by the managed resource. 3.1.18 timed interval b-ITU-T M.3100: A period of time. 3.2 Terms defined in this Recommendation This Recommendation has no new definitions. 4 Abbreviations This Recommendation uses the following abbreviations and acron

47、yms: AP Access Point ARC Alarm Reporting Control ASAP Alarm Severity Assignment Profile AVC Attribute Value Change Notification DN Distinguished Name FD Flow Domain 4 Rec. ITU-T M.3160 (11/2008) FDFr Flow Domain Fragment FP Flow Point FPP Flow Point Pool FPPLink Flow Point Pool Link FTP Flow Termina

48、tion Point ICC ITU Carrier Code IOC Information Object Class ME Managed Element MO Managed Object MOC Managed Object Class NE Network Element NEF Network Element Function NWCTP Network Connection Termination Point NWTTP Network Trail Termination Point OS Operations System RDN Relative Distinguished

49、Name PBX Private Branch eXchange RDN Relative Distinguished Name SC Service Customer SCN State Change Notification SDH Synchronous Digital Hierarchy SLA Service Level Agreement SP Service Provider TMN Telecommunication Management Network UML Unified Modelling Language 5 Conventions This Recommendation follows the conventions defined by the Methodology in ITU-T M.3020. 6 Concepts and background A generic network information model is essential to the generation of uniform fault, configuration, per