ITU-T M 3100-2005 Generic Network Information Model (Study Group 4)《通用网络信息模型的研究四研究组》.pdf

《ITU-T M 3100-2005 Generic Network Information Model (Study Group 4)《通用网络信息模型的研究四研究组》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3100-2005 Generic Network Information Model (Study Group 4)《通用网络信息模型的研究四研究组》.pdf（98页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T M.3100TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (04/2005) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Generic network information model ITU-T Recommendation M.3100 ITU-T M-SERIE

2、S 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 channel signalling systems

3、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 network M.1200M.1299 I

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

5、further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3100 (04/2005) i ITU-T Recommendation M.3100 Generic network information model Summary This Recommendation provides a generic network information model. The model describes managed object classes and their properties th

6、at are generic and useful to describe information exchanged across all interfaces defined in M.3010 TMN architecture. These generic managed object classes are intended to be applicable across different technologies, architecture and services. The managed object classes in this Recommendation may be

7、specialized to support the management of various telecommunications networks. Source ITU-T Recommendation M.3100 was approved on 29 April 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. This edition includes the modifications introduced by Corrigendum 1 to ITU-T

8、 Recommendation M.3100 (2005), approved on 13 November 2005 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. ITU-T Rec. M.3100 (04/2005) ii FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunicat

9、ions. 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 basis. The World Telecommunicatio

10、n 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 Resolution 1. In some areas of info

11、rmation 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 and a recognized operating age

12、ncy. 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 met. The words “shall“ or some

13、 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 possibility that the practice or i

14、mplementation 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 Recommendation development pro

15、cess. 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 may not represent the latest information and are therefore strong

16、ly urged to consult the TSB patent database. ITU 2005 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. M.3100 (04/2005) iii CONTENTS Page 1 Scope 1 1.1 Purpose . 1 1.2 Field of application. 1 2 Refere

17、nces. 2 3 Definitions 2 3.1 General definitions . 2 3.2 Alarm report-related definitions. 2 3.3 ARC state definitions . 3 4 Abbreviations 3 5 Conventions 4 6 Overview of the model . 5 6.1 Network fragment. 6 6.2 Managed element fragment 7 6.3 Physical equipment fragment . 8 6.4 Logical equipment fra

18、gment. 8 6.5 Termination point fragment Network element view . 9 6.6 Termination point fragment Network view. 9 6.7 Topology and connectivity fragment Network view. 10 6.8 Telemetry fragment 11 6.9 Transmission fragment . 11 6.10 Cross-connection fragment. 12 6.11 Functional area fragment 12 7 GDMO

19、definitions 12 8 ASN.1 modules. 12 9 TMN application context 13 Annex A Index 13 A.1 Managed objects. 13 A.2 Packages . 15 A.3 Attributes 18 A.4 Notifications . 22 A.5 Actions 22 A.6 Parameters 23 A.7 Name bindings 24 Annex B Network level model methodology . 27 Annex C Telemetry fragment . 28 Annex

20、 D Circuit pack fragment 29 iv ITU-T Rec. M.3100 (04/2005) Page Annex E Generic protection fragment 29 E.1 Protection Group R2. 29 E.2 Protection Unit R1 31 E.3 Example protection applications 38 Annex F Generic alarm reporting control (ARC) feature. 40 F.1 Business requirements 40 F.2 Analysis 42 F

21、.3 Design. 52 Annex G Bridge-and-roll cross-connect feature . 57 G.1 Business requirements 57 G.2 High-level use cases . 57 G.3 Analysis 59 Annex H Enhanced cross-connect feature 65 H.1 Business requirements 65 H.2 High-level use cases . 65 H.3 Analysis 68 H.4 Design. 69 Annex I Attribute value rang

22、es feature. 69 Annex J Generic transport TTP feature 71 Appendix I User guidelines. 72 I.1 Introduction 72 I.2 Use of supported by object list . 72 I.3 Use of upstream and downstream connectivity pointers 72 I.4 Use of cross-connection objects . 75 I.5 Cross-connection use examples 75 I.6 Object cla

23、sses and logical layering. 80 I.7 Mandatory naming attribute . 80 I.8 Interoperability between ITU-T Rec. M.3100 (1992) and this Recommendation 80 I.9 Support for multipoint trails . 81 I.10 Use of topological link . 81 I.11 System initialization . 82 I.12 Use of equipmentHolder acceptableCircuitPac

24、kList attribute . 82 Appendix II User guidelines Network topology 83 II.1 Inter-layer relationship alternatives 83 II.2 Intra-layer topology alternatives. 84 II.3 Example #1. 84 II.4 Example #2. 85 ITU-T Rec. M.3100 (04/2005) v Page Appendix III Alarm Report Control (ARC) Additional considerations 8

25、6 III.1 Business requirement considerations . 86 III.2 GDMO/ASN.1 design considerations 87 Electronic attachment: GDMO definitions (clause 7) ASN.1 modules (clause 8) ITU-T Rec. M.3100 (04/2005) 1 ITU-T Recommendation M.3100 Generic network information model 1 Scope This Recommendation provides a ge

