7.1.1 Functional requirements of serving MSC

03.183GPPBasic call handlingRelease 1998TS

7.1.1.1 Process OCH_MSC

The variable TCH allocated is global data, accessible to the procedure Establish_Originating_TCH_If_Required.

The procedures CCBS_Report_Not_Idle and CCBS_Check_Last_Call are specific to CCBS; they are specified in GSM 03.93 [19].

7.1.1.2 Procedure Process_Access_Request_MSC

Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC, the VMSC may encapsulate the request for the IMEI in the Start ciphering request; the BSS relays the response in the Cipher Mode complete message to the MSC.

Sheet 2: the VMSC maps the negative response received on the B interface to the appropriate reject cause according to the rules defined in ETS 300 607 [25].

Sheet 2: The Start ciphering request may indicate one of several ciphering algorithms, or no ciphering.

Sheet 2, sheet 3: At any stage, the MS may terminate the transaction with the network by sending a CM service abort message.

Sheet 2, sheet 3: if the VMSC receives a Set-up message from the MS while the access request is being handled, the message is saved for processing after the access request has been handled.

7.1.1.3 Procedure OG_Call_Setup_MSC

Sheet 1: the variables Alerting sent, MS connected and Reconnect are global data, accessible to the procedures CCBS_Check_OG_Call, CCBS_OCH_Report_Failure, CCBS_OCH_Report_Success, CCBS_Check_If_CCBS_Possible, Send_Alerting_If_Required and Send_Access_Connect_If_Required.

Sheet 1: the VMSC converts the GSM bearer capability negotiated between the VMSC and the MS to a GSM basic service according to the rules defined in GSM 07.01 [21].

Sheet 1: the variable UUS1 result sent is specific to UUS. This variable is accessible to all UUS specific procedures.

Sheet 1: the procedure UUS_OCH_Check_Setup is specific to UUS; it is specified in GSM 03.87 [17].

Sheet 1, sheet 2, sheet 5: the procedure CCBS_OCH_Report_Failure is specific to CCBS; it is specified in GSM 03.93 [19].

Sheet 1, sheet 5, sheet 6, sheet 8: at any stage after the Set-up has been received, the MS may terminate the transaction with the network by sending a Release transaction request.

Sheet 2: the procedure Set_CLI_Presentation_Indicator_MSC is specific to CLIR. If the VMSC does not support CLIR, processing continues from the "Yes" exit of the test "Result=Call allowed?".

Sheet 2: the procedure CAMEL_OCH_MSC_INIT is specific to CAMEL; it is specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?".

Sheet 2: the procedure CCBS_Check_OG_Call is specific to CCBS; it is specified in GSM 03.93 [19]. If the VMSC does not support CCBS, processing continues from the "Yes" exit of the test "Result=Pass?".

Sheet 2: the procedure UUS_OCH_Set_Info_In_IAM is specific to UUS; it is specified in GSM 03.87 [17].

Sheet 2: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is specified in GSM 03.66 [6].

Sheet 3: the procedure CCBS_OCH_Report_Success is specific to CCBS; it is specified in GSM 03.93 [19].

Sheet 3, sheet 6: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2; they are specified in GSM 03.78 for CAMEL Phase 2 [9].

Sheet 3: the task "UTU2Cnt := 0" is executed only if the VMSC supports UUS

Sheet 4: the procedure CAMEL_OCH_MSC_ANSWER is specific to CAMEL; it is specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?".

Sheet 4: the procedure Set_COLP_Info_MSC is specific to COLP.

Sheet 4: the procedure Handle_AoC_MO_MSC is specific to AoC.

Sheet 5: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS; they are specified in GSM 03.93 [19]. The task "Store CCBS Result" is executed only if the VMSC supports CCBS. If the VMSC does not support CCBS, processing continues from the "CCBS Not Possible" exit of the test "CCBS Result".

Sheet 5, sheet 6: the procedures CAMEL_OCH_MSC_DISC3 and CAMEL_OCH_MSC_DISC4 are specific to CAMEL; they are specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9] respectively.

Sheet 5, sheet 6: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2; it is specified in GSM 03.78 for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL phase 2, processing continues from the "No" exit of the test "Result=Reconnect?".

