Professional Documents
Culture Documents
11 Apr 2008
www.huawei.com
MNP overview
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
►
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
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
MNP overview
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
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
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
MNP overview
Case Study
Contents
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
DP1 NP_DeactivatedR
NP_DeactivatedRReponse
NP_ Deactibated
Error
NOTIFY MSG NP Deact Broadcast
NOTIFY MSG
(NP Deactivated ,
RejectCode) (NP Deactivated , OK)
NP Deact Done
STP&NPDB STP&NPDB
1 2
3 4
5
MSC GMSC GMSC
STP&NPDB STP&NPDB
3 4
1 2 5
IGMSC IGMSC GMSC GMSC
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
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
STP&NPDB STP&NPDB
1 4 5
6
7 8
9
MSC GMSC GMSC
SCP
MNP relay
1 2 Signaling Channel
STP&NPDB STP&NPDB
2
3 Voice Channel
Signaling Channel
STP&NPDB STP&NPDB
1
4 8 9
7
5 6 10
MSC IGMSC GMSC GMSC
NPAC
SMSC to support
MNP
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
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
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
Case Study
作者:XXX
Norway
Poland Russia
Bulgaria
Uzbekistan
Pakistan China
Hong Kong
UAE Thailand
Mexico Philippines
Singapore
Colombia Malaysia Brunei
Indonesia
Brazil
Botswana
Chile
Argentina
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
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