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
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
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
SIST I-ETS 300 637 E1:2003
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: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright 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 cl
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.