ITU-T Q 826-2000 Routing Management Model Series Q Switching and Signalling Q3 Interface《路由管理模型-系列Q 交换和信令-Q3接口(第4研究组)》.pdf

《ITU-T Q 826-2000 Routing Management Model Series Q Switching and Signalling Q3 Interface《路由管理模型-系列Q 交换和信令-Q3接口(第4研究组)》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 826-2000 Routing Management Model Series Q Switching and Signalling Q3 Interface《路由管理模型-系列Q 交换和信令-Q3接口(第4研究组)》.pdf（148页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNIONITU-T Q.826TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(02/2000)SERIES Q: SWITCHING AND SIGNALLINGQ3 interfaceRouting management modelITU-T Recommendation Q.826(Formerly CCITT Recommendation)ITU-T Q-SERIES RECOMMENDATIONSSWITCHING AND SIGNALLINGSIGNALLING IN THE

2、 INTERNATIONAL MANUAL SERVICE Q.1Q.3INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 Q.120Q.249SPECIFICATIONS OF SIGNA

3、LLING SYSTEM No. 6 Q.250Q.309SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499DIGITAL EXCHANGES Q.500Q.599INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799General Q.700Message transfer part (MTP) Q.701Q.

4、709Signalling connection control part (SCCP) Q.711Q.719Telephone user part (TUP) Q.720Q.729ISDN supplementary services Q.730Q.739Data user part Q.740Q.749Signalling System No. 7 management Q.750Q.759ISDN user part Q.760Q.769Transaction capabilities application part Q.770Q.779Test specification Q.780

5、Q.799Q3 INTERFACE Q.800Q.849DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999PUBLIC LAND MOBILE NETWORK Q.1000Q.1099INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199INTELLIGENT NETWORK Q.1200Q.1699SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799BROADBAND ISDN Q.2000Q.2999For

6、 further details, please refer to the list of ITU-T Recommendations.ITU-T Q.826 (02/2000) iITU-T Recommendation Q.826Routing management modelSummaryThis Recommendation provides a management information model which covers the managementaspects of the “routing and digit analysis“ function in an exchan

7、ge. The scope is further limited to theexchange aspects of circuit switched networks. This model is restricted to the Operations Systems toNetwork Element (Q3) interface.SourceITU-T Recommendation Q.826 was prepared by ITU-T Study Group 4 (1997-2000) and approvedunder the WTSC Resolution 1 procedure

8、 on 4 February 2000.ii ITU-T Q.826 (02/2000)FOREWORDThe International Telecommunication Union (ITU) is the United Nations specialized agency in the field oftelecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ ofITU. ITU-T is responsible for studying techn

9、ical, operating and tariff questions and issuing Recommendationson them with a view to standardizing telecommunications on a worldwide basis.The World Telecommunication Standardization Conference (WTSC), which meets every four years,establishes the topics for study by the ITU-T study groups which, i

10、n turn, produce Recommendations on thesetopics.The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1.In some areas of information technology which fall within ITU-Ts purview, the necessary standards areprepared on a collaborative basis with ISO and IEC.NOTE

11、In this Recommendation, the expression “Administration“ is used for conciseness to indicate both atelecommunication administration and a recognized operating agency.INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation mayinvolv

12、e the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence,validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or othersoutside of the Recommendation development process.As of the date of approval of this Recommend

13、ation, ITU had not received notice of intellectual property,protected by patents, which may be required to implement this Recommendation. However, implementors arecautioned that this may not represent the latest information and are therefore strongly urged to consult theTSB patent database. ITU 2001

14、All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means,electronic or mechanical, including photocopying and microfilm, without permission in writing from ITU.ITU-T Q.826 (02/2000) iiiCONTENTSPage1 Scope 12 Normative references 23 Definitions and ab

