C.6 Handling of MAP to ISUP mapping (informative)
23.0663GPPRelease 17Stage 2Support of Mobile Number Portability (MNP)Technical realizationTS
Different configurations can be possible within a portability domain depending on the versions of MAP and ISUP protocols being used. The following clauses describe possible interworking scenarios.
C.6.1 ETSI Mapping direction: ISUP to MAP
The GMSC always constructs the Send Routeing Info message using the MSISDN. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM.
C.6.2 ETSI Mapping direction: MAP to ISUP
In MAP SRIack messages from NPLR, MAP versions 1 and 2 only support concatenate addressing for MNP. If MSISDN parameter is present in the SRIack, this means that separate addressing is used in MAP; this is only possible if MAP version 3 is used. MAP version 3 can also support concatenate addressing. In all cases, when a Routeing Number is returned, it is included in the MSRN parameter of the SRIack.
Regardless of how MAP is established, the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [6]):
1. CdPN parameter includes only the MSISDN.
2. CdPN parameter includes both RN and MSISDN concatenated.
3. CdPN parameter includes the MSISDN and NRN parameter includes the Routeing Number.
4. CdPN parameter includes the Routeing Number and CDN parameter includes the MSISDN.
In all cases, the method to transport the routeing number in the IAM depends on the interfaces agreed by the operators in the portability domain.
C.6.3 ANSI Mapping direction: ISUP to MAP
The GMSC always constructs the Send Routeing Info message using the MSISDN. If the incoming IAM corresponds to a ported number the GMSC shall retrieve the MSISDN from the corresponding parameter in the IAM.
The IAM message is specified for ANSI ISUP implementation in [8] and [9].
C.6.4 ANSI Mapping direction: MAP to ISUP
In MAP SRIack messages from NPLR, MAP versions 1 and 2 only support concatenate addressing for MNP. If MSISDN parameter is present in the SRI Ack, this means that separate addressing is used in MAP; this is only possible if MAP version 3 is used. MAP version 3 can also support concatenate addressing. In all cases, when a Routeing Number is returned, it is included in the MSRN parameter of the SRI Ack.
Regardless of how MAP is established, the possible mappings of the parameters in ISUP IAM message is one of these 4 options (see also [8] and [9]):
|
MAP Parameters |
SRI Ack |
ISUP Parameters |
IAM |
|
|
IMSI |
Subscriber IMSI |
CdPN |
MSRN |
|
|
MSRN |
MSRN |
MAPS TO |
GAP |
N/A |
|
MSISDN |
Not Present |
FCI Bit M Indicator |
1 |
|
|
MNP Indicator |
Not Present |
|
MAP Parameters |
SRI Ack |
ISUP Parameters |
IAM |
|
|
IMSI |
Default IMSI |
CdPN |
Dialled DN |
|
|
MSRN |
Dialled DN |
MAPS TO |
GAP |
N/A |
|
MSISDN |
Not Present |
FCI Bit M Indicator |
1 |
|
|
MNP Indicator |
NotKnownToBePorted |
|
MAP Parameters |
SRI Ack |
ISUP Parameters |
IAM |
|
|
IMSI |
Default IMSI |
CdPN |
RN |
|
|
MSRN |
RN |
MAPS TO |
GAP |
Dialled DN |
|
MSISDN |
Dialled DN |
FCI Bit M Indicator |
1 |
|
|
MNP Indicator |
OwnNumber |
|
MAP Parameters |
SRI Ack |
ISUP Parameters |
IAM |
|
|
IMSI |
Default IMSI |
CdPN |
RN |
|
|
MSRN |
RN |
MAPS TO |
GAP |
Dialled DN |
|
MSISDN |
Dialled DN |
FCI Bit M Indicator |
1 |
|
|
MNP Indicator |
Foreign Number PortedToForeign |
In all cases, the method to transport the routing number in the IAM depends on the interfaces agreed by the operators in the portability domain.
Annex D:
Void
Annex E (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
#03 |
Transferred to 3GPP CN2 |
||||||
|
Aug 1999 |
3.0.0 |
||||||
|
#05 |
001 |
Harmonisation of terminology interrogating |
3.1.0 |
||||
|
#05 |
002 |
Proposed changes to B.4.2 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as Higher-level Relay |
3.1.0 |
||||
|
#05 |
003 |
Clarification of NPLR functionality in not known to be ported case |
3.1.0 |
||||
|
#07 |
007 |
1 |
Editorial cleanup |
3.2.0 |
|||
|
#07 |
008 |
4 |
Alignment of IN interface with Fixed Networks |
3.2.0 |
|||
|
#07 |
009 |
3 |
Detection of database synchronisation errors in SRF |
3.2.0 |
|||
|
#07 |
012 |
2 |
Result of Public Enquiry 9953 |
3.2.0 |
|||
|
#07 |
015 |
1 |
Clarification of NPDB error detection and MNP specific call handling |
3.2.0 |
|||
|
#08 |
019 |
2 |
North American Service Provider Number Portability impacts for Mobile Number Portability |
3.3.0 |
|||
|
#11 Mar 2001 |
Release 4 after CN#11 |
4.0.0 |
|||||
|
#16 Mar 2002 |
References updated |
4.0.1 |
|||||
|
#16 Jun 2002 |
Release 5 after CN#16 |
5.0.0 |
|||||
|
#20 Jun 2003 |
023 |
1 |
IN-based solution for correct charging of calls to ported or non-ported subscribers originated by pre-paid subscribers |
5.1.0 |
|||
|
#21 Sep 2003 |
026 |
1 |
Incorrect CAMEL pre-paid charging in MNP networks |
5.2.0 |
|||
|
CN#22 Dec 2003 |
027 |
Incorrect implementation of CR 023r1 |
5.3.0 |
||||
|
CN#22 Dec 2003 |
028 |
1 |
MNP correction for prepaid charging |
5.3.0 |
|||
|
CN#26 |
Release 6 after CN#26 |
6.0.0 |
|||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
CT#46 |
– |
Update to Rel-9 version (MCC) |
9.0.0 |
||||
|
2011-03 |
– |
Update to Rel-10 version (MCC) |
10.0.0 |
||||
|
2012-09 |
– |
Update to Rel-11 version (MCC) |
11.0.0 |
||||
|
2014-09 |
– |
Update to Rel-12 version (MCC) |
12.0.0 |
||||
|
2015-12 |
Update to Rel-13 version (MCC) |
13.0.0 |
|||||
|
2017-03 |
– |
Update to Rel-14 version (MCC) |
14.0.0 |
||||
|
2018-06 |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
||||
|
2020-07 |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
||||
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |