Top Banner
www.tekelec.com An overview of number portability, including design issues, cost recovery and solutions, for ANSI- and ITU-based fixed and mobile operators. WHITE PAPER Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks.
24
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Operator Guidelines for Number Portability

www.tekelec.com

An overview of number portability, including design issues, cost

recovery and solutions, for ANSI- and ITU-based fixed and

mobile operators.

WHITE PAPER

Operator Guidelines for Number PortabilityChallenges and Solutions for ITU- & ANSI-based Networks.

Page 2: Operator Guidelines for Number Portability

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITyOPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

This document is for informational purposes only, and Tekelec reserves the right to change any aspect of the products, features or functionality described in this document without notice. Please contact Tekelec for additional information and updates. Solutions and examples are provided for illustration only. Actual implementation of these solutions may vary based on individual needs and circumstances.

© 2010 Tekelec. All rights reserved. The EAGlE and Tekelec logos are registered trademarks of Tekelec. All other trademarks are the property of their respective owners. TKlC-WP-002.2-NA-01-2010

Tekelec Global Headquarters +1.919.460.5500 [email protected]

EMEA +44.1784.437000 APAC +65.6796.2288 CALA +1.919.460.5500

Tekelec has more than 25 offices worldwide serving customers in more than 100 countries. Addresses, phone and fax numbers are listed on the Tekelec website at www.tekelec.com/offices.

Page 3: Operator Guidelines for Number Portability

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Table of ContentsIntroduction ................................................................................................4

Industry drivers for Number Portability ........................................................4

Implementing Number Portability ................................................................5

Architecture Considerations ........................................................................9

Tekelec Solutions for Number Portability ......................................................12

About Tekelec .............................................................................................17

Appendix 1: Acronyms Used in This document ...........................................18

Appendix 2: Number Portability Charging fees ............................................20

Appendix 3: Tekelec Number Portability deployments by

Country and Technology .............................................................................23

Page 4: Operator Guidelines for Number Portability

4

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

IntroductionNumber portability (NP) allows customers to keep their telephone numbers when they

change physical locations, service providers or types of service. Number portability

provides a great customer benefit. for residential customers, the phone number is a

direct link to family and friends, as well as to critical services such as those provided

by doctors and schools. business customers advertise their telephone numbers on

letterheads, advertising and promotional materials; the number becomes their primary

source of contact. by retaining their phone numbers after relocation, service provider

or service type change, residential and business customers experience no disruption of

services or the inconvenience and cost of having to notify others of their new number.

Government regulators usually mandate the rules and criteria for implementing NP (this

may include network interconnection, conveyance charges between operators, etc.), but

operators independently can decide the best method to implement NP in their networks.

The purposes of this paper are to:

• Provide an overview of number portability, to include:

– Industry drivers for number portability

– Implementing number portability

– Portability types

– Key network elements in a number portability domain

– Routing methods

– Costs and recovery

• discuss architectural considerations and implications related to number portability

• Address potential solutions for implementing number portability in American National Standards Institute (ANSI) and International Telecommunications Union (ITU) networks

for more technical details relating to various Tekelec number portability solutions

addressed herein, please visit Tekelec’s web site at www.tekelec.com, or contact your

Tekelec sales representative.

Industry Drivers for Number PortabilityNumber portability is a network capability that allows subscribers to keep their telephone number when they change: (1) Service provider, (2) Service types, and/or (3) location. Traditionally, the following arguments have been used to support a government mandate for number portability:

• Increased Competition: Ability of subscribers to keep their telephone number increases likelihood that they will switch operators, resulting in increased competition for subscribers.

Page 5: Operator Guidelines for Number Portability

5

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

• Lower Consumer Costs: Increased competition will lower costs for subscribers.

• Increased Sales of New/Additional Phone Services: lower costs result in sales of phone services to individuals who didn’t previously subscribe, and will prompt the sale of additional, high-end telephony services to existing subscribers.

Implementing Number PortabilitySince early adopters first implemented number portability in the mid 1990s, deployments

have increased dramatically. The time line below gives a general picture of worldwide

