7.13 The interaction with Super-Charger
23.1193GPPGateway Location Register (GLR)Release 17Stage 2TS
Following clauses show the location updating procedures in the case that the serving nodes in the network with the GLR support the Super-Charger functionality.
7.13.1 First Location Updating Procedure in the Super-Charged network
The first location updating procedure in a Super-Charged network is illustrated in figure 7.13/1. Each step is explained in the following list.
Figure 7.13/1: First Location Updating Procedure in the case that visited NW supports the Super-Charger features
Procedure:
1) When the GLR receives an Update Location or Update GPRS Location message from a serving node (i.e., VLR or SGSN) and does not hold the subscriber’s information for the user (ex. at the first location updating to the GLR), it relays the message without age indicator (if age indicator is received from the serving node, the GLR deletes it) to the HLR.
2) The HLR stores the address and number of serving node. Thereafter the HLR initiates insert subscriber data procedure and cancel location procedure (only if both the HLR and previous serving node support the Super-Charger features). When the GLR receives Insert Subscriber Data message from the HLR, the GLR creates an age indicator and stores the subscriber’s information in the message and transports it to the serving node with the age indicator.
3) After these procedures, the HLR replies to an Update Location or Update GPRS Location message from the GLR and the GLR transports the response to the serving node.
7.13.2 Second and further Location Updating Procedure in the Super-Charged networks
The second and further location updating procedure in a Super-Charged network is illustrated in figure 7.13/2. Each step is explained in the following list.
Figure 7.13/2: Second and further Location Updating Procedure in the case that visited NW supports the Super-Charger features
Procedure:
1) When the GLR receives an Update Location or Update GPRS Location message with an age indicator from newly visited serving node (i.e. VLR or GSSN) and holds the subscriber information for the user (i.e. at second or further location updating to the GLR), it stores the address and number of newly visited serving node included in the received message.
2) The GLR does not initiate cancel location procedure if the previous node supports the Super-Charger features.
3) When the age indicator from the serving node indicates the serving node does not request the subscription data, the GLR checks if the subscription data retained in serving node is consistent with that stored in the GLR. If so, the GLR shall not send subscription data to the newly visited serving node. Otherwise the GLR initiates the insert subscriber procedure to the serving node.
4) After these procedures, the GLR replies to an Update Location or Update GPRS Location message from the serving node.
7.13.3 Cancel Location Procedure in the Super-Charged networks
The cancel location procedure in a Super-Charged network when MS leave the network is illustrated in figure 7.13/3. Each step is explained in the following list.
Figure 7.13/3: Cancel Location Procedure in the case that visited NW supports the Super-Charger features
Procedure:
1) When the GLR receives a Cancel Location message from the HLR, it checks whether the serving node supports the Super-Charger features or not.
2) If the serving node does not supports the Super-Charger features, the GLR initiates a cancel location procedure to the serving node.
3) When the GLR receives the response of the Cancel Location message, it responses to the HLR by sending the Cancel Location ack message.
7.13.4 Functional requirement for the GLR
7.13.4.1 Procedure Super_Charged_Cancel_Location_GLR
Figure 7.13/4 shows SDL chart for Procedure Super_Charged_Cancel_Location_GLR.
Figure 7.13/4: Procedure Super_Charged_Cancel_Location_GLR
7.13.4.2 Procedure Super_Charged_Location_Updating_GLR
Figure 7.13/5 shows SDL chart for Procedure Super_Charged_Location_Updating_GLR.
Figure 7.13/5: Procedure Super_Charged_Location_Updating_GLR