Transmission and Multiplexing (TM); Management of Synchronous Digital Hierarchy (SDH) transmission equipment; Fault management and performance monitoring; Functional description

Functional specification for all management aspects fo SDH equipment and the mapping between the atomic functions and the information model.

Prenos in multipleksiranje (TM) – Upravljanje prenosne opreme sistema sinhrone digitalne hierarhije (SDH) – Obvladovanje okvar in lastnosti – Funkcijski opis

General Information

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Standard

Standard
SIST EN 301 167 V1.1.1:2003
English language
33 pages
sale 10% off
Preview
sale 10% off
Preview

e-Library read for
1 day

Standards Content (sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Prenos in multipleksiranje (TM) – Upravljanje prenosne opreme sistema sinhrone digitalne hierarhije (SDH) – Obvladovanje okvar in lastnosti – Funkcijski opisTransmission and Multiplexing (TM); Management of Synchronous Digital Hierarchy (SDH) transmission equipment; Fault management and performance monitoring; Functional description33.040.20Prenosni sistemTransmission systemsICS:Ta slovenski standard je istoveten z:EN 301 167 Version 1.1.1SIST EN 301 167 V1.1.1:2003en01-december-2003SIST EN 301 167 V1.1.1:2003SLOVENSKI

STANDARD
SIST EN 301 167 V1.1.1:2003

EN 301 167 V1.1.1 (1998-08)European Standard (Telecommunications series)Transmission and Multiplexing (TM);Management of Synchronous Digital Hierarchy (SDH)transmission equipment;Fault management and performance monitoring;Functional descriptionSIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)2ReferenceDEN/NA-042137 (at000ico.PDF)Keywordsmanagement, SDH, TMN, transmission, transportETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00

Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)3ContentsIntellectual Property Rights................................................................................................................................5Foreword............................................................................................................................................................51Scope........................................................................................................................................................62Normative references...............................................................................................................................63Abbreviations...........................................................................................................................................74Fault management....................................................................................................................................84.1Purpose..............................................................................................................................................................84.2Additional definitions........................................................................................................................................84.2.1Functional architecture.................................................................................................................................94.2.2Alarm information description and management..........................................................................................94.3Time stamping.................................................................................................................................................115Performance monitoring.........................................................................................................................115.1General principles............................................................................................................................................115.1.1Generic definition of the block...................................................................................................................115.1.2In-service monitoring.................................................................................................................................115.1.3Out-of-service monitoring..........................................................................................................................115.1.4Error performance events and parameters..................................................................................................125.1.4.1Determination of error performance events and parameters.................................................................125.1.5Definition of unavailability........................................................................................................................145.1.6Unavailability parameters...........................................................................................................................145.1.7Performance data collection.......................................................................................................................145.1.7.1Data collection for maintenance purposes............................................................................................155.1.7.2Data collection for error performance purposes...................................................................................155.1.7.3Performance monitoring history...........................................................................................................155.1.8Performance filtering and thresholding......................................................................................................185.1.8.115-minute treatment..............................................................................................................................185.1.8.224 hour treatment..................................................................................................................................185.1.9Synchronous Equipment Management Function (SEMF)..........................................................................205.1.10Maintenance thresholds..............................................................................................................................215.1.11Time-stamping...........................................................................................................................................215.1.12Additional performance events and parameters..........................................................................................215.2Performance monitoring of SDH paths............................................................................................................225.2.1Block definition..........................................................................................................................................225.2.2Error performance parameters....................................................................................................................225.2.3Events and parameters determination.........................................................................................................235.2.3.1Anomalies.............................................................................................................................................235.2.3.2Defects..................................................................................................................................................235.2.3.3Determination of the performance events.............................................................................................235.2.4Unavailability of path.................................................................................................................................245.2.4.1Criteria for a uni-directional path.........................................................................................................245.2.4.2Criteria for a bi-directional path...........................................................................................................245.2.5Data management.......................................................................................................................................245.2.5.1Performance monitoring history...........................................................................................................245.2.5.2Error performance evaluation...............................................................................................................255.2.5.3Unavailability management..................................................................................................................255.2.6Maintenance thresholds configuration........................................................................................................255.2.6.115-minute thresholds............................................................................................................................255.2.6.224-hour thresholds................................................................................................................................265.3Performance monitoring of multiplex sections................................................................................................265.3.1Block definition..........................................................................................................................................265.3.1.1Block definition for STM-N sections (1 £N £ 16)...............................................................................265.3.1.2Block definition for STM-64 section....................................................................................................265.3.1.3Block definition for STM-0 section......................................................................................................26SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)45.3.1.4Block sizes............................................................................................................................................265.3.2Error performance events...........................................................................................................................265.3.3Events determination for multiplex sections..............................................................................................275.3.3.1Anomalies.............................................................................................................................................275.3.3.2Defects..................................................................................................................................................275.3.3.3Determination of the performance events.............................................................................................275.3.4Unavailability of multiplex section............................................................................................................285.3.5Data management.......................................................................................................................................285.3.5.1Performance monitoring history...........................................................................................................285.3.5.2Unavailability management..................................................................................................................285.3.6Maintenance thresholds configuration........................................................................................................285.3.6.115-minute thresholds............................................................................................................................285.3.6.224-hour thresholds................................................................................................................................295.4Performance management of regenerator sections...........................................................................................295.4.1Block definition..........................................................................................................................................295.4.1.1Block definition applicable to STM-1..................................................................................................295.4.1.2Block definition applicable to STM-N (4£N£64)................................................................................295.4.1.3Block definition applicable to bit rates STM-0....................................................................................295.4.1.4Block sizes............................................................................................................................................295.4.2Error performance events...........................................................................................................................305.4.3Events determination for regenerator sections...........................................................................................305.4.3.1Anomaly...............................................................................................................................................305.4.3.2Defects..................................................................................................................................................305.4.3.3Determination of the performance events.............................................................................................305.4.4Unavailability of regenerator section.........................................................................................................315,4.5Data management.......................................................................................................................................315.4.5.1Performance monitoring history...........................................................................................................315.4.5.2Unavailability management..................................................................................................................315.4.6Maintenance thresholds configuration........................................................................................................325.4.6.115-minute thresholds............................................................................................................................325.4.6.224-hour thresholds................................................................................................................................32History..............................................................................................................................................................33SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee NetworkAspects (NA).The present document specifies the fault management and performance monitoring aspects of the Synchronous DigitalHierarchy (SDH) transmission equipments.National transposition datesDate of adoption of this EN:7 August 1998Date of latest announcement of this EN (doa):30 November 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 May 1999Date of withdrawal of any conflicting National Standard (dow):31 May 1999SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)61ScopeThe present document specifies the functional requirements for fault management and performance monitoring aspectsof SDH equipments.The Telecommunications Management Network (TMN) provides management functions which cover the planning,installation, operations, administration, maintenance and provisioning of telecommunications networks and services.ITU-T Recommendation M.3010 [1] proposes five management functional areas identified as follows:-Fault management;-Performance management;-Configuration management;-Security management;-Accounting management.The present document provides guidance and supporting information for the functional specification for the first two ofthese management areas.The TMN functionality is realized by means of processes in Equipment Management Function (EMF) in NetworkElements (NE), Element Management Systems (EMS) and Network Management Systems (NMS) or OperationSystems (OS).The present document fully specifies the EMF functionalities. NMS/OS functionalities are described only if needed forclarification.2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]ITU-T Recommendation M.3010: "Principles for a Telecommunications management network".[2]ITU-T Recommendation M.20: "Maintenance philosophy for telecommunications networks".[3]ETS 300 417: "Generic functional requirements for Synchronous Digital Hierarchy (SDH)equipment".[4]ITU-T Recommendation M.3100: "Generic network information model".[5]ITU-T Recommendation X.733: "Data networks and open system communications OSImanagement. Information technology – Open Systems Interconnection – Systems Management:Alarm reporting function".SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)7[6]ITU-T Recommendation X.734: "Data networks and open system communications OSImanagement. Information technology – Open Systems Interconnection – Systems Management:Event report management function".[7]ITU-T Recommendation X.735: "Data networks and open system communications OSImanagement. Information technology – Open Systems Interconnection – Systems Management:Log control function".[8]ITU-T Recommendation G.826: "Error performance parameters and objectives for international,constant bit rate digital paths at or above the primary rate".[9]ETS 300 416: "Availability performance of path elements of international paths".[10]ITU-T Recommendation M.2120: "PDH path, section and transmission system and SDH path andmultiplex section fault detection and localization procedures".[11]ITU-T Recommendation M.2101: "Performance limits for bringing-into-service and maintenanceof international SDH paths, sections and transmission systems".[12]EN 301 129: "Transmission and Multiplexing (TM); Digital Radio Relay Systems (DRRS);Synchronous Digital Hierarchy (SDH); System performance monitoring parameters of SDHDRRS".[13]ITU-T Recommendation G.707: "Network node interface for the synchronous digital hierarchy(SDH)".[14]ITU-T Recommendation M.2110: "Bringing-into-service of international PDH paths, sections andtransmission systems and SDH paths and multiplex sections".[15]ITU-T Recommendation G.783: "Characteristics of synchronous digital hierarchy (SDH)equipment functional blocks".[16]ITU-T Recommendation G.784: "Synchronous digital hierarchy (SDH) management".3AbbreviationsFor the purposes of the present document, the following abbreviations apply:AISAlarm Indication SignalARAvailability RatioAUAdministrative UnitBBEBackground Block ErrorBBERBackground Block Error RatioBIPBit Interleaved ParityCSESConsecutive SESEBErrored BlockEDCError Detection CodeEMFEquipment Management FunctionENEuropean NormeESErrored SecondESRErrored Second RatioFE BBEFar-End Background Block ErrorFE ESFar-End Errored SecondFE SESFar-End Severely Errored SecondFFSFor Further StudyHPHigh order PathLOFLoss Of FrameLOMLoss Of MultiframeLOPLoss Of PointerLOSLoss Of SignalLPLow order PathSIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)8MOMean time between digital path OutageMPManagement PointMSMultiplex SectionNENetwork ElementNE BBENear-End Background Block ErrorNE ESNear-End Errored SecondNE SESNear-End Severely Errored SecondNMSNetwork Management SystemOIOutage IntensityOSOperation SystemPJEPointer Justification EventPLMPath Label MismatchPSProtection SwitchPSCProtection Switch CountPSDProtection Switch DurationRDIRemote Defect IndicationREIRemote Error IndicationRSRegenerator SectionSDHSynchronous Digital HierarchySEMFSynchronous Equipment Management FunctionSESSeverely Errored SecondSESRSeverely Errored Second RatioSTM-nSynchronous Transfer Module nTMNTelecommunication Management NetworkVCVirtual ContainerUNEQUnequippedUTCUniversal Time Co-ordinated4Fault managementFault management is a set of functions which enables the detection, isolation and correction of abnormal operation of thetelecommunication network and its environment.4.1PurposeThis subclause describes the generic process of alarm handling in SDH network element.4.2Additional definitionsThese definitions have been derived from ITU-T Recommendation M.20 [2].fault: A fault is the inability of a function to perform a required action. This does not include an inability due topreventive maintenance, lack of external resources, or planned actions.anomaly: The smallest discrepancy which can be observed between the actual and desired characteristics of an item.The occurrence of a single anomaly does not constitute an interruption in the ability to perform a required function.Anomalies are used as the input for the performance monitoring process and for the detection of defects.defect: The density of anomalies has reached a level where the ability to perform a required function has beeninterrupted. Defects are used as input for performance monitoring, the control of consequent actions, and thedetermination of Fault Cause (FC).fault cause: A single disturbance or fault may lead to the detection of multiple defects. A FC is the result of acorrelation process which is intended to pinpoint the defect that is representative of the disturbance or fault that iscausing the problem.failure: The FC persisted long enough to consider the ability of an item to perform a required function to be terminated.The item may be considered as failed; a fault has now been detected.SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)9alarm: A human observable indication that draws attention to a failure (detected fault) usually giving an indication ofthe severity of the fault.4.2.1Functional architectureThe functional architecture is depicted in figure 1.Anomaly processing, defect filtering, consequent action functional blocks are defined in ETS 300 417 [3].Fault cause persistency, which allows the NE to wait a certain amount of time before to entering in the failure state andtherefore it conditions the generation of alarms. The persistency time needed to declare a failure is settable independence of defect characteristics (toggling, stable, ...). Only a defect which passes that filter could be subsequentlyreported as an alarm.A failure shall be declared if the fault cause persists continuously for X seconds. The failure shall be cleared if the faultcause is absent continuously for Y seconds. X and Y shall be within the range between 100 ms and 30 s in steps of Z ms.The incremental value Z shall follow a logarithmic scale (for further study). It is recommended that X < = Y.Severity assignment, which is used to assign the management perception of the severity of a Fault which could dependon the service dependency of the fault, a non service affecting Fault will be alarmed with a severity of Warning orMinor, while a service affecting fault will be reported with a severity of Major or Critical. A service independent faultwill be alarmed with any value of the severity. This is an information that is provided by the OS (refer toITU-T Recommendation. M.3100 [4]).Station alarm, represents the synthesis of alarm for purpose of audible and visual indication to a human operator in thestation. Station alarms can be suppressed by management operations.Unit alarm represents the synthesis of alarm on replaceable unit basis, the unit could be a board, sub-rack, etc.Alarm notification, represents the ability to generate alarm. For more details refer toITU-T Recommendation. X.733 [5].Alarm filtering, which is used to filter the alarm depending on the contents of the alarm such as the type and cause ofthe alarm, the source of the alarm, the severity, the correlation information etc. prior to report and/or log alarms. Alarmfiltering is different for logging and reporting.Alarm logging and alarm reporting. alarm reporting allows the reporting of those alarms which have passed the alarmfiltering process to a single or multiple destinations. for more details refer to ITU-T Recommendation.X.734 [6] andITU-T Recommendation. X.735 [7].4.2.2Alarm information description and managementThis subclause aims to classify alarms in terms of severity, type, probable cause, etc. Furthermore, basic principles ofalarm management should be identified.The above issues need further study.SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)10Alarm LoggingAlarm ReportingAlarm NotificationFault Persistency ProcessingDefect FilteringDefect CorrelationSeverity Assigment

