21.2.1 General

29.0023GPPMobile Application Part (MAP) specificationRelease 17TS

The message flows for successful retrieval of routeing information for a mobile terminating call are shown in figure 21.2/1 (mobile terminating call which has not been optimally routed) and 21.2/2 (mobile-to-mobile call which has been optimally routed). The message flow for successful retrieval of routeing information for a gsmSCF initiated call is shown in figure 21.2/3. The message flow for a successful Mobile Terminating Roaming Forwarding procedure is shown in figure 21.2/4.

1) I_IAM (Note 1)

2) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 2)

3) MAP_PROVIDE_SUBSCRIBER_INFO_req/ind (Note 3, Note 4)

4) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf (Note 4)

5) MAP_SEND_ROUTING_INFORMATION_rsp/cnf (Note 4)

6) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 4)

7) MAP_PROVIDE_ROAMING_NUMBER_req/ind

8) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf

9) MAP_SEND_ROUTING_INFORMATION_rsp/cnf

10) I_IAM (Note 1)

11) MAP_RESTORE_DATA_req/ind (Note 4)

12) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 4)

13) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 4)

12) MAP_RESTORE_DATA_rsp/cnf (Note 4)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations and ETSI specification:

– Q.721‑725 ‑ Telephone User Part (TUP);

– ETS 300 356-1 ‑ Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services.

NOTE 2: This service may also be used by an ISDN exchange for obtaining routing information from the HLR.

NOTE 3: As a network operator option, the HLR sends MAP_PROVIDE_SUBSCRIBER_INFORMATION to the VLR. For further details on the CAMEL procedures refer to 3GPP TS 23.078 [98].

NOTE 4: Services printed in italics are optional.

Figure 21.2/1: Message flow for retrieval of routeing information (non-optimally routed call)

1) I_IAM (Note 1)

2) MAP_SEND_ROUTING_INFORMATION_req/ind

3) MAP_PROVIDE_SUBSCRIBER_INFO_req/ind (Note 2)

4) MAP_PROVIDE_SUBSCRIBER_INFO_rsp/cnf (Note 2)

5) MAP_PROVIDE_ROAMING_NUMBER_req/ind (Note 2)

6) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf (Note 2)

7) MAP_SEND_ROUTING_INFORMATION_rsp/cnf

8) I_IAM (Note 1)

9) MAP_RESTORE_DATA_req/ind (Note 3)

10) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3)

11) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3)

12) MAP_RESTORE_DATA_rsp/cnf (Note 3)

NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. For further details on the TUP and ISUP procedures refer to the following ITU-T Recommendations & ETSI specification:

– Q.721‑725 ‑ Telephone User Part (TUP);

– ETS 300 356-1 ‑ Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services.

NOTE 2: For Optimal Routeing phase 1, only one of the information flows for Provide Subscriber Info and Provide Roaming Number is used.

NOTE 3: Services printed in italics are optional.

Figure 21.2/2: Message flow for retrieval of routeing information (optimally routed call)

1) MAP_SEND_ROUTING_INFORMATION_req/ind

2) MAP_SEND_ROUTING_INFORMATION_rsp/cnf (Note 1)

3) MAP_SEND_ROUTING_INFORMATION_req/ind (Note 1)

4) MAP_PROVIDE_ROAMING_NUMBER_req/ind

5) MAP_PROVIDE_ROAMING_NUMBER_rsp/cnf

6) MAP_SEND_ROUTING_INFORMATION_rsp/cnf

7) MAP_RESTORE_DATA_req/ind (Note 1)

8) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 1)

9) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 1)

10) MAP_RESTORE_DATA_rsp/cnf (Note 1)

NOTE 1: Services printed in italics are optional.

Figure 21.2/3: Message flow for retrieval of routeing information for a gsmSCF initiated call

The following MAP services are used to retrieve routing information:

MAP_SEND_ROUTING_INFORMATION see clause 10.1;

MAP_PROVIDE_ROAMING_NUMBER see clause 10.2;

MAP_PROVIDE_SUBSCRIBER_INFO see clause 8.11.2;

MAP_RESTORE_DATA see clause 8.10.3.

1) I_IAM

2) MAP_CANCEL_LOCATION_req/ind

3) MAP_PROVIDE_ROAMING_NUMBER_req/ind

4) MAP_ PROVIDE_ROAMING_NUMBER_rsp/cnf

5) I_IAM

Figure 21.2/4: Message flow for Mobile Terminating Roaming Forwarding

The following MAP services are used for the Mobile Terminating Roaming Forwarding procedure:

MAP_PROVIDE_ ROAMING_NUMBER see clause 10.2;