ETSI I-ETS 300 637 ed.1 (1996-09)

Network Aspects (NA); Functional specification of traffic management on the Network Element/Operations System (NE/OS) interface

DI/NA-043314

Omrežni vidiki (NA) – Funkcijska specifikacija za upravljanje prometa na vmesniku omrežni element/operacijski sistem (NE/OS)

General Information

• Status: Published
• Publication Date: 23-Sep-1996
• Technical Committee: NA 4 - Network Architecture, Operations, Maintenance, Principle & Performance
• Current Stage: 12 - Completion
• Due Date: 20-Sep-1996
• Completion Date: 24-Sep-1996
• Ref Project: SIST I-ETS 300 637 E1:2003 - Network Aspects (NA); Functional specification of traffic management on the Network Element/Operations System (NE/OS) interface

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Omrežni vidiki (NA) – Funkcijska specifikacija za upravljanje prometa na vmesniku omrežni element/operacijski sistem (NE/OS)Network Aspects (NA); Functional specification of traffic management on the Network Element/Operations System (NE/OS) interface33.040.40Podatkovna komunikacijska omrežjaData communication networksICS:Ta slovenski standard je istoveten z:I-ETS 300 637 Edition 1SIST I-ETS 300 637 E1:2003en01-december-2003SIST I-ETS 300 637 E1:2003SLOVENSKI
STANDARD
INTERIMEUROPEANI-ETS 300 637TELECOMMUNICATIONSeptember 1996STANDARDSource: ETSI TC-NAReference: DI/NA-043314ICS:33.020Key words:TMN, Interface, NE, trafficNetwork Aspects (NA);Functional specification of traffic managementon the Network Element/Operations System (NE/OS) interfaceETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: [e-mail].: [phone] - Fax: [phone]Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1996. All rights reserved.SIST I-ETS 300 637 E1:2003

Page 2I-ETS 300 637: September 1996Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST I-ETS 300 637 E1:2003

Page 3I-ETS 300 637: September 1996ContentsForeword.7Introduction.71Scope.92Normative references.93Definitions and abbreviations.103.1Definitions.103.2Abbreviations.114Functional requirements.124.1Status and performance monitoring functions.124.2Traffic management control functions.124.3Reference data functions.124.4Administrative functions.134.5Modelling methodology.135Information model diagrams.135.1Entity relationship diagrams.135.2Inheritance hierarchy.175.3Naming hierarchy.186Information model description.186.1Object class descriptions.196.1.1Managed element fragment.196.1.1.1Managed element (managedElement).196.1.1.2Congestion level indication (congestionLevelIndication).196.1.1.3Observed destination (observedDestination).196.1.1.4Hard to reach destination (htrDestination).206.1.1.5Exchange termination point sub-group (xtpsg).216.1.1.6Traffic management circuit end point sub-group(tmCircuitEndPointSubgroup).216.1.2Status and performance monitoring fragment.226.1.2.1Current data (currentData).226.1.2.2CircuitEndPointSubgroup current data(circuitEndPointSubgroupCurrentData).226.1.2.3Observed destination current data(observedDestinationCurrentData).236.1.2.4Exchange performance current data(exchangePerformanceCurrentData).246.1.2.5Traffic control current data (trafficControlCurrentData).256.1.2.6Traffic management circuitEndPointSubgroup currentdata (tmCircuitEndPointSubgroupCurrentData).266.1.2.7Controlled circuitEndPointSubgroup current data(controlledCircuitEndPointSubgroupCurrentData).266.1.2.8Traffic management observed destination current data(tmObservedDestinationCurrentData).276.1.2.9Traffic management exchange performance current data(tmExchangePerformanceCurrentData).276.1.2.10Traffic Management traffic control current data(tmTrafficControlCurrentData).286.1.2.11History data (historyData).286.1.2.12CircuitEndPointSubgroup history data(circuitEndPointSubgroupHistoryData).28SIST I-ETS 300 637 E1:2003

