You are on page 1of 38

Huawei MNP Solution

11 Apr 2008
www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.


Contents

MNP overview

Huawei MNP Solution

Interconnection with NPAC and core


network elements

Case Study
Growing MNP Trend
Year Regions introducing MNP
Regions introducing MNP

(many of them adopting signaling solution)
(many of them using signaling solution)
50
1997 Singapore
45
1999 UK, Netherlands, Hong Kong
40
2000 Spain, Switzerland

35 2001 Sweden, Denmark, Norway, Australia

30 2002 Belgium, Germany, Italy, Portugal

25 2003 Finland, Luxembourg, Ireland, France

Greece, Australia, Slovenia, Cyprus, Lithuania, Poland, Hungary, USA,


20 2004
South Korea

2005 Estonia, Latvia (planed), Malta (31 July 2005)


15
2006 Morocco, Jordan, South Africa, Japan
10
2007 Pakistan, Brazil, Mexico…
5


2008 India, Thailand, Malaysia, Turkey, Russia…
0
1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 Y
Year
ear Sources: Own inquiries, EEC

“In
In the interest of developing and sustaining competition in the telecommunications sector, all
subscribers should be able to benefit from number portability”
-------Article
Article 30, EC Directive 2002/22/EC on Universal Service and Users’ Rights
MNP-SRF --- Most Cost--Efficient MNP Solution

$ On-switch
switch
Average cost

IN
MNP-SRF
solution
Trigger Yes No
requirement
Switch
Upgrade for NP Yes No
query
Call related Yes Yes
NP service
IN solution Non-Call
related NP No Yes
service
MNP-SRF
SRF

Number of Porting

On-switch --- Based on the call forwarding function


IN solution (sever solution) --- NP query is implemented on the IN platform
MNP-SRF --- NP query is implemented on the STP by the signaling relay function
MNP Subscriber Categories

Regular-Own:
Own: An own subscriber is still with own network
Regular-Foreign
Foreign : An Other Mobile Operator (OMO) subscriber is
still in the original number range holder network
Port-In:
In: An OMO subscriber ported in own network
Port-Out:
Out: An own subscriber ported out to OMO
Cross-Ported:
Ported: OMO subscriber ported out to another OMO
network
75% of Operators Adopt ACQ Solution

• Simple routing flow


Call Routing
• Save all NP user data Year Country
Method

Number 1997 Singapore Onward routing


DB Number
Porting New Porting United
DB Onward routing
Kingdom
New SP 1999 Hong Kong ACQ
SP 4
3 Netherlands ACQ
Old
1 2 Old
Orig. SP Spain Onward routing
SP 2 release w/o # 2000
Orig. Switzerland Onward routing
1 Donor Denmark ACQ
2001 Norway ACQ
All Call Query (ACQ) Query On Release (QoR) Sweden ACQ & QoR
Belgium ACQ & QoR
Number Number
Porting Porting Germany ACQ
2002
New New Portugal ACQ & QoR
SP SP Italy Onward routing
Old Old
4 France ACQ & QoR
SP SP
Orig. 3 2003 Ireland ACQ & QoR
Orig.
Finland ACQ
3 release w/t # 1 DB
1 Donor 2 USA ACQ
Donor 2 DB 2004
Austria ACQ

Dropback Onward Routing Estonia ACQ


2005
Lithuania ACQ
Contents

MNP overview

Huawei MNP Solution

Interconnection with NPAC and core


network elements

Case Study
E2E NP Solution Overview

Central
National NPDB Clearing
Layer House

SOAP/XML

SOAP/XML
MNP Provisioning LSMS
Layer
BOSS/Cares Donor Operator
BOSS/Cares

NP Routing SG7000
Process Layer

Service Process
Layer
MSC HLR SCP SMSC MMSC

Benefit:
l Abundant NP solution including MNP-SRF,
SRF, IN-based,
IN ISUP-triggerless, SIP-based
l End to End NP solution including STP&NPDB and LSMS

l Low query delay based on the embedded memory NPDB


Supported Standards

Organization Standards
GSM03.66 < Support of Mobile Number Portability (MNP), Technical Realization >
GSM02.66 < Support of Mobile Number Portability (MNP), Service description >
ETSI GSM09.78 < CAMEL Application Part (CAP) specification >
GSM09.02 < Mobile Application Part (MAP) specification >
INAP Capability Set 1 (CS1)
INAP Capability Set 2 (CS2)

