Mobile Number Portability Corporate (Bulk) Process

1. Mobile Number PortabilityCorporate (Bulk) Process Alan Boniface MNP Product Manager 28 March 2000

2. Current Industry Process ONO = Original Network Operator DNO = Donor Network Operator RNO = Recipient Network Operator DSP = Donor Service provider RSP = Recipient Service Provider 1 - Customer requests port-in to RSP 2 - RSP submits porting request to DSP 3 - DSP clarifies port-out request with customer (optional) 4 - Customer withdraws or wishes to revise porting request (optional) 5 - DSP rejects porting request (exception) 6A - DSP accepts porting request 6B - DSP initiates port-out actions 7A - DNO proceeds with port-out actions 7B - ONO modifies residual subscription 7C - DNO completes port-across actions 8A - RSP initiates port-in actions 8B - RSP completes port-in actions

3. Industry Porting Timeline RSP receives port-in request 2 days to send port request to DSP 2 days RSP submits request to DSP 2 days for DSP to acknowledge receipt 2 days DSP acknowledges request 5-15 days for DSP to confirm with customer 5-15 days 15-25 wk days Point of No Return for customer RSP action date 6 days RSP has 6 days to get phone and/or SIM to customer MSISDN ported to RNO

4. MNP - What are the challenges? Current Problems - Six Major • Customer & Industry Confusion • Complexity • Communications - Fax, volume of calls • Time it takes - minimum 15 working days • Unsuccessful Porting • Charging

5. MNP volumes across the industry are much lower than originally forecast (225k versus approx. 900k) why would this be? what would you do to stimulate demand? A couple of questions for you…..

6. MNP - Process 2000 - what’s happening? • Network Operators and Service Providers desire to have a more efficient and cost effective MNP solution which will better serve the needs of their customers • OFTEL has requested a new process to be implemented in mid-2000 • shorter timescales • better process visibility • more robust/less errors

7. New Process Plan • new industry process has been in design since early June 1999, manual agreed January 2000 • process sub-group designing new process • 1 rep from each Network, 1 each from 2 Independent Service Providers, 1 OFTEL rep • 2 distinct processes • consumer - 1 to 25 MSISDNs • one week to port, ie 5 working days • corporate (Bulk) - 26+ MSISDNs • variable timescale, up to 35 working days • will incorporate Web technology for inter-SP communications - to be developed and hosted by 3rd party

8. New Corporate (Bulk) Process 5 Recipient Service Provider Donor Service Provider port request communicate details electronically request response 6 3 Inform & Negotiate issue porting authorisation code (PAC) 2 1 request approach RSP with PAC Dealer 4 Corporation 7 respond to port request

9. Pre-requisite: Customer has obtained PAC from DSP Total Process Time-scale = 35 working days. Customer can request to port as soon as they have PAC 25 Working Days t = 0 days Min. Customer requests Port In to RSPAnytime between date of issue of PAC and 30 calendar days RSP Submits Port request to DSPWithin 2 working days of receiving port request DSP Confirms or refuses port request Within 2 working days of receipt from RSP Port is scheduled to occur within this 25 working day timeframe. DSP and RSP agree on Porting Schedule Within 8 working days. Port Day.Confirmed Port is processed. t = 30 days Max 1 Working Day PAC is valid for 30 calendar days from issue date. 2 Working Days 2 Working Days MNP 2000 - Bulk Porting Process Time-scales DSP = Donor Service Provider RSP = Recipient Service Provider

10. Pros: Donor Service Provider dealing with customer not third party Recipient Service Provider gets full information quicker Port day expectations set & met Lends itself to electronic communication Con: Could be lengthy or no quicker than existing process New Corporate (Bulk) Process No ‘Show Stoppers’ identified

11. MNP - A new way of communicating Communicate byE-mail, moving to Web Technology.