ETSI EN 300 292-1998 Telecommunications Management Network (TMN) Functional Specification of Call Routeing Information Management on the Operations System Network Element (OS NE) I.pdf

《ETSI EN 300 292-1998 Telecommunications Management Network (TMN) Functional Specification of Call Routeing Information Management on the Operations System Network Element (OS NE) I.pdf》由会员分享，可在线阅读，更多相关《ETSI EN 300 292-1998 Telecommunications Management Network (TMN) Functional Specification of Call Routeing Information Management on the Operations System Network Element (OS NE) I.pdf（118页珍藏版）》请在麦多课文档分享上搜索。

1、 STD-ETSI EN 300 292-ENGL 1998 3900855 03301b2 487 EN 300 292 VI 2.1 (1998-08) European Standard (Telecommunications series) Telecommunications Management Network (TMN); Functional specification of call routeing information management on the Operations SystemNetwork Element (OWNE) interface COPYRIGH

2、T European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTD-ETSI EN 300 272-ENGL 1998 E 3400855 03301b3 315 2 Reference REN/TMN-00034 (2pcOOioo.PDF) Keywords EN 300 292 V1.2.1 (1998-08) Management, addressing, network ETSI Postal address F-O6921 Sophia Antipolis Ced

3、ex - FRANCE Office address 650 Route des Lucioles - Sophia Antipolis Vaibonne - FRANCE Siret No 348 623 562 00017 - NAF 742 C Association but non lucratii enregistre la Sous-Prfecture de Grasse (06) No 780W88 Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Internet secretariat etzi.fr http:/www.e tsi

4、.fr http:/www.etsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 1998, All rights reserved. E TSI COPYRIGHT European T

5、elecommunications Standards InstituteLicensed by Information Handling ServicesSTD-ETSI EN 300 272-ENGL L77 D lLiOO855 0330Lb4 251 D 3 EN 300 292 Vi .2.1 (1 998-08) Contents Intellectual Property Rights ,. 7 Foreword .,.,.,.,.,.7 1 2 3 3.1 3.2 4 5 6 6.1 6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.2 7 7.1 7.2 7.3

6、 7.4 7.5 7.6 7.7 7.8 7.9 7.10 7.1 1 7.12 7.13 7.14 7.15 7.16 7.17 7.18 7.19 7.20 8 8.1 8.1.1 8.1.2 8.1.3 8.1.4 8.1.5 8.1.6 8.1.7 8.1.8 8.1.9 8.1.10 8.1.11 Scope 8 References i0 Definitions and abbreviations i 1 Definitions , . . . , . ., , 1 1 Abbreviations. . 12 Functional requirements . 12 Conform

7、ance 14 Information model . . 14 Infomation model overview 14 Digit rebuilding fragment . . 14 Destination selection fragment . 15 Routing possibility selection fragment . Digit preparation fragment 15 Exception handling fragme . 15 Information model diagrams . . . . . . . . . . . . . . . . . . . .

8、. . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . , , . , . . , . , . , , . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . Information model description ._ . . . . _ . . . . ., . 2 1 analy siscriteria . . . . . . . . . . . . . . . . . 22 calll

9、listory . . 23 .,.I 24 . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . 25 cep . . . 31 localDes tination . . . , , . . . ._ , . . . . . . . . postAnalysisEvaluation . 34 . . 37 39 routingPossRestrict . . 40 irafficDistribution _. treatment . . _ . . . . . . . . . . . .

10、. , , , . . , . . . . OC definitions . 42 . 42 . Managed OC definitions . . . . . . . . . . . . . analvsislriteria . ._ . . . . . . 43 44 M with N an integer (O) and M an integer (1 ). Other cases are expiicitely specified. - OR means that any or all branches can be present; XOR means that exactly o

11、ne branch can be present. mean that the class or relation .,. fragment. i-i L-,J N I y) I COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services16 1-1 EN 300 292 Vi .2.1 (1 998-08) Criteria oints to ? Modification Figure 2 (E-R Diagram): Digit rebuilding f

12、ragment carrierData national Destination - dailyOperationScheduler I weeklperationSdieduier I monthlperationScheduler I from ITU-T Rec.X.746 17 L-J I 1 I 1 Scheduler fromEN 301 09816 I - - - - - - - - - - - - Digitnnaiysis A”: l oints t O,M 11 I I XOR N M I XOR OR I I I traffic postAnalysis Distribu

13、tion Evaluation treatment -I I l e.g. I I other areas: IN,SCI. . I -i * : M-cardinality because of Time scheduling; WithoulTime scheduling: M=l Figure 3 (E-R Diagram): Destination selection fragment ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Servic