Page 4I-ETS 300 637: September 19966.1.2.13Controlled circuitEndPointSubgroup history data(controlledCircuitEndPointSubgroupHistoryData).296.1.2.14Observed destination history data(observedDestinationHistoryData).306.1.2.15Exchange performance history data(exchangePerformanceHistoryData).306.1.2.16Traffic control history data (trafficControlHistoryData).316.1.2.17Simple scanner (simpleScanner).326.1.3Traffic management control fragment.326.1.3.1Traffic control (trafficControl).326.1.3.2Destination code control function.336.1.3.3Destination code control (destinationCodeControl).346.1.3.4Destination code control group (dccGroup).366.1.3.5Cancel to (cancelTo).376.1.3.6Cancellation of routing from (cancelFrom).386.1.3.7Skip control (skip).396.1.3.8Temporary alternative routing to a circuit sub-group(tarTo).406.1.3.9Temporary alternative routing from a circuit sub-group(tarFrom).416.1.3.10Cancel rerouted overflow (cancelRerouted).436.1.3.11Selective Circuit Reservation Control (scr).446.1.3.12Selective circuit reservation affected traffic(scrAffectedTraffic).456.2Definition of attributes.466.2.1RDN.466.2.2Performance attributes.476.3Actions description.476.4Notifications description.477Formal object class definitions.487.1Definition of object classes.487.1.1Managed element fragment.487.1.1.1Managed element (managedElement).487.1.1.2Congestion level indication (congestionLevelIndication).487.1.1.3Observed destination (observedDestination).497.1.1.4Hard to reach destination (htrDestination).497.1.1.5Exchange termination point sub-group (xtpsg).507.1.1.6Traffic management circuit end point sub-group(tmCircuitEndPointSubgroup).507.1.2Status and performance monitoring fragment.507.1.2.1Current data (currentData).507.1.2.2CircuitEndPointSubgroup current data(circuitEndPointSubgroupCurrentData).507.1.2.3Observed destination current data(observedDestinationCurrentData).517.1.2.4Exchange performance current data(exchangePerformanceCurrentData).517.1.2.5Traffic control current data (trafficControlCurrentData).527.1.2.6Traffic management circuitEndPointSubgroup currentdata (tmCircuitEndPointSubgroupCurrentData).527.1.2.7Controlled circuitEndPointSubgroup current data(controlledCircuitEndPointSubgroupCurrentData).537.1.2.8Traffic management observed destination current data(tmObservedDestinationCurrentData).537.1.2.9Traffic management exchange performance current data(tmExchangePerformanceCurrentData).547.1.2.10Traffic Management traffic control current data(tmTrafficControlCurrentData).547.1.2.11History data (historyData).547.1.2.12CircuitEndPointSubgroup history data(circuitEndPointSubgroupHistoryData).55SIST I-ETS 300 637 E1:2003

Page 5I-ETS 300 637: September 19967.1.2.13Controlled circuitEndPointSubgroup history data(controlledCircuitEndPointSubgroupHistoryData).557.1.2.14Observed destination history data(observedDestinationHistoryData).567.1.2.15Exchange performance history data(exchangePerformanceHistoryData).567.1.2.16Traffic control history data (trafficControlHistoryData).567.1.2.17Simple scanner (simpleScanner).567.1.3Traffic management control fragment.577.1.3.1Traffic control (trafficControl).577.1.3.2Destination code control (destinationCodeControl).577.1.3.3Destination code control group (dccGroup).587.1.3.4Cancel to (cancelTo).597.1.3.5Cancellation of routing from (cancelFrom).597.1.3.6Skip control (skip).607.1.3.7Temporary alternative routing to a circuit sub-group(tarTo).607.1.3.8Temporary alternative routing from a circuit sub-group(tarFrom).617.1.3.9Cancel rerouted overflow (cancelRerouted).627.1.3.10Selective Circuit Reservation Control (scr).627.1.3.11Selective circuit reservation affected traffic(scrAffectedTraffic).637.2Name bindings.647.3Definition of packages.667.4Definition of attributes.687.4.1General traffic management attributes.687.4.2Naming attributes.727.4.3Performance monitoring attributes.727.5Definition of behaviours.757.6Definition of actions.757.7Definition of notifications.757.8ASN.1 defined types module.75Annex A (normative):Assignment of the performance attributes to the individual xtspg subclasses.79Annex B (informative):TMN management service "Traffic Management".80Annex C (informative):Correlation between E.412 traffic controls and object classes.81Annex D (informative):Differentiation of direct and alternate routed traffic for cancel to and cancelfrom controls.82Annex E (informative):Use of ITU-T Recommendation Q.822 for traffic measurements.84E.1Introduction.84E.2Overview of the performance management information model.84E.3Initial configuration.84E.3.1Current data.84E.3.2History data.85E.3.3Simple scanner.85E.4Autonomous reporting.86E.5Polled reporting.86E.6Changes to the report.86E.7Conclusions.86SIST I-ETS 300 637 E1:2003