NP deployment.

1996 1997 1998 1999 2000 2001 2002 2003

UKFrance

GermanyUS

CanadaSwedenAustralia Denmark TaiwanTaiwan

Hong KongUK

HollandIceland

FranceUS

FinlandIrelandGreece

SpainItaly

Switzerland

SwedenAustraliaDenmarkNorway

GermanyBelgiumPortugal

Fixed-Line NP Deployments

Mobile NP Deployments

Mobile NP Deployments

Fixed-Line NP Deployments

2004 2009 2010-2014

PeruColumbiaEcuadorBahrain

IndiaThailandTurkey

ChileRussia

South KoreaSlovakiaLithuaniaIcelandHungryCyprusAustria

BrazilTurkeyMexico

MalaysiaDominican

Rep.

AlbaniaArgentinaBahrainChina

EcuadorIndia

BelarusChile

ColumbiaCoasta RicaGuatemala

PanamaPeru

RussiaThailandUkraine

VenezuelaYugoslavia

AlgeriaBangladesh

GhanaIndonesia

IraqKazakhstan

KenyaMoroccoNigeria

PhilippinesTanzaniaTunisia

UAEVietnam

TaiwanMalta

LuxembourgLatvia

EstoniaCroatia

IsraelSaudi-Arabia

South AfricaPolandOmanJapan

Czech Rep.

New-ZealandEgypt

SingaporeRomaniaPakistanCanadaBulgaria

20072005 2006 2008

SloveniaGreece Hong Kong Singapore BrazilMexico

Figure 1. Worldwide Fixed-Line and Mobile NP Deployment Schedule

Page 6: Operator Guidelines for Number Portability

6

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Portability Types:There are three types of number portability:

• Service Provider Portability: The most commonly deployed number portability type, service provider portability enables end users to retain their telephone numbers when changing service providers.

• Location Portability: location portability is the ability of end users to retain their telephone numbers when moving from one location to another (e.g., between areas serviced by different central offices). In this instance, a telephone number could be associated with a device, independent of location. It would allow customers to keep their numbers when they move to locations outside of the original rate center. Until very recently, no requirements have been designated or mandated for location portability in the USA. (Note: In August 2005, the federal Communication Commission (fCC) mandated a 90-day waiver for location number portability to help victims displaced by Hurricane Katrina in mississippi, Alabama and louisiana.)

• Service Portability: This is the ability of end users to retain the same telephone number as they change from one service to another. The new service can be offered by a new operator or can be within the same operator network. for example, a subscriber shifts subscription to a VoIP service provider, or from a code division multiple access (CdmA) or time division multiple access (TdmA) network to a global system for mobile communications (GSm) network or vice versa.

Key Network Elements in a Number Portability Domain:listed below and shown in figure are several key network elements in a number portability domain:

• NP Server: maintains the number portability database (NPdb) and provides routing instructions. An example solution would be Tekelec’s EAGlE® 5 platform.

• donor Network: Network from where the number originally came.

• Originating/Initiating Network: Network from where the call originated.

• Subscription Network: Network in which the subscriber is presently being served.

• Recipient Network: Network to where a number is ported.

• Transit Network: Network between two networks (where signaling is transported prior to arriving at the recipient network).

Page 7: Operator Guidelines for Number Portability

7

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Routing Methods:

for fixed-line networks, four different routing methods are defined: (1) all call query, (2)

Onward routing, (3) dropback, and (4) Query on release. for mobile networks, there

are two different routing methods: direct and indirect, which are described below and

depicted in figure 3 and figure 4 respectively.

• direct routing (all call query) – the originating network has the responsibility to:

– determine whether the called party is a ported number; and,

– Route the call to its subscription network.

• Indirect routing (onward routing) – the donor network has the responsibility to:

– determine whether the called party is a ported number; and,

– Route the call to its subscription network.

OriginatingNetwork

TransitNetwork

Called Subscriber

DonorNetwork

SubscriptionNetwork

CalledSubscriber

NP Server can bean STP or SCP

CallingSubscriber

