Sie sind auf Seite 1von 31

Mobile Number Portability (MNP) Implementation in Wire Line Switches

Meeting of South and West Zone Dated 13.01.2010

Sanjay Kumar
DGM (NWO-II/CFA) NWO-CFA Cell BSNL CO

Agenda
1. What is MNP-An overview? 2. DOT guidelines. 3. What is required to be done in Wire Line Switches and why? 4. Post MNP-How to make Wire Line switches compatible with Mobile Network? 5. Implementation Plan 6. What is required to be done in CDR Billing Project? 7. Responsibilities of Nodal Officers of the Circles 8. Timelines 9. Discussions

Steps already taken:


Completion of Field Trial at Bangalore Issuing of instructions along with technical note vide letter dated 15.12.2009. Issuing of List of RN Finalization of solution for making CDR Billing Project compatible with MNP. Development and field trial of C-DOT patch required for above solution completed.

What is Number Portability?


Portability of Mobile Numbers between all GSM and CDMA operators within the same Service Area. A Mobile subscriber can change his/her operator within the same Service Area without changing his/her number. No Portability beyond Service Area. Portability between GSM and CDMA network of same operator in same service area possible.

What is Number Portability?


First Mobile Number is deprovisioned from Donor operators HLR Later Mobile Number is provisioned in Recipient operators HLR

9420023456
HLR

PSTN HLR

9420023456

Wireless Operator A

Wireless Operator B

Subscriber changes Mobile Service Provider while keeping its mobile number

CMTS Licensed Service Area

Some Definations
IAM (Initial Address Message)- One of the CCS-7 Message, used to seize the circuit between two xges, contain Calling and Called party number SSTP- Stand alone STP STP- Signaling Transfer Point RN- Routing Number MCHA- Mobile Clearing House Administration

Some Definations-Contd
NPDB- Number Portability Database RN Routing Number TAX Trunk Automatic Exchange ILD International Long Distance TAX NPDB Number Portability Database Home RN Operators own RN PSTN Public Switched Telephone Network, here BSNL Wire line Network PLMN Public Land Mobile Network, here BSNL GSM Mobile Network

Porting Definations
Not Ported Mobile Numbers belonging to BSNL. These numbers will be defined in the NPDB with HLR (PC & SSN) information .Will be defined in the Range DN Table of the NPDB
Imported Number ported into BSNL from another network. These numbers will be defined in the NPDB with HLR (PC & SSN) information. Will be defined in the Single DN Table of the NPDB. Ported Out Number Ported out to another network from BSNL . These numbers will be defined in the NPDB with RN information . Will be defined in the Single DN Table of the NPDB. Foreign Number Other Operator subscriber not known to be ported. These numbers will be defined in the NPDB with RN information. Will be defined

in the Range DN Table of the NPDB.

DOT Guidelines
In first Phase MNP is to be implemented in 4 metros and all 5 A category LSAs 9 LSAs in total In second phase B and C category Circles Deadline: 31.03.2010

Number Portability Business Process Inter and Intra Telco


1. Request to switch to Telco A

Telco A
Sales Customer Service Network

Telco B
Sales

2. Request to port
IT

Customer Service Network

Voice

IT

3. Verify the request

Telco B Customer 6. Update OSS / BSS 7. Update Voice / SMS Routing 4. Approve or Reject

Mobile Clearing House

Telco C
Sales Customer Service Network

Telco D
5. Update the Central Data Base
Sales Customer Service Network

IT

IT

What is to be done in land Line switches and why?

Presently calls are being routed to concerned operator based on dialed number

Post MNP ; to route the Mobile calls to correct operator switches has to determine the present operator of the dialed number(B)

To know the present operator of the dialed number(RN) , switches need to be connected with external database i.e. LPDB

After getting the RN, switch routes the call to concerned operator based on RN+B Information .

Routing and Charging of Mobile Calls in Pre MNP Scenario- Routing of calls from local Xge to L-II TAX

Voice and Signaling path


LEX PC: 2000

(Associated Mode)

L-II TAX PC:4000

PSTN Cloud

Routing Table
Route Code -> Destination 9.. 09. ->PC 4000 ->PC 4000

