Rel Train 2002 112 USMNP v10

North American
Mobile Number Portability

CR SMSC_2002_112
Release Notes SMSC_V04_61_012; SMSC_V05_01_011
Sergey Marin
Welcome to LogicaCMG
January 22, 2016
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
January 22,
Mobile Number Portability in the US
Mobile Number Portability (MNP) = a service:

switch subscription to another operator,
keep the same mobile number
The MNP in the US is forced by law

Not enabled in the whole country at once
Some areas are or will be portable earlier than others
January 22,
Portability ranges
Some operators want to divide the NPA portability ranges into

sub ranges.
The prefix of such sub range consists either of NPA-NXX or of
NPA-NXX-X
January 22,
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
January 22,
Portability ranges
Such a range from which at least one number is ported is called

contaminated
If certain number not in contaminated range -> this number is
surely not-ported
Organisations in the US maintain and publish the list of:
portable NPA ranges
contaminated ranges.
Not all operators want such level of detail: the NPA portability
ranges suffice some of them
January 22,
Portability ranges
1-347-001-1234
T-Mobile USA
Numerex
The sub-range 1-347-001-XXX becomes contaminated

January 22,
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
January 22,
Existing Mobile Number Portability

MO case (release 4.5)
Mobile Number Portability is enabled -> SMSC does not know if
the originator of the SMS is an subscriber of the operator
If information from the message does not tell that -> SMSC
performs an SRI request to a HLR
The attribute SMSC_COMMON/NUMBER_PORTABILITY
needs to be enabled to perform this SRI request (refer to CR
SMSC_2001_041 for details)
January 22,

MO case (release 4.5) continued
Which file the SMSC uses 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
January 22,

MO case (release 4.5) continued
1
January 22,
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
January 22,
Solution description
Portable ranges configured in GIW_HLR_ADDR_MO.DAT file

by means of prefixes
The SMSC performs the SRI request for an MO message only if
the address of the originator matches a prefix
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).
January 22,
The situation before the change

(release 4.5)
If the SMSC had to perform an MO SRI request, the SMSC
looked in the routing file (which is GIW_HLR_ADDR_MO.DAT if
the attribute MNP_LOCAL_SRI_ENABLED is ON)
If the SMSC could not find a match it referred to the attribute
GIW_COMMON/NO_IMSI_ACTION_REJECT
If this attribute was set to YES, the SMSC forwarded the
message to the service centre, no SRI request was made
If this attribute was set to NO, the SMSC rejected the message
January 22,
A possible solution
We set the attribute

GIW_COMMON/NO_IMSI_ACTION_REJECT to NO
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
January 22,
A possible solution
A shortcoming of this solution is that the attribute

GIW_COMMON/NO_IMSI_ACTION_REJECT needs to be set
to NO
It may be needed to set this attribute to YES to handle the
situations when we do not receive an IMSI from the HLR
January 22,
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
January 22,
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
January 22,

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
January 22,
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
January 22,
Changing configuration
The value of the attribute MNP_RANGE_CFG_ENABLED can be

changed on the fly
Note: the attribute MNP_RANGE_CFG_ENABLED has no effect if
the MNP_LOCAL_SRI_ENABLED and NUMBER_PORTABILITY
are disabled.
These last two attributes can not be changed on the 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 described on the notes page to avoid unwanted loss
of dialogues
January 22,
The scenarios
The following slides present some scenarios with respect to this

functionality
January 22,
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
January 22,
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)
January 22,
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
January 22,
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
January 22,
References
Release note: SMSC_V04_61_012 (for release 4.6)
ATP: Option 16e
Requirements, requirements analysis and change request
description (CR SMSC_2002_112):
http://telecomi/teams/smsc_req/SMSC/Baseline 4.htm
January 22,
Questions
January 22,

Rel Train 2002 112 USMNP v10

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 USMNP v10

Caricato da

Copyright:

Formati disponibili

North American

Mobile Number Portability

January 22, 2016

Numbering according to the

Mobile Number Portability in the US

Mobile Number Portability (MNP) = a service:

The MNP in the US is forced by law

Some operators want to divide the NPA portability ranges into

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

Portable ranges configured in GIW_HLR_ADDR_MO.DAT file

The situation before the change

We set 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

The following slides present some scenarios with respect to this

Potrebbero piacerti anche