C.6 Handling of MAP to ISUP mapping (informative)
03.663GPPStage 2Support of GSM Mobile Number Portability (MNP)TS
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 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 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 [7]):
- CdPN parameter includes only the MSISDN
- CdPN parameter includes both RN and MSISDN concatenated
- CdPN parameter includes the MSISDN and NRN parameter includes the Routeing Number
- CdPN parameter includes the Routeing Number and CDN parameter includes the MSISDN
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 (informative):
Status of Technical Specification GSM 03.66
This annex lists all changes made to the present document since its initial approval by the ETSI committee, SMG.
|
SMG# |
Tdoc |
CN2 Tdoc |
VERS |
CR |
Phase |
CAT |
SUBJECT |
New Version |
|
s29 |
P99-458 |
N2-99282 |
7.0.0 |
A001r1 |
R98 |
F |
Alignment between 03.66 Part one and Normative Annex C Description of call related functionality |
7.1.0 |
|
s29 |
P99-458 |
N2-99283 |
7.0.0 |
A002r1 |
R98 |
C |
Editorial clarifications and alignments |
7.1.0 |
|
s29 |
P99-458 |
N2-99284 |
7.0.0 |
A003r1 |
R98 |
F |
Routeing conventions in a Portability Cluster |
7.1.0 |
|
s29 |
P99-458 |
N2-992671 |
7.0.0 |
A004r1 |
R98 |
F |
Adding of MNP indicator to the SRI ack |
7.1.0 |
|
s29 |
P99-458 |
N2-99672 |
7.0.0 |
A005 |
R98 |
F |
Corrections on MNP |
7.1.0 |
|
CN#05 |
NP-99302 |
N2-99948 |
7.1.0 |
A006r1 |
R98 |
F |
Harmonisation of terminology |
7.2.0 |
|
CN#05 |
NP-99302 |
N2-99870 |
7.1.0 |
A007 |
R98 |
F |
Proposed changes to B.4.2 Delivery of SMS to a Non-ported Number – Direct Routeing – MNP-SRF acts as Higher-level Relay |
7.2.0 |
|
CN#05 |
NP-99302 |
N2-99D08 |
7.1.0 |
A009r1 |
R98 |
F |
Clarification of NPLR functionality in not known to be ported case |
7.2.0 |
|
s30 |
Version approved by SMG#30 |
7.2.0 |
||||||
|
CN#07 |
NP-000072 |
N2B000432 |
7.2.0 |
A014r2 |
R98 |
D |
Result of Public Enquiry 9953 |
7.3.0 |
|
7.3.0 |
Update to Version 7.3.1 for Publication |
7.3.1 |