26、neric 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-independent level; or are super-classes of technology-specific managed objects in a telecommunication

27、 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 the M.3010 TMN architecture 1. This Recommendation addresses generically the abstractions of th

28、ose aspects of telecommunication resources (e.g., equipments, telecommunication services) required to manage the network. It also includes the abstractions related to the management services. ITU-T Rec. G.803, on the architecture of the transport network, is used as the basis in developing the trans

29、port aspects of this model. This Recommendation does not address abstractions relevant to technology-specific areas or implementation-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-speci

30、fic areas, such as switching and transmission. One purpose of this Recommendation is to provide a vehicle for management interoperability between such systems. 1.1.2 Technology-independent management By introducing the concept of technology-independent management, it is possible to perform managemen

31、t of diverse equipment using common communication interfaces. In this manner, an “abstract“ view over a set of network-elements can be achieved. 1.1.3 Facilitating information model development This Recommendation also provides a framework from which technology-specific information models may be dev

32、eloped using the modelling principles defined in ITU-T Rec. X.720 2. 1.2 Field of application This Recommendation captures the generally applicable requirements of the technology-independent and technology-specific information models as well as information relating to TMN management services. Throug

33、h specialization, this Recommendation is applicable to technology-specific TMN information models. The mechanism for specialization is inheritance. Even though technology-specific models may be derived from this Recommendation, some of the generic managed object classes in this Recommendation are in

34、stantiable in order to provide interoperability between equipment supporting information models derived from this Recommendation and equipment that only supports the information model in this Recommendation. 2 ITU-T Rec. M.3100 (04/2005) 2 References The following ITU-T Recommendations and other ref

35、erences 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 encouraged to in

36、vestigate 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. The reference to a document within this Recommendation does not give it, as a stand-alone document, the

37、status of a Recommendation. 1 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. 2 ITU-T Recommendation X.720 (1992) | ISO/IEC 10165-1:1993, Information technology Open Systems Interconnection Structure of management information: Management information model.

38、 3 ITU-T Recommendation X.722 (1992) | ISO/IEC 10165-4:1992, Information technology Open Systems Interconnection Structure of management information: Guidelines for the definition of managed objects. 4 ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002, Information technology Abstract Syntax No

39、tation One (ASN.1): Specification of basic notation. 5 ITU-T Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, Information technology Open Systems Interconnection Structure of management information: Definition of management information. 6 ITU-T Recommendation G.803 (2000), Architecture of transpo

40、rt networks based on the synchronous digital hierarchy (SDH). 7 ITU-T Recommendation Q.821 (2000), Stage 2 and Stage 3 description for the Q3 interface Alarm surveillance. 8 ITU-T Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, Information technology Open Systems Interconnection Systems manageme

41、nt: Event report management function. 3 Definitions This Recommendation defines the following terms: 3.1 General definitions 3.1.1 management interface: Any managed entity interface that is defined for the purpose of management (e.g., OS interface, craft interface, LED indicator). 3.1.2 managed enti

42、ty: 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.3 managed resource: A specific component of a managed system/managed application (e.g., a specific circuit pack, termination point). 3.1.

43、4 managed resource-specific/unit audible/visual indicator: An audible/visual alarm indicator that is specific to a single managed resource. 3.2 Alarm report-related definitions 3.2.1 alarm reporting: Process of alerting, for the purposes of management, external systems and users regarding alarms. IT

44、U-T Rec. M.3100 (04/2005) 3 3.2.2 aggregate audible/visual indicators: An audible/visual alarm indicator that reflects information about a set of managed resources. 3.2.3 alarm reporting control: Involves the turning off of alarm reporting which includes inhibiting new autonomous alarm indication no

45、tification, and inhibiting the use of managed resource-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

46、reporting “off“ is supported by the “NALM-QI“, “NALM-TI“, and “NALM“ states. 3.2.4 ARC interval: Generic term that applies to both the persistence and timed intervals. 3.2.5 inhibited: This term is used throughout this feature description to identify that reporting is off (or in other words, is not

47、allowed). 3.2.6 persistence interval: A period of time for which a managed entity must be free of qualified problems. 3.2.7 timed interval: A period of time. 3.2.8 qualified problem: A problem that affects the operability of the managed entity and used to qualify transitions between the “NALM-NR“ an

48、d “NALM-CD“ states. Additional detail for this definition is managed resource specific and is to be defined by the managed resource. 3.3 ARC state definitions 3.3.1 ALM: ALarM reporting: Alarm Reporting is turned on. 3.3.2 NALM: No ALarM reporting: Alarm Reporting is turned off. 3.3.3 NALM-TI: No AL

49、arM reporting, Timed Inhibit: Alarm Reporting is turned off for a specified timed interval. 3.3.4 NALM-QI: No ALarM reporting; Qualified Inhibit: Alarm Reporting is turned off until the managed entity is qualified problem-free for a specified persistence interval. 3.3.5 NALM-CD: No ALarM reporting, CountDown: This is a substate of NALM-QI and performs the persistence timing countdown function when the managed entity is qualified problem-free. 3.3.6 NALM-NR: No ALarM reporting, NotReady: This is a subs