Documente Academic
Documente Profesional
Documente Cultură
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
9420023456
HLR
PSTN HLR
9420023456
Wireless Operator A
Wireless Operator B
Subscriber changes Mobile Service Provider while keeping its mobile number
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
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
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
(Associated Mode)
PSTN Cloud
Routing Table
Route Code -> Destination 9.. 09. ->PC 4000 ->PC 4000
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
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
PSTN Cloud
Charging Table
Route Code -> Charging
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
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.
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.
SSTP will prefix the RN with B party number in the IAM and send it to next destination.
PSTN Cloud
Routing and Charging of Mobile Calls in Post MNP ScenarioRouting of calls from local Xge to L-II TAX
PSTN Cloud
s
SSTP
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
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
C7 link
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
SSTP
PSTN Cloud
Before MNP: Voice and Signaling Path for Fixed to Mobile Calls
SDCA-A
SDCA-B
SDCA-C
LDCA
Voice Path Signaling Path
After MNP: Voice and Signaling Logical Path for Fixed to Mobile Calls
SDCA-A
SDCA-B
SDCA-C
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
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.
Responsibilities
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
Necessary creation of routing and charging information is required to be done at Level I/II Taxs.
This method requires connecting all the local exchanges with SSTP.
Since availability of limited ports in SSTP network and large number of local exchanges in BSNL networks, hence it has been decided only few new technology local exchanges
For handling Fixed to Mobile Calls for various IN Services e.g. VCC, FPH, FLPP etc.
For handling prepaid IN calls like VCC, FLPP, ACC ,FLPP etc,SSP functionality of only local exchanges can be used so that only IAM is intercepted before calls enter into the Lev II/Tandems having POI connectivity. Hence all field units should ensure local exchanges connecting to SSTP are upgraded for SSP functionality. Implementing MNP in Postpaid IN Services such as FPH, UAN, VPN etc, mapped number in SCP is to be defined with RN+B (in case translated number is mobile). In few cases (where all local switches are CDOT technology) which cant be used for SSP functionality and only SSP functionality of LEV II tax is available then all intra circle Fixed to Mobile-IN Prepaid traffic may be routed to respective Lev I Tax. Necessary re-dimensioning of Poi's at Lev I Tax to be taken care off.
C-9449828818 9449828818 55559449828818 (In PREA 15 TRAD 6, PRE = C944982 RCE=2) Analysis 944982 to opened in TRAD 6 And routed to TAX with PTX=0 and FITX To be given towards TAX ACH (new).
In this scenario Customer dials Service access code 1860425+ 4 digit code (Code can be 0000 to 4999 any number). This 4 digit code is mapped with a mobile number with RN prefixed, Eg - 55559449828818. When customer dials the access code in return SCP returns C+RN+DN (C55559449828818) to SSP with charge band. SSP -------------------------> SCP 18604252222 SSP ------------------------- SCP C55559449828818 + Charge Band Calling party is charged 30sec pulse. Called party is not charged.
Split Charging
In this scenario Customer dials Service access code 1860425+ 4 digit code (Code can be 5000 to 9999 any number). This 4 digit code is mapped with a mobile number with RN prefixed, Eg 55559449828818. When customer dials the access code in return SCP returns C+RN+DN (C55559449828818) to SSP with charge band. SSP -------------------------> SCP 18604252222 SSP ---------------------- SCP C55559449828818 + Charge Band Calling party is charged 180sec pulse. Called party is charged as per STD charges
Thank you