ETSI TR 101 886-2002 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Requirements Definition Study Real Time Aspects of a Resolution Service (V1 1 1)《.pdf

1、ETSI TR 101 886 1.1.1 (2002-02) Technical Repor Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Req u i remen ts Def i n it ion Stud y; Real time aspects of a resolution service COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling S

2、ervices2 ETSI TR 101 886 VI .I .I (2002-02) Reference DTR/TIPHON-04008 Keywords addressing, ID, IP, network, service ETSI 650 Route des Lucioles F-O6921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association but non lucratif

3、enregistre la Sous-prfecture de Grasse (06) No 7803/88 Important notice Individual copies of the present document can be downloaded from: http:l/w.etsi .orq The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in

4、contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the do

5、cument may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at 3 If you find errors in the present document, send your comment to: Cori vriaht Notifica tion No part may be reproduced except as authorized by written permission

6、. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institute 2001. All rights reserved. ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services3 ETSI TR 101 886 VI . 1 . 1 (2002-02

7、) Contents Intellectual Property Rights 4 Foreword . 4 1 2 3 3.1 3.2 4 4.1 5 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.2.3 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.3.5 5.3.6 5.4 5.4.1 5.4.2 5.4.3 5.4.4 5.4.5 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 History Scope 5 References 5 Definitions and abbreviations . 5 Definitions

8、5 Abbreviations . 6 Overview 7 10 Functional requirements for the ARDB . 11 Service provider management 11 Service provider profile 11 Access control . 11 Access methods 12 Subscriber record 12 Access control . 12 Access methods 12 Number management . 12 Number assignment 12 Number recall . 13 State

9、s of a number 13 Service disconnect 13 13 13 Number portability CO 13 Verification of the 14 Activation of the provisioning request 14 Confirmation of the old service provider 14 Conflict resolution 14 Order cancellation 14 Requirements for the RTDB . 15 Completing the call from home network to term

10、inating network Subscriber record management 12 . General . 15 HNN . 15 Scalability . 15 Availability . 15 Session 16 Performance . 16 Security 16 17 . ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services4 ETSI TR 101 886 VI .I .I (2002-02) Intellec

11、tual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR O00 314: “Intellectual Property Rights

12、(7PRs); Essential, orpotentially Essential, IPRs notlJied to ETSI in respect ofETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (5). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ET

13、SI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Report (TR) has been produced by ETSI Project Telecommunications

14、and Internet Protocol Harmonization Over Networks (TIPHON). TIPHON Resolution Capability (TRC) is a centralized resolution mechanism for inter-service provider call routing in TIPHON compliant networks. Its main function is to map an E. 164 number to a unique service provider name called a Home Netw

15、ork Name (HNN). This HNN can be further resolved into network address(es) of the next-hop service provider network elements by the local resolution capability of the current service provider (which is outside of TRC). In this way, TRC allows call signalling to be routed hop-by-hop, through multiple

16、service provider networks, to the terminating service provider network, where call signalling is routed to the destination terminal identified by the E. 164 number. At the heart of TRC is the database that stores the mapping from an E.164 number to an HNN of a service provider. There are two differe

17、nt parts of the TRC database operations: administrative and real-time. The administrative part deals with the required processes and procedures for administering E. 164 numbers and service provider data, while the real-time part allows the originating service provider to query the database to determ

18、ine the HNN of the home service provider serving the E. 164 number. It should be noted that although the TRC was originally developed to support an international UPT service, the concepts and technology infrastructure are equally applicable to other TIPHON applications, including national variants.

19、The present document has been written to describe a generic resolution framework from which different scenarios can be derived. In some cases, specific features may need to be added to make it suitable for particular applications. NOTE: For certain numbering rangedtypes of service, a centralized res

20、olution mechanism of the type offered by TRC is not a mandatory feature of TIPHON compliant networks. In those network scenarios, routing between originating and terminating networks may be carried out on a hop-by-hop basis, using a resolution function embedded in each of the networks traversed. ETS

21、I COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services5 ETSI TR 101 886 VI .I .I (2002-02) 1 Scope The present document describes the requirements and definitions for the administrative and real-time aspects of the TIPHON Resolution Capability (TRC). TIP

22、HON Resolution Capability (TRC) is a centralized resolution mechanism for inter-service provider call routing in TIPHON compliant networks. In terms of the general framework given in TR 101 326, the TRC is an objective service resolution. Its main function is to map an E. 164 number to a unique serv

23、ice provider name called a Home Network Name (HNN). The administrative part deals with the required processes and procedures for administering E. 164 numbers and service provider data, while the real-time part allows the originating service provider to query the database to determine the HNN of the

24、home service provider serving the E.164 number. It should be noted that although the TRC was originally developed to support an International UPT service, the concepts and technology infrastructure are equally applicable to other TIPHON applications, including national variants. The present document

25、 provides the basis for the Resolution Service capability in TS 101 878. At the same time, the present document can also be used as a stand-alone document. 2 Re fe re nces For the purposes of this Technical Report (TR), the following references apply: il 21 31 ITU-T Recommendation E. 164: “The inter

26、national public telecommunication numbering plan“. ITU-T Recommendation E. 168: “Application of E. 164 numbering plan for UPT“. ITU-T Recommendation Q. 1290: “Glossary of terms used in the definition of intelligent networks“. 41 ETSI TS 101 3 14: “Telecommunications and Internet Protocol Harmonizati