Figure 2. Key Elements in a Number Portability Domain

Figure 3. Direct Routing Example for GSM Ported Directory Number

IncomingCall

SRI_ACK

SRI

NPDB

1

3

4

2

IAM

3

IAM

Switch

RecipientNetwork

OriginatingNetwork

TransitNetwork

CallingSubscriber

CalledSubscriber

Page 8: Operator Guidelines for Number Portability

8

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Call flow:

1. Originating Network receives an incoming call

2. Originating Network passes the call to donor Network

3. donor Network queries NP Server for routing instructions

4. donor receives routing instructions from NP Server

5. donor routes the call to an mSC in the Subscription Network

6. Switch performs normal call setup

Costs and Recovery:

Cost recovery has been critical to operators and regulators as they contemplate rolling

out number portability. There are a variety of costs incurred to prepare networks for

NP implementation.

Call flow:

1. Originating Network receives an incoming call

2. Originating Network queries NP Server for routing instructions

3. NP Server returns routing instructions to Originating Network

4. Originating Network routes the call to Subscription Network (directly or via Transit Network)

5. Switch performs normal call setup

Figure 4. Indirect Routing Example for GSM Ported Directory Number

IncomingCall

SRI_ACK

SRI NPDB

1

3

4

2 5

IAM

IAM

Switch

RecipientNetwork

NP Server

OriginatingNetwork

TransitNetwork

DonorNetwork

CallingSubscriber

CalledSubscriber

Cost recovery has been critical

to operators and regulators as

they contemplate rolling out

number portability.

Page 9: Operator Guidelines for Number Portability

9

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

• Establishment costs: Systems costs and per-operator costs (operator interfaces).

• Usage costs: Per-line administration costs (porting), additional call conveyance costs, auditing costs, costs related to handling customer problems.

• maintenance costs: Additional staffing for maintaining systems and technology.

Governments and regulators determine how service providers can recover costs associated with implementing number portability. The following are four NP cost recovery models that have been adopted or are being recommended.

• Operators assess a small monthly fee to all of their subscribers (e.g., lNP in the USA).

• Operators (can be the donor and/or recipient operators) charge the subscriber who ports (e.g., European Union Countries).

• Operators charge both a one-time porting application fee and a monthly service fee.

• A fund owned and controlled by the regulatory agency or its assignee is created. Each operator contributes to the fund based upon its number of subscribers. Withdrawals are based on actual costs.

In the USA, the fCC determined that existing local telephone companies were allowed to recover these costs over a period of five years through two kinds of charges: (1) Charges paid by other telephone companies that use a telephone company’s NP, and (2) A small fixed monthly charge assessed on telephone customers or end users. Appendix 2 lists the different NP fee charges regulated (permitted) by various countries around the world.

Critical Implementation Steps:In countries where NP has recently been mandated or is being considered, carriers can take advantage of the experiences of others. The following steps are critical to successfully implementing NP:

• define What Type of Number Portability Will be Supported

• Select the Network Architectures for Signaling and Administration

• Examine Costs and Cost-Recovery methods

• Select Vendors with Available Solutions

• Establish the deployment Schedule

• deploy NP for larger markets first, followed by Smaller markets

Architecture ConsiderationsHistorically, all numbering plans have assumed a fixed relationship between a customer’s

number, an operator and/or physical switch location. In the NP environment, the

operator and physical switch locations are decoupled from the customer’s number,

becoming a virtual number. Implementing NP requires carriers to retool their network

architecture and rethink the role of the intelligent network.

NP requires carriers to retool

their network architecture

and rethink the role of the

intelligent network.

Page 10: Operator Guidelines for Number Portability

10

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Operators face many challenges in finding the right NP solution for their network

and need to carefully consider the requirements for each. Implementing NP causes an

enormous increase in traffic loads and changes in traffic mixes to signal transfer points

(STPs) and/or service control points (SCPs). Critical points of consideration include:

• Using a centralized NP database (prevalent in North America and most other countries) versus a distributed NP database.

• determining what type of routing methods should be used.

