1. Mobile Number Portability Corporate (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. RSP receives port-in request RSP submits request to DSP DSP acknowledges request RSP action date MSISDN ported to RNO 2 days 5-15 days 6 days 2 days to send port request to DSP 2 days for DSP to acknowledge receipt 5-15 days for DSP to confirm with customer Point of No Return for customer RSP has 6 days to get phone and/or SIM to customer 15-25 wk days Industry Porting Timeline

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. A couple of questions for you….. 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?

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 Recipient Service Provider Donor Service Provider Corporation Dealer 1 2 request port request communicate details electronically issue porting authorisation code (PAC) approach RSP with PAC respond to port request Inform & Negotiate 3 4 5 6 7 request response

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

10. New Corporate (Bulk) Process 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 No ‘Show Stoppers’ identified

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