mobile number portability (mnp) implementation in wire line switches meeting at circle office dated...
Post on 26-Dec-2015
220 Views
Preview:
TRANSCRIPT
Mobile Number Portability (MNP)Implementation in Wire Line Switches
Meeting at Circle OfficeDated 12.01.2010
Agenda1. 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 Plan6. What is required to be done in CDR Billing Project?7. Responsibilities of Nodal Officers of the Circles8. Timelines9. 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.
• 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.
• 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?
WirelessOperator A
WirelessOperator B
HLR HLR
94200234569420023456
Subscriber changes Mobile Service Providerwhile keeping its mobile number
PSTN
CMTS Licensed Service Area
First Mobile Number is de-provisioned from Donor
operator’s HLR
First Mobile Number is de-provisioned from Donor
operator’s HLR
Later Mobile Number is provisioned in Recipient
operator’s HLR
Later Mobile Number is provisioned in Recipient
operator’s HLR
What is Number Portability?
• 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
• 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
NPDB- Number Portability DatabaseRN – Routing NumberTAX – Trunk Automatic ExchangeILD – International Long Distance TAXNPDB – Number Portability DatabaseHome RN – Operators own RNPSTN – Public Switched Telephone Network, here
BSNL Wire line NetworkPLMN – Public Land Mobile Network, here BSNL GSM
Mobile Network
NPDB- Number Portability DatabaseRN – Routing NumberTAX – Trunk Automatic ExchangeILD – International Long Distance TAXNPDB – Number Portability DatabaseHome RN – Operators own RNPSTN – Public Switched Telephone Network, here
BSNL Wire line NetworkPLMN – 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
What is to be done in land Line switches and why?
Routing and Charging of Mobile Calls in Pre MNP Scenario- Routing of calls from local Xge to L-II TAX
LEXPC: 2000
LEXPC: 2000
Routing TableRoute Code -> Destination
9..…… ->PC 400009……. ->PC 4000
Charging Table
Route Code -> Charging
9..…… -> by Next Higher Xge09……. ->by Next Higher Xge
L-II TAXPC:4000L-II TAXPC:4000
Routing TableRoute Code-> Destination- Signaling Point Code
94282..…… -> Send to PC 4001 (BSNL MSC)98382……. -> Send to PC 4005 ( BHARTI MSC)09…… -> send to PC 5000 (L-I TAX)
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)099567……. -> Charging Defined (inter Circle- inter operator)
PSTNCloudVoice and Signaling path
(Associated Mode)
Routing and Charging of Mobile Calls in Pre MNP Scenario- Routing of calls from L-II TAX to L-I TAX/MSC
L-II TAXPC:4000L-II TAXPC:4000
Routing TableRoute Code-> Destination
94282..…… -> Send to PC 4001 (BSNL MSC)98382……. -> Send to PC 4005 ( BHARTI MSC)09…… -> send to PC 5000 (L-I TAX)
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)
PSTNCloud
BSNLMSC
(PC:4001)
BHARTIMSC
(PC:4005)
L-ITAX BSNL(PC:5000)
From LEX
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.
Routing and Charging of Mobile Calls in Pre MNP Scenario- Routing of calls from local Xge to L-II TAX
LEXPC: 2000
LEXPC: 2000
L-II TAXPC:4000L-II TAXPC:4000
PSTNCloud
SSTPSSTP
ssLEX
PC: 2000LEX
PC: 2000L-II TAXPC:4000L-II TAXPC:4000
PSTNCloud
SSTPSSTP SSTPSSTP
Routing and Charging of Mobile Calls in Post MNP Scenario- Routing of calls from local Xge to L-II TAX
Logical Connectivity of Exchanges with SSTP
Centralized Solution
NPAC
NPDatabase
Operator 1NP Database
NOperator 3NP Database
Operator 2NP Database
Operator 4NP 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
•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
Route Number Solution
Flow of RN from NPDB to PSTN Exchanges
NPDB
SSTP Cloud
PSTN Cloud
CCS-7 Links
RN
NPDBRN(BHARTI
GSM)=5555
C- 7 HSL connectivity
SSTPSSTP
LEXPC: 2000
LEXPC: 2000 L-II TAXL-II TAX
PSTNCloud
Physical Connectivity of Exchanges with SSTP in Post MNP and Call Flow
CH iCH iCH iC4 iCH iCH iCH iVoice Path
1. IAM message is tunneled through the permanent C-7 connection from L-II TAX to SSTP
BHARTIMSC
(PC:4005)
9444923456
C7 link
C7 link
Trunk Group
2. RN is retrieved by SSTP from NPDB
3. B number in IAM is replaced by RN+B4. Modified IAM is sent towards L-II TAX
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
7. MSC checks whether the RN is same as Home RN, if yes, call proceeds otherwise call is rejected
Nailed Up C7 Connection
SDCA-A SDCA-B
SDCA-C
LDCA
BSNL/Pvt. Operators
CMSP Network
SDCA-D
Local cum Tandem Exch.
Level-II TAX
BSNL PSTN
Network
Voice Path Signaling Path
Before MNP: Voice and Signaling Path for Fixed to Mobile Calls
SDCA-A SDCA-B
SDCA-C
LDCA
BSNL/Pvt. Operators
CMSP Network
SDCA-D
Local cum Tandem Exch.
Level-II TAX
BSNL PSTN
NetworkSSTP/LPDB
Voice Path Signaling Path
After MNP: Voice and Signaling Logical Path for Fixed to Mobile Calls
Note: The connectivity between local exchanges and SSTP may be established by creating NUC(Nailed Up Connections) at TAX.
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 I C-7 Traffic already shifted to SSTP Network
•All Level-II to Level II 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•No CMTS POI at Local Exchanges
Issues in CDR Billing Project
Solution Finalized:
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
IMPLEMENTATION OF MNP IN BSNL WIRE LINE NETWORK
• All PSTN switches in all Circles are also required to be complaint with MNP regime for Fixed to Mobile Calls.
• 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.• “IAM Relay” method is used for implementing MNP in BSNL.• The Scope of MNP implementation in Wire Line PSTN network covers following network
elements/platforms: a) Wire Line Switches for handling Fixed to Mobile Calls. b) Wire Line ILD Switches for handling Fixed to Mobile incoming ISD calls. c) Wire Line IN platform for handling Fixed to Mobile call for various IN Services e.g. VCC,FPH,FLPP etc.
NOTE ON IAM RELAY METHOD
• In IAM Relay method SSTP must intercept all IAMs for fixed to mobile calls originating from local exchanges and prefix the RN number with B party number in the IAM before sending the same to Level-I/II Taxs/Tandems.
• This RN+B number information used by Level I/II Taxs/Tandems to route the call to correct service provider.
• 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 ISD Incoming Calls to be terminated on Mobile Network.
• All ILD Gateways route their traffic to respective L1 Tax's via SSTP only.
• IAM of such calls will be relayed by SSTP after prefixing the appropriate RN+B number.
• Calls with RN+B will be analyzed by L1 Tax's and will be routed to respective MSCs.
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 can’t 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.
VCC(VIRTUAL CALLING CARD)
Origination customer has to be BSNL / MTNL only. Termination can be any operator customer. Customer dials 1802-425. SCP will play announcement to dial the card no. Once the 15 digit card no is entered and verified , announcement is played
to dial the destination No. Destination no dialed is 9449828818 which is a ported no in NPDB. CIC | | • SSP ----------- SCP--------- SSP ------ Tandem------ SSTP---------- TAX--- MSC 1802-425-15 digit Card no. 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).
FPH (Free Phone Call) Requirement. Originating customer can be any operator.
Terminating customer is only BSNL/MTNL
RN Value for BSNL – 5555
RN Value for MTNL – 4444
SSP ------------ SCP
Customer dials 1800-425-2222
SCP ------------ SSP
This 2222 is mapped to C-5555-9449828818 at SCP and forwarded to SSP. SSP will strip off C and forward rest of the digit to Tandem. ___________________CIC__________________________ | | SSP ------------ Tandem -------------- SSTP------------ TAX IAM (Called No-55559449828818) |----------------------------Signaling----------------------------------| SSP --------------------------------------- SSTP -------------- TAX ------- MSC IAM (Called No - 55559449828818) Now SSTP should be transparent to forward the same to the TAX, since RN is already prefixed by SCP.
UAN call within Local Exchange
Fixed Charging
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
top related