Content for TS 23.066 Word version: 18.0.0
C.5 Contents of the messages
C.5.1 Send Routeing Info
C.5.2 Send Routeing Info ack
C.6 Handling of MAP to ISUP mapping (informative)
C.6.1 ETSI Mapping direction: ISUP to MAP
C.6.2 ETSI Mapping direction: MAP to ISUP
C.6.3 ANSI Mapping direction: ISUP to MAP
C.6.4 ANSI Mapping direction: MAP to ISUP
$ Change history
C.5 Contents of the messages p. 79
This clause contains detailed description of the messages shown in this part B of the specification.
The contents of the messages used on the gsmSCF - MNP-SRF interface are specified in 3G TS 23.078. When the message is sent from the NPLR to the gsmSCF, the MNP specific information are defined as in clause C.5.2. The gsmSCF may transit the information received from NPLR to the gateway MSC with the CAP Connect message in order to avoid a subsequent SRI message.
C.5.1 Send Routeing Info p. 80
The contents of this message are specified in 3G TS 23.018.
C.5.2 Send Routeing Info ack p. 80
The contents of this message are specified in 3G TS 23.018. In the case that the message is sent from the NPLR to the GMSC, the following MNP specific information is defined:
| Information element name | Required | Description |
|---|---|---|
| Imsi | M | The IMSI returned by an NPLR is a generic IMSI, i.e. it is not tied necessarily to the Subscriber. MCC and MNC values in this IMSI shall point to the Subscription Network of the B Subscriber |
| Msrn | C | When returned from the NPLR, this parameter contains a Routeing Number that points to Subscription Network. If concatenate addressing is used, it also contains the MSISDN in addition to the Routeing Number.In the case of a number which is not known to be ported, the Routeing Number may be omitted as an operator option. If the routeing number is omitted, this parameter contains only the MSISDN. |
| Msisdn | C | MSISDN of the B subscriber. This information element shall be present if MSRN contains the routeing number to reach the subscription network for B subscriber and the MSISDN is not contained in the MSRN information element. |
| MNP Indicator | U | Indicates the number portability status of the subscriber. |
C.6 Handling of MAP to ISUP mapping (informative) p. 80
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 p. 80
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 p. 80
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]):
- 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.
C.6.3 ANSI Mapping direction: ISUP to MAP p. 81
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 p. 81
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 PortedOut |
| 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 Network |
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.
D Void
$ Change history p. 83