Route Code-> 94282.. 98382. 09

Routing Table Destination- Signaling Point Code -> Send to PC 4001 (BSNL MSC) -> Send to PC 4005 ( BHARTI MSC) -> send to PC 5000 (L-I TAX)

Charging Table

Charging Table
Route Code -> Charging 9.. 09. -> by Next Higher Xge ->by Next Higher Xge

Route Code -> 94282.. 98382.. 094500. 099567.

Charging

->Charging Defined(intra operator-intra circle) ->Charging Defined(inter operator-intra circle) -> Charging Defined (inter Circle- intra operator) -> Charging Defined (inter Circle- inter operator)

Routing and Charging of Mobile Calls in Pre MNP Scenario- Routing of calls from L-II TAX to L-I TAX/MSC

From LEX

L-II TAX PC:4000


Routing Table Destination -> Send to PC 4000 (BSNL MSC) -> Send to PC 4005 ( BHARTI MSC) -> send to PC 5000 (L-I TAX)
BHARTI MSC (PC:4005)

BSNL MSC (PC:4000)

Route Code-> 94282.. 98382. 09

PSTN Cloud

Charging Table
Route Code -> Charging

L-I TAX BSNL (PC:5000)

94282.. ->Charging Defined(intra operator-intra circle) 98382.. ->Charging Defined(inter operator-intra circle) 094500. -> Charging Defined (inter Circle- intra operator)

Routing and Charging Scenario in Present ( Pre MNP) Scenario Routing and Charging is done in Exchanges based on Dialed Digits ( B Party Number) For Routing the Fixed to Mobile calls ROUTE CODES are created in Xges

Charging is also based on dialed digits.


By analyzing the Dialed Digits ( B Party Number) in exchanges it is possible to route the code to corresponding MSC/ Landline Xge( for further routing to corresponding MSC) First 2 or 5 Digits (2 Digits Access Code + 3 Digit MSC code) of a mobile number determines the Mobile operator of the number.

Routing and Charging Scenario in Post MNP Scenario Issues: In exchanges it would not be possible to route the Fixed to Mobile call to corresponding MSC by analyzing the Dialed Digits ( B Party Number) , because now any Mobile number can belong to any Operator in the Service Area. Mobile number no longer determines the Mobile operator of the number.

As per DOT guidelines determination of correct Terminating Mobile Operator is the responsibility of the Originating Operator.

What is required to solve the problem:

Issues:
1. Getting information for determining present operator of the Mobile Number 2. Using this information to determine correct Routing and Charging in the exchanges.

What is required to solve the problem:


Solution: Getting the extra ROUTING information This extra information will be provided by the Route Number given by the DOT to each operator (one for GSM network and one for CDMA network). RN for each Mobile Number will be stored in one central Database (NPDB). Associated RN of each Mobile Number will determine the present operator of the number. This RN changes when a mobile number is ported to other Mobile Operator.

What is required to solve the problem-contd:

Solution: Getting the extra information

These NPDB will be integrated with SSTP


SSTP will intercept IAM (Initial Address Message) passing through it and will scan the B Party Number. SSTP will get the appropriate RN for the B party number (retrieved from IAM) from integrated NPDB

SSTP will prefix the RN with B party number in the IAM and send it to next destination.

What is required to solve the problem-contd:

Solution: Using the extra information


RN codes need to be created in exchanges. CCS 7 messages related to Fixed to Mobile Calls need to pass through SSTP network, at least once, before call is handed over to corresponding MSCs. Determination of corresponding MSC ,where call can be routed, is based on RN.

Logical Connectivity of Exchanges with SSTP


Routing and Charging of Mobile Calls in Pre MNP ScenarioRouting of calls from local Xge to L-II TAX

LEX PC: 2000

L-II TAX PC:4000 SSTP

PSTN Cloud

Routing and Charging of Mobile Calls in Post MNP ScenarioRouting of calls from local Xge to L-II TAX

LEX PC: 2000

L-II TAX PC:4000 SSTP

PSTN Cloud
s

SSTP

Route Number Solution


Centralized Solution
Operator 1 NP Database Operator 2 NP Database