Page 6I-ETS 300 637: September 1996Annex F (informative):Examples to illustrate the effect of the key attribute priority rules of thenetwork management control object classes on the selection of a controlinstance applicable for a call.89F.1Object class destinationCodeControl.89F.1.1Example 1 for a destinationCodeControl database.89F.1.2Example 2 for a destinationCodeControl database.89F.2Object class cancelTo.90F.2.1Example 1 for a cancelTo database.90F.2.2Example 2 for a cancelTo database.91F.3Other circuitEndPointSubgroup related control object classes.92Annex G (informative):Object classes defined in other documents providing reference data relevantfor traffic management.93G.1Circuit sub-group reference data.93G.2Destination related reference data.93G.3Exchange related reference data.93G.4Call routing related reference data.93G.4.1xtpsgComb.93G.4.2orderedListXTPSGComb.93G.5Traffic control related reference data.94Annex H (informative):References to corresponding object classes and name bindings defined inITU-T Recommendation Q.823 (1996).95Annex I (informative):Bibliography.96History.97SIST I-ETS 300 637 E1:2003

Page 7I-ETS 300 637: September 1996ForewordThis Interim European Telecommunication Standard (I-ETS) has been produced by the Network Aspects(NA) Technical Committee of the European Telecommunications Standards Institute (ETSI).An ETSI standard may be given I-ETS status either because it is regarded as a provisional solution aheadof a more advanced standard, or because it is immature and requires a "trial period". The life of an I-ETSis limited to three years after which it can be converted into an ETS, have it's life extended for a furthertwo years, be replaced by a new version, or be withdrawn.Proposed announcement dateDate of adoption of this I-ETS:30 August 1996Date of latest announcement of this I-ETS (doa):31 December 1996IntroductionThe objective of traffic management is to enable as many calls as possible to be successfully completed.This objective is met by maximizing the use of all available resources in any situation. It is also to be seenas the function of supervising the performance of a network, and to be able, if necessary, to take action tocontrol the flow of traffic for optimizing the utilisation of the network capacity.The information model given in this I-ETS provides a common view for the performance data retrievalfrom the Network Element (NE), and for the administration of controls and instructions from theOperations System (OS) to the NE. The performance data provide information for the activation of trafficmanagement controls, for the validation of former traffic management actions, and as input data for futuretraffic management actions.SIST I-ETS 300 637 E1:2003

Page 8I-ETS 300 637: September 1996Blank pageSIST I-ETS 300 637 E1:2003