3GPP TS23.066 <Support of Mobile Number Portability (MNP), Technical Realization >
TS22.066 < Support of Mobile Number Portability (MNP), Service description >
TS29.078 < CAMEL Application Part (CAP) specification >
TS29.002 < Mobile Application Part (MAP) specification >

ANSI TIA/EIA-41-D
Overall Application

GSM
MNP

FNR
CDMA
MNP
Full NP
Solution
LNP
C-G
MNP
2G-3G
MNP
SG7000 Capacity of Query & Data Storage

NP query E1/T1 FE NP query


Interface Interface Ability of NP query Capacity of NP
data storage
E1/T1 Interface Unit FE Interface Unit

u Each SBPU board


supports ability of query : u Support 50 million
Switch network
2560 times/sec users
u Cross delay:< 30ms
u Support 189(number u Capacity up to 200
of SBPU board)×2560 million subscribers
NPDB NPDB smoothly
= 484,000 times/sec

Signaling Process Unit Signaling Process Unit

Full distributed structure:: NP data query & protocol processing are in the same unit.

Advantage: Lower query delay than external NPDB & excellent performance
Distributed system ensures smooth expansion and reliability
Released 作者:
Ready XXX
for Contract
Planned Planning
Huawei Signaling Solution Roadmap commercially not binding
SG7000 V200R003 SG7000 V200R005
~ SG7000 V200R001 SG7000 V200R002 ------------------- -------------------
SANEX V100R001 SANEX V100R002
SRS V100R001 SRS V100R002

FUNCTIONS FUNCTIONS FUNCTIONS FUNCTIONS


l Signaling service l Signaling service
l Signaling service u Preferred Roaming l Support IMS architecture
u FNR
SMS IN bypass function u International seamless
u Signaling Firewall u u ENUM server & NP
Gateway Roaming service
u Voice IN bypass function Enhanced LSMS for ENUM
u Call filter u
u Signaling load-sharing
u Routing redirection
l Signaling Monitor function server & NP
u Signaling Accounting
(SANEX)
u SMS router l Signaling service
u Enhanced Signaling Load- u CDR/TDR
u SMS MO Authentication
u Signaling Monitor Data Mining
u IMEI Catch (TIC)
sharing u
u Call Trace
u White & Black list
u Enhanced Signaling
u ANSI ITU conversion Accounting
l NP dipping function
l NP function u KPI real time Monitor
u GSM, CDMA, C-G MNP
l Intelligent report u Integrated Statistic Analyze

u LNP l IP Signaling Network Qos l NP function


u
u MNP-SRF, IN-based,
detection LNP enhancement
ISUP trigger-less NP (SIP/ISUP/INAP)
u LSMS l SUA
l IP Signaling Network reliability
enhancement
CAPACITY / CAPACITY / PERFORMANCE CAPACITY / PERFORMANCE
PERFORMANCE l 25M NPDB and FNR number CAPACITY / PERFORMANCE
l 200M NPDB and FNR number
l 6048 64K links l 4000 SCTP Associations (*)
l 756 HSL l 50M NPDB and FNR number
l 1000 SCTP Associations l IP Signaling Network
l 12M NPDB and FNR performance enhancement
number
l 3800 k MSU/s
l 1800 k GTT/s
~ 2005 2006 2007Q3 2008Q2 (2008/05) 2009Q4
(*) this feature will be release on 2008Q4
作者:XXX
Contents

MNP overview

Huawei MNP Solution

Interconnection with NPAC and core


network elements

Case Study
Contents

Interconnection with NPAC

Interconnection with MSC/GMSC

Interconnection with SCP

Interconnection with SMSC

Requirement of Billing system


Interconnection with NPAC

• LSMS is a Sun server


NPAC
which houses the NP
synchronization software.
SOAP/XML
• The LSMS connects to SOAP/XML
NPAC via SOAP/XML.
• The LSMS connects to BOSS/Cares LSMS

BOSS or customer care


system for NP related STP-NPDB

