This action might not be possible to undo. Are you sure you want to continue?
Worldwide Trends and Best Practices
VP Russia & CIS
© Neustar Inc. / Proprietary and Confidential
• Number Portability implementation options
• Worldwide Trends
• Key Impacts to Porting Rates
• Success Factors • Best Practices
Number Portability Technical Solutions
Country Australia Austria Belgium Canada Croatia Cyprus Czech Republic Denmark Egypt Estonia Finland France Germany Greece Hong Kong Hungary Iceland Ireland Israel Italy Japan Latvia Technical Method Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Indirect Indirect/Query on Release Direct-ACQ Direct-ACQ Direct ACQ Direct-ACQ Indirect/Onward Routing
Number Portability Technical Solutions Country Lithuania Luxembourg Macau Malta Netherlands New Zealand Norway Oman Pakistan Poland Portugal Singapore Slovakia Slovenia Saudi Arabia South Africa South Korea Spain Sweden Switzerland Taiwan UK USA Technical Method Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Indirect/Onward Routing Direct-ACQ Direct-ACQ* Indirect/Query on Release Direct-ACQ* Indirect/Onward Routing Direct-ACQ Direct-ACQ Direct-ACQ Direct-ACQ Indirect/Onward Routing Direct-ACQ Indirect/Onward Routing Direct-ACQ Indirect/Onward Routing* Direct-ACQ .
Number Portability Database Models Centralized Database model » Serves as a common infrastructure for ordering. provisioning and notification processes − Single/centralized reference database containing mapping data of Ported numbers and their respective Routing numbers Distributed Database model » Separate databases representing multiple subsets of total data generally managed by each network operator individually − Subsets of data typically reside at different locations .
Mobile Number Portability Database Models Country Australia Austria Belgium Canada Croatia Cyprus Czech Republic Database Type Centralized Distributed Centralized Centralized Centralized Distributed Centralized Denmark Egypt Estonia Finland France Germany Centralized Centralized Centralized Centralized Centralized Centralized Greece Hong Kong Hungary Iceland Ireland Israel Centralized Distributed Centralized Centralized Centralized Centralized Italy Japan Latvia Centralized Distributed Centralized .
Mobile Number Portability Database Models Country Lithuania Luxembourg Macau Malta Netherlands New Zealand Norway Oman Pakistan Poland Portugal Singapore Slovakia Slovenia Saudi Arabia South Africa South Korea Spain Sweden Switzerland Taiwan UK USA Database Type Centralized Centralized Centralized Distributed Centralized Centralized Centralized Distributed Centralized Distributed Centralized Centralized* Distributed Centralized Centralized Centralized Distributed Distributed Centralized Centralized Centralized Distributed* Centralized .
8 285.48 108.09.1 75.12 2008.01 2007.641.01.11.95 13.05 2010.07.542.5 11.30 2009.14 2009.0 7.3 20.951.01 2003.0 21.505 150.6 78% 64% 72% 86% 69% 73% 93% 2008.10.America Country Brazil Canada Dominican Republic Ecuador Mexico Peru USA 08 Population 08 Mobile Subs 08 Mobile MNP Deployment (million) (thousand) Penetration Date Time to Port 191.MNP Deployment .09.305.487 9.03.84 308.610.210.24 3 Days 2 hours 3–10 Days 4 Days 2-13 Days 7-9 Days 2 hours Porting Charge 4 BRL Free 80 DOP Free 1 USD Free (but 15 PEN for new SIM) Free (but monthly NP surchage) Neustar Confidential and Proprietary 8 .97 33.455.56 28.
0 11.412.13 4 Days 1 Day 30 mins 1 Day 1.10.5 45.620.7 6.06.13 2004.000 KRW 3 hours 1.03.607.15 23.29 0.04 22.03.395.04 2007.0 4.713.1 110.07 6.580.0 88.120.100 Yen • Singapore was the 1st one to launch MNP in the world (1997 with call forwarding) • South Korea is the one with shortest time to port (30 mins) in the world • India MNP launched Jan 2011 • Only country has decided to select 2 CSMS/NPAC vendors • Thailand MNP launched by February of 2011 Neustar Confidential and Proprietary 9 .95 4.23 176.98 127.019.0 25.5 Days Porting Charge Free Free (plus call forwarding) 2.375.0 933.25 1999.01 2006.5 105% 166% 87% 170% 103% 109% 50% 138% 95% 110% 2001.23 2008.01 4.55 27.24 2001 2008 2007.MNP Deployment – Asia Pacific Country Australia Hong Kong Japan Macau Malaysia New Zealand Pakistan Singapore South Korea Taiwan 08 Population 08 Mobile Subs 08 Mobile MNP Deployment (million) (thousand) Penetration Date Time to Port 21.10.01 2005.0 27.09.62 48.
2 6.15 2001.02 2002.224.01 2000.11.677.01 2006.0 13.862.49 9.91 65.01.07 2005.799.02.01 10 days 5 Days 8 days 13 days 7-30 Days 20 days 7 days 5 days 5 days 15-30 days 6 Days 5 Days Free 18.09.62 Free Free 9.627.016.44 59.4 2.04 82.0 105.11.6 10.6 707.892.0 8.5 6.26 11.022.01.7 13.523.054.72) 0-29 DKK 3 Days 2 days Porting Charge 19 Free € 2.03 2008.03 2004 2003 2002.86 10.824.14 10.1 10.MNP Deployment – Europe Country Austria Belgium Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland France Germany Greece Hungary Ireland Italy Latvia Lithuania Luxembourg Macedonia Netherlands Norway Poland Portugal Romania Slovak Republic Slovenia Spain Sweden Switerland 16.01 2003.56 5.36 5.250.520.780.25 2003.816.09.01 2008.2 7.8 1.2 10.896. the highest porting charge (30 euro) Turkey 73.5 10.46 1.05 2005 2000.42 0.15 2006 2005 2005.972.0 11.0 130% 112% 139% 133% 118% 134% 126% 188% 129% 93% 128% 124% 122% 121% 152% 2004.0 2.1 United Kingdom 61.9 43.8 10 .830.0 57.07 2006.3 62.68 21.10 2004.0 90.7 • MNP is a mandate from EU • All major European countries have implemented MNP • Some of the European countries have the longest time-toport (60 days).2 5.0 5.360.34 10.02 44.909.08 10 NOK Free 15 Free 10 5 EUR 6 days 5 Days 30-60 Days 5 Days 5 Days 7 days 5 Days 12 days 6 days 2 hours 3 Days 10 Days 5 Days 1 Days Free Free 10 Free Free Free €25 (up to €30.12 2001.59 7.34 5.32 5.09 1999.3 12.467.879.01.01 2001.06 2002.0 2.926.01 4.3 9.01 2008.01 1999.4 14.524.341.04.01 2004.357.2 5.07.500.77 38.04 2005.58 4.32 0.54 20.48 5.01.05 2002.23 Neustar Confidential and Proprietary 77.822.53 4.10.7 125% 110% 115% 140% 115% 102% 102% 112% 118% 118% 89% 126% 3.0 5.0 151% 147% 08 Population 08 Mobile Subs 08 Mobile MNP Deployment (million) (thousand) Penetration Date Time to Port 8.9 49.21 2004.6 24.10 2008.
5 3.06.05 5.219.07.95 151.5 8.3 36.21 2.12.03 2010.08 3 days 5 days 3–4 hours 1 Day Free 7 JOD Porting Charge • Least developed MNP market in the world.01 2011 2006.53 7.0 62.08.79 25.0 51% 127% 101% 42% 115% 143% 2008.0 6.26 2006.272.MNP Deployment – Mid East and Africa Africa & Mideast Country Egypt Israel Jordan Nigeria Oman Saudi Arabia 08 Population 08 Mobile Subs 08 Mobile MNP Deployment (million) (thousand) Penetration Date Time to Port 81.982.2 41.04 2007.010.988. in terms of deployments and ported numbers • Several Africa countries are in process of implementing MNP Neustar Confidential and Proprietary 11 .000.
it’s less clear that reducing the time to port beyond a few hours results in any material improvement in MNP adoption rates » • Porting Process Manual. time-consuming processes for end-users need to be avoided » Need to balance convenience with security to keep rejection rate at minimum » • End-user Porting Charges Higher porting charges will lead to lower porting rates » However. complicated. a small porting charge doesn’t inhibit the adoption rate » Neustar Confidential and Proprietary 12 .Key Impacts to NP Porting Rates • Time to Port Reducing time to port generally increases the adoption of porting » At the other extreme.
NP Implementation – Best Practices • Regulatory mandates are required to motivate the industry to act on LNP and must define: » Database Method for Number Portability Implementation » Database Architecture and Administration » Deployment Measures » Cost Recovery • Industry involvement is critical for success to: » Develop Business Rules for Porting Processes » Collaboration on New Technology and Supporting Implementation Requirements 13 .
NP Implementation – Best Practices Success factors: Maximize the amount of stakeholder awareness and buy-in to the NP Program » Create positive perceptions of the NP Program by highlighting benefits to Operators » Consistent flow of information across business lines is critical to the success of the NP Program. ensuring that there is a constant communication stream at all levels of the NP Program. The more validation. inform and dispel misinformation and rumors » Provide a vehicle for customer feedback » Communication Road Show to promote NP across the country » Manage Customer expectations » Limit validation fields. the higher the Fallout » Neustar Confidential and Proprietary 14 . It is important to educate and inform all employees on NP. » Educate.
/ Proprietary and Confidential .US Model 15 © Neustar Inc.
FCC Criteria LNP Minimum Performance Criteria » Support existing network services. features and capabilities » » » Efficiently use numbering resources Not require end users to change their telecommunications numbers Not require telecommunications carriers to rely on databases. or services provided by other telecommunications carriers in order to route calls to proper termination point Not result in unreasonable degradation in service quality or network reliability when implemented Not result in any degradation of service quality or network reliability when customers switch carriers » » » » » Not result in a carrier having a proprietary interest Be able to accommodate location and service portability in the future Have no significant adverse impact outside areas where number portability is deployed 16 . other network facilities.
How Local Number Portability Works Consumers & Businesses 1. Requests to Port Number 2. Request to Validate Subscriber Information *Note: Old Service Provider may NOT approve port and place Pending Port in ―Conflict‖. Broadcast of New Routing Instructions Users of NPAC Data LSMS . If consumer/business changes mind on port request.‖ New/Gaining Service Provider Old/Losing Service Provider 3. Notification of Pending Port 4. Activation of Pending Port 6. Confirmation of Subscriber Information 5. which. Approval of Pending Port* Users of NPAC Data LSMS 8. Creation of Pending Port Neustar Number Portability Administration Center 7. typically requires ―verbal‖ interaction between new and old service providers. Pending Port may be ―Cancelled.
U.S. Enforcement NANC Policy enactment LNP WG FCC LLC LNPA WG NANC NAPM LLC NPAC PUC Federal Communications Commission Limited Liability Corporation Local Number Portability Administration Working Group North American Numbering Council North American Portability Management Limited Liability Corporation Number Portability Administration Center Public Utility Commission Policy/standards formation NAPM LLC Master Agreement Contract/procurement administration Neutral third-party services User Agreements Users NPAC users Neustar Confidential and Proprietary 18 . Governance Model Key to Success FCC State PUC Policy.
/ Proprietary and Confidential . is controlled by. any telecommunications service provider 19 © Neustar Inc. or is under the direct or indirect common control with another person • Shall not be aligned with any particular telecommunication industry segment • Not to be subject to undue influence by parties with a vested interest in the outcome • May not issue a majority of its debt to. nor may it derive a majority of its revenues from.FCC Neutrality Criteria • Shall be an independent and impartial non-government entity • May not be an affiliate of any telecommunications service provider » ―Affiliate‖ is a person who controls.
or member interest) of such other person 20 © Neustar Inc. whether through the ownership of or right to vote voting rights attributable to the stock. joint venture participation. or member interest in the other person ten (10%) percent or more of the total outstanding equity interests The power to vote ten (10%) percent or more of the securities The power to direct or cause the direction of the management and policies.FCC Neutrality Criteria • Any affiliate may not issue a majority of its debt to. » » » An equity interest by stock. joint venture participation. partnership (general or limited) interest. / Proprietary and Confidential . partnership (general or limited) interest. nor derive a majority of its revenues from any telecommunications service provider.
/ Proprietary and Confidential .Other Governance Models 21 © Neustar Inc.
Wireless .Key Components Enforcement/Policy CRTC Policy Recommendation Policy/Standards Formation CISC BPWG and LNPA WG Master Agreement CLNPC Contract/Procurement Administration Neutral Third Party Services CRTC Canadian Radio and Television Commission CISC CRTC Interconnection Steering Committee BPWG Best Practices Working Group CLNPC Canadian Local Number Portability Consortium LNPA WG Local Number Portability Administration Working Group NPAC Number Portability Administration Center NPAC User Agreements Users NPAC Users Wireline.22 Canada Governance Model .
local Brazilian partner • 5 year contract • System and Maintenance • • • • 180 M Population 110 M Mobile Lines 50 M Fixed Lines 4 carriers in each market Group formed by the carriers and led by Anatel “LLC” The contracting party ABRt Roaming Association ClearTech NeuStar 23 Proprietary & Confidential .Brazil Governance Model Brazil LNP Community of Interest ANATEL Brazil Communications Regulatory Agency GIP Portability Group Fixed & Mobile Carriers • NS contract is with ClearTech.
Taiwan Governance Model Key to Success NCC NPAC Committee owned by operators Policy. Enforcement Policy enactment TECH WG ADMIN WG Policy/standards formation Contract/procurement administration Neutral third-party services NCC National Communications Commission (equivalent to FCC) Number Portability Administration Center Telecom Technology Center (NCC subsidiary) Technical Working Group TTC Master Agreement NPAC TTC TECH WG ADMIN WG User Agreements Administration Working Group Users NPAC users Neustar Confidential and Proprietary 24 .
NP Administration Models Consortium Administration NP Administrator organization (legal entity such as limited liability corporation) is set-up by Operators/Government Administrator has a single contract with supplier NP Administrator manages commercial service delivery with Operators Direct Administration Supplier acts as administrator Operator consortium makes initial purchase decision NP Provision directly engaged from Supplier Each Operator signs a service contract with Administrator Operators + Government Operators Gov’t Service contract NP Administrator Service contract NP Administrator System and service contract CDB CDB .
what about Transit Operators and other Telecom Service Providers and third parties enjoying benefits from Porting Data but never port a single number? » Generally deployed in smaller countries 26 © Neustar Inc.Charging Model Options • Fixed Price » Normally two components − Start-up fee to deploy the NP system − Monthly fixed fee to cover operations & maintenance » Considerations − There has to be a contracting entity − How to split costs amongst participants in a fair & equitable manner? • For example. / Proprietary and Confidential .
Charging Model Options • Transaction Based No upfront investment needed. / Proprietary and Confidential . vendor takes risks » Cost Recovery tied to either initiated or completed ports » There might be guaranteed minimum requirements » Only the operators who ―benefit‖ from NP pay for NP » Generally deployed in large countries » • Hybrid Start-up fee to deploy NP system (at least partial recovery) » Transaction based fees to cover operations & maintenance » 27 © Neustar Inc.
/ Proprietary and Confidential .Neustar Model to International Number Portability 28 © Neustar Inc.
Neustar Approach to Number Portability and Central Reference Database (CRD) • CRD is a key element for a successful NP implementation • CRD is a Service Offering based on » Core System » Best Practices » Managed Services • CRD Characteristics » Low-risk and rapid implementation » Flexibility to support initial needs and accommodate future requirements • Complete visibility and tight control of the entire project • Meeting financial targets by having predictable costs 29 © Neustar Inc. / Proprietary and Confidential .
Centralized NP Solution Architecture National Level Overall Management of the NP data Message Hub CDB Distribution Inventory Operator Level NP Service Provision and Synchronization Number Management Billing SOA LSMS Customer Records Operator NP Routing Level Query DB for NP Routing Information Local DB Service Provider Level Network Elements that perform NP routing MSC HLR MMSC SMSC 30 © Neustar Inc. / Proprietary and Confidential .
or DNS/ENUM server OSS Mobile Operator X 31 . SBC. CSCF. or DNS/ENUM server BSS MSC Gateway SSP Softswitch. SBC. CSCF. CSCF. or DNS/ENUM server Real-time Data Query NPDB STP Real-time Data Query Softswitch.Query Based Solution Architecture Donor Mobile Operator X Clearinghouse Provider Recipient Mobile Operator Y BSS Register Data Register Data Gateway Billing Gateway CDB Distribution Message Hub Billing BSS OSS MSC SSP MSC SSP OSS Download Data Softswitch. SBC.
» Logic layer − Business rules. DB management software for our NP Repository . 10 © Neustar Inc. » Data layer − Physical Data Base. DB interfacing software to allow on the fly emergency maintenance.Neustar’s Number Portability (NP) System • Our NP key components include: » Interface layer − Manual and M2M interfaces—Web -based GUI. customized software applications for BDR core services. reporting. notification/exception management. Performance & Health systems monitoring. File-based (FTP). Web services (SOAP/HTTPS). » Infrastructure layer − Network operation management systems. / Proprietary and Confidential .
Bodnar@neustar.Questions and Answers.biz 21 © Neustar Inc. / Proprietary and Confidential . / Proprietary and Confidential © Neustar Inc. Patrick Bodnar + 1 571 291 1200 patrick.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.