SIST EN 300 417-7-1 V1.1.1:2003

• Abstract:

  Functional requirements for auxiliary layers in equipment based on the principles described in part 1-1.

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.040.20 - Transmission systems
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI EN 300 417-7-1 V1.1.1 (2000-10) - Transmission and Multiplexing (TM); Generic requirements of transport functionality of equipment; Part 7-1: Equipment management and auxiliary layer functions

SIST EN 300 417-7-1 V1.1.1:2003 is the Slovenian adoption of EN 300 417-7-1 Version 1.1.1, published by SIST. It specifies equipment management and auxiliary layer functions for Transmission and Multiplexing (TM) equipment, so engineers, quality managers and buyers can see which management, performance monitoring, configuration, DCC and V11 functions a compliant network element may implement.

What does SIST EN 300 417-7-1 V1.1.1:2003 specify?

SIST EN 300 417-7-1 V1.1.1:2003 specifies a library of basic building blocks and combination rules for transport functionality and equipment management function (EMF) functionality in equipment. It is organized around clauses for scope, references, definitions, the equipment management function, DCC layer functions and V11 section layer functions, plus informative annexes A to C.

The document focuses on SDH and PDH transport equipment and on the management functions that sit around those layers. The generic functionality is described in EN 300 417-1-1, while this part adds the equipment management and auxiliary-layer pieces that support practical operation.

Annex	What it covers
Annex A	Applications and topologies of performance monitoring
Annex B	Examples of some performance monitoring packages
Annex C	Use of NPME/FPME when G.826 and M.2100/M.2101 packages are selected together

What are the key requirements of SIST EN 300 417-7-1 V1.1.1:2003?

SIST EN 300 417-7-1 V1.1.1:2003 defines how an equipment-level manager interacts with transport atomic functions through management information points, and how the EMF reduces and reports that information. In practice, this is the part that turns raw defect and performance signals into alarms, counters, thresholds and configuration actions.

Time, fault handling and alarms

Clause 4.1 defines the Network Element Real Time Clock (NE-RTC). It provides date and time with 1 second resolution, can be set by SET-RTC, and is aligned to UTC on a regular basis. That matters because all performance timestamps and interval boundaries depend on a consistent time base.

Clause 4.2 defines fault management filters. A failure is declared only after a fault cause persists continuously for 2.5 seconds, and it is cleared after 10 seconds without the fault cause. That prevents short transients from becoming operational alarms.

Clause 4.2 also assigns severity to faults and distinguishes unit alarms, network element alarms and station alarms. The document points to X. series severity schemes and the M.20 scheme, so implementers can map technical defects to the alarm style used in their network.

Performance monitoring

Clause 4.4 defines the performance monitoring functions. SIST EN 300 417-7-1 V1.1.1:2003 covers near-end and far-end event functions, availability filters, delay, history registers, thresholding and package combinations. In practice, equipment must count ES, SES, BBE, UAT/UAS and PJE in the right direction and on the right time base.

The availability filters suppress event counts during unavailable time and align event data with a 10 second delayed PM time base. The history functions store current and recent 15 minute and 24 hour values, which means the equipment needs register storage, timestamps and rollover behavior.

Thresholding is handled by single-level TR and dual-level TR/RTR mechanisms. The document says threshold crossing is detected within a defined reporting delay and that the threshold report carries a timestamp, so operators can see when a degradation started, not just that it happened.

The performance monitoring packages combine those blocks for specific use cases:

• M.2100 near-end and far-end maintenance packages for PDH
• M.2101 near-end and far-end maintenance packages for SDH
• G.826 bi-directional error performance packages at trail termination or at an intermediate node
• Pointer Justification Event monitoring for 24 hour counting

Configuration, synchronization and auxiliary layers

Clause 4.5 defines configuration management functions for protection switching, trace identifiers, payload and multiplex structures, matrix connections, DEG thresholds, port and termination point modes, defect reporting, 2 Mbit/s multiframe alignment and synchronization. In practice, this is the part used to provision how the equipment is built and how it reacts in service.

Clause 5 defines DCC layer functions and clause 6 defines V11 section layer functions. That gives the document a management channel and an electrical user-interface layer in addition to the transport functions.

What terms does SIST EN 300 417-7-1 V1.1.1:2003 define?

• Equipment Management Function (EMF) - The set of functions that manages network element behavior by exchanging management information with atomic transport functions.
• Network Element Real Time Clock (NE-RTC) - The internal clock that provides date and time for management timestamps and interval timing.
• Unavailable Time (UAT) - A period in which performance event counting is suppressed and availability-related outputs are zeroed.
• Near-end Performance Monitoring Event (NPME) - The function that derives near-end BBE, ES and SES from atomic performance primitives.
• Far-end Performance Monitoring Event (FPME) - The function that derives far-end BBE, ES and SES from the far-end performance primitives.
• Severely Errored Second (SES) - A performance event classification used in monitoring and thresholding, with layer-specific estimators.
• Pointer Justification Event (PJE) - A performance event counted over 24 hours for pointer justification activity.

Who uses SIST EN 300 417-7-1 V1.1.1:2003?

SIST EN 300 417-7-1 V1.1.1:2003 is used by network operators, equipment suppliers and integrators of SDH and PDH transmission equipment. They use it to decide which management, monitoring, protection, synchronization and auxiliary-layer functions a network element should support.

It is also useful for engineers and quality managers who need to compare vendor implementations, configure protection switching and synchronization behavior, or verify how alarms and performance data are generated and stored.

Which standards are used with SIST EN 300 417-7-1 V1.1.1:2003?