service activity.
• LSMS will synchronize the
NPDB with all SG7000 .
MSC HLR SCP SMSC MMSC
Interconnection with Central Clearing House
Initiation Flow
Interconnection with Central Clearing House
Cancel Flow
Signaling flow between STP-NPDB
STP and Central
Clearing House
Activation flow
Activatation Flow illustration
CARES(R) LSMS(R) CDBA LSMS(D) CARES(D) LSMS(O)
AcP1 NP_Execution
NP_ExecutionReponse
NP_Exec
Error
NOTIFY MSG NP_Exec
(NP Exec , RejectCode) NOTIFY MSG
(NP_Exec , OK)
NP_ReadyOK AcP2
NP Ready
NP Ready
NOTIFY MSG
(NP_Ready , OK)

AcP3 NP_nonRFService
NP_nonRFServiceReponse
NP nonRFS
Error
NOTIFY MSG NP nonRFS
(NP nonRFS , RejectCode)

AcP4 NP_RFService
NP_RFServiceReponse
NP RFS
Error SRF_NPDBD)
NOTIFY MSG NP RFS Broadcast
(NP RFS , RejectCode)
AcP5a SQL(route)
NOTIFY MSG
AcP5b (NP RFS Broadcast , OK)
NP RFS Broadcast
NP Activated AcP6a
NP Activated AcP6b

NP Activated Status
Signaling flow between STP-NPDB
STP and Central
Clearing House
Disconnect flow
Disconnect Flow illustration

CARES(R) LSMS(R) CDBA LSMS(O) CARES(O)

DP1 NP_DeactivatedR

NP_DeactivatedRReponse
NP_ Deactibated

Error
NOTIFY MSG NP Deact Broadcast
NOTIFY MSG
(NP Deactivated ,
RejectCode) (NP Deactivated , OK)

NP Deact Done DP2

NP Deact Done

NP Deact Done status


Interconnection with MSC/GMSC

MSC to support MNP


Call Type Requirement
Prepaid-MO calls 1.When the MSC receives the CONTINUE message, it
ported-in, ported- can send SRI(MSISDN) to HLR (via STP-NPDB)
out, cross-ported or regardless of MSISDN belonging to own or other
regular-foreign network. NPAC
subscriber
Forwarding Call: C If C number is ported-out, cross-ported or regular-
number is ported- foreign, the MSC shall Continue the Forwarding Call
out, cross-ported or
regular-foreign
number
BOSS/Cares LSMS SOA
GMSC to support MNP
Call Type Requirement
MTC from other 1.GMSC receives the IAM message(RN+MSISDN), it STP-NPDB
mobile operator to can delete RN in IAM called number and send
regular-own, SRI(MSISDN=MSISDN) to HLR.
ported-in number 2.Called number which is recorded in CDR is MSISDN,
the RN is removed by GMSC.
Onwards routing 1. GMSC shall support onwards routing for incoming
(Call from PSTN, call from PSTN call. MSC HLR SCP SMSC MMSC
RN is not present)
MTC to ported-out GMSC receives the IAM message (RN+MSISDN) from
number (Loop mobile network and the called subscriber don’t belong
detection) to own network, it can release the call
Interconnection with MSC/GMSC
Call
Call-Related Service: Post-Paid MO

HLR MNP relay


Signaling Channel
Voice Channel

STP&NPDB STP&NPDB

1 2
3 4
5
MSC GMSC GMSC

Originating Network Terminating Network

1. SRI(MSISDN) CdPA=MSISDN, CgPA=MSC address


2. SRI ack(RN+MSISDN) CdPA=MSC address, CgPA=MSISDN
3,4,5. IAM(RN+MSISDN)
Interconnection with MSC/GMSC
Call-Related
Related Service: International roaming Post-Paid
Post MO

HLR MNP relay


Signaling Channel
Voice Channel

STP&NPDB STP&NPDB

3 4

1 2 5
IGMSC IGMSC GMSC GMSC

Other Country Number range holder Network Terminating Network

1. IAM (MSISDN)
2. IAM (MSISDN)
3. SRI (MSISDN) CdPA=MSISDN, CgPA=MSC address
4. SRI ack (RN+MSISDN) CdPA=MSC address, CgPA=MSISDN
5. IAM (RN+MSISDN)
Interconnection with MSC/GMSC
Call-Related
Related Service: GMSC Loop Detection

HLR MNP relay


Signaling Channel
Voice Channel