MessageCommunication

FunctionConsequent actionFunctional BlockSEMFQ InterfaceFailureFault CauseDefectAnomalyF1F3F4F2Alarm FilteringAlarm FilteringStation AlarmUnit AlarmPotential Alarm ReportAlarm ReportFigure 1: Fault managementSIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)114.3Time stampingFault cause notification implies the time-stamping of its activation/deactivation time. The stamped time shall be the oneindicated by the local real time clock of NE. The time-stamping shall have a resolution of one second with respect to theNE clock. The relationship between the time given by a particular NE and the Universal Time Co-ordinated (UTC) isfor further study.5Performance monitoringPerformance monitoring is important part of the performance management, that provides functions to evaluate andreport upon the behaviour of telecommunication equipment and the effectiveness of the network or network element. Itsrole is to provide information for maintenance purposes and for network error performance evaluation.The performance monitoring requirement is generic in that it defines the parameters for paths and sections independentof the physical transport network providing the paths.ITU-T Recommendation. G.826 [8] defines error performance parameters and objectives for international digital pathsat or above the primary rate. It is worthwhile noticing that ITU-T Recommendation. G.826 [8] is only applicable to pathlayer and no direct allocation of the objectives can be derived for NEs.All the SDH equipments are described in terms of functional blocks, so a minimum set of parameters common to allequipments will be used.5.1General principles5.1.1Generic definition of the blockThe error performance parameters are based upon the measurement of blocks defined as follows:A block is a set of consecutive bits associated with the path and the section; each bit belongs to one and only one block.Consecutive bits may not be contiguous in time.Subclauses 5.2.1, 5.3.1 and 5.4.1 contain definition of block sizes for paths, multiplex and regenerator sections.5.1.2In-service monitoringEach block is monitored by means of an inherent Error Detection Code (EDC), e.g. Bit Interleaved Parity (BIP). TheEDC bits are physically separated from the block to which they apply. If there is a discrepancy between the EDC and itscontrolled block, it is always assumed that the controlled block is in error, because usually it is not possible to determinewhether a block or its controlling EDC is in error.Estimation of errored blocks on an in-service basis is dependent upon the type of EDC available.5.1.3Out-of-service monitoringThe out-of-service monitoring can be used for Bringing-Into-Service (BIS) purposes of trails. The description of BIS isrecommended in ITU-T M-Series recommendations and it is outside of the scope of the present document.The out-of-service monitoring can be performed by using the same approach as for the in-service monitoring.SIST EN 301 167 V1.1.1:2003

ETSIEN 301 167 V1.1.1 (1998-08)125.1.4Error performance events and parametersError performance parameters are evaluated from the following error performance events:-EB - Errored Block. A block in which one or more bits are in error.-ES - Errored Second. A one-second period with at least one errored block or at least one defect.-SES - Severely Errored Second. A one-second period which contains ³ X % errored blocks or at least onedefect. An SES is also an ES.-BBE - Background Block Error. An errored block not occurring as part of an SES.The defects and performance criteria are listed in the relevant sections. The value of X is given in subclause 5.2.2 forPath, in subclause 5.3.2 for Multiplex Section (MS) and subclause 5.4.2 for Regenerator Section(RS).The error performance parameters are:-ESR - Errored Second

...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.