NPAC
NP Database

Operator 3 NP Database

Operator 4 NP Database

Central Database containing the information of association of each mobile number with Mobile Service Operator Each Operator has been given two unique 4 digit Number( one for GSM and one for CDMA operator) called Routing Number(RN) Number is called Routing Number as it is used to route the call to correct Service Provider

Flow of RN from NPDB to PSTN Exchanges


SSTP Cloud

CCS-7 Links

RN

PSTN Cloud

NPDB

Physical Connectivity of Exchanges with SSTP in Post MNP and Call Flow
1. IAM message is tunneled through the permanent C-7 connection from L-II TAX to SSTP

2. RN is retrieved by
SSTP from NPDB

NPDB
RN(BHARTI GSM)=5555

9444923456
Trunk Group

C7 link
LEX PC: 2000

Nailed Up C7 Connection

Voice Path

L-II TAX PC: 4000

C7 link

CH i CH i CH i C4 i CH i CH i CH 3. B number iin IAM is

C- 7 HSL connectivity

5. A new IAM is formed by L-II TAX based on the Routing Table and RN information 6. IAM is sent to corresponding MSC

replaced by RN+B 4. Modified IAM is sent towards L-II TAX

SSTP

BHARTI MSC (PC:4005)

7. MSC checks whether


the RN is same as Home RN, if yes, call proceeds otherwise call is rejected

PSTN Cloud

Before MNP: Voice and Signaling Path for Fixed to Mobile Calls

SDCA-A

SDCA-B

SDCA-C

BSNL/Pvt. Operators CMSP Network

SDCA-D Level-II TAX

Local cum Tandem Exch.

BSNL PSTN Network

LDCA
Voice Path Signaling Path

After MNP: Voice and Signaling Logical Path for Fixed to Mobile Calls

SDCA-A

SDCA-B

SDCA-C

BSNL/Pvt. Operators CMSP Network

SDCA-D Level-II TAX Local cum Tandem Exch. SSTP/LPDB

BSNL PSTN Network

LDCA
Voice Path Signaling Path
Note: The connectivity between local exchanges and SSTP may be established by creating NUC(Nailed Up Connections) at TAX.

Prerequisites
All Level-II to Level I C-7 Traffic already shifted to SSTP Network

All Level-II to Level II C-7 Traffic already shifted to SSTP Network No CMTS POI at Local Exchanges

Issues in CDR Billing Project

Post MNP, RN Information will be available only in L-II /L-I TAX s not in Local Exchanges. For implementing Deferential charging in Retail Billing RN information must be available in CDRs of Local Exchanges. One of the method is to take Fixed to Mobile calls CDRs from L-II TAX and use it for retail billing along with the CDRs generated at Local Exchanges The above method requires major changes in software and Hardware of Retail Billing Servers of CDR project.

Solution Finalized:
One of the alternative method is to use Charge Band Number captured in CDRs of Local Exchanges, for determining the Intra and Inter operator call As the CHB number captured in the CDRs of Local Exchanges will be different in case tariff for intra BSNL and inter operator calls is different Though CHB No information is captured by all NT switches but not by C-DOT switches One Patch for capturing the CHB No in CDRs of C-DOT exchanges has been got developed

This patch is to be loaded in all C-DOT exchanges before they come under CDR Billing Project
For SSAs already under CRD project, necessary instructions are to be issued by IT Cell, CO/ITPC.

Timelines
Activity
Holding of internal meetings with SSAs and finalization of implementation Plan Completion of Physical Connectivity

To be completed by
17.01.2010 22. 01.2010

Completion of Database Creation in switches and SSTP Completion of Testing with BSNL Mobile Network Completion of Testing with Mobile Network of other Service Operators

25. 01.2010
30. 01.2010

To be intimated Later

Responsibilities of Nodal Officers


Monitoring of Implementation and to ensure completion of work as per schedule Co-ordination between Wire line and Mobile Group
Interaction with HO Holding Internal Meetings with SSA and finalization of plan Loading of C-DOT patch based on CDR Billing Rollout Plan

Thank you

Das könnte Ihnen auch gefallen