STP&NPDB STP&NPDB

2
3
1
GMSC GMSC
4
Originating Network Terminal Network

1. IAM (RN+MSISDN)
2. SRI(MSISDN) CdPA=MSISDN, CgPA=GMSC address
3. SRI ack (RNf+MSISDN) CdPA=MSC address, CgPA=MSISDN
4. REL
Interconnection with SCP

NPAC
SCP to support MNP

Call Type Requirement

Prepaid-MO/ 1.SCP can identify an


International on-net and off-net call
roaming based on RN (Route BOSS/Cares LSMS
Prepaid-MO Number). and apply
calls ported- differential tariffing based
in, ported-out on an on-net and off-net
or cross- call.
ported 2.IN CDRs shall have STP-NPDB
subscriber sufficient information to
distinguish between
regular-own, ported-in,
ported-out, cross-ported
and regular-foreign calls.

MSC HLR SCP SMSC MMSC


Interconnection with SCP
Call-Related
Related Service: Pre-Paid
Pre MO

HLR SCP MNP relay


Signaling Channel
2 Voice Channel
3

STP&NPDB STP&NPDB

1 4 5
6
7 8
9
MSC GMSC GMSC

Originating Network Terminating Network

1. IDP(MSISDN) 2. IDP(RN+MSISDN) 3. CONTINUE() 4. CONTINUE()


5. SRI(MSISDN) 6. SRI ACK(RN+MSISDN) 7,8,9. IAM(RN+MSISDN)
Interconnection with SCP
Call
Call-Related Services: ATI Query

SCP

MNP relay
1 2 Signaling Channel

STP&NPDB STP&NPDB

1. ATI (MSISDN), CdPa= MSISDN


2. ATI ack (RN, MSISDN, number ported out), CdPa=SCP address
Interconnection with SCP
Call-Related
Related Service: International Roaming Pre-Paid
Pre MO

HLR SCP MNP relay

2
3 Voice Channel
Signaling Channel

STP&NPDB STP&NPDB

1
4 8 9
7

5 6 10
MSC IGMSC GMSC GMSC

Other Country Number range holder Network Terminating Network


1. IDP (MSISDN)
2. IDP (RN+MSISDN)
3. Continue
4. Continue
5. IAM (MSISDN)
6. IAM (MSISDN)
7. SRI (MSISDN) CdPA=MSISDN, TT=SRI, CgPA=MSC address
8. SRI ack (RN+MSISDN) CdPA=MSC address, CgPA=MSISDN
9.10. IAM (RN+MSISDN)
Interconnection with SMSC

NPAC

SMSC to support
MNP

STP will intercept MO message


and prefix RN to called MSISDN,
so SMSC should Identify the RN BOSS/Cares LSMS
code.

CDR including MNP information


with RN
STP-NPDB

Apply on-net or off-net charging


correctly for PPS

MSC HLR SCP SMSC MMSC


Interconnection with SMSC (interconnect by GMSC)
MO-Forward
Forward-SM & SRI-FOR-SM Interception

MNP relay
Signaling Channel HLR

STP&NPDB STP&NPDB 6 7

9
1 2 3 10 4
5
VMSC SMC 11 GMSC 8 GMSC
12

Originating Network Terminating Network

1. MO-Forward-SM(MSISDN)
SM(MSISDN) 2. MO-Forward-SM(RN+MSISDN)
MO
3. SRI-FOR-SM
SM (MSISDN), CdPa=MSISDN 4,5. SRI-FOR-SM
SRI (MSISDN), CdPa=RN+MSISDN
6. SRI-FOR-SM
SM (MSISDN), CdPa=HLR address 7,8,9,10. SRI-FOR-SM
SRI ack (MSC address), CdPa=SMSC address
11,12. Forward-SM(MSC address)
Non-Call-Related
Related Service: MO-FSM
MO Message Interception

SMSC MNP relay


Signaling Channel

STP&NPDB STP&NPDB

2
1

MSC SMSC

Originating Network

