7.2.1 Functional requirements of GMSC
23.0183GPPBasic call handlingRelease 17Technical realizationTS
7.2.1.1 Process MT_GMSC
Sheet 1: the variables ACM sent, Answer sent, Network connect sent, Reconnect and Resume call are global data, accessible to the procedures CCBS_MT_GMSC_Check_CCBS Possible, CCBS_Set_Diagnostic_For_Release, Obtain_Routeing_Address, Send_ACM_If_Required, Send_Answer_If_Required and Send_Network_Connect_If_Required.
Sheet 1: the variable UUS CF interaction is specific to UUS; it is accessible to all UUS specific procedures in the GMSC.
Sheet 1: the procedure MNP_MT_GMSC_Set_MNP_Parameters is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10].
Sheet 1: the procedure OR_Set_ORA_Parameters is specific to Support of Optimal Routeing; it is specified in 3GPP TS 23.079 [13].
Sheet 1: the procedure CAMEL_Set_ORA_Parameters is specific to CAMEL; it is specified in 3GPP TS 23.078 [12].
Sheet 1: the parameters "Reference address", "OR" and "Own PLMN" are passed to the procedure Obtain_Routeing_Address only if the GMSC supports Optimal Routeing. The parameter "Destination address" is returned by the procedure Obtain_Routeing_Address only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. The Send Routeing Info negative response information element received in the execution of the procedure Obtain_Routeing_Address is global data, available to the parent process.
Sheet 1: the suggested mapping from values of the Send Routeing Info negative response information element to values of the ISUP release cause (see ITU‑T Recommendation Q.850 [37]) is shown in table 1. The mapping used is a matter for the network operator, depending on the telephony signalling system used.
Table 1: Suggested mapping of Send Routeing Info (SRI)
negative responses to ISUP release causes
|
SRI negative response |
ISUP release cause number |
ISUP release cause name |
|
Absent subscriber |
20 |
Subscriber absent |
|
Bearer service not provisioned |
57 |
Bearer capability not authorized |
|
Busy subscriber |
17 |
User busy |
|
Call barred (ODB) |
21 |
Call rejected |
|
Call barred (SS barring) |
21 |
Call rejected |
|
Call barred (ACR) |
31 |
Normal, unspecified (NOTE 2) |
|
CUG reject (Called party SS interaction violation) |
21 |
Call rejected |
|
CUG reject (Incoming calls barred within CUG) |
55 |
Incoming calls barred within CUG |
|
CUG reject (Subscriber not member of CUG) |
87 |
User not member of CUG |
|
CUG reject (Requested basic service violates CUG constraints) |
87 |
User not member of CUG |
|
Data missing |
111 |
Protocol error, unspecified |
|
Facility not supported |
69 |
Requested facility not implemented |
|
Forwarding violation |
21 |
Call rejected |
|
Number changed |
22 |
Number changed |
|
System failure |
111 |
Protocol error, unspecified |
|
Teleservice not provisioned |
57 |
Bearer capability not authorized |
|
Unexpected data value |
111 |
Protocol error, unspecified |
|
Unknown subscriber |
1 26 |
Unallocated (unassigned) number Misrouted call to a ported number (NOTE 1) |
|
NOTE 1: If the Diagnostic parameter indicates "NPDB mismatch", MNP can require a specific ISUP release cause value, according to National Coding Standard, to indicate "Misrouted call to a ported number", depending on national regulations. North American GSM Number Portability (NAGNP) requires the SRI negative response "unknown subscriber" to be treated differently under certain conditions. If the IAM received from the originating exchange contained the HPLMN routing number for NAGNP then the SRI negative response "unknown subscriber" shall be mapped to ISUP release cause number 26 "Misrouted call to a ported number"; under all other conditions the SRI negative response "unknown subscriber" shall be mapped to ISUP release cause number 1 "Unallocated (unassigned) number". NOTE 2: The GMSC will play an announcement towards the calling user to signal that the call is rejected due to anonymous call rejection and then include cause 24 "call rejected due to feature at destination" in ACM or CPG. See 3GPP TS 23.088 [21]. |
||
Sheet 1: it is an operator option whether to send an Address Complete message if the Number Portability Database returns a routeing number. If the GMSC sends an Address Complete message, it shall include the called party’s status field of the Backward call indicator set to "no indication".
Sheet 1: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in the Perform Call Forwarding ack.
Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 1: it is an operator option whether to send an Address Complete message if the HLR returns forwarding information. If the GMSC sends an Address Complete message, it shall include the called party’s status field of the Backward call indicator set to "no indication".
Sheet 1, sheet 8: the process CAMEL_MT_LEG1_GMSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12].
Sheet 2, sheet 3: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?".
Sheet 2, sheet 3: the procedure CAMEL_MT_GMSC_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result".
Sheet 2, sheet 3: the task "Set destination address parameter" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.
Sheet 3: the procedure Handle_COLP_Forwarding_Interaction is specific to COLP.
Sheet 4: the input signal Resume Call Handling and all the subsequent processing on this sheet are specific to Support of Optimal Routeing, and will occur only if the GMSC supports Optimal Routeing. The procedure OR_Handle_RCH is specified in 3GPP TS 23.079 [13].
Sheet 4, sheet 6: the procedure CCBS_MT_GMSC_Check_CCBS_Possible is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 5: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL_MT_GMSC_DISC5 is specified in 3GPP TS 23.078 [12].
Sheet 6: the procedure CAMEL_MT_GMSC_DISC3 is specific to CAMELphase 1; it is specified in 3GPP TS 23.078 [12].
Sheet 6: the procedures CAMEL_MT_GMSC_DISC4 and CAMEL_MT_GMSC_DISC6 are specific to CAMEL phase 2 or later, they are specified in 3GPP TS 23.078 [12].
Sheet 6: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 6, sheet 7: the processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL.
Sheet 7: the procedure CAMEL_MT_GMSC_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".
Sheet 7: the procedure CAMEL_MT_GMSC_DISC2 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL, processing continues from the "Normal handling" exit of the test "Result?".
Sheet 7: after the GMSC has sent an IAM to the destination VMSC or the forwarded-to exchange (via the process MT_CF_MSC), it acts as a relay for messages received from the originating exchange and the destination VMSC or the process MT_CF_MSC. Any message other than Address Complete, Connect, Answer or Release causes no change of state in the process MT_GMSC.
Sheet 8: the procedure CAMEL_MT_LEG2_GMSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12].
7.2.1.2 Procedure Obtain_Routeing_Address
Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10].
Sheet 1: the procedure CCBS_MT_GMSC_Check_CCBS_Call is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 1: the procedure CLI_MT_GMSC is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14]. This procedure shall also be performed if the GMSC supports the ACR supplementary service.
Sheet 1: for SCUDIF calls, the message Send Routeing Info shall include the ISDN BC of both the preferred and the less preferred service, as specified in 3GPP TS 23.172 [38].
Sheet 1: global flag "Clear MT Roaming Retry IE" is initialized to No at the start of MT_GMSC procedure.
Sheet 1: if Mobile Terminating Roaming Retry is supported, and if no Resume Call Handling message for roaming retry has been received, the GMSC shall include the GMSC address, the call reference number and the MT Roaming Retry Supported IE in the SRI message.
Sheet 2: the procedure SCUDIF_Negative_SRI_Response_Handling is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the GMSC does not support SCUDIF, processing continues from the "Fail" exit of the test "Result".
Sheet 2: the procedure OR_Handle_SRI_Negative_Response is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the GMSC does not support Optimal Routeing, processing continues from the "No" exit of the test "Result=Pass?".
Sheet 2: the test "Error=Unknown subscriber" refers to the negative response value received from the HLR.
Sheet 2: the procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10].
Sheet 3: the procedure SCUDIF_Check_Service_Availability is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the GMSC does not support SCUDIF, processing continues from the "continue" exit of the test "Result ?".
Sheet 3: the procedure CAMEL_MT_GMSC_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12].
Sheet 3: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38].
Sheet 3: sending of "Release Resources" is an implementation option. If support of "Release Resources" by the VMSC is not indicated in Send Routing Info ack, "Release Resources" shall not be sent.
Sheet 4: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38].
Sheet 4: the procedure CCBS_MT_GMSC_Check_CCBS_Indicators is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 4: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal Routeing.
Sheet 4: The test "MSRN contains a Routeing Number" is executed only if the SRF solution for call related MNP is used. If the SRF solution for call related MNP is not used, processing continues from the "No" exit of the test "MSRN contains a Routeing Number".
Sheet 4: the procedure MNP_MT_GMSC_Check_MNP_Indicators is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10].
Sheet 5: the procedure CAMEL_MT_GMSC_Notify_CF is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 2 or later, processing continues from the "Continue" exit of the test "Result".
Sheet 5: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38].
Sheet 6: the task "BOR:=OR" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.
Sheet 6: the procedures CCBS_MT_GMSC_Remove_Indicators_Store_FWT is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 6: the procedure Route_Permitted is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the GMSC does not support Optimal Routeing, processing continues from the "True" exit of the test "Route permitted".
Sheet 6: the procedure CAMEL_MT_MSC_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12].
Sheet 6: the procedure CAMEL_MT_GMSC_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 6: the task "OR:= True" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.
7.2.1.3 Procedure Send_ACM_If_Required
If no useful information would be carried in the Call Progress message, it is not sent.
7.2.1.4 Procedure Send_Answer_If_Required
If no useful information would be carried in the Call Progress message, it is not sent.
7.2.1.5 Procedure Send_Network_Connect_If_Required
If no useful information would be carried in the Call Progress message, it is not sent.
7.2.1.6 Procedure Handle_COLP_Forwarding_Interaction_MSC
The originating exchange or the destination exchange may release the call while a response is awaited from the process COLP_MAF039. The message is saved for processing after return from the procedure.
7.2.1.7 Procedure Activate_CF_Process
The processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL.
7.2.1.8 Process MT_CF_MSC
Sheet 1: the procedure CAMEL_CF_MSC_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 1, sheet 4: the procedure CAMEL_CF_Dialled_Services is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 3 or later, processing continues from the "Pass" exit of the test "Result?".
Sheet 1, sheet 3, sheet 4: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 2 or later, processing continues from the "Yes" exit of the test "Result=Reconnect?".
Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10].
Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 1, sheet 3: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12].
Sheet 1, sheet 3: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 1, sheet 6: the procedure CAMEL_MT_CF_LEG1_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12].
Sheet 2: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result?".
Sheet 2: the procedure UUS_MSC_Clear_UUS is specific to UUS; it is specified in 3GPP TS 23.087 [20].
Sheet 2: the procedure CAMEL_CF_MSC_ALERTING is specific to CAMEL phase 4 or later; it is specifed in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?".
Sheet 3: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 3: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL.
Sheet 4: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23.078 [12].
Sheet 5: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".
Sheet 5: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=Reconnect?" .
Sheet 5: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL.
Sheet 5: after the process MT_CF_MSC has sent an IAM to the forwarded-to exchange, it acts as a relay for messages received from the parent process and the forwarded-to exchange. Any message other than Address Complete, Connect, Answer or Release causes no change of state in the process MT_GMSC.
Sheet 6: the process CAMEL_MT_CF_LEG2_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12].
7.2.1.9 Macro CUG_Support_Check_GMSC
Figure 36a: Process MT_GMSC (sheet 1)
Figure 36b: Process MT_GMSC (sheet 2)
Figure 36c: Process MT_GMSC (sheet 3)
Figure 36d: Process MT_GMSC (sheet 4)
Figure 36e: Process MT_GMSC (sheet 5)
Figure 36f: Process MT_GMSC (sheet 6)
Figure 36g: Process MT_GMSC (sheet 7)
Figure 36h: Process MT_GMSC (sheet 8)
Figure 36i: Process MT_GMSC (sheet 9)
Figure 37a: Procedure Obtain_Routeing_Address (sheet 1)
Figure 37b: Procedure Obtain_Routeing_Address (sheet 2)
Figure 37c: Procedure Obtain_Routeing_Address (sheet 3)
Figure 37d: Procedure Obtain_Routeing_Address (sheet 4)
Figure 37e: Procedure Obtain_Routeing_Address (sheet 5)
Figure 37f: Procedure Obtain_Routeing_Address (sheet 6)
Figure 38: Procedure Send_ACM_If_Required
Figure 39: Procedure Send_Answer_If_Required
Figure 40: Procedure Send_Network_Connect_If_Required
Figure 41: Procedure Handle_COLP_Forwarding_Interaction_MSC
Figure 42: Procedure Activate_CF_Process
Figure 43a: Process MT_CF_MSC (sheet 1)
Figure 43b: Process MT_CF_MSC (sheet 2)
Figure 43c: Process MT_CF_MSC (sheet 3)
Figure 43d: Process MT_CF_MSC (sheet 4)
Figure 43e: Process MT_CF_MSC (sheet 5)
Figure 43f: Process MT_CF_MSC (sheet 6)
Figure 43bis: Macro CUG_Support_Check_GMSC