15、breviations. 33.1 Definitions 33.2 Abbreviations . 44 Functional requirements . 55 Information model 75.1 Information model overview 75.1.1 Digit rebuilding fragment 75.1.2 Carrier selection fragment. 85.1.3 Destination selection fragment 85.1.4 Routing possibility selection fragment 85.1.5 Digit pr

16、eparation fragment 85.1.6 Exception handling fragment 85.2 Information model diagrams 86 Information model description . 146.1 analysisCriteria . 156.2 callHistory 176.3 carrierData 186.4 carrierList . 196.5 carrierSelectionCriteria. 196.6 cep. 206.7 cepsg. 226.8 cepsgComb . 256.9 cepsgCombList . 27

17、6.10 digitModification 286.11 digitPreparationCriteria 296.12 digitRebuildingCriteria. 306.13 exception. 316.14 exceptionCurrentData. 316.15 exceptionHistoryData . 326.16 localDestination 326.17 nationalDestination. 336.18 postAnalysisEvaluation 34iv ITU-T Q.826 (02/2000)Page6.19 prefixDigitAnalysis

18、 356.20 routingPossData 366.21 routingPossibilities . 376.22 routingPossRestrict. 386.23 trafficDistribution . 396.24 treatment . 407 Object class definitions. 417.1 Managed object class definitions 417.1.1 analysisCriteria 417.1.2 callHistory . 437.1.3 carrierData. 437.1.4 carrierList 447.1.5 carri

19、erSelectionCriteria . 447.1.6 cep . 457.1.7 cepsg 457.1.8 cepsgComb 477.1.9 cepsgCombList 487.1.10 digitModification. 487.1.11 DigitPreparationCriteria 487.1.12 DigitRebuildingCriteria. 497.1.13 exception . 497.1.14 exceptionCurrentData 507.1.15 exceptionHistoryData 507.1.16 localDestination. 507.1.

20、17 nationalDestination 517.1.18 postAnalysisEvaluation. 527.1.19 prefixDigitAnalysis . 537.1.20 routingPossData 547.1.21 routingPossibilities 557.1.22 routingPossRestrict 557.1.23 trafficDistribution 567.1.24 treatment 577.2 Reused packages definitions. 587.2.1 callingPartyCategoryPackage 587.2.2 de

21、stinationTypePackage 587.2.3 digitModificationInstancePackage 587.2.4 externalSchedulerPackage. 587.3 Attributes definitions 587.3.1 activeDestination. 58ITU-T Q.826 (02/2000) vPage7.3.2 activeRoutingPossibilities . 597.3.3 analysisCriteriaId 597.3.4 analysisCriteriaInstance 597.3.5 analysisOrigin 5

22、97.3.6 assocSignRouteSetNePart . 597.3.7 boundaryCrossing 597.3.8 calledNumberingPlan 607.3.9 callHistoryId 607.3.10 callHistoryInstance 607.3.11 callingPartyCategory. 607.3.12 carrierCode 607.3.13 carrierCodePresent 607.3.14 carrierDataId 607.3.15 carrierDataInstance 607.3.16 carrierListId. 617.3.1

23、7 carrierSelectionCriteriaId 617.3.18 carrierSelectionOrigin . 617.3.19 carrierType 617.3.20 cepId 617.3.21 cepsgCombId. 617.3.22 cepsgCombListId 617.3.23 cepsgCombListSelection. 627.3.24 cepsgCombOrCepsgInstance 627.3.25 cepsgCombSelection . 627.3.26 cic 627.3.27 circuitNumber 627.3.28 crankbackAdm

24、inState . 637.3.29 ctpbInstance. 637.3.30 destinationCode. 637.3.31 destinationGroupLabel 637.3.32 destinationType . 637.3.33 digitCombInsert. 647.3.34 digitCombReplace. 647.3.35 digitModificationId . 647.3.36 digitModificationInstance . 647.3.37 digitPreparationCriteriaId 647.3.38 digitRebuildingCr