1. MO-forward-SM
SM (MSISDN),cdPA=SMSC-ID,
(MSISDN),cdPA=SMSC cgPA=MSC-ID
2. MO-forward-SM
SM ack (USER ERROR), cdPA=MSC-ID,
cdPA=MSC cdPA=SMSC-ID
Requirement of Billing system
Service type Charging Type Callee type MSRN format in MSC’s CDR /
Called Number format in SCP’s CDR
voice call On-net rate The Callee is regular-own
regular MSISDN in MSC/SCP CDR
subscribers
The Callee is Port-in
in subscribers MSISDN in MSC CDR
RN (own network RN) +MSISDN in SCP
CDR
Off-net rate The Callee is Port-out
out subscribers RN (OMO RN) + MSISDN in MSC/SCP
CDR
The Callee is cross-port
port subscribers RN (OMO RN) + MSISDN in MSC/SCP
CDR
The Callee is regular-foreign
regular RN (OMO RN) + MSISDN in MSC CDR
subscribers OMO MSISDN in SCP CDR
Service type Charging Type Callee type MSRN format in MSC’s CDR
SMS / MMS On-net rate The Callee is regular-own
regular MSISDN
subscribers
The Callee is Port-in
in subscribers RN (own network RN) + MSISDN
Off-net rate The Callee is Port-out
out subscribers RN (OMO RN) + MSISDN
The Callee is cross-port
port subscribers RN (OMO RN) + MSISDN
The Callee is regular-foreign
regular OMO MSISDN
subscribers
Contents

MNP overview

Huawei MNP Solution

Interconnection with NPAC and core


network elements

Case Study
作者:XXX

Customers’ Choice – Best Partner in Signaling Field

Norway

Poland Russia
Bulgaria
Uzbekistan
Pakistan China
Hong Kong
UAE Thailand
Mexico Philippines
Singapore
Colombia Malaysia Brunei

Indonesia
Brazil
Botswana

Chile
Argentina

l More than 910 sets of Huawei STP deployed in over 40 countries


l 70% of market share in China
E2E MNP Solution in Pakistan

About
• Famous mobile operator in Pakistan
• Support 5 million MNP Subscribers
• The NPAC (Central Clearing House) is ISL1 FAB1
SG7000-
constructed by Telcordia
NPDB
• Interconnection with core network elements MSC Plane A
KAR1 LAH1
(Siemens, Nortel), SMSC (Logica), MMSC (Logica),
HLR (Siemens, Nortel), SCP (Huawei, Nortel)

Challenges
• E2E MNP is required to be implemented
in 3 months
ISL2 FAB2
• FNR in urgent need
SG7000-
• Future oriented NPDB
KAR2
Plane B
LAH2
Benefits
• Facilitates rollout of MNP & FNR
• Independent signaling network supports
TDM/IP convergence network National signaling network
• Lower CAPEX & OPEX

Huawei MNP Solution is the best solution in Pakistan --- Pakistan Government
C/G MNP Based on STP in Brazil

About International CCS7


• Biggest mobile operator in Brazil Signaling Network

with 40 million subscribers


SG7000
1500NSL 1500NSL
Challenges
• CDMA customers retreated
• STP with lower performance couldn’t
C/G MNP Service
meet legacy multiple standards

Benefits CDMA STP


GSM
• Remain CDMA customers & can transit PSTN
to GSM network smoothly
• SG7000 satisfying multiple standards in Over 10 pairs of SG7000 deployed

C/G/PSTN for whole network by 2006


MNP Solution in Singapore
– little impact on current network

About
A Leading Singapore Operator SG7000
SG7000
SMSC
Challenges
To fast deploy MNP
• FNR already applied
• STP(GMSC) exist in network MMSC
SCP
Benefits HLR
GMSC/STP
• Facilitates rollout of MNP & FNR GMSC/STP
• SG7000 act as MNP server
• Cooperate with Syniverse providing LSMS
• Lower CAPEX & OPEX
VMSC MSC Server
2G/3G MNP Based on Convergence STP

About LSMS
• An emerging mobile operator in Poland
NPAC
Challenges
SG7000
• Few subscribers
• Signaling network should satisfy 2G & 3G
convergence network simutaneously

Benefits MSC SCP SMSC HLR GMSC


• Easy to attract subscribers & upgrade them
from 2G to 3G smoothly
P4 Network
• A cost-effectively solution for 2G/3G & TDM/IP
signaling processed by one pair of STP
TDM link (NSL or HSL)

IP link (M3UA or M2PA)


Thank You
www.huawei.com
www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.