Page 9I-ETS 300 637: September 19961ScopeThis Interim European Telecommunication Standard (I-ETS) provides an information model which coversthe management aspects of the "traffic management" services functions in an exchange, as defined in theETR 047. The application of this I-ETS is limited only to circuit-switched networks. Traffic management forSignalling System No.7 (SS7) networks and intelligent networks are outside the scope of this I-ETS.This I-ETS focuses only on the information model at the Q3 interface between Network Element (NE) andOperations System (OS).The following restrictions to the scope of this I-ETS apply:-this I-ETS does not cover traffic measurement aspects;-the handling and processing of traffic management related information on OS level and theforwarding of these data on OS level are out of the scope of this I-ETS.-network performance data are needed as input for the traffic management controls. Sometimes thesame data can be used for traffic measurement, but this coincidence is ignored in this context. Thenetwork performance data are identified and modelled as far as they are relevant and when theycannot be retrieved from other documents;-functions listed in Task Information Base B (TIB B) for traffic management (ETR 047,subclause 5.5) which are supportable by information models defined in other ETSI and ITU-Tdocuments are not redefined in this I-ETS. Those information models are either referenced or, ifnecessary, inherited;-as far as possible and sensible, the functions defined in the Open Systems Interconnection (OSI)system management framework are considered.2Normative referencesThis I-ETS incorporates by dated and undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this I-ETS only when incorporated in it by amendment or revision. For undated references thelatest edition of the publication referred to applies.[1]I-ETS 300 292 (1995): "Network Aspects (NA); Functional specification of callrouting information management on the Operations System/Network Element(OS/NE) interface".[2]prI-ETS 300 293 (1996): "Telecommunications Management Network (TMN);Generic managed objects".[3]CCITT Recommendation E.410 (1992): "International network management -General information".[4]CCITT Recommendation E.411 (1992): "International network management -Operational guidance".[5]CCITT Recommendation E.412 (1992): "Network management controls".[6]CCITT Recommendation E.502 (1992): "Traffic measurement requirements fordigital telecommunication exchanges".[7]CCITT Recommendation M.3100 (1992): "Generic network information model".[8]CCITT Recommendation Q.763 (1992): "Formats and codes of the ISDN userpart of Signalling System No.7".SIST I-ETS 300 637 E1:2003

Page 10I-ETS 300 637: September 1996[9]ITU-T Recommendation Q.822 (1994): "Stage 1, stage 2 and stage 3description for the Q3 interface - Performance management".[10]CCITT Recommendation X.720 (1992): "Information technology - OpenSystems Interconnection - Structure of management information: Managementinformation model".[11]CCITT Recommendation X.721 (1992): "Information technology - OpenSystems Interconnection - Structure of management information: Definition ofmanagement information".[12]CCITT Recommendation X.730 (1992): "Information technology - OpenSystems Interconnection - Systems Management: Object managementfunction".[13]CCITT Recommendation X.731 (1992): "Information technology - OpenSystems Interconnection - Systems Management: State management function".[14]CCITT Recommendation X.732 (1992): "Information technology - OpenSystems Interconnection - Systems Management: Attributes for representingrelationships".[15]CCITT Recommendation X.733 (1992): "Information technology - OpenSystems Interconnection - Systems Management: Alarm reporting function".[16]CCITT Recommendation X.734 (1992): "Information technology - OpenSystems Interconnection - Systems Management: Event report managementfunction".[17]CCITT Recommendation X.735 (1992): "Information technology - OpenSystems Interconnection - Systems Management: Log control function".[18]ITU-T Recommendation X.738 (1993): "Information technology - Open SystemsInterconnection - Systems management: Summarization function".[19]ITU-T Recommendation X.739 (1993): "Information technology - Open SystemsInterconnection - Systems Management: Metric objects and attributes".[20]ITU-T Recommendation X.746 (1995): "Information technology - Open SystemsInterconnection - Systems management: Scheduling function".3Definitions and abbreviations3.1DefinitionsFor the purposes of this I-ETS, the following definitions apply:answer signal: See CCITT Recommendation E.410 [3].bid: See CCITT Recommendation E.410 [3].circuit: See CCITT Recommendation E.410 [3].NOTE 1:Only the exchange termination point that terminates a circuit is visible on NEmanagement level.circuit group: See CCITT Recommendation E.410 [3].NOTE 2:On the NE management level it is represented by the exchange termination pointsub-groups addressing the identical adjacent exchange. For traffic management, acircuit group is not visible on NE management level.SIST I-ETS 300 637 E1:2003