Sheet 5, sheet 6, sheet 8: the processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL.

Sheet 6, sheet 8: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in GSM 03.87 [17].

Sheet 7: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2, and will occur only if the VMSC supports CAMEL phase 2. The procedure CAMEL_OCH_MSC2 is specified in GSM 03.78 for CAMEL Phase 2 [9].

Sheet 7: the input signal User To User is specific to UUS; it is discarded if the VMSC does not support UUS.

Sheet 7: the procedures UUS_MSC_Check_UUS2_UUI_to_MS and UUS_MSC_Check_UUS2_UUI_to_NW are specific to UUS; they are specified in GSM 03.87 [17].

Sheet 8: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL; it is specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".

Sheet 8: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL; it is specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".

7.1.1.4 Procedure Obtain_IMSI_MSC

The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMSI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.

7.1.1.5 Procedure Authenticate_MSC

The MS may terminate the transaction with the network while the VMSC is waiting for the MS to respond to an authentication request. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.

7.1.1.6 Procedure Obtain_IMEI_MSC

The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.

7.1.1.7 Procedure Check_IMEI_MSC

The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.

The MS may terminate the transaction with the network while the VMSC is waiting for the result of the IMEI check from the EIR. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.

7.1.1.8 Procedure Establish_Originating_TCH_If_Required

7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC

The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIR_MAF004. The message is saved for processing after return from the procedure.

7.1.1.10 Procedure Send_Alerting_If_Required

The test "Backward call indicator=no indication" refers to the called party’s status field in the backward call indicators parameter of the ISUP Address Complete message which triggered the call of the procedure Send_Alerting_If_Required.

The procedures UUS_MSC_Check_UUS1_UUI and UUS_OCH_Set_Alert_And_Connect_Param are specific to UUS; they are specified in GSM 03.87 [17]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?".

If no useful information would be carried in the Progress message, it is not sent.

7.1.1.11 Procedure Set_COLP_Info_MSC

The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process COLP_MAF006. The message is saved for processing after return from the procedure.

7.1.1.12 Procedure Send_Access_Connect_If_Required

The test "Acknowledgement required" refers to the result returned by the procedure Handle_AoC_MSC. If the VMSC does not support AoC, processing continues from the "No" exit of the test "Acknowledgement required".

The procedure UUS_OCH_Set_Alert_And_Connect_Param is specific to UUS, it is specified in GSM 03.87 [17]. If the VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?".

If no useful information would be carried in the Facility message, it is not sent.

7.1.1.13 Procedure Handle_AoC_MO_MSC

The charging parameters and the Boolean variable Acknowledgement required are global data which can be read by the parent process.

Figure 6: Process OCH_MSC

Figure 7a: Procedure Process_Access_Request_MSC (sheet 1)

Figure 7b: Procedure Process_Access_Request_MSC (sheet 2)

Figure 7c: Procedure Process_Access_Request_MSC (sheet 3)

Figure 8a: Procedure Outgoing_Call_Setup_MSC (sheet 1)

Figure 8b: Procedure Outgoing_Call_Setup _MSC (sheet 2)

Figure 8c: Procedure Outgoing_Call_Setup _MSC (sheet 3)

Figure 8d: Procedure Outgoing_Call_Setup _MSC (sheet 4)

Figure 8e: Procedure Outgoing_Call_Setup _MSC (sheet 5)

Figure 8f: Procedure Outgoing_Call_Setup _MSC (sheet 6)

Figure 8g: Procedure Outgoing_Call_Setup _MSC (sheet 7)

Figure 8h: Procedure Outgoing_Call_Setup _MSC (sheet 8)

Figure 9: Procedure Obtain_IMSI_MSC

Figure 10: Procedure Authenticate_MSC

Figure 11: Procedure Obtain_IMEI_MSC

Figure 12: Procedure Check_IMEI_MSC

Figure 13: Procedure Establish_Originating_TCH_If_Required

Figure 14: Procedure Set_CLI_Presentation_Indicator_MSC

Figure 15: Procedure Send_Alerting_If_Required

Figure 16: Procedure Set_COLP_Info_MSC

Figure 17: Procedure Handle_AoC_MO_MSC

Figure 18: Procedure Send_Access_Connect_If_Required