Rel Train 2002 112 v0.2

North American
Mobile Number Portability

Sergey Marin
Consultant
Welcome to LogicaCMG
9 November 2015
Numbering according to the

North American Numbering Plan
In the US a mobile number includes the area prefix this number
belongs to (Numbering Plan Area or NPA).
A number has a form NPA-NXX-XXXX
9 November 2
Mobile Number Portability in the US
Mobile Number Portability = a service that allows a mobile

subscriber to switch her/his subscription to another operator
while keeping the same mobile number
The mobile operators in the US are obliged to support the
mobile number portability
The mobile number portability will not be enabled in the whole
country at once. Instead, some areas will became portable
earlier than the others
9 November 3
Portability ranges
To handle the performance issues the mobile operators

proposed to divide the portable area code based ranges into
sub ranges.
The prefix of such a sub range consists of NPA-NXX-X
9 November 4
Portability ranges
District Columbia
1-202-NXX-XXXX
The US num.range
1-NPA-NXX-XXXX
New York
1-347-NXX-XXXX
New York
1-212-NXX-XXXX
Sub ranges
1-347-000
1-347-001
1-347-002
9 November 5
Portability ranges
Such a range from which at least one number is ported is called

contaminated
If certain number is not in a contaminated range, this number
could not have been ported yet
There are various organisations in the US that maintain and
publish the list of portable area code ranges and contaminated
ranges.
9 November 6
Portability ranges
1-347-001-1234
T-Mobile USA
Numerex
The sub-range 1-347-001-XXX becomes contaminated

9 November 7
Mobile Number Portability in the US

Summary
So all mobile numbers in the US can be divided into two
categories of ranges
Ranges for which we know that they contain only not ported
numbers
Ranges that may contain ported numbers.
We shall call a range from the second category a portable

range
9 November 8
Existing Mobile Number Portability

MO case
If the Mobile Number Portability is enabled, the SMSC in
general can not know whether the originator of the SMS is an
own subscriber of the operator
If the SMSC on basis of the information present in the message
can not say whether the originator is an own subscriber the
SMSC will perform an SRI request to a HLR to find this out
The attribute SMSC_COMMON/NUMBER_PORTABILITY
needs to be enabled to perform this SRI request
9 November 9

MO case
Which file is used to build the SCCP address for an MO SRI
request depends on the setting of the attribute
SMSC_COMMON/LOCAL_SRI_ENABLED
If this attribute is enabled the GIW uses a special file
GIW_HLR_ADDR_MO.DAT
If this attribute is disabled the GIW uses the same file as the file
used for an MT SRI request: GIW_HLR_ADDR.DAT
9 November 1

MO case
1
9 November 1
Problem Description
The operators in the US want that the SMSC performs the MO

SRI requests only for the numbers that lie in the portable
ranges
9 November 1
Solution description
The portable ranges can be configured in the

GIW_HLR_ADDR_MO.DAT file by means of prefixes
The SMSC will perform the SRI request for an MO message
only if the address of the originator matches a prefix in this file
Note: the attributes
SMSC_COMMON/NUMBER_PORTABILITY and
SMSC_COMMON/MNP_LOCAL_SRI_ENABLED need to be
enabled
Note: in certain sense this is an extension of the Country Code
list already used for the mobile number portability (attribute
SMSC_COMMON/MNP_CC_LIST)
9 November 1
The situation before
If the SMSC needed to perform an MO SRI request it looked in

the routing file (GIW_HLR_ADDR_MO.DAT if the attribute
MNP_LOCAL_SRI_ENABLED was ON)
If the SMSC could not find a match it referred to the attribute
GIW_COMMON/NO_IMSI_ACTION_REJECT
If this attribute was enabled the SMSC forwarded the message
to the service centre, no SRI request was made
If this attribute was disabled the SMSC reject the message if no
match was found
9 November 1
A possible solution
We disable the attribute

GIW_COMMON/NO_IMSI_ACTION_REJECT
We configure the portable ranges in the
GIW_HLR_ADDR_MO.DAT
We enable the attributes
SMSC_COMMON/NUMBER_PORTABILITY and
SMSC_COMMON/MNP_LOCAL_SRI_ENABLED
If the SMSC does not find a match it does not do an SRI and it
does not reject the message
9 November 1
A possible solution
A shortcoming of this solution is that the attribute

GIW_COMMON/NO_IMSI_ACTION_REJECT needs to be
disabled
It may be needed to set this attribute to ON to handle the
situations when we do not receive an IMSI from the HLR
9 November 1
The proposed solution
We introduce a new attribute

GIW_COMMON/MNP_RANGE_CFG_ENABLED
This attribute can take values ON or OFF
This attribute is licensed
If this attribute is enabled the SMSC shall consider a no match
in the GIW_HLR_ADDR_MO.DAT as normal
If this attribute is disabled the SMSC shall consider a no match
in the GIW_HLR_ADDR_MO.DAT as fault
9 November 1
If the SMSC considers a no match in the