Page 11I-ETS 300 637: September 1996circuit sub-group: See CCITT Recommendation E.410 [3].NOTE 3:On the NE management level the view on a circuit sub-group is represented by"ITU-T Recommendation M.3100 (1996)": circuitEndPointSubgroup resp."prI-ETS 300 293 (1996)": exchange termination point sub-group.destination: See CCITT Recommendation E.410 [3].NOTE 4:A destination identified by one or more destination codes, i.e. digit combinations.destination code: See CCITT Recommendation E.410 [3].seizure: See CCITT Recommendation E.410 [3].switching node: An exchange represented by an instance of "CCITT Recommendation M.3100 (1992)":managed element or a subclass of it.congestion level: An indicator for the present congestion situation in an exchange and an indicator forthe degree of traffic management actions to be taken. It is expressed by the following Machine CongestionLevels (MCL):-MCL0: No exchange congestion.The exchange works well, no traffic management action needs to be done with respect to themachine load;-MCL1: moderate exchange congestion, the exchange keeps working. Some calls may get rejectedif no traffic management action is taken.This is a warning, the exchange may have activated internal traffic control actions. No additionaltraffic should be directed to this exchange;-MCL2: serious congestion level, the exchange is no more able to handle all offered traffic.More severe traffic management actions are to be performed to reduce the exchange load;-MCL3: complete inability of the exchange to process calls.With high probability, the exchange is not able to handle any calls. No further calls should bedirected to this exchange.direct routed traffic: A collection of offered calls for which a circuit sub-group would be the first choice.alternate routed traffic: A collection of offered calls for which a circuit sub-group would be the overflowcase.3.2AbbreviationsFor the purposes of this I-ETS, the following abbreviations apply:ACCAutomatic Congestion ControlCCSCommon Channel SignallingDCCDestination Code ControlHTRHard To ReachMCLMachine Congestion LevelsM/C/OMandatory/Conditional/OptionalNENetwork ElementOSOperations SystemOSIOpen Systems InterconnectionRDNRelative Distinguished NameSCRSelective Circuit ReservationSS7Signalling System No.7TARTemporary Alternative RoutingTIBTask Information BaseTMNTelecommunications Management NetworkSIST I-ETS 300 637 E1:2003

Page 12I-ETS 300 637: September 19964Functional requirementsThe functional requirements are derived from the TIB A and TIB B specified in ETR 047 for the trafficmanagement service (see annex B). They cover the following management service function areas:-status monitoring functions;-performance monitoring functions;-control functions;-reference data;-administrative functions.The status and performance monitoring functions considered in the model are based on measurementitems specified in CCITT Recommendation E.502 [6] (which is internally based on CCITTRecommendation E.411 [4]).The traffic management control functions considered in the model are based on controls specified inCCITT Recommendation E.412 [5].4.1Status and performance monitoring functionsA wide range of status and performance monitoring functions is still covered by the information modelprovided in ITU-T Recommendation Q.822 [9]. An excerpt of this recommendation is given in annex E.Therefore this I-ETS contains only those parts of the information model which cannot be referenced toITU-T Recommendation Q.822 [9].For the presentation of the performance data at the NE-OS interface the use of the simpleScanner objectclass and its scan report notification as defined in ITU-T Recommendation X.738 [18] were chosen, asdue to the potential amount of performance data their retrieval from one simpleScanner object instanceper observed object class is assumed to fit more into a five minute interval of time than their retrieval fromone historyData object instance per observed object instance.4.2Traffic management control functionsThe status and performance monitoring functions provide the input data for traffic management decisionswhich may lead to the initiation of network management control functions.This I-ETS provides an information model covering network management control functions defined inCCITT Recommendation E.412 [5]. Annex C indicates by which object class the considered networkmanagement control functions are covered.It was recognized that the circuit turndown/busying/blocking traffic control is not to be considered, as thiscontrol seems nowadays no longer applicable in a sensible way. More sophisticated controls are availablein a Telecommunications Management Network (TMN) environment.Furthermore it was identified that the circuit directionalization traffic control is covered by the cancel toobject class when an instance of cancel to is valid for all traffic types and traffic sources. Therefore thistraffic control is not considered as well.The modelling of the Q3 aspects of the Automatic Congestion Control (ACC) and the automaticdestination control are for further study.NOTE:These controls are being modelled in draft ITU-T Recommendation Q.823 which waselaborated in parallel with this I-ETS.4.3Reference data functionsReference data provides the network traffic manager with information retained by the NE about itsresources. This includes information about the topology of the NE and its relationship to the network aswell as data on the NEs capacities and capabilities.SIST I-ETS 300 637 E1:2003