• Considering the network scalability for capacity and performance.

• determining if all the originating offices are IN-equipped.

• Administering the customer care system as an integral part of the NP implementation. The customer care system needs to be modified due to the new type of service change requests.

• Network planning to handle the increase in signaling traffic related to number portability.

• Impact of NP on short message service (SmS), multimedia message service (mmS) and pre-paid services.

• determining whether to perform NP through an integrated STP/NP node (such as the Tekelec EAGlE 5 platform) – as shown in 5.

Figure 5. Integrated STP/NP Solution

Signaling andNetwork Intelligence Layer

ServiceManagement

SMS

IntelligentNetwork Layer

SMSC

Base Station BSC MSC MSC

Subscriber

Subscriber

NP Server NP Server

VMSCVMSC

OtherNetworks

NPDBNPDB

Page 11: Operator Guidelines for Number Portability

11

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Table 1 shows the many advantages of going with an integrated STP/NP solution versus

the SCP approach.

Table 1. Benefits of an Integrated STP/NP Approach Compared to the SCP NP Approach

Integrated STP/NP Approach

SCP NP Approach

Footprint Integrated STP, NP db and Signaling Relay function (SRf)

multi-platform deployment requiring additional point codes (PCs)

Performance High transaction rates, real-time memory db access ~ 75,000 transactions per second (TPS) per system

low transaction rates, typically non-real time disk access ~ 4,000 transactions per second (TPS) per system

Scalability Simple growth – additional cards hot-plugged into existing frame/system

Growth may require new nodes

Data Management Centralized data maintenance

Related data is maintained in multiple network entities

Reliability Higher reliability – avoids potential network failures due to external network connections

lower reliability – due to external network connections

Throughput Superior throughput Throughput of an SCP is limited by 32-link combined linkset constraint

Cost lower cost – reduced number of links required

Higher cost – related to deployment of SCP nodes and the associated transmission facilities

Page 12: Operator Guidelines for Number Portability

12

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

ITU-based Number Portability Solutions:

mobile Number Portability

There are two approaches to mobile number portability (mNP): signaling relay function

(SRf) - a triggerless solution, and intelligent network (IN) triggering - a triggered

solution. The triggered approach requires the switch to be equipped with IN triggering

capabilities. The triggerless method intercepts the GSm/IS41 call delivery messages that

are already flowing in the network, so that the switches need not be equipped with IN

capabilities. The triggered solution can be used in either fixed or mobile environments.

fixed Number Portability

A triggered solution is commonly used in North America to support fixed number

portability. In ITU (non-North American) markets, an ISUP-based triggerless solution is

used to support fixed number portability. The ITU-T Q. series specifies the functional

requirements for supporting number portability, applicable to mobile and fixed networks.

Tekelec Solutions for Number PortabilityTekelec has extensive experience and expertise in deploying number portability solutions for fixed and mobile operators – with more than 94 deployments worldwide (see Appendix 3 for Tekelec’s NP deployments). Tekelec solves the number portability problem for voice, short message service (SmS), multimedia message service (mmS) and prepaid calls. Tekelec’s NP solutions for voice include:

• SRF-based Mobile Number Portability (MNP): Triggerless solution applicable to GSm operators to support fixed-line NP and mobile NP.

• ANSI-41 Mobile Number Portability: Triggerless solution applicable to CdmA and TdmA operators to support fixed-line NP and mobile NP.

• INAP-based Number Portability: Triggered solution applicable to GSm and ITU-based fixed-line operators to support fixed-line NP and mobile NP.

• ANSI-41 Number Portability (AINPQ): Triggered solution applicable to TdmA and CdmA operators to support fixed-line NP and mobile NP.

• Triggerless ISUP-based Number Portability (TINP): Triggerless solution applicable to wireline operators to support fixed-line NP and mobile NP.

• IS-41 to GSM Migration: Triggerless solution supports portability when an operator migrates its TdmA/CdmA-based network to a GSm based network and vice versa.

• Local Number Portability (LNP): Triggered solution applicable to North American (excluding mexico) fixed-line and mobile (GSm, TdmA and CdmA) operators to support fixed-line and mobile NP.

