Mobile Number Portability (MNP)

5 Mobile Number Portability (MNP)
5.1
© Alcatel University - 8AS 90200 0738 VT ZZA Ed.01
© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

Page 5.1
Session presentation
▼ Objective: to be able to solve a problem related to

Mobile Number Portability (MNP)
5.2

Page 5.2
▼ Program : MOBILE NUMBER PORTABILITY Page
5.1 Definitions
Objective 6
consequences 7
NPDB access method 8
5.2 MNP-SRF procedures

Call routing to a mobile 10
Call to a non ported number 11
OC Call to a ported number via direct routing 12
Call to a ported number via indirect routing 13
Call to a PN via indirect routing with reference to the subscription network 14
Off-Call message routing 15
Off-Call message routing 16
Call handling at the " NRON" PLMN 17
Call handling at the " subscription" PLMN 18
Charging at the RCP 21
5.3 Setting up MNP

Observation at the RCP 24
Observation at the RCP 25
Operation at the HLR - MAP version management 26
Operation at the RCP 27
Operation at the SSP 30
5.4 Data structure

F_MNP_001 32
F_MNP_002 33
F_MNP_006 34
F_MNP_007 35
F_MNP_008 36
F_CG_055 37
Data specific to MNP-SRF and PLMN 38
Unsolicited messages 39
Evaluation 41

Page 5.3
▼ Page intentionally left blank

Page 5.4
5.1 Definitions
5.5

Page 5.5
5.1 Definitions
Objective
▼ The Mobile Number Portability (MNP) enables a mobile

subscriber to change subscription for another PLMN within the
same country, while retaining the same directory number
(MSISDN).
▼ A new IMSI, belonging to the new PLMN, is assigned to the

mobile subscriber.
5.6

Page 5.6
5.1 Definitions
Consequences
▼ The MSISDN is no longer enough to route calls or messages (SMS, for
example) to the called mobile.
▼ The standard routing mechanisms result in routing to the network the number
belongs to :
z NRON: Number Range Owner Network
▼ The MNP function is based on a Number Portability Database (NPDB) for

rerouting calls or messages to the new subscription network:
z Subscription Network
▼ The portability relates only to a set of PLMNs called "PORTABILITY

CLUSTER".
5.7

Page 5.7
5.1 Definitions
NPDB access method
▼ Intelligent Network (IN): a subset of IN-CS1 operations (Initial-DP, Connect,
Continue) can be used to query the Number Portability Data Base (NPDB).
Î not retained in R6/R7
▼ Signalling Relay Function (SRF): the NPDB is queried via an SCCP relay via
which the messages addressed by an MSISDN are routed:
z For calls to a mobile: Send Routing Information (SRI) message
z For off-call messages: SRI with OR, SRI for SMS
Î method retained in R6/R7, because:
' mandatory for routing off-call messages,
' the SCCP relay can be used to distribute the MSISDNs to the
different HLRs of the PLMN,
' Alcatel product - DSC available for handling the MNP-SRF
function.
5.8

Page 5.8
5.9

Page 5.9
Call routing to a mobile
Number Range INDIRECT ROUTING Subscription Network