Page 13I-ETS 300 637: September 1996CCITT Recommendations E.411 [4] and E.502 [6] recognize the need for reference data as part of thedata required for traffic management.Reference data is usually long term in nature, that is, it does not change rapidly. However, when changedor modified, this should be reported immediately to the OS. An additional requirement imposed by the OSis the need to resynchonize its database at any time with the data base of the NE. This will allow recoveryfrom events like loss of data link, data base corruption, etc.The relevant reference data object classes are or will be defined as part of other information models, e.g.like I-ETS 300 292 [1]. Annex G identifies the already defined object classes and corresponding attributesthat are relevant for traffic management. In detail, the following minimum set was identified:-circuitEndPointSubgroup resp. xtpsg;-traffic direction;-signalling capability;-bearer capability;-total number of circuits in circuitEndPointSubgroup resp. xtpsg;-adjacent exchange id;-xtpsgComb;-xtpsgComb identity;-set of corresponding xtpsgs;-algorithm used for assigning traffic to the corresponding xtpsgs;-orderedListXTPSGComb;-orderedListXTPSGComb identity;-set of corresponding XTPSGCombs;-algorithm used for assigning traffic to the corresponding XTPSGCombs.Reference data can either be retrieved directly from the NE or from another OS, depending upon thespecific implementation.4.4Administrative functionsThe administrative functions listed in subclause 5.5 of ETR 047 (TIB B, item 6) are mainly alarm reportingfunctions, event report management functions, and scheduling functions as defined in CCITTRecommendations X.733 [15], X.734 [16], respectively ITU-T Recommendation X.746 [20] and modelledin CCITT Recommendation X.721 [11]. Some of the administrative functions are covered as well byETR 088.The retrieval of routing information is provided by the call routing information model given inI-ETS 300 292 [1].4.5Modelling methodologyThe modelling techniques described in ETR 078 (Methodology for Specification of TMN Interfaces) andETR 046 (Modelling Guidelines) have been regarded.In the modelling work the definitions of the supporting object classes given in the OSI systemmanagement framework (X.700 series) and in ETR 088 were adopted.The managed object classes specified in this I-ETS are defined in line with I-ETS 300 292 [1],prI-ETS 300 293 [2], CCITT Recommendations M.3100 [7] and X.721 [11], and ITU-T RecommendationQ.822 [9].5Information model diagrams5.1Entity relationship diagramsFigure 1 gives the entity relationship diagram for the object classes defined in the managed elementfragment, and figure 2 gives the entity relationship diagram for the object classes defined in the status andSIST I-ETS 300 637 E1:2003

Page 14I-ETS 300 637: September 1996performance monitoring fragment. For clearness, the inheritances of the current data and history dataobject classes is not drawn in figure 2. These inheritances are shown in table 1.In figure 3 the entity relationship diagram for the traffic management control fragment is provided.The relationships of object classes which are referenced in this I-ETS but defined in other documents areshown in this I-ETS only as far as it is needed for the clarification of their relationships in the trafficmanagement context.Containment, naming relationcontainsIs associated withis ass. w.htrDestinationmanaged-ElementM.3100:congestionLevel-Indicationcontains1n1mnis ass. w.nprI-ETS 300 293:xtpsgnis ass. w.nM.3100circuitEndPoint-SubgroupFigure 1: Managed element fragmentSIST I-ETS 300 637 E1:2003

Page 15I-ETS 300 637: September 1996containsmanaged-ElementM.3100:CurrentDataPerformance-tmExchange-prI-ETS 300 293:xtpsgobserved-DestinationX.738:simpleScannercontainscontainsnn1111n1nn11111contains11contains111observedDestination-HistoryDatais ass. w.nmcontains1Containment, naming relationcontainsIs associated withis ass. w.nncontains11contains11scansscansscans1scanstmObserved-DestinationCurrent-DatatmCircuitEndPoint-SubgroupCurrentData-HistoryDataPerformance-exchange-tmTrafficControl-CurrentDatatrafficControl-HistoryDatatrafficControl(subclasses)M.3100:circuitEnd-PointSubgroup/circuitEndPoint-SubgroupHistoryDataFigure 2: Status and performance monitoring fragmentIt is to be considered that the simpleScanner object class can be as well associated with the currentDatasubclasses, not using the historyData subclasses for the retrieval of performance data.SIST I-ETS 300 637 E1:2003