25、iteriaId 647.3.39 digitSuppress . 647.3.40 echoSuppressor 647.3.41 exceptionId 64vi ITU-T Q.826 (02/2000)Page7.3.42 exceptionCount 657.3.43 excludedSubscriberCodes . 657.3.44 extSchedulingAttribute 657.3.45 ignoredDialledCarriers 657.3.46 ignoredPreselectedCarriers 657.3.47 interceptedDialledCarrier

26、s 657.3.48 interceptedPreselectedCarriers 657.3.49 initialSubscriberCodes 667.3.50 inputCriteriaDataForAlgorithm. 667.3.51 languageDigit 667.3.52 languageDigitProc. 667.3.53 listOfCarriers. 667.3.54 localDestinationId . 667.3.55 matchesIf . 677.3.56 nationalDestinationCode . 677.3.57 nationalDestina

27、tionId 677.3.58 nationalDestinationInstance 677.3.59 natureOfAddress 677.3.60 numberOfDigits. 677.3.61 numberOfSatLinks 677.3.62 officeEquipment 677.3.63 originForAnalysis 687.3.64 originForPreparation . 687.3.65 originForRebuilding 687.3.66 originForRouting. 687.3.67 ownCac 687.3.68 possibilitiesIn

28、List 697.3.69 postAnalysisEvaluationId 697.3.70 prefixCode. 697.3.71 prefixDigitAnalysisId 697.3.72 prefixDigits 697.3.73 prefTrafficDirect . 697.3.74 preparationOrigin 697.3.75 preparationTerm 707.3.76 rDNId 707.3.77 rebuildingOrigin 707.3.78 reqBearerCapability. 707.3.79 reqSignCapability 707.3.80

29、 routingOrigin. 707.3.81 routingPossDataId . 70ITU-T Q.826 (02/2000) viiPage7.3.82 routingPossibilitiesId. 707.3.83 routingPossibilitiesSelection . 707.3.84 routingPossRestrictId 717.3.85 schedulingAttribute . 717.3.86 searchMethod 717.3.87 selectedCarrierType 717.3.88 selectedInstances . 717.3.89 s

30、kipGroupSignal1 727.3.90 skipGroupSignal2 727.3.91 suppressCac. 727.3.92 suppressOwnCac . 727.3.93 termForPreparation 727.3.94 trafficCategory. 737.3.95 trafficDistributionData 737.3.96 trafficDistributionId 737.3.97 trafficDistributionInstance. 737.3.98 treatmentId 737.3.99 treatmentInstance 737.3.

31、100 usedAlgorithm. 747.4 Namebindings. 747.4.1 analysisCriteria-managedElement. 747.4.2 callHistory-managedElement 747.4.3 carrierData-managedElement 757.4.4 carrierList-managedElement . 757.4.5 carrierSelectionCriteria-managedElement 757.4.6 cep-cepsg. 757.4.7 cepsg-managedElement-DelCep . 767.4.8

32、cepsg-managedElement-NoDelCep 767.4.9 cepsgComb-managedElement. 767.4.10 cepsgCombList-managedElement. 777.4.11 digitModification-managedElement 777.4.12 digitPreparationCriteria-managedElement 777.4.13 digitRebuildingCriteria-managedElement 777.4.14 exception-managedElement 787.4.15 exceptionCurren

33、tData-exception. 787.4.16 localDestination-managedElement 787.4.17 nationalDestination-managedElement 787.4.18 postAnalysisEvaluation-managedElement 797.4.19 prefixDigitAnalysis-managedElement 797.4.20 routingPossData-managedElement . 79viii ITU-T Q.826 (02/2000)Page7.4.21 routingPossRestrict-routin

34、gPossibilities . 807.4.22 routingPossibilities-managedElement. 807.4.23 trafficDistribution-managedElement. 807.4.24 treatment-managedElement. 807.5 ASN.1 type definitions . 817.5.1 Rules of extensibility. 817.5.2 ASN.1 type definition module 818 Action service. 859 Functional units 869.1 Functional

