SIST EN 300 379-1 V1.2.1:2003
(Main)Telecommunications Management Network (TMN); Q3 interface at the Local Exchange (LE) for fault and performance management of V5 interfaces and associated customer profiles; Part 1: Q3 interface specification
- Abstract
To align the published I-ETS with the corresponding ITU-T Recommendation.
- Status
- Published
- Publication Date
- 31-Oct-2003
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Nov-2003
- Due Date
- 01-Nov-2003
- Completion Date
- 01-Nov-2003
SIST EN 300 379-1 V1.2.1:2003 is the Slovene adoption of ETSI EN 300 379-1 V1.2.1 for the Telecommunications Management Network (TMN). It specifies the Q3 interface at the Local Exchange (LE) for fault and performance management of V5 interfaces and associated customer profiles.
The document is intended for TMN and network professionals who need to model alarms, performance data, and management objects for V5.1 and V5.2 access arrangements. In practice, it defines what the LE reports, how those objects are organized, and which companion standards provide the underlying object and protocol framework.
What does SIST EN 300 379-1 V1.2.1:2003 specify?
SIST EN 300 379-1 V1.2.1:2003 specifies the Q3 interface between an LE and the TMN for fault and performance management of V5 interfaces and associated customer profiles. It focuses on the V5-related parts of access management, not on general equipment management or non-V5 transmission and media management.
The document is organized into:
- Clause 4 - information model diagrams
- Clause 5 - information model description
- Clause 6 - formal object class definitions
- Clause 7 - protocol requirements
- Annex A - normative alarm-report parameters
- Annex B - normative V5 traffic measurements
- Annex C - informative task information base (TIB)
- Annex D - informative management function descriptions
| Annex | What it covers |
|---|---|
| Annex A | Parameters for V5-specific alarm reports |
| Annex B | V5-specific traffic measurements |
| Annex C | TMN task information base for fault and performance management |
| Annex D | Descriptions of alarm surveillance and performance management functions |
What are the key requirements of SIST EN 300 379-1 V1.2.1:2003?
SIST EN 300 379-1 V1.2.1:2003 defines a management information model for V5 fault and performance management, with object classes imported from related ETSI and ITU-T specifications. That matters because the standard relies on shared TMN object models instead of redefining everything locally.
Fault management model
Clause 5.1.1 defines the V5 interface objects that carry fault notifications:
v5Interfacereports common control, BCC, protection, and PSTN-related errors, plus V5 interface identification failures and provisioning variant mismatch failures.v5Ttpreports layer 1 reception of AIS, RAI, and LFA, along with link and CRC failures.v5TimeSlotreports cessation of flags on a C-channel.
In practice, this tells implementers which network element objects must generate alarms and what kinds of V5 problems they are expected to signal.
Access port and customer access objects
Clause 5.1.2 extends fault reporting to virtualAnalogueAccessR1, virtualBasicRateAccessR1, virtualPrimaryRateAccessR1, and virtualLeasedAccessR1. The standard distinguishes PSTN, ISDN basic rate, ISDN primary rate, and leased access ports because each port type has different alarm conditions and relevance to service.
For example, virtualBasicRateAccessR1 and virtualPrimaryRateAccessR1 report ISDN layer 1, 2, and 3 faults, while virtualAnalogueAccessR1 reports PSTN protocol and port control errors. This matters for fault localisation: the alarm points to the access type that actually needs attention.
Performance management model
Clause 5.1.5 defines V5 traffic measurements using currentData, historyData, and simpleScanner / scanReportRecord. The measurements are collected on 15-minute intervals, which is important for operational reporting and trend analysis.
For bearer channels, the model tracks allocations, holding times, in-service times, and unsuccessful allocation attempts. For communication channels, it tracks out-of-service duration, outages, and LAPV5-EF frame octets. In practice, these measurements support service quality checks and capacity assessment.
Object containment and reporting
Clause 4 shows the entity relationship, inheritance, and naming hierarchies for the LE managed objects. Clause 5.4 adds the specific notifications offHook, onHook, and timeOut for ringback service treatment.
This means the document is not only about alarms and counters - it also shows how the managed objects fit together in the TMN model and how test-related notifications are carried.
Protocol and parameter references
Clause 7 states that the protocol stack on this Q3 interface is the same as in the companion configuration-management standard, EN 300 377-1. Annex A then binds V5-specific alarms to the communicationsAlarm notification and gives the alarm parameters to use.
That matters because implementers can reuse the same underlying Q3 protocol profile while adding V5-specific alarm content.
What terms does SIST EN 300 379-1 V1.2.1:2003 define?
V5 interface- the access interface between the LE and the AN used for narrowband access services.Q3 interface- the TMN management interface used between the LE and management systems.LE (Local Exchange)- the exchange side network node that hosts the managed V5 interface objects.AN (Access Network)- the network side that carries the customer access toward the LE.BCC (Bearer Channel Connection)- the bearer-channel control function used in bearer-channel allocation and deallocation.C-channel- the communication channel used for control signalling on V5.TIB (Task Information Base)- the management-service view of tasks and functions such as fault and performance management.
Who uses SIST EN 300 379-1 V1.2.1:2003?
SIST EN 300 379-1 V1.2.1:2003 is used by TMN architects, LE and AN equipment suppliers, operations-system designers, and network operators managing V5 access. It is relevant when they need to define alarms, collect performance data, map managed objects, or integrate LE fault and performance reporting into a Q3-based management system.
It is also useful for test and assurance teams that need to understand which faults, counters, and notifications should be available for V5.1 and V5.2 interfaces and associated customer profiles.
Which standards are used with SIST EN 300 379-1 V1.2.1:2003?
The standard is built on these companion standards:
- EN 300 324-1 - defines V5.1 interface details and many V5 terms used in the alarm and measurement definitions.
- EN 300 347-1 - defines V5.2 interface details and protection-related terminology.
- EN 300 377-1 - defines configuration management for the same Q3 interface and provides the shared protocol stack.
- EN 300 378-1 - gives the related Q3 interface specification for fault and performance management at the AN.
- EN 300 291-1 - provides the access-port object classes used for analogue, basic rate, primary rate, and leased access.
- ITU-T Q.821, Q.822, Q.824.5, and Q.835 - provide the base alarm, performance, configuration, and test-management object models used by this standard.
What does the SIST EN 300 379-1 V1.2.1:2003 document contain?
The document contains information-model diagrams, formal managed-object definitions, and protocol requirements for the LE-side Q3 interface. It also contains parameter mappings for V5-specific alarms and traffic measurements, including the tables that describe object attributes and measurement names.
Annex C and Annex D describe the fault-management and performance-management tasks in operational terms, which helps when mapping the standard to real TMN workflows. Annex A and Annex B provide the concrete alarm and measurement content that implementers use for reporting, logging, and service-quality monitoring.
Get Certified
Connect with accredited certification bodies for this standard
ANCE
Mexican certification and testing association.
Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST EN 300 379-1 V1.2.1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Telecommunications Management Network (TMN); Q3 interface at the Local Exchange (LE) for fault and performance management of V5 interfaces and associated customer profiles; Part 1: Q3 interface specification". This standard covers: To align the published I-ETS with the corresponding ITU-T Recommendation.
To align the published I-ETS with the corresponding ITU-T Recommendation.
SIST EN 300 379-1 V1.2.1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.040.35 - Telephone networks. The ICS classification helps identify the subject area and facilitates finding related standards.
SIST EN 300 379-1 V1.2.1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Telekomunikacijsko upravljavno omrežje (TMN) ) - Vmesnik Q3 krajevne centrale (LE) za upravljanje okvar in delovanja vmesnikov V5 in pridruženih profilov stranke - 1. del: Specifikacija vmesnika Q3Telecommunications Management Network (TMN); Q3 interface at the Local Exchange (LE) for fault and performance management of V5 interfaces and associated customer profiles; Part 1: Q3 interface specification33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 379-1 Version 1.2.1SIST EN 300 379-1 V1.2.1:2003en01-november-2003SIST EN 300 379-1 V1.2.1:2003SLOVENSKI
STANDARD
ETSIEN300379-1V1.2.1(1999-10)EuropeanStandard(Telecommunicationsseries)TelecommunicationsManagementNetwork(TMN);Q3interfaceattheLocalExchange(LE)forfaultandperformancemanagementofV5interfacesandassociatedcustomerprofiles;Part1:Q3interfacespecificationSIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)2ReferenceREN/TMN-02004-1(3ic90ioo.PDF)Keywordsinformationmodel,LE,management,performance,Q3interface,TMN,V5interfaceETSIPostaladdressF-06921SophiaAntipolisCedex-FRANCEOfficeaddress650RoutedesLucioles-SophiaAntipolisValbonne-FRANCETel.:+33492944200Fax:+33493654716SiretN°34862356200017-NAF742CAssociationàbutnonlucratifenregistréeàlaSous-PréfecturedeGrasse(06)N°7803/88Internetsecretariat@etsi.frIndividualcopiesofthisETSIdeliverablecanbedownloadedfromhttp://www.etsi.orgIfyoufinderrorsinthepresentdocument,sendyourcommentto:editor@etsi.frImportantnoticeThisETSIdeliverablemaybemadeavailableinmorethanoneelectronicversionorinprint.Inanycaseofexistingorperceiveddifferenceincontentsbetweensuchversions,thereferenceversionisthePortableDocumentFormat(PDF).Incaseofdispute,thereferenceshouldbetheprintingonETSIprintersofthePDFversionkeptonaspecificnetworkdrivewithinETSISecretariat.CopyrightNotificationNopartmaybereproducedexceptasauthorizedbywrittenpermission.Thecopyrightandtheforegoingrestrictionextendtoreproductioninallmedia.©EuropeanTelecommunicationsStandardsInstitute1999.Allrightsreserved.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)3ContentsIntellectualPropertyRights.6Foreword.6Introduction.61Scope.82References.83Definitionsandabbreviations.93.1Definitions.93.2Abbreviations.104Informationmodeldiagrams.114.1Entityrelationshipdiagram.114.2Inheritancehierarchy.124.3Naminghierarchy.135Informationmodeldescription.135.1Managedobjectclassesdescription.145.1.1V5interfacefragment.145.1.1.1V5interface(v5Interface).145.1.1.2V5trailterminationpoint(v5Ttp).155.1.1.3V5timeslot(v5TimeSlot).155.1.2Accessportfragment.165.1.2.1Virtualanalogueaccess(virtualAnalogueAccessR1).165.1.2.2Virtualbasicrateaccess(virtualBasicRateAccessR1).165.1.2.3Virtualprimaryrateaccess(virtualPrimaryRateAccessR1).175.1.2.4Virtualleasedaccess(virtualLeasedAccessR1).185.1.3Communicationpathfragment.185.1.4Protectionfragment.185.1.5Performancefragment.185.1.5.1Bearerchannelcurrentdata.195.1.5.2Bearerchannelhistorydata.205.1.5.3Communicationchannelcurrentdata.205.1.5.4Communicationchannelhistorydata.215.1.6Alarmsurveillancefragment.215.1.7Supportfragment.215.1.7.1Eventreportmanagement.215.1.7.2Logcontrolfunction.215.1.8Testfragment.215.1.8.1Accessnetworkringbackservicetreatment(anRbsTreatment).215.2Attributesdescription.225.3Actionsdescription.225.4Notificationsdescription.226Formalobjectclassdefinitions.226.1V5interfacefragment.226.2Accessportfragment.226.3Communicationpathfragment.236.4Protectionfragment.236.5Performancefragment.236.6Alarmsurveillancefragment.236.7Supportfragment.246.8Testfragment.24SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)47Protocolrequirements.24AnnexA(normative):SpecificationofparametersforV5specificalarmreports.25A.1AlarmreportsrelatedtotheV5interfaceobjectclass.25A.2AlarmreportsrelatedtotheV5trailterminationpointobjectclass.25A.3AlarmreportsrelatedtotheV5timeslotobjectclass.25A.4Alarmreportsrelatedtothevirtualaccessportobjectclassandsubclasses.25A.4.1Controlprotocolerrors.25A.4.2PSTNprotocolerrors.26A.4.3ISDNlayerfaults.26AnnexB(normative):V5specifictrafficmeasurement.28B.1BearerchannelorientedmeasurementsattheV5interface.28B.1.1Totalnumberofbearerchannelallocationsbothway.28B.1.2Measurementofthetotalnumberofbearerchannelallocationsforterminatingtraffic.28B.1.3Totalnumberofbearerchannelallocationsfororiginatingtraffic.28B.1.4Totalsumofbearerchannelholdingtimesbothway.29B.1.5Totalsumofbearerchannelholdingtimesforterminatingtraffic.29B.1.6Totalsumofbearerchannelholdingtimesfororiginatingtraffic.29B.1.7Numberofunsuccessfulbearerchannelallocationattemptsforincomingtraffic.29B.1.8NumberofunsuccessfulbearerchannelallocationattemptsforLEinternaltraffic.30B.1.9Totalsumofbearerchannelin-servicetimes.30B.2CommunicationchannelorientedmeasurementsattheV5interface.30B.2.1DurationofC-channelout-of-serviceduetoanyreason.30B.2.2DurationofC-channelout-of-serviceduetonearendblocking.30B.2.3DurationofC-channeloutofservicebyfarendblocking.30B.2.4NumberofC-channeloutages.30B.2.5NumberofLAPV5-EFframeoctetsonaC-channel.31AnnexC(informative):TaskInformationBase(TIB).32C.1TMNmanagementservice"FaultmanagementofV5interfacesandassociateduserports".32C.1.1Description.32C.1.2Componentsofservice(TIBA).32C.1.2.1Failuredetection.32C.1.2.2Systemprotection.32C.1.2.3Failureinformation.32C.1.2.4Failurelocalisation.32C.1.2.5Faultcorrection.32C.1.2.6Verification.32C.1.2.7Restoration.32C.1.3Managementfunctionlist(TIBB).33C.1.3.1Requeststatus.33C.1.3.2Initiateswitch-over.33C.1.3.3Reportautomaticswitch-over.33C.1.3.4Setservicestate.33C.1.3.5Alarmreport.33C.1.3.6Setalarmconditions.33C.1.3.7Applytestsignals.33C.1.3.8Removetestsignals.33C.1.3.9Requesttestresults.33C.1.3.10Testresultreport.33C.2TMNmanagementservice"PerformancemanagementofV5interfacesandassociateduserports".34C.2.1Description.34C.2.2Componentsofservice(TIBA).34C.2.2.1Performancemonitoring.34C.2.2.2Performanceinformation.34SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)5C.2.3Managementfunctionlist(TIBB).34C.2.3.1Start/stopPMdata.34C.2.3.2PMdatareport.34AnnexD(informative):Descriptionofmanagementfunctions.35D.1Alarmsurveillance.35D.1.1Alarmsurveillancefunctions.35D.1.1.1Alarmreportingfunctions.35D.1.1.2Alarmsummaryfunctions.35D.1.1.3Alarmeventcriteriafunctions.36D.1.1.4Alarmindicationmanagementfunctions.36D.1.1.5Logcontrolfunctions.36D.1.2Alarmreportingfunction.36D.1.2.1Eventtype.36D.1.2.2Probablecause.36D.1.2.3Specificproblems.36D.1.2.4Perceivedseverity.37D.1.2.5Monitoredattributes.37D.1.2.6Additionalinformation.37D.2Performancemanagement.37D.2.1Performancemanagementfunctions.37D.2.1.1Performancemanagementdatacollectionfunctions.37D.2.1.2Performancemanagementdatastoragefunctions.38D.2.1.3Performancemanagementthresholdingfunctions.38D.2.1.4Performancemanagementdatareportingfunctions.38D.2.2Performancemanagementmodel.38D.2.2.0Monitoredobject.39D.2.2.1CurrentDataobject.39D.2.2.2HistoryDataobject.39D.2.2.3ThresholdDataobject.39D.2.2.4Scanners.40Bibliography.41History.42SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)6IntellectualPropertyRightsIPRsessentialorpotentiallyessentialtothepresentdocumentmayhavebeendeclaredtoETSI.TheinformationpertainingtotheseessentialIPRs,ifany,ispubliclyavailableforETSImembersandnon-members,andcanbefoundinSR000314:"IntellectualPropertyRights(IPRs);Essential,orpotentiallyEssential,IPRsnotifiedtoETSIinrespectofETSIstandards",whichisavailablefromtheETSISecretariat.LatestupdatesareavailableontheETSIWebserver(http://www.etsi.org/ipr).PursuanttotheETSIIPRPolicy,noinvestigation,includingIPRsearches,hasbeencarriedoutbyETSI.NoguaranteecanbegivenastotheexistenceofotherIPRsnotreferencedinSR000314(ortheupdatesontheETSIWebserver)whichare,ormaybe,ormaybecome,essentialtothepresentdocument.ForewordThisEuropeanStandard(Telecommunicationsseries)hasbeenproducedbyETSITechnicalCommitteeTelecommunicationsManagementNetwork(TMN).Thepresentdocumentispart1ofamulti-partENcoveringtheQ3interfaceattheLocalExchange(LE)forfaultandperformancemanagementofV5interfacesandassociatedcustomerprofiles,asidentifiedbelow:Part1:"Q3interfacespecification";Part2:"ManagedObjectsConformanceStatement(MOCS)proforma"(forfurtherstudy).NationaltranspositiondatesDateofadoptionofthisEN:15October1999DateoflatestannouncementofthisEN(doa):31January2000DateoflatestpublicationofnewNationalStandardorendorsementofthisEN(dop/e):31July2000DateofwithdrawalofanyconflictingNationalStandard(dow):31July2000IntroductionV5interfaces,asdescribedinEN300324-1[2]andEN300347-1[3],operatebetweenaLocalExchange(LE)andanAccessNetwork(AN)tosupportvariousnarrowbandIntegratedServicesDigitalNetwork(ISDN)andPublicSwitchedTelephoneNetwork(PSTN)services.TheseinterfacesandtheirassociateduserportsneedtobemanagedbytheOperationsSystems(OSs)withintheTelecommunicationsManagementNetwork(TMN).ThismanagementisperformedbymeansofQ3interfaces.ThecompanionstandardonconfigurationmanagementEN300377-1[4]defineshowtheQ3interfaceofaLEhandlestheconfigurationinformationforV5interfacesandtheirassociatedcustomerprofiles.Thepresentdocumentdescribestheextensiontoincludefaultandperformancemanagement.FaultmanagementofV5interfacesandassociateduserportsispartofamanagementactivitywhichisperformedbytheoperatorinordertodetectfailureconditionsandtobringthecustomeraccessbacktoitsnormalstateofoperationwheneveradeviationoccurs.PerformancemanagementofV5interfacesandassociateduserportsispartofamanagementactivitywhichisemployedinordertomaintainthequalityofservicelevelsagreedwiththecustomers.Theactivitiesundertakeninperformancemanagementaremonitoring,analysisandproblemalerting,diagnosis,optimizationandcontrol.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)7Acustomeraccessisconsideredasbeingthatpartofthelocalnetworkwhichextendsfromthenetworkterminationequipmentuptoandincludingtheexchangetermination.Here,onlythesepartsoftheactivitiesarecoveredwhicharerelateddirectlytoaV5interfacebetweenaLEandanANortothatpartofthecustomeraccesswhichextendsfromtheANtothenetworkterminationequipment.AnISDNaccessextendstobutdoesnotincludetheTreferencepoint.AnanalogueaccessextendstoandmayincludetheCustomerPremiseEquipment(CPE)(seefigure1).V5Q(LE)Q(AN)ANZTPSTNTETLEV5TPV5TPNT1ISDNTEISDNTETEPSTNUPISDNUPISDNUPLLUPNOTE:ShadedareasaresubjecttoV5faultandperformancemanagement.UserportsrepresentthedifferentconfigurationsforLineCircuit(LC),LineTermination(LT),ExchangeTermination(ET)andNetworkTermination(NT)asindicatedinEN300324-1[2]andEN300347-1[3].Figure1:ScopeofV5faultandperformancemanagementThepresentdocumentdetailsonlythosefunctionsandmanagementinformationmodelcomponentsforwhichV5specificdescriptionsarerequired.However,theuseofothercomponentswhichmaybeapplicablefromotherspecificationsisnotprecluded.Inthiscase,combinedapplicationincorporatingbothV5-specificandmoregenericaspectswouldresult.Forexample,iflogcontrolistobeprovidedinconjunctionwiththeV5specificalarmreportingfunction(seeannexA)thenotherspecifications(e.g.ITU-TRecommendationX.735[17])areavailabletodefinethis.Themanagementinformationmodeldescribedinthepresentdocumentcomplementsthatforconfiguration;bothinformationmodelswillnormallysharethesamephysicalinterface.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)81ScopeThepresentdocumentspecifiestheQ3interfacebetweenaLocalExchange(LE)andtheTelecommunicationsManagementNetwork(TMN)forthesupportofFaultandPerformanceManagementfunctionsforV5interfaces,asdescribedinEN300324-1[2]andEN300347-1[3],andtheirassociatedcustomerprofiles.Themanagementoftransmission,mediaandserviceswhicharenotrelatedtoV5interfacesisoutsidethescopeofthepresentdocument,asisthemanagementofequipment.Thepresentdocumentincludestheloggingoffaultsandrelatedfunctions.Forcertainimplementations,sometestrelatedfunctionslikelinemonitoring,patterninjectionforloopbacktestsandDualToneMulti-Frequency(DTMF)measurementsmayalsobeperformedintheLE,e.g.duetoeconomicalreasons.AQinterfaceforthesefunctionsisrequiredattheLE.AstheyarenotV5specific,thishastobehandledwithinanoverallLEtestmodelwhichisoutsidethescopeofthepresentdocument.ThelocationoftheQ3interfacetowhichthepresentdocumentrefersisspecifiedinEN300377-1[4].Existingprotocolsareusedwherepossible,andthefocusoftheworkisondefiningtheobjectmodels.ThedefinitionofOperationsSystem(OS)functionalityisoutsidethescopeofthepresentdocument.2ReferencesThefollowingdocumentscontainprovisionswhich,throughreferenceinthistext,constituteprovisionsofthepresentdocument.· Referencesareeitherspecific(identifiedbydateofpublication,editionnumber,versionnumber,etc.)ornon-specific.· Foraspecificreference,subsequentrevisionsdonotapply.· Foranon-specificreference,thelatestversionapplies.· Anon-specificreferencetoanETSshallalsobetakentorefertolaterversionspublishedasanENwiththesamenumber.[1]Void.[2]EN300324-1:"VinterfacesatthedigitalLocalExchange(LE);V5.1interfaceforthesupportofAccessNetwork(AN);Part1:V5.1interfacespecification".[3]EN300347-1:"VinterfacesatthedigitalLocalExchange(LE);V5.2interfaceforthesupportofAccessNetwork(AN);Part1:V5.2interfacespecification".[4]EN300377-1:"Q3interfaceattheLocalExchange(LE)forconfigurationmanagementofV5interfacesandassociatedcustomerprofiles;Part1:Q3interfacespecification".[5]CEPTRecommendationT/S54-08E(1987):"ISDNsubscriberaccessandinstallationmaintenance".[6]ITU-TRecommendationM.3010(1996):"Principlesforatelecommunicationsmanagementnetwork".[7]ITU-TRecommendationM.3100(1995):"Genericnetworkinformationmodel".[8]ITU-TRecommendationQ.821(1993):"Stage2andstage3descriptionfortheQ3interface;Alarmsurveillance".[9]ITU-TRecommendationQ.822(1994):"Stage1,stage2andstage3descriptionfortheQ3interface;Performancemanagement".[10]CCITTRecommendationX.208(1988):"SpecificationofAbstractSyntaxNotificationOne(ASN.1)".SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)9[11]ITU-TRecommendationX.721|ISO/IEC10165-2(1992):"Informationtechnology;Opensystemsinterconnection;Structureofmanagementinformation:Definitionofmanagementinformation".[12]Void.[13]Void.[14]Void.[15]ITU-TRecommendationX.733|ISO/IEC10164-4(1992):"Informationtechnology;Opensystemsinterconnection;Systemsmanagement:Alarmreportingfunction".[16]ITU-TRecommendationX.734|ISO/IEC10164-5(1992):"Informationtechnology;Opensystemsinterconnection;Systemsmanagement:Eventreportmanagementfunction".[17]ITU-TRecommendationX.735|ISO/IEC10164-6(1992):"Informationtechnology;Opensystemsinterconnection;Systemsmanagement:Logcontrolfunctions".[18]ITU-TRecommendationX.738|ISO/IEC10164-13(1993):"Informationtechnology;Opensystemsinterconnection;Systemsmanagement:Summarizationfunction".[19]ITU-TRecommendationX.739|ISO/IEC10164-11(1993):"Informationtechnology;Opensystemsinterconnection;Systemsmanagement:Metricobjectsandattributes".[20]Void.[21]ITU-TRecommendationQ.831(1997):"FaultandperformancemanagementofV5interfaceenvironmentsandassociatedcustomerprofiles".[22]ITU-TRecommendationQ.835(1999):"LineandlinecircuittestmanagementofISDNandanaloguecustomeraccesses".[23]EN300378-1:"TelecommunicationManagementNetwork(TMN);Q3interfaceattheAccessNetwork(AN)forfaultandperformancemanagementofV5interfacesandassociateduserports;Part1:Q3interfacespecification".[24]ITU-TRecommendationQ.824.5(1997):"Stage2andstage3descriptionfortheQ3interface;Customeradministration:ConfigurationmanagementofV5interfaceenvironmentsandassociatedcustomerprofiles".[25]EN300291-1:"TelecommunicationsManagementNetwork(TMN);FunctionalspecificationofCustomerAdministration(CA)ontheOperationsSystem/NetworkElement(OS/NE)interface;Part1:Singlelineconfigurations".3Definitionsandabbreviations3.1DefinitionsForthepurposesofthepresentdocument,thefollowingtermsanddefinitionsapply:AccessNetwork(AN):seeEN300324-1[2]bearerchannel:seeEN300324-1[2]BearerChannelConnection(BCC):seeEN300347-1[3]Communicationchannel(C-channel):seeEN300324-1[2]Communicationpath(C-path):seeEN300324-1[2]controlprotocol:seeEN300324-1[2]SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)10envelopefunctionaddress:seeEN300324-1[2]layer3address:seeEN300324-1[2]leasedlines:seeEN300324-1[2]LocalExchange(LE):SeeEN300324-1[2]OperationsSystem(OS):seeITU-TRecommendationM.3010[6]protectionprotocol:seeEN300347-1[3]V5interface:seeEN300324-1[2]V5interfacemessages:thistermreferstoallFunctionElements(FEs)andotherV5protocolmessagesasdefinedinEN300324-1[2]andEN300347-1[3]whicharecommunicatedviatheV5interfaceV5timeslot:seeEN300324-1[2]3.2AbbreviationsForthepurposesofthepresentdocument,thefollowingabbreviationsapply:AISAlarmIndicationSignalANAccessNetworkASN.1AbstractSyntaxNotationOne(seeCCITTRecommendationX.208[10])BCCBearerChannelConnectionC-channelCommunicationchannelC-pathCommunicationpathCPECustomerPremiseEquipmentCRCCyclicRedundancyCheckDTMFDualToneMulti-FrequencyETExchangeTerminationIDIdentity,identifierISDNIntegratedServicesDigitalNetworkLAPV5LinkAccessProtocolforV5interfaceLCLineCircuitLELocalExchangeLFALossofFrameAlignmentLTLineTerminationM/C/OMandatory/Conditional/OptionalNENetworkElementNTNetworkTerminationOSOperationsSystemPMPerformanceManagementPSTNPublicSwitchedTelephoneNetworkRAIRemoteAlarmIndicationRDNRelativeDistinguishedNameTIBTaskInformationBaseTMNTelecommunicationsManagementNetworkTTPTrailTerminationPointSIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)114InformationmodeldiagramsTheentityrelationshipdiagramisgiveninsubclause4.1andtheinheritancehierarchy(is-arelationships)andnaminghierarchy(containmentrelationships)aregiveninsubclauses4.2and4.3,respectively.4.1EntityrelationshipdiagramTrafficmeasurementsintheLEareconcernedwithbearerchannelallocationandcommunicationchanneltrafficcharacteristics.SubclassesofITU-TRecommendationQ.822[9]currentDataobjectclassareusedtostoretrafficmeasurementdataobtainedfromtheobjectinstancetheyarecontainedin.Thecurrentdataisupdatedevery15minutes.TheobjectclassbearerchannelcurrentdatahasattributesforbearerchannelorientedperformancemeasurementsofaV5.2interface.ThemeasurementresultsareobtainedfromtheV5InterfaceobjectinstancerepresentingtheV5.2interface.Theobjectclasscommchannelcurrentdataiscontainedinaninstanceofcommchannel.IthasattributesforcommunicationchannelorientedmeasurementsrelatedtoaV5communicationchannel.AninstanceofITU-TRecommendationX.738[18]simplescannerobjectclassmaybeusedtocollectthetrafficmeasurementresultsstoredincommchannelcurrentdataandbearerchannelcurrentdataobjectinstancesinacertaintimeinterval.Itgeneratesascanreportnotificationbeingsenttothemanagingsystem.Inaddition,resultsmaybeloggedinascanreportrecordobjectinstancewhichiscontainedinalogobject.v5InterfacesimpleScannerscanReportRecordscanreportlogc1nc1nc1nc1nc1n1Element"M.3100":managed"X.721":"Q.824.5":"Q.824.5":commChannelcommChannelCurrentDatabearerChannelCurrentData"Q.831":bearerChannelHistoryDatacommChannelHistoryDataseenoteseenotec1nc11c1nc1nc11an1an1"Q.831":"Q.831":"Q.831":"X.738":"X.738":n"Q.835":anRbsTreatmentNOTE:Historydataobjectsmayalsobecontainedintherelatedcurrentdataobjects.Figure2:Entityrelationshipdiagram-V5trafficmeasurementInsteadofgeneratingscanreports,instancesoftheobjectclassesbearerchannelhistorydataandcommchannelhistorydatamaybeusedtostorethetrafficmeasurementresults.Newinstancesoftheseobjectclassesarecreatedattheendofeachinterval.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)124.2InheritancehierarchyFigure3tracestheinheritancefromthehighestlevelobject"ITU-TRecommendationX.721[11]":toptothemanagedobjectsdefinedinthepresentdocument."X.721":"X.721":toplog(note)"X.721":"X.721":discriminatoreventForwarding-(note)Discriminator"X.721":"X.721":"X.721":logRecordeventLogRecordalarmRecord(note)(note)"X.738":"M.3100":scanReportRecordmanagedElement"Q.822":"Q.831":bearerCh-historyDataannelHistoryData(note)"Q.831":commCh-annelHistoryData"X.739":"X.738":homoge-"X.738":scannerneousScannersimpleScanner(note)(note)"Q.822":"Q.831":bearerCh-currentDataannelcurrentData(note)"Q.831":commCh-annelCurrentData"Q.835":anRbsTreatmentNOTE:Non-instantiableobjectclass.Figure3:InheritancehierarchySIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)134.3NaminghierarchyFigure4showsthenaming(i.e.containment)relationshipsfortheLE'smanagedobjectsassociatedwithfaultandperformancemanagement."M.3100":managedElement"Q.835":"Q.824.5":"X.721":"X.738":anRbsTreatmentv5InterfacelogsimpleScanner"X.738":"Q.831":bearerCh-"Q.824.5":scanReportRecordannelCurrentDatacommChannel"Q.831":bearerCh-annelHistoryData"Q.831":commCh-annelCurrentData"Q.831":commCh-annelHistoryDataNOTE:Historydataobjectsmayalsobenamedfromtherelatedcurrentdataobjects.Figure4:Naminghierarchy5InformationmodeldescriptionThisclauseprovidesahigh-levelinformaldescriptionoftheinformationmodelforfaultandperformancemanagementoftheLE.Subclause5.1containsabriefdescriptionforeachnewobjectclassorpackageusedinthemodelasfarasitisnotdescribedinthereferencedocuments.Thedescriptioncovers:-thepurposeofthenewobjectclassorpackage;-theattributesdefinedorinheritedfortheobjectclassorpackage;-thecontentsoftheeventreportsdefinedinthepresentdocument;-therelationshipoftheobjectclasstootherobjectclasses;-theapplicabilityofthepackages.Attributeswhicharecommontoseveralobjectclassesaredescribedinsubclause5.2.Subclause5.3describesactionswhichareinfluencingseveralobjectclassesintheinformationmodel.Subclause5.4describesthecommonaspectsofthenotificationsusedintheinformationmodel.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)145.1ManagedobjectclassesdescriptionSubclause5.1isdividedintosubclauseswhichdescribethefragmentsoftheinformationmodel.5.1.1V5interfacefragmentInthisfragment,thefollowingobjectclassesareused.TheyaredefinedinITU-TRecommendationQ.824.5[24]:-V5interface(v5Interface);-V5TTP(v5Ttp);-V5timeslot(v5TimeSlot).5.1.1.1V5interface(v5Interface)V5interfaceisanobjectclassrepresentingaV5.xinterface(x=1,2,.)asanabstractentityofitsownright.ThismanagedobjectclassisdefinedinITU-TRecommendationQ.824.5[24].ForV5faultmanagementthefollowingpackagesshallbeinstantiatedwithinstancesofthisobjectclass:-"ITU-TRecommendationM.3100[7]":operationalStatePackage;-"ITU-TRecommendationM.3100[7]":tmnCommunicationsAlarmInformationPackage.ThefollowingeventsshallbereportedbyinstancesofthisobjectclassusingthecommunicationsAlarmnotification(forthespecificationofthealarmreportsandforcrossreferencetotherelevantV5protocolspecifications,seeannexA):a)commoncontrolprotocoltimeouterrors;b)portcontrolprotocollayer3addresserrors;c)linkcontrolprotocollayer3addresserrors;d)BCCprotocoltimeouterrors;e)protectionprotocoltimeouterrors;f)PSTNprotocoltimeouterrors;g)PSTNprotocollayer3address;h)V5Interfaceidentificationfailures;i)linkcontrolprotocoldatalinkfailures;j)BCCprotocoldatalinkfailures;k)protectionprotocoldatalinkfailures;l)commoncontrolprotocoldatalinkfailures;m)PSTNprotocoldatalinkfailures;n)V5interfaceprovisioningvariantmismatchfailure.Thefollowingeventsmaybereportedoptionally:a)commoncontrolprotocolsyntaxerrors;b)controlprotocollayer3addresserrors;c)BCCprotocolsyntaxerrors;d)protectionprotocolsyntaxerrors.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)155.1.1.2V5trailterminationpoint(v5Ttp)AV5trailterminationpointisanobjectclassrepresentinga2Mbit/sinterfaceoftheLEthatisusedasV5.1interfaceoraspartofaV5.2interface.ThismanagedobjectclassisdefinedinITU-TRecommendationQ.824.5[24].ForV5faultmanagementthefollowingpackagesshallbeinstantiatedwithinstancesofthisobjectclass:-"ITU-TRecommendationM.3100[7]":tmnCommunicationsAlarmInformationPackage.ThefollowingeventshavetobereportedbyinstancesofthisobjectclassusingthecommunicationsAlarmnotification(forthespecificationofthealarmreportsandforcrossreferencetotherelevantV5protocolspecifications,seeannexA):a)V5interfacelayer1receptionofAlarmIndicationSignal(AIS);b)V5interfacelayer1receptionofRemoteAlarmIndication(RAI);c)V5interfacelayer1LossofFrameAlignment(LFA);d)linkidentificationfailures;e)linkcontrolprotocoltimeouterrors;f)linkcontrolprotocolerrorswhile"OutofService";g)linkcontrolprotocollayer3addresserrors;h)CRCerrors;i)internalfailures.Thefollowingeventsmaybereportedoptionally:-linkcontrolprotocolsyntaxerrors.5.1.1.3V5timeslot(v5TimeSlot)AV5timeslotisanobjectclassrepresentinga64kbit/schannelofaV5interfacethatiseitherusedasbearerchannelorascommunicationchannel.ThismanagedobjectclassisdefinedinITU-TRecommendationQ.824.5[24].ForV5faultmanagementthefollowingpackagesshallbeinstantiatedwithinstancesofthisobjectclassifthetimeslotisusedasacommunicationchannel:-"ITU-TRecommendationM.3100[7]":tmncommunicationsalarminformationpackage.ThefollowingeventshavetobereportedbyinstancesofthisobjectclassusingthecommunicationsAlarmnotification(forthespecificationofthealarmreportsandforcrossreferencetotherelevantV5protocolspecificationsseeannexA):-cessationofflagsonaC-channel.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)165.1.2AccessportfragmentInthisfragmentthefollowingobjectclassesareused.TheyaredefinedinEN300291-1[25]:a)Virtualanalogueaccess(virtualAnalogueAccessR1);b)Virtualbasicrateaccess(virtualBasicRateAccessR1);c)Virtualprimaryrateaccess(virtualPrimaryRateAccessR1);d)Virtualleasedaccess(virtualLeasedAccessR1).5.1.2.1Virtualanalogueaccess(virtualAnalogueAccessR1)Avirtualanalogueaccessisanobjectclassrepresentinganimageofananalogue(PSTN)customeraccessportwhichislocatedinanANandconnectedtotheLEviaV5interface.ThismanagedobjectclassisdefinedinEN300291-1[25].ForV5faultmanagementthefollowingpackagesshallbeinstantiatedwithinstancesofthisobjectclass:-"ITU-TRecommendationM.3100[7]":tmnCommunicationsAlarmInformationPackage.ThefollowingeventsshallbereportedbyinstancesofthisobjectclassusingthecommunicationsAlarmnotification(forthespecificationofthealarmreportsandforcrossreferencetotherelevantV5protocolspecifications,seeannexA):a)portcontrolprotocoltimeouterrors;b)portcontrolprotocolerrorswhile"OutOfService";c)portcontrolprotocollayer3addresserror;d)PSTNprotocoltimeouterrors;e)PSTNprotocollayer3addresserror.Thefollowingeventsmaybereportedoptionally:a)portcontrolprotocolsyntaxerrors;b)PSTNprotocolsyntaxerrors.Inaddition,thefollowingpackagemaybeinstantiatedwithinstancesofthisobjectclassiftheassociatedinterfaceisaV5.2interfaceandtheinstancesupportsit:-"ITU-TRecommendationQ.824.5[24]":anfaultreportedpackage.5.1.2.2Virtualbasicrateaccess(virtualBasicRateAccessR1)AvirtualbasicrateaccessisanobjectclassrepresentinganimageofanISDNbasiccustomeraccessportwhichislocatedinanANandconnectedtotheLEviaV5interface.ThismanagedobjectclassisdefinedinEN300291-1[25].ForV5faultmanagementthefollowingpackagesshallbeinstantiatedwithinstancesofthisobjectclass:-"ITU-TRecommendationM.3100[7]":tmnCommunicationsAlarmInformationPackage.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)17ThefollowingeventsshallbereportedbyinstancesoftheobjectclassvirtualbasicrateaccessusingthecommunicationsAlarmnotification(forthespecificationofthealarmreportsandforcrossreferencetotherelevantV5protocolspecifications,seeannexA):a)ISDNlayer1activationfaults(onlyforanaccesswithpermanentlayer1requestedinthedchannelactivationattribute);b)ISDNlayer2faults(onlyforanaccesswithpermanentlayer2requestedinthedChannelActivationattribute);c)ISDNlayer3faults;d)portcontrolprotocoltimeouterrors;e)portcontrolprotocolerrorswhile"OutofService";f)portcontrolprotocollayer3addresserror.Thefollowingeventsmaybereportedoptionally:-portcontrolprotocolsyntaxerrors.Inaddition,thefollowingpackagemaybeinstantiatedwithinstancesofthisobjectclassiftheassociatedinterfaceisaV5.2interfaceandtheinstancesupportsit:-"ITU-TRecommendationQ.824.5[24]":anfaultreportedpackage.ForV5performancemanagement,thefollowingpackagesshallbeinstantiatedwithinstancesoftheobjectclassvirtualbasicrateaccesswheneveradegradedqualityofserviceoftheaccessdigitalsectionhastobereportedtotheOS:-"ITU-TRecommendationQ.824.5[24]":gradingalarmpackage.5.1.2.3Virtualprimaryrateaccess(virtualPrimaryRateAccessR1)AvirtualprimaryrateaccessisanobjectclassrepresentinganimageofanISDNprimaryratecustomeraccessportwhichislocatedinanANandconnectedtotheLEviaV5interface.ThismanagedobjectclassisdefinedinEN300291-1[25].ForV5faultmanagementthefollowingpackagesshallbeinstantiatedwithinstancesofthisobjectclass:-"ITU-TRecommendationM.3100[7]":tmnCommunicationsAlarmInformationPackage.ThefollowingeventsshallbereportedbyinstancesoftheobjectclassvirtualprimaryrateaccessusingthecommunicationsAlarmnotification(forthespecificationofthealarmreportsandforcrossreferencetotherelevantV5protocolspecificationsseeannexA):a)ISDNlayer1activationfaults;b)ISDNlayer2faults;c)ISDNlayer3faults;d)portcontrolprotocoltimeouterrors;e)portcontrolprotocolerrorswhile"OutofService";f)portcontrolprotocollayer3addresserror.Thefollowingeventsmaybereportedoptionally:-portcontrolprotocolsyntaxerrors.Inaddition,thefollowingpackagemaybeinstantiatedwithinstancesofthisobjectclassiftheassociatedinterfaceisaV5.2interfaceandtheinstancesupportsit:-"ITU-TRecommendationQ.824.5[24]":anFaultReportedPackage.SIST EN 300 379-1 V1.2.1:2003
ETSIETSIEN300379-1V1.2.1(1999-10)18ForV5performancemanagementthefollowingpackagesshallbeinstantiatedwithinstancesoftheobjectclassvirtualprimaryrateaccesswheneveradegradedqualityofserviceoftheaccessdigitalsectionhastobereportedtotheOS:-"ITU-TRecommendationQ.824.5[24]":gradingAlarmPackage.5.1.2.4Virtualleasedaccess(virtualLeasedAccessR1)Avirtualleasedaccessisanobjectclassrepresentinganimageofanaccessportservingasemi-permanentleasedlinewhichislocatedinanANandconnectedtotheLEviaaV5interface.ThismanagedobjectclassisdefinedinEN300291-1[25].ForV5faultmanagementthe"ITU-TRecommendationM.3100[7]":tmnCommunicationsAlarmInformationpackageshouldbeinstantiatedwithinstancesofthisobjectclass.EventsasapplicableshouldbereportedbyinstancesofthisobjectclassusingthecommunicationsAlarmnotification(seealsoannexA).NOTE:Intheabsenceofclearstandardsforeventreportingonleasedlinesitisnotappropriatetostatemandatoryrequirements.5.1.3CommunicationpathfragmentInthisfragmentthefollowingobjectclassesareused.TheyaredefinedinITU-TRecommendationQ.824.5[24]:-"V5communicationchannel(commCh
...