Owner Network WITH REFERENCE TO
THE SUBSCRIPTION
MNP-SRF HLRb
NPDB 2
NETWORK
IAM 3
(MS
ISD
N)
MNP-SRF
INDIRECT ROUTING GMSCa IAM
((RN
+) MSIS NPDB
) DN)
DN
MSIS
(
IAM
IAM (MSRN)
Other Network GMSCb
N)
MNP-SRF SD
NPDB SI
+ )M
N
((R
1 M
IA DIRECT ROUTING
VMSC GMSC
PORTABILITY CLUSTER
5.10
▼ CALL ROUTING TO A MOBILE
z GMSCa routes the Send Routing Information (SRI) message to query the HLR to the MNP-SRF of its PLMNa.
The Translation Type (TT) in the SCCP address of the called party (CdPA) indicates: call handling message (SRI).
z The MNP-SRF is based on an internal MAP application (MATF) for handling the SRI message and on the NPDB for
the routing information.
z If the called subscriber number is not ported or ported in PLMNa :
Î the MNP-SRF sends the SRI to the HLR: Called Party = HLR address (3),
Î then standard terminating call handling follows.
z If the called subscriber number is ported in another PLMNb :
Î Case of direct routing
ª The visited PLMN interrogates its NPDB. The MNP-SRF then returns the "SRI res" to the GMSCa with
a re-routing number ((RN)+MSISDN) towards the PLMNb (1). This involves the PLMN to know all the
ported MIISDN of the cluster.
Î Case of indirect routing. The visited PLMN interrogate the called party NRON and can process the call
depending on two cases :
ª 1 The MNP-SRF of the NRON interrogates its NPDB finds that the MSISDN is ported out in the
PLMNb so returns the SRI res to the NRON GMSCa with a re-routing number ((RN)+MSISDN)
towards the PLMNb .
ª 2 Indirect routing with reference to the subscription network. The MNP-SRF of the NRON interrogates
its NPDB and finds that the MSISDN is ported out in the PLMNb. The NRON SRF sends the SRI to the
MNP-SRF of PLMNb which itself interrogates its own NPDB.
- If MSISDN is ported in PLMNb this one returns the "SRI res" to the GMSCa with the
RN+MSISDN (2). The GMSCa can then re-routes the call to the GMSCb.
- If MSISDN is not ported in PLMNb (ported out) the call is released because of non coherency
of the data bases.
ª This solution avoid the databases inconsistencies before the seizure of a circuit between NRON and
PLMNb GMSCs
z The GMSCb performs the same process as the GMSCa, but the SRI is relayed to the HLR since the subscriber is
ported in his PLMNb.

Page 5.10
Call to a non ported number
Subscription Network
= PORTABILITY
Number Range Owner Network CLUSTER
HLRb
Originating
Network SRI (MSISDN)
CdPA = HLRb address 3
CgPA = GMSCb address
MNP
SRI res (MSRN)
NPDB SRF/MATF 4 CdPA = GMSCb address
CgPA = HLRb address
SRI (MSISDN)
CdPA = MSISDN, TT=SRI 2
CgPA = GMSCb address
Originating
IAM (MSISDN) IAM (MSRN)
Exchange 1 GMSCb 5
5.11

Page 5.11
OC Call to a ported number via direct routing
PORTABILITY
Originating Network CLUSTER Subscription Network
MNP
NPDB SRF/MATF HLRb
SRI (MSISDN) SRI res (RN + MSISDN)

CdPA = MSISDN, TT=SRI
3 4 CdPA = GMSCa address MNP
8
CgPA = GMSCa address CgPA = MNP_SRF address NPDB SRF/MATF 7
IAM (MSISDN) IAM (MSRN)

IAM ((RN +) MSISDN) GMSCb
1 VMSCa 2 GMSCa 5 9
SETUP (MSISDN)
5.12

Page 5.12
Call to a ported number via indirect routing
Originating Number Range PORTABILITY

CLUSTER Subscription Network
Network Owner Network
HLRb
MNP
NPDB SRF/MATF
SRI (MSISDN) MNP

SRI res (RN + MSISDN) 7
NPDB SRF/MATF
2 3 CdPA = GMSCa address
CgPA = GMSCa address CgPA = MNP_SRF address
IAM (MSRN)
Originating IAM (MSISDN) IAM ((RN +) MSISDN) GMSCb 8
Exchange 1 GMSCa 4
5.13

Page 5.13
Call to a ported number via indirect routing with reference to the
subscription network
PORTABILITY
Originating Number Range CLUSTER Subscription Network
Network Owner Network
SRI (MSISDN)
CdPA = RN + MSISDN, TT=SRI HLRb
MNP
NPDB CgPA = GMSCa address
SRF/MATF
3
7
MNP
SRI (MSISDN) 8
7
NPDB SRF/MATF
2 SRI res (RN + MSISDN)
CgPA = GMSCa address
CdPA = GMSCa address
CgPA = MNP_SRF address 6
4
Originating IAM (MSRN)

Exchange IAM (MSISDN) IAM ((RN +) MSISDN) GMSCb 9
1 GMSCa 5
5.14

Page 5.14
Off-Call message routing
▼ Off-call messages for which the SCCP address of the called party is the
MSISDN are routed via the MNP-SRF:
z SRI for SMS: between the SMS-GSMC and the HLR,
z SRI for optimal routing: between the GMSC and the HLR of another
PLMN
z ATI: between the "Camel" SCP and the HLR
▼ If the MSISDN is not ported or ported in the PLMNa of the MNP-SRF, the
message is transmitted to the relevant entity (CdPA = entity address).
▼ If the MSISDN is ported in another PLMNb, the message is transmitted to the

MNP-SRF of the PLMNb (CdPA = RN+MSISDN) which relays it to the
relevant entity.
5.15

Page 5.15
Off-Call message routing : SMS to a number ported via indirect routing
PORTABILITY
Number Range Subscription Network CLUSTER
Interrogating Network
Owner Network
SRI_for_SM ack (VMSCB address)

CdPA = SMS-GMSCa address HLRb
CgPA = HLRb address 5
SRI_for_SM (MSISDN)
SRI_for_SM (MSISDN) 4 CdPA = HLRb address

SC CgPA = SMS-GMSCa address
CdPA = RN (+MSISDN)
CgPA = SMS-GMSCa add
MNP- MNP-
Forward SM SRF 3 SRF Visited Network
(MSISDN)
1
SRI_for_SMS (MSISDN)
2
CdPA = MSISDN, TT=0 7
SMS
CgPA = SMS-GMSCa address
GMSCa Forward_SM (VMSCB address) VMSCb
6
5.16

Page 5.16
Call handling at the " NRON" PLMN
▼ AT THE GMSC OF THE PORTED NUMBER'S OWNER NETWORK:
z On the request for call routing information to the HLR via the Send Routing
Information message:
Î The RCP sets the Translation Type (TT) of the called party's SCCP address in
the "without optimal routing" SRI message to a specific value defined by a
PLMN parameter (D_TTSRF).
z On call rerouting to the subscription network:

Î The MNP-SRF/MATF supplies in the SRI result:
' the optional "number portability status" parameter:
– not known as ported number,
– PLMN number, ported to another PLMN of the "cluster",
– number of a foreign PLMN ported to a foreign PLMN.
' The RN on its own or concatenated with the MSISDN (RN+MSISDN).
Î RCP calls the translator (origin: "MAPMSRN") to analyse the RN and obtain:
' the called party number RN+MSISDN,
' a specific numbering type, "RNCDN": "network routing number
concatenated with call directory number",
' identification of the subscription PLMN (observations) :
– Î new translation result operator command parameter:
PLMNNAME 5.17

Page 5.17
Call handling at the " subscription" PLMN
▼ AT THE GMSC OF SUBSCRIPTION NETWORK:
z As for any terminating call, the called party number (RN+MSISDN)

corresponding to a subscriber ported in the PLMN is analysed in the RCP
translator (origin = "network" and numbering type = "network routing
number concatenated with call directory number" (RNCDN)).
z The translator:
Î extracts the MSISDN from the called party number to query the
HLR, prefixes the SCCP address of the called party in the SRI
message with the RN
'(if option F-MNP-008 is active),
Î identifies whether portability has already been handled in another
PLMN to detect inconsistencies between the PLMNs
'(if option F-MNP-007 is active).
5.18

Page 5.18
▼ TO AVOID LOOPS IN THE NETWORK::
z (Optional) checks can be used to detect inconsistencies between the

NPDBs of the different PLMNs in the "cluster":
Î For example:
'MSISDN registered as "ported" in the "NRON" PLMN and
absent in the "subscription" PLMN.
'MSISDN registered as "ported" to PLMNb in PLMNa and
registered as "ported" to PLMNa in PLMNb The translator:
z These checks can be carried out:

Î by the gateway MSC if option F-MNP-007 is active,
Î and/or by the MNP-SRF if option F-MNP-008 is active.
5.19

Page 5.19
▼ TO AVOID LOOPS IN THE NETWORK::
z If option F-MNP-007 is active, the following checks are carried out by the gateway
MSC of the "subscription" PLMN:
Î an unsolicited message is output if the call rerouted for portability is
unknown in the HLR of the subscription network (receipt of SRI error with
"cause = unknown subscriber"),
Î an unsolicited message is output and the call is released if the MNP-SRF of
the subscription network asks for the rerouting of a call that is already
rerouted for portability by another PLMN (receipt of SRI res with
"Number portability status = own ported out".
z If option F-MNP-008 is active, the gateway MSC of the subscription network can
indicate to the MNP-SRF that a number is ported in its network by providing it
with an SCCP address of the called party consisting of the MSISDN prefixed by a
local rerouting number.
Î The MNP-SRF therefore has the capability to detect inconsistencies if this
MSISDN is not registered in its portability database as ported in its network:
In this case, an unsolicited message is output and the call is released
by the gateway MSC
5.20

Page 5.20
Charging at the RCP
▼ The GMSC ("NRON" PLMN or "originating" PLMN) that reroutes the call to
the subscription network generates a "rerouted TC" CDR with MNP-specific
information if option F-CG-055 is active:
z IMSI supplied by the MNP-SRF/MATF (only MCC-MNC meaningful)
z "Number portability status" as supplied by the MNP-SRF/MATF
▼ The GMSC of the "subscription" PLMN generates a "rerouted TC" CDR with
MNP-specific information if option F-CG-055 is active:
z "Number portability status": "ported in",
z rerouting number as received from the network (RN+MSISDN).
5.21

Page 5.21

Page 5.22
5.3 Setting up MNP
5.23

Page 5.23
5.3 Setting up MNP
Observation at the RCP
▼ "NRON" PLMN:
z In the GMSC, a new family of counters is provided to total

the number of calls re-routed for portability to a given PLMN:
Î family identifier: 35809
Î number in the family: name of destination PLMN:
' as given by the new "PLMNNAME" parameter of
the "ROUTING" type result derived from translation
of the "MAPMSRN" original rerouting number "RN"
Î counter type: peg counter
5.24

Page 5.24
5.3 Setting up MNP
Observation at the RCP
▼ MSISDNs (CC-NDC-SN) registered in the HLR can be from a number of PLMNs:
z Need to be able to register, for each subscriber, the NDC (representing the
PLMN) in addition to the SN.
z The "SN" parameter of the HLR commands is used to define the part of the
MSISDN specific to each subscriber and should include the NDC if portability is
offered.
z If option F-TR-012 is active, translation of the MSISDNs (SRI) of other PLMNs
must be added to the translators corresponding to the "NBRCHK" origin.
As standard, the "SN" parameter is limited to 10 digits:
Format of non-ported MSISDN
CC NDC SN
1 to 3 digits 1 to 3 digits 1 to 10 digits
With option F-SA-012, the "SN" parameter can be extended to 14 digits:

Format of ported MSISDN
CC NDC SN
1 to 4 digits
1 to 3 digits 1 to 14 digits
5.25

Page 5.25
5.3 Setting up MNP
Operation at the HLR - MAP version management
▼ "Subscription" PLMN:
z MAP version management:

Î if F-VH-001 is active, the "SRI for SMS" messages from
other PLMNs in the "portability cluster" must be
accepted on reception:
' RAPCTX= SMGWAY , RVERS=V2 (or V1).
5.26

Page 5.26
5.3 Setting up MNP
Operation at the RCP
▼ THE GMSC CAN RECEIVE CALLS:
z to any MSISDNa for which it is within the "NRON" PLMN
z to any RN+MSISDNb for which it is within the "subscription" PLMN
▼ RCP TRANSLATION:
z analysis (origin = "network") of the MSISDNa and RN+MSISDNb should give an
"HLR interrogation" type result (HLRROUT)
Î the result of analysis of the (RN+)MSISDNb should indicate that there has
already been interrogation of the MNP/SRF by the NPDBQ=DONE
parameter
▼ "SCCP" ANALYSES:
z analysis of the MSISDNa and (RN+)MSISDNb should lead to routing of the SRI
message to the MNP-SRF with the MSISDN (preceded by an RN if F-MNP-008
is active) as the called subscriber's global title
▼ MAP VERSION MANAGEMENT:
z the MAPKEY parameter derived from translation of the MSISDNs should identify
the MNP-SRF (instead of the HLR)
5.27

Page 5.27
5.3 Setting up MNP
▼ THE VMSCa RECEIVE CALLS FROM MSs:
z to any MSISDNa for which it is within the "NRON" PLMN
z to any MSISDNb belonging to PLMNs of the "portability cluster"
▼ RCP TRANSLATION:
z analysis (origin = "mobile") of the MSISDNa should give an "HLR interrogation"
type result (HLRROUT)
z in the case of direct routing, analysis (origin = "mobile") of the MSISDNb should
also give an "HLR interrogation" type result (HLRROUT)
z in the case of indirect routing, analysis (origin = "mobile") of the MSISDNb should
give a "routing to "NRON" PLMN type result (ROUTING)
▼ "SCCP" ANALYSES:
z analysis of the MSISDNa (and MSISDNb in the case of direct routing) should
lead to routing of the SRI message to the MNP-SRF with the MSISDN as the
called subscriber's global title
▼ MAP VERSION MANAGEMENT:
z as for the GMSC, the MAPKEY parameter obtained from translation of the
MSISDNs should identify the MNP-SRF
5.28

Page 5.28
5.3 Setting up MNP
▼ REROUTING TO THE "subscription" PLMN :
z If the subscriber is ported in another PLMN, the VMSC or GMSC receives in the
SRI result a rerouting number (RN) to the "subscription" PLMN in place of the
roaming number (MSRN):
Î Like the MSRN, the RN is analysed in the RCP translator (orig =
MAPMSRN).
Î MSISDN (international format) is provided as « additional number » to the
translation function.
Î The translation result is "routing_to_subscription_PLMN" type (ROUTING)
and can be used in particular:
' if not directly performed by the MNP-SRF, to add the MSISDN after
RN (INS=length(cc) - length(MSISDN), RINS=(length(RN)+1)),
' to position a specific numbering type: "network routing number
concatenated with call directory number" (NUMTYP=RNCDN),
' to identify the subscription PLMN for observation purposes
(PLMNNAME=xxx).
5.29

Page 5.29
5.3 Setting up MNP
Operation at the SSP
▼ PREANALYSIS:
z The specific numbering type : RNCDN "network Routing Number
Concatenated with call Directory Number" (PRE=x) must be provided
in the preanalysis tables (PREA = "ISUP" and PREA = "Alcatel INAP").
▼ ANALYSIS:
z The SSP's translation function must be initialised to allow the reception
and transmission of MSISDNs prefixed with a rerouting number for
portability (RN) :
Î in the "terminating" translator, analysis of the HPLMN's RN
(concatenated with the MSISDN) should initiate a call to the RCP
(server routing)
Î in the "originating" translator, analysis of the RNs of the other
PLMNs (concatenated with the MSISDN) should result in the call
being routed to the PLMN concerned
5.30

Page 5.30
5.4 Data structure
5.31

Page 5.31
5.4 Data structure
F_MNP_001
▼ F-MNP-001 (RCP)
z Sys. Par. : PARNAME = P2B_F_MNP_001, BOOLVAL
z RTDMS database : RELNAME = PYR_SY2B attribute :
D_MNP001
▼ F-MNP-001 enables the MNP feature.
▼ Meaning :
z TRUE : The RCP supports MNP.
z FALSE : The RCP does not support MNP.
5.32

Page 5.32
5.4 Data structure
F_MNP_002
▼ F-MNP-002 (RCP)
D_MNP002
▼ F-MNP-002 enables the use of the MNP-SRF solution

z implicit optionnal function
5.33

Page 5.33
5.4 Data structure
F_MNP_006
▼ F-MNP-006 (RCP)
D_MNP006
▼ F-MNP-006 determines the sending of anticipated ACM

messages upstream if there is MNP functionality.
z implicit optionnal function
5.34

Page 5.34
5.4 Data structure
F_MNP_007
▼ F-MNP-007 (RCP)
z RTDMS database : RELNAME = PYR_SY2B attribute : D_MNP007
▼ F-MNP-007 allows inconsistencies between the portability databases (NPDB) to be
detected by the GMSC of the subscription network.
z If inconsistencies are detected by the GMSC, F-MNP-007 ensures :
Î immediate output of a message if, during a re-routed call, the subscriber is
unknown in the HLR of the subscriber network
Î the release of the re-routed call and immediate output of a message if the
MNP/SRF of the subscriber network responds with a state of portability
that is incompatible with continuation of the call (call already conveyed by
an MNP/SRF).
▼ Meaning :
z TRUE : F-MNP-001 must be set to TRUE. The GMSC ensures the detection of
inconsistencies in the portability databases.
z FALSE : The GMSC does not ensure the detection of inconsistencies in the
portability databases
5.35

Page 5.35
5.4 Data structure
F_MNP_008
▼ F-MNP-008 (RCP)
z RTDMS database : RELNAME = PYR_SY2B attribute : D_MNP008
▼ F-MNP-008 allows the detection of inconsistencies by the MNP/SRF between the portability
databases (NPDB).
z F-MNP-008 enables the possibility of handling loop checks between the PLMNs of the
"portability cluster", at the MNP-SRF
z Some MNP/SRFs can detect inconsistencies between NPDBs themselves.
z In this case, the MNP/SRF resends the information in the MAP_SEND_ROUTING_INFO
_ERROR message so that the GMSC proceeds as follows:
Î release of the re-routed call and output of a message if the MNP/SRF of the network
detects an inconsistency (call already conveyed by an MNP/SRF).
▼ Meaning :
z TRUE : F-MNP-001 is set to TRUE. F-MNP-008 allows the GMSC to provide (to the
MNP/SRF) an SCCP address for the called party consisting of the MSISDN prefixed by a
routing number
z FALSE : F-MNP-008 does not allow the MNP/SRF to detect NPDB inconsistencies
5.36

Page 5.36
5.4 Data structure
F_CG_055
▼ F-CG-055 (RCP)
z Sys. Par. : PARNAME = P2B_F_CG_055, BOOLVAL
z RTDMS database : RELNAME = PYR_SY2B attribute : D_CG_055
▼ F-CG-055 is used to generate call data records with information specific to the portability function
of the numbers (MNP)
▼ Meaning :
z TRUE : F-CG-055 is significant if F-MNP-001 is set to TRUE.
Î The GMSC/VMSC that re-routes the call to the subscriber network and generates a
call data record with the following information :
' Portability status as provided by the MNP/SRF in the MAP SRI message
' Re-routing number (RN)
' MSISDN of the called mobile subscriber
' the IMSI as provided by the MNP/SRF
Î The subscriber network GMSC generates a CDR with the following information :
' Portability status
' Re-routing number (RN)
' MSISDN of the called mobile subscriber
z FALSE :
Î The RCP does not generate information specific to portability in the call data record
5.37

Page 5.37
5.4 Data structure
Data specific to MNP-SRF and PLMN
▼ Initialisation of the "Translation type" field of the "called party address"
parameter for the SCCP part of the frame for "SRI without OPTIMAL
ROUTING" messages (RCP).
z Sys. Par. : TT_SRF_MNP, VALUE
z RTDMS database : RELNAME = PYR_SY2B attribute : D_TTSRF
z minimum value = 0, maximum value = 255, default value = 0
▼ Default rerouting PLMN identifier (in the absence of the PLMNNAME

parameter in the translation result)
z Sys. Par. : P2B_RRPL_D , VALUE
z RTDMS database : RELNAME = PYR_SY2B attribute : D_RRPL_D
z value: string of up to 8 characters (1 character minimum), default value =
PLMN
5.38

Page 5.38
5.4 Data structure
Unsolicited messages
PMLX/6073 - ABONNE INCONNU DU RESEAU D’ABONNES (SUBSCRIBER
UNKNOWN TO SUBSCRIBER NETWORK)
MEANING:
The call has been rerouted for MNP to the subscriber network and the called subscriber is
unknown to the HLR.
NETRN = Rerouting number received in the network
MSISDN = Called subscriber's identity
ACTION REQUIRED:
- check for existence of the ported subscriber at the HLR and check the NPDBs of the portability
cluster's PLMNs
PMLX/6074- REROUTAGE INCOHERENT POUR LE MNP DANS LE RESEAU

D’ABONNES (INCONSISTENT REROUTING FOR MNP IN THE SUBSCRIBER
NETWORK)
MEANING:
The call has been rerouted for MNP to the subscriber network and the subscriber network's NPDB
database (via the SRI result) requests further rerouting of the call.
NETRN = RN received in the network
NPDBRN = RN received in the SRI result
NPSTATUS = Portability status, if received in the SRI result
MSISDN = Called subscriber's identity
ACTION REQUIRED:
- check the NPDB of the PLMN and have the NPDBs of the portability cluster's PLMNs checked
5.39

Page 5.39

Page 5.40
Evaluation
▼ Objective: to be able to solve a problem

related to Mobile Number Portability
(MNP).
Thank you for answering

the self-assessment
of the objectives sheet
5.41

Page 5.41

Page 5.42

Mobile Number Portability (MNP)

Uploaded by

Copyright:

Available Formats

Mobile Number Portability (MNP)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mobile Number Portability (MNP)

Uploaded by

Copyright:

Available Formats

5 Mobile Number Portability (MNP)

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

▼ Objective: to be able to solve a problem related to

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

5.2 MNP-SRF procedures

5.3 Setting up MNP

5.4 Data structure

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

▼ The Mobile Number Portability (MNP) enables a mobile

▼ A new IMSI, belonging to the new PLMN, is assigned to the

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

▼ The MNP function is based on a Number Portability Database (NPDB) for

▼ The portability relates only to a set of PLMNs called "PORTABILITY

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

5.2 MNP-SRF procedures

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

Number Range INDIRECT ROUTING Subscription Network

▼ CALL ROUTING TO A MOBILE

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

SRI (MSISDN) SRI res (RN + MSISDN)

IAM (MSISDN) IAM (MSRN)

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

Originating Number Range PORTABILITY

SRI (MSISDN) MNP

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

Originating IAM (MSRN)

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

▼ If the MSISDN is ported in another PLMNb, the message is transmitted to the

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

SRI_for_SM ack (VMSCB address)

SRI_for_SM (MSISDN) 4 CdPA = HLRb address

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

z On call rerouting to the subscription network:

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

z As for any terminating call, the called party number (RN+MSISDN)

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

z (Optional) checks can be used to detect inconsistencies between the

z These checks can be carried out:

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

5.3 Setting up MNP

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

z In the GMSC, a new family of counters is provided to total

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

With option F-SA-012, the "SN" parameter can be extended to 14 digits:

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

z MAP version management:

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01

5.4 Data structure

© Alcatel University - 8AS 90200 0738 VH ZZA Ed.01