WHITE PAPER

Operator Guidelines for Number Portability

Challenges and Solutions for ITU- & ANSI-based Networks

An overview of number portability, including design issues, cost recovery and solutions, for ANSI- and ITU-based fixed and mobile operators.

5200 Paramount Parkway Morrisville, NC 27560 (USA) 1-919.460.5500 or 1-888.628.5527 1

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. 2008, 2009 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-02-2009

www.tekelec.com
1

This page intentionally left blank

ii

Table of Contents
Introduction .............................................................................................................................................1 Industry Drivers for Number Portability................................................................................................1 Implementing Number Portability .........................................................................................................2
Portability Types................................................................................................................................................... 3 Key Network Elements in a Number Portability Domain ................................................................................. 3 Routing Methods.................................................................................................................................................. 4 Costs and Recovery .............................................................................................................................................. 5 Critical Implementation Steps ............................................................................................................................. 6

Architecture Considerations ...................................................................................................................6

ITU-based Number Portability Solutions ............................................................................................................ 8 Mobile Number Portability ................................................................................................................................... 8 Fixed Number Portability ...................................................................................................................................... 8

Tekelec Solutions for Number Portability .............................................................................................8

SRF-based Mobile Number Portability................................................................................................................ 8 Triggerless MNP for ANSI-41 Network ............................................................................................................... 9 Triggered-based NP Solution............................................................................................................................... 9 ANSI-41 INP Query (AINPQ) ................................................................................................................................. 9 Triggerless ISUP-based NP (TINP) ........................................................................................................................ 9 IS-41 to GSM Migration ....................................................................................................................................... 9 Number Portability for SMS, MMS & Prepaid Calls ........................................................................................... 9 Number Portability Provisioning Flow ............................................................................................................. 11

About Tekelec........................................................................................................................................11 Appendix 1 Acronyms Used in this Document.................................................................................13 Appendix 2 Number Portability Charging Fees................................................................................14 Appendix 3 Tekelec Number Portability Deployments by Country and Technology....................15

Introduction
Number 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: o Industry drivers for number portability o Implementing number portability o Portability types o Key network elements in a number portability domain o Routing methods o 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 Tekelecs web site at www.tekelec.com, or contact your Tekelec sales representative.

Industry Drivers for Number Portability

Number 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. 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 didnt previously subscribe, and will prompt the sale of additional, high-end telephony services to existing subscribers.

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

Implementing Number Portability

Since 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.

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

White Paper - 2008, 2009 Tekelec, Inc.

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 Tekelecs 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).

Figure 2. Key Elements in a Number Portability Domain

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

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: o Determine whether the called party is a ported number; and o Route the call to its subscription network Indirect routing (onward routing) - the donor network has the responsibility to: o Determine whether the called party is a ported number; and o Route the call to its subscription network

Figure 3. Direct Routing Example for GSM Ported Directory Number

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

White Paper - 2008, 2009 Tekelec, Inc.

Figure 4. Indirect Routing Example for GSM Ported Directory Number

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. 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.

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

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 companys 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 Considerations
Historically, all numbering plans have assumed a fixed relationship between a customers number, an operator and/or physical switch location. In the NP environment, the operator and physical switch locations are decoupled from the customers number, becoming a virtual number. Implementing NP requires carriers to retool their network architecture and rethink the role of the intelligent network. 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.

White Paper - 2008, 2009 Tekelec, Inc.

Figure 5: Integrated STP/NP solution 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

Footprint Integrated STP, NP dB and Signaling Relay Function (SRF) High transaction rates, real-time memory dB access ~ 75,000 transactions per second (TPS) per system Simple growth additional cards hotplugged into existing frame/system Centralized data maintenance

SCP NP Approach
Multi-platform deployment requiring additional point codes (PCs) Low transaction rates, typically nonreal time disk access ~ 4,000 transactions per second (TPS) per system Growth may require new nodes

Performance

Scalability

Data Management

Related data is maintained in multiple network entities Lower reliability due to external network connections

Reliability

Higher reliability - avoids potential network failures due to external network connections Superior throughput

Throughput

Throughput of an SCP is limited by 32-link combined linkset constraint. Higher cost related to deployment of SCP nodes and the associated transmission facilities

Cost

Lower cost - reduced number of links required

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

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 Portability