Page 13: Operator Guidelines for Number Portability

13

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

SRF-based Mobile Number Portability:

The Tekelec SRf-based mNP solution implements mobile number portability for GSm

networks according to 3GPP TS 03.66.

for call-related messages, SRf-based mNP will act as an “NP home location register

(HlR)” when the number has been ported out – by responding to the switch with a

mobile application part (mAP) SRI_ACK message. for calls to ported-in numbers and

non-call related messages (such as short messages), SRf-based mNP performs message

relay. The SRf-based mNP solution specifies two routing options: direct and indirect

routing. With direct routing, the network from where the call originates is responsible for

determining whether the called party number has been ported, and then routing the call

to the new subscription network. With indirect routing, this is the responsibility of the

network that originally owned the number. The SRf-based mNP solution supports both

direct and indirect routing.

Triggerless MNP for ANSI-41 Network:

The Tekelec triggerless mNP solution supports number portability in an ANSI-41

environment (supporting TdmA or CdmA networks). This is a triggerless solution, similar

to the SRf-based mNP solution deployed in GSm networks.

The Tekelec EAGlE 5 platform intercepts the ANSI-41 loc_Req message (initiated by a

TdmA/CdmA mSC querying HlR concerning the terminating subscriber’s subscription

information). The EAGlE 5 platform performs an NP database (NPdb) lookup to

determine the portability status of the dialed number. It then returns the routing number

(RN) that indicates the current subscription network of the terminating subscriber – in a

loc Req return result (RR) message if the subscriber is identified as ported out, foreign

subscriber ported to a foreign network, or a non-ported other licensed operator (OlO)

subscriber. The EAGlE 5 platform relays the loc_Req message to its intended HlR if the

subscriber is a non-ported or imported subscriber. for non-call related messages (such as

short messages), the EAGlE 5 platform relays the message to its intended destination.

Triggered-based NP Solution:

The Tekelec triggered-based NP solution can be deployed in fixed or mobile networks if

the fixed network end offices or mobile switching centers (mSCs) are equipped with

IN capabilities.

The solution is a trigger-based application. An IN equipped EO/mSC can detect if a call

requires special routing instructions. When the triggering conditions are detected, the

EO/mSC suspends call processing and sends a query to a real-time NP database system,

Page 14: Operator Guidelines for Number Portability

14

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

such as the EAGlE 5 platform, requesting routing instructions. A trigger can be detected

based on a block of dialed numbers or on an individually dialed number.

In the ITU signaling environment, the EO/mSC commonly uses the INAP message

to query routing instructions from the real-time database system that hosts the NP

database. four different routing methods are defined to support a trigger-based NP

solution. The Tekelec triggered-based NP solution supports all four routing methods.

ANSI-41 INP Query (AINPQ):

With this solution, a TdmA/CdmA mSC detects calls that require NP triggering and

sends the EAGlE 5 platform an ANSI-41 NPREQ message. The EAGlE 5 platform

performs NP database look-ups based on the dialed digit encoded in NPREQ and

responds to the mSC with the NP status of the CdPN. If the CdPN has been ported, the

EAGlE 5 platform returns routing instructions to the mSC.

Triggerless ISUP-based NP (TINP):

The ITU triggerless NP feature identifies the subscription network of the called party

by examining the called party number (CdPN) of a received IAm message. Carriers

can use the additional RN/Sub-network Id information to apply different charge rates

(for instance, prepaid calls) or route/segregate traffic based on the sub-network Id

pre-pended to the CdPN. The ITU triggerless NP solution provides the recipient switch

portability status of the CdPN without the recipient switch having to perform additional

NP queries.

IS-41 to GSM Migration:

The Tekelec IS-41 to GSm migration solution enables an operator with a hybrid network

or who plans to migrate from one technology to another (e.g., from TdmA/CdmA

to GSm or from GSm to CdmA/TdmA) to allow its subscribers to retain their phone

numbers while migrating within its network. The IS-41 to GSm migration solution allows

