7.2.2 Functional requirements of HLR

23.0183GPPBasic call handlingRelease 17Technical realizationTS

7.2.2.1 Process SRI_HLR

Sheet 1: the procedures Check_Parameters, Subscription_Check_HLR, SCUDIF_Subscription_Check_HLR, Handle_OR_HLR_CF and CAMEL_HLR_INIT can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI_HLR.

Sheet 1: the procedure Handle_OR_HLR_CF is specific to Support of Optimal Routeing; it is specified in 3GPP TS 23.079 [13]. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test "Result=Forward?".

Sheet 1: the procedure SCUDIF_Subscription_Check_HLR is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. This procedure gets the result from the Subscription_Check_HLR procedure, and modifies it if needed. If the HLR does not support SCUDIF, the test "Result = Fail ?" applies to the result of the Subscription_Check_HLR procedure.

Sheet 1: the procedure CAMEL_HLR_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR does not support CAMEL, processing continues from the "No" exit of the test"Result=Fail?".

Sheet 2: the procedure First_Forwarding_HLR can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI_HLR.

Sheet 2: the procedure Domain_Selection_HLR is specific to domain selection for a subscriber who has subscriptions in both the CS and the IMS domain.

NOTE: The domain selection function mentioned in this procedure is service domain selection specified in 3GPP TS 23.221 [40].

Sheet 2: the procedure CAMEL_CSI_Check_HLR is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR does not support CAMEL, processing continues from the "No" exit of the test"Result=CSI active?".

Sheet 2: the procedure SCUDIF_CAMEL_CSI_Check_HLR is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. This procedure gets the result from the CAMEL_CSI_Check_HLR procedure, and modifies it if needed. If the HLR does not support SCUDIF, the test "Result = CSI Active ?" applies to the result of the CAMEL_CSI_Check_HLR procedure. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?".

Sheet 2: the test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit.

Sheet 2: the test "Suppress CCBS Handling?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit.

Sheet 2: the procedure CCBS_Handling_HLR is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. If the HLR does not support CCBS, processing continues from the "Yes" exit of the test "Result = OK?".

Sheet 3: the procedure OR_HLR_Interrogate_VLR is specific to Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test "Result=Forward".

Sheet 3: the procedure SCUDIF_Set_Correct_PLMN_BC is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Set_PLMN_BC" exit of the test "Result ?".

Sheet 3: if the HLR does not support Network Indication of Alerting, the test "Alerting pattern required" and the task "Set Alerting Pattern" are omitted.

Sheet 3: the procedure CLI_HLR_Set_CLI is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14].

Sheet 5: the procedure SCUDIF_Check_Second_Service_after_PRN is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "yes" exit of the test "Result = Continue ?".

Sheet 5: the procedure PRN_Error_HLR can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI_HLR.

Sheet 5: the procedure Forward_CUG_Check is specific to CUG. If the HLR does not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?".

Sheet 6: the test "Forwarding enquiry" is specific to Support of Optimal Routeing. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test.

Sheet 6: the procedure CAMEL_CSI_Check_HLR is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?".

Sheet 6: the procedure SCUDIF_CAMEL_CSI_Check_HLR is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. This procedure gets the result from the CAMEL_CSI_Check_HLR procedure, and modifies it if needed. If the HLR does not support SCUDIF, the test "Result = CSI Active ?" applies to the result of the CAMEL_CSI_Check_HLR procedure. If the HLR does not support CAMEL, processing continues from the "No" exit of the test "Result=CSI active?".

Sheet 6: the procedure SCUDIF_Check_Second_Service_before_Negative_Response can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global data, accessible by the process SRI_HLR.

Sheet 6: the procedure SCUDIF_Check_Second_Service_before_Negative_Response is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Fail" exit of the test "Result ?".

Sheet 7: the procedures CAMEL_T_CSI_CHECK_HLR and CAMEL_O_CSI_CHECK_HLR are specific to CAMEL; they are specified in 3GPP TS 23.078 [12].

Sheet 7: the procedure CAMEL_D_CSI_CHECK_HLR is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12].

Sheet 7: the procedure SCUDIF_Set_Second_Service_when_Forwarded is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Yes" exit of the test "Result = Continue ?".

Sheet 7: the procedure SCUDIF_Check_Second_Service_when_Forwarded is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the HLR does not support SCUDIF, processing continues from the "Yes" exit of the test "Result = Continue ?".

