19.1 Location management Procedures

29.1203GPPMobile Application Part (MAP) specification for Gateway Location Register (GLR)Release 17TS

For non-GPRS subscribers, this subclause comprises a number of processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP SSN (VLR or HLR) and the Application Context. The processes in the GLR interact with the processes in the VLR or HLR defined in 29.002. The followings show the relations between the protocol processes in the GLR and the processes in the other node.

Process Update Location (VLR-GLR):

– Initiator: Update_Location_Area_VLR or Update_Location_HLR;

– Responder: Update_Location_GLR.

Process Update Location (GLR-HLR):

– Initiator: GLR_Update_Location_HLR;

– Responder: Update_Location_HLR.

Process Cancel Location (VLR-GLR):

– Initiator: GLR_Cancel_Location_VLR;

– Responder: Cancel_Location_VLR.

Process Cancel Location (GLR-HLR):

– Initiator: Cancel_Location_HLR;

– Responder: Cancel_Location_GLR.

Process Purge MS (VLR-GLR):

– Initiator: Purge_MS_VLR;

– Responder: Purge_MS_GLR.

Process Purge MS (GLR-HLR):

– Initiator: GLR_Purge_MS_HLR;

– Responder: Purge_MS_HLR.

A Location Management Co-ordinator in the GLR co-ordinates the two protocol processes "Update_Location_GLR" (subclause 19.1.2) and "RESTORE_DATA_GLR" (subclause 19.2) that are addressed by the same application context.

On receipt of a dialogue request for the Location Management Application Context, the location Management_Coordinator_GLR will:

– Terminate the process in case of parameter problems; or

– Revert to MAP version Vr protocol if the VLR requests version Vr protocol; or

– Continue as described in the following, if the dialogue is accepted.

The protocol process is created depending on the first primitive received from the MAP service provider within this dialogue:

– Update_Location_GLR if the primitive is a MAP_UPDATE_LOCATION indication.

– RESTORE_DATA_GLR if the primitive is a MAP_RESTORE_DATA indication.

If a MAP_NOTICE indication is received instead, the dialogue towards the VLR is terminated and the process returns to idle state.

After creation of the protocol process the service primitive received from the MAP service-provider is passed to the protocol process. Henceforth, the co-ordinator will relay all service primitives from MAP service-provider to the MAP service-user and vice versa, until a request or indication for dialogue termination is received. This last primitive will be relayed, too, before the Co-ordinator process returns to idle state.

Figure 19.1.1/1: Process Location_Management_Coordinator_GLR

For GPRS subscribers, this subclause comprises a number of other processes to handle the mobile nature of the subscriber. The processes will be addressed by SCCP Sub-System Number (SGSN or HLR) and the Application Context. The processes in the GLR interact with the processes in the VLR, SGSN or HLR defined in 29.002. The followings show the relations between the processes in the GLR and the processes in the other node:

Process GPRS Update Location (VLR or SGSN-GLR):

Initiator: GPRS_Update_Location_Area_VLR, or SGSN_Update_HLR.

Responder: Update_GPRS_Location_GLR.

Process GPRS Update Location (GLR-HLR):

Initiator: GLR_Update_GPRS_Location_HLR.

Responder: Update_GPRS_Location_HLR.

Process Cancel Location (SGSN-GLR):

Initiator: GLR_Cancel_Location_SGSN.

Responder: Cancel_Location_SGSN.

Process Cancel Location (GLR-HLR):

Initiator: Cancel_GPRS_Location_HLR.

Responder: Cancel_GPRS_Location_GLR.

Process Purge MS (SGSN-GLR):

Initiator: Purge_MS_SGSN.

Responder: Purge_MS_GLR_for_GPRS.

Process Purge MS (GLR-HLR):

Initiator: GLR_Purge_MS_HLR_for_GPRS.

Responder: Purge_MS_HLR.