ETSI EN 300 292 V1.2.1 (1998-08)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Telekomunikacijsko upravljavno omrežje (TMN) - Funkcijska specifikacija upravljanja informacije usmerjanja klica na vmesniku obratovalnega sistema/omrežnega elementa (OS/NE)Telecommunications Management Network (TMN); Functional specification of call routeing information management on the Operations System/Network Element (OS/NE) interface33.040.35Telefonska omrežjaTelephone networksICS:Ta slovenski standard je istoveten z:EN 300 292 Version 1.2.1SIST EN 300 292 V1.2.1:2003en01-november-2003SIST EN 300 292 V1.2.1:2003SLOVENSKI
STANDARD
EN 300 292 V1.2.1 (1998-08)European Standard (Telecommunications series)Telecommunications Management Network (TMN);Functional specification ofcall routeing information managementon the Operations System/Network Element (OS/NE) interfaceSIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)2ReferenceREN/TMN-00034 (2pc00ioo.PDF)KeywordsManagement, addressing, networkETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frhttp://www.etsi.frhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)3ContentsIntellectual Property Rights.7Foreword.71Scope.82References.103Definitions and abbreviations.113.1Definitions.113.2Abbreviations.124Functional requirements.125Conformance.146Information model.146.1Information model overview.146.1.1Digit rebuilding fragment.146.1.2Destination selection fragment.156.1.3Routing possibility selection fragment.156.1.4Digit preparation fragment.156.1.5Exception handling fragment.156.2Information model diagrams.157Information model description.217.1analysisCriteria.227.2callHistory.237.3carrierData.247.4cep.257.5cepsg.267.6cepsgComb.287.7cepsgComblist.307.8digitModification.307.9digitPreparationCriteria.317.10digitRebuildingCriteria.327.11exception.337.12localDestination.347.13nationalDestination.357.14postAnalysisEvaluation.367.15prefixDigitAnalysis.377.16routingPossData.387.17routingPossibilities.397.18routingPossRestrict.407.19trafficDistribution.407.20treatment.418OC definitions.428.1Managed OC definitions.428.1.1analysisCriteria.428.1.2callHistory.438.1.3carrierData.448.1.4cep.448.1.5cepsg.458.1.6cepsgComb.468.1.7cepsgCombList.468.1.8digitModification.478.1.9digitPreparationCriteria.478.1.10digitRebuildingCriteria.478.1.11exception.48SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)48.1.12localDestination.488.1.13nationalDestination.498.1.14postAnalysisEvaluation.498.1.15prefixDigitAnalysis.508.1.16routingPossData.518.1.17routingPossibilities.518.1.18routingPossRestrict.528.1.19trafficDistribution.528.1.20treatment.538.2Reused packages definitions.538.2.1callingPartyCategoryPackage.538.2.2destinationTypePackage.538.2.3externalSchedulerPackage.538.3Attributes definitions.548.3.1activeDestination.548.3.3analysisCriteriaId.548.3.4analysisCriteriaInstance.548.3.5analysisOrigin.548.3.6assocSignRouteSetNePart.548.3.7boundaryCrossing.548.3.8calledNumberingPlan.548.3.9callHistoryId.558.3.10callHistoryInstance.558.3.11callingPartyCategory.558.3.12carrierCode.558.3.13carrierCodePresent.558.3.14carrierDataId.558.3.15carrierDataInstance.558.3.16cepId.558.3.17cepsgCombId.558.3.18cepsgCombListId.568.3.19cepsgCombListSelection.568.3.20cepsgCombOrCepsgInstance.568.3.21cepsgCombSelection.568.3.22cic.568.3.23circuitNumber.568.3.24crankbackAdminState.568.3.25ctpbInstance.578.3.26destinationCode.578.3.27destinationGroupLabel.578.3.28destinationType.578.3.29digitCombInsert.578.3.30digitCombReplace.578.3.31digitModificationId.578.3.32digitModificationInstance.588.3.33digitPreparationCriteriaId.588.3.34digitRebuildingCriteriaId.588.3.35digitSuppress.588.3.36echoSuppressor.588.3.37exceptionId.588.3.38excludedSubscriberCodes.588.3.39extSchedulingAttribute.588.3.40initialSubscriberCodes.588.3.41inputCriteriaDataForAlgorithm.588.3.42languageDigit.598.3.43languageDigitProc.598.3.44localDestinationId.598.3.45matchesIf.598.3.46nationalDestinationCode.598.3.47nationalDestinationId.59SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)58.3.48nationalDestinationInstance.598.3.49natureOfAddress.598.3.50numberOfDigits.608.3.51numberOfSatLinks.608.3.52officeEquipment.608.3.53originForAnalysis.608.3.54originForPreparation.608.3.55originForRebuilding.608.3.56originForRouting.608.3.57ownCac.618.3.58postAnalysisEvaluationId.618.3.59prefixCode.618.3.60prefixDigitAnalysisId.618.3.61prefixDigits.618.3.62prefTrafficDirect.618.3.63preparationOrigin.618.3.64preparationTerm.618.3.65rDNId.618.3.66rebuildingOrigin.628.3.67reqBearerCapability.628.3.68reqSignCapability.628.3.69routingOrigin.628.3.70routingPossDataId.628.3.71routingPossibilitiesId.628.3.72routingPossibilitiesSelection.628.3.73routingPossRestrictId.628.3.74schedulingAttribute.628.3.75searchMethod.638.3.76selectedInstances.638.3.77skipGroupSignal1.638.3.78skipGroupSignal2.638.3.79suppressCac.638.3.80suppressOwnCac.638.3.81termForPreparation.648.3.82trafficCategory.648.3.83trafficDistributionData.648.3.84trafficDistributionId.648.3.85trafficDistributionInstance.648.3.86treatmentId.648.3.87treatmentInstance.648.3.88usedAlgorithm.658.4Name bindings.658.4.1analysisCriteria-managedElement.658.4.2callHistory-managedElement.658.4.3carrierData-managedElement.658.4.4cep-cepsg.658.4.5cepsg-managedElement.668.4.6cepsgComb-managedElement.668.4.7cepsgCombList-managedElement.668.4.8digitModification-managedElement.668.4.9digitPreparationCriteria-managedElement.668.4.10digitRebuildingCriteria-managedElement.678.4.11exception-managedElement.678.4.12localDestination-managedElement.678.4.13nationalDestination-managedElement.678.4.14postAnalysisEvaluation-managedElement.678.4.15prefixDigitAnalysis-managedElement.688.4.16routingPossData-managedElement.688.4.17routingPossRestrict-routingPossibilities.688.4.18routingPossibilities-managedElement.68SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)68.4.19trafficDistribution-managedElement.688.4.20treatment-managedElement.698.5ASN.1 type definitions.698.6Cross reference list.72Annex A (informative):OC configuration examples.75A.1Introduction.75A.2Scenario 1.75A.2.1First solution.75A.2.2Second solution.76A.3Scenario 2.77A.3.1First solution.78A.3.2Second solution.80A.3.3Third solution.81A.4Scenario 3.83A.4.1First solution.83A.4.2Second solution.85A.4.3Third solution.87A.4.4Fourth solution.89A.5Scenario 4.90A.5.1Solution.91A.6Scenario 5.92A.6.1First solution.92A.6.2Second solution.94A.6.3Third solution.96A.6.4Fourth solution.97Annex B (informative):Object instance configuration examples.98B.1Introduction.98B.2Example 1: illustrates bearer capability dependent routing.98B.2.1First solution.99B.2.2Second solution.101B.2.3Third solution.103B.3Example 2: illustrates origin dependent routing.104B.3.1First solution.106B.3.2Second solution.107B.4Example 3: illustrates proportional bidding.109B.4.1First solution.110B.5Example 4.111B.5.1First solution.111B.5.2Second solution.112B.6Example 5.113B.6.1First solution.113B.6.2Second solution.115Bibliography.117History.118SIST EN 300 292 V1.2.1:2003

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