35、 units from other Recommendations . 879.2 Negotiation of functional units. 8710 Relationship with other Recommendations 8711 Conformance 8811.1 Static conformance . 8811.2 Dynamic conformance 89Appendix I Object class configuration examples. 89I.1 Introduction 89I.2 Scenario 1 .90I.2.1 First solutio

36、n 90I.2.2 Second solution . 90I.3 Scenario 2 .92I.3.1 First solution 92I.3.2 Second solution . 95I.3.3 Third solution 97I.4 Scenario 3 .99I.4.1 First solution 99I.4.2 Second solution . 101I.4.3 Third solution 103I.4.4 Fourth solution 105I.5 Scenario 4 . 107I.5.1 Solution . 107I.6 Scenario 5 . 108I.6

37、.1 First solution 109I.6.2 Second solution . 111I.6.3 Third solution 112I.6.4 Fourth solution 114ITU-T Q.826 (02/2000) ixPageAppendix II Object instance configuration examples 115II.1 Introduction 115II.2 Example 1: illustrates bearer capability dependent routing 115PageII.2.1 First solution 117II.2

38、.2 Second solution . 118II.2.3 Third solution 120II.3 Example 2: illustrates origin dependent routing. 121II.3.1 First solution 123II.3.2 Second solution . 124II.4 Example 3: illustrates proportional bidding . 126II.4.1 First solution 127II.5 Example 4. 128II.5.1 First solution 128II.5.2 Second solu

39、tion . 129II.6 Example 5. 130II.6.1 First solution 130II.6.2 Second solution . 132ITU-T Q.826 (02/2000) 1ITU-T Recommendation Q.826Routing management model1ScopeThis Recommendation provides a management information model ITU-T X.720 11 which coversthe management aspects of the “routing and digit ana

40、lysis“ function in an exchange. The scope isfurther limited to the exchange aspects of circuit switched networks. This model is restricted to theOperations Systems to Network Element (Q3) interface (see ITU-T M.3010 1).The information to be managed is limited to the signalling systems DSS1 (Digital

41、SubscriberSignalling System No. 1), C5 (Signalling System CCITT No. 5), SS No. 7 (Signalling SystemNo. 7 ISUP (ISDN User Part) only) and R2 (Regional Signalling 2). (SS No. 7 with TUP(Telephone User Part) level 4 is not considered.) The information for routing purposes, which needsto be maintained b

42、y the manager, depends on the signalling systems used by the exchange. Thisinformation model can be applied for exchanges with the known standardized signalling systemsDSS1, SS No. 7, R2, C5. Because of the existence of different signalling systems, not all attributesand objects will be applicable f

43、or all exchanges. Information about applicability can be found in theobject classes behaviour.As this model only offers an element management layer view (i.e. limited to a switch) of the routinginformation, and only shows the partial view a switch has of its network environment, and does notshow the

44、 whole network picture, it does not provide all the information needed for network-widemanagement application.The information model covers the management of following aspects: incoming digit rebuilding; locally originating, locally terminating (up to recognizing that the DN (Directory Number)belongs

45、 to the exchange), 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 (this is covered in ITU-T Q.18xx); CTM (Cordless Terminal Mobility);due to lack of stable requirement

46、s at the time of writing this Recommendation.The information model includes entry/exit points (via instances of specific OC) for: customer administration (see ITU-T Q.824.x 13); subscriber controlled input (no standard exists yet);IN (Intelligent Network) (see Q.18xx); specific treatments as, e.g. a

47、nnouncements.The information model does not cover routing or digit analysis aspects of the following topics: traffic management (see ITU-T Q.823 16); call-control; broadband; supplementary services;2 ITU-T Q.826 (02/2000) IN (Intelligent Network); customer administration; other services of which the

48、 definition is still under study (e.g. tariff management); PABX (Private Automatic Branch Exchange) as exchanges or as termination points ofsubscriber lines (because this is covered by customer administration); centrex implementations; mobility issues like cellular and personnel mobility;neither the

49、 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.However, the model defined by this Re