operators to seamlessly migrate their networks without tedious protocol conversion

(when transporting signaling messages between these two different types

of networks is required to complete call setup). Number Portability for SmS, mmS &

Prepaid Calls.

listed below are Tekelec’s NP solutions for SmS, mmS and prepaid calls include:

• mO-SmS-GSm: Triggerless solution applicable to GSm operators to support SmS NP based on mO_fWd_SmS message.

• mO-SmS-IS41: Triggerless solution applicable to IS41 operators to support SmS NP based on SmdPP message.

Page 15: Operator Guidelines for Number Portability

15

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

• mT-SmS-GSm: Triggerless solution applicable to GSm operators to support SmS NP based on SRI_Sm message.

• mT-SmS-IS41: Triggerless solution applicable to TdmA/CdmA operators to support SmS NP based on SmSREQ message.

• mT-mmS-GSm: Triggered solution applicable to wireless operators to support mmS NP based on SRI_Sm as NP query message.

• mT-mmS-IS41: Triggered solution applicable to wireless operators to support mmS NP based on SmSREQ as NP query message.

• GSm mmS using INAP: Triggered solution applicable to wireless operators to support mmS NP based on IdP as NP query message.

• ANSI mmS using INAP: Triggered solution applicable to wireless operators to support mmS NP based on NPREQ as NP query message.

• IdPR: Triggerless solution applicable to GSm operators to support Prepaid NP based on IdP message.

• AINPQ: Triggered solution applicable to TdmA/CdmA operators to support Prepaid NP based on NPREQ as NP query message.

Page 16: Operator Guidelines for Number Portability

16

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Table 2 lists Tekelec’s broad portfolio of ITU- and ANSI-based NP solutions covering voice,

SmS, mmS and prepaid calls.

Table 2. Tekelec’s Number Portability Solutions for Mobile and Fixed-Line Networks

NP Solutions

Data Type

Type Operator Type

Protcol MessageName(s)

SRF-based MNP

Voice Triggerless GSm GSm mAP SRI

Triggerless MNP for ANSI-41 Network

Voice Triggerless TdmA/CdmA

IS41 lOCREQ

TINP Voice Triggerless Wireline ISUP IAm

Triggered-based NP Solution

Voice Triggered Wireline INAP IdP

GSm INAP/CAmEl

IdP

AINPQ Voice Triggered TdmA/CdmA

IS41 NPREQ

MO-SMS GSM

SmS Triggerless GSm GSm mAP mO_SmS

MO-SMS-IS41

SmS Triggerless TdmA/CdmA

IS41 SmdPP

MT-SMS GSM

SmS Triggerless GSm GSm mAP SRI_Sm

MT-SMS IS41

SmS Triggerless TdmA/CdmA

IS41 SmSREQ

MT-MMS-GSM

mmS Triggerless GSm GSm mAP SRI_Sm

MT-MMS-IS41

mmS Triggerless TdmA/CdmA

IS41 SmSREQ

GSM MMS using INAP

mmS Triggered GSm INAP/CAmEl

IdP

ANSI MMS using IS41

mmS Triggered TdmA/CdmA

IS41 NPREQ

IDPR Pre-paid Triggerless GSm INAP/CAmEl

IdP

AINPQ Pre-paid Triggered TdmA/CdmA

IS41 NPREQ

Page 17: Operator Guidelines for Number Portability

17

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

NP Solutions

Data Type

Type Operator Type

Protcol MessageName(s)

SRF-based MNP

Voice Triggerless GSm GSm mAP SRI

Triggerless MNP for ANSI-41 Network

Voice Triggerless TdmA/CdmA

IS41 lOCREQ

TINP Voice Triggerless Wireline ISUP IAm

Triggered-based NP Solution

Voice Triggered Wireline INAP IdP

GSm INAP/CAmEl

IdP

AINPQ Voice Triggered TdmA/CdmA

IS41 NPREQ

MO-SMS GSM

SmS Triggerless GSm GSm mAP mO_SmS

MO-SMS-IS41

