Академический Документы
Профессиональный Документы
Культура Документы
9420023456 PSTN
9420023456
HLR HLR
Wireless Wireless
Operator A Operator B
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.
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
PSTN
Voice and Signaling path Cloud
LEX L-II TAX
PC: 2000 (Associated Mode) PC:4000
Routing Table
Routing Table Route Code-> Destination- Signaling Point Code
Route Code -> Destination
94282.. -> Send to PC 4001 (BSNL MSC)
9.. ->PC 4000 98382. -> Send to PC 4005 ( BHARTI MSC)
09. ->PC 4000 09 -> send to PC 5000 (L-I TAX)
Charging Table
Charging Table
Route Code -> Charging
Route Code -> Charging 94282.. ->Charging Defined(intra operator-intra circle)
98382.. ->Charging Defined(inter operator-intra circle)
9.. -> by Next Higher Xge 094500. -> Charging Defined (inter Circle- intra operator)
09. ->by Next Higher Xge 099567. -> 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
Routing Table
Route Code-> Destination BHARTI
MSC
94282.. -> Send to PC 4001 (BSNL MSC) (PC:4005) PSTN
98382. -> Send to PC 4005 ( BHARTI MSC) Cloud
09 -> send to PC 5000 (L-I TAX)
Issues:
Issues:
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:
PSTN
LEX L-II TAX Cloud
PC: 2000
PC:4000
SSTP
PSTN
LEX L-II TAX Cloud
PC: 2000
PC:4000 s
SSTP SSTP
Route Number Solution
Centralized Solution
Operator 1 Operator 2
NP Database NP Database
NPAC
NP
Database
Operator 3 Operator 4
N
NP Database NP Database
Each Operator has been given two unique 4 digit Number( one for GSM and
one for CDMA operator) called Routing Number(RN)
SSTP Cloud
CCS-7 Links
RN
PSTN Cloud
NPDB
Physical Connectivity of Exchanges with SSTP in Post MNP and Call Flow
PSTN
7. MSC checks whether Cloud
the RN is same as Home
RN, if yes, call proceeds
otherwise call is rejected
Before MNP: Voice and Signaling Path for Fixed to Mobile Calls
SDCA-B
SDCA-A
BSNL/Pvt.
Operators
CMSP
SDCA-C Network
SDCA-D
Level-II
Local cum TAX
Tandem Exch.
BSNL PSTN
Network
LDCA
Voice Path Signaling Path
After MNP: Voice and Signaling Logical Path for Fixed to Mobile Calls
SDCA-B
SDCA-A
BSNL/Pvt.
Operators
CMSP
SDCA-C Network
SDCA-D
Level-II TAX
Local cum
Tandem Exch. BSNL PSTN
SSTP/LPDB Network
LDCA
Note: The connectivity between local exchanges and
SSTP may be established by creating NUC(Nailed Up
Voice Path Signaling Path Connections) at TAX.
Prerequisites
Post MNP, RN Information will be available only in L-II /L-I TAX s not in
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
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
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
Interaction with HO
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 method requires connecting all the local exchanges with SSTP.
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.
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.
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.