27、on Over Networks (TIPHON); Network architecture and reference configurations; TIPHON Release 2“. ETSI TR 101 326: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); the procedure for determining IP addresses for routeing packets on interconnected IP networks that support

28、 public telephony“. ETSI TS 101 878: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Service Capability Definition; Service Capabilities for a simple call“. 51 61 3 3.1 Definitions and abbreviations De fi nit ions For the purposes of the present document, th

29、e following terms and definitions apply: Administrative Reference DataBase (ARDB): centralized database used for storing the master copy of E. 164 number to HNN mapping that will be periodically downloaded to RTDBs for real-time query NOTE: Service providers can create, update and delete records of

30、E.164 number to HNN mapping in this database. It also contains the participating service provider profiles, which can be created, updated and deleted by the TRC administrators. There is logically exactly one ARDB per TRC. availability: probability that a system can perform the required function at a

31、 given instant of time NOTE: It is estimated by the ratio of actual service time to scheduled service time, and is expressed as percentage, or equivalently, as average downtime per year. database sizing: storage capacity of a database system, usually measured as the number of records with respect to

32、 a specific record size ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services6 ETSI TR 101 886 VI .I .I (2002-02) home network network that supports the service to which a customer subscribes Home Network Name (H“): unique identifierhame for a servic

33、e provider NOTE: An HNN may be further resolved to a routable network address of the service provider by means outside of TRC. home service provider of an E.164 number: service provider that provides the telephony services to the subscriber of the E. 164 number Number Allocation Authority (NAA): nat

34、ional or international organization being responsible for issuing telephone numbers to service providers andor individual subscribers query response time: between the last bit of query entering the database and the last bit of response going out of the database NOTE: In other words, query response t

35、ime only concerns the database query processing time, excluding the transmission delay incurred by the network between the querying entity and the database. Real-Time DataBase (RTDB): database that contains a copy of the E.164 number to service provider HNN mapping from ARDB for real-time query by s

36、ervice providers NOTE: RTDB is read-only by service providers, and its content is updated periodically by ARDB download. There can be more than one RTDB in a TRC, some of which may reside inside a service provider network. resolution domain: group of service providers that agree to provide inter-car

37、rier telephony services over a specific E. 164 numbering rangehype NOTE: There shall be one TRC per resolution domain. throughput: number of queries per second the database which is able to perform with respect to a certain load condition TIPHON Resolution Capability (TRC): mapping function from E.

38、164 numbers to HNNs NOTE: Also refers to the set of network elements, protocols, and procedures necessary to provide such mapping. Universal Personal Telecommunications (UPT): telecommunications service which enables uninterrupted access to telecommunications services while allowing personal mobilit

39、y UPT Number (UPTN): which uniquely and unambiguously identifies each UPT user NOTE: It is used by a calling party to reach the UPT user. This number is independent of terminal, network or service used and shall conform to ITU-T Recommendation E. 168 2. A UPT user may have more than one UPT number (

40、for example, a business UPT number for business calls and a private UPT number for private calls), see ITU-T Recommendation E. 168 2. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AD AD-BES ARDB HNN IP ITU-T NAA PIN PSTN RTDB SCN SCP Administrative Do

41、main Administrative Domain Back-End Service Administrative Reference DataBase Home Network Name Internet Protocol International Telecommunication Union - Telecommunications standardization sector Number Allocation Authority Personal Identification Number Public Switched Telephone Network Real-Time D

42、ataBase Switched Circuit Network Service Control Point ETSI COPYRIGHT European Telecommunications Standards InstituteLicensed by Information Handling Services7 ETSI TR 101 886 VI .I .I (2002-02) SOA Service Order Activation TRC TIPHON Resolution Capability UPT Universal Personal Telecommunications U

43、PTN UPT Number 4 Overview The main purpose of the TIPHON Resolution Capability (TRC) is to provide a global, geographically independent service to telephony users in TIPHON compliant networks. Each user obtains a unique E. 164 number during the provisioning process either from a Number Allocation Au

44、thority (NAA) or via the service provider where he/she fiist subscribes to the service. This globally unique E. 164 number unambiguously identifies the subscriber. TRC enables personal mobility in that numbers are assigned to individuals and not to terminals; and they belong to individuals, not serv

45、ice providers. Hence, subscribers using TRC may change their service providers while keeping their E. 164 numbers. TRC is designed to operate within a resolution domain defined by the following characteristics: there is a group of service providers that agree to interconnect their networks together

46、to provide cross-service provider telephony services to their subscribers. Each service provider constitutes an administrative domain, and is identified by one or more unique names called HNNs; each provider may have multiple networks and these networks may be heterogeneous, such as PSTN, wireless a

47、nd IP networks. But all participating networks shall be TIPHON compliant; there is a specific E. 164 numbering rangehype that the group agrees to use for the intended telephony services. The numbering rangehype is distributed among the service providers (this can be either in blocks of numbers or nu

48、mber by number like in International UPT). At any instant, an active E. 164 number is served by exactly one service provider, called the home service provider of the subscriber. However, the association of an E.164 number and its home service provider cannot be derived directly from the number itsel

49、f without querying the TRC. A TRC is defined with respect to a resolution domain, which in turn is defiied by the group of service providers and the E. 164 numbering rangehype for a specific telephony service. There is exactly one TRC for each resolution domain. In the case where the same group of service providers use different E. 164 numbering rangedtypes for different telephony services, they are considered as different resolution domains, and thus the corresponding TRCs are functionally different even though in some implementations they may be packaged together in one phy