SIST-TP TR 101 886 V1.1.1:2004
(Main)Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Requirements Definition Study; Real time aspects of a resolution service
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); Requirements Definition Study; Real time aspects of a resolution service
To outline the real-time service to be provided by a Resolution Service that provides contact IDs from E.164 numbers (This outline would then be converted into a fromal service capability description by WG1)
Harmonizacija telekomunikacij in internetnega protokola prek omrežij (TIPHON) - Študija definicije zahtev - Realnočasovni vidiki resolucijskih storitev
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST-TP TR 101 886 V1.1.1:2004
01-april-2004
+DUPRQL]DFLMDWHOHNRPXQLNDFLMLQLQWHUQHWQHJDSURWRNRODSUHNRPUHåLM 7,3+21
âWXGLMDGHILQLFLMH]DKWHY5HDOQRþDVRYQLYLGLNLUHVROXFLMVNLKVWRULWHY
Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON);
Requirements Definition Study; Real time aspects of a resolution service
Ta slovenski standard je istoveten z: TR 101 886 Version 1.1.1
ICS:
33.020 Telekomunikacije na splošno Telecommunications in
general
SIST-TP TR 101 886 V1.1.1:2004 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
---------------------- Page: 2 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
ETSI TR 101 886 V1.1.1 (2002-02)
Technical Report
Telecommunications and Internet Protocol
Harmonization Over Networks (TIPHON);
Requirements Definition Study;
Real time aspects of a resolution service
---------------------- Page: 3 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
2 ETSI TR 101 886 V1.1.1 (2002-02)
Reference
DTR/TIPHON-04008
Keywords
addressing, ID, IP, network, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
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 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 document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
editor@etsi.fr
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.
© European Telecommunications Standards Institute 2001.
All rights reserved.
ETSI
---------------------- Page: 4 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
3 ETSI TR 101 886 V1.1.1 (2002-02)
Contents
Intellectual Property Rights.4
Foreword.4
1 Scope.5
2 References.5
3 Definitions and abbreviations.5
3.1 Definitions.5
3.2 Abbreviations.6
4 Overview.7
4.1 Completing the call from home network to terminating network.10
5 Functional requirements for the ARDB .11
5.1 Service provider management.11
5.1.1 Service provider profile .11
5.1.2 Access control.11
5.1.3 Access methods.12
5.2 Subscriber record management .12
5.2.1 Subscriber record.12
5.2.2 Access control.12
5.2.3 Access methods.12
5.3 Number management.12
5.3.1 Number assignment.12
5.3.2 Number recall.13
5.3.3 States of a number .13
5.3.4 Service disconnect.13
5.3.5 Problem solving.13
5.3.6 Subscriber support.13
5.4 Number portability considerations .13
5.4.1 Verification of the provisioning request .14
5.4.2 Activation of the provisioning request.14
5.4.3 Confirmation of the old service provider.14
5.4.4 Conflict resolution.14
5.4.5 Order cancellation.14
6 Requirements for the RTDB.15
6.1 General.15
6.2 HNN.15
6.3 Scalability.15
6.4 Availability.15
6.5 Session.16
6.6 Performance.16
6.7 Security.16
History .17
ETSI
---------------------- Page: 5 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
4 ETSI TR 101 886 V1.1.1 (2002-02)
Intellectual 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 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (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 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 Network 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 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 different 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 determine 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. 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 ranges/types of service, a centralized resolution 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.
ETSI
---------------------- Page: 6 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
5 ETSI TR 101 886 V1.1.1 (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).
TIPHON 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 service 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 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 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 References
For the purposes of this Technical Report (TR), the following references apply:
[1] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".
[2] ITU-T Recommendation E.168: "Application of E.164 numbering plan for UPT".
[3] ITU-T Recommendation Q.1290: "Glossary of terms used in the definition of intelligent
networks".
[4] ETSI TS 101 314: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON); Network architecture and reference configurations; TIPHON Release 2".
[5] 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 public telephony".
[6] ETSI TS 101 878: "Telecommunications and Internet Protocol Harmonization Over Networks
(TIPHON) Release 3; Service Capability Definition; Service Capabilities for a simple call".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the 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 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 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 a
specific record size
ETSI
---------------------- Page: 7 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
6 ETSI TR 101 886 V1.1.1 (2002-02)
home network: network that supports the service to which a customer subscribes
Home Network Name (HNN): unique identifier/name for a service 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): national or international organization being responsible for issuing telephone
numbers to service providers and/or 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 time 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 service 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-carrier telephony services over a specific
E.164 numbering range/type
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.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 mobility
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 (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 Administrative Domain
AD-BES Administrative Domain Back-End Service
ARDB Administrative Reference DataBase
HNN Home Network Name
IP Internet Protocol
ITU-T International Telecommunication Union - Telecommunications standardization sector
NAA Number Allocation Authority
PIN Personal Identification Number
PSTN Public Switched Telephone Network
RTDB Real-Time DataBase
SCN Switched Circuit Network
SCP Service Control Point
ETSI
---------------------- Page: 8 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
7 ETSI TR 101 886 V1.1.1 (2002-02)
SOA Service Order Activation
TRC TIPHON Resolution Capability
UPT Universal Personal Telecommunications
UPTN 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 Authority (NAA) or via the service provider where he/she first
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
service 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 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 and
IP networks. But all participating networks shall be TIPHON compliant;
• there is a specific E.164 numbering range/type that the group agrees to use for the intended telephony services. The
numbering range/type is distributed among the service providers (this can be either in blocks of numbers or number
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 itself without querying the TRC.
A TRC is defined with respect to a resolution domain, which in turn is defined by the group of service providers and the
E.164 numbering range/type 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 ranges/types 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 physical network element.
Unless otherwise stated explicitly, the present document only concerns requirements of TRC with respect to a single
resolution domain. Requirements for services involving multiple TRCs are out of scope of the present document, but
may be a subject for further study.
An example of a resolution domain is depicted by figure 1. For a given resolution domain, TRC serves as a centralized
number resolution clearinghouse among all service providers for inter-domain call routing. Its main function is to map
an E.164 number to the HNN of the home service provider of that number. However, since an HNN includes the
identifier for a service provider, for call routing purposes another resolution function (routing resolution) may be needed
to map the HNN to the network addresses of the service provider network. This is accomplished by the Administrative
Domain-Back End System (AD-BES) of a service provider, which is outside the scope of TRC.
ETSI
---------------------- Page: 9 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
8 ETSI TR 101 886 V1.1.1 (2002-02)
TRC
AD-BES
AD-BES
Service Provider C
Service Provider A
AD-BES
Service Provider B
Resolution Domain
Figure 1: Resolution domain and TIPHON Resolution Capability (TRC)
Inter-provider call routing within a resolution domain follows the hop-by-hop paradigm using the two-level resolution
hierarchy. The top-level resolution, called service resolution, is accomplished by querying the TRC, which returns the
HNN of the home service provider of the called E.164 number. This is normally done once by the originating service
provider since the HNN is passed along by the call signalling messages.
Note: Service resolution may occur at the originating network or the originating network can route the call to a network
where service resolution takes place.
Once the home network has been identified by the objective service resolution, a second-level of resolution called
routing resolution, which is subjective, takes place. This resolution may be repeated hop-by-hop by intermediate service
provider (including the originating service provider) until the home network is reached. The home network signals to
the terminating network. For the final stage of routing when call signalling finally reaches the terminating service
provider network, the terminating service provider will resolve the called E.164 number to the destination terminal
network address and route the call signalling to that terminal accordingly.
As is shown in figure 2, TRC is functionally divided into two parts: the administrative part and the real-time part. The
administrative part is used to store and update the information about the association between subscribers E.164 numbers
and the service providers while the real-time part is responsible for identifying the home service provider of the called
user during the call setup process.
NAA SOA SOA
Provisioning Interface
ARDB
T
Download Interface
R
C
Clearing
Service
RTDB RTDB
Houses
Providers
Real-time Query Interface
AD-BES AD-BES AD-BES
Figure 2: Functional separation of TRC: real-time and administrative aspects
ETSI
Real-time Aspects
Administrative Aspects
---------------------- Page: 10 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
9 ETSI TR 101 886 V1.1.1 (2002-02)
The administrative part consists of a (logically) single Administrative Reference DataBase (ARDB), which contains the
participating service provider profiles and the mapping for each active E.164 number to the HNN of its home service
provider. A service provider performs number administration using its Service Order Activation (SOA) system, through
the TRC provisioning interface, to create, update and delete records in ARDB for the subscribers E.164 numbers within
its administrative domain. Each service provider should be only able to access and update E.164 number mapping
information for its own subscribers in ARDB.
Note that all E.164 to HNN mapping records shall first be created and stored in the ARDB. Subsequent update and/or
deletion of these records shall also be done through ARDB. However, during call setup, a service provider's AD-BES
normally does not query the ARDB directly. Instead, it queries a TRC Real-Time DataBase (RTDB), which contains a
copy of the mapping records of ARDB, through the real-time query interface of TRC. There can be (physically) more
than one RTDB for a TRC, some of which may belong to competitive service providers such as resolution
clearinghouses, while others may reside in participating service providers' networks. Changes made to ARDB, through
the provisioning interface, are propagated to the RTDBs, through the download interface, by periodic database
download from the ARDB to the RTDBs.
Note that the one-to-many arrangement between ARDB and RTDBs in TRC is aimed at improving query performance
and service availability of the TRC. Logically, there should be exactly one ARDB for each TRC, though ARDB may be
physically replicated to improve reliability and availability. On the other hand, the separation of ARDB and RTDB is a
functional one. It is possible that ARDB and a RTDB may co-locate in the same physical network element, while other
RTDBs reside in different physical network elements.
Hence a service provider has two ways to access TRC. One way is to use its own SOA to do number administration via
the TRC provisioning interface. The other way is to use its AD-BES to request for E.164 number to HNN translation
during call setup via the TRC real-time query interface. The requirements of administrative aspects of TRC apply to
ARDB, the provisioning interface, and the download interface. The requirements of real-time aspects of TRC apply to
RTDB and the real-time query interface. An example, specific to VISIONng, for International UPT is shown below in
figure 3.
Number Allocation
Authority
Legend:
TRC . TIPHON Resolution Capability ITU
TSB (see note)
UPTN
RTDB . Real Time DataBase
Registrar
ARDB . Administrative Reference Database
SOA . Service Order Activation
Outsourcing the UPT number space
RT-I . Real Time Interface
A1 878 (10) to VISIONng
TRC
Provisioning
Interface
Home
Service Provider
UPT
A2
VISIONng
SOA
ARDB
Phase 1
UPT
implementation
Download
Sub-
Provisioning
A3 Interface
scriber
RTDB
RT-I
A4
Real-Time
Query Interface
VISIONng Members
NOTE: The ITU-TSB is responsible for the allocation and assignment of international number resources that are
under the purview of the ITU-T.
Figure 3: TRC functional components and interfaces in
the context of subscribers and service providers
ETSI
---------------------- Page: 11 ----------------------
SIST-TP TR 101 886 V1.1.1:2004
10 ETSI TR 101 886 V1.1.1 (2002-02)
A subscriber can obtain an E.164 number from a service provider. However, the detailed number issuing process,
though very important in its own right, is out of the scope of the present document. Hence, those interfaces are marked
as a dotted line. The provisioning interface consists of the A2 interface with service providers' SOAs. The real-time
interface consists of the A4 interface. The requirements on real-time aspects of TRC are concerned with the real-time
query interface A4.
It should be noted that TRC is independent of the underlying network technologies. Hence the external interfaces A2
and A4 shall be made accessible to network elements from various network types within a service provider domain,
including SCN, wireless, ATM, and IP networks.
4.1 Completing the call from home network to terminating
network
The following describes how the call is completed. These steps are not part of TRC.
Once the home network has been identified by the objective service resolution, a second-level of resolution, called
routing resolution, which is subjective takes place. This resolution may be repeated hop-by-hop by intermediate service
providers (including the originating service provider) until the home network is reached. The home network signals to
the terminating network. For the final stage of routing when call signalling finally reaches the terminating service
provider network, the terminating service provider will resolve the called E.164 number to the destination terminal
network address and route the call signalling to that terminal accordingly.
Two scenarios are depicted below, corresponding to whether
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.