14、es STD*ETSI EN 300 272-ENGL 1978 3400855 0330178 84b 17 EN 300 292 V1.2.1 (1 998-08) Destination CepsgCombList roups + o, 1 *“ . Comb . I digitModification M : M cardinality because of Time scheduling Without Time scheduling: M=l . - - - - _ - - - - - - dailperationScheduler weeklperationScheduler m

15、onthlperationSaieduler irom ITU-T Rec.X.746 i71 _ Figure 4 (E-R Diagram): Routing possibility selection fragment ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTD-ETSI EN 300 292-ENGL 1998 = 3400855 0330379 782 m 18 EN 300 292 V1.2.1 (1 998-08

16、) analysisCriteria f- I digitPreparation Criteria , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ,. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ! routingPossData j postAnalycisEvaluation : I ., oints t e digit U Modification oints to e Modification Modifica

17、tion Figure 5 (E-R Diagram): Digit preparation fragment. I treatment Figure 6 (E-R Diagram): Exception handling fragment ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTDSETSI EN 300 292-ENGL 3798 3400855 0330380 4T4 19 managed digitRebuilding

18、 Criteria excepon Destinatio nalionalDeslinalion I postAnalysis Evaluation prefixDigrt Analysis r routingPossData IrafficDisbibution -w Contains Figure 7: Naming relations EN 300 292 V1.2.1 (1 998-08) COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services2

19、0 EN 300 292 V1.2.1 (1 998-08) mU-T Rec.X.721 13: bP TU-T Rec.M.3100 5: circuitEndPointSubgroup callHistory carrierData cepsgcomb cepsgcom bList digit I digitPreparation exception routingPossibilities Destination nationalDestination postAnalysis Evaluation traificDistribution Figure 8: Inheritance t

20、ree E TSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTDeETSI EN 300 272-ENGL 1998 3400855 0330181 330 21 EN 300 292 V1.2.1 (1 998-08) 7 Information model description In this clause the OCs of the information model are described. For OCs descrip

21、tion the following table is used. Table 1: OCS generic description The column M/C indicates whether the information presented by the attributes/actions/notifications is mandatory(M) or conditionai( C) . The column “Value Set“ indicates whether the attribute is single-valued or set-valued (see 1TU-T

22、Recommendation X.720 lS, subclause 5.1.2.2). The column “Operation“ indicates the operations possible on the attribute. Combination of key-attributes value shail be unique among all instances of a given OC. An asterisque * following an attribute name indicates a key attribute. Important notice: The

23、conflict resolution that shall occur when several instances of a given OC match a specific call is out of the scope of the present document. ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services7.1 22 EN 300 292 V1.2.1 (1 998-08) a na lys isC rit e r

24、i a The OC analysiscriteria describes the management information needed to make a selection among possible destinations. For certain calls, e.g. service numbers and originating calls of virtual private networks, it is possible that initial digits need to be modified before the destination can be ide

25、ntified. The destination associated with this new digit string can then be determined by another instance of OC analysislriteria. Table 2: AnalysisCriteria description IobjectManagemen tNotifications Package The following attributes describe the OC analysislnteria: - analysiscriteriald; This attribu