Page 16I-ETS 300 637: September 1996Containment, naming relationcontainsSubclassing of an object classis aIs associated withis ass. w.nnn1ncancelTocancelFromskipntarTotarFromcancelReroutedcontains1nnn1is ass. w.is ais ass. w.1is ass. w.11mscrAffected-TraffictrafficControlscrn1nis ass. w.dccGroupprI-ETS 300 293:xtpsgmanaged-ElementM.3100:destination-CodeControlM.3100:circuitEnd-PointSubgroup/Figure 3: Traffic management control fragmentSIST I-ETS 300 637 E1:2003

Page 17I-ETS 300 637: September 19965.2Inheritance hierarchyTable 1"CCITT Recommendation X.721 (1992)":topcongestionLevelIndicationobservedDestinationhtrDestination"ITU-T Recommendation M.3100 (1996)":circuitEndPointSubgrouptmCircuitEndPointSubgroup"ITU-T Recommendation X.738 (1993)":scanner"ITU-T Recommendation Q.822 (1994)":currentDatacircuitEndPointSubgroupCurrentDatatmCircuitEndPointSubgroupCurrentDatacontrolledCircuitEndPointSubgroupCurrentDataobservedDestinationCurrentDatatmObservedDestinationCurrentDataexchangePerformanceCurrentDatatmExchangePerformanceCurrentDatatrafficControlCurrentDatatmTrafficControlCurrentData"ITU-T Recommendation Q.822 (1994)":historyDatacircuitEndPointSubgroupHistoryDatacontrolledCircuitEndPointSubgroupHistoryDataobservedDestinationHistoryDataexchangePerformanceHistoryDatatrafficControlHistoryDatatrafficControldestinationCodeControlcancelTocancelFromskiptarTotarFromcancelReroutedscrdccGroupscrAffectedTrafficThis table shows the inheritances of the object classes defined in this I-ETS. The inheritances of objectclasses referenced from other documents but not subclassed in this I-ETS are defined in the referenceddocuments.SIST I-ETS 300 637 E1:2003

Page 18I-ETS 300 637: September 19965.3Naming hierarchyTable 2"CCITT Recommendation M.3100 (1992)":managedElementcongestionLevelIndicationhtrDestinationobservedDestinationobservedDestinationHistoryDataobservedDestinationCurrentDataobservedDestinationHistoryDataexchangePerformanceHistoryDataexchangePerformanceCurrentDataexchangePerformanceHistoryData"ITU-T Recommendation M.3100 (1996)":circuitEndPointSubgroupcircuitEndPointSubgroupHistoryDatacircuitEndPointSubgroupCurrentDatacircuitEndPointSubgroupHistoryData"prI-ETS 300 293 (1996)":xtpsgcircuitEndPointSubgroupHistoryDatacircuitEndPointSubgroupCurrentDatacircuitEndPointSubgroupHistoryDatatrafficControltrafficControlHistoryDatatrafficControlCurrentDatatrafficControlHistoryDatadccGroupscrAffectedTrafficsimpleScannerThis table shows the name bindings (containment relationships) of the object classes defined in thisI-ETS. The name bindings of object classes referenced from other documents are defined in thereferenced documents. They are only indicated in this table where necessary.6Information model descriptionThis clause provides a high-level informal description of the Traffic Management information model.Subclause 6.1 contains a brief description for each object class used in the model covering:-the purpose of the object class;-the attributes defined and inherited for the object class; and-the relationship of the object class to other object classes.Attributes which are common to several object classes are described in subclause 6.2.Subclause 6.3 describes actions which are influencing several object classes in the information model.Subclause 6.4 describes the common aspects of the notifications used in the information model.SIST I-ETS 300 637 E1:2003