GIW_HLR_ADDR_MO.DAT as normal the SMSC shall accept the
message if the message passes other applicable MO checks
9 November 1

GIW_HLR_ADDR_MO.DAT as fault and
the item GIW_COMMON/NO_IMSI_ACTION_REJECT is Yes -> the
SMSC shall reject the message
GIW_HLR_ADDR_MO.DAT as fault and
the item NO_IMSI_ACTION_REJECT is No -> the SMSC shall accept
the message if the message passes other applicable MO checks
9 November 1
Note the relation between the attributes

GIW_COMMON/MNP_RANGE_CFG_ENABLED &
GIW_COMMON/NO_IMSI_ACTION_REJECT in case no match is
found in the GIW_HLR_ADDR_MO.DAT file
MNP_RANGE_CFG MNP_RANGE_CFG
_ENABLED is ON
_ENABLED is OFF
NO_IMSI_ACTION_REJECT the SMSC shall accept The SMSC shall reject
the message if the
the message
is YES
message passes other
applicable MO checks
NO_IMSI_ACTION_REJECT the SMSC shall accept
the message if the
is NO
the SMSC shall accept

the message if the
9 November 2
Changing configuration
The value of the attribute MNP_RANGE_CFG_ENABLED can be

changed on-fly
Note: the attribute MNP_RANGE_CFG_ENABLED has no effect if
the MNP_LOCAL_SRI_ENABLED and NUMBER_PORTABILITY
are disabled. The values of these attributes can not be changed on-fly
Adding or removing of ranges to the GIW_HLR_ADDR_MO.DAT
can be done without loss of service:
The GIW entities should be restarted one by one after the file has been
updated
Follow the procedure to avoid unwanted loss of dialogues
9 November 2
Scenario 1
MNP_RANGE_CFG_ENABLED is OFF AND
NO_IMSI_ACTION_REJECT is YES
ms
Switch
HLR
GIW
SC
submit
submit_sm_req
MSISDN_not_match_in_GIW_HLR_ADDR_MO
attribute_MNP_RANGE_CFG_ENABLED_is_OFF
attr_NO_IMSI_ACTION_REJECT_is_NO
RP_submit
RP_submit_resp
submit_resp
submit_sm_resp
9 November 2
Scenario 2
MNP_RANGE_CFG_ENABLED is OFF AND
ms
Switch
submit
HLR
GIW
SC
submit_sm_req
attribute_MNP_RANGE_CFG_ENABLED_is_OFF
attr_NO_IMSI_ACTION_REJECT_is_YES
submit_resp
(Negative)
submit_sm_resp
(Negative)
9 November 2
Scenario 3
MNP_RANGE_CFG_ENABLED is ON AND
ms
Switch
submit
HLR
GIW
SC
submit_sm_req
attribute_MNP_RANGE_CFG_ENABLED_is_ON
attr_NO_IMSI_ACTION_REJECT_is_YES
RP_submit
submit_resp
submit_sm_resp
RP_submit_resp
9 November 2
Scenario 4
Match found in GIW_HLR_ADDR_MO.DAT
MS
Switch
submit
HLR
GIW
SC
submit_sm
MSISDN_matches_GIW_HLR_ADDR_MO_file
and of course if other
MNP conditions are satisfied
according to the CR 2001_041
SendRoutingInfoForSM_req
SendRoutingInfoForSM_resp
submit_resp
submit_sm_resp
RP_Submit
RP_Response
9 November 2
References
Release note: SMSC_V04_61_012 (for release 4.6)
ATP: Option 16e
Design:
Requirements, requirements analysis and change request
description (CR SMSC_2002_112):
http://telecomi/teams/smsc_req/SMSC/Baseline 4.htm
9 November 2
Questions
9 November 2

Rel Train 2002 112 v0.2

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Rel Train 2002 112 v0.2

Caricato da

Copyright:

Formati disponibili

North American

Mobile Number Portability

Numbering according to the

Mobile Number Portability in the US

Mobile Number Portability = a service that allows a mobile

To handle the performance issues the mobile operators

Such a range from which at least one number is ported is called

The sub-range 1-347-001-XXX becomes contaminated

Mobile Number Portability in the US

We shall call a range from the second category a portable

Existing Mobile Number Portability

Existing Mobile Number Portability

Existing Mobile Number Portability

The operators in the US want that the SMSC performs the MO

The portable ranges can be configured in the

The situation before

If the SMSC needed to perform an MO SRI request it looked in

We disable the attribute

A shortcoming of this solution is that the attribute

The proposed solution

We introduce a new attribute

If the SMSC considers a no match in the

If the SMSC considers a no match in the

Note the relation between the attributes

the SMSC shall accept

The value of the attribute MNP_RANGE_CFG_ENABLED can be

Potrebbero piacerti anche