26、te is the object identifier attribute (Relative Distinguished Name (RDN) of OC analysiscriteria. - des tina tionlode; This attribute characterizes a destination by specifying the Country Code (CC), or/and area code, orland exchange identifying code, orland individual line number etc. to which the ca

27、ll can be routed. - analysisorigin; This attribute identifies the originForAnalysis group value.originForAnalysis can be defined in e.g. incoming or two-ways cepsg or in subscriber data as described in Customer Administration Model. An instance of the OC analysiscriteria being independent of the ana

28、lysis origin gets the value anyorigin. - activeDestination; This attribute either references an object instance or selects a group of instances via a label. If scheduling is supported, then this attribute contains the target, which is currently selected by the Scheduler Object (SO). This attribute i

29、s read only in case of a scheduler being connected, otherwise read/write. - callingPartyCategory; COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling ServicesSTDeETSI EN 300 292-ENGL 1998 3900855 0330183 103 createDeleteNotificationsPackag4 attributeValueChangeN

30、otificationPackage “ITU-T Recommendation M.31 O0 8“: 23 EN 300 292 V1.2.1 (1998-08) C This attribute identifies the calling party category (according 1TU-T Recommendation 4.763 1131 or ITU-T Recommendation Q.440 lo, ITU-T Recommendation 4.441 li) which have to be considered for routing purposes. Cal

31、ling party categories include operator, test or normal subscriber call. - nationalDesunationinstance: This attribute identifies the instance of OC nationalDestination which is applicable if the destinationcode value has to be assigned unambiguously to a national destination. - destinationType; This

32、attribute indicates the type of destination - extSchedulingA ttribute; This attribute provides the scheduling information in the Scheduled Managed Object (SMO), if external scheduling is supported as in EN 301 098 131. - externalSchedulerName: This attribute is used in the SMO for referencing the ex

33、ternal SOS. (see ITU-T Recommendation X.746 1201) - numberOfDigits; This attribute indicates the number of digits in the digit string. The existence of multiple analysiscriteria instances with different values for this attribute allows the administration of variable length digit strings that shall b

34、e routed to the same destination. It also allows the specification of a destination that depends not only on the leading digits as indicated in the attribute destinationCode, but also on the length of the digit string. In this way digit strings with identical leading digits, but with different lengt

35、hs can be routed to different destinations. When a specific number of digits is specified, this number cannot be smaller than the number of digits in the digit string as specified in the destinationcode attribute. - camerDataInstance. This atlribute allows the selection of destinations depending on

36、the dialled or assigned carrier code of the call. 7.2 call H istory This OC describes criteria and/or restrictions related to the history of a call, e.g. the number of satellite links. It can be used, for example, to restrict the propagation delay. Table 3: callHistory description CallHistoryld Sing

37、le IGET echoSuppressor I c I- Sinsle IGE-REPLACE I ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services24 EN 300 292 V1.2.1 (1 998-08) The following attributes describe the OC cailiistory: - callHistoryld; This attribute is the object identifier ami

38、bute (RDN) of OC callHistory. echo S uppre s sor; This attribute reflects whether an echo suppressor is required or not depending on whether an echo suppressor has already been included. If an echo suppressor is required, then cepsgs of suitable capability need to be identified, if the exchange does

39、 not provide the use of echo control devices inserted from a common pool (see ITU-T Recommendation Q.115 SI). - - numbeIOfSatLinks. This attribute represents the number of satellite links in the history of the call. The number of hops allowed for a certain caii can be limited. In general, the limita

40、tion values for telephony are zero or one, for data no limitations are present. 7.3 carrierData This OC represents -via the carrier code- carriers that can be used in the exchange for call routing purposes. Table 4: carrierData description carrierDatald Single JGET carriercode“ Sinale I GET ndation

41、M.31 O0 Ia: M IobjectManagemen tNotificationsPackacje The following attributes describe the OC carrierData: - canierDataId; This attribute is the object identifier attribute (RDN) of OC carrierData. - carrierCode; This attribute describes the unambiguous carrier specific code that identifies a carri

42、er. It can be dialled by a subscriber or supplied by the exchange. - ownCac. This attribute describes whether the Carrier Access Code (CAC) identifies the network where the exchange is located. ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services- S

43、TD*ETSI EN 300 272-ENGL 3778 W 3400855 0330385 TBb cepld “ITU-T Recommendation X.721 191“: administrativeState ctpblnstance circuitNumber officeEquipment 25 EN 300 292 V1.2.1 (1 998-08) M Single GET M Single GET-REPLACE M Single GET M Single GET C Single GET SET-BY-CREATE SET-BY-C REATE 7.4 cep This

44、 OC describes a circuit end point. One cep belongs only to one set of circuit end points, the cepsg (circuit end point subgroup). Table 5: cep description - I SET-BY-CREATE cic ICI Sinaie IGET createDeleteNotificationsPackage I I I “ITU-T Recommendation X.721 I 91“: statechange MI The following attr

45、ibutes describe the OC cep: - cepld; This attribute is the object identifier attribute (RDN) of OC cep - administrativestate; This attribute indicates whether the circuit end point subgroup is administratively permitted to carry traffic (value unlocked) or not (value locked). - ctpblnstance; This at

46、tribute points to an instance of OC “ITU-T Recommendation M.3 100 SI: connectionTerminationPointBidirectiona1 which has the channebiumber attribute. - circuiiNumber; This attribute indicates the logical circuit end point number within the containing circuit end point subgroup. - officeEquipment; Thi

47、s attribute references the physical equipment the circuit end point is associated with. If the inst choice is used, it references an instance of OC “ITU-T Recommendation M.3100 8“: circuiffack. If the string choice is used, the value is technology specific. - cic. This attribute indicates the Circui

48、t Identification Code (CIC) of the circuit which is terminated by the circuit end point. This attribute is applicable if SS No. 7 is used. ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services7.5 transmissionCharacteristics “ITU-T Recommendation M.31

49、00 8“: IabelOfFarEndExchange administrativeState “ITU-T Recommendation X.721 19“: acsocSignRouteSetNePart boundarvcrocsina 26 M Single REPLACE M Single G ET-R E P LAC E M Single REPLACE-WITH-DEFAULT M Single REPLACE-WITH-DEFAULT GET-REPLACE EN 300 292 V1.2.1 (1 998-08) This OC represents a circuit end point subgroup. An instance of cepsg has directionality one-way incoming, one-way outgoing or two-way. This