1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STAN DARD IZATION SECTOR OF ITU M.2140 (02/2000) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS I n te rn a t io n a I transport network Transport n
2、etwork event correlation ITU-T Recommendation M.2140 (Formerly CCITT Recommendation) ITU-T M-SERIES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and general principles of maintenance and ma
3、intenance organization International transmission systems M.300-M.55 9 International telephone circuits M.560-M.759 Common channel signalling systems M.760-M.799 International telegraph systems and phototelegraph transmission M.800-M.899 International leased group and supergroup links M.900-M.999 In
4、ternational leased circuits M. 1000-M. 1099 Mobile telecommunication systems and services M. 1 100-M. 1 199 International public telephone network M. 1200-M. 1299 International data transmission systems M.1300-M.1399 Designations and information exchange M.1400-M.1999 M. 10-M.299 I- Integrated servi
5、ces digital networks M.3600-M.3999 Common channel signalling systems M.4000-M.4999 For further details, please refer to the list of ITU-T Recornmendations ITU-T Recommendation M.2140 Transport network event correlation Summary This ITU-T Recommendation is a functional description of the operations f
6、unctions required to achieve Network Event Correlation in the surveillance of international transport networks. The capability described is to correlate notifications of faults and impairments fi-om Network Elements and to reveal the nature, location and severity of the faults and impairments and th
7、eir true effect on the network. This Recommendation is based on the TMN Functional Architecture as specified in ITU-T Recommendation M.30 1 O. This Recommendation identifies the TMN Management Function Sets from ITU-T Recommendation M.3400 that are involved in Transport Network Event Correlation, pr
8、ovides functional descriptions of each Management Function Set, and illustrates how they interact to achieve Transport Network Event Correlation. Source ITU-T Recommendation M.2140 was prepared by ITU-T Study Group 4 (1997-2000) and approved under the WTSC Resolution 1 procedure on 4 February 2000.
9、Keywords Alarm Correlation, Event Correlation, Fault Management, Functional Architecture, International Transmission Entities, Network Management, Performance Management, Surveillance, Telecommunications Management Network (TMN). FOREWORD The International Telecommunication Union (ITU) is the United
10、 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 technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommu
11、nications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), 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 pro
12、cedure laid down in WTSC 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 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a tel
13、ecommunication administration and a recognized operating agency. 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 Property Right. ITU takes no position concerning the evidence,
14、 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 of intellectual property, protected by patents, which may be
15、 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 TSBpatent database. o ITU 2001 All rights reserved. No part of this publication may be reproduced or utilized in any form
16、 or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU. CONTENTS 1 2 3 4 5 5.1 5.2 5.3 5.4 6 7 7.1 7.2 7.3 7.4 7.5 7.6 7.7 8 8.1 Scope References Terms and definitions . Abbreviations . Principles Event correlation processes 5.1.2 Com
17、parison of events 5.1.3 Persistence analysis . 5.1.4 Dependencies 5.1.5 Patterning Generic event correlation model . 5.2.1 Stage O . 5.2.2 Stage 1 . 5.2.3 Stage 2 . 5.2.4 Stage 3 . 5.2.5 Stage 4 . 5.1.1 Selection of events Surveillance operations flows . Implementation considerations . The transport
18、 network event correlation MAF interaction diagram . Performance management Detection. counting. storage and reporting . NE(s) performance characterization . Performance monitoring data accumulation . NE(s) trend analysis . Data aggregation and trending NE(s) TCA processing . 7.6.1 TCA correlation r
19、ules 7.6.2 Persistence analysis . Network performance monitoring event correlation and filtering 7.7.1 7.7.2 Correlation of impairment indications among related trails 7.7.3 Correlation of trend indications with impairment indications Correlation of impairment indications along a trail Fault managem
20、ent Failure event detectionand reporting . Page 1 1 1 2 3 3 3 3 4 5 6 6 7 7 7 7 7 8 10 10 14 15 15 15 16 16 16 17 17 18 18 18 18 19 19 8.2 8.3 8.4 8.5 9 9.1 9.2 Alarm reporting 8.2.1 Equipment faults . 8.2.2 Communication faults . 8.2.3 Environmental conditions . Alarm correlation and filtering . 8.
21、3.1 8.3.2 8.3.3 8.3.4 8.3.5 8.3.6 8.3.7 Processing of equipment alarms Processing of communication alarms Processing of environmental alarms . Processing of state changes . Correlation of alarms among related trails Persistence analysis . Declaring fault indications Network fault event analysis. inc
22、luding correlation and filtering 8.4.1 Correlation of fault indications along a trail . 8.4.2 Correlation of fault indications among related trails . Network fault localization 8.5.1 Patterning of indications Correlation of indications among related resources . 8.5.2 Configuration management Notific
23、ation of state changes by NEs . 9.2.1 Operational state changes 9.2.2 Administrative state changes . NE(s) status and control . Page 19 20 20 20 20 21 21 21 22 22 22 23 23 23 23 24 24 25 25 25 25. 25 26 Introduction Planning, developing and supporting operations functions in Network Elements (NEs) a
24、nd management systems, and linking them together via well-defined open interfaces, are critical steps to introducing new technologies and services into the network and providing network operations support across boundaries between network/service providers. One of the key areas for networkkervice pr
25、oviders to automate with management systems supporting open interfaces is the area of service assurance. Service assurance is increasingly driven by the ability of the network to detect and report service affecting conditions before the customer reports a trouble. The network provides a wealth of in
26、formation about its performance and the occurrence of service affecting conditions. Existing Operations Systems can process this information to some degree, but not completely, and rarely across different layers of a layered network or across traditional operations centre boundaries. As a result, se
27、rvice assurance today requires significant manual effort to properly interpret the information reported by NEs. The key to driving cost out of service assurance and improving its response time is to further automate the interpretation and correlation of events in complex layered networks. The intend
28、ed audience of this Recommendation includes: O network operators interested in deploying management systems that perform Network Event Correlation within a TMN (operations and maintenance planners, transport network maintenance staff); Correlation, including element management systems (systems engin
29、eers and software developers); TMN (systems engineers and software developers). a OS vendors interested in providing management systems that perform Network Event a NE suppliers needing to understand how notifications that NEs produce will be used by the Background TMN emphasizes the use of open, st
30、andard interfaces among management systems as well as between management systems and NEs. TMN also provides a logical framework for describing the Management Application Functions (MAFs) associated with the management of the network and the management of services supported by the network. ITU-T Reco
31、mmendation M.3400, TMN Managernent Functions, is a guide for planning and deploying the management systems necessary for timely and efficient management of networks and services. The Management Function Sets of M.3400 serve as atomic units of network management functionality. The Management Function
32、s in each set cannot easily stand alone. The Management Function Sets can stand alone or they can be packaged together into management systems at the discretion of networldservice providers. Each Management Function Set can be considered to be its own Management Application Function (MAF) as defined
33、 in ITU-T Recommendation M.3010. This Recommendation treats each Management Function Set as an MAF. The functional decomposition of operations functions into the MAFs that correspond to the Management Function Sets of ITU-T Recommendation M.3400 helps achieve consistency of functionality among Opera
34、tions Systems fi-om various suppliers used by different networldservice providers managing various network technologies. This functional consistency along with TMN open, standard interfaces (defined in ITU-T Recommendation M.30 1 O) allows interoperability between these Operations Systems and the ra
35、pid integration of new emerging technologies into a comprehensive Network Event Correlation capability. ITU-T Recommendation M.2140 Transport network event correlation 1 Scope The purpose of this Recommendation is the use of the Telecommunications Management Network (TMN) to correlate notifications
36、of conditions (faults and impairments) from Network Elements and to reveal the conditions themselves and their true effect on the network. This Recommendation is based on the TMN Functional Architecture as specified in ITU-T Recommendation M.3010 3. This Recommendation identifies the TMN Management
37、Application Functions (MAFs) corresponding to the Management Function Sets of ITU-T Recommendation M.3400 4 that are involved in Transport Network Event Correlation. It provides hctional descriptions of each MAF, and illustrates how these MAFs interact to achieve Transport Network Event Correlation.
38、 This Recommendation also includes timing criteria for event correlation. Transport Network Event Correlation relies on current configuration information fi-om Configuration Management MAFs. It also is controlled in the specifics of its operation by policies in Business Management Layer MAFs. These
39、interactions are mentioned in appropriate places, but are outside of the scope of this Recommendation. This Recommendation does not require the exchange of any particular operators information about its national network. Algorithms for event correlation are important to the successful implementation
40、 of the MAFs described in this Recommendation. Detailed specification of these algorithms is outside of its scope. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. All Recomme
41、ndations and other references are subject to revision; all 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 regular
42、ly published. 11 CCITT Recommendation M.20 (1 992), Maintenance philosophy for telecommunication networks. 2 ITU-T Recommendation M.60 (1993), Maintenance terminology and definitions. 3 ITU-T Recommendation M.301 O (2000), Princzples for a telecommunications management network. 4 ITU-T Recommendatio
43、n M.3400 (2000), TMN managementfunctions. 3 Terms and definitions This Recommendation defines the following terms: 3.1 active: Not cleared. 3.2 3.3 compute each stored measurement and detect maintenance threshold crossings. 3.4 clear: The end of a fault; the termination of a standing condition. data
44、 collection interval: The period over which performance parameters are accumulated to degradation: The presence of anomalies or defects in the absence of a fault. 3.5 event: An instantaneous occurrence that changes the global status of an object. This status change may be persistent or temporary, al
45、lowing for surveillance, monitoring and performance measurement functionality, etc. Events may or may not generate reports; they may be spontaneous or planned; they may trigger other events or may be triggered by one or more other events. (Recommendation M. 60 .) 3.6 event correlation process: A pro
46、cess that accepts events as input, performs one or more event correlation subprocesses, and reports events as output. 3.7 event correlation subprocess: A single step in an event correlation process (see 5.1 for the five types). 3.8 event report message: A message sent from one physical system to ano
47、ther that contains information about an event. 3.9 event set: The set of all events that are grouped by a selection process for direct comparison or patterning. 3.10 impairment: A condition that causes anomalies and defects without causing a failure (degrades the performance of a resource without ca
48、using a failure). 3.11 indication: An intermediate output of the event correlation process. A notification, indicating a persistent network detected trouble condition. The three types of indication are fault indication, impairment indication .and trend indication. 3.12 independent event: An event th
49、at is not currently superseded by another event. 3.13 notification: Information emitted by a managed object relating to an event that has occurred within the managed object (Recommendations M.60, X.710; Information passed from one MAF to another regarding an event). 3.14 standing condition: A condition that has duration, beginning with a failure and ending with a clear. 3.15 threshold crossing alert: A transient condition declared when a performance monitoring parameter reaches or exceeds a preset threshold. 3.16 transient condition: A condition that has no duration, a one time