SmS Triggerless TdmA/CdmA

IS41 SmdPP

MT-SMS GSM

SmS Triggerless GSm GSm mAP SRI_Sm

MT-SMS IS41

SmS Triggerless TdmA/CdmA

IS41 SmSREQ

MT-MMS-GSM

mmS Triggerless GSm GSm mAP SRI_Sm

MT-MMS-IS41

mmS Triggerless TdmA/CdmA

IS41 SmSREQ

GSM MMS using INAP

mmS Triggered GSm INAP/CAmEl

IdP

ANSI MMS using IS41

mmS Triggered TdmA/CdmA

IS41 NPREQ

IDPR Pre-paid Triggerless GSm INAP/CAmEl

IdP

AINPQ Pre-paid Triggered TdmA/CdmA

IS41 NPREQ

Number Portability Provisioning Flow:

figure 6 shows the provisioning flow for Tekelec’s NP solutions. The advantage of this

provisioning model is that data is auto-synchronized between all integrated STP/NP

nodes – providing fully replicated data and a redundant system – critical for ensuring

high reliability in operator deployments.

About TekelecTekelec enables billions of people and devices to talk, text and access the Web. Our

portfolio delivers a unique layer of intelligence allowing service providers to both manage

and monetize the exponential growth in data traffic and applications. Tekelec has more

than 25 offices around the world serving customers in more than 100 countries. for

more information, please visit www.tekelec.com.

Prim

ary

Writ

eW

rite

50 T

PSs

Prim

ary

Rea

dR

ead

100

TPSs

Stan

dby

Writ

e &

Rea

d

2 x EPAPServers per

EAGLE Node

Redundant EPAPProvisioning

System

Auto-Synch DB

EAGLE 5 Platform

EPAP-B EPAP-B

Provisioning System

SM 1 SM 24 SM 0

EPAP-A

IS41-GSM MigrA-PortG-FlexG-Port

INPTIFNP

EIRGTT

Auto-Synch DB

EAGLE 5 Platform

SM 1 SM 0

EPAP-A

SM 24

IS41-GSM MigrA-PortG-FlexG-Port

INPTIFNP

EIRGTT

Figure 6. Full NPDB Replicated in Each SM Card and in Each EPAP Server

Page 18: Operator Guidelines for Number Portability

18

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Appendix 1: Acronyms Used in This Document ANSI American National Standards Institute

AINPQ ANSI-41 INP Query

ATm Asynchronous Transfer mode

CAmEl Customized Applications for mobile Enhanced logic

CAPEX Capital Expense

CdmA Code division multiple Access

CdPN Called Party Number

dN directory Number

EO End Office

EPAP EAGlE Provisioning Application Processor

ETSI European Telecommunications Standards Institute

fCC federal Communication Commission

GSm Global System for mobile Communications

GTT Global Title Translation

HlR Home location Register

IAm Initial Address message

ImSI International mobile Station Identifier

IN Intelligent Network

INAP Intelligent Network Application Protocol or Part

INP INAP-based Number Portability

IS-41 Interim Standard 41

ISdN Integrated Services digital Network

ITU International Telecommunications Union

lNP local Number Portability

mAP mobile Application Part

mmS multimedia message Service

mNP mobile Number Portability

Page 19: Operator Guidelines for Number Portability

19

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

mSISdN mobile Station International ISdN Number

NP Number Portability

NPdb Number Portability database

OPEX Operating Expense

POTS Plain Old Telephone Service

RN Routing Number

SCP Service Control Point

SIm Subscriber Identity module

SmPP Short message Peer-to-Peer Protocol

Sm Service module

SRf Signaling Relay function

STP Signal Transfer Point

TdmA Time division multiple Access

TINP Triggerless ISUP-based NP

UmTS Universal mobile Telecommunications System

USA United States of America

Page 20: Operator Guidelines for Number Portability

20

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Appendix 2: Number Portability Charging Fees

Country Permission of Charging Fees?

Regulation of Maximum Fee?

Fee Basis

Austria yES max. •19 Recipient network charges •4-15.

