7.1.2 Functional requirements of VLR
23.0183GPPBasic call handlingRelease 17Technical realizationTS
7.1.2.1 Process OCH_VLR
7.1.2.2 Procedure Process_Access_Request_VLR
Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated.
Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated.
Sheet 2: the process Subscriber_Present_VLR is described in 3GPP TS 29.002 [29].
Sheet 2: it is a network operator decision (subject to MoU requirements) whether a GSM connection should be ciphered. A UMTS connection shall always be ciphered.
Sheet 3: it is a network operator decision (subject to MoU requirements) how often an IMEI should be checked.
Sheet 3, sheet 4, sheet 5: the procedure CCBS_Report_MS_Activity is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 5: it is a network operator decision whether emergency calls are allowed from an ME with no SIM.
7.1.2.3 Procedure OG_Call_Subscription_Check_VLR
Sheet 1: it is an implementation option to carry out the check for operator determined barring of all outgoing calls before the check on provisioning of the requested basic service.
Sheet 1: the procedure Check_OG_Multicall_VLR is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 1: the procedure OG_CUG_Check is specific to CUG. If the VLR does not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?".
Sheet 1: the procedure Get_LI_Subscription_Info_MO_VLR is specific to CLIR and COLP. If the VLR supports neither CLIR nor COLP, the procedure call is omitted.
Sheet 1: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC.
Sheet 1: the procedure UUS_OCH_Check_Provision is specific to UUS; it is specified in 3GPP TS 23.087 [20]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 2: the procedure CAMEL_OCH_VLR is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the VLR does not support CAMEL, processing continues from connector 1 to the call to the procedure Check_OG_Barring.
Sheet 2: 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_OG_Barring.
7.1.2.4 Procedure Obtain_Identity_VLR
It is a network operator decision whether open (non ciphered) identification of the MS by its IMSI is allowed.
7.1.2.5 Procedure Obtain_IMSI_VLR
7.1.2.6 Procedure Authenticate_VLR
Sheet 1: the number of unused authentication sets which triggers the VLR to request further authentication sets from the HLR is an operator option.
7.1.2.7 Procedure Obtain_Authentication_Sets_VLR
7.1.2.8 Procedure Start_Tracing_VLR
7.1.2.9 Procedure Check_IMEI _VLR
If the response from the EIR to a request to check an IMEI indicates that the ME is:
– in the prohibited list, then service is not granted;
– in the tracking list, then service is granted, but the network operator may decide to initiate tracing;
– in the permitted list, then service is granted.
7.1.2.10 Procedure Obtain_IMEI_VLR
7.1.2.11 Process Fetch_Authentication_Sets_VLR
7.1.2.12 Procedure Check_BAOC
Sheet 1: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF017, the message is saved for handling after return from the procedure.
7.1.2.13 Procedure OG_CUG_Check
If the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF014, the message is saved for handling after return from the procedure.
7.1.2.14 Procedure Get_LI_Subscription_Info_MO_VLR
If the VLR does not support CLIR, it omits the signal interchange with the process CLIR_MAF003.
If the VLR does not support COLP, it omits the signal interchange with the process COLP_MAF005.
If the VLR receives an Abort message from the MSC while it is awaiting a response from the process CLIR_MAF003 or the process COLP_MAF005, the message is saved for handling after return from the procedure.
7.1.2.15 Procedure Get_AoC_Subscription_Info_VLR
The indicator of whether or not AoC is provisioned is global data which can be read by the parent process.
7.1.2.16 Procedure Check_OG_Barring
Sheet 3: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF018 or MAF020 (see 3GPP TS 23.088 [21]), the message is saved for handling after return from the procedure.
7.1.2.17 Process Update_Location_VLR
The procedure Update_HLR_VLR is described in 3GPP TS 23.012 [6].
Figure 7.1.2.1: Process OCH_VLR
Figure 7.1.2.2a: Procedure Process_Access_Request_VLR (sheet 1)
Figure 7.1.2.2b: Procedure Process_Access_Request_VLR (sheet 2)
Figure 7.1.2.2c: Procedure Process_Access_Request_VLR (sheet 3)
Figure 7.1.2.2d: Procedure Process_Access_Request_VLR (sheet 4)
Figure 7.1.2.2e: Procedure Process_Access_Request_VLR (sheet 5)
Figure 7.1.2.3a: Procedure OG_Call_Subscription_Check_VLR (sheet 1)
Figure 7.1.2.3b: Procedure OG_Call_Subscription_Check _VLR (sheet 2)
Figure 7.1.2.4: Procedure Obtain_Identity_VLR
Figure 7.1.2.5: Procedure Obtain_IMSI_VLR
Figure 7.1.2.6a: Procedure Authenticate_VLR (sheet 1)
Figure 7.1.2.6b: Procedure Authenticate_VLR (sheet 2)
Figure 7.1.2.7a: Procedure Obtain_Authentication_Sets_VLR (sheet 1)
Figure 7.1.2.7b: Procedure Obtain_Authentication_Sets_VLR (sheet 2)
Figure 7.1.2.8: Procedure Start_Tracing_VLR
Figure 7.1.2.9: Procedure Check_IMEI_VLR
Figure 7.1.2.10: Procedure Obtain_IMEI _VLR
Figure 7.1.2.11: Process Fetch_Authentication_Sets_VLR
Figure 7.1.2.12: Procedure Check_BAOC
Figure 7.1.2.13: Procedure OG_CUG_Check
Figure 7.1.2.14: Procedure Get_LI_Subscription_Info_MO_VLR
Figure 7.1.2.15: Procedure Get_AoC_Subscription_Info_VLR
Figure 7.1.2.16a: Procedure Check_OG_Barring (sheet 1)
Figure 7.1.2.16b: Procedure Check_OG_Barring (sheet 2)
Figure 7.1.2.16c: Procedure Check_OG_Barring (sheet 3)
Figure 7.1.2.17: Process Update_Location_VLR