Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.018  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.2.1   5.2.2   5.2.3   5.2.4   5.3   6…   7…   7.2…   7.3…   8…   A…

 

5.2.4  Mobile Terminating Roaming Forwarding Call during Retrieval of Routeing Information |R10|p. 29

The information flow for mobile terminating roaming forwarding (MTRF) call during retrieval of routeing information is shown in Figure 4d. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC, if the old and the new terminating MSC/VLRs support the MT Roaming Forwarding procedure. The HLR should also support the Mobile Terminating Roaming Forwarding procedure in order to ensure that roaming forwarding can be offered in all scenarios (e.g. in case of IMSI in the LAU Request from UE); an HLR that supports Optimal Routeing shall support the requirements defined in this clause to ensure that charging requirements for optimal routeing are never contravened. The procedure may e.g. apply during pre-paging if the GMSC, HLR and old MSC/VLR support pre-paging.
The principles and requirements specified for MT Roaming Forwarding Call after successful Retrieval of Routeing Information (see clause 5.2.3) shall also apply for MT Roaming Forwarding Call during Retrieval of Routeing Information with the following modifications or clarifications.
When an MSRN is retrieved successfully from the new MSC/VLR, the old MSC/VLR shall return the received MSRN within the MAP Provide Roaming Number response to the HLR, which allows the call to be routed from the GMSC to the new MSC.
Copy of original 3GPP image for 3GPP TS 23.018, Fig. 4d: Information flow for a mobile terminating roaming forwarding call during Retrieval of Routeing Information
Up
The sequence follows the normal MT terminating call with the following differences:
Step 1-2.
Same as steps 1 and step 2 in Figure 4c.
Step 3.
Same as step 3 in Figure 4c, with the addition that the HLR shall not authorise MTRF between the old and the new MSCs if routing the call between the GMSC and the new MSC contravenes charging requirements if Optimal Routeing is supported (see TS 23.079).
Step 4.
Same as step 4 in Figure 4c, where the old MSC/VLR stops pre-paging.
Step 5.
Same as step 5 in Figure 4c.
Step 6.
Same as step 6 in Figure 4c. If the OR interrogation indicator is received in the PRN request, the new VLR shall return a PRN negative response if it does not support Optimal Routeing (see TS 23.079).
Step 7.
Same as step 7 in Figure 4c.
Step 8.
The new MSC/VLR returns to the old VLR a MAP Providing Roaming Number response including the MSRN, the new VMSC Address, and if the new MSC/VLR supports the MAP Release Resource procedure, the ReleaseResourcesSupported flag.
Step 9.
Upon receipt of the MSRN from the new VLR, the old VLR returns the PRN Ack to the HLR including the MSRN and the VMSC Address received from the new VLR, and the ReleaseResourcesSupported flag if received from the new MSC/VLR.
Step 10.
If the HLR needs to return the VMSC Address to the GMSC (as per the conditions specified in TS 29.002), and if a VMSC Address was received with an MSRN in the PRN Ack, the HLR shall pass in the SRI ack to the GMSC the MSRN and the VMSC Address received in the PRN ack.
Receipt of the MSRN from the HLR enables the GMSC to relay the call towards the new MSC.
Step 11.
Same as step 10 in Figure 4c.
Up

Up   Top   ToC