Tekelec has extensive experience and expertise in deploying number portability solutions for fixed and mobile operators with more than 76 deployments worldwide (see Appendix 3 for Tekelecs NP deployments). Tekelec solves the number portability problem for voice, short message service (SMS), multimedia message service (MMS) and prepaid calls. Tekelecs 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.

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.

White Paper - 2008, 2009 Tekelec, Inc.

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 subscribers 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, 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 Tekelecs NP solutions for SMS, MMS and prepaid calls include:

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

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. 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. Table 2 lists Tekelecs broad portfolio of ITU- and ANSI-based NP solutions covering voice, SMS, MMS and prepaid calls. NP Solutions SRF-based MNP Triggerless MNP for ANSI41 Network TINP Triggered-based NP Solution AINPQ MO-SMS GSM MO-SMS-IS41 MT-SMS GSM MT-SMS IS41 MT-MMS-GSM MT-MMS-IS41 GSM MMS using INAP ANSI MMS using IS41 IDPR AINPQ Data Type Voice Voice Voice Voice Type Triggerless Triggerless Triggerless Triggered Operator Type GSM TDMA/CDMA Wireline Wireline GSM Voice SMS SMS SMS SMS MMS MMS MMS MMS Pre-paid Pre-paid Triggered Triggerless Triggerless Triggerless Triggerless Triggerless Triggerless Triggered Triggered Triggerless Triggered TDMA/CDMA GSM TDMA/CDMA GSM TDMA/CDMA GSM TDMA/CDMA GSM TDMA/CDMA GSM TDMA/CDMA Protcol GSM MAP IS41 ISUP INAP INAP/CAMEL IS41 GSM MAP IS41 GSM MAP IS41 GSM MAP IS41 INAP/CAMEL IS41 INAP/CAMEL IS41 Message Name(s) SRI LOCREQ IAM IDP IDP NPREQ MO_SMS SMDPP SRI_SM SMSREQ SRI_SM SMSREQ IDP NPREQ IDP NPREQ

Table 2. Tekelecs number portability solutions for mobile and fixed-line networks

10

White Paper - 2008, 2009 Tekelec, Inc.

Number Portability Provisioning Flow

Figure 6 shows the provisioning flow for Tekelecs 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.

Figure 3. Tekelec number portability provisioning flow

Figure 6. Full NPDB replicated in each SM card and in each EPAP Server

About

Tekelec
Tekelec is a high-performance network applications company that is accelerating the transition to IP multimedia subsystem (IMS) networks for service providers around the globe. Tekelec is the worldwide leader in the SS7 STP market with a 38% share (Sources: VDC, May 2006), more than double that of the nearest competitor. Tekelec has led the industry in number portability innovation, deploying the first integrated number portability solution in 1997 with Bell Atlantic. Since then, Tekelec has deployed number portability solutions with more than 76 operators around the world. Tekelec has a broad portfolio of NP solutions (Table 2) covering GSM, CDMA and fixed networks, as well as intra-carrier number retention. Tekelecs EAGLE 5 platform brings additional value to operators by enabling them to leverage new or existing EAGLE deployments for integrated signaling-NP solutions, as well as other core network applications such as HLR and voicemail route optimization, performance and service management. See Appendix 3 for additional information on Tekelecs number portability deployments. Tekelec is the recognized leader in integrated, high-performance, carrier-grade NP solutions, offering: Flexibility Supports either stand-alone or integrated approaches. In a stand-alone configuration, the EAGLE 5 platform is deployed as a stand-alone NP server. In an integrated configuration, the EAGLE 5 platform supports both standards-compliant STP functions and NP functions. Scalability Supports any size network and provides fully scalable transaction rates. Capacity to scale from 850 to 75,000 transactions per second with connectivity for two to two thousand links, one million GTT entries, and up to 96 million NP subscriber records. The North American LNP solution is scheduled to support 384 million records by 2008. Cost effectiveness Integrated STP/NP configuration of the EAGLE 5 eliminates CAPEX and OPEX associated with external SCPs by saving on external links (to SCPs) and having fewer network elements to maintain.

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

11

High performance Supports up to 75,000 message signaling units (MSUs) per second. Carrier-grade reliability Eliminates unnecessary external network connections and signaling hops. Signaling traffic routing is simplified, thereby reducing network failures and improving network reliability. For additional information on number portability and to learn more on how you can implement it in your network, please contact your local Tekelec representative or visit www.tekelec.com.