Sheet 7: A HLR implementing the Mobile Terminating Roaming Retry feature (see clause 5.2.1) shall delay the sending of the PRN message till completion of any on-going Location Update procedure.

7.2.2.2 Procedure Check_Parameters

If any parameters required by the rules in clause 8 are missing from the message, the procedure sets the negative response to "Data missing". If any parameter has a value which is not in the set of values expected for the parameter, the procedure sets the negative response to "Unexpected data value".

7.2.2.3 Procedure Subscription_Check_HLR

The HLR derives the possible PLMN bearer capability to populate the parameter in the Provide Roaming Number request according to the rules defined in 3GPP TS 29.007 [30].

If the HLR is able to determine the PLMN bearer capability or equivalent ISDN compatibility information to be sent to the VLR in the Provide Roaming Number request, it applies the corresponding PLMN bearer service or teleservice for handling the call. If the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request, it applies a default basic service according to the requirements of the operator.

If the HLR receives Send Routeing Information from the gsmSCF and the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request, then the HLR shall apply basic service TS11.

NOTE The information element "gsmSCF Initiated Call" in Send Routeing Information serves as an indication to the HLR that this Send Routeing Information is sent by the gsmSCF. Refer to 3GPP TS 23.078 [12].

It is an implementation option to carry out the check for operator determined barring of incoming calls before the check on provisioning of the requested basic service.

The test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit.

The test "Suppress CUG Handling?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later, processing continues from the "No" exit.

The negative response "Call barred" indicates whether the reason is operator determined barring or supplementary service barring, according to the result returned by the procedure Check_IC_Barring.

The negative response "CUG reject" indicates whether the reason is:

– Incoming calls barred within CUG;

– Requested basic service violates CUG constraints;

– Subscriber not member of CUG;

according to the cause returned by the procedure IC_CUG_Check.

7.2.2.4 Procedure First_Forwarding_HLR

The MS is not reachable if any of the following conditions is satisfied:

– The HLR has no location information for the subscriber.

– The subscriber record is marked as MS purged.

– The subscriber record is marked as MSC area restricted.

– The subscriber record is marked as Roaming Restricted due to Unsupported Feature.

– The subscriber is marked as deregistered because of subscription restrictions on roaming.

7.2.2.5 Procedure PRN_Error_HLR

The procedure CCBS_Report_PRN_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. The procedure does not return a value; the following tests are on the value of the Provide Roaming Number negative response.

The procedure Super_Charged_SRI_Error_HLR is specific to Super-Charger; it is specified in 3GPP TS 23.116 [24]. If the HLR does not support Super-Charger, processing continues from the "No" exit of the test "Result=Purged?".

If the HLR does not support Optimal Routeing, processing starts with the test "Negative response=Facility not supported?".

7.2.2.6 Procedure Forward_CUG_Check

7.2.2.7 Void

7.2.2.8 Procedure Check_IC_Barring

7.2.2.9 Procedure IC_CUG_Check

7.2.2.10 Procedure Handle_CFU

The test "Normal call" refers to the value of the indicator returned by the process MAF007.

The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?".

7.2.2.11 Procedure Handle_CFNRc

The test "Mobile subscriber not reachable" refers to the value of the indicator returned by the process MAF010.

The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?".

7.2.2.12 Procedure Domain_Selection_HLR

The procedure Domain_Selection_HLR is specific to Domain Selection specified in 3GPP TS 23.221 [40].

Figure 44a: Process SRI_HLR (sheet 1)

Figure 44b: Process SRI_HLR (sheet 2)

Figure 44c: Process SRI_HLR (sheet 3)

Figure 44d: Process SRI_HLR (sheet 4)

Figure 44e: Process SRI_HLR (sheet 5)

Figure 44f: Process SRI_HLR (sheet 6)

Figure 44g: Process SRI_HLR (sheet 7)

Figure 45: Procedure Check_Parameters

Figure 46: Procedure Subscription_Check_HLR

Figure 47: Procedure First_Forwarding_HLR

Figure 48: Procedure PRN_Error_HLR

Figure 49: Procedure Forward _CUG_Check

Figure 50: Void

Figure 51a: Procedure Check_IC_Barring (sheet 1)

Figure 51b: Procedure Check_IC_Barring (sheet 2)

Figure 52: Procedure IC_CUG_Check

Figure 53: Procedure Handle_CFU

Figure 54: Procedure Handle_CFNRc

Figure 54A: Process Domain_Selection_HLR