ETSIEN 300 292 V1.2.1 (1998-08)81ScopeThe present document provides a management information model [12] which covers the management aspects of the"routing and digit analysis" function in an exchange. The scope is further limited to the exchange aspects of circuitswitched networks. This model is restricted to the Operations Systems (OSs) to Network Element (Q3) interface(see ITU-T Recommendation M.3010 [7]).The information to be managed is limited to the signalling systems Digital Subscriber Signalling System No. 1 (DSS1) ,Signalling System CCITT No.5 (C5), Signalling System Number 7 (SS No.7) - ISDN User Part (ISUP) only) andRegional Signalling 2 (R2). (SS No.7 with Telephone User Part (TUP) level 4 is not considered.) The information forrouting purpose, which needs to be maintained by the manager, depends on the signalling systems used by the exchange.This information model can be applied for exchanges with the known standardized signalling systems DSS 1, SS No. 7,R2, C5. Because of the existence of different signalling systems, not all attributes and objects will be applicable for allexchanges. Information about applicability can be found in the object classes behaviour.As this model only offers an element management layer view (ie: limited to a switch) of the routing information, andonly shows the partial view a switch has of its network environment, and does not show the whole network picture, itdoes not provide all the information needed for network-wide management application.The information model covers the management of following aspects:-incoming digit rebuilding;-locally originating, locally terminating (up to recognizing that the Directory Number (DN) belongs to theexchange), and transit calls;-digit analysis;-circuit end point selection;-outgoing digit preparation;as far as they are relevant for routing. It does not cover management of:-DN portability;-Cordless Terminal Mobility (CTM);-Dynamic Routing;due to lack of stable requirements at the time of writing the present document.The information model includes entry/exit points (via instances of specific Object Class (OC)) for:-customer administration (see ITU-T Recommendation Q.824.x [15] or ETS 300 291 [1]);-Subscriber Controlled Input (SCI) (no standard exists yet);-Intelligent Network (IN) (no standard exists yet);-specific treatments as e.g. announcements.The information model does not cover routing or digit analysis aspects of following topics:-traffic management (see ITU-T Recommendation Q.823 [14] or I-ETS 300 637 [2]);-call-control;-broadband;-supplementary services;-IN (Intelligent Network);-customer administration;SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)9-other services of which the definition is still under study (e.g. tariff management);-Private Automatic Branch Exchange (PABX) as exchanges or as termination points of subscriber lines (becausethis is covered by customer administration);-centrex implementations;-mobility issues like cellular and personnel mobility;neither following specific points:-characterization of non-blockable digits (e.g. emergency numbers);-characterization of destinations for which carrier dialling is not allowed or ignored e.g. service numbers,emergency calls, specific local calls;-numbering plans for virtual private networks;-blocking of national and/or international traffic due to subscriber permission;-echo suppressor handling depending on selected routing possibility;-use of propagation delay counter;-permanent connections.Because the borders between call processing, digit analysis, routing and traffic management are not always clear, thefollowing rules have been used to differentiate between call processing, digit analysis and routing, and trafficmanagement:-digit analysis and routing processes are related to the end point selection. If a managed item has no relation withthe choice of the end point selection, then this managed item is not included in this model;-call control processes are related to whether or when a call is required to be routed. These processes do notinfluence the end point selection;-the border between traffic management and routing is determined by following conditions:-routing management deals with individual calls under normal conditions;-traffic management optimizes overall traffic flow in case of overload or network failure.Modelling described here does not imply any sequencing of call processing activities.SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)102ReferencesThe following documents contain provisions which, through reference in this text, constitute provisions of the presentdocument.· References are either specific (identified by date of publication, edition number, version number, etc.) ornon-specific.· For a specific reference, subsequent revisions do not apply.· For a non-specific reference, subsequent revisions do apply.· A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]I-ETS 300 291 (1995): "Network Aspects (NA) - Functional specification of CustomerAdministration (CA) on the Operations System/Network Element (OS/NE) interface".[2]I-ETS 300 637 (1996): "Network Aspects (NA) - Functional specification of traffic managementon the Network Element/Operation System (NE/OS) interface".[3]EN 301 098 (V1.1): "Telecommunications Management Network (TMN); Scheduling function;Support object classes ".[4]ITU-T Recommendation E.164 (1991): "Telephone Network and ISDN Operation, Numbering,Routing and Mobile Service - Numbering Plan for the ISDN Era".[5]ITU-T Recommendation E.170 (1992): "Traffic Routing".[6]ITU-T Recommendation E.410 (1992): "Telephone Network And ISDN - Quality Of Service,Network Management And Traffic Engineering - International Network Management - GeneralInformation".[7]ITU-T Recommendation M.3010 (1992): "Maintenance: Telecommunications ManagementNetwork - Principles for a Telecommunications Management Network".[8]ITU-T Recommendation M.3100 (1995): "Generic Network Information Model".[9]ITU-T Recommendation Q.115 (1993): "Control of Echo Suppressors and Echo Cancellers".[10]ITU-T Recommendation Q.440 (1988): "(Signalling System R2 - Interregister signalling)General".[11]ITU-T Recommendation Q.441 (1988): " (Signalling System R2 - Interregister signalling)Signalling code".[12]ITU-T Recommendation Q.751.1 (1995): "Signalling System No.7 Managed Objects".[13]ITU-T Recommendation Q.763 (1993): "Specifications of Signalling System No.7 - Formats andCodes of the ISDN User Part of Signalling System No.7".[14]ITU-T Recommendation Q.823 (1996): "Stage 2 and Stage 3 function specifications for trafficmanagement".[15]ITU-T Recommendation Q.824.x (1995): "Stages 2 and 3 description for the Q3 interface -Customer administration - Integrated System Digital Network (ISDN) series".[16]ITU-T Recommendation Q.850 (1993): "Usage of cause and location in the digital subscribersignalling system no 1 and the signalling system no 7 ISDN user part".[17]ITU-T Recommendation Q.931 (1993): "Digital Subscriber Signalling System No. 1 (DSS 1) -ISDN user-network interface layer 3 specification for basic call control".SIST EN 300 292 V1.2.1:2003

ETSIEN 300 292 V1.2.1 (1998-08)11[18]ITU-T Recommendation X.720 (1992): "Information technology - Open Systems Interconnection -Structure of management information: management information model".[19]ITU-T Recommendation X.721 (1992): "Information technology - Open Systems Interconnection -Structure of management information: definiti
...