Mobile Number Port August, 2014
Safe Harbor THIS PRESENTATION IS INTENDED TO OUTLINE OUR GENERAL PRODUCT DIRECTION. IT IS INTENDED FOR INFORMATION PURPOSES ONLY, AND MAY NOT BE INCORPORATED INTO ANY CONTRACT.. IT IS CONTRACT I S NOT A COMMITMENT TO DELIVER DELI VER ANY MATERIAL, CODE, OR FUNCTIONALITY, AND SHOULD NOT BE RELIED UPON IN MAKING PURCHASING DECISIONS. THE DEVELOPMENT DEVELOPMEN T, RELEASE, REL EASE, AND TIMING OF ANY FEATURES FEATURES OR FUNCTIONALITY DESCRIBED DESCRIBED FOR ORACLE'S PRODUCTS REMAINS AT THE SOLE DISCRETION OF ORACLE.
Agenda
MNP Concepts and Terminologies
MNP Global Status
MNP Overal Architecture Architecture
EAGLE 5 MNP
MNP Routing Option
MNP Concepts and Terminology Terminology
What is Number Portability? Subscriber changes Wireline Service Provider while keeping its telephone number 55 5323-8970 SSP
Wireline Operator B
Wireline Operator A
55 5323-8970
SSP
PSTN
55 1010-7325
HLR
HLR
Wireless Wireless Operator Operator A B Subscriber changes Mobile Service Provider while keeping its mobile number
55 1010-7325
Number Portability Common Terminologies
The Directory Number (DN) is the telephone number entered when making a voice call or sending an SMS to a customer. –
In mobile network networks s DN=MSISDN DN=MSISDN
The Network that the customer is leaving is called the Donor network. network.
The Network that the customer is moving to is called the Recipient or Subscription network. network.
The Network that originating the call is called Originating Network
The Network that own the number is called Number Range Holder Network.
A Routing Number (RN) is a number assigned by a regulator to an operator to distinguish between different operators networks in the Portability environment.
Key Participants in a NP Domain How to route calls to the right subscription network? Transit Network Calling Subscriber
Originating Network
• Donor Network: Previously owns the number • Number Range Holder: Donor of the first porting, has been assigned the number range (NDC) the number belongs to. • Originating Network: Where call is originated • Recipient Network: Where the subscriber is presently served • Transit Network: Where signaling (possibly also the bearer channel) is transported prior to arriving at recipient Network
Donor Network
No longer Serve the Called Sub
No longer Number Range Holder Serve the
Called Sub
Recipient Network
Called Subscriber
Other Other importa important nt aspec aspects ts
IMSI IMSI addres addresses ses (SIM (SIM cards) cards) are are not porta portable ble.. – Each Each port ported ed sub subscri scrib ber gets gets a new SIM SIM card card from from the the
new new subs subscri cript ptio ion n netw networ ork k
MNP MNP allo allows ws port portin ing g of the the numb number er but but not not the the serv servic ice! e! – Cre Credits dits with ith the the don donor ope operato ratorr will ill be lost lost – Some Some serv serviices ces may may work ork dif differe feren nt fro from m one one ope operato ratorr to
anot anothe herr, e.g. e.g. acc acces ess s to voic voice e mail mail vices s may no lon longer work – Some service
Administrative Layer: De-Centralized Vs. Centralized
No central reference database Synchronization dependent on each operator Requires many connections between all operators OK for indirect routing
De-Centralized De-Centralized Solution Operator 1
Operator 2
NP Database
NP Database
Centralized reference database – Most countries Third party manages database and distributes to all operators Minimizes interconnections between operators
Centralized Solution Operator 1 NP Database
Operator 2 NP Database
NCH NP Database
Operator 3
Operator 4
NP Database
NP Database
Operator 3 NP Database
Operator 4 NP Database
Number Porting Process – General Flow Donor
Recipient
NP Order
Donor OSSGW
2) NPO transferred to DNO
3) NP Order Confirmation or Rejection
NP Order
Centralized
Recipient OSSGW
Number Portability Confirm
Management
Confirm
System Activation Time commences
Donor OSSGW
5) Service Disconnect Request
1) Number Port Order containing Authorization Info and Proposed Order Transfer Time
4) Number Port Order Approved and Order Transfer Time Confirmed
(CNPMS)
Disconnect
Connect
5) Service Connect Notice to ALL operators
All LSMS in the Country
The subscriber applies for Number Porting
5) Service Connect Notification
n o i t e a s i t a o h g P e N
Informs the customer that the Porting Time is confirmed
Recipient OSSGW The subscriber can switch the SIM Card or Phone
n o i e t s a a v h i t P c A
g e n i s t a r h o P P
Number Porting Process – Scenarios
Various Scenarios – Pre-validation (Optional) – Submission – Confirmation – Rejection – Cancellation – Activation – De-activation – Routing Info Distribution
Porting Activation Flow Control
12
Operators may worry that their IT System and Network will be overloaded during the
NPCH CNPDB Service Connect Service Disconnect RN Broadcast
P o r t A c t i v at at i o n W i n d o w OSSG WLSMS
Our strategies
RN Broadcast
LSMS OSSG WLSMS
– Port Activation Window(s)
configurable at the NPCH – Subscribers select the Port
Activation Window – NPCH allocates the orders
to the windows
s r e d r O t r o P
Activation Timeslot 1
Activation Timeslot 2
time
Activation Timeslot 3
Subscription Termination Process – General Flow Number Range Holder Network
Subscription (Recipient) Network • A Ported Subscriber terminates his service from the Subscription Network
Centralized Number
• Subscription Network disconnects the Number and retains the Number for X days
Portability Management
NRHN OSSGW
2) Number Returned to the NRHN
Number Return
System (CNPMS)
1) Number Port Order Termination Number Return containing the Subscriber Number and Termination Time
SN OSSGW
n o i t e a i s t a o h g P e N
Activation Time Window
All LSMS in the Country
3) Service Disconnect Notice to ALL operators
g e n s i t a r o h P P
Subscription Termination Termination Process – Scenarios
Various Scenarios – Submission – Confirmation – Rejection – Routing Info Distribution
Other Number Portability Processes
Routing Information Distribution – Real-time, Full DB, Partial DB – The process to ensure everybody are in synchronous of the
Ported Number and RN Mapping
Subscription Suspension Process – Optional process to terminate a subscriber if he does not pay after
ported out – The subscriber can be a prepaid or postpaid
Optional Advanced Processes – RN Audit, Active Reconciliation, Status Query, Query, Down-time Down- time
Notification, Reversal, etc
MNP Global Status
Worldwide Number Portability Deployment Status Fixed-Line NP Deployments UK
US Canada
France Germany
1996
1997
1998
Sweden Australia
Denmark
1999
2000
2001
2002
Hong Kong UK Holland Iceland
Spain Italy Switzerland
Sweden Australia Denmark Norway
Germany Belgium Portugal
Mobile NP Deployments
Taiwan
2003 France US Finland Ireland Greece
Worldwide Worldwide Numbe Numberr Portability Portability Timeline Timeline 2005 2005 - 2012 Fixed-Line NP Deployments Bahrain Columbia Dominican Rep. Ecuador South Africa Turkey
Hong Kong
Slovenia
Singapore
Brazil Mexico
2005
2006
2007
2008
2009
2010
2011
Croatia Estonia Latvia Luxembourg Malta South Korea Taiwan
Czech Rep. Israel Japan Oman Poland Saudi Arabia South Africa
Canada Egypt New Zealand Pakistan Romania
Brazil Bulgaria Macedonia Malaysia Mexico Singapore Turkey
Azerbaijan Bahrain Dominican Rep. Ecuador
Honduras Jordan Peru Thailand (China)
Albania Bahrain Colombia Ghana Georgia India Kenya Panama Serbia
Mobile NP Deployments
South Africa Thailand
India
Chile
2012 Argentina Belarus Cayman Is. Chile
In the the pr proc oces ess s
Implementing
Activities of some kind
– Azerbaijan
– Bangladesh
– Moldova
– Guatemala
– Nigeria
– Indonesia
Vend endor or sel select ection ion
– Kazakhstan
– Bahamas
– Philippines
– Costa Rica
– Russia
– Jamaica
– Venezuela
– Tunisia
– Vietnam – Ukraine
MNP Architecture
Number Portability Administrative Architecture Coordinate Number Portability Workflows Centrally
NPCH
Master Reference Database of Routing Info.
Operator Side NPGW
Central Side CNPMS
CNPDB
QNPDB
y t i v i t c e n n o C P I
Coordinate Number Portability Workflow within an operator
Query Number Portability DB e.g. HTTP, SOAP, ENUM, SIP, ITDB, …
OSSGW LSMS
SS7 / IP
STP from partners t e n a r t n I
QNPDB
Receive Routing Info from the CNPDB and provision the QNPDBs
Optional Centralized Query Box
CNPMS Centralized Number Portability Management System • NPCH – Number Portability Clearing House • CNPDB – Centralized Number Portability Database –
NPGW Number Portability Gateway • OSSGW – OSS Gateway • LSMS – Local Service Management System QNPDB Query Number Portability Database –
–
Administrative Infrastructure Overview Centralized NP Mgmtt Sy Mgm Syss NPCH
Query NPDB
CNPDB
A. Mobile Operators
LSMS
Live Live Query NPDB NPDB NPDB
OSSG W
BSS/OSS
Core Network
Console(s)
Disaster Recovery System Sync
ACQ
Vendor Specific Protocol(s)
ACQ
Data
B. International Gateways C. Fixed-line Operators
Vendor Specific Protocol(s)
NPCH CNPDB
API & Web
LSMS Console(s)
Data
Primary System Operation Centre (s)
Live Live Query NPDB NPDB NPDB
Query NPDB
Operator Gateway(s)
(Optional) Content Providers
Core Network
Typical Signaling Architecture Components Administrative Layer
Administrative Layer
Management Network CNPDB
Provisio Provi sionin ning g& Port process
Management System (LSMS)
Centralized NP Management System
Inter-Network Signaling
Signaling Network NPDB
MSC
Management System (LSMS)
Signaling Network NPDB
NPDB
SMSC
Operator 1
Network Routing Layer
ISUP SCCP SIP ENUM
Network Routing Layer
…
NPDB
MSC
Operator N
SMSC
EAGLE 5 MNP
EAGLE EAGLE 5 - Databa Database se Featu Features res –
– –
– – – – – – –
GSM Mobile Number portabilit y (Voice, SMS and MMS) G-Port – G-Port – (GSM SRF based MNP) – G-Port Circular Route Prevention – Portability Check for MO SMS – SMS MO NP – SMS MT NP GSM Fixed Number portability INP – INP – (INAP Based Number Portability) Prepaid IDP Relay – Relay – (MNP for Prepaid - GSM) ATI Query ISUP NP Triggerless Triggerless Number Portability Portability ATI Query ANSI Number Number Portability Portability A-Port (IS-41 SRF based MNP) NP Req (WIN Based Based Number Portability) Portability) ANSI NP Prepaid Relay – (MNP for Prepaid – Prepaid – IS-41) Analyzed Info Relay – G-Flex – G-Flex – (IMSI or MSISDN Router) EIR – EIR – (Equipment Identity Register)
HLR 1
HLR N
… Eagle 5 DB
MSC/ SSP
STP with integrated database functions NP Portability Status Exchange with OLOs e.g. via central database
Intelligent Network Layer Data Provisioning System
HLR
SCP
VMSC
Eagle 5
Eagle 5
DB
DB
Signalling & Network Intelligence Intelligence Layer
BSC
Subscriber
MSC
MSC SSP Base Station
Subscriber
Other Networks
EAGLE 5 Provisioning Application Processor: EPAP EPAP
A database provisioning provisioning system system that maintains maintains a subscriber subscriber database database for support of query processing of the subscriber management and number portability applications EPAP interfaces with: • A customer customer NP provisioning system if NPDB is to be administered administered directly by the customer; or • An LSMS if NPDB is to be administered by a centralized NP Administration Centre
Database Replications
EPAP EPAP Processing Processi ng Capacity Capa city
Database Capacity • Up to 120M individual DN entries • Up to 50,000 range DN entries
Throughput • Supports 25+ Provisioning System Updates/sec • Supports 250+ Provisioning System reads/sec
Support Multiple EAGLE 5s • Automatic provisioning synchronization up to 12 EAGLE 5 nodes
Rout Routin ing g Opti Option ons s
Routing Options
Indirect Routing (Onward Routing) –
Routing via number range holder
–
Sometimes referred to as “Onward Routing”
–
Operator database only holds imported and exported numbers
–
Does not require All Call Query (ACQ)
Direct Routing –
Calls and MSUs are transferred directly f rom origination to subscription network without involvement of the Number Range Holder network
–
Operator database need to hold all ported numbers
–
Requires All Call Query
Indirect Routing NPDB
NPDB
ISUP IAM
Originating network
NPDB
Subscription network
Number Range Holder network
Direct, Indirect, Partially Direct Routing, Call to Own Number Originating Network A = Subscription Network HLRA
SRI (MSISDN) CdPA=HLRB or 3 MSISDN CgPA=GMSCA
Eagle SRI (MSISDN) 5 CdPA=MSISDN, G-Port 2 CgPA=GMSCA 1
IAM (MSISDN)
GMSCA
4
SRI ack (MSRN) CdPA=GMSCA CgPA=HLRA
5
IAM (MSRN)
If the subscriber number is part of the own number range and the number has not been ported, the call is handled inside the originating network
Indirect Routing, Call to Ported-in Number Originating Network A = Subscription Network
Number Range Holder Network
HLRA
SRI (MSISDN)
7
HLRB
SRI ack (MSRN=MSISDN) 8
Eagle 5 SRI G-Port ((RN+)MSISDN)
SRI (MSISDN)
3
6
1
IAM (MSISDN)
GMSCA
Eagle 5 G-Port
SRI ack (MSRN=RN+MSISDN) 4 CdPA=GMSCB CgPA=HLRB
2 IAM (MSISDN) 5 IAM (RN+MSISDN)
GMSCB
9IAM (MSRN)
If the subscriber number is not from the own number range, the originating network routes the call to the number range holder network
The range holder network performs a MNP check and routes the call back to the origination network
This effect is known as tromboning
Indirect Routing, Call to Non Ported Number Originating Network A
Number Range Holder Network = Subscription Network HLRB
SRI ack (MSRN)
SRI (MSISDN) 4
5
SRI (MSISDN) 1
IAM (MSISDN)
GMSCA
2
IAM (MSISDN)
Eagle 5 G-Port 3
GMSCB
6
IAM (MSRN)
If the subscriber number is not from the own number range, the originating network routes the call to the number range holder network
The Number Range Holder Network determines that it is the current subscription network and handles the call inside the network
Indirect Routing, Call to Cross-Ported Number Number Range Holder Network B
Originatin g Network A
Subscription Network C
HLRB
SRI (MSISDN) 1
GMSCA
IAM (MSISDN)
2
IAM (MSISDN)
Eagle 5 G-Port 3
GMSCB
HLRC
SRI (MSISDN) 7 SRI ack (MSRN= RN+MSISDN) 4 Eagle 5 SRI G-Port ((RN+)MSISDN) 6 5
IAM (RN+MSISDN)
SRI ack (MSRN) 8
9
GMSCC
VMSCC
IAM (MSRN)
If the subscriber number is not from the own number range, the originating network routes the call to the number range holder network The Number Range Holder Network determines the current subscription network and forwards the call to the network
Direct Routing NPDB
NPDB
Originating network
Number Range Holder network
ISUP IAM
NPDB
Subscription network
Direct Routing, Call to Ported-in Number Originating Network A = Subscription Network HLRA
SRI (MSISDN) 3
SRI ack (MSRN) 4
SRI (MSISDN) 1
IAM (MSISDN)
Eagle 5 G-Port 2
GMSCA
5
VMSCA
IAM (MSRN)
The originating network performs a MNP check
If the subscriber number is an own customer, the call is handled inside the network
Direct Routing, Call to Non Ported Number Originating Network A
Number Range Holder Network = Subscription Network
HLRA
HLRB
SRI (MSISDN) 6 7
SRI ack (MSRN=MSISDN) Eagle 5 G-Port SRI (MSISDN) 2 1
IAM (MSISDN)
GMSCA
3
SRI (MSISDN) 4
IAM (MSISDN)
SRI ack (MSRN)
Eagle 5 G-Port 5
GMSCB
8
VMSCB
IAM (MSRN)
The originating network performs a MNP check and determines the current subscription network
If the subscriber number is not an own customer, the call is routed to the subscription network
Direct Routing, Call to Cross-Ported Number Originating Network A
Subscription Network B ≠ Number Range Holder Network
HLRA
HLRB
SRI ack (MSRN)
SRI (MSISDN) 6 SRI ack (MSRN=MSISDN)
SRI (MSISDN) 1
IAM (MSISDN)
Eagle 5 G-Port
3
SRI ((RN+)MSISDN)
2
GMSCA
4
IAM (RN+MSISDN)
7
Eagle 5 G-Port 5
GMSCB
8
VMSCB
IAM (MSRN)
The originating network performs a MNP check and determines the current subscription network
If the subscriber number is not an own customer, the call is routed to the subscription network
EAGLE5 signaling approach
NP Product Family
ITU Based NP solutions – Inter-Carrier NP Solutions (Service Provider Portability)
–
GSM G-Port Mobile Number Portability (G-Port (G-Port): ): applicable to the GSM networks. ANSI-41 A-Port MNP (A-Port (A-Port): ): applicable to TDMA/CDMA networks INAP-based Number Portability (INP (INP): ): applicable to GSM/IS41 network and/or ITU based fixed-line networks.
Intra-Carrier NP Solution
IS41->GSM Migration: Migration: Support number portability –
–
Triggerless NP Solution Solution using ISUP
when an operator migrate its TDMA/CDMA networks to GSM or vice-versa
ISUP Triggerless Triggerless NP (based on intercept of ISUP IAM)
North America NP solution –
Local Number Portability (LNP): applicable to North America fixed-line and wireless GSM, TDMA and CDMA networks
GSM Portability : G-Port
Service Provider Portability deployed in GSM networks Subscribers change operators while retaining their MSISDN numbers
Based on Signaling Relay Function (a triggerless solution) defined in 3GPP TS 23.066
Intercepts MAP messages already flowing in network, thus creating minimum disruption to existing deployed network elements Requires GTT
–If a number is p o r t ed e d o u t and the message is call-related, G-Port G-Port acts as an “NP HLR,” by
responding to the switch with a MAP SRI ACK message. –If a number is n o n - p o r t e d or p o r t e d -i -i n , G-Port performs an HLR translation and forwards the
translated message to the destination HLR.
MT to Non-ported or Imported Number Originating Network
Recipient Network
HLRB SRI (MSISDN) CdPA=HLRB or MSISDN CgPA=GMSCB
2
3
G-Port SRI (MSISDN) CdPA=MSISDN, TT=SRI CgPA=GMSCB
SRI ack (MSRN) CdPA=GMSCB CgPA=HLRB
1
4
GMSCA
IAM (MSRN)
VMSCB
MT to Ported Out Number
Originating Network
Recipient Network
G-Port SRI (MSISDN) CdPA=MSISDN, CgPA=GMSCA
1
2
GMSCA
SRI ack (RN + MSISDN) CdPA=GMSCA CgPA=G-Port_MNP
3
IAM (RN+MSISDN)
GMSCB
INAP-based Portability: INP A Trigger Based Solution
EO/MSC needs to be IN-equipped to detect IN triggering so that IN queries can be sent to external network nodes for NPDB lookup
Trigger detection can be initiated from an Originating, Transit, Transit, Donor, or Subscription network
NP Server performs NPDB lookup based on the Called Party Number populated in I NAP IDP to determine if the number is a ported port ed number –
If exported subscriber, NP Server returns a routing number
–
If non-ported or imported, NP server instructs the EO/MSC to handle the call as it is
Handling of non-call related messages is based on the SRF funct ion as defined in 3GPP TS23.066
Supports “triggered” solution based on Intelligent Network Application Protocol (INAP) InitialDP message (IDP), defined by ITU Series Q and Supplement 2
INAP – Feature highlight
Supports “triggered” INAP (Intelligent Network Application Application Protocol), defined by ITU Q. Series of specifications on TCAP/IN as well as supplement 2 Handling of non-call related messages EO/MSC needs to be IN-equipped to set IN trigger points to detect messages that require NPDB lookup Trigger detection can be initiated from an Originating, Transit, Donor, Donor, or Subscription network INP may be used for several purposes – NP in Fixed Networks (Operator and Geographical NP) – MNP database query in fixed networks for direct routing – FNP database query in mobile networks for direct routing – Call related scenario in MNP (ACQ, QoD, QoHR)
Call Flow for IN Based Solution For call related messages only 2. INAP IDP Query 1. incoming call
NP Server
EO/MSC
NPD B
3a. INAP Connect 3b. INAP Continue
EO/MSC receives an incoming call and detects an IN trigger
EO/MSC sends NP Server an INAP IDP to query routing instructions instructions
NP Server performs NPDB lookup to determine if the called party is a ported number: 3a. If ported ported,, NP Server Servers s retur returns ns an INAP INAP Connec Connectt Mess Message age with with Routin Routing g Number 3b. If not ported, NP Server returns an INAP Continue (or a CONNECT) Message to route the call as is
Trigger riggerles less s ITU ISUP ISUP NP
Intercept ISUP IAM message and perform NPDB lookup to determine portability status of t he Called Party Number encoded in the IAM
Include portability information information (RN or SubNet ID) in the IAM message prior to forwarding the message to its intended destination
Sample Applications: –
Upon receipt the modified IAM message from the EAGLE 5, the recipient switch (e.g., MSC) populate the portability information in an INAP IDP message when querying a prepaid node
– A recipient recipient switch can redirect the modified IAM based on the portability information encoded in the
IAM message
Signaling approach in detail
Affected Services: Mobile Terminating Calls GSM Solution
INP Call to Non-ported (or Ported-in Number) Originating Network
Terminating Network
NPDB
InitialDP 1
2
Continue
SSP could be in a different network Switch
3 IAM
Return INAP Continue Message
Switch
INP Call to Ported(-out) Number Originating Network
Terminating Network
NPDB
InitialDP
1
2
Connect DRA = RN+DN
Switch
3
Switch
IAM (RN+DN)
Return INAP Connect Message
Destination Routing Address Address (DRA) = RN+DN, Operator can provision to send the RN only
INP Call related scenario in MNP (ACQ) Call to Non-Ported Number MSC
HLR
Eagle 5 INP
B IDP (CdPN=B) A CONTINUE SRI (CdPA=B)
SRI (MSRN).
•
INP imposes an additional dialog, which increases
The call setup delay
the CPU usage at MSC
The required number of links, …
G-Port MNP (call related) – Signalling Relay Function (SRF) MSC
HLR
Eagle 5 G-Port
B SRI (CdPA=B) A
SRI (B) SRI (MSRN). IAM (MSRN)
› › ›
The SRF based MNP solution uses existing SRI dialog The SRI message is relayed to the respective HLR for imported an d own subscribers Same principles may be applied to regular own subscribers → MSISDN based Flexible Routing is an integral part of G-Port
G-Port MNP (call related) Signalling Relay Function (SRF) MSC
Eagle 5 G-Port
B
A
HLR
SRI (CdPa=B)
SRI (MSRN=RN+B)
IAM (RN+B)
›
The SRI message is answered (MAP termination function) if exported or non ported f or differentiated billing → MSC should add MSRN to the CDRs to allow for
Call to a ported number – Query on ISUP Release
MSC
GMSC
GMSC @OLO
HLR Eagle 5 G-Port
1. IAM (CdPN=MSISDN)
Call is routed As if there is No MNP MSC triggers an IDP
2. IAM (CdPN=MSISDN) 3. REL (Cause=14)
Call is Released, Number is Ported to OLO
4. IDP (CdPN=MSISDN)
5. CONNECT (DRA=NRN+MSISDN
MSC routes the call To the respective OLO
6. IAM (CdPN=NRN+MSISDN)
INP finds an entry, which points to a OLO and sends back a CONNECT
INP – QoHR (Query on HLR Release)
MSC B
A
HLR
Eagle 5 G-Port
SRI (CdPA=B)
Unknown Subscriber IDP (CdPN=B) CONNECT (DRA=RN+B) IAM (RN+B)
Summary Mobile Terminated Calls
SRF is the preferred solution – Least Intrusive – Limited Overhead – Implemented in numerous operators
Query on Release – Very efficient and low overhead as long the number of ported subscribers is
low – Issues:
Release with specific Release Cause Value Value may be a problem
Delay
– Has been implemented in Poland
Trigg riggerless erless ISUP based based solutions solutions All digital networks
Triggerless Number Portability
How How does does it work? ork? –
Eagle 5 intercepts intercepts ISUP IAM IAM messages
–
Extrac Extracts ts the CdPN CdPN
–
Does Does a databas database e search search
–
Pref Prefix ixes es the the CdPN CdPN if the the numb number er is port ported ed
Switch
602 123456
A
Eagle 5 SAS
Transit Switch
Switch @SN
IAM (602123456) IAM (RN 602123456) IAM (RN 602123456)
Triggerless Number Portability Advantages
Does not require an additional dialog to resolve number portability – Low delay – No additional CPU requirements at the switch – No additional protocol requirements at the switch, e.g.
INAP – Does not use up triggerpoints that may be required for
other applications
Triggerless Number Portability Limitations
Eagle 5 cannot change the first leg of the bearer channel – I.e., calls may be routed via the number range holder (NRH) network
NRH does not have to perform NP database check Possibly not allowed by regulation Switch
Eagle 5
Switch @NRH
Switch @SN
602 123456
A
IAM (602123456)
IAM (RN 602123456)
IAM (RN 602123456)
Triggerless Number Portability Possible Workaround: ISUP Loop
Rout Route e call calls s on a loop loop via via the the Eagl Eagle e5 – If the the numb numbe er is ported rted,, a RN is inse insert rted ed – If the the numb numbe er is not port ported ed,, the the IAM IAM is rou routed ted back ack
unchanged
Draw Drawba back ck:: Incr Increa ease ses s the the work worklo load ad at the the swit switch ch Switch
Eagle 5
602 123456 IAM (602123456) A IAM (RN 602123456)
IAM (RN 602123456)
Switch @SN
Possible Workaround: Reroute on RELEASE
Route calls to the Eagle 5 ISS – If the number is ported, the t he Eagle 5 ISS returns ret urns a REL containing the routing number and subscriber number in the redirection number parameter – If the number is not ported, route the ISUP message to the next switch Drawback: Some switches do not support this part of the ISUP specifications In service in Mexico Switch
602 123456
A
Eagle 5 ISS
IAM (602123456) REL (RN 602123456)
IAM (RN 602123456)
Switch @SN
Possible Workaround: Combined Solution
Combined Triggered and Triggerless Solution – Triggerless where you can – Triggered where you have to
Circular Route Prevention
Circular Route Prevention
Problem – Circular routing can occur due to incorrect information in one or more of the
number portability databases. – For example, network A has the correct routing information, indicating that the subscriber now belongs to network B. But network B may have the incorrect (old) information, indicating that the subscriber belongs to network A.
Effects – Calls are looped around between the donor and subscription networks
Solution – G-Port Circular Route Prevention (SRF solution) – TIF Circular Route Route Prevention (Triggerless (Triggerless ISUP solution) solution) – INP Circular Route Prevention (Triggered INAP solution)
G-Port MNP Prevention of Circular Routing Originating Network A
Network B
HLRA
HLRB
SRI ack (MSRN=MSISDN) Eagle 5 G-Port SRI (MSISDN) 2 1
IAM (MSISDN)
3
Eagle 5 SRI ((RN+)MSISDN)G-Port CdPA=RN+MSISDN, 5 CgPA=GMSCB
GMSCA 4 IAM (RN+MSISDN)
6
UDTS
GMSCB
Network A determines Network B as the subscription network for a given MSISDN and forwards the call to it
Network B determines that the MSISDN is not an own subscriber and returns an error
On receipt of an SRI message. If a home RN is appended to the message; then the Eagle examines the DN before performing NPDB lookup as following: –
If DN is of a Ported-out number -> Circular Route conditions identified
–
If DN is of a Ported-in number -> The Eagle relay the message to HLR
INP Prevention of Circular Routing (In Network B) Originating Network A
Network B
HLRA
HLRB
SRI ack (MSRN=MSISDN) Eagle 5 G-Port SRI (MSISDN) 2 1
IAM (MSISDN)
3
Eagle 5 INAP IDP INP CdPN=RN+MSISDN, 5 CgPA=GMSCB
GMSCA 4 IAM (RN+MSISDN)
6
INAP RELEASE CALL Provisiona Provisionable ble RCV
GMSCB
Network A determines Network B as the subscription network for a given MSISDN and forwards the call to it
Network B determines that the MSISDN is not an own subscriber releases the call
On receipt of an INAP IDP message. If a home RN is appended to the CdPN; then the Eagle examines the DN before performing NPDB lookup as following: –
If DN is of a Ported-out number -> Circular Route conditions identified
–
If DN is of a Ported-in number -> The Eagle replies with CONNECT operation
TIF NP Prevention of Circular Routing (In Network B) Originating Network A
Network B
HLRA
HLRB
SRI ack (MSRN=MSISDN) Eagle 5 G-Port SRI (MSISDN) 2 1
IAM (MSISDN)
GMSCA
3
4 IAM (RN+MSISDN) 5 RELEASE
Eagle 5 TIF
GMSCB
Network A determines Network B as the subscription network for a given MSISDN and forwards the call to it
Network B determines that the MSISDN is not an own subscriber releases the call
On receipt of an ISUP IAM message. If a home RN is appended to the CdPN; then the Eagle examines the DN before performing NPDB lookup as following: –
If DN is of a Ported-out number -> Circular Route conditions identified
–
If DN is of a Ported-in number -> The Eagle forwards the call to the GMSC
Affected Services: Prepaid GSM Solution
MNP Effect on Prepaid
Main Problem: Differentiated On-Net/Off-Net On-Net/Off-Net Charging
Prepaid IN needs subscription network information in real time
Prepaid Considerations
Signalling in a Portability environment is further complicated when we consider Pre-paid subscribers
Before any call is originated for a Prepaid subscriber the IN SCP is checked to ensure that the caller has enough credit to make the call
This credit check is normally performed using an INAP or CAMEL query (IDP) to an SCP (IN Node)
It is common for network operators to charge different rates if a subscriber is calling another network subscriber.
In this instance the SCP must be able to determine the subscription network of B-number to apply the corresponding rate. This requires the NP status of the B-number be known by the SCP.
Prepaid Number Portability Solution
There are 3 basic methods defined to provide the NP status to the SCP: IDP Relay, SRI Query Qu ery & ATI ATI Query Que ry
IDP Relay involves sending the existing IDP dialogue via the NPDB so that the B-number can be modified to include the NP status
ATI ATI or SRI Query involve the Pre-paid SCP interrogating the NPDB to determine the NP status after an IDP has been received IDP Relay is the most efficient since it does not require additional triggers on the SCP (i.e. no costly upgrade)
Prepaid Credit Check 2 NPDB 3
1
ISUP IAM
IDP Relay
2 NPDB
3 1 4
SRI or ATI Query
ISUP IAM
Mobile Originated call to a non-ported number or Imported OLO number
MSC
PPPPSCP
Eagle 5 G-Port
MSISDN
A
1. IDP (CdPN=MSISDN)
Eagle 5 ISS intercepts the IDP and prefixes the CdPN 2. IDP (HLR-ID+MSISDN)
3. CONNECT (DRA=HLR-ID+MSISDN)
4. SRI (MSISDN=MSISDN)
HLR
Mobile Originated call to a exported, foreign ported or non-ported OLO number
MSC
Eagle 5 G-Port
MSISDN
A
1. IDP (CdPN=MSISDN)
Eagle 5 ISS intercepts the IDP and prefixes the CdPN 2. IDP (CdPN=RN+MSISDN)
3. CONNECT (DRA=RN+MSISDN)
The call is setup to the respective network operator 4. IAM (CdPN=RN+MSISDN)
PPPPSCP
ATI Inte Interfac rface e at Eagle Eagle
Eagl Eagle e can also also prov provid ide e an ATI int inter erfa face ce for for MNP MNP Quer Query y
Depe Depend ndin ing g on IN vend vendor or and and impl implem emen enta tati tion on the the easi easier er solu soluti tion on – Standards based – No depen dependen dencie cies s on INAP INAP or CAME CAMEL L interf interface ace
Could be used in addition to or instead of IDP Relay
Ported-out or Cross-Ported subscriber Originating Network A
SCP 1. ATI (MSISDN) 1. SRI (CdPA=MSISDN, TT=9) 2. ATI_Rsp (RN+MSISDN) 2. SRI_Ack (MSRN=RN+MSISDN)
Eagle 5 G-Port
Ported-in subscriber Originating Network A
SCP 1. ATI (MSISDN) 1. SRI (CdPA=MSISDN, TT=9) 2. ATI_Rsp (HLR-Id+MSISDN) 2. SRI_Ack (MSRN=HLR-Id+MSISDN)
Eagle 5 G-Port
Non-ported own subscriber Originating Network A
SCP 1. ATI (MSISDN) 1. SRI (CdPA=MSISDN, TT=9) 2. ATI_Rsp (MSISDN) 2. SRI_Ack (MSRN=MSISDN)
Eagle 5 G-Port
Non-ported foreign subscriber Originating Network A
SCP 1. ATI (MSISDN) 1. SRI (CdPA=MSISDN, TT=9) 2. ATI_Rsp (Prefix+MSISDN) 2. SRI_Ack (MSRN=Prefix+MSISDN)
Eagle 5 G-Port
SMS & MMS
G-Port MNP (non-call related) SMSC SMS to B
SCCP GW OLO
SRI_for SM (CdPA=B)
A
›
HLR
Eagle 5 G-Port
1. CdPN is own Subscriber
SRI_for SM (CdPA=B)
2. CdPN is not own subscriber
SRI_for SM (CdPA=RN+B)
Non-call related messages are ar e relayed, e.g. HLR query que ry for SMS delivery,
to the respective network element for imported and own subscribers
to the SCCP gateway at the respective operator if exported or non ported
MNP Check for Mobile Originated SMS
Problem – Ported out subscribers reprogram their handsets handsets to continue using
previous operator Short Message Service Center – Number range check does not work any more
Effects – Revenue lost for the operator by providing the service without being able
to charge it
Solution – Tekelec’s “MNP Check for Mobile Originated SMS” Solution
Portability Check for Mobile Originated SMS MSC
Eagle 5 G-Port
MO_FSM
A
MO_FSM
SMSC
IF A is an own customer Forward SMS to SMSC MO_FSM
MAP Error
IF A is not an own customer Filter SMS and return error
Protects own SMSCs from misuse Avoids MNP database at the SMSCs
ITU NP support for MO-SMS
MSC
Eagle 5
SMSC
SMS NP
MO_FSM
A
SCP/ RI
MO_FSM MAP Error
IF A is an own cus tomer •Forward SMS to SMSC •Prefix B-Number MO_FSM MAP SM UI=RN+B CR (RN+B)
IF A is not an own customer Filter SMS and return error
› Protects own SMSC from misuse › Allows for On-net/Off-net charging › Avoids MNP database at the SMSCs SMSCs › Avoids additional dialog to dip NPDB
Ack SRI_for_SM (SCCP CdPA=RN+B, MAP MSISDN=B)
SCCP GW OLO
Portability Check for Mobile Originated SMS (HLR based) MSC
HLR SMSC
SCP/ RI
MO_FSM
A
MO_FSM SRI_for_SM/ATI SRI_for_SM/ATI (A) Ack (A) SRI_for_SM/ATI SRI_for_SM/ATI (B) Ack (RN+B) CR (RN+B) Ack
Two additional database queries If SRI_for_SM Query is used, the MSU may also have to be relayed to the respective subscription network
Thank you
Q&A
Contact me:
[email protected]