12

White Paper - 2008, 2009 Tekelec, Inc.

Appendix 1 Acronyms Used in this Document

ANSI AINPQ ATM CAMEL CAPEX CDMA CdPN DN EO EPAP ETSI FCC GSM GTT HLR IAM IMSI IN INAP INP IS-41 ISDN ITU LNP MAP MMS MNP MSISDN NP NPDB OPEX POTS RN SCP SIM SMPP SM SRF STP TDMA TINP UMTS USA American National Standards Institute ANSI-41 INP Query Asynchronous Transfer Mode Customized Applications for Mobile Enhanced Logic Capital Expense Code Division Multiple Access Called Party Number Directory Number End Office EAGLE Provisioning Application Processor European Telecommunications Standards Institute Federal Communication Commission Global System for Mobile Communications Global Title Translation Home Location Register Initial Address Message International Mobile Station Identifier Intelligent Network Intelligent Network Application Protocol or Part INAP-based Number Portability Interim Standard 41 Integrated Services Digital Network International Telecommunications Union Local Number Portability Mobile Application Part Multimedia Message Service Mobile Number Portability Mobile Station International ISDN Number Number Portability Number Portability Database Operating Expense Plain Old Telephone Service Routing Number Service Control Point Subscriber Identity Module Short Message Peer-to-Peer Protocol Service Module Signaling Relay Function Signal Transfer Point Time Division Multiple Access Triggerless ISUP-based NP Universal Mobile Telecommunications System United States of America Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

13

Appendix 2 Number Portability Charging Fees

Source: S. Buehler et al (2006). Mobile Number Portability in Europe. Telecommunications Policy, 30, 385399. Country
Austria Belgium

Permission of charging fees?

YES YESOnly recipient network is allowed to charge fees. YESCustomers pay typically the fee that operators charge to their competitors. YES

Regulation of maximum fee?

Max. 19 Max. 15

Fee
Recipient network charges 415 Only pre-paid but not post-paid customers are charged for porting mobile subscribers Operators committed to charge 9.60 per ported number to customers. The donor operator charges the same amount to the new operator.

Basis
Cost oriented

Denmark

NO

Cost oriented

Germany

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

YESOnly recipient network is allowed to charge fees. YES YES

NO

The donor network charges about 510 to the recipient operator. No fees for customers. Up to the recipient operator whether or not to charge the porting customers for porting. No fees for customers.

Cost oriented

Greece Hong Kong

Max. HK$10

Cost oriented

Ireland

YESCharges shall not be a disincentive for users to port their number. YESOnly recipient network is allowed to charge fees. YESOnly recipient network is allowed to charge fees. Charge shall not exceed administrative costs. YESOnly recipient network is allowed to charge fees.

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

Cost oriented

Italy

The donor operator charges 10.02 to the recipient operator. No fees for customers. The recipient operator is allowed to charge the customer 9. Charges consist of administrative fees.

Netherlands

Max. 9

Norway

NO

Charge between networks should cover costs of donor network. Cost oriented (administrative and porting costs) Marginal costs Cost oriented

Portugal Sweden

YES YESOnly donor network is allowed to charge fees. YES YES YES YESOptionally, 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 enduser has a ported number or not. YESA 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.

NO NO (to customer), YES (donor to recipient) NO Charges shall not be a disincentive for users to port their number. adequate fees 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.

Only donor operators charge 424 fees to the recipient operator. No fees. Typically no fees. Some operators charge 25. 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. Monthly charge from a few cents to a little over a dollar for a period of five (5) years.

Switzerland Spain UK US (Mobile)

US (Fixed)

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.

Cost oriented

14

White Paper - 2008, 2009 Tekelec, Inc.

Appendix 3 Tekelec Number Portability Deployments by Country and Technology

NP solutions or orders with more than 76 operators in 26 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 North America
More than 30 LNP deployments

AsiaPacific

Egypt France Germany Morocco Netherlands Poland Reunion Romania Spain Switzerland

CALA
Brazil Dominican Republic Guadeloupe Guiana Martinique Mexico St Barthelemy

Australia India (Trials) Israel Pakistan Singapore Taiwan

Operator Guidelines for Number Portability Challenges and Solutions for ITU- & ANSI-based Networks

15