Belgium yES – Only recipient network is allowed to charge fees.

max. •15 Only pre-paid but not post-paid customers are charged for porting mobile subscribers.

Cost oriented

Denmark yES – Customers pay typically the fee that operators charge to their competitors.

NO Operators committed to charge •9.60 per ported number to customers. The donor operator charges the same amount to the new operator.

Cost oriented

Germany yES A unique fee based on the costs caused by porting numbers.

O2 charges •22.50 and T-mobile, Vodafone and E-Plus charge •24.95 to their customers. Some small service providers charge •29.95.

Cost oriented

Finland yES – Only recipient network is allowed to charge fees.

NO The donor network charges about •5-10 to the recipient operator. No fees for customers.

Cost oriented

Greece yES – – –

Hong Kong

yES max. HK$10 Up to the recipient operator whether or not to charge the porting customers for porting.

Cost oriented

Page 21: Operator Guidelines for Number Portability

21

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Ireland yES – Charges shall not be a disincentive for users to port their number.

Charges shall not be a disincentive for user to port their number.

No fees for customers.

Cost oriented

Italy yES – Only recipient network is allowed to charge fees.

max. •10.02 The donor operator charges •10.02 to the recipient operator. No fees for customers.

Netherlands yES – Only recipient network is allowed to charge fees. Charge shall not exceed administrative costs.

max. •9 The recipient operator is allowed to charge the customer •9. Charges consist of administrative fees.

Norway yES – Only recipient network is allowed to charge fees.

NO – Charge between networks should cover costs of donor network.

Portugal yES NO – –

Sweden yES – Only donor network is allowed to charge fees.

NO (to customer), yES (donor to recipient)

Only donor operators charge •4-24 fees to the recipient operator.

Cost oriented (administrative and porting costs).

Switzerland yES NO – –

Spain yES Charges shall not be a disincentive for users to port their number.

No fees. –

UK yES “adequate fees”

Typically no fees. Some operators charge £25.

marginal costs

Page 22: Operator Guidelines for Number Portability

22

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

US (Mobile)

yES – Optionally, a fee to the customers at the time their number is ported (recipient network can pay this fee for the benefit of the new customers). Also, a monthly charge for a specific period of time (less than five years). monthly charges are levied regardless of whether the end-user has a ported number or not.

Carriers may decide to recover their costs of providing long-term telephone number portability in any lawful manner consistent with their obligations under the Telecommunications Act of 1996.

monthly charge from a few cents to a little over a dollar. Carriers have been allowed to do this in advance of the lNP deadline (five years since the first collected charge) because they have been incurring costs for lNP upgrades in preparation for the deadline. Also, carriers are allowed to charge a fee to customers at the time their number is ported.

Cost oriented

US (Fixed)

yES – A monthly charge for a specific period of time (five years). monthly charges are levied regardless of whether the end-user has a ported number or not.

Carriers may decide to recover their costs of providing long-term telephone number portability in any lawful manner consistent with their obligations under the Telecommunications Act of 1996.

monthly charge from a few cents to a little over a dollar for a period of five (5) years.

Cost oriented

Page 23: Operator Guidelines for Number Portability

23

OPERATOR GUIdElINES fOR NUmbER PORTAbIlITy

Appendix 3: Tekelec Number Portability Deployments by Country and Technology

• NP solutions or orders with more than 94 operators in 32 countries

• deployed 1st NP solution in 1997

• NP solutions for GSm, CdmA, fixed networks, cable as well as intra-carrier number retention

• NP solutions for voice, SmS, mmS and pre-paid calls

EMEA

• Egypt

• france

• Germany

• morocco

• Netherlands

• Poland

• Reunion

• Romania

• Spain

• Switzerland

North America

more than 30 lNP deployments

CALA

• brazil

• dominican Republic

• Guadeloupe

• Guiana

• martinique

• mexico

• St barthelemy

AsiaPacific

• Australia

• India (Trials)

• Israel

• Pakistan

• Singapore

• Taiwan

Page 24: Operator Guidelines for Number Portability

www.tekelec.com