Page 19I-ETS 300 637: September 19966.1Object class descriptionsThis subclause is divided into subclauses in which the object classes of the information model aredescribed, where they are not described in other documents. In these cases, references are given.In the tables listing the attributes of the object classes, the attributes inherited from super classes (e.g."CCITT Recommendation X.721 (1992)":top or other object classes) are not mentioned explicitly, althoughthey are present in these object classes as defined in CCITT Recommendation X.721 [11] and the othercorresponding deliverables.6.1.1Managed element fragment6.1.1.1Managed element (managedElement)The managed element object class is defined in CCITT Recommendation M.3100 [7].6.1.1.2Congestion level indication (congestionLevelIndication)An instance of the congestion level indication object class provides an indication of the current congestionlevel of the managed element object instance in which it is contained.Although it is desirable, the managed element might not be able to provide an MCL3 indication duringcatastrophic failures.This object class is identical to "ITU-T Recommendation Q.823 (1996)": congestionLevelIndication.Table 3NameM/C/OValue SetcongestionLevelIndicationIdMRDNcongestionLevelMsinglecongestionLevelIndicationIdgives the Relative Distinguished Name (RDN).congestionLevelis an indicator for the present congestion situation in an exchange and anindicator for the degree of traffic management actions to be taken. It isexpressed by the following machine congestion levels (MCL):MCL0: No exchange congestion.The exchange works well, no traffic management action needs to be donewith respect to the machine load;MCL1: Moderate exchange congestion, the exchange keeps working. Somecalls may get rejected if no traffic management action is taken.This is a warning, the exchange may have activated internal traffic controlactions. No additional traffic should be directed to this exchange;MCL2: Serious congestion level, the exchange is no more able to handle alloffered traffic.More severe traffic management actions are to be performed to reduce theexchange load;MCL3: Complete inability of the exchange to process calls.With high probability, the exchange is not able to handle any calls. No furthercalls should be directed to this exchange.6.1.1.3Observed destination (observedDestination)A destination is a country, an area, an exchange or other location, or special service, in which the calledsubscriber is located and that may be specified within the country. A destination is identified by thedestination code. It is defined in annex A
of CCITT Recommendation E.410 [3].SIST I-ETS 300 637 E1:2003

Page 20I-ETS 300 637: September 1996An observed destination is only instantiated for performance monitoring purposes. Its performance ismonitored by a contained tmObservedDestinationCurrentData object instance.Table 4NameM/C/OValue SetobservedDestinationIdMRDNdestinationTypeCsingledestinationCodeMsingletmSurveillanceMsinglecircuitEndPointSubgroupsCsetcreatorIdentityOsingleobservedDestinationIdgives the RDN.destinationTypeindicates either the nature of address of the destination code referred by aninstance of this object class in a seven bit string according to CCITTRecommendation Q.763 [8], or the type of the destination as an enumeratedvalue. If it has NULL value, it is not to be considered.destinationCodeis a country code, or area code, or exchange identifying code, or individualline number etc. which this observedDestination object instance represents.tmSurveillanceidentifies whether the object instance is being monitored for trafficmanagement purposes. If this attribute is set to TRUE, the object instancecontains an instance of the corresponding subclass of current data.circuitEndPointSubgroupspoints to the circuit sub-groups ("ITU-T Recommendation M.3100(1996)":circuitEndPointSubgroup resp. "prI-ETS 300 293 (1996)":xtpsg) onwhich this destination shall be observed.creatorIdentitygives the creator identity (resource or management operation).6.1.1.4Hard to reach destination (htrDestination)A destination is a country, an area, an exchange or other location, or special service, in which the calledsubscriber is located and that may be specified within the country. A destination is identified by thedestination code. It is defined in annex a of CCITT Recommendation E.410 [3].An instance of the htrDestination object class represents a destination identified as Hard To Reach (HTR).All instances of the htrDestination object class are forming the HTR list.The decision whether a destination is hard or easy to reach is made based on the answer to bid ratio oranswer to seizure ratio either by the OS or by the resource management of the exchange. In the lattercase, the administrativeState attribute provides the opportunity to inhibit the HTR status.The HTR status of a destination can be correlated with circuit sub-groups by using thecircuitEndPointSubgroups attribute. If this attribute is empty set, the destination is assigned HTR via allpossible circuit sub-groups.In this I-ETS the mechanisms for the recognition of the HTR status of a destination by the resourcemanagement of the exchange are not modelled, as in a TMN environment due to performance monitoring,all relevant information are present in the OS.A destination for which no htrDes
...