• EN 300 417-1-1 - Gives the generic processes, performance rules, definitions and combination rules used throughout the series.
• EN 300 417-4-1 and EN 300 417-6-1 - Provide the path-layer and synchronization-layer context used by the management functions.
• ETS 300 147, ETS 300 167 and ETS 300 337 - Contribute multiplexing structure, 2048 kbit/s interface characteristics and generic frame structures.
• ETS 300 304, EN 300 371, ETS 300 411, ETS 300 412, ETS 300 413, ETS 300 493, EN 301 155, EN 301 268, EN 301 384 and ES 202 098 - Provide the information models referenced for management application functions and performance monitoring.
• EN 301 167 - Gives the functional description for SDH fault management and performance monitoring from the network point of view.
• G.826, G.828, M.2100, M.2101, M.2101.1 and M.2120 - Define error performance objectives, maintenance limits and the monitoring behavior used by the performance packages.
• Q.822, Q.921 and V.11 - Contribute performance management, LAPD and electrical user-interface behavior.

What does the SIST EN 300 417-7-1 V1.1.1:2003 document contain?

SIST EN 300 417-7-1 V1.1.1:2003 contains process blocks, interface tables and figures for each atomic function, including the EMF, NE-RTC, fault management, performance monitoring, configuration management, DCC and V11 functions. It also includes tables for register sizing, SES estimators, threshold settings, protection parameters and synchronization behavior.

Annex A gives example topologies for performance monitoring at termination nodes and intermediate nodes. Annex B shows example performance monitoring packages, and Annex C explains how NPME and FPME can be shared or separated when G.826 and M.2100/M.2101 packages are selected together.

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.XQNFLRQDOQRVWWTransmission and Multiplexing (TM); Generic requirements of transport functionality of equipment; Part 7-1: Equipment management and auxiliary layer functions33.040.20Prenosni sistemTransmission systemsICS:Ta slovenski standard je istoveten z:EN 300 417-7-1 Version 1.1.1SIST EN 300 417-7-1 V1.1.1:2003en01-december-2003SIST EN 300 417-7-1 V1.1.1:2003SLOVENSKI
STANDARD
ETSIEN300417-7-1V1.1.1(2000-10)EuropeanStandard(Telecommunicationsseries)TransmissionandMultiplexing(TM);Genericrequirementsoftransportfunctionalityofequipment;Part7-1:EquipmentmanagementandauxiliarylayerfunctionsSIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)2ReferenceDEN/TM-01015-7-1Keywordsgeneric,SDH,PDH,transmissionETSI650RoutedesLuciolesF-06921SophiaAntipolisCedex-FRANCETel.:[phone]Fax:[phone]SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88ImportantnoticeIndividualcopiesofthepresentdocumentcanbedownloadedfrom:http://www.etsi.orgThepresentdocumentmaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshallbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.Usersofthepresentdocumentshouldbeawarethatthedocumentmaybesubjecttorevisionorchangeofstatus.InformationonthecurrentstatusofthisandotherETSIdocumentsisavailableathttp://www.etsi.org/tb/status/Ifyoufinderrorsinthepresentdocument,sendyourcommentto:[e-mail]opartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute2000.Allrightsreserved.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)3ContentsIntellectualPropertyRights.6Foreword.6Introduction.71Scope.82References.83Definitions,abbreviations,symbolsanddiagrammaticconventions.103.1Definitions.103.2Abbreviations.103.3Symbolsanddiagrammaticconventions.134Equipmentmanagementfunction.134.1NetworkElement-RealTimeClock(NE-RTC)Function.144.2FaultManagementFunctions.164.2.1Failurefilterf4.164.2.2Severityassignmentfilterf5.174.2.3Replaceableunitalarmfilterf6.174.2.4Networkelementalarmfilterf7.174.2.5Stationalarmfilterf8.174.3ManagementApplicationFunctions.174.4PerformanceMonitoringFunctions.174.4.1PerformancemonitoringclockfunctionPMC.204.4.2Performancemonitoringeventsfunctions.214.4.2.1Near-endperformancemonitoringeventfunction(NPME).214.4.2.2Far-endperformancemonitoringeventfunction(FPME).234.4.2.3Uni-directionalavailabilityfilterfunction(AvFu).254.4.2.4Bi-directionalavailabilityfilterfunction(AvFb).264.4.2.5Delayfilterfunction(Delay).274.4.3Performancemonitoringhistoryfunctions.284.4.3.1Current15mregisterfunction.284.4.3.2Recent15mregisterfunction.304.4.3.3Current24hregisterfunction.314.4.3.4Recent24hregisterfunction.334.4.3.5Begin/EndofUATeventgenerationfunction.344.4.3.6CSESlogfunction.344.4.4Performancemonitoringthresholdingfunctions.364.4.4.1Singlelevelthresholdingfunction(ThrFs).374.4.4.2Duallevelthresholdingfunction(ThrFd).394.4.5Performancemonitoringpackages.404.4.5.1ITU-TRecommendationsM.2100Near-end(A/Zdirection)maintenance(uni-directional)package.414.4.5.2ITU-TRecommendationsM.2100far-end(Z/Adirection)maintenance(uni-directional)package.424.4.5.3ITU-TRecommendationsM.2101Near-end(A/Zdirection)maintenance(uni-directional)package.434.4.5.4ITU-TRecommendations/M.2101far-end(Z/Adirection)maintenance(uni-directional)package.444.4.5.5ITU-TRecommendationG.826errorperformance(bi-directional)packageattrailtermination.454.4.5.6ITU-TRecommendationG.826errorperformance(bi-directional)packageatintermediatenodealongthetrail.464.4.5.7PointerJustificationEventpackage.474.5ConfigurationManagementFunctions.474.5.1Networkelementconfiguration.484.5.2Protectionswitchingprovisioning.484.5.2.1LinearSTM-NMSprotection.494.5.2.2STM-NMSSPringprotection.494.5.2.3Linear1+1SNCprotection.49SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)44.5.2.4Linear1+1VCTrailprotection.504.5.3Protectionswitchingstatusandcontrol.504.5.3.1LinearSTM-NMSprotection.504.5.3.2STM-NMSSPringprotection.504.5.3.3Linear1+1SNCprotection.514.5.3.4Linear1+1VCTrailprotection.514.5.4Traceidentifierprocessesprovisioningandreporting.514.5.5Payloadstructuresprovisioningandreporting.524.5.6Multiplexstructuresprovisioningandreporting.524.5.6.1AUGprovisioning.524.5.6.2AUGautonomousadaptation.534.5.6.3AUGreporting.534.5.6.4TUGprovisioning.534.5.6.5TUGreporting.534.5.7Matrixconnectionsprovisioning.544.5.8DEGthresholdssetting.564.5.9Portmode,TerminationPointmodeprovisioning.564.5.10AccessPointmodeprovisioning.564.5.11Defectreportingprovisioning.564.5.122Mbit/smultiframealignmentprovisioning.574.5.13Networkelementsynchronizationprovisioning.574.5.13.1QualityLevelmodeprovisioning.574.5.13.2TimingMarkermodeprovisioning.574.5.13.3SSMandTMsupportprovisioning.574.5.13.4SSMandTMdisablingprovisioning.584.5.13.5QloverwriteandQlfixedValueprovisioning.584.5.13.6CSidassignment.584.5.13.7QLminimumprovisioning.584.5.13.8NEclockbehaviour.584.5.13.9NSPriorityconfiguration.594.5.13.10NSLockoutcommands.594.5.13.11NSExternalcommands.594.5.13.12NSWaittorestoretime.594.5.13.13SelectSabitforSSMprovisioning.604.5.14PerformanceMonitoring15minuteand24hourTRandRTRthresholdsetting.605DCCLayerFunctions.615.1DCCconnectionfunctionDCC_C.626V11SectionLayerFunctions.636.1V11ConnectionfunctionV11_C.646.2V11TrailTerminationfunctions.646.2.1V11TrailTerminationSourceV11_TT_So.646.2.2V11TrailTerminationSinkV11_TT_Sk.656.3V11Adaptationfunctions.656.3.1V11toV0XAdaptationSourceV11/V0X_A_So.656.3.2V11toV0XAdaptationSinkV11/V0X_A_Sk.66SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)5AnnexA(informative):Applications/TopologiesofPerformanceMonitoring.67A.1Single-ended,bi-directionalperformancemonitoringarchitectureataterminationnode.67A.2Single-ended,bi-directionalperformancemonitoringarchitectureatanintermediatenode.68A.3Dualended,bi-directionalperformancemonitoringarchitectureatterminationnodes.69A.4Performancemonitoringarchitectureatanintermediatenodeforfaultlocalization.69A.5Singleended,bi-directionalTCMrelatedperformancemonitoringarchitectureataTCterminationnode.70A.6Singleended,bi-directionalTCMrelatedperformancemonitoringarchitectureatanintermediatenode.71AnnexB(informative):Examplesofsomeperformancemonitoringpackages.72AnnexC(informative):UseofNPME/FPMEfunctionswhenbothG.826andM.2100/M.2101packagesareselectedforoneterminationpoint.74Bibliography.77History.78SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinETSISR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinETSISR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeTransmissionandMultiplexing(TM).Thepresentdocumentisoneofafamilyofdocumentsthathasbeenproducedinordertoprovideinter-vendorandinter-operatorcompatibilityofSynchronousDigitalHierarchy(SDH)equipment.ThepresentdocumentisPart7-1ofamulti-partENcoveringthegenericrequirementsoftransportfunctionalityofequipment,asidentifiedbelow:Part1-1:"Genericprocessesandperformance";Part1-2:"GeneralinformationaboutImplementationConformanceStatement(ICS)proforma";Part2-1:"SynchronousDigitalHierarchy(SDH)andPlesiochronousDigitalHierarchy(PDH)physicalsectionlayerfunctions";Part2-2:"SynchronousDigitalHierarchy(SDH)andPlesiochronousDigitalHierarchy(PDH)physicalsectionlayerfunctions;ImplementationConformanceStatement(ICS)proformaspecification";Part3-1:"SynchronousTransportModule-N(STM-N)regeneratorandmultiplexsectionlayerfunctions";Part3-2:"SynchronousTransportModule-N(STM-N)regeneratorandmultiplexsectionlayerfunctions;ImplementationConformanceStatement(ICS)proformaspecification";Part4-1:"SynchronousDigitalHierarchy(SDH)pathlayerfunctions";Part4-2:"SynchronousDigitalHierarchy(SDH)pathlayerfunctions;ImplementationConformanceStatement(ICS)proformaspecification";Part5-1:"PlesiochronousDigitalHierarchy(PDH)pathlayerfunctions";Part5-2:"PlesiochronousDigitalHierarchy(PDH)pathlayerfunctions;ImplementationConformanceStatement(ICS)proformaspecification";Part6-1:"Synchronizationlayerfunctions";Part6-2:"Synchronizationlayerfunctions;ImplementationConformanceStatement(ICS)proformaspecification";Part7-1:"Equipmentmanagementandauxiliarylayerfunctions";Part7-2:"Auxiliarylayerfunctions;ImplementationConformanceStatement(ICS)proformaspecification".Parts2to7specifythelayersandtheiratomicfunctions.NOTE:TheSDHradioequipmentfunctionalblocksareaddressedbyETSIWGTM4.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)7VariousoftheabovepartshavepreviouslybeenpublishedaspartsofETS300417.TheyhavebeenconvertedintopartsofEN300417withouttechnicalchanges,butsomeeditorialchangeshavebeennecessary(e.g.references).Inparticular:-Parts2-1,2-2and3-2havebeenmodifiedtotakeaccountofeditorialerrorspresentinedition1;-Part1-1hashaditstitlechangetoalignwithotherpartspublishedatalaterdate.AlsonotethatinthemeantimeParts8-1and8-2togetherwithallPartsx-3(AbstractTestSuites)havebeenstopped.NationaltranspositiondatesDateofadoptionofthisEN:13October2000DateoflatestannouncementofthisEN(doa):31January2001DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31July2001DateofwithdrawalofanyconflictingNationalStandard(dow):31July2001IntroductionThepresentdocumentspecifiesforfaultmanagement,performancemonitoring,andconfigurationmanagementalibraryofbasicequipmentmanagementfunction(EMF)buildingblocksandasetofrulesbywhichtheyarecombinedinordertodescribeanequipment'sEMFfunctionality.ThelibrarydefinedinthepresentdocumentformspartofthesetoflibrariesdefinedfurthermoreintheotherpartsofEN300417.Inaddition,anumberofcompoundfunctionsconsistingofanumberofEMFbuildingblocksaredefined.NOTE:Noteveryfunctiondefinedinthepresentdocumentisrequiredforeveryapplication.Differentsubsetsoffunctionsmaybeassembledindifferentwaystoprovideavarietyofdifferentcapabilities.Networkoperatorsandequipmentsuppliersmaychoosewhichfunctionstoimplementforeachapplication.Inaddition,thepresentdocumentspecifiesfunctionsintheauxiliarylayers:DCClayerandV11sectionlayer.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)81ScopeThepresentdocumentspecifiesalibraryofbasicbuildingblocksandasetofrulesbywhichtheyarecombinedinordertodescribetransportandequipmentmanagementfunction(EMF)functionalityinequipment.ThelibrarycomprisesthefunctionalbuildingblocksneededtocompletelyspecifythegenericfunctionalstructureoftheEuropeanDigitalTransmissionHierarchy.Equipment,whichiscompliantwiththepresentdocument,willbedescribableasaninterconnectionofasubsetofthesefunctionalblockscontainedwithinthepresentdocument.Theinterconnectionsoftheseblockswillobeythecombinationrulesgiven.ThegenericfunctionalityisdescribedinEN300417-1-1[8].2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.• Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.• Foraspecificreference,subsequentrevisionsdonotapply.• Foranon-specificreference,thelatestversionapplies.• Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]ETSIETS300147(1997):"TransmissionandMultiplexing(TM);SynchronousDigitalHierarchy(SDH);Multiplexingstructure".[2]ETSIETS300167:"TransmissionandMultiplexing(TM);Functionalcharacteristicsof2048kbit/sinterfaces".[3]ETSIETS300304:"TransmissionandMultiplexing(TM);SynchronousDigitalHierarchy(SDH);SDHinformationmodelfortheNetworkElement(NE)view".[4]ETSIEN300371:"TransmissionandMultiplexing(TM);PlesiochronousDigitalHierarchy(PDH)informationmodelfortheNetworkElement(NE)view".[5]ETSIETS300411:"TransmissionandMultiplexing(TM);Performancemonitoring;InformationmodelfortheNetworkElement(NE)view".[6]ETSIETS300412:"TransmissionandMultiplexing(TM);PayloadConfiguration;InformationmodelfortheNetworkElement(NE)view".[7]ETSIETS300413:"TransmissionandMultiplexing(TM);Multiplexsectionprotection;InformationmodelfortheNetworkElement(NE)view".[8]ETSIEN300417-1-1:"TransmissionandMultiplexing(TM);Genericrequirementsoftransportfunctionalityofequipment;Part1-1:Genericprocessesandperformance".[9]ETSIEN300417-4-1:"TransmissionandMultiplexing(TM);Genericrequirementsoftransportfunctionalityofequipment;Part4-1:SynchronousDigitalHierarchy(SDH)pathlayerfunctions".[10]ETSIEN300417-6-1:"TransmissionandMultiplexing(TM);Genericrequirementsoftransportfunctionalityofequipment;Part6-1:Synchronizationlayerfunctions".[11]ETSIETS300493:"TransmissionandMultiplexing(TM);SynchronousDigitalHierarchy(SDH)informationmodeloftheSubNetworkConnectionProtection(SNCP)fortheNetworkElement(NE)view".[12]ETSIEN301167:"TransmissionandMultiplexing(TM);ManagementofSynchronousDigitalHierarchy(SDH)transmissionequipment;Faultmanagementandperformancemonitoring;Functionaldescription".SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)9[13]ETSIEN301155:"SynchronousDigitalHierarchy(SDH);Unidirectionalperformancemonitoringforthenetworkelementview".[14]ETSIEN301268:"TelecommunicationsManagementNetwork(TMN);LinearmultiplexsectionprotectionconfigurationinformationmodelfortheNetworkElement(NE)view".[15]ETSIETS300337:"TransmissionandMultiplexing(TM);Genericframestructuresforthetransportofvarioussignals(includingAsynchronousTransferMode(ATM)cellsandSynchronousDigitalHierarchy(SDH)elements)attheITU-TRecommendationG.702hierarchicalratesof2048kbit/s,34368kbit/sand139264kbit/s".[16]ETSIEN301384:"TelecommunicationsManagementNetwork(TMN);PerformancemonitoringforPlesynchronousDigitalHierarchy(PDH)interfaces;InformationmodelfortheNetworkElement(NE)view".[17]ETSIES202098:"TelecommunicationsManagementNetwork(TMN);InformationmodelforaVCtransportsystemusinga34Mbit/sPDHtransmissionsysteminaccordancewithITU-TRecommendationG.832".[18]ITU-TRecommendationG.774(1992):"Synchronousdigitalhierarchy(SDH)managementinformationmodelforthenetworkelementview".[19]ITU-TRecommendationG.826(02/99):"Errorperformanceparametersandobjectivesforinternational,constantbitratedigitalpathsatorabovetheprimaryrate".[20]ITU-TRecommendationG.828(02/00):"Errorperformanceparametersandobjectivesforinternational,constantbitratesynchronousdigitalpaths".[21]ITU-TRecommendationM.20(1992):"Maintenancephilosophyfortelecommunicationsnetworks".[22]ITU-TRecommendationM.2100(1995):"Performancelimitsforbringing-into-serviceandmaintenanceofinternationalPDHpaths,sectionsandtransmissionsystems".[23]ITU-TRecommendationM.2101(1997):"Performancelimitsforbringing-into-serviceandmaintenanceofinternationalSDHpathsandmultiplexsections".[24]ITU-TRecommendationM.2101.1(1997):"Performancelimitsforbringing-into-serviceandmaintenanceofinternationalSDHpathsandmultiplexsections".[25]ITU-TRecommendationM.2120(1997):"PDHpath,sectionandtransmissionsystemandSDHpathandmultiplexsectionfaultdetectionandlocalizationprocedures".[26]ITU-TRecommendationQ.822(1994):"Stage1,Stage2andStage3descriptionfortheQ3interface–Performancemanagement".[27]ITU-TRecommendationQ.921(1997):"ISDNuser-networkinterface–Datalinklayerspecification".[28]ITU-TRecommendationV.11(1996):"Electricalcharacteristicsforbalanceddouble-currentinterchangecircuitsoperatingatdatasignallingratesupto10Mbit/s".SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)103Definitions,abbreviations,symbolsanddiagrammaticconventions3.1DefinitionsForthepurposesofthepresentdocument,thetermsanddefinitionsgiveninEN300417-1-1[8]apply.3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:15m15minutes24h24hoursAccPerAccumulationPeriodAcSLAcceptedSignalLabelAcTIAcceptedTraceIdentifierAFAtomicFunctionAvFbAvailabilityFunctionbi-directionalAvFuAvailabilityFunctionuni-directionalAIAdaptedInformationAISAlarmIndicationSignalAPAccessPointAPIAccessPointIdentifierARCHARCHitectureATMAsynchronousTransferModeAUAdministrativeUnitAUGAdministrativeUnitGroupA/ZfromAtoZBBEBackgroundBlockErrorBUTBeginofUnavailableTimeCICharacteristicInformationCKClocKCLRCLeaRClrLONClearLockoutofNormaltrafficsignalfromprotectionCMConfigurationManagementCMConnectionMatrixCPConnectionPointCRCCyclicRedundancyCheckCSClockSourceCSESConsecutiveSeverelyErroredSecondsCur15mCurrent15minutesCur24hCurrent24hourDCCDataCommunicationsChannelDECDECrementDEGDEGradedDEGMDEGradedMonitorperiodDEGTHRDEGradedTHresholdDMADeferredMaintenanceAlarmDSDefectSecondEBCErroredBlockCountEDCErrorDetectionCodeEFSEquipmentFunctionalSpecificationEMFEquipmentManagementFunctionEQEQuipmentESElectricalSectionESErroredSecondEUTEndofUnavailableTimeEXERExerciseSIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)11EXER-RExercise-RingEXER-SExercise-SpanEXTCMDEXTernalCoMmanDExTIExpectedTraceIdentifierF_BFar-endBlockFASFrameAlignmentSignalFBBEFar-endBackgroundBlockErrorFESFar-endErroredSecondFFSForFurtherStudyFPMEFar-endPerformanceMonitoringEventFOPFailureOfProtocolFSFrameStartsignalFSESFar-endSeverelyErroredSecondFS-RForcedSwitchtoprotection-ringFS-SForcedSwitchtoprotection-spanFSwForcedSwitchG826ENG.826[19]bi-directionalpackageatthetrailendnodeG826ING.826[19]bi-directionalpackageatintermediatenodeHOHoldOff(usedinHOTime)IDIDentifierIMInMultiframestateINCINCrementIncAISIncomingAISLOLockoutOfprotectionLOFLossOfFrameLOMLossOfMultiframeLONLockoutOfNormaltrafficsignalfromprotectionLOPLossOfPointerLOSLossOfSignalLOW-RLockoutOfWorkingchannels-ringswitchLOW-SLockoutOfWorkingchannels-spanswitchLP-ALockoutofProtection–AllspansLP-SLockoutofProtection-SpanLSSLossofSequenceStructureLTCLossofTandemConnectionMCMatrixConnectionMCFMessageCommunicationsFunctionMEIMaintenanceEventInformationMFPMultiFramePresentMIManagementInformationMPManagementPointMOManagedObjectMONMONitoredMPManagementPointMSMultiplexSectionMS1STM-1MultiplexSectionMS16STM-16MultiplexSectionMS4STM-4MultiplexSectionMS64STM-64MultiplexSectionMSPMultiplexSectionProtectionMS-RManualSwitchtoprotection-ringMS-SManualSwitchtoprotection-spanMSwManualSwitchN/ANotApplicableNBBENear-endBackgroundBlockErrorNCNetworkConnectionNENetworkElementNESNear-endErroredSecondNMONNotMONitoredNPMENear-endPerformanceMonitoringEventNSESNear-endSeverelyErroredSecondODIOutgoingDefectIndicationSIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)12OEIOutgoingErrorIndicationOFOutgoingFar-endOHOverHeadONOutgoingNear-endOPEROPERationOSOpticalSectionOWOrderWirePProtectionP12s2048kbit/sPDHpathlayerwithsynchronous125µsframestructureaccordingtoETS300167[2]P22e8448kbit/sPDHpathlayerwith4plesiochronous2048kbit/sP31e34368kbit/sPDHpathlayerwith4plesiochronous8448kbit/sP31s34368kbit/sPDHpathlayerwithsynchronous125µsframestructureaccordingtoETS300337[15]P4e139264kbit/sPDHpathlayerwith4plesiochronous34368kbit/sP4s139264kbit/sPDHpathlayerwithsynchronous125µsframestructureaccordingtoETS300337[15]PDHPlesiochronousDigitalHierarchyPJEPointerJustificationEventPJE-NegativePointerJustificationEventPJE+PositivePointerJustificationEventPLMPayLoadMismatchPMPerformanceMonitoringPMAPromptMaintenanceAlarmPMCFPerformanceMonitoringClockFunctionPMFPerformanceMonitoringFunctionPRCPrimaryReferenceClockPROTPROTectionPSProtectionSwitchingRDIRemoteDefectIndicatorREIRemoteErrorIndicatorRIRemoteInformationRSRegeneratorSectionRS1STM-1RegeneratorSectionRS16STM-16RegeneratorSectionRS4STM-4RegeneratorSectionRS64STM-64RegeneratorSectionRTCRealTimeClockRTHRResetThresholdRTRResetThresholdReportSDHSynchronousDigitalHierarchySESSeverelyErroredSecondSFSignalFailSkSinkSNCSub-NetworkConnectionSNC/IInherentlymonitoredSub-NetworkConnectionprotectionSNC/NNon-intrusivelymonitoredSub-NetworkConnectionprotectionSNC/SSublayermonitoredSub-NetworkConnectionprotectionSoSourceSOHSectionOverHeadSSFServerSignalFailSSMSynchronizationStatusMessageSTMSynchronousTransportModuleSTM-NSynchronousTransportModule,levelNTCTandemConnectionTCPTerminationConnectionPointTHRThresholdThrFdDuallevelThresholdingFunctionThrFsSinglelevelThresholdingFunctionTITimingInformationTITraceIdentifierSIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)13TIMTraceIdentifierMismatchTIMdisTraceIdentifierMismatchdisableTMNTelecommunicationsManagementNetworkTPTimingPointTPmodeTerminationPointmodeTRThresholdReportTSTimeSlotTSETestSequenceErrorTSNTibutarySignalNumberTTTrailTerminationfunctionTTITrailTraceIdentifierTUTributaryUnitTUGTributaryUnitGroupTxTITransmittedTraceIdentifierUASUnavailableSecondUATUnavailableTimeUNEQUNEQuippedUTCUniversalTimeCoordinatedVCVirtualContainerVC-nVirtualContainer,levelnWWorkingWTRWaitToRestoreZ/AfromZtoA3.3SymbolsanddiagrammaticconventionsForthepurposesofthepresentdocument,thesymbolsanddiagrammaticconventionsdescribedinEN300417-1-1[8]apply.4EquipmentmanagementfunctionTheequipmentmanagementfunction(EMF)(figure1)providesthemeansthroughwhichanetworkelementlevelmanagermanagesthenetworkelementfunction(NEF).TheEMFinteractswiththetransportandsynchronizationlayeratomicfunctionsbyexchanginginformation(MI:managementinformation)acrosstheMPreferencepoints.TheEMFcontainsanumberoffunctionsthatprovideadatareductionmechanismontheinformationreceivedacrosstheMPreferencepoints.Thesefunctionoutputsareavailabletotheagentviathenetworkelementresourcesandmanagementapplicationfunctions(MAF)whichrepresentthisinformationasmanagedobjects.Networkelementresourcesprovideeventprocessingandstorage.TheMAFprocesstheinformationprovidedtoandbytheNEresources.Forexample,theagentconvertsthisinformationtoCMISE(commonmanagementinformationserviceelement)messagesandrespondstoCMISEmessagesfromthemanagerbyperformingtheappropriateoperationsonthemanagedobjects.NOTE:Themanagementapplicationfunctionspecificationisoutsidethescopeofthepresentdocument.Networkelementsmaysupportseveralfunctions,whichcanbeoperatedonlyinexclusivityofeachother.Besidessuchconfigurationprovisionings,provisioningsareneededforparametersinindividualfunctionsandprocesseswithinaNE.Anumberoffunctions/processesandreportshaveanotionoftime.ThenetworkelementRealTimeClockfunctionprovidesthistimeinformation.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)14NE-RTCFaultManagementPerformanceMonitoringConfigurationManagementManagmentApplicationFunctionsMI_cXXXMI_pXXXMI_XXXMI_1secondSD_CI_CKMPFigure1:EquipmentManagementFunctionprocessblockdiagramMPTheMIatthispointisasetofmanagementsignalsto/fromtheatomicfunctions,includingconfigurationandoperationcontrol,faultmanagement,performancemonitoring,protectionswitching,synchronizationcontrolandreportingsignals.SD_CPTheCIatthispointistheSD_CI_CKsignal.4.1NetworkElement-RealTimeClock(NE-RTC)FunctionSymbol:NE-RTCRealTimeclockSET-RTCSD_TI_CKFigure2:NERTCfunctionSIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)15Interfaces:Table1:NE-RTCinputandoutputsignalsInput(s)Output(s)SET-RTCSD_TI_CKNE-RTCProcesses:TherealtimeclockisalogicalentitywithintheNEwhichprovidesdateandtimeinformationtoequipmentmanagementfunctionswithintheNE.Therealtimeclockshallhavearesolutionof1second.Thedateshallberepresentedasyear:month:dayandbe"year2000"compliant.Thetimeshallberepresentedashour:minute:second.OnreceiptoftheSET-RTCcommand,therealtimeclockshallbesettothedate:timespecifiedbytheSET-RTCcommand.Onaregularbasis,theRTCistoberealignedwithUTC.Thisrealignmentperiodshouldbedeterminedsuchthatthecorrectionislessthan±10secondstopreventthatallactivePMFsdeclaresuspectintervals.Therealtimeclockmaybeafreerunningclockormaybelockedtoanyavailableclocksource(e.g.equipmentclockSD_TI_CK).Thestabilityoftherealtimeclockshallbesuchthatinany24hourperiod(whereaSET-RTCcommandhasnotbeenreceived),theRTCshallnothavedeviatedbymorethan±Ysecondsfromthe24hourperiodofaUTC;Yisforfurtherstudy.WhenaSET-RTCcommandisreceived,theerrorbetweentheManagementcommandattheinputtotheNE(figure3)andtheresultantNE-RTCtimeshallbewithin±Xseconds;Xisforfurtherstudy.NOTE:TherelationshipandtimingtransferbetweenthemanagementcommandattheinputtotheNEandtheresultantSET-RTCcommandisbeyondthescopeofthepresentdocument.NENEProcessingandallinternaldelaysSET_RTCRTCNE_RTCMessageUTC+/-XsecondsFigure3:NE_RTCandUTCrelationSIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)164.2FaultManagementFunctionsTheequipmentmanagementfunctionwithinthenetworkelementperformsapersistencycheckonthefaultcausesbeforeitdeclaresafaultcauseafailure.Thefaultcausesaregeneratedbytheatomicfunctionfaultmanagementprocess.Aseverityisassociatedwitheachalarm.Thefailureisreportedviatheagentprocess(outputfailurereport)andbymeansofalarms(audibleandvisibleindicators).Typically,alarmscanbedividedintounitlevelalarms,NElevelalarmsandstationalarms.UnitAlarmsNetworkElementAlarmsStationAlarmsFailureReportstoTMNfaultCausecZZZFailurefZZZseverityassignmentManagementApplicationFunctionf4f5f6f7f8Figure4:FaultmanagementinsideEMFfunctionFilterFunctionf4integrationoffaultcausesintofailuresf5assignseveritytofailuref6translationoffailuresintoUnitalarmsf7translationoffailuresintoNetworkElementalarms(e.g.severity)f8translationoffailuresintostationalarms&alarmdisconnectcontrol4.2.1Failurefilterf4Atransmissionfailureshallbedeclaredifthefaultcausepersistscontinuouslyfor2,5±0,5seconds.Thefailureshallbeclearedifthefaultcauseisabsentcontinuouslyfor10±0,5seconds.Thefailurechange(declaration/clearing)shallbetimestamped.Thetimestampshallindicatethestartofthefaultcausetofailureintegrationtime.Thetimestampshallhaveanaccuracyof1secondrelativetotheNE-RTC.Agenericlistoffailuresisshownintable2.Table2:FailuresdeclaredperatomicfunctionTerminationsinkAdaptationsinkConnectionfSSFfLOFfFOPfUNEQfLOMfTIMfLOPfDEGfAISfLOSfPLMfRDIfLTIfLTCfLSSfIncAISfODISIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)174.2.2Severityassignmentfilterf5Aseverityisusedtoindicatethemanagementperceptionoftheseverityofafaultwhichcoulddependontheservicedependencyofthefault.RefertoEN301167[12].NOTE:Twoseverityschemesarebeingused.OnebasedontheITU-TRecommendationsXserieswhichhastheseverityelements:critical,major,minorandwarning.TheotherbasedontheITU–TRecommendationM.20[21]whichhastheseverityelements:promptmaintenancealarm(PMA),deferredmaintenancealarm(DMA)andmaintenanceeventinformation(MEI).4.2.3Replaceableunitalarmfilterf6Therearesomanypreferencesamongstthepublicnetworkoperators,standardizationoftheunitalarmsisnotpossibleatthemoment.NOTE:TheroleofthisinterfacewithinmanagementproceduresshouldbereviewedinlightofincreasedfunctionalityoftheQinterface.4.2.4Networkelementalarmfilterf7Therearesomanypreferencesamongstthepublicnetworkoperators,standardizationofthenetworkelementalarmsisnotpossibleatthemoment.NOTE:TheroleofthisinterfacewithinmanagementproceduresshouldbereviewedinlightofincreasedfunctionalityoftheQinterface.4.2.5Stationalarmfilterf8Therearesomanypreferencesamongstthepublicnetworkoperators,standardizationofthenetworkelementalarmsisnotpossibleatthemoment.NOTE:TheroleofthisinterfacewithinmanagementproceduresshouldbereviewedinlightofincreasedfunctionalityoftheQinterface.4.3ManagementApplicationFunctionsRefertoinformationmodelstandards(ETS300304[3],EN300371[4],ETS300411[5],ETS300412[6],ETS300413[7],ETS300493[11],EN301155[13],EN301268[14],EN301384[16],ES202098[17]).4.4PerformanceMonitoringFunctionsTheEMFperformancemonitoringprocesscollectstheeventcountsassociatedwith:-thetrailperformanceparametersErroredSeconds(ES),SeverelyErroredSeconds(SES),BackgroundBlockError(BBE)andUnavailableTime(UAT)/UnavailableSecond(UAS);-thelinkconnectionperformanceparameterPointerJustificationEvent(PJE).Itprocessestheeventcountstoderivetheperformanceparameters,andstorestheseperformanceeventsinregisters.Suchinformationcanbeusedtosectionalizefaultsandtolocatesourcesofintermittenterrors,and/ordeterminethequalityoftheservice.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)18Figure5presentsanoverviewofthePerformanceMonitoringFunctions(PMF)withintheEMF.TheshadedboxesarePMFsdefinedinthepresentdocument.TheintermediateellipsesrepresenttheinterconnectoptionsbetweenthePMFs.TheEquipmentFunctionalSpecification(EFS)defineswhich(sub)setofPMFsis(tobe)supportedbytheequipment,aswellasthequantityofeachPMF.NOTE1:Forthecasewherethenumberoftransportatomicfunctionsexceedthenumberofperformancemonitoringresources,selectionmaybeindicatedby"performancemonitoringconnectionfunctions",orbyalternativemeans.Thisisoutsidethescopeofthepresentdocument.Forthecasewhereasuchselectivityisnotpresentorisnotrequired,theinterconnectispredefinedandcanberepresentedintheEFSbyexplicitinterconnectionsbetweenPMFsandatomicfunctions.TheNPMEfunctiondeterminesonapersecondbasisthenumberofnear-endbackgroundblockerrors(BBE),andwhetheranESand/orSESoccurred.TheFPMEfunctiondeterminesonapersecondbasisthenumberoffar-endBackgroundBlockErrors(BBE),andwhetheranESand/orSESoccurred.TheAvFufunctiondetermineswhetheraonesecondisuni-directionallyavailableorunavailable,andpassesthroughthe(ES,SES,BBE)inputsignal'svalueforsecondsinavailabletime.Theinputsignalvalueinsecondsinunavailabletimeisnotoutput,insteadthevalue"0"isoutput.TheAvFbfunctiondetermineswhetheraonesecondisbi-directionallyavailableorunavailable,andpassesthroughthe(ES,SES,BBE)inputsignal'svalueinsecondsinavailabletime.Theinputsignalvalueinsecondsinunavailabletimeisnotoutput,insteadthevalue"0"isoutput.Thedelayfunctiondelaystheinputsignal(whichisnotsubjectto"availability"processing)by10secondstoalignitwiththeperformancemonitoringtimebasewhichis10secondsdelayedfromthetimeofday.The15mfunctionaccumulatestheinputvalues(fromi.e.ES,SES,BBE,PJE+,PJE-,TSE)overperiodsof15minutes.Thefunctioncontainsseventeen15minuteregisters:onecurrentand16recentregisters.The24hfunctionaccumulatestheinputsignalvaluesoverperiodsof24hours.Thefunctioncontainstwo24hourregisters:onecurrentandonerecentregister.TheThrFsandThrFdfunctionscanbeusedtogenerateanautonomouseventreport(athresholdreport)whenthecountinthecurrent15m/24hregistertowhichitisconnectedreachesorexceedstheprovisionedthresholdvalue.Inaddition,theThrFdfunctiongeneratesaresetthresholdreportwhenthecountattheendofa15mperiodhasnotcrossedaprovisionedresetthreshold.Theinputstotheperformancemonitoringprocess-thePerformanceMonitoringprimitives(MI_pXXX)-areonesecondcountsof:-erroredblocks(pX_EBC),defectsecond(pX_DS)generatedbyterminationsinkfunctions;-pointerjustificationevents(pPJE+,pPJE-)generatedbyadaptationsinkfunctions.NOTE2:"X"representsnear-end(X=N),far-end(X=F),outgoingnear-end(X=ON),oroutgoingfar-end(x=of).NOTE3:Tandemconnectionssupportsocalled"OutgoingDefectIndication"and"OutgoingErrorIndication".FordetailsseeETS300147[1]andEN300417-4-1[9].TheseprimitivesarepassedfromtheAtomicFunctions(AFs)totheEquipmentManagementFunction(EMF)forfurtherprocessing.ThePerformancemonitoringtimingfunctionoutputsthe1secondindication(MI_1second)towardstheatomicfunctionstoperformthe1secondcountingoftheperformanceprimitivespXXX.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)19MI_pF_EBCMI_pF_DSMI_pN_DSMI_pOF_EBCMI_pOF_DSMI_pON_DSMI_pN_EBCMI_pN_DSMI_pON_EBCMI_pON_DSMI_pPJE+MI_pPJE-NPMEFPMECur15mUATCSESCur24hAvFuAvFbThrFsPMCMI_1secondDelayManagementApplicationFunctionsMI_pN_TSEThrFdRec15mRec24hPerformancePrimitivesPerformanceEventsNESNSESNBBEFESFSESFBBEUATUATFigure5:OverviewofPerformanceMonitoringfunctionsandtheirinput/outputrelationsPerformancemonitoringfunctionsconnecttothehigherlayermanagementfunctions.ThosefunctionsaredefinedinETS300304[3],ETS300411[5],EN301155[13],EN301167[12]andotherrelatedstandards.Thepresentdocumentaddressesperformancemonitoringfromanequipmentpointofview.EN301167[12]describestheperformancemonitoringfromanetworkpointofview.SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)204.4.1PerformancemonitoringclockfunctionPMCSymbol:NE-RTCPMclockPMclock15mPMclock24h10secondsdelay15minuteintervalcounter24hourintervalcounter1secondperiodsMI_1secondStart24hFigure6:PMclockfunctionInterfaces:Table3:PMclockfunctioninputandoutputsignalsInput(s)Output(s)NE-RTCStart24hPMclockPMclock15mPMclock24hMI_1secondProcesses:Thefunctiongeneratestheclocksignalsassociatedwiththeperformancemonitoringprocessingintheatomicfunctionsandtheperformancemonitoringfunctionswithinanetworkelement.1secondperiods:thisfunctionshallgeneratethe1secondsignalattheendofeach1secondperiodasindicatedbytheNErealtimeclock(NE-RTC).10secondsdelay:forperformancemonitoringpurposes,theNE-RTCshallbedelayedby10seconds(PMclock)forthepurposetoaccommodatetheeffects(a10seconddelay)associatedwiththeunavailabletimecalculation.15minuteintervalcounter:thisprocessgeneratesthe15minuteperiodindications(PMclock15m)whicharealignedwiththeendofeachquarterofanhourperiod(00:00,15:00,30:00,45:00)withrespecttoPMclock.Thestartofaperiodisequaltotheendofthepreviousperiod.IftheNE-RTCisnotpreset,each15minuteperiodspans900onesecondperiods.24hourintervalcounter:thisprocessgeneratesthe24hourperiodindications(PMclock24h)whicharealignedwiththeendofaquarterofanhourperiod(00:00:00,00:15:00,00:30:00,…23:45:00)withrespecttoPMclock.Thestartofaperiodisequaltotheendofthepreviousperiod.IftheNE-RTCisnotpreset,each24hourperiodspans86400onesecondperiods.For24-hourdataspecifically,theNEmaybeinstructed(Start24h)onwhentobeginmeasurementofthe24hourperiodforthepurposeofreportingdata.TheNEshallbeabletobeginthemeasurementatthestartofany15minuteperiod(refertosubclause2.3.3.3ofITU-TRecommendationM.2120[25])(defaultshallbe00:00onthePMclock).SIST EN 300 417-7-1 V1.1.1:2003

ETSIETSIEN300417-7-1V1.1.1(2000-10)214.4.2Performancemonitoringeventsfunctions4.4.2.1Near-
...