7.10 Interaction with CCBS

23.1193GPPGateway Location Register (GLR)Release 17Stage 2TS

7.10.1 Two possible treatments for interaction with CCBS

In order to treat CCBS function in the GLR, There may be two possible treatments applied. When a subscriber is monitored (either as being a target or being the initiator of CCBS request), and roams to visited network which contains the GLR, the GLR manages monitoring state of subscriber.

If monitoring is ongoing when the GLR receives a Location Update request from the new VLR, the GLR can take one of the following actions:

– (Alternative 1): Relay the Location Update request to the HLR to inform the appropriate CCBS processes in the HLR, or

– (Alternative 2): Send a StatusReport MAP operation, indicating "Idle" to the HLR, handle the Location Update request locally in the GLR, and start monitoring on the new VLR, by sending a SetReportingState MAP operation to the new VLR.

Should the SetReportingState response from the new VLR indicate "Not reachable" or "Not Idle", then the GLR will send this status information in a StatusReport towards the HLR.

The alternative 1 has the advantage that the GLR monitoring functionality is straightforward, but implies unnecessary MAP LU traffics.

The alternative 2 has the advantage that MAP LU traffic is saved, but implies monitoring logic to be available in the GLR.

Both options imply that the GLR needs to keep track of subscribers being monitored.

7.10.2 The functionality in the GLR

The CCBS Monitoring Flag is used in the GLR to judge whether requested location updating is necessary to be indicated to HLR or not. The figure 7.10/1 and figure 7.10/2 show how to handle a Location Update request signal referring with the CCBS Monitoring Flag in the GLR by using the alternative 1 treatment, the alternative 2 treatment respectively. These figures only indicate how a Location Update request signal is treated in the GLR. Refer to the 3G TS 23.093 [8] for a more detail treatment about the CCBS service.

Other CCBS related MAP operations, e.g. RegisterCC-entry, EraseCC-Entry and RemoteUserFree are always relayed transparently from the HLR to the VLR or vice versa.

Figure 7.10/1: Update Location request signal handling for CCBS in the GLR (Alternative 1)

Figure 7.10/2: Update Location request signal handling for CCBS in the GLR (Alternative 2) Functional requirements of GLR

The Alternative 1 introduced in this clause for Update Location request signal handling for CCBS in the GLR is illustrated in the clause 7.2.1 Location Management Procedures as one possible alternative. Process Set_reporting_GLR

Figure 7.10/3 shows the SDL chart for Process Set_reporting_GLR.

Figure 7.10/3: Process Set_reporting_GLR Process Status report GLR

Figure 7.10/4 shows the SDL chart for Process Status_report_GLR.

Figure 7.10/4: Process Status_report_GLR Process Remote_User_Free_GLR

Figure 7.10/5 shows the SDL chart for Process Remote_User_Free_GLR.

Figure 7.10/5: Process Remote_User_Free_GLR Procedure CCBS_status_report_GLR

Figure 7.10/6 shows the SDL chart for Procedure CCBS_status_report_GLR.

Figure 7.10/6: Procedure CCBS_Status_Report_GLR Procedure CCBS_start_report_GLR

Figure 7.10/7 shows the SDL chart for Procedure CCBS_start_report_GLR

Figure 7.10/7: Procedure CCBS_Start_Report_GLR