E00

3GPP TS 23.018 V14.0.
0 (2017-03)
Technical Specification
3rd Generation Partnership Project;

Technical Specification Group Core Network and Terminals;
Basic call handling;
Technical realization
(Release 14)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP.
The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented.
This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification.
Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.
Release 14 2 3GPP TS 23.018 V14.0.0 (2017-03)
Keywords
UMTS, GSM, basic, call
3GPP
Postal address
3GPP support office address

650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification
No part may be reproduced except as authorized by written permission.

The copyright and the foregoing restriction extend to reproduction in all media.
2017, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC).
All rights reserved.
UMTS is a Trade Mark of ETSI registered for the benefit of its members
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
LTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners
GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 14 3 3GPP TS 23.018 V14.0.0 (2017-03)
Contents
Foreword............................................................................................................................................................. 7
1 Scope ........................................................................................................................................................ 8
2 References ................................................................................................................................................ 8
3 Definitions and abbreviations................................................................................................................. 10
3.1 Definitions ............................................................................................................................................................... 10
3.2 Abbreviations........................................................................................................................................................... 10
4 Architecture ............................................................................................................................................ 11
4.1 Architecture for an MO call .................................................................................................................................... 11
4.2 Architecture for an MT call .................................................................................................................................... 12
4.3 Architecture for a TO call ....................................................................................................................................... 13
5 Information flows ................................................................................................................................... 14
5.1 Information flow for an MO call ............................................................................................................................ 14
5.2 Information flow for retrieval of routeing information for an MT call ............................................................... 17
5.2.1 Mobile Terminating Roaming Retry Call after successful Retrieval of Routeing Information ................................. 18
5.2.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing Information ................................................ 20
5.2.3 Mobile Terminating Roaming Forwarding Call after successful Retrieval of Routeing Information ....................... 23
5.2.4 Mobile Terminating Roaming Forwarding Call during Retrieval of Routeing Information ........................ 29
5.3 Information flow for an MT call ............................................................................................................................ 31
6 Principles for interactions with supplementary services ........................................................................ 33
6.1 Call Deflection service (3GPP TS 23.072) ............................................................................................................ 34
6.2 Line identification services (3GPP TS 23.081) ..................................................................................................... 34
6.2.1 Calling Line Identification Presentation (CLIP) ............................................................................................. 34
6.2.2 Calling Line Identification Restriction (CLIR) ............................................................................................... 34
6.2.3 Connected Line Identification Presentation (COLP) ...................................................................................... 34
6.2.4 Connected Line Identification Restriction (COLR) ........................................................................................ 34
6.3 Call forwarding services (3GPP TS 23.082) ......................................................................................................... 34
6.3.1 Call Forwarding Unconditional (CFU) ............................................................................................................ 34
6.3.2 Call Forwarding on mobile subscriber Busy (CFB) ........................................................................................ 34
6.3.3 Call Forwarding on No Reply (CFNRy) .......................................................................................................... 34
6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) ................................................................... 34
6.4 Call wait (3GPP TS 23.083) ................................................................................................................................... 35
6.5 Call hold (3GPP TS 23.083) ................................................................................................................................... 35
6.6 Multiparty (3GPP TS 23.084) ................................................................................................................................ 35
6.7 Closed user group (3GPP TS 23.085) .................................................................................................................... 35
6.8 Advice of charge (3GPP TS 23.086)...................................................................................................................... 35
6.9 User-to-user signalling (3GPP TS 23.087) ............................................................................................................ 35
6.10 Call barring (3GPP TS 23.088) .............................................................................................................................. 35
6.10.1 Barring of outgoing calls................................................................................................................................... 35
6.10.2 Barring of incoming calls .................................................................................................................................. 35
6.11 Explicit Call Transfer (3GPP TS 23.091) .............................................................................................................. 36
6.12 Completion of Calls to Busy Subscriber (3GPP TS 23.093) ................................................................................ 36
6.13 Multicall (3GPP TS 23.135) ................................................................................................................................... 36
7 Functional requirements of network entities .......................................................................................... 36
7.1 MO call .................................................................................................................................................................... 37
7.1.1 Functional requirements of serving MSC ........................................................................................................ 37
7.1.1.1 Process OCH_MSC ..................................................................................................................................... 37
7.1.1.2 Procedure Process_Access_Request_MSC ............................................................................................... 37
7.1.1.3 Procedure OG_Call_Setup_MSC ............................................................................................................... 37
7.1.1.4 Procedure Obtain_IMSI_MSC ................................................................................................................... 39
7.1.1.5 Procedure Authenticate_MSC .................................................................................................................... 39
7.1.1.6 Procedure Obtain_IMEI_MSC ................................................................................................................... 39
7.1.1.7 Procedure Check_IMEI_MSC .................................................................................................................... 39
7.1.1.8 Procedure Establish_Originating_TCH_If_Required ............................................................................... 40
3GPP
Release 14 4 3GPP TS 23.018 V14.0.0 (2017-03)
7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC .................................................................................... 40

7.1.1.10 Procedure Send_Alerting_If_Required ...................................................................................................... 40
7.1.1.11 Procedure Set_COLP_Info_MSC .............................................................................................................. 40
7.1.1.12 Procedure Send_Access_Connect_If_Required ........................................................................................ 40
7.1.1.13 Procedure Handle_AoC_MO_MSC ........................................................................................................... 40
7.1.1.14 Procedure TCH_Check ............................................................................................................................... 41
7.1.2 Functional requirements of VLR ...................................................................................................................... 67
7.1.2.1 Process OCH_VLR ..................................................................................................................................... 67
7.1.2.2 Procedure Process_Access_Request_VLR ................................................................................................ 67
7.1.2.3 Procedure OG_Call_Subscription_Check_VLR ....................................................................................... 67
7.1.2.4 Procedure Obtain_Identity_VLR ................................................................................................................ 67
7.1.2.5 Procedure Obtain_IMSI_VLR .................................................................................................................... 67
7.1.2.6 Procedure Authenticate_VLR ..................................................................................................................... 67
7.1.2.7 Procedure Obtain_Authentication_Sets_VLR ........................................................................................... 68
7.1.2.8 Procedure Start_Tracing_VLR ................................................................................................................... 68
7.1.2.9 Procedure Check_IMEI _VLR ................................................................................................................... 68
7.1.2.10 Procedure Obtain_IMEI_VLR .................................................................................................................... 68
7.1.2.11 Process Fetch_Authentication_Sets_VLR ................................................................................................. 68
7.1.2.12 Procedure Check_BAOC ............................................................................................................................ 68
7.1.2.13 Procedure OG_CUG_Check ....................................................................................................................... 68
7.1.2.14 Procedure Get_LI_Subscription_Info_MO_VLR ..................................................................................... 68
7.1.2.15 Procedure Get_AoC_Subscription_Info_VLR .......................................................................................... 68
7.1.2.16 Procedure Check_OG_Barring ................................................................................................................... 68
7.1.2.17 Process Update_Location_VLR ................................................................................................................. 68
7.2 Retrieval of routeing information for MT call ...................................................................................................... 95
7.2.1 Functional requirements of GMSC .................................................................................................................. 95
7.2.1.1 Process MT_GMSC .................................................................................................................................... 95
7.2.1.2 Procedure Obtain_Routeing_Address ........................................................................................................ 97
7.2.1.3 Procedure Send_ACM_If_Required .......................................................................................................... 98
7.2.1.4 Procedure Send_Answer_If_Required ....................................................................................................... 99
7.2.1.5 Procedure Send_Network_Connect_If_Required ..................................................................................... 99
7.2.1.6 Procedure Handle_COLP_Forwarding_Interaction_MSC ....................................................................... 99
7.2.1.7 Procedure Activate_CF_Process ................................................................................................................ 99
7.2.1.8 Process MT_CF_MSC ................................................................................................................................ 99
7.2.1.9 Macro CUG_Support_Check_GMSC ......................................................................................................101
7.2.2 Functional requirements of HLR ....................................................................................................................127
7.2.2.1 Process SRI_HLR ......................................................................................................................................127
7.2.2.2 Procedure Check_Parameters ...................................................................................................................129
7.2.2.3 Procedure Subscription_Check_HLR ......................................................................................................129
7.2.2.4 Procedure First_Forwarding_HLR ...........................................................................................................130
7.2.2.5 Procedure PRN_Error_HLR .....................................................................................................................130
7.2.2.6 Procedure Forward_CUG_Check .............................................................................................................130
7.2.2.7 Void ............................................................................................................................................................130
7.2.2.8 Procedure Check_IC_Barring ...................................................................................................................130
7.2.2.9 Procedure IC_CUG_Check .......................................................................................................................130
7.2.2.10 Procedure Handle_CFU ............................................................................................................................130
7.2.2.11 Procedure Handle_CFNRc........................................................................................................................131
7.2.2.12 Procedure Domain_Selection_HLR .........................................................................................................131
7.2.3 Functional requirements of VLR ....................................................................................................................148
7.2.3.1 Process PRN_VLR ....................................................................................................................................148
7.2.3.2 Process Restore_Subscriber_Data_VLR ..................................................................................................149
7.2.3.3 Process PSI_VLR ......................................................................................................................................149
7.2.3.4 Procedure Retrieve_Location_Info_VLR ................................................................................................150
7.2.3.5 Procedure Active_Info_Retrieval_VLR...................................................................................................150
7.2.4 Functional requirements of MSC ...................................................................................................................167
7.2.4.1 Process Prepage_MSC ..............................................................................................................................167
7.2.4.2 Procedure Prepaging_Page_MS_MSC ....................................................................................................167
7.2.4.3 Prepaging_Search_For_MS_MSC ...........................................................................................................167
7.2.4.4 Process OSI_MSC .....................................................................................................................................167
7.2.4.5 Process RCL_MSC ....................................................................................................................................167
7.2.4.6 Procedure Active_Info_Retrieval_Page_MSC ........................................................................................167
7.2.4.7 Procedure Active_Info_Retrieval_Search_MSC .....................................................................................167
3GPP
Release 14 5 3GPP TS 23.018 V14.0.0 (2017-03)
7.2.4.8 Procedure Retrieve_IMEI_If_Required ...................................................................................................168

7.3 MT call ...................................................................................................................................................................176
7.3.1 Functional requirements of serving MSC ......................................................................................................176
7.3.1.1 Process ICH_MSC.....................................................................................................................................176
7.3.1.2 Procedure Page_MS_MSC .......................................................................................................................178
7.3.1.3 Procedure Search_For_MS_MSC ............................................................................................................179
7.3.1.4 Procedure Complete_Call_In_MSC .........................................................................................................180
7.3.1.5 Void ............................................................................................................................................................181
7.3.1.6 Procedure Set_CLIP_Info_MSC ..............................................................................................................181
7.3.1.7 Void ............................................................................................................................................................182
7.3.1.8 Procedure Establish_Terminating_TCH_If_Required ............................................................................182
7.3.1.9 Procedure Handle_AoC_MT_MSC .........................................................................................................182
7.3.1.10 Procedure Set_COL_Presentation_Indicator_MSC ................................................................................182
7.3.2 Functional requirements of VLR ....................................................................................................................224
7.3.2.1 Process ICH_VLR .....................................................................................................................................224
7.3.2.2 Void ............................................................................................................................................................225
7.3.2.3 Procedure Search_For_MS_VLR .............................................................................................................225
7.3.2.4 Procedure Get_CW_Subscription_Info_VLR .........................................................................................225
7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR ...................................................................................225
7.3.2.6 Procedure Handle_CFB ............................................................................................................................226
7.3.2.7 Procedure Handle_CFNRy .......................................................................................................................226
7.4 Subs_FSM ..............................................................................................................................................................240
7.4.1 Functional requirements of serving MSC ......................................................................................................240
7.4.1.1 Process Subs_FSM ....................................................................................................................................240
7.4.1.1.1 Macro Check_Ongoing_Calls .............................................................................................................241
7.4.1.1.2 Macro Update_Non_Speech_Calls_Status ........................................................................................241
7.4.1.1.3 Macro Increment_Call_Counter .........................................................................................................241
7.4.1.1.4 Macro Decrement_Call_Counter ........................................................................................................241
7.5 TO call....................................................................................................................................................................263
7.5.1 Functional requirements of inter-connecting MSC .......................................................................................263
7.5.1.1 Process TO_MSC ......................................................................................................................................263
8 Contents of messages ........................................................................................................................... 271
8.1 Messages on the B interface (MSC-VLR) ...........................................................................................................272
8.1.1 Abort .................................................................................................................................................................272
8.1.2 Authenticate .....................................................................................................................................................272
8.1.3 Authenticate ack ..............................................................................................................................................273
8.1.4 Authenticate negative response ......................................................................................................................273
8.1.5 Call arrived.......................................................................................................................................................273
8.1.6 Check IMEI......................................................................................................................................................273
8.1.7 Check IMEI ack ...............................................................................................................................................273
8.1.8 Check IMEI negative response .......................................................................................................................273
8.1.9 Complete Call ..................................................................................................................................................274
8.1.10 Complete Call ack ...........................................................................................................................................275
8.1.11 Complete Call negative response ...................................................................................................................275
8.1.12 Forward New TMSI ........................................................................................................................................275
8.1.13 Forward New TMSI ack .................................................................................................................................275
8.1.14 Forward New TMSI negative response..........................................................................................................275
8.1.15 Obtain Subscriber Info ....................................................................................................................................275
8.1.16 Obtain Subscriber Info ack .............................................................................................................................275
8.1.17 Page MS ...........................................................................................................................................................276
8.1.18 Page MS ack ....................................................................................................................................................276
8.1.19 Page MS negative response ............................................................................................................................276
8.1.20 Page MS via SGSN .........................................................................................................................................277
8.1.21 Process Access Request ..................................................................................................................................277
8.1.22 Process Access Request ack ...........................................................................................................................277
8.1.23 Process Access Request negative response....................................................................................................278
8.1.24 Process Call Waiting .......................................................................................................................................278
8.1.25 Process Call Waiting ack ................................................................................................................................279
8.1.26 Process Call Waiting negative response ........................................................................................................279
8.1.27 Provide IMEI ...................................................................................................................................................279
8.1.28 Provide IMEI ack ............................................................................................................................................279
3GPP
Release 14 6 3GPP TS 23.018 V14.0.0 (2017-03)
8.1.29 Provide IMSI....................................................................................................................................................279

8.1.30 Provide IMSI ack .............................................................................................................................................279
8.1.31 Radio connection released ..............................................................................................................................279
8.1.32 Search For MS .................................................................................................................................................279
8.1.33 Search For MS ack ..........................................................................................................................................280
8.1.34 Search For MS negative response ..................................................................................................................280
8.1.35 Search for MS via SGSN ................................................................................................................................281
8.1.36 Send Info For Incoming Call ..........................................................................................................................281
8.1.37 Send Info For Incoming Call ack ...................................................................................................................282
8.1.38 Send Info For Incoming Call negative response ...........................................................................................282
8.1.39 Send Info For Outgoing Call ..........................................................................................................................283
8.1.40 Send Info For Outgoing Call negative response ............................................................................................283
8.1.40A Send UESBI-Iu to Access Network ...............................................................................................................283
8.1.41 Start security procedures .................................................................................................................................284
8.1.42 Trace subscriber activity .................................................................................................................................284
8.1.43 Use existing TMSI...........................................................................................................................................284
8.1.44 Release MSRN.................................................................................................................................................284
8.2 Messages on the C interface (MSC-HLR) ...........................................................................................................284
8.2.1 Send Routeing Info ..........................................................................................................................................284
8.2.2 Send Routeing Info ack ...................................................................................................................................286
8.2.3 Send Routeing Info negative response ...........................................................................................................286
8.3 Messages on the D interface (VLR-HLR) ...........................................................................................................287
8.3.1 Provide Roaming Number ..............................................................................................................................287
8.3.2 Provide Roaming Number ack........................................................................................................................288
8.3.3 Provide Roaming Number negative response ................................................................................................288
8.3.4 Provide Subscriber Info...................................................................................................................................289
8.3.5 Provide Subscriber Info ack ............................................................................................................................289
8.3.5.1 Location information .................................................................................................................................291
8.3.6 Provide Subscriber Info negative response ....................................................................................................291
8.3.7 Restore Data .....................................................................................................................................................291
8.3.8 Restore Data ack ..............................................................................................................................................292
8.3.9 Restore Data negative response ......................................................................................................................292
8.4 Messages on the F interface (MSC-EIR) .............................................................................................................292
8.4.1 Check IMEI......................................................................................................................................................292
8.4.2 Check IMEI ack ...............................................................................................................................................292
8.4.3 Check IMEI negative response .......................................................................................................................292
8.5 Messages on the MSC internal interface .............................................................................................................293
8.5.1 CF cancelled ....................................................................................................................................................293
8.5.2 Perform Call Forwarding ................................................................................................................................293
8.5.3 Perform Call Forwarding ack .........................................................................................................................293
8.5.4 Perform Call Forwarding negative response .................................................................................................293
8.6 Messages on the VLR internal interface ..............................................................................................................293
8.6.1 Call arrived.......................................................................................................................................................293
8.6.2 PAR completed ................................................................................................................................................293
8.7 Messages on the Gs interface ...............................................................................................................................294
8.7.1 Page MS ...........................................................................................................................................................294
8.7.2 Send MS information ......................................................................................................................................294
8.7.3 Send MS information ack ...............................................................................................................................294
8.7.4 Send MS information negative response .......................................................................................................294
8.8 Messages on the E interface (GMSC-VMSC).....................................................................................................295
8.8.1 Release Resources ...........................................................................................................................................295
Annex A (informative): Handling of an IAM at an MSC ................................................................. 296

Annex B (informative): Change history ............................................................................................. 298
3GPP
Release 14 7 3GPP TS 23.018 V14.0.0 (2017-03)
Foreword
This Technical Specification has been produced by the 3 rd Generation Partnership Project (3GPP).
The present document specifies the technical realization of the handling of calls originated by a 3G mobile subscriber
and calls directed to a 3G mobile subscriber, up to the point where the call is established within the 3GPP system.
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 Indicates a TSG approved Release 1999 document under change control;
4 Indicate a TSG approved Release 4 document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the specification;
3GPP
Release 14 8 3GPP TS 23.018 V14.0.0 (2017-03)
1 Scope
The present document specifies the technical realization of the handling of calls originated by a UMTS or GSM mobile
subscriber and calls directed to a UMTS or GSM mobile subscriber, up to the point where the call is established.
Normal release of the call after establishment is also specified. Trunk Originated call is also modelled.
In the present document, the term MS is used to denote a UMTS UE or GSM MS, as appropriate.
The handling of DTMF signalling and Off-Air Call set-up (OACSU) are not described in the present document.
The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the
relevant 3GPP TS 23.07x, 3GPP TS 23.08x and 3GPP TS 23.09x series of specifications.
The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling,
but is required for both CAMEL (3GPP TS 23.078 [12]) and optimal routeing (3GPP TS 23.079 [13]). The use of the
Provide Subscriber Information message flow is shown in 3GPP TS 23.078 [12] and 3GPP TS 23.079 [13].
The logical separation of the MSC and VLR (shown in clauses 4, 5 and 7), and the messages transferred between them
(described in clause 8) are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which
is a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour.
If there is any conflict between the present document and the corresponding stage 3 specifications
(3GPP TS 24.008 [26], 3GPP TS 25.413 [27], 3GPP TS 48.008 [2] and 3GPP TS 29.002 [29]), the stage 3 specification
shall prevail.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 43.020: "Security related Network Functions".
[2] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface Layer 3
specification".
[3] 3GPP TS 52.008: "Telecommunication management; GSM subscriber and equipment trace".
[4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[5] 3GPP TS 23.003: "Numbering, addressing and identification".
[6] 3GPP TS 23.012: "Location management procedures".
[7] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".
[8] Void
[9] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[10] 3GPP TS 23.066: "Support of GSM Mobile Number Portability (MNP); Stage 2".
[11] 3GPP TS 23.072: "Call deflection Supplementary Service; Stage2".
3GPP
Release 14 9 3GPP TS 23.018 V14.0.0 (2017-03)
[12] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL);
Stage 2".
[13] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical realization; Stage 2".
[14] 3GPP TS 23.081: "Line identification Supplementary Services; Stage 2 ".
[15] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services; Stage 2".
[16] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service; Stage 2".
[17] 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Service; Stage 2".
[18] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service; Stage 2".
[19] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service; Stage 2".
[20] 3GPP TS 23.087: "User-to-User Signalling (UUS) Supplementary Service; Stage 2".
[21] 3GPP TS 23.088: "Call Barring (CB) Supplementary Service; Stage 2".
[22] 3GPP TS 23.091: "Explicit Call Transfer (ECT) supplementary service; Stage 2".
[23] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS);
Stage 2".
[24] 3GPP TS 23.116: "Super-charger technical realization; Stage 2".
[25] 3GPP TS 23.135: "Multicall supplementary service; Stage 2".
[25a] 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities".
[26] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[27] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".
[28] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[29] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[30] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile
Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched
Telephone Network (PSTN)".
[31] 3GPP TS 29.010: "Information Element Mapping between Mobile Station - Base Station System
(MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC) Signalling
Procedures and the Mobile Application Part (MAP)".
[32] 3GPP TS 33.102: "3G Security; Security architecture ".
[33] ITU-T Recommendation Q.761 (1999): " Signalling System No. 7 - ISDN User Part functional
description ".
[34] ITU-T Recommendation Q.762 (1999): "Signalling System No. 7 - ISDN User Part general
functions of messages and signals".
[35] ITU-T Recommendation Q.763 (1999): "Signalling System No. 7 - ISDN User Part formats and
codes".
[36] ITU-T Recommendation Q.764 (1999): " Signalling System No. 7 ISDN user part signalling
procedures".
[37] ITU-T Recommendation Q.850 (05/1998) including Amendment 1 (07/2001): "Usage of cause and
location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN
User Part".
[38] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service ; UDI/RDI
fallback and service modification; Stage 2".
3GPP
Release 14 10 3GPP TS 23.018 V14.0.0 (2017-03)
[39] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage
2".
[40] 3GPP TS 23.221: "Technical specification Group Services and System Aspects; Architectural
Requirements".
[41] 3GPP TS 29.118: "Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs
interface specification".
[42] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2".
[43] 3GPP TS 23.007: "Restoration procedures".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
A subscriber: the calling mobile subscriber
B subscriber: the mobile subscriber originally called by the A subscriber
C subscriber: the subscriber to whom the B subscriber has requested that calls be forwarded
The C subscriber may be fixed or mobile.
Location Information: information to define the whereabouts of the MS, and the age of the information defining the
whereabouts
PLMN Bearer Capability: information transferred over the UMTS or GSM access interface to define the information
transfer capabilities to be used between the MS and the network for a circuit-switched connection
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
A&O Active & Operative

ACM Address Complete Message
ANM ANswer Message
AoC Advice of Charge
BC Bearer Capability
BOIC-exHC&BOIZC Barring of Outgoing International Calls except those directed to the HPLMN Country &
Barring of Outgoing InterZonal Calls
BOIZC Barring of Outgoing InterZonal Calls
BOIZC-exHC Barring of Outgoing InterZonal Calls except those directed to the HPLMN Country
CCBS Completion of Calls to Busy Subscriber
CFB Call Forwarding on Busy
CFNRc Call Forwarding on mobile subscriber Not Reachable
CFNRy Call Forwarding on No Reply
CFU Call Forwarding Unconditional
CLIP Calling Line Identity Presentation
CLIR Calling Line Identity Restriction
COLP COnnected Line identity Presentation
COLR COnnected Line identity Restriction
CSG Closed Subscriber Group
CUG Closed User Group
CW Call Waiting
FTN Forwarded-To Number
FTNW Forwarded-To NetWork
GMSCB Gateway MSC of the B subscriber
3GPP
Release 14 11 3GPP TS 23.018 V14.0.0 (2017-03)
GPRS General Packet Radio Service

HLC Higher Layer Compatibility
HLRB The HLR of the B subscriber
HPLMNB The HPLMN of the B subscriber
IAM Initial Address Message
IPLMN Interrogating PLMN - the PLMN containing GMSCB
IWU Inter Working Unit
LLC Lower Layer Compatibility
MO Mobile Originated
MPTY MultiParTY
MT Mobile Terminated
NDUB Network Determined User Busy
NRCT No Reply Call Timer
PgA Paging Area
PLMN BC (GSM or UMTS) PLMN Bearer Capability
PRN Provide Roaming Number
PUESBINE Provision of User Equipment Specific Behaviour Information to Network Entities
SCUDIF Service Change and UDI/RDI Fallback
SGSN Serving GPRS support node
SIFIC Send Information For Incoming Call
SIFOC Send Information For Outgoing Call
SRI Send Routeing Information
TO Trunk Originated
UDUB User Determined User Busy
UESBI-Iu User Equipment Specific Behaviour Information over the Iu interface
VLRA The VLR of the A subscriber
VLRB The VLR of the B subscriber
VMSCA The Visited MSC of the A subscriber
VMSCB The Visited MSC of the B subscriber
VPLMNA The Visited PLMN of the A subscriber
VPLMNB The Visited PLMN of the B subscriber
4 Architecture
Subclauses 4.1 and 4.2 show the architecture for handling a basic MO call and a basic MT call. A basic
mobile-to-mobile call is treated as the concatenation of an MO call and an MT call.
4.1 Architecture for an MO call

A basic mobile originated call involves signalling between the MS and its VMSC via the BSS, between the VMSC and
the VLR and between the VMSC and the destination exchange, as indicated in figure 1.
In figure 1 and throughout the present document, the term BSS is used to denote a GSM BSS or a UTRAN, as
appropriate.
3GPP
Release 14 12 3GPP TS 23.018 V14.0.0 (2017-03)
Radio I/F signalling Iu or A I/F signalling IAM (ISUP)

BSSA VMSCA
MS
SIFOC
Complete call
VPLMNA VLRA
Figure 1: Architecture for a basic mobile originated call
In figure 1 and throughout the present document, the term ISUP is used to denote the telephony signalling system used
between exchanges. In a given network, any telephony signalling system may be used.
When the user of an MS wishes to originate a call, the MS establishes communication with the network using radio
interface signalling, and sends a message containing the address of the called party. VMSCA requests information to
handle the outgoing call (SIFOC) from VLRA, over an internal interface of the MSC/VLR. If VLRA determines that
the outgoing call is allowed, it responds with a Complete Call. VMSCA:
- establishes a traffic channel to the MS; and

- constructs an ISUP IAM using the called party address and sends it to the destination exchange.
4.2 Architecture for an MT call

A basic mobile terminated call involves signalling as indicated in figure 2. Communication between VMSCB and the
MS is via the BSS, as for the mobile originated case. If VPLMNB supports GPRS and the Gs interface between VLRB
and the SGSN is implemented (see 3GPP TS 23.060 [9]) and there is an association between VLRB and the SGSN for
the MS, the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS. The IPLMN,
containing GMSCB, is in principle distinct from HPLMNB, containing HLRB, but the practice for at least the majority
of current UMTS or GSM networks is that a call to an MS will be routed to a GMSC in HPLMNB.
3GPP
Release 14 13 3GPP TS 23.018 V14.0.0 (2017-03)
Radio I/F
IAM signalling
IPLMN (ISUP) VMSCB BSSB
IAM
(ISUP)
GMSCB SIFIC
MS
Page/ack
Complete call
VLRB VPLMNB
Send Routeing
Info/ack
Provide Roaming
Number/ack
HLRB
HPLMNB
Figure 2: Architecture for a basic mobile terminated call
When GMSCB receives an ISUP IAM, it requests routeing information from HLRB using the MAP protocol. HLRB
requests a roaming number from VLRB, also using the MAP protocol, and VLRB returns a roaming number in the
Provide Roaming Number Ack. HLRB returns the roaming number to GMSCB in the Send Routeing Info ack. GMSCB
uses the roaming number to construct an ISUP IAM, which it sends to VMSCB. When VMSCB receives the IAM, it
requests information to handle the incoming call (SIFIC) from VLRB, over an internal interface of the MSC/VLR. If
VLRB determines that the incoming call is allowed, it requests VMSCB to page the MS. VMSCB pages the MS using
radio interface signalling. When the MS responds, VMSCB informs VLRB in the Page ack message. VLRB instructs
VMSCB to connect the call in the Complete call, and VMSCB establishes a traffic channel to the MS.
4.3 Architecture for a TO call

A basic trunk originated call involves signalling between the PSTN and the PLMNs MSC, as indicated in figure x. The
originating exchange may also be another MSC of the same or different PLMN.
The MSC may also be connected to PBX but that is outside the scope of this document. In the PBX case same
modelling applies but the PBX signalling is different to ISUP.
3GPP
Release 14 14 3GPP TS 23.018 V14.0.0 (2017-03)
IAM GMSCB/
(ISUP/internal) VMSCB
IAM
Originating IAM
(ISUP) MSC
exchange (ISUP)
PSTN
sw itch
IAM
(ISUP)
Other
PLMN
Figure 4.3.1: Architecture for a basic trunk originated call
In figure x and throughout the present document, the term ISUP is used to denote the telephony signalling system used
between exchanges. In a given network, any telephony signalling system may be used.
The MSC receives a setup (IAM) message from the originating exchange. The MSC analyses the called party number
and routes the call to an appropriate destination. If the called party number is an MSISDN the gateway MSC
functionality is activated. If the MSISDN belongs to another PLMN (or is ported out), the call is routed to another
PLMN. If the called number is a PSTN number then the call is routed to (appropriate) PSTN operator. There may be
other destinations also.
5 Information flows
In this clause and clause 7, the terms "security procedures" and "security control" denote the UMTS ciphering and
integrity protection mechanism defined in 3GPP TS 33.102 [32] or the GSM ciphering mechanism defined in
3GPP TS 43.020 [1], as appropriate.
5.1 Information flow for an MO call

An example information flow for an MO call is shown in figure 3; many variations are possible. Signalling over the
radio interface between MSA and BSSA or VMSCA is shown by dotted lines; signalling over the Iu interface (for
UMTS) or the A interface (for GSM) between BSSA and VMSCA is shown by dashed lines; signalling over the B
interface between VMSCA and VLRA is shown by chain lines; and ISUP signalling between VMSCA and the
destination exchange is shown by solid lines.
3GPP
Release 14 15 3GPP TS 23.018 V14.0.0 (2017-03)
MSA BSSA VMSCA VLRA
CM service req
CM service req
Process access req
Authenticate
Authenticate
Authenticate (note 1)
Authenticate resp
Authenticate resp
Authenticate ack
Start security
procedures (note 2)
Process access req
Security control cmd Start security
ack
procedures (note 3)
(note 3)
Security control rsp
Security procedures
complete
Setup
SIFOC
Complete call
Call proceeding
Allocate channel
Assignment cmd
Assignment comp
Allocation complete
IAM
ACM
Alert
ANM
Connect
Connect ack
NOTE 1: Authentication may occur at any stage during the establishment of an MO call; its position in this message
flow diagram is an example.
NOTE 2: Security procedures may be initiated at any stage after authentication; the position in this message flow
diagram is an example.
NOTE 3: If ciphering is not required for a GSM connection, the MSC may send a CM service accept towards the
MS; optionally it may instead send a "start ciphering" request indicating that no ciphering is required. This
option is not available for a UMTS connection [ffs].
NOTE 4: The network may request the IMEI from the MS, and may check the IMEI, at any stage during the
establishment of an MO call, either as part of the procedure to start security procedures or explicitly after
security procedures have started; this is not shown in this message flow diagram.
Figure 3: Information flow for a basic mobile originated call
3GPP
Release 14 16 3GPP TS 23.018 V14.0.0 (2017-03)
When the user wishes to originate a call, MSA establishes a signalling connection with BSSA, and sends a Connection
Management (CM) service request to BSSA, which relays it to VMSCA. VMSCA sends a Process Access Request to
VLRA. VLRA may then initiate authentication, as described in 3GPP TS 33.102 [32] for UMTS and
3GPP TS 43.020 [1] for GSM. VLRA may also initiate security procedures at this stage, as described in
3GPP TS 33.102 [32] for UMTS 3GPP TS 43.020 [1] for GSM. If the user originates one or more new MO calls in a
multicall configuration, MSA sends a CM service request through the existing signalling connection for each new call.
If the MS has performed the Connection Management (CM) service request in a CSG cell, VLRA shall control if the
CSG cell is allowed by the CSG subscription data stored in VLRA. If the CSG cell is not allowed, VLRA shall reject
the Process Access Request.
If the MS has performed the Connection Management (CM) service request in a hybrid cell, VLRA shall set the CSG
membership status in the Process Access Request ack according to the CSG subscription data stored in VLRA.
If VLRA determines that MSA is allowed service, it sends a Process Access Request ack to VMSCA. If VMSCA has
received a Start security procedures message from VLRA, the Process Access Request ack message triggers a Start
security procedures message towards BSSA; otherwise VMSCA sends a CM Service Accept message towards BSSA.
If BSSA receives a Start security procedures message from VMSCA, it initiates security procedures as described in
3GPP TS 33.102 [32] for UMTS and 3GPP TS 43.020 [1] for GSM; when security procedures have been successfully
initiated, MSA interprets this in the same way as a CM Service Accept. If security procedures are not required at this
stage, BSSA relays the CM Service Accept to MSA.
When MSA has received the CM Service Accept, or security procedures have been successfully initiated, MSA sends a
Set-up message containing the B subscriber address via BSSA to VMSCA. MSA also uses the Set-up message to
indicate the bearer capability required for the call; VMSCA translates this bearer capability into a basic service, and
determines whether an interworking function is required. VMSCA sends to VLRA a request for information to handle
the outgoing call, using a Send Info For Outgoing Call (SIFOC) message containing the B subscriber address.
If VLRA determines that the call should be connected, it sends a Complete Call message to VMSCA. VMSCA sends a
Call Proceeding message via BSSA to MSA, to indicate that the call request has been accepted, and sends an Allocate
channel message to BSSA, to trigger BSSA and MSA to set up a traffic channel over the radio interface. The Call
Proceeding message includes bearer capability information if any of the negotiable parameters of the bearer capability
has to be changed. When the traffic channel assignment process is complete (indicated by the Allocation complete
message from BSSA to VMSCA), VMSCA constructs an ISUP IAM using the B subscriber address, and sends it to the
destination exchange.
When the destination exchange returns an ISUP Address Complete Message (ACM), VMSCA sends an Alerting
message via BSSA to MSA, to indicate to the calling user that the B subscriber is being alerted.
When the destination exchange returns an ISUP ANswer Message (ANM), VMSCA sends a Connect message via
BSSA to MSA, to instruct MSA to connect the speech path.
The network then waits for the call to be cleared.
For an emergency call, a different CM service type (emergency call) is used, and the mobile may identify itself by an
IMEI. It is a network operator option whether to allow an emergency call when the mobile identifies itself by an IMEI.
Details of the handling are shown in clause 7.
3GPP
Release 14 17 3GPP TS 23.018 V14.0.0 (2017-03)
5.2 Information flow for retrieval of routeing information for an

MT call
The information flow for retrieval of routeing information for an MT call is shown in figure 4. ISUP signalling between
the originating exchange and GMSCB, and between GMSCB and VMSCB is shown by solid lines; signalling over the
MAP interfaces between GMSCB and HLRB and between HLRB and VLRB, and over the B interface between VLRB
and VMSCB is shown by chain lines; signalling over the Iu interface (for UMTS) or the A interface (for GSM) between
VMSCB and BSSB is shown by dashed lines; and signalling over the radio interface between BSSB and MSB is shown
by dotted lines.
NOTE 1: If pre-paging is used, paging is initiated after VLRB has accepted the PRN message. The paging
procedure is described in subclause 5.3.
NOTE 2: VMSCB starts the timer for the release of radio resources after it sends the Process Access Request
message to VLRB. VMSCB releases the radio resource allocated for the MT call if the timer expires before
the IAM is received, and when the MAP RELEASE_RESOURCES message is received from the GMSC.
NOTE 3: If an ISUP REL message is received at the GMSC between sending of SRI and receiving of SRI ack, the
GMSC does not send IAM to the VMSC. Instead a MAP Release_Resources message may be sent to the
VMSC.
Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call
When GMSCB receives an IAM, it analyses the called party address. If GMSCB can derive an HLR address from the B
party address, it sends a request for routeing information (SRI) to HLRB. If GMSCB supports pre-paging (i.e. it is
prepared to wait long enough for the SRI ack to allow pre-paging to be completed), it indicates this by an information
element in the SRI message.
3GPP
Release 14 18 3GPP TS 23.018 V14.0.0 (2017-03)
HLRB decides whether pre-paging is supported according to the following criteria:
- GMSCB has indicated that it supports pre-paging; and
- HLRB supports pre-paging (i.e. it is prepared to wait long enough for the PRN ack to allow pre-paging to be
completed).
HLRB sends a request for a roaming number (PRN) to VLRB; if pre-paging is supported, it indicates this by an
information element in the PRN message. If Paging Area function is supported in HLRB then HLRB sends the paging
area if stored in HLR. VLRB returns the roaming number in the PRN ack, and HLRB relays the roaming number to
GMSCB in the SRI ack. GMSCB constructs an IAM using the roaming number, and sends it to VMSCB.
If the GMSC performs domain selection through HLR interrogation and the HLR supports domain selection
functionality, HLRB executes domain selection functionaility. The HLR shall:
- send PRN to VLRB as defined in this section , if the result of domain selection is to handle the call in CS
domain; or
- reply with SRI ack without sending PRN to VLRB, if the result of domain selection is to transfer the call from
CS domain to IMS domain.
5.2.1 Mobile Terminating Roaming Retry Call after successful Retrieval of

Routeing Information
The information flow for mobile terminating roaming retry call after successful retrieval of routeing information is
shown in figure 4a. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old
to a new MSC, if the GMSC, the HLR and the old terminating VMSC support the MT Roaming Retry procedure.
In that case, upon receipt of:
- an ISUP IAM message which was preceeded by a MAP Cancel Location procedure, or
- a MAP Cancel Location procedure while on-going paging,
the old VMSC shall instruct the GMSC to resume terminating call procedure by sending a MAP Resume Call Handling
message. The GMSC shall then release the ISUP connection to the old VMSC, terminate any open CAP dialogue, and
retry the terminating call setup towards the new MSC by sending an additional SRI to the HLR. This second SRI
request leads to obtaining a roaming number from the new MSC towards which the call can then be delivered (possibly
after new CAMEL interactions).
An HLR supporting the "mobile terminating roaming retry" feature shall always send a MAP Cancel Location message
message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR
and the old VLR support Super-Charger (see 3GPP TS 23.116 [24]), regardless of whether the new VLR indicates or
not during the location update procedure that the previous network entity must be notified.
NOTE 1: HLRs compliant with an earlier release of the specification and supporting mobile terminating roaming
retry and Super-Charger may not always send a Cancel Location message in a supercharged network. To
support mobile terminating roaming retry with such HLR implemenations, the old VLR can start a timer
upon receipt of the MAP Send Identification message while on-going paging to trigger the sending of an
internal Cancel Location to the old MSC and thus the sending of a MAP Resume Call Handling message
by the old MSC to the GMSC after the sending of the MAP Update Location by the new VLR to the
HLR.
3GPP
Release 14 19 3GPP TS 23.018 V14.0.0 (2017-03)
Old New
GMSC HLR VMSC/VLR VMSC/VLR MS
SRI (B, GMSC@,call Ref.,Roaming retry)1

PRN (call ref.,GMSC@, Roaming retry)2
PRN ACK (MSRN)
SRI ACK
LocUpdate
IAM (MSRN)
Paging
Send Identification2
Authentication Procedure
Update Location
Cancel Location3
Cancel Location Ack
Old MSC stops paging timer and
inform GMSC
Insert Subscriber Data (multiple)
4
RCH (call reference, roaming retry)
ACK
REL
RLC
2nd SRI (B, basic call interrogation)5
HLR delays the sending of PRN

until location update procedure
finishes. 6
Insert Subscriber Data (continued)

Update Location Ack Further procedures
PRN related to location
PRN ACK (MSRN)7 update. E.g.
ciphering, TMSI
2nd SRI ACK (MSRN)7 reallocation.
IAM (MSRN)
New VMSC/VLR may delay setup until

location update procedure finishes.8
LocUpdate Accept
TMSI Realloc Cmplt
Setup
Call Confirmed
Normal MT call procedure follows.
3GPP
Release 14 20 3GPP TS 23.018 V14.0.0 (2017-03)
Figure 4a: Information flow for a mobile terminating roaming retry call after successful Retrieval of
1. A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the
GMSC address and the MT Roaming Retry Supported IE in the first SRI sent to the HLR.
2. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the
GMSC address and the MT Roaming Retry Supported IE in the PRN sent to the MSC/VLR if received in the
SRI.
2'. An old VLR supporting the "mobile terminating roaming retry" feature may indicate in the MAP Send
Identification response sent to the new VLR whether there is a pending mobile terminating call at the old VLR.
3. Receipt of the MT Roaming Retry Supported IE in the PRN indicates that the GMSC supports the Resume Call
Handling procedure and the mobile terminating roaming retry feature. Upon receipt of the ISUP IAM message
which was preceeded by a MAP Cancel Location message, or upon receipt of the MAP Cancel Location
message while paging, the old MSC/VLR stops paging, if paging was on-going, and if it supports the "mobile
terminating roaming retry" feature and did receive the MT Roaming Retry Supported IE in the PRN, sends an
RCH message to the GMSC with the MT Roaming Retry IE. The old MSC shall terminate any open CAP
dialogue when receiving RCH ACK or ISUP REL message.
4. Upon receipt of the RCH message with the MT roaming retry IE, the GMSC acknowledges the RCH message,
releases the call towards the old MSC/VLR, terminates T-CSI dialog with the SCP, if any exists, using T-
Abandon EDP, and re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call
reference number.
5. To avoid looping, the new SRI shall be sent without the Roaming Retry Supported IE. Furthermore, the GMSC
shall use an appropriate high value for the timer supervising receipt of SRI ACK.
Note that the Suppress T-CSI field is not set since the Mobile Terminating procedure is restarted from the
beginning including the handling of CAMEL interaction on T-CSI (this is because T-CSI treatments may end
differently if old and new MSCs are not in the same PLMN or in the same geographical area, e.g. different
charging rates or regional service subscription).
6. Upon receipt of a SRI request or PRN ack (regardless of the PRN response from the old VLR) during an on-
going Update Location procedure, the HLR delays the sending of the PRN to the new VLR till completion of the
Update Location procedure.
7. Receipt of the MSRN' from the new MSC/VLR enables the GMSC to relay the call towards the new MSC/VLR.
8. If the IAM message is received before the Location Update procedure is completed with the MS, the new MSC
may delay the setup of the call until the completion of the Location Update procedure or start at once the normal
terminating call procedure. In the former case, if the Location Update is received with the "follow-on" indication
and if the VMSC supports the "follow-on" indication, the incoming IAM may either be handled as a waiting call
or forwarded as Busy (CFB), depending on the state of the "follow-on" call and the subscriber's subscription
data.
If no IAM message has been received at the time the Location Update procedure completes, the new MSC may
shortly defer the release of the signalling connection with the MS if the old VLR indicated in the MAP Send
Identification response that there is a pending mobile terminating call at the old VLR.
NOTE 2: For a CS Fallback mobile terminating call, the new MSC also defers the release of the signalling
connection with the MS if the MS includes the "CSMT" flag in the Location Update message (see
subclause 7.5 of 3GPP TS 23.272 [42]).
Similarly, a HLR supporting the "mobile terminating roaming retry" feature should wait for the completion of any on-
going Location Update procedure when processing other terminating requests e.g. MAP-SEND-ROUTING-INFO-
FOR-SM, MAP-SEND-ROUTING-INFO-FOR-LCS, MAP-ANY-TIME-INTERROGATION. More generally, this also
applies to all TCAP transactions that the HLR may have to open toward a VLR (e.g. USSD, PSI).
5.2.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing

Information
The information flow for mobile terminating roaming retry call during retrieval of routing information is shown in
figure 4b. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new
3GPP
Release 14 21 3GPP TS 23.018 V14.0.0 (2017-03)
MSC, if the GMSC and the HLR support the MT Roaming Retry procedure. The procedure may e.g. apply during pre-
paging if the GMSC, HLR and old MSC/VLR support pre-paging.
In that case, upon receipt of:
- a MAP Cancel Location procedure while on-going pre-paging,
the old VMSC/VLR shall return a PRN negative response to the HLR. If "Suppress T-CSI" was included in the SRI
request, the HLR shall relay a SRI negative response with the error "absent subscriber" including the reason
"mtRoamingRetry" to the GMSC. If "Suppress T-CSI" was not included in the SRI request, and the called party is
roaming to a different MSC/VLR during the PRN procedure, the HLR may either return a SRI negative response with
the error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC, or instead delay the sending of a
PRN request to the new VLR until completion of the Update Location procedure.
The GMSC shall release the T-CSI dialogue (if existing) and retry the terminating call setup towards the new MSC by
sending an additional SRI to the HLR when receiving a SRI negative response with the error "absent subscriber"
including the reason "mtRoamingRetry". This second SRI request leads to obtaining a roaming number from the new
MSC towards which the call can then be delivered (possibly after new CAMEL interactions).
NOTE 1: If "Suppress T-CSI" was included in the SRI request, the mobile terminating procedure is restarted from
the beginning including the handling of CAMEL interaction on T-CSI, because T-CSI treatments can end
differently if old and new MSCs are not in the same PLMN or in the same geographical area, e.g.
different charging rates or regional service subscription.
An HLR supporting the "mobile terminating roaming retry" feature shall always send a MAP Cancel Location message
message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR
and the old VLR support Super-Charger (see 3GPP TS 23.116 [24]), regardless of whether the new VLR indicates or
not during the location update procedure that the previous network entity must be notified.
NOTE 2: Legacy HLR implementations supporting mobile terminating roaming retry and Super-Charger may not
always send a Cancel Location message in a supercharged network. To support mobile terminating
roaming retry with such HLR implementations, the old VLR can start a timer upon receipt of the MAP
Send Identification message while on-going paging to trigger the sending of an internal Cancel Location
to the old MSC and thus the sending of a PRN negative response to the HLR after the sending of the
MAP Update Location by the new VLR to the HLR.
3GPP
Release 14 22 3GPP TS 23.018 V14.0.0 (2017-03)
Old New
GMSC HLR VMSC/VLR VMSC/VLR MS
1
SRI (B, GMSC@,call Ref.,Roamingretry)
2
PRN (call ref.,GMSC@)
LocUpdate
Pre-Paging
Send Identification 2'
Update Location
Cancel Location 3
Cancel Location Ack
Old MSC/VLR stops pre-paging
timer if it is ongoing pre-paging and
return a PRN negative response
PRN Negative Response 3

4
SRI Negative Response (Absent Subscriber / Roaming retry)
2nd SRI (B, basic call interrogation) 5
HLR delays the sending of PRN

until location update procedure
finishes. 6
Update Location Ack
Further procedures
PRN related to location
PRN ACK (MSRN) 7 update. E.g.
ciphering, TMSI
2nd SRI ACK (MSRN) 7
reallocation.
IAM (MSRN)
New VMSC/VLR may delay setup until

location update procedure finishes. 8
LocUpdate Accept
TMSI Realloc Cmplt
Setup
Call Confirmed
Figure 4b: Information flow for a mobile terminating roaming retry call during Retrieval of Routeing
Information
1. A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number, the
GMSC address, and the MT Roaming Retry Supported IE in the first SRI sent to the HLR. The Pre-paging
Supported IE is included in the SRI message if the GSMC supports the "Pre-paging" feature.
3GPP
Release 14 23 3GPP TS 23.018 V14.0.0 (2017-03)
2. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number and the
GMSC address in the PRN sent to the MSC/VLR if received in the SRI. If GMSC and HLR support the "Pre-
paging" feature, the Pre-paging Supported IE is included in the PRN message.
2'. An old VLR supporting the "mobile terminating roaming retry" feature may indicate in the MAP Send
Identification response sent to the new VLR whether there is a pending mobile terminating call at the old VLR.
3. Upon receipt of the MAP Cancel Location message while pre-paging, the old MSC/VLR stops pre-paging and
sends a PRN negative response message to the HLR. If meanwhile the HLR has received a new Update Location
procedure from a new MSC/VLR, the HLR returns a SRI negative response with error "absent subscriber"
including the reason "mtRoamingRetry" to the GMSC.
4. Upon receipt of the SRI negative response with error "absent subscriber" including the reason
"mtRoamingRetry", the GMSC re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new
call reference number.
5.-8. See the same procedures from step 5 to step 8 in the figure 4a.
Similarly, a HLR supporting the "mobile terminating roaming retry" feature should wait for the completion of any on-
going Location Update procedure when processing other terminating requests e.g. MAP-SEND-ROUTING-INFO-
FOR-SM, MAP-SEND-ROUTING-INFO-FOR-LCS, MAP-ANY-TIME-INTERROGATION. More generally, this also
applies to all TCAP transactions that the HLR may have to open toward a VLR (e.g. USSD, PSI).
5.2.3 Mobile Terminating Roaming Forwarding Call after successful Retrieval

of Routeing Information
The information flow for mobile terminating roaming forwarding (MTRF) call after successful retrieval of routeing
information is shown in figure 4c. It applies to a mobile terminating call while the called mobile is simultaneously
moving from an old to a new MSC, if the old and the new terminating MSC/VLRs support the MT Roaming
Forwarding procedure. The HLR should also support the Mobile Terminating Roaming Forwarding procedure in order
to ensure that roaming forwarding can be offered in all scenarios (e.g. in case of IMSI in the LAU Request from UE).
NOTE 1: The full support of MTRF for roaming scenarios requires both home network (HLR) and visited network
(VLRs) to support the MTRF procedures and protocol extensions. As deployment scenarios may exist
where the home network (HLR) has not been updated to support MTRF the visited network can perform a
limited roaming forwarding solution autonomously if the MTRF Supported flag is signalled in the MAP
Send Identification message under the conditions defined in this clause.
The new terminating VLR shall include an MTRF Supported flag in the MAP Update Location message sent to the
HLR. If the HLR authorises the MTRF call between the old and the new terminating MSCs, the HLR shall include the
MTRF Supported And Authorized flag and the new MSC/VLR numbers in the MAP Cancel Location message sent to
the old VLR. Otherwise if the HLR disallows the MTRF call between the old and the new terminating MSCs, the HLR
shall include the MTRF Supported And Not Authorized flag in the MAP Cancel Location message sent to the old VLR.
The new VLR may also signal the MTRF Supported flag and the new MSC/VLR numbers in the MAP Send
Identification message to indicate to the old VLR that it supports MTRF.
An HLR supporting the "mobile terminating roaming forwarding" feature shall always send a MAP Cancel Location
message message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if
the HLR and the old VLR support Super-Charger (see 3GPP TS 23.116 [24]), regardless of whether the new VLR
indicates or not during the location update procedure that the previous network entity must be notified.
If the old VLR receives a MAP Send Identification message containing the MTRF Supported flag it shall not trigger
any MAP Provide Roaming Number request to the new terminating VLR until is has received the MAP Cancel
Location message.
Upon receipt of a MAP Cancel Location message while ongoing paging, if either of the following is true:
- the MAP Cancel Location message includes the MTRF Supported And Authorized flag or;
- the MAP Cancel Location message does not include the MTRF Supported And Not Authorized flag and the old
VLR has received the MTRF Supported flag earlier in the MAP Send Indentification message,
3GPP
Release 14 24 3GPP TS 23.018 V14.0.0 (2017-03)
the old VLR shall send a MAP Provide Roaming Number request (including the MTRF Indicator and the parameters
received from the HLR in the MAP Provide Roaming Number) to the new terminating VLR. The new terminating
MSC/VLR shall then allocate an MSRN to allow the call to be routed from the old MSC to the new MSC and send it to
the old VLR within the MAP Provide Roaming Number response.
3GPP
Release 14 25 3GPP TS 23.018 V14.0.0 (2017-03)
GMSC HLR Old MSC/VLR New MSC/VLR MS
SRI (B)
PRN
SRI ACK PRN ACK (MSRN) Location Update
IAM (MSRN) Paging
1. Send Identification
(MTRF Supported, new MSC/VLR numbers )
2. Update Location (MTRF Supported)
3. Cancel Location (MTRF Supported And Authorized, New MSC/VLR numbers)

Cancel Location Ack
4. Old MSC stops paging timer
5. If HLR authorises MTRF then use new MSC/VLR

numbers to trigger sending of PRN Req
6. PRN (MTRF Indicator, Old MSC number)
Update Location Ack
Further procedures
7. After Update Location Ack is received, the new
related to location
VLR returns MSRN to the old VLR.
update. E.g.
8. PRN ACK (MSRN) ciphering, IMEI
checking, TMSI
9. IAM (MSRN) reallocation.
10. New VMSC/VLR delays setup until location

update procedure finishes.
Location Update Accept

TMSI Realloc Cmplt
Setup
Call Confirmed
3GPP
Release 14 26 3GPP TS 23.018 V14.0.0 (2017-03)
Figure 4c: Information flow for a mobile terminating roaming forwarding call after successful
Retrieval of Routeing Information
The sequence follows the normal MT terminating call with the following differences:
1. If the Location Update Request contains a valid TMSI/old LAI (e.g. not after the old VLR restart), a new
MSC/VLR supporting the MTRF feature may include the MTRF Supported flag and the new MSC/VLR
numbers in the MAP Send Identification to the old VMSC.
The new VLR shall not include the MTRF Supported flag in the MAP Send Identification message sent to the
old VMSC if the Location Update message received from the MS indicates a CS fallback mobile originating call.
An old VLR supporting the MTRF feature may indicate in the MAP Send Identification response sent to the new
VLR whether there is a pending mobile terminating call at the old VLR.
NOTE 2: it is implementation dependent if the new VLR decides to not include the MTRF Supported flag in the
MAP Send Identification message sent to the old VMSC if the Location Update message received from
the MS contains the "follow-on request pending" flag.
2. A new MSC/VLR supporting the MTRF feature includes the MTRF Supported flag in the MAP Update Location
message sent to the HLR, unless the Location Update message received from the MS indicates a CS fallback
mobile originating call.
NOTE 3: it is implementation dependent if the new VLR decides to not include the MTRF Supported flag in the
MAP Update Location message sent to the HLR if the Location Update message received from the MS
contains the "follow-on request pending" flag.
3. Upon receipt of a MAP Update Location including the MTRF Supported flag, an HLR supporting the MTRF
feature decides whether to authorise MTRF call between the old and the new MSCs based on roaming
agreements with the old and the new MSCs. If MTRF is authorised, the HLR includes the MTRF Supported And
Authorized flag and the new MSC/VLR numbers in the MAP Cancel Location message sent to the old VLR. If
MTRF is not authorised, the HLR includes the MTRF Supported And Not Authorized flag in the MAP Cancel
Location message sent to the old VLR.
4. Upon receipt of a MAP Cancel Location message while on-going paging and if it includes the MTRF Supported
And Authorized flag or if the MAP Cancel Location message does include neither the MTRF Supported And
Authorized flag nor the MTRF Supported And Not Authorized flag but the old MSC/VLR had received earlier
the MTRF Supported flag at step 1, the old MSC/VLR stops paging.
5. If it supports MTRF and decides to apply MTRF based on local operator policy and optionally roaming
agreements with the HLR and new MSC for MTRF, it sends a MAP Provide Roaming Number request
(including the MTRF Indicator and the parameters received from the HLR in the MAP Provide Roaming
Number) to the new terminating VLR.
If the the MAP Cancel Location message does not include the MTRF Supported And Authorized flag and it did
not receive the MTRF Supported flag at step 1 or if the MAP Cancel Location message includes the MTRF
Supported And Not Authorized flag, the old MSC/VLR may initiate the MT Roaming Retry procedure as per
subclause 5.2.1.
If the old MSC supports both the MT Roaming Retry and the MT Roaming Forwarding procedures, and if the
conditions for using these procedures are met, the MSC can decide based on operator policy which procedure to
follow.
6. Upon receipt of the MAP Provide Roaming Number Request, the new MSC/VLR may check roaming
agreements with the HLR and the old MSC for MTRF.
The new MSC/VLR may reject the MAP Provide Roaming Number Request with a cause indicating that the
subscriber is busy if it has received from the MS a CM Service Request indicating a CS mobile originated call.
If the new VLR rejects the MTRF request, the new VLR returns a negative response to the old VLR.
3GPP
Release 14 27 3GPP TS 23.018 V14.0.0 (2017-03)
As an option, the new MSC/VLR may check whether it also performs the GMSC function for the call by
comparing the GMSC address received in the MAP Provide Roaming Number with its own MSC address. If so,
the GMSC / new MSC/VLR may proceed as shown in figure 4ca to deliver the MT call directly to the UE
without further involving the old MSC/VLR.
7. If the new VLR accepts the MAP Provide Roaming Number request, upon successful completion of the MAP
Update Location procedure with the HLR, the new MSC/VLR allocates an MSRN to allow the call to be routed
from the old MSC to the new MSC. As an implementation option, the new MSC/VLR may allocate an MSRN
before completion of the MAP Update Location procedure with the HLR.
8. The new MSC/VLR sends MSRN to the old VLR within the MAP Provide Roaming Number response.
Upon receipt of the MSRN from the new MSC/VLR, the old MSC/VLR terminates any on-going Camel
transaction.
9. Receipt of the MSRN from the new MSC/VLR enables the old MSC to relay the call towards the new MSC.
10. If the IAM message is received before the Location Update procedure is completed with the MS, the new MSC
may delay the setup of the call until the completion of the Location Update procedure or start at once the normal
terminating call procedure. In the former case, if the Location Update is received with the "follow-on" indication
and if the MSC supports the "follow-on" indication, the incoming IAM may either be handled as a waiting call
or forwarded as Busy (CFB), depending on the state of the "follow-on" call and the subscriber's subscription
data.
The Location Update Accept message may be sent to the MS at any time after receipt of the MAP Update
Location Ack from the HLR, i.e. the location update procedure with the MS is not affected by the MT Roaming
Forwarding procedure.
If no MAP Provide Roaming Number request has been received at the time the Location Update procedure
completes, the new MSC may shortly defer the release of the signalling connection with the MS if the old VLR
indicated in the MAP Send Identification response that there is a pending mobile terminating call at the old
VLR.
NOTE 4: For a CS Fallback mobile terminating call, the new MSC also defers the release of the signalling
connection with the MS if the MS includes the "CSMT" flag in the Location Update message (see
subclause 7.5a of 3GPP TS 23.272 [42]).
The MAP Update Location message and Send Identification message may include the new LMSI allocated by the new
terminating MSC/VLR if the MTRF Supported flag is present in those messages. If available, the HLR shall include the
new LMSI in the MAP Cancel Location message it sends to the old VLR if the MTRF Supported And Authorized flag
is present in this message. If available, the old VLR shall include the new LMSI in the MAP Provide Roaming Number
message it sends to the new VLR.
A VLR may also set the MTRF Supported flag in the MAP Update Location message it sends to the HLR upon
establishment of an SGs association (see 3GPP TS 23.272 [42]). This enables in particular mobile terminating roaming
forwarding calls during the mobile terminated CS service delivery via an alternative MME in MME pool procedure
when the new SGs association is established towards a new VLR (see clause 26 of 3GPP TS 23.007 [43]).
The information flow for mobile terminating roaming forwarding (MTRF) call if the GSMC and the new MSC/VLR are
the same node and if they support the option (in step 6) to deliver the MT call directly to the UE without further
involving the old MSC/VLR is shown in figure 4ca.
3GPP
Release 14 28 3GPP TS 23.018 V14.0.0 (2017-03)
New Old
GMSC HLR MS
MSC/VLR MSC/VLR
1. SRI (B, GMSC@, Call Ref.)

PRN (GMSC@, Call Ref.)
SRI ACK PRN ACK (MSRN)
IAM (MSRN)
Paging
Location Update
2. Steps 1 to 5 of MTRF scenario as per figure 4c
3. PRN (MTRF Indicator, old MSC number,

GMSC@, Call Ref.)
Perform MTRF Update Location Ack

Optimal Routing
4. Release
Release Complete
5. New MSC/VLR closes the MAP

dialogue locally.
Complete MTRF
Optimal Routing 5. MAP Abort
Further procedures
related to location
6. New MSC/VLR delays setup
update. E.g.
until location update finishes.
ciphering, TMSI
Location Update Accept reallocation.
TMSI Reallocation Complete

Setup
Call Confirmed
Figure 4ca : Information flow for a mobile terminating roaming forwarding call after successful
Retrieval of Routeing Information with MTRF Optimal Routing when the GMSC and the new MSC/VLR
are the same node
The sequence follows the normal flow for MTRF call after successful Retrieval of Routeing Information (as specified in
figure 4c) with the following differences:
3GPP
Release 14 29 3GPP TS 23.018 V14.0.0 (2017-03)
1. The GMSC shall include the GMSC address and the Call reference number used by the GMSC for this call in the
MAP Send Routing Information . The HLR shall include these parameters in the MAP Provide Roaming
Number if received in the MAP Send Routing Information.
2. Steps 1 to 5 as specified for figure 4c.
3. The new MSC/VLR shall determine that it also performs the GMSC function for the call identified by the Call
Reference Number if the GMSC address received in the MAP Provide Roaming Number matches its own MSC
address.
4. In that case, the GMSC shall send a Release message to the old MSC/VLR. Upon receipt of this message, the old
MSC/VLR shall return a Release Complete message to the GMSC.
5. The new MSC/VLR shall close the MAP Dialogue (initiated in step 3) locally (i.e. MAP-Close service with the
release method set to "pre-arranged end"). Alternatively, the new MSC/VLR may send a MAP Abort message to
the old MSC/VLR after receiving the Release Complete message. The old MSC/VLR shall release all resources
associated to the call (if not already done at step 4).
NOTE 5: The MAP Abort message is sent after receipt of the Release Complete message to avoid the old
MSC/VLR initiating a Release procedure towards the GMSC or invoking Call Forwarding upon receipt
of the MAP Abort message.6. The new MSC/VLR shall then proceed with the establishment of the MT
call without further involving the old MSC/VLR.
NOTE 6: The internal messages between the GMSC and the new MSC/VLR are implementation specific and not
further described in 3GPP specifications.
5.2.4 Mobile Terminating Roaming Forwarding Call during Retrieval of

The information flow for mobile terminating roaming forwarding (MTRF) call during retrieval of routeing information
is shown in figure 4d. It applies to a mobile terminating call while the called mobile is simultaneously moving from an
old to a new MSC, if the old and the new terminating MSC/VLRs support the MT Roaming Forwarding procedure. The
HLR should also support the Mobile Terminating Roaming Forwarding procedure in order to ensure that roaming
forwarding can be offered in all scenarios (e.g. in case of IMSI in the LAU Request from UE); an HLR that supports
Optimal Routeing shall support the requirements defined in this clause to ensure that charging requirements for optimal
routeing are never contravened. The procedure may e.g. apply during pre-paging if the GMSC, HLR and old MSC/VLR
support pre-paging.
The principles and requirements specified for MT Roaming Forwarding Call after successful Retrieval of Routeing
Information (see clause 5.2.3) shall also apply for MT Roaming Forwarding Call during Retrieval of Routeing
Information with the following modifications or clarifications.
When an MSRN is retrieved successfully from the new MSC/VLR, the old MSC/VLR shall return the received MSRN
within the MAP Provide Roaming Number response to the HLR, which allows the call to be routed from the GMSC to
the new MSC.
3GPP
Release 14 30 3GPP TS 23.018 V14.0.0 (2017-03)
Old New
GMSC
GMSC HLR
HLR
Old New
MS
MS
MSC/VLR
MSC/VLR
MSC/VLR
MSC/VLR
SRI (B)
PRN Location Update
Pre-Paging
1. Send Identification (MTRF supported, new MSC/VLR numbers)
2. Update Location (MTRF
Supported)
3. Cancel Location (MTRF Supported And Authorized, new MSC/VLR numbers)
Cancel Location Ack
4. Old MSC stops pre-paging
timer
5. If HLR authorizes MTRF feature then use new MSC/VLR

numbers to trigger sending of PRN req to new VLR
6. PRN (MTRF Indicator, old MSC Number)

Update Location Ack
Further procedures
7. After Update Location Ack is received, the new
VLR returns MSRN to the old VLR. related to location
update. E.g. ciphering,
8. PRN Ack TMSI reallocation.
9. PRN Ack (MSRN, VMSC Address)
10. SRI Ack (MSRN, (MSRN, VMSC Address)
VMSC Address) IAM (MSRN)
11. New MSC/VLR may delay setup until location update
finishes
Location Update
TMSIAccept
Realloc
Cmplt
SETUP
Call Confirmed
Normal MT call procedure follows
Figure 4d: Information flow for a mobile terminating roaming forwarding call during Retrieval of
The sequence follows the normal MT terminating call with the following differences:
1-2. Same as steps 1 and step 2 in figure 4c.
3. Same as step 3 in figure 4c, with the addition that the HLR shall not authorise MTRF between the old and the
new MSCs if routing the call between the GMSC and the new MSC contravenes charging requirements if
Optimal Routeing is supported (see 3GPP TS 23.079[13]).
4. Same as step 4 in figure 4c, where the old MSC/VLR stops pre-paging.
5. Same as step 5 in figure 4c.
6. Same as step 6 in figure 4c. If the OR interrogation indicator is received in the PRN request, the new VLR shall
return a PRN negative response if it does not support Optimal Routeing (see 3GPP TS 23.079 [13]).
3GPP
Release 14 31 3GPP TS 23.018 V14.0.0 (2017-03)
8. The new MSC/VLR returns to the old VLR a MAP Providing Roaming Number response including the MSRN,
the new VMSC Address, and if the new MSC/VLR supports the MAP Release Resource procedure, the
ReleaseResourcesSupported flag.
9. Upon receipt of the MSRN from the new VLR, the old VLR returns the PRN Ack to the HLR including the
MSRN and the VMSC Address received from the new VLR, and the ReleaseResourcesSupported flag if
received from the new MSC/VLR.
10. If the HLR needs to return the VMSC Address to the GMSC (as per the conditions specified in 3GPP TS 29.002
[29]), and if a VMSC Address was received with an MSRN in the PRN Ack, the HLR shall pass in the SRI ack
to the GMSC the MSRN and the VMSC Address received in the PRN ack.
Receipt of the MSRN from the HLR enables the GMSC to relay the call towards the new MSC.
5.3 Information flow for an MT call

An example information flow for an MT call is shown in figure 5; many variations are possible. ISUP signalling
between GMSCB and VMSCB is shown by solid lines; signalling over the B interface between VMSCB and VLRB is
shown by chain lines; signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and
BSSB is shown by dashed lines; and signalling over the radio interface between VMSCB or BSSB and MSB is shown
by dotted lines.
3GPP
Release 14 32 3GPP TS 23.018 V14.0.0 (2017-03)
GMSCB VLRB VMSCB BSSB MSB

IAM
SIFIC
Page MS
Page
Page
Chan req
Imm ass
Page resp
MS conn
Process estab
access req
Start security
proc (note 1)
Process
access req ack Start security Security control
procedures
(note 2) command
Security control
response
Call arrived (note 5)
(note 6)
Complete call
Setup
Call conf
Allocate
channel Assignment
command
Assignment
Allocation complete
complete
Alerting
ACM
Connect
ANM
Connect ack
Complete call
ack
NOTE 1: Security procedures may be initiated at any stage after the network has accepted the page response; the
position in this message flow diagram is an example.
NOTE 2: If Security procedures are not required, the MSC may send a Start security procedures message indicating
that no ciphering is required.
NOTE 3: This message flow diagram assumes that the MS has already been authenticated on location registration.
If this is not so (for the first MT call after VLR restoration), the network may initiate authentication after the
MS responds to paging.
NOTE 4: The network may request the IMEI from the MS, and may check the IMEI, at any stage after the MS
responds to paging, either as part of the procedure to start security procedures or explicitly after security
procedures have been started; this is not shown in this message flow diagram.
NOTE 5: If a connection between MSCB and MSB has been established as a result of pre-paging, the paging
procedure is not performed.
NOTE 6: If a connection between MSCB and MSB has been established as a result of pre-paging, VLRB sends the
Call arrived message to MSCB to stop the guard timer for the release of the radio connection.
Figure 5: Information flow for a basic mobile terminated call
3GPP
Release 14 33 3GPP TS 23.018 V14.0.0 (2017-03)
When VMSCB receives an IAM from GMSCB it sends to VLRB a request for information to handle the incoming call,
using a Send Info For Incoming Call (SIFIC) message containing the roaming number received in the IAM.
If VLRB recognizes the roaming number, and MSB is allowed service, it sends a request to VMSCB to page MSB. If a
radio connection between the network and MSB is already established, VMSCB responds immediately to the page
request. If no radio connection exists, VMSCB sends a page request to BSSB, and BSSB broadcasts the page on the
paging channel. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see
3GPP TS 23.060 [9]) and there is a valid association between VLRB and the SGSN for the MS, the paging signal
towards the MS goes from VMSCB via VLRB and the SGSN to the BSS.
If MSB detects the page, it sends a channel request to BSSB, which responds with an immediate assignment command,
to instruct MSB to use the specified signalling channel. MSB then sends a page response on the signalling channel;
BSSB relays this to VMSCB. VMSCB sends a Process access request message to VLRB to indicate that MSB has
responded to paging. VLRB may then initiate authentication, as described in 3GPP TS 33.102 [32] for UMTS and
3GPP TS 43.020 [1] for GSM. VLRB may also initiate security procedures at this stage, as described in
3GPP TS 33.102 [32] for UMTS and 3GPP TS 43.020 [1] for GSM.
If the MS is paged in a CSG cell, VLRB shall control if the CSG cell is allowed by the CSG subscription data stored in
VLRB. If the CSG cell is not allowed, VLRB shall reject the the Process Access Request.
If the MS is paged in a hybrid cell, VLRA shall set the CSG membership status in the Process Access Request ack
according to the CSG subscription data stored in VLRA.
VLRB may restore CSG data from CSS for a MT call after a VLRB restart.
If VLRB determines that MSB is allowed service, it sends a Process access request ack to VMSCB. The Process access
request ack message triggers a Start security procedures message towards BSSB; if VMSCB has not received a Start
security procedures message from VLRB, the Start security procedures message indicates no ciphering.
VLRB then sends a Complete call message to VMSCB. VMSCB sends a Set-up message towards MSB. The Set-up
message may include bearer capability information for the call.
When MSB receives the Set-up message from BSSB, it responds with a Call confirmed message. The Call Confirmed
message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be
changed. When VMSCB receives the Call confirmed message via BSSB, it sends an Allocate channel message to
BSSB. BSSB instructs MSB to tune to a traffic channel by sending an Assignment command. When MSB has tuned to
the specified traffic channel it responds with an Assignment complete, message, which BSSB relays to VMSCB as an
Allocation complete, and sends an Alerting message to indicate that the called user is being alerted. VMSCB sends an
ACM to GMSCB, which relays it to the originating exchange.
When the called user answers, MSB sends a Connect message, which BSSB relays to VMSCB. VMSCB:
- responds with a Connect ack message towards MSB;
- sends an ANM to GMSCB, which relays it to the originating exchange;
- sends a Complete call ack to VLRB.
The network then waits for the call to be cleared.
6 Principles for interactions with supplementary

services
This clause specifies the principles used to describe the invocation of the GSM or UMTS supplementary services which
were standardized when the present document was drafted. Registration, erasure, activation, deactivation and
interrogation are call-independent operations; they are therefore outside the scope of the present document. Descriptions
may be found in the stage 2 specifications for each supplementary service.
In the modelling used in the present document, each supplementary service which a network entity supports is managed
by a supplementary service handler, which handles data in the entity in which it runs. The call handling processes
defined in the present document use the data to define the contents of messages to other entities. The basic call handling
processes defined in the present document interact with the supplementary service handlers as shown in the SDL
3GPP
Release 14 34 3GPP TS 23.018 V14.0.0 (2017-03)
diagrams and the supporting text. If a network entity does not support a supplementary service, it bypasses the
interaction with the handler for that supplementary service. Exceptions to this general principle are described later in
this clause.
6.1 Call Deflection service (3GPP TS 23.072)

The basic call handling processes ICH_MSC and ICH_VLR interact with the CD supplementary service
(3GPP TS 23.072 [11]) as described in subclauses 7.3.1 and 7.3.2 respectively.
6.2 Line identification services (3GPP TS 23.081)

6.2.1 Calling Line Identification Presentation (CLIP)
The basic call handling processes ICH_VLR and ICH_MSC interact with the processes CLIP_MAF001 and
CLIP_MAF002 (3GPP TS 23.081 [14]) as described in subclauses 7.3.1 and 7.3.2.
6.2.2 Calling Line Identification Restriction (CLIR)

The basic call handling processes OCH_MSC and OCH_VLR interact with the processes CLIR_MAF004 and
CLIR_MAF003 (3GPP TS 23.081 [14]) as described in subclauses 7.1.1 and 7.1.2.
6.2.3 Connected Line Identification Presentation (COLP)

The basic call handling processes OCH_MSC and OCH_VLR interact with the processes COLP_MAF006 and
COLP_MAF005 (3GPP TS 23.081 [14]) as described in subclauses 7.1.1 and 7.1.2.
The basic call handling processes MT_GMSC and ICH_MSC interact with the process COLP_MAF039
(3GPP TS 23.081 [14]) as described in subclauses 7.2.1 and 7.3.1.
6.2.4 Connected Line Identification Restriction (COLR)

The basic call handling processes ICH_VLR and ICH_MSC interact with the processes COLR_MAF040 and
COLR_MAF041 (3GPP TS 23.081 [14]) as described in subclauses 7.3.2 and 7.3.1.
6.3 Call forwarding services (3GPP TS 23.082)

6.3.1 Call Forwarding Unconditional (CFU)
The basic call handling process SRI_HLR interacts with the process MAF007(3GPP TS 23.082 [15]) as described in
subclause 7.2.2.
6.3.2 Call Forwarding on mobile subscriber Busy (CFB)

The basic call handling process ICH_VLR interacts with the process MAF008 (3GPP TS 23.082 [15]) as described in
subclause 7.3.2.
6.3.3 Call Forwarding on No Reply (CFNRy)

subclause 7.3.2.
6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)

The basic call handling processes SRI_HLR and ICH_VLR interact with the process MAF010 (3GPP TS 23.082 [15])
as described in subclauses 7.2.2 and 7.3.2.
3GPP
Release 14 35 3GPP TS 23.018 V14.0.0 (2017-03)
6.4 Call wait (3GPP TS 23.083)

subclause 7.3.2. Further details of the handling of call waiting are given in subclauses 7.3.1 and 7.3.2.
6.5 Call hold (3GPP TS 23.083)

Invocation of call hold before a basic call has been established will be rejected.
The basic call handling processes OCH_MSC and ICH_MSC interact with the procedures Process_Hold_Request and
Process_Retrieve_Request as described in subclauses 7.1.1 and 7.3.1.
6.6 Multiparty (3GPP TS 23.084)

Invocation of multiparty before a basic call has been established will be rejected.
6.7 Closed user group (3GPP TS 23.085)

The basic call handling process OCH_VLR interacts with the process CUG_MAF014 (3GPP TS 23.085 [18]) as
described in subclause 7.1.2.
The basic call handling process SRI_HLR interacts with the process CUG_MAF015 (3GPP TS 23.085 [18]) as
described in subclause 7.2.2.
The interactions between call forwarding and CUG (3GPP TS 23.085 [18]) are handled as described in
subclause 7.2.2.6.
6.8 Advice of charge (3GPP TS 23.086)

The interactions between Advice of Charge (3GPP TS 23.086 [19]) and MO calls are handled as described in
subclauses 7.1.1 and 7.1.2.
The interactions between Advice of Charge (3GPP TS 23.086 [19]) and MT calls are handled as described in
subclauses 7.3.1 and 7.3.2.
6.9 User-to-user signalling (3GPP TS 23.087)

The basic call handling processes OCH_MSC, OCH_VLR, MT_GMSC and ICH_MSC interact with the UUS
supplementary service as described in subclauses 7.1.1, 7.1.2, 7.2.1 and 7.3.1 respectively.
6.10 Call barring (3GPP TS 23.088)

6.10.1 Barring of outgoing calls
The basic call handling process OCH_VLR interacts with the processes MAF017, MAF018 and MAF020
(3GPP TS 23.088 [21]) as described in subclause 7.1.2.
6.10.2 Barring of incoming calls

The basic call handling process SRI_HLR interacts with the processes MAF022, MAF023 and MAF024 (3GPP
TS 23.088 [21]) as described in subclause 7.2.2.
3GPP
Release 14 36 3GPP TS 23.018 V14.0.0 (2017-03)
6.11 Explicit Call Transfer (3GPP TS 23.091)

There is no interaction between Explicit Call Transfer and the basic call handling described in the present document.
6.12 Completion of Calls to Busy Subscriber (3GPP TS 23.093)

The basic call handling processes OCH_MSC, OCH_VLR, MT_GMSC, SRI_HLR, PRN_VLR, ICH_MSC and
ICH_VLR interact with the CCBS supplementary service as described in subclauses 7.1.1, 7.1.2, 7.2.1, 7.2.2, 7.2.3,
7.3.1 and 7.3.2respectively.
6.13 Multicall (3GPP TS 23.135)

The basic call handling processes OCH_MSC, OCH_VLR, ICH_MSC & ICH_VLR interact with the Multicall
supplementary service as described in subclauses subclauses 7.1.1, 7.1.2, 7.3.1 and 7.3.2respectively.
7 Functional requirements of network entities

The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the
SDL diagrams.
The entities described in this clause interwork with other entities over four different types of interface:
- The Iu interface, used to interwork between the MSC and the UTRAN or the UMTS UE;
- The A interface, used to interwork between the MSC and the GSM BSS or the GSM MS;
- The C, D & F interfaces, used to interwork between the MSC & HLR (C), VLR & HLR (D) and MSC & EIR
(F);
- Telephony signalling interfaces, used to interwork between an MSC and another exchange.
The protocols used over the Iu interface are RANAP, which is specified in 3GPP TS 25.413 [27], for interworking with
the UTRAN and DTAP, which is specified in 3GPP TS 24.008 [26], for interworking with the MS.
The protocols used over the A interface are BSSMAP, which is specified in 3GPP TS 48.008 [2], for interworking with
the BSS and DTAP, which is specified in 3GPP TS 24.008 [26], for interworking with the MS.
The protocol used over the C, D & F interfaces is MAP, which is specified in 3GPP TS 29.002 [29].
For the purposes of the present document, the protocol used over telephony signalling interfaces is ISUP, which is
specified in ITU-T Recommendations Q.761[33], Q.762 [34], Q.763 [35] and Q.764 [36]; other telephony signalling
systems may be used instead.
The present document shows the call handling application processes interworking with a protocol handler for each of
the protocols listed above. Each protocol defines supervision timers. If a supervision timer expires before a distant
entity responds to a signal, the handling is as defined in the appropriate protocol specification. In general, the protocol
handler reports timer expiry to the application as an error condition or negative response. Where a timer is shown in the
present document, therefore, it is an application timer rather than a protocol timer. Interworking with the protocol
handlers uses functional signal names which do not necessarily have a one-to-one correspondence with the names of
messages used in the protocols.
An MSC which receives an IAM from an originating exchange may react in three different ways:
- It acts as a transit exchange, i.e. it relays the IAM to a destination exchange determined by analysis of the called
party address, and thereafter relays other telephony signalling between the originating and destination exchange
until the connection is released. This behaviour is not specific to UMTS or GSM;
- It acts as a terminating exchange, i.e. it attempts to connect the call to an MS currently registered in the service
area of the MSC;
3GPP
Release 14 37 3GPP TS 23.018 V14.0.0 (2017-03)
- It acts as a GMSC, i.e. it interrogates an HLR for information to route the call. If the HLR returns routeing
information, the MSC uses the routeing information from the HLR to construct an IAM, which it sends to a
destination exchange determined by analysis of the routeing information from the HLR.
Annex A describes the method which the MSC uses to decide how to process the IAM.
The SDL diagrams in this clause show the handling for a number of optional features and services. If the handling
consists only of a call to a procedure specific to the feature or service, the procedure call is omitted if the entity does not
support an optional feature or service. If the handling consists of more than a call to a procedure specific to the feature
or service, the text associated with each SDL diagram specifies the handling which applies if the entity does not support
an optional feature or service. For simplicity of description, it is assumed that support for Operator Determined Barring
and the Call Forwarding and Call Barring supplementary services is mandatory.
7.1 MO call
7.1.1 Functional requirements of serving MSC
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
3GPP TS 23.093 [23].
7.1.1.2 Procedure Process_Access_Request_MSC

Sheet 1: the processing starting with the input signal "Send UESBI-Iu to Access Network" is specific to PUESBINE. If
the MSC does not support PUESBINE, this signal will not be received.
Sheet 1: the task "Convert IMEISV to UESBI" is defined in 3GPP TS 23.195 [25a].
Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC, the VMSC may encapsulate the request for the
IMEI in the Start security procedures message; the BSS relays the response in the Security procedures 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 3GPP TS 29.010 [31].
Sheet 2: The Start security procedures message may indicate one of several ciphering algorithms, or (for GSM only) 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 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 3GPP TS 23.087 [20].
Sheet 1: the VMSC converts the PLMN bearer capability negotiated between the VMSC and the MS to a basic service
according to the rules defined in 3GPP TS 27.001 [28].
Sheet 1: the procedure CAMEL_N_CSI_CHECK_MSC is specific to CAMEL Phase 3 or later, it is specified in

3GPP TS 23.078 [12].
3GPP
Release 14 38 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 1: the procedure Check_OG_Multicall_MSC 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 variable "On_Hold" is used only if the VMSC supports Call Hold.
Sheet 1, sheet 2, sheet 3, sheet 6: the procedure CCBS_OCH_Report_Failure is specific to CCBS; it is specified in
3GPP TS 23.093 [23].
Sheet 1, sheet 2, sheet 6, sheet 7, sheet 9: 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, sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8, sheet 9: signals are sent to and received from the process
Subs_FSM as described in subclause 7.4.
Sheet 3: 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 3: the procedure CAMEL_OCH_MSC_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the
VMSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 3: the procedure CAMEL_MO_Dialled_Services is specific to CAMEL phase 3 or later; it is specified in

3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "Pass"
exit of the test "Result?".
Sheet 3: the procedure CCBS_Check_OG_Call is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. If the
VMSC does not support CCBS, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 3: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is

specified in 3GPP TS 23.066 [10].
Sheet 3: the procedure UUS_OCH_Set_Info_In_IAM is specific to UUS; it is specified in 3GPP TS 23.087 [20].
Sheet 3: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later; it is specified in

3GPP TS 23.078 [12].
Sheet 3: the procedure CCBS_OCH_Report_Success is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 3, sheet 5: the procedure CAMEL_OCH_LEG1_MSC is specific to CAMEL phase 4 or later; it is specified in
3GPP TS 23.078 [12].
Sheet 4, sheet 7: 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 4: the task "UTU2Cnt := 0" is executed only if the VMSC supports UUS
Sheet 4: the procedure CAMEL_OCH_MSC_ALERTING is specific to CAMEL phase 4 or later; it is specified in

Sheet 5: the procedure CAMEL_OCH_MSC_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12].
If the VMSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 5: the procedure Set_COLP_Info_MSC is specific to COLP.
Sheet 5: the procedure Handle_AoC_MO_MSC is specific to AoC.
Sheet 5: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports
CAMEL phase 3 or later.
Sheet 5: The process CAMEL_OCH_LEG2_MSC is specific to CAMEL phase 4 or later; it is specified in

3GPP TS 23.078 [12].
Sheet 6: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS; they are
specified in 3GPP TS 23.093 [23]. 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".
3GPP
Release 14 39 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 6, sheet 7: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL Phase 1; it is specified in

3GPP TS 23.078 [12].
Sheet 6, sheet 7: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later; it is specified in
3GPP TS 23.078 [12].
Sheet 6, sheet 6: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2 or later; it is specified in
3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 2 or later, processing continues from the "No" exit
of the test "Result=Reconnect?".
Sheet 6, sheet 7, sheet 9: the processing in the branch beginning with the Int_Release_Call input will occur only if the
MSC supports CAMEL.
Sheet 7, sheet 9: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in 3GPP

TS 23.087 [20].
Sheet 8: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later, and
will occur only if the VMSC supports CAMEL phase 2 or later. The procedure CAMEL_OCH_MSC2 is specified in
3GPP TS 23.078 [12].
Sheet 8: the input signal User To User is specific to UUS; it is discarded if the VMSC does not support UUS.
Sheet 8: 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 3GPP TS 23.087 [20].
Sheet 9: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If
the VMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".
the VMSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".
Sheet 10: the procedure Process_Hold_Request is specific to Call Hold; it is specified in 3GPP TS 23.083[16].
Sheet 10: the procedure Process_Retrieve_request is specific to Call Hold; it is specified in 3GPP TS 23.083[16].
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 Send IMEI request to the MS specifies the IMEISV as the requested identity.
The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If a
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
3GPP
Release 14 40 3GPP TS 23.018 V14.0.0 (2017-03)
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 3GPP TS 23.087 [20]. 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 3GPP TS 23.087 [20].

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.
3GPP
Release 14 41 3GPP TS 23.018 V14.0.0 (2017-03)
7.1.1.14 Procedure TCH_Check
Process OCH_MSC OCH_MSC1(1)

Process in the MSC to
handle an outgoing call request
Idle
Signals from the left
are from the BSS
CM
service
request
Process_
Access_
Request_MSC
No
Result=
Pass?
Yes
Wait_For_
Setup
CM
Setup Service
Abort
CCBS_Report_
See TS 23.093
Not_Idle
TCH allocated:=
False
OG_Call_
Setup_MSC
CCBS_Check_
See TS 23.093
Last_Call
Release
call
resources
Idle
Figure 6: Process OCH_MSC
3GPP
Release 14 42 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Process_Access_Request_MSC PAR_MSC1(3)

Procedure in the MSC Signals to/from the left
to handle a request from are to/from the BSS;
the MS for system access signals to/from the right
are to/from the VLR.
Process
Access
Request
Wait_For_
PAR_Result
Trace
Provide
Authenticate Subscriber
IMSI
Activity
Tracing
Obtain_IMSI_ Authenticate_
Active:=
MSC MSC
TRUE
No No
Result= Result=
Pass? Pass?
Yes Yes
Result:= Result:=
Fail Fail
Wait_For_ Wait_For_ Wait_For_

PAR_Result PAR_Result PAR_Result
Wait_For_
PAR_Result
CM Start
Provide Send UESBI-Iu
service security
IMEI to Access Network
abort procedures
Ciphering
Obtain_IMSI_ Convert IMEISV
Required:= See 3GPP TS 23.195
MSC to UESBI-Iu
True
No
Result=
Abort UESBI-Iu
Pass?
Yes
Result:= Result:=
Fail Fail

PAR_Result PAR_Result PAR_Result
Figure 7a: Procedure Process_Access_Request_MSC (sheet 1)
3GPP
Release 14 43 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the MSC Wait_For_ Signals to/from the left
to handle a request from PAR_Result are to/from the BSS;
Process Access Process

Abort Request Access
negative Request ack
response
Yes False
Service type= Ciphering
Page Response? required
No True
Map negative Yes

Service type=
response to Page Response?
reject cause
No
Release CM Service
transaction Reject
Result:= Start CM Service

Fail security Accept
procedures
Wait_For_
TMSI_
Reallocation
CM Provide Check Forward Use

service Setup Abort Existing
IMEI IMEI New TMSI
abort TMSI
Obtain_IMEI_ Check_IMEI_ Map negative

MSC MSC response to
reject cause
No No
Result= Result= Reallocate
Abort Abort
Pass? Pass? TMSI
Yes Yes
Result:= Result:= Result:= Result:=

Fail Fail Fail Pass

TMSI_ TMSI_ TMSI_Ack
Reallocation Reallocation
Figure 7b: Procedure Process_Access_Request_MSC (sheet 2)
3GPP
Release 14 44 3GPP TS 23.018 V14.0.0 (2017-03)

to handle a request from TMSI_Ack are to/from the BSS;
CM TMSI TMSI
service Setup Abort Reallocation Reallocation
abort Failure Complete
Forward Forward
Abort New TMSI New TMSI
negative ack
response
Result:= Result:= Result:=

Fail Fail Pass
Figure 7c: Procedure Process_Access_Request_MSC (sheet 3)
3GPP
Release 14 45 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure OG_Call_Setup_MSC OCS_MSC1(11)

Procedure in the originating VMSC
to set up an outgoing call after a Setup
message has been received from the MS
Alerting sent:=False
Backward call indicator:=No indication
MS connected:=False
Reconnect:=False
UUS1 result sent:=False
On_Hold=False
CAMEL_invocation:=False
UUS_OCH_
Check_ See TS 23.087
Setup
Convert
PLMN BC to
basic service
CAMEL_N_CSI_
See TS 23.078
CHECK_MSC
Check_OG_
See TS 23.135
Multicall_MSC
No
Result=
Pass?
Yes
Release Send Info For

transaction Outgoing Call
CCBS_OCH_
See TS 23.093
Report_Failure
Wait_For_
MO_Call_
Result
Figure 8a: Procedure OG_Call_Setup_MSC (sheet 1)
3GPP
Release 14 46 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the originating VMSC
to set up an outgoing call after a Setup
message has been received from the MS Wait_For_
MO_Call_
Result
Send Info For

Release Complete Outgoing Call
transaction Call negative
response
Convert PLMN BC
to channel
requirement
Call Release
Abort
Proceeding transaction
Establish_
Originating_
TCH_If_
Required
No
Result=
Pass?
Yes
CCBS_OCH_ CCBS_OCH_
See TS 23.093 See TS 23.093
Report_Failure Report_Failure
Figure 8b: Procedure OG_Call_Setup _MSC (sheet 2)
3GPP
Release 14 47 3GPP TS 23.018 V14.0.0 (2017-03)

1
Procedure in the originating VMSC Signals to/from the left
to set up an outgoing call after a Setup are to/from the BSS;
message has been received from the MS signals to/from the right
Set_CLI_ are to/from the destination exchange
Presentation_ unless otherwise marked.
Indicator_
MSC
No
Result=
Call allowed?
Yes
Release CAMEL_OCH_
See TS 23.078 3
transaction MSC_INIT
Yes
Result=
Leg1_only?
No
No
Result= Reconnect:=
A
Pass? True
Yes
CAMEL_MO_
Dialled_ See TS 23.078
Services
A
Leg1_only
Result?
Abort Fail
Pass
Leg1_Status
A
:=Set-up
CCBS_Check_
See TS 23.093
OG_Call
CAMEL_OCH_
See TS 23.078 LEG1_MSC
No
Result= (Leg1_Status)
Pass?
Yes
Idle
Release MOBILE_NUMBER_
PORTABILITY_ See TS 23.066
transaction
IN_OQoD
UUS_OCH_
Set_Info_ See TS 23.087
In_IAM
Call setup Initial

To Subs_FSM
failed Address
Destination address:=
IAM.Called Party Address
CCBS_OCH_ CAMEL_Store_
See TS 23.093 Destination_ See TS 23.078
Report_Failure
Address
(False, False)
Wait_For_
ACM
Figure 8c: Procedure OG_Call_Setup _MSC (sheet 3)
3GPP
Release 14 48 3GPP TS 23.018 V14.0.0 (2017-03)

Wait_For_ are to/from the destination exchange
ACM unless otherwise marked.
Address
Connect
Complete
CCBS_OCH_ CCBS_OCH_
See TS 23.093 See TS 23.093
Report_Success Report_Success
CAMEL_
See TS 23.078
Start_TNRy
Send_
Alerting_If_
Required
No
Result=
Pass?
Yes
CAMEL_OCH_
Release See TS 23.078
MSC_ALERTING
Release
Result?
Fail Reconnect Answer
Pass
Release
UTU2Cnt:=0 3
transaction
Call setup Alerting in

To Subs_FSM To Subs_FSM
failed progress
Wait_For_
Answer
ECT
Answer
request
ECT
To Subs_FSM
request
CAMEL_
See TS 23.078
Stop_TNRy
Wait_For_
Answer
2
Figure 8d: Procedure OG_Call_Setup _MSC (sheet 4)
3GPP
Release 14 49 3GPP TS 23.018 V14.0.0 (2017-03)

2
Procedure in the originating VMSC Signals from the left
to set up an outgoing call after a Setup are from the BSS;
message has been received from the MS signals to the right
are to the process
Subs_FSM
CAMEL_OCH_
See TS 23.078
MSC_ANSWER
No
Result=
Pass?
Yes
Yes
Result= Set_COLP_
Reconnect? Info_MSC
No
Handle_AoC_
3
MO_MSC
Send_Access_
Connect_If_
Required
Yes
Result=
Fail?
No
No
Result=
Call setup
Connect
failed
sent?
Yes
Wait_For_
Connect_Ack
Connect
Ack
MS connected:=
True
Store CW treatment
indicator for this call B
if received in SII2
Call CAMEL_OCH_
See TS 23.078
established LEG2_MSC
No
CAMEL phase 4 or later Leg1_Status
control relationship exists? := Active
Yes
CAMEL_OCH_
B See TS 23.078 LEG1_MSC
(Leg1_Status)
Wait_For_
Idle
Clear
Figure 8e: Procedure OG_Call_Setup _MSC (sheet 5)
3GPP
Release 14 50 3GPP TS 23.018 V14.0.0 (2017-03)

message has been received from the MS Wait_For_ signals to/from the right
ACM are to/from the destination exchange
unless otherwise marked.
Release From Int_Release_

Release destination From gsmSSF
transaction Call
exchange
CCBS_OCH_ CCBS_Check_ CCBS_OCH_

See TS 23.093 If_CCBS_ See TS 23.093 See TS 23.093
Report_Failure Report_Failure
Possible
Store CCBS
Result
CAMEL Phase 2 CAMEL Phase 2

or higher or higher
supported? supported?
No Yes No Yes
Yes Release cause=

No answer
from user?
No
CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_

4
MSC_DISC3 MSC_DISC4 MSC_DISC3 MSC1
No
Result= Release
See TS 23.078
Reconnect? transaction
Yes
3
CCBS
CCBS Possible
Result
CCBS Not
Possible
Release CCBS_
Release Activation_ See TS 23.093 Release
transaction
MSC
Call setup
To Subs_FSM
failed
Figure 8f: Procedure OG_Call_Setup _MSC (sheet 6)
3GPP
Release 14 51 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the originating VMSC Wait_For_Connect_Ack
to set up an outgoing call after a Setup Wait_For_Answer
Release Int_Release_
Release From gsmSSF
transaction Call
CAMEL Phase 2 CAMEL Phase 2

or higher or higher
No Yes No Yes
Yes
Release cause=
No answer from user?
No
CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ Release

See TS 23.078
MSC_DISC3 MSC_DISC4 MSC_DISC3 MSC1 transaction
UUS_MSC_ No
Result=
Reconnect?
UUS1_UUI
Yes
UUS_MSC_
See TS 23.087 Check_ 3
UUS1_UUI
Release
Release Release
transaction
Call setup
To Subs_FSM
failed
Signals to/from the left are to/from the BSS;

signals to/from the right
are to/from the destination exchange
Figure 8g: Procedure OG_Call_Setup _MSC (sheet 7)
3GPP
Release 14 52 3GPP TS 23.018 V14.0.0 (2017-03)

Wait_For_
Answer
User to User to TNRy

Internal
User User expired
UUS_MSC_
Check_UUS2_ See TS 23.087 4 Release
UUI_to_NW
UUS_MSC_ CAMEL_OCH_
See TS 23.087 Check_UUS2_ See TS 23.078
MSC2
UUI_to_MS
Release Reconnect
Result?
Continue,
Release Fail
transaction
Call setup
To Subs_FSM
failed
Wait_For_
Answer
Figure 8h: Procedure OG_Call_Setup _MSC (sheet 8)
3GPP
Release 14 53 3GPP TS 23.018 V14.0.0 (2017-03)

Wait_For_Clear
Release Int_Release_
Release from gsmSSF
transaction Call
UUS_MSC_ UUS_MSC_ Release

Check_ See TS 23.087 Check_ See TS 23.087
transaction
UUS1_UUI UUS1_UUI
CAMEL_OCH_ CAMEL_OCH_
See TS 23.078 See TS 23.078
MSC_DISC1 MSC_DISC2
Yes
Result=
Reconnect?
No
Result= Yes Yes Result=

CAMEL CAMEL 3
handling? handling?
No
No
Release
Release Release
transaction
Call
To Subs_FSM
cleared
Figure 8i: Procedure OG_Call_Setup _MSC (sheet 9)
3GPP
Release 14 54 3GPP TS 23.018 V14.0.0 (2017-03)

to set up an outgoing call after a Setup are to/from the BSS
Wait_For_
Clear
Hold Retrieve
request request
Hold Hold
Yes No No Yes
See 3G TS Process_ Hold Retrieve Process_ See 3G TS

23.083 Hold_ reject reject Retrieve_ 23.083
Request Request
Wait_For_
Clear
Figure 8j: Procedure OG_Call_Setup _MSC (sheet 10)
3GPP
Release 14 55 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the originating VMSC Signals from the left
to set up an outgoing call after a Setup are from the BSS;
message has been received from the MS signals to the right
are to the Subs_FSM process.
Wait_For_
Clear
ECT MPTY
request request
ECT MPTY
request request
Wait_For_
Clear
Figure 8k: Procedure OG_Call_Setup _MSC (sheet 11)
3GPP
Release 14 56 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_IMSI_MSC OIMSI_M1(1)

Procedure in the MSC
to obtain the IMSI from the MS
and relay it to the VLR
Signals to/from the left

are to/from the BSS;
Signals to/from the right Send
are to/from the VLR IMSI
Wait_For_
IMSI
Send IMSI Release Send IMSI

ack transaction negative
response
Release
transaction
Provide
Abort
IMSI ack
Result:= Result:=
Pass Aborted
Figure 9: Procedure Obtain_IMSI_MSC
3GPP
Release 14 57 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Authenticate_MSC AUT_MSC1(1)

to obtain an authentication
response from the MS

Signals to/from the right
Authenticate
are to/from the VLR
Wait_For_
Auth_Response
Authenticate Release Authenticate

response
Authenticate Authenticate
Abort negative
ack
response
Release
transaction
Wait_For_ Result:=
Auth_Result Aborted
Authentication Authentication
accepted rejected
Authentication
rejected
Result:=
Pass
Figure 10: Procedure Authenticate_MSC
3GPP
Release 14 58 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_IMEI_MSC OIMEI_M1(1)

to obtain the IMEI from the MS

Signals to/from the right Send
are to/from the VLR IMEI
Wait_For_
IMEI
Send IMEI Release Send IMEI

response
Release
transaction
Provide
Abort
IMEI ack
Result:= Result:=
Pass Aborted
Figure 11: Procedure Obtain_IMEI_MSC
3GPP
Release 14 59 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Check_IMEI_MSC CIMEI_M1(1)

Procedure in the MSC to check the
IMEI and relay the result to the VLR
Yes
IMEI
Signals to/from the left available?
are to/from the BSS; No
are to/from the VLR
unless marked otherwise.
Send IMEI
Wait_For_
IMEI
CM Send IMEI Send IMEI

service negative ack
abort response
Release
Check IMEI To EIR
transaction
Wait_for_
Abort Check_IMEI_
Result
Result:= Release Check IMEI Check IMEI

negative From EIR From EIR
Aborted transaction ack
response
Check IMEI Check IMEI

Abort negative ack
response
Result:= Result:=
Aborted Pass
Figure 12: Procedure Check_IMEI_MSC
3GPP
Release 14 60 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Establish_Originating_TCH_If_Required EOTCIR1(1)

to establish a Traffic Channel are to/from the BSS;
if one has not been established signals to the right are
for this call to the process Subs_FSM
TCH_Check
Result
Use existing Allocate Aborted, Fail Reject
Allocate
channel
Wait_For_
Allocation_
Complete
Release Allocation Allocation

transaction failure complete
Release
transaction
Result:= Result:= Result:= Result:= Result:=

Pass Fail Pass Fail Rejected
Call setup Call setup

failed failed
Figure 13: Procedure Establish_Originating_TCH_If_Required
3GPP
Release 14 61 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Set_CLI_Presentation_Indicator_MSC CAIND_M1(1)

to determine the CLI
presentation indicator value

are to/from the process
Initiate
CLIR_MAF004
handling
of CLIR
Wait_For_
CLIR_Info
Release Clear Continue

From BSS call
transaction call
handling
Result:= Result:=
Call not Call
allowed allowed
Figure 14: Procedure Set_CLI_Presentation_Indicator_MSC
3GPP
Release 14 62 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Send_Alerting_If_Required SALTIR1(1)

Procedure to send an Signals to the left
Alerting message to the MS are to the BSS
if one is required for this call
True
Alerting sent
False
True Access
Connect
sent
False
Yes
Backward call indicator=
no indication?
No
UUS_MSC_ UUS_OCH_Set_
See TS 23.087 Check_ Alert_And_ See TS 23.087
UUS1_UUI Connect_Param
No
Result=
Pass?
Yes
Progress Alerting
Alerting sent:=
True
Result:= Result:=
Pass Fail
Figure 15: Procedure Send_Alerting_If_Required
3GPP
Release 14 63 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Set_COLP_Info_MSC COINF_M1(1)

to determine the COLP
information to be sent to the MS

Initiate
COLP_MAF006
handling
of COLP
Wait_For_
COLP_Info
Release Continue From

From BSS call Release destination
transaction
handling exchange
Figure 16: Procedure Set_COLP_Info_MSC
3GPP
Release 14 64 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_AoC_MO_MSC AoCMO_M1(1)

to handle AoC signalling
towards the MS for an MO call
Yes
AoC(I)
provisioned?
No
Set
charging
parameters
No
AoC(C)
provisioned?
Yes
Set
charging
parameters
Acknowledgment Acknowledgment
required:= required:=
False True
Figure 17: Procedure Handle_AoC_MO_MSC
3GPP
Release 14 65 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Send_Access_Connect_If_Required SACONIR1(1)

Procedure to send a Signals to/from the left
Connect message are to/from the BSS;
to the MS signals to/from the right
if one is required for this call are to/from the destination exchange
True False
MS
connected
UUS_OCH_
Set_Alert_And_ See TS 23.087
Connect_Param
Facility Connect
No No
Acknowledgment Acknowledgment
required? required?
Yes Yes
Start AoC Start AoC

acknowledgment acknowledgment
timer timer
Wait_For_ Wait_For_
AoC_Ack_F AoC_Ack_C
Charging Release AoC Charging Release Connect AoC

Parameters transaction acknowledgment Parameters transaction Ack acknowledgment
ack timer expired ack timer expired
Release Release
transaction transaction
Release Release

Facility Fail Connect Fail
sent sent
Figure 18: Procedure Send_Access_Connect_If_Required
3GPP
Release 14 66 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure TCH_Check TCH_Ch1(1)

Procedure in originating or terminating Signals to/from the left
VMSC to check if a trafic channel has are to/from the BSS;
been established for this call. signals to/from the right
Subs_FSM
No
Is call
speech?
Yes
Non speech Speech

TCH TCH
required required
Wait_For_
TCH_Result
Release Allocate TCH TCH already

From GMSC Release
transaction TCH available allocated
Result:= Result := Result := Result := Result :=

Aborted Fail Allocate Use existing Reject
Figure 19: Procedure OCH_VLRTCH_Check
3GPP
Release 14 67 3GPP TS 23.018 V14.0.0 (2017-03)
7.1.2 Functional requirements of VLR
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.
3GPP
Release 14 68 3GPP TS 23.018 V14.0.0 (2017-03)
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 is:
- blacklisted, then service is not granted;
- greylisted, then service is granted, but the network operator may decide to initiate tracing;
- whitelisted, 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].
3GPP
Release 14 69 3GPP TS 23.018 V14.0.0 (2017-03)
Process OCH_VLR OCH_VLR1(1)

Process in the VLR
to handle an outgoing
(MO) call setup request

are to/from the MSC.
Idle
Process
Access
Request
Process_
Access_
Request_VLR
No
Result=
Pass
Yes
Wait_For_
Idle
SIFOC
Send Info
For Outgoing Abort
Call
Yes
Emergency
Idle
call?
No
Complete OG_Call_
Call Subscription_
Check_VLR
Idle Idle
Figure 7.1.2.1: Process OCH_VLR
3GPP
Release 14 70 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Process_Access_Request_VLR PAR_VLR1(5)

Procedure in the VLR Signals to/from the left
to handle a request from are to/from the MSC
the MS for system access
IMEISV
stored?
Yes
No
Obtain_
IMEI_VLR
PUESBINE
supported? PUESBINE
supported?
Yes
No
Result=
Pass?
No Yes
Yes
Result:=
Aborted
Send UESBI-Iu
to Access Network
No
No
Identity
known?
Yes
Obtain_
Identity_VLR
YesResult=
Pass?
Identity= Yes No
IMEI?
No Result= No
No Fail?
Authentication
required?
Yes Yes
Authenticate_
VLR
No
Result=
Pass?
Yes
IMSI
detached:=
False
Confirmed by Set negative Set negative Result:=

Radio Contact:= response: response: Aborted
True System Unidentified
Failure Subscriber
2 1 3 3
Figure 7.1.2.2a: Procedure Process_Access_Request_VLR (sheet 1)
3GPP
Release 14 71 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the VLR
to handle a request from 1
True Location info

confirmed
in HLR
False
Update_
Location_VLR
No Mobile Not
Reachable
Flag set?
Yes
Subscriber_
See TS 29.002
Present_VLR
False
Data confirmed
by HLR
True Set negative
response:
Unidentified
Subscriber
No
Roaming allowed
in current LA?
Yes Set negative
response:
Roaming
No Not Allowed
Tracing
required?
Yes
Start_
Tracing_VLR
No
Ciphering
required?
Yes
4 5 3
Figure 7.1.2.2b: Procedure Process_Access_Request_VLR (sheet 2)
3GPP
Release 14 72 3GPP TS 23.018 V14.0.0 (2017-03)

to handle a request from 4 5
Signals to the left

are to the MSC.
Start
security
procedures
Identity:=
IMSI
Process
Access
Request ack
No
IMEI check
required?
Yes
Check_
IMEI_VLR
No
Result=
Pass?
Yes
TMSI No No
Result=
reallocation Fail?
required?
Yes Yes
CCBS_Report_
See TS 23.093
MS_Activity
Forward Use IMSI

New TMSI Existing detached:=
TMSI True
Freeze Result:= Set negative Result:=

existing Pass response: Aborted
TMSI Illegal
Equipment
Wait_For_
3
TMSI_Ack
Figure 7.1.2.2c: Procedure Process_Access_Request_VLR (sheet 3)
3GPP
Release 14 73 3GPP TS 23.018 V14.0.0 (2017-03)

to handle a request from
Signals from the left Wait_For_

are from the MSC. 2
TMSI_Ack
Yes
Result=
Aborted? Forward Forward
New TMSI New TMSI
No
Result:= ack negative
Aborted response
Result= Yes
Procedure
Error? Unfreeze
existing
No Set negative TMSI
response:
System
Result= Yes Failure
Unknown
Subscriber? CCBS_Report_
See TS 23.093
No MS_Activity
Result= Yes
Unidentified
Subscriber? Result:=
No Set negative Pass
response:
Unidentified
Subscriber
Set negative
response:
Illegal
Subscriber
Figure 7.1.2.2d: Procedure Process_Access_Request_VLR (sheet 4)
3GPP
Release 14 74 3GPP TS 23.018 V14.0.0 (2017-03)

to handle a request from 3
Signals to the left

are to the MSC.
CM service type
=Emergency call?
No
Yes
Emergency call
setup allowed
without SIM?
No
Yes
No
IMEI
required?
Yes
Obtain_
IMEI_VLR
No
Result=
Pass?
Yes
Yes
Identity:= Result=
IMEI Fail?
No Process Access
Request Ack already sent ?
Process
Access No Yes
Request ack
Process Access
Request Abort
negative
CCBS_Report_ response
See TS 23.093
MS_Activity

Pass Aborted Fail
Figure 7.1.2.2e: Procedure Process_Access_Request_VLR (sheet 5)
3GPP
Release 14 75 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure OG_Call_Subscription_Check_VLR OCSCVLR1(2)

to perform subscription
checks for an outgoing call
Signals to the left

are to the MSC No
Basic
service
provisioned?
Yes
Check_OG_ Set negative Bearer service

See TS 23.135 response:
Multicall_VLR or teleservice
Basic service
not provisioned
No
Result=
Pass?
Yes
Check_
BAOC
Result= Yes
Call
barred?
No
OG_CUG_ Set negative

Check response:
Call barred
Result= No
Call
allowed?
Yes
Get_LI_ Set negative
Subscription_ response:
Info_MO_VLR CUG reject
Get_AoC_
Subscription_
Info_VLR
UUS_OCH_
Check_
Provision
No
Result=
Pass?
Yes
Send Info
For Outgoing
Call negative
response
Figure 7.1.2.3a: Procedure OG_Call_Subscription_Check_VLR (sheet 1)
3GPP
Release 14 76 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure OG_Call_Subscription_Check_VLR OCSCVLR2(2)

Procedure in the VLR Signals to the left
to perform subscription are to the MSC
checks for an outgoing call
1
CAMEL_
See TS 23.078
OCH_VLR
Yes
Result=
Fail?
No
Check_OG_
Barring
Yes
Call
barred?
No
Set negative
response:
Call barred
Complete Send Info

Call For Outgoing
Call negative
response
Figure 7.1.2.3b: Procedure OG_Call_Subscription_Check _VLR (sheet 2)
3GPP
Release 14 77 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_Identity_VLR OID_VLR1(1)

to obtain the identity of an MS
Yes
Identity=
IMSI?
No
Identification
allowed?
No
Yes
Obtain_
IMSI_VLR
No
Result=
Pass?
Yes
No
IMSI
known?
Yes

Fail Pass Aborted
Figure 7.1.2.4: Procedure Obtain_Identity_VLR
3GPP
Release 14 78 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_IMSI_VLR OIMSI_V1(1)

Process in the VLR
to obtain the IMSI
from the MS via the MSC

are to/from the MSC.
Provide
IMSI
Wait_For_
IMSI
Provide
Abort
IMSI ack
Result:= Result:=
Pass Aborted
Figure 7.1.2.5: Procedure Obtain_IMSI_VLR
3GPP
Release 14 79 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Authenticate_VLR AUT_VLR1(2)

to authenticate an MS
via the MSC

are to/from the MSC. Yes
Authentication
sets available?
No
Obtain_
Authentication_
Sets_VLR
No
Result=
2
Pass?
Yes
Yes
Result=
Authenticate
Aborted?
No
Yes Result= Wait_For_

Result:=
Aborted Procedure Authenticate_
Error? Result
No
Result:= Result:= Authenticate Authenticate

Procedure Unknown negative Abort
ack
Error Subscriber response
No Authentication
Received SRES=
expected SRES? failure
report
Yes
More No More No
authentication authentication
sets needed? sets needed?
Yes Yes
Fetch_ Fetch_
Authentication_ Authentication_
Sets_VLR Sets_VLR
Authentication
accepted
Result:= Result:=
Pass Aborted
Figure 7.1.2.6a: Procedure Authenticate_VLR (sheet 1)
3GPP
Release 14 80 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Authenticate_VLR AUT_VLR2(2)

to authenticate an MS 1
via the MSC
Signals to the left

are to the MSC. Yes
Identity=IMSI?
No
Retry No
with
IMSI?
Yes
Obtain_
IMSI_VLR
No
Result=
Pass?
Yes
No
IMSI
known?
Yes
IMSI Yes
matches
TMSI?
No
accepted rejected
Authentication
failure
report
Result:= Result:= Identity:= Result:=

Aborted Unidentified IMSI Illegal
Subscriber Subscriber
Figure 7.1.2.6b: Procedure Authenticate_VLR (sheet 2)
3GPP
Release 14 81 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_Authentication_Sets_VLR OAS_VLR1(2)

to obtain authentication
sets from the HLR

are to/from the HLR
Send
Authentication
Info
Wait_For_
Authentication_
Sets
Send Send
Info ack Info negative
response
Yes No
Empty Unknown
result? Subscriber?
No Yes
Authentication No
sets available
in VLR?
Yes
Yes Re-use No
old
sets?

Pass Procedure Unknown
Error Subscriber
Figure 7.1.2.7a: Procedure Obtain_Authentication_Sets_VLR (sheet 1)
3GPP
Release 14 82 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_Authentication_Sets_VLR OAS_VLR2(2)

to obtain authentication
sets from the HLR
Signals to/from the left Wait_For_

are to/from the MSC; Authentication_
Signals to/from the right Sets
are to/from the HLR
Abort Abort
No
Authentication
Abort
sets available?
Yes
Yes Re-use No
old
sets?

Aborted Pass Procedure
Error
Figure 7.1.2.7b: Procedure Obtain_Authentication_Sets_VLR (sheet 2)
3GPP
Release 14 83 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Start_Tracing_VLR ST_TR_V1(1)

to request the MSC to
start activity tracing
Signals to the left

are to the MSC. No
Tracing
active?
Yes
Trace
Subscriber
Activity
Figure 7.1.2.8: Procedure Start_Tracing_VLR
3GPP
Release 14 84 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Check_IMEI_VLR CIMEI_V1(1)

to request the MSC to
check an IMEI

are to/from the MSC
Check
IMEI
Wait_For_
Check_IMEI_
Result
Check Check
Abort IMEI negative IMEI ack
response
No
Service
granted?
Yes

Aborted Fail Pass
Figure 7.1.2.9: Procedure Check_IMEI_VLR
3GPP
Release 14 85 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_IMEI_VLR OIMEI_V1(1)

Process in the VLR
to obtain the IMSI
from the MS via the MSC

are to/from the MSC
Provide
IMEI
Wait_For_
IMEI
Provide
Abort
IMEI ack
Store IMEISV
Result:= Result:=
Pass Aborted
Figure 7.1.2.10: Procedure Obtain_IMEI _VLR
3GPP
Release 14 86 3GPP TS 23.018 V14.0.0 (2017-03)
Process Fetch_Authentication_Sets_VLR FAS_VLR1(1)

Process in the VLR
to retrieve authentication
sets from the HLR
Obiain_
Authentication_
Sets_VLR
Figure 7.1.2.11: Process Fetch_Authentication_Sets_VLR
3GPP
Release 14 87 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Check_BAOC CBAOC1(1)

Procedure to check call
request against ODBAOC
and SS BAOC

are to/from the process Yes
MAF017 Operator determined BAOC
imposed?
No
Result:= Initiate
Call barred handling
(ODB) of BAOC
Wait_For_
BAOC_
Response
Continue
From MSC Abort call
handling
Yes
Call
barred?
No
Result:= Result:=
Call barred Call allowed
(SS barring)
Figure 7.1.2.12: Procedure Check_BAOC
3GPP
Release 14 88 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure OG_CUG_Check OG_CUG1(1)

Procedure to carry out
CUG authorisation check
for an outgoing (MO) call

outgoing
CUG_MAF014
call
request
Wait_For_
CUG_Response
response complete call reject

From MSC Abort to call (conditional call
request CUG info) (cause)
Result:= Result:=
Call allowed Call barred
Figure 7.1.2.13: Procedure OG_CUG_Check
3GPP
Release 14 89 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Get_LI_Subscription_Info_MO_VLR GLI_MOV1(1)

to retrieve subscription
information for the CLIR
& COLP line identification
services for an MO call
Initiate
handling To process CLIR_MAF003
of CLIR
Wait_For_
CLIR_Info
Continue
From MSC Abort call From process CLIR_MAF003
handling
Initiate
handling To process COLP_MAF005
of COLP
Wait_For_
COLP_Info
Continue
From MSC Abort call From process COLP_MAF005
handling
Figure 7.1.2.14: Procedure Get_LI_Subscription_Info_MO_VLR
3GPP
Release 14 90 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Get_AoC_Subscription_Info_VLR GAOCI_V1(1)

to determine the subscription
to Advice of Charge services
Yes
AoC(I)
provisioned?
No
No
AoC(C)
provisioned?
Yes
Set indicator: Set indicator: Set indicator:

AoC not AoC(C) AoC(I)
provisioned provisioned provisioned
Figure 7.1.2.15: Procedure Get_AoC_Subscription_Info_VLR
3GPP
Release 14 91 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Check_OG_Barring COB1(3)

request against SS barring
and ODB categories
Yes
Operator determined
BOIC imposed?
No No
Destination address CC=
Local CC?
Yes
Yes
Operator determined
BOIC-exHC imposed?
Yes No
Local CC?
No
1
No
HPLMN CC?
Yes
Yes
Operator determined
BOIZC imposed?
No No
Destination address ZC=
Local ZC?
Yes
Yes
Operator determined
BOIZC-exHC imposed?
Yes No
Local ZC?
No
1
No
HPLMN CC?
Yes
Result:=
Call barred
(ODB)
Figure 7.1.2.16a: Procedure Check_OG_Barring (sheet 1)
3GPP
Release 14 92 3GPP TS 23.018 V14.0.0 (2017-03)

request against SS barring 1
and ODB categories
No Operator determined
BOIC-exHC&BOIZC
imposed?
Yes
2
Yes
Local ZC?
No
Yes
Local CC?
No
2
No
HPLMN CC?
Yes
Result:=
Call barred
(ODB)
Figure 7.1.2.16b: Procedure Check_OG_Barring (sheet 2)
3GPP
Release 14 93 3GPP TS 23.018 V14.0.0 (2017-03)

2
and ODB categories
Yes
Call
barred?
No
Initiate
handling To process MAF018
of BOIC
Wait_For_
BOIC_
Response
Continue
From MSC Abort call From process MAF018
handling
Yes
Call
barred?
No
Initiate
handling To process MAF020
of BOIC-exHC
Wait_For_
BOIC-exHC_
Response
Continue
From MSC Abort call From process MAF020
handling
Yes
Call
barred?
No
Result:= Result:=
Call barred Call allowed
(SS barring)
Figure 7.1.2.16c: Procedure Check_OG_Barring (sheet 3)
3GPP
Release 14 94 3GPP TS 23.018 V14.0.0 (2017-03)
Process Update_Location_VLR UL_VLR1(1)

Process in the VLR
to update the location
information in the HLR.
Update_HLR_
See TS 23.012
VLR
Figure 7.1.2.17: Process Update_Location_VLR
3GPP
Release 14 95 3GPP TS 23.018 V14.0.0 (2017-03)
7.2 Retrieval of routeing information for MT call

7.2.1 Functional requirements of GMSC
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

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.
3GPP
Release 14 96 3GPP TS 23.018 V14.0.0 (2017-03)
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 21 Call rejected
interaction violation)
CUG reject (Incoming calls barred 55 Incoming calls barred within CUG
within CUG)
CUG reject (Subscriber not 87 User not member of CUG
member of CUG)
CUG reject (Requested basic 87 User not member of CUG
service violates CUG constraints)
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 Unallocated (unassigned) number
26 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.

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"
3GPP
Release 14 97 3GPP TS 23.018 V14.0.0 (2017-03)
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
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].
will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL_MT_GMSC_DISC5 is
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
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".
3GPP
Release 14 98 3GPP TS 23.018 V14.0.0 (2017-03)
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

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.

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

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".

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.
3GPP
Release 14 99 3GPP TS 23.018 V14.0.0 (2017-03)
7.2.1.4 Procedure Send_Answer_If_Required

7.2.1.5 Procedure Send_Network_Connect_If_Required

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?".


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
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"
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.
3GPP
Release 14 100 3GPP TS 23.018 V14.0.0 (2017-03)
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].
the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".
the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=Reconnect?" .
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].
3GPP
Release 14 101 3GPP TS 23.018 V14.0.0 (2017-03)
7.2.1.9 Macro CUG_Support_Check_GMSC
Process MT_GMSC MT_GMSC1(9)

Process in the GMSC to Signals to/from the left
handle a mobile-terminated are to/from the originating exchange;
call request signals to/from the right
are to/from the destination MSC
unless marked otherwise
Idle
Initial
Address
CUG_Support_
1
Check_GMSC
ACM sent:=False
Reconnect:= Answer sent:=False
True Network connect sent:=False
Reconnect:=False
Resume call:=False
UUS CF Interaction:=False
MNP_MT_GMSC_
See TS 23.066 Set_MNP_
Parameters
OR_Set_ORA_
See TS 23.079
Parameters
CAMEL_Set_
See TS 23.078
ORA_Parameters
Figure 36a: Process MT_GMSC (sheet 1)
3GPP
Release 14 102 3GPP TS 23.018 V14.0.0 (2017-03)

handle a mobile-terminated are to/from the originating exchange;
call request signals to/from the right
4 are to/from the destination MSC
Obtain_Routeing_Address
(Called party address, Reference address,
OR, Own PLMN, Routeing address,
Destination address, Result)
Result?
Leg1_only
Fail Aborted Routeing Number Forward
Pass Leg1_status
:= Set-up
CAMEL_MT_
Set
See TS 23.078 LEG1_GMSC
cause
(Leg1_status)
Release Idle
Release Initial Address Initial Address Initial Address

call (Routeing (Routeing (Routeing To process MT_CF_MSC
resources Address) Address) Address)
CAMEL_Store_ CAMEL_Store_
Idle See TS 23.078 Destination_ Destination_ See TS 23.078
Address Address
(OR, False) (OR, False)
Send_ACM_ Send_ACM_ To originating

If_Required If_Required exchange
Wait_For_ Wait_For_
ACM Forward_ACM
Figure 36b: Process MT_GMSC (sheet 2)
3GPP
Release 14 103 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the GMSC to Signals from the right are
handle a mobile-terminated from the destination exchange
call request
Wait_For_
ACM
Address
Connect
Complete
Send_ACM_
If_Required
CAMEL_
See TS 23.078
Start_TNRy
CAMEL_MT_
See TS 23.078
MSC_ALERTING
Answer Else
Result?
Pass
Wait_For_
Answer
Answer
CAMEL_
See TS 23.078
Stop_TNRy
CAMEL_MT_ CAMEL_MT_
See TS 23.078 See TS 23.078
GMSC_ANSWER GMSC_ANSWER
Else Else
Result? Result?
Pass Pass
Set destination Set destination

Release Reconnect
address Result? address
parameter parameter
Fail
Send_Network_
Send_Answer_
Release 1 Connect_If_
If_Required
Required
3 Idle 3
Figure 36c: Process MT_GMSC (sheet 3)
3GPP
Release 14 104 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the GMSC to
handle a mobile-terminated
call request Signals from the right are
Wait_For_ from the process MT_CF_MSC
Forward_ACM
Address
Connect
Complete
Send_ACM_
If_Required
CAMEL_MT_
See TS 23.078
MSC_ALERTING
Answer Else
Result?
Pass
Wait_For_
Forward_
Answer
Answer
CAMEL_MT_ CAMEL_MT_
See TS 23.078 See TS 23.078
GMSC_ANSWER GMSC_ANSWER
Else Else
Result? Result?
Pass Pass
Handle_COLP_ Handle_COLP_
Release Reconnect
Forwarding_ Result? Forwarding_
Interaction_MSC Interaction_MSC
Fail
Set COLP Set COLP

presentation Release 1 presentation
indicator indicator
Set destination Set destination

address Idle address
parameter parameter
Send_Network_
Send_Answer_
Connect_If_
If_Required
Required
3 3
Figure 36d: Process MT_GMSC (sheet 4)
3GPP
Release 14 105 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the GMSC to Wait_For_ACM, Signals to/from the right
handle a mobile-terminated Wait_For_Answer are to/from the destination MSC
call request unless marked otherwise
Resume Refer to TS 23.079 for

Call message contents
Handling
MT Roaming
Retry supported
Yes
No
MT Roaming
Retry IE received No
Yes CCBS_MT_GMSC_
Check_CCBS_ See TS 23.093
Resume Call Possible
Handling Ack
Resume call:-
True
Release
CAMEL_
see TS 23.078
CAMEL_ Stop_TNRy
MT_GMSC_
DISC6
OR_Handle_
See TS 23.079
RCH
Clear MT Roaming
Retry IE := true
Yes
Result=
Fail?
Resume call := true
No
Yes
Result=
Release?
4
No
Yes Result=
Release
Refuse?
No
Yes
Result=
Reconnect?
No
Wait_For_
- 1 Idle
Forward_ACM
Figure 36e: Process MT_GMSC (sheet 5)
3GPP
Release 14 106 3GPP TS 23.018 V14.0.0 (2017-03)

handle a mobile-terminated Wait_For_ are to/from the originating MSC;
call request Answer signals to/from the right
are to/from the destination MSC
TNRy
Internal
expired
2 Release
CAMEL_MT_
See TS 23.078
GMSC_DISC5
Release Reconnect
Result?
Continue,
Fail
Release
Release call
resources
Idle 1
Figure 36f: Process MT_GMSC (sheet 6)
3GPP
Release 14 107 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the GMSC to Wait_For_ACM, Signals to/from the left
handle a mobile-terminated Wait_For_Forward_ACM, are to/from the originating exchange;
call request Wait_For_Answer, signals to/from the right
Wait_For_Forward_Answer are to/from the destination exchange
or process MT_CF_MSC
Int_Release_
Release Release From gsmSSF
Call
CCBS_MT_GMSC_
Check_CCBS_ See TS 23.093
Possible
CAMEL phase 2 CAMEL phase 2

or higher or higher
No Yes No Yes
Yes
Release cause=
No
CAMEL_MT_ CAMEL_MT_ CAMEL_MT_ CAMEL_MT_

See TS 23.078
GMSC_DISC3 GMSC_DISC6 GMSC_DISC3 GMSC_DISC4
No
Result=
Release
Reconnect?
Yes
CCBS_Set_
Diagnostic_
For_Release
Release Release 1 Release
Release call
resources
Idle
Figure 36g: Process MT_GMSC (sheet 7)
3GPP
Release 14 108 3GPP TS 23.018 V14.0.0 (2017-03)

handle a mobile-terminated Wait_For_ are to/from the originating exchange;
call request Clear signals to/from the right
or the process MT_CF_MSC
Int_Release_
Call
CAMEL_MT_ CAMEL_MT_
See TS 23.078 See TS 23.078
GMSC_DISC1 GMSC_DISC2
Yes Reconnect CAMEL handling

Result=
CAMEL Result? Release
handling?
No Normal handling
Release 1 Release Release
Release call
resources
Wait_For_
Idle
Clear
Resume Wait_For_ACM,
Call Wait_For_Forward_ACM,
Handling Wait_For_Answer,
Wait_For_Forward_Answer,
Wait_For_Clear
Set negative
response: OR * *
not allowed
Resume Call
Handling - -
negative
response
Wait_For_
-
Clear
Figure 36h: Process MT_GMSC (sheet 8)
3GPP
Release 14 109 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the GMSC to
handle a mobile-terminated
call request
CAMEL phase 4 or later No

control relationship exists?
Yes
Leg1_status
:= Active
CAMEL_MT_ Wait_For_
See TS 23.078
LEG1_GMSC Clear
(Leg1_status)
CAMEL_MT_
See TS 23.078
GMSC_LEG2
Idle
Figure 36i: Process MT_GMSC (sheet 9)
3GPP
Release 14 110 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Obtain_Routeing_Address ORA1(6)

Procedure in a GMSC Procedure Obtain_Routeing_Address
to determine the address FPAR IN Input address, Reference address,
to which a call should be routed Own PLMN
IN/OUT Routeing address,
Destination address, OR, Result
MOBILE_NUMBER_
See TS 23.066 PORTABILITY_
IN_TQoD
Result= Yes
Number
ported?
No
CCBS_MT_ Routeing
See TS 23.093 GMSC_Check_ address:=
CCBS_Call routeing number
Reconnect
Result:=
True Routeing
False
number
See TS 23.081 CLI_MT_
GMSC
Pre-paging
supported
in GMSC?
No
Yes
Set Pre-paging
supported
MT Roaming
Retry supported
Yes No
Clear MTRoaming
Retry IE true
false
set MT Roaming
Retry Supported IE
Send
To HLR Routeing
Info
Wait_for_
Routeing_ 1
Info
Figure 37a: Procedure Obtain_Routeing_Address (sheet 1)
3GPP
Release 14 111 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in a GMSC Signals to/from the left
to determine the address Wait_for_ are to/from the originating exchange;
to which a call should be routed signals to/from the right
Routeing_
Info are to/from the HLR
Send
Routeing
Release Info negative
response
If MT Roaming Retry is supported

Yes
and MT Roaming Retry Indicator received?
Set: Clear RoamingRetry
Call Released Supported IE
No
Call Released?
Wait_for_
Yes Send Routeing Info
Routeing_
Info No
Result:= SCUDIF_negative_
SRI_response_ See TS 23.172
Aborted
handling Wait_for_Routeing_Info
Result
Fail
Pass Retry
Send Routeing Info
OR_Handle_SRI_
4 Negative_Response See TS 23.079
(Own PLMN)
Result= Wait_for_
Pass? Routeing_
Yes Info
No
Result:=Pass
No Error=
Unknown
subscriber?
Yes
MOBILE_NUMBER_
See TS 23.066 PORTABILITY_
IN_QoHR
No Result=
Number
ported?
Yes
Routeing
address:=
routeing number
Result:=Fail
Result:=
Routeing
number
Figure 37b: Procedure Obtain_Routeing_Address (sheet 2)
3GPP
Release 14 112 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in a GMSC
to determine the address
to which a call should be routed
Wait_for_
Routeing_
Info
Send
Routeing From HLR
Info ack
Yes
Call Relaesed?
No
MSRN received?
No SCUDIF_Check_
See TS 23.172
Service_Availability
Yes
Release Resources 4
Result?
second_SRI
Continue
Result:= Network Signal Info:=

Aborted less preferred service
CAMEL
1
supported?
Send Routeing Info
No Yes
MSRN
received?
No CAMEL_MT_
See TS 23.078
GMSC_INIT
Wait_for_
Yes
Routeing_
Info
3
SCUDIF_Check_ Result=
Service_Compatibility MSRN
Yes
No
Result=
See TS 23.172 3
Aborted
Yes
No
Yes
Result =
Leg1_only?
Result:=
Aborted
Result :=
Leg1_only
2 5
Figure 37c: Procedure Obtain_Routeing_Address (sheet 3)
3GPP
Release 14 113 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in a GMSC
SCUDIF_Check_
See TS 23.172
Service_Compatibility
CCBS_MT_
GMSC_Check_ See TS 23.093
CCBS_
Indicators
Store Forwarding
Interrogation
Required
indicator
No
MSRN contains
a Routeing number?
Yes
MNP_MT_GMSC_ Routeing
See TS 23.066 Check_MNP_ address:=
Indicators MSRN
Result=
Fail?
Yes
No
Routeing Destination
address:= address:=
MSRN VMSC address
Result:=
Result:= Result:=
Routeing
Fail Pass
number
Figure 37d: Procedure Obtain_Routeing_Address (sheet 4)
3GPP
Release 14 114 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in a GMSC
Result=
Fail
No
Yes
Result
CAMEL_FTN
GSM_FTN
CAMEL_
MT_GMSC_ See TS 23.078
Notify_CF
Fail
Result
Continue
Reconnect
SCUDIF_Check_ Reconnect := Result:=

See TS 23.172
Service_Compatibility True Fail
2 1
Figure 37e: Procedure Obtain_Routeing_Address (sheet 5)
3GPP
Release 14 115 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in a GMSC
2
BOR:=OR
Activate_
CF_Process
Result?
Fail Release
Pass
CCBS_MT_
Release GMSC_Remove_ See TS 23.093
Indicators_
Store_FWT
Route_Permitted
Result:= (OR,FTN, See TS 23.079
Aborted Reference
Address)
False
Route
permitted
True CAMEL phase 2

or higher
supported?
No Yes
CAMEL_MT_ CAMEL_MT_
See TS 23.078 See TS 23.078
GMSC_DISC3 GMSC_DISC4
To process CF
MT_CF_MSC cancelled
Routeing Routeing
address:= address:=
FTN Reference
address
Destination Destination
address:= address:=
FTN Reference
address
OR:=True OR:=False
Result:= Result:=
Forward Pass
Figure 37f: Procedure Obtain_Routeing_Address (sheet 6)
3GPP
Release 14 116 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Send_ACM_If_Required SACMIR1(1)

Address Complete Message are to the originating exchange
to the preceding exchange if
one is required for this call
True
ACM
sent
False
True Network
connect
sent
False
Call Address
Progress Complete
ACM sent:=
True
Figure 38: Procedure Send_ACM_If_Required
3GPP
Release 14 117 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Send_Answer_If_Required SANMIR1(1)

Answer Message are to the originating exchange
True
Answer
sent
False
True Network
connect
sent
False
Call
Answer
Progress
Answer sent:=
True
Figure 39: Procedure Send_Answer_If_Required
3GPP
Release 14 118 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Send_Network_Connect_If_Required SNCONIR1(1)

Procedure to send a Signals to the left
Connect Message are to the originating exchange
True Network
connect
sent
False
True
Answer
sent
False
ACM
sent
True
False
Call
Answer Connect
Progress
Answer sent:= Connect sent:=

True True
Figure 40: Procedure Send_Network_Connect_If_Required
3GPP
Release 14 119 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_COLP_Forwarding_Interaction_MSC COINT_M1(1)

Procedure in the GMSC or VMSC
to handle the interaction between
COLP and Call Forwarding
Signals to/from the right Initiate

are to/from the process handling
COLP_MAF039 of COLP
Wait_For_
COLP_Info
From originating exchange continue

Release call
or destination exchange
handling
Figure 41: Procedure Handle_COLP_Forwarding_Interaction_MSC
3GPP
Release 14 120 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Activate_CF_Process ACFP1(1)

to initiate the process which are to/from the originating exchange;
handles call forwarding signals to/from the right
are to/from the process MT_CF_MSC
Perform call
forwarding
(BOR, FTN)
Wait_For_
CF_Response
Perform call
Perform call forwarding Int_Release_
Release From gsmSSF
forwarding ack negative Call
response
CF
cancelled
CF
cancelled

Fail Pass Fail Release
Figure 42: Procedure Activate_CF_Process
3GPP
Release 14 121 3GPP TS 23.018 V14.0.0 (2017-03)
Process MT_CF_MSC MTCFMSC1(6)

Process in the MSC Signals to/from the left
to handle call forwarding are to/from the parent process;
Idle
Perform call
forwarding
CAMEL_CF_
See TS 23.078
MSC_INIT
Result =
Yes Leg1_only?
4
No
No
Result=
Pass?
Leg1_status
:= Set-up Yes
CAMEL_CF_
See TS 23.078
CAMEL_MT_CF Dialled_Services
_LEG1_MSC See TS 23.078
(Leg1_status)
Fail
Result?
Idle Leg1_only Abort
Pass
Perform call No
CAMEL_ Result=
4 forwarding See TS 23.078 OCH_MSC1 Fail?
ack(FTN)
Yes
No
Wait_For_ Result=
Idle
IAM Reconnect?
Yes
Initial CF Perform Call

1 2 Forwarding
Address cancelled
negative
response
MOBILE_NUMBER_ CAMEL phase 2

See TS 23.066 PORTABILITY_ or higher
IN_OQoD supported?
Initial
Address
No Yes
CAMEL_Store_ CAMEL_OCH_ CAMEL_OCH_

See TS 23.078 Destination_ See TS 23.078 See TS 23.078
MSC_DISC3 MSC_DISC4
Address
(BOR, True)
Wait_For_
Idle Idle
ACM
Figure 43a: Process MT_CF_MSC (sheet 1)
3GPP
Release 14 122 3GPP TS 23.018 V14.0.0 (2017-03)

to handle call forwarding Wait_For_ are to/from the parent process;
ACM signals to/from the right
Address
Connect
Complete
CAMEL_
See TS 23.078
Start_TNRy
UUS_MSC_ UUS_MSC_
See TS 23.087 See TS 23.087
Clear_UUS Clear_UUS
CAMEL_CF_
See TS 23.078
MSC_ALERTING
Answer Else
Result?
Pass
Address Address
Complete Complete
Wait_For_
Answer
Answer
CAMEL_
See TS 23.078
Stop_TNRy
CAMEL_CF_ CAMEL_CF_
See TS 23.078 See TS 23.078
MSC_ANSWER MSC_ANSWER
Else Else
Result? Result?
Pass Pass
UUS_MSC_ Reconnect Release

See TS 23.087 Result?
Clear_UUS
Fail
Answer 2 Release Connect
A Idle A
Figure 43b: Process MT_CF_MSC (sheet 2)
3GPP
Release 14 123 3GPP TS 23.018 V14.0.0 (2017-03)

to handle call forwarding are to/from the parent process;
Wait_For_ACM, are to/from the destination exchange
Wait_For_Answer unless marked otherwise
Int_O_
Release
CAMEL phase 2 CAMEL phase 2

or higher or higher
No Yes No Yes
Yes
Release cause=
No

See TS 23.078
No
Result=
Reconnect?
Yes
CAMEL_
See TS 23.078 Release
Stop_TNRy
Release
call
resources
Idle
Figure 43c: Process MT_CF_MSC (sheet 3)
3GPP
Release 14 124 3GPP TS 23.018 V14.0.0 (2017-03)

to handle call forwarding Wait_For _ are to/from the parent process;
Answer signals to/from the right
TNRy
Internal
expired
3 Release
CAMEL_OCH_
See TS 23.078 2
MSC2
Release Reconnect
Result?
Fail
CAMEL_CF_
Release See TS 23.078 Dialled_
Services
Abort Pass
Result?
Fail
Release
CAMEL_
call See TS 23.078 1
OCH_MSC1
resources
Yes
Result=
Idle
Reconnect?
No
Perform Call
Forwarding 2
negative
response
Idle
Figure 43d: Process MT_CF_MSC (sheet 4)
3GPP
Release 14 125 3GPP TS 23.018 V14.0.0 (2017-03)

to handle call forwarding Wait_For_ are to/from the parent process;
Clear signals to/from the right
Int_O_
Release
See TS 23.078 See TS 23.078 Release
MSC_DISC1 MSC_DISC2
Result= Result=
Yes Yes
CAMEL CAMEL
Handling? Handling?
No No
Yes
Result=
Reconnect?
No
Release
call
resources
Idle
* *
- -
Figure 43e: Process MT_CF_MSC (sheet 5)
3GPP
Release 14 126 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC
to handle call forwarding
No
CAMEL phase 4 or later
Yes
CAMEL_MT_
See TS 23.078
CF_LEG2_MSC
Leg1_status Wait_For_
:= Active Clear
CAMEL_MT_
See TS 23.078 CF_LEG1_MSC
(Leg1_status)
Idle
Figure 43f: Process MT_CF_MSC (sheet 6)
3GPP
Release 14 127 3GPP TS 23.018 V14.0.0 (2017-03)
Macrodefinition CUG_Support_Check_GMSC CUG_SC1(1)

Macro to check support of CUG in GMSC,
if needed, and check if call can continue.
No Yes
CUG info
present?
GMSC
supports CUG?
Yes
No
Yes Outgoing
Access
present?
No
Pass Fail
Figure 43bis: Macro CUG_Support_Check_GMSC
7.2.2 Functional requirements of HLR
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
3GPP
Release 14 128 3GPP TS 23.018 V14.0.0 (2017-03)
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
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
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?".
3GPP
Release 14 129 3GPP TS 23.018 V14.0.0 (2017-03)
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 sub-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.
3GPP
Release 14 130 3GPP TS 23.018 V14.0.0 (2017-03)
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?".
3GPP
Release 14 131 3GPP TS 23.018 V14.0.0 (2017-03)
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.

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].
Process SRI_HLR SRI_HLR1(7)

Process in the HLR to handle Signals to/from the left
a request for routeing information are to/from the GMSC
or the gsmSCF;
are to/from the VLR
Idle
Send
Routeing
Info
Check_
Parameters
Result=
Pass?
No
Yes
Subscription_
Check_HLR
SCUDIF_Subscription
See TS 23.172
_Check_HLR
7
Result=
Fail?
Yes
No
See TS 23.079 OR_HLR_CF 6
Yes
Result=
Fail?
No
Yes
Result=
Forward?
No
CAMEL_
See TS 23.078
HLR_INIT
Yes
Result=
Fail?
No
3 1 2 1
Figure 44a: Process SRI_HLR (sheet 1)
3GPP
Release 14 132 3GPP TS 23.018 V14.0.0 (2017-03)

a request for routeing information 3 are to/from the GMSC
or the gsmSCF;
are to/from the VLR
First_
Forwarding_HLR
Yes
Result=Fail?
No HLR support
Domain Selection?
Result=Forward?
No Yes
HLR support No
Domain Selection?
2 Yes
Yes No
Domain_Selection Domain_Selection
_HLR _HLR
IMS CS
Result=
CS or IMS?
Result=
CS or IMS
IMS
CAMEL_ CS
12 See TS 23.078
CSI_Check_HLR
12
SCUDIF_CAMEL_
See TS 23.172
CSI_Check_HLR CAMEL_
See TS 23.078 CSI_Check_
HLR
Yes Result=
CSI
active?
No SCUDIF_CAMEL_
See TS 23.172 CSI_Check_
gsmSCF Initiated HLR
Call? No
4
Yes
Yes Result=
Suppress CCBS
Handling? CSI
Yes active?
No
No
CCBS_Handling_
See TS 23.093
HLR
4
Yes
Result =
Forward
No
No
Result =
OK
1
Yes
5 1 2
Figure 44b: Process SRI_HLR (sheet 2)
3GPP
Release 14 133 3GPP TS 23.018 V14.0.0 (2017-03)

a request for routeing information are to/from the GMSC
or the gsmSCF;
are to/from the VLR
5
OR_HLR_
See TS 23.079
Interrogate_VLR
Yes
Result=
Fail?
No
Result=
1
Forward?
Yes
No
SCUDIF_Set_
Correct_PLMN_BC
Result
Set_PLMN_BC
SRI_Ack Continue
Yes
PLMN BC=
4
NULL?
No
Set
PLMN BC
parameter
No
Alerting
Pattern
required?
Yes
Set
Alerting
Pattern
CLI_HLR_
See TS 23.081
Set_CLI
Figure 44c: Process SRI_HLR (sheet 3)
3GPP
Release 14 134 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the HLR to handle
a request for routeing information
Pre-paging
supported
in HLR?
Yes No
No
Pre-paging
supported
in GMSC?
Yes
Set Pre-paging
supported
Provide
Roaming
Number
Wait_For_
MSRN
Figure 44d: Process SRI_HLR (sheet 4)
3GPP
Release 14 135 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the HLR to handle Wait_For_ Signals to/from the left
a request for routeing information MSRN are to/from the GMSC
or the gsmSCF;
are to/from the VLR
Provide Provide
Roaming Roaming
Number ack Number negative
response
PRN_Error_
Routeing HLR
address:=
MSRN
MT Roaming Retry
Yes
supported and
received Update
Location Request ? Set Error=Absent Subscriber
with reason "mtRoamingRetry"
No
SCUDIF_Check_ in the SRI response
Second_Service_ See TS 23.172
after_PRN
Result= Send Routeing
Fail? Info Negative Rsp
2 Yes
No
1 Idle
Forward_
CUG_Check
Result=
Call
Result= allowed? No
Continue?
No 11
Yes
Yes
7
9 12
Set Routeing
4 10 see TS 23.292
address
Send
Routeing
Info ack
Idle
Figure 44e: Process SRI_HLR (sheet 5)
3GPP
Release 14 136 3GPP TS 23.018 V14.0.0 (2017-03)

11
Yes
Forwarding
1
enquiry?
No
CAMEL_
CSI_Check_ See TS 23.078
HLR
SCUDIF_CAMEL_
See TS 23.172
CSI_Check_HLR
No
Result=
CSI
active?
Yes
Called party SS Set negative

interaction response:
violation CUG reject
SCUDIF_Check_
before_negative_
response
Result?
Pass fail Second_Interrogation
6 7
Send Send
Routeing Routeing
Info ack Info negative
response
Idle Idle
Figure 44f: Process SRI_HLR (sheet 6)
3GPP
Release 14 137 3GPP TS 23.018 V14.0.0 (2017-03)

Routeing
address:=
FTN
SCUDIF_Set_Second_
Service_when_ See TS 23.172
Forwarded
Result=
Continue?
No
Yes
10
Yes
Forwarding
enquiry?
No
CAMEL_T_
See TS 23.078 CSI_CHECK_
HLR
CAMEL_O_
HLR
CAMEL_D_
HLR
SCUDIF_Check_
when_Forwarded
Result=
Continue?
No
Yes
Send
Routeing 7
Info ack
Idle
Figure 44g: Process SRI_HLR (sheet 7)
3GPP
Release 14 138 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Check_Parameters Chk_Par1(1)

Procedure to check
the parameters of a
received message
No
All required
parameters present?
Yes
No Set negative
All parameter values
acceptable? response:
Data missing
Yes
Set negative
response:
Unexpected
data value
Result:= Result:=
Pass Fail
Figure 45: Procedure Check_Parameters
3GPP
Release 14 139 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Subscription_Check_HLR SC_HLR1(1)

Procedure in the HLR
to make subscription
checks for a mobile-
terminated call
MS No
known?
Yes
Set negative
response:
Unknown
subscriber
Number Yes
changed?
No
Set negative
Derive requested response:
See TS 29.007
basic service Number
changed
Requested
No
service
provisioned?
Yes
gsmSCF Initiated No
Call? Set negative Bearer service
response: or
Yes service not Teleservice
provisioned
Yes Suppress
ICB?
No
Check_IC_
Barring
Result=
Yes
Call
barred?
No
Set negative
response:
Call barred
gsmSCF Initiated No
Call?
Yes
Yes Suppress
CUG?
No
IC_CUG_
Check
Result=
No
Call
allowed?
Yes
Set negative
response:
CUG reject
Result:= Result:=
Pass Fail
Figure 46: Procedure Subscription_Check_HLR
3GPP
Release 14 140 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure First_Forwarding_HLR FF_HLR1(1)

to handle call forwarding
before interrogation of the VLR
Handle_CFU
Yes
Result=
Fail?
No Set negative
response:
Forwarding
Yes violation
Result=
Forward?
No
No
MS not
reachable?
Yes
Handle_CFNRc
Yes
Result=
Fail?
No Set negative
response:
Forwarding
violation
No
Result=
Forward?
Yes Set negative
response:
Absent
subscriber

Forward Continue Forward Fail
Figure 47: Procedure First_Forwarding_HLR
3GPP
Release 14 141 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure PRN_Error_HLR PRN_E_H1(1)

to handle a negative response
for a roaming number request
CCBS_Report_
See TS 23.093
PRN_Failure
Negative Yes
response=OR
not allowed??
No Set negative
response:
OR not
allowed
Negative Yes
response=Facility
not supported?
No
Yes Negative Set negative

response=Absent response:
subscriber? Facility not
No supported
Negative No
response=No
roaming
number? Yes
Set negative
Handle_CFNRc Handle_CFNRc response:
System
failure
Fail Forward Forward Fail

Result? Result?
Not reachable Not reachable

Set negative Super_Charged_ Set negative
response: SRI_Error_ response:
Forwarding HLR Forwarding
violation violation
Yes
Result=
Purged?
No
Set negative Set negative
response: response:
Absent System
subscriber failure

Fail Forward Fail
Figure 48: Procedure PRN_Error_HLR
3GPP
Release 14 142 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Forward_CUG_Check FWD_CUG1(1)

Procedure to carry out
CUG authorisation check
for a forwarded call
No CUG provisioned for

forwarding subscriber against
requested basic service
Yes
CUG info provided in Yes

routeing information
request
No
Perform
Forwarding CUG As defined in TS 23.085
authorisation
CUG Pass
authorisation
result
Fail

Call allowed Call barred Call allowed
Update CUG
As defined in TS 23.085
info
Figure 49: Procedure Forward _CUG_Check
Figure 50: Void
3GPP
Release 14 143 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Check_IC_Barring CIB1(2)

and ODB categories
Yes
Operator determined
BAIC imposed?
No
Yes
Operator determined
BIC-Roam imposed?
No
No MS registered
in HPLMN
country?
Yes
Yes Operator determined

BIC-RoamHZ
imposed?
No
No MS registered
in HPLMN
zone?
Yes
Result:=
Call barred
(ODB)
Figure 51a: Procedure Check_IC_Barring (sheet 1)
3GPP
Release 14 144 3GPP TS 23.018 V14.0.0 (2017-03)
p r o c e d u r e C h e c k _ I C _ B a r r in g C IB 2 (2 )
1
P r o c e d u r e to c h e c k c a ll
r e q u e s t a g a in s t S S b a r r i n g
a n d O D B c a te g o rie s
I n i ti a t e
h a n d lin g T o p ro c e s s M A F 0 2 2
o f B A IC
W a it _ F o r _
B A IC _
R esp onse
C o n t in u e
c a ll F ro m p ro c e s s M A F 0 2 2
h a n d lin g
Yes
C a ll
b a rre d ?
No
I n i ti a t e
h a n d lin g T o p ro c e s s M A F 0 2 3
o f B IC -R o a m
W a it _ F o r _
B IC - R o a m _
R esp onse
C o n t in u e
h a n d lin g
Yes
C a ll
b a rre d ?
No
R e s u l t: = I n i ti a t e
C a ll b a r re d h a n d lin g T o p ro c e s s M A F 0 2 4
(S S b a rrin g ) of AC R
W a it _ F o r _
ACR_
R esp onse
C o n t in u e
h a n d lin g
Yes
C a ll
b a rre d ?
No
R e s u l t: = R e s u lt :=
C a ll b a r re d C a ll a llo w e d
(A C R )
Figure 51b: Procedure Check_IC_Barring (sheet 2)
3GPP
Release 14 145 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure IC_CUG_Check IC_CUG1(1)

Procedure to carry out Signals to/from the right
CUG authorisation check are to/from the process
for an incoming (MT) call CUG_MAF015
HLR
supports CUG?
Yes
No
No
SRI
incoming
contains CUG
call
info?
Yes
Yes
Outgoing
Access
present?
W ait_For_
No CUG_Response
reject response complete call

call to call (conditional
(cause) request CUG info)
Result:=
Result:= Result:=
Call barred
Call allowed Call allowed
(cause)
Figure 52: Procedure IC_CUG_Check
3GPP
Release 14 146 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_CFU H_CFU1(1)

to handle Call Forwarding
Unconditional

MAF007
CAMEL_CHECK
See TS 23.078
_SII2_CDTI
No
Result =
Pass?
Yes
initiate
handling
of CFU
Wait_For_
CFU_Result
continue
call
handling
Yes
Error?
No
Normal Yes
call?
No

Fail Forward Continue
Figure 53: Procedure Handle_CFU
3GPP
Release 14 147 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_CFNRc H_CFNRc1(1)

or VLR to handle Call
Forwarding on Mobile
Subscriber Not Reachable

MAF010
CAMEL_CHECK
See TS 23.078
_SII2_CDTI
No
Result =
Pass?
Yes
initiate
handling
of CFNRc
Wait_For_
CFNRc_Result
continue
call
handling
Yes
Error?
No
Yes
Mobile subscriber
not reachable?
No

Fail Forward Not reachable
Figure 54: Procedure Handle_CFNRc
3GPP
Release 14 148 3GPP TS 23.018 V14.0.0 (2017-03)
process Domain_Selection_HLR 1(1)

procedure in the HLR to
determine how to route the session
Domain_Selection refer to TS 23.221
Session to be
routed to IMS?
no
yes
Result:=
to CS
Result:=
to IMS
Figure 54A: Process Domain_Selection_HLR
7.2.3.1 Process PRN_VLR

Sheet 1: the procedure Check_Parameters is specified in subclause 7.2.2.2.
Sheet 1: the test "Pre-paging allowed" takes the "yes" exit if:
- the information element "Pre-paging supported" was present in the Provide Roaming Number message; or
- as an operator option, the paging procedure can be completed before the minimum timer value for the Provide
Roaming Number operation timer in the HLR has elapsed.
Sheet 1: the procedure Check_Reason_In_Serving_Network_Entity is specific to Super-Charger; it is specified in

3GPP TS 23.116 [24]. If the VLR does not support Super-Charger, processing continues from the "No" exit of the test
"Result=Purged?".
3GPP
Release 14 149 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 1: Pre-paging is not applicable if the Provide Roaming Number request includes the MTRF Indicator.
Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CAMEL_SET_SOA is specific to CAMEL; it is specified in
3GPP TS 23.078 [12].
Sheet 2, sheet 3, sheet 6, sheet 7: the task "Store alerting pattern (if received)" is executed only if the VLR supports the
feature Network Indication of Alerting.
Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CLI_PRN_VLR is specific to Enhanced CLI Handling. It is specified in
3GPP TS 23.081 [14].
Sheet 2, sheet 3, sheet 6, sheet 7: the procedure CCBS_Handle_PRN is specific to CCBS; it is specified in
3GPP TS 23.093 [23].
Sheet 2, sheet 4: A VLR not supporting the flag "Subscriber data dormant" shall behave as if this flag is set to false.
Sheet 2: As an implementation option, the VLR may skip the "Authorize_MTRF_VLR" procedure (i.e. assume the
result of that procedure takes the "Pass" exit) and allocates an MSRN before the completion of the MAP Update
Location procedure with the HLR.
Sheet 3, sheet 4: the number of unused authentication sets which triggers the VLR to request further authentication sets
from the HLR is an operator option.
Sheet 3, sheet 4: the process Fetch_Authentication_Sets_VLR is specified in subclause 7.1.2.11.
Sheet 4: the procedure Search_For_MS_VLR is specified in subclause 7.3.2.3.
Sheet 4: the test "Paging via SGSN possible" takes the "yes" exit if:
- the Gs interface is implemented; and
- there is an association established for the MS between the MSC/VLR and the SGSN.
Sheet 4: "Location cancelled" cause is set when VMSC receives Cancel Location while paging.
Sheet 6: "Location cancelled with new VLR address" cause is set when VMSC receives Cancel Location with MTRF
Supported And Authorized while paging and new MSC/VLR numbers have been received either in the Cancel Location
or the Send Identification message.
Sheet 7, sheet 8: the state variables PAR pending, PAR successful and Fatal PAR error are global data, accessible to the
matching instance of the process ICH_VLR, which is linked by the MSRN.
Sheet 8: this process communicates with the matching instance of the process ICH_VLR, which is linked by the MSRN.
Sheet 8: the test " Fatal PAR error?" takes the "Yes" exit if:
- the MS failed authentication; or
- the MS failed IMEI checking; or
- the HLR returned an "Unknown subscriber" error;
during the handling of the Process Access Request.
7.2.3.2 Process Restore_Subscriber_Data_VLR
7.2.3.3 Process PSI_VLR

Sheet 1: the procedure Check_Parameters is specified in subclause 7.2.2.2. If the HLR requests none of location
information subscriber state, MS classmark and IMEI, the VLR treats this as a missing parameter.
Sheet 2: the test "Active retrieval required" takes the "Yes" exit if any one or more of current location, MS classmark or
IMEI is indicated in the Provide Subscriber Info request.
3GPP
Release 14 150 3GPP TS 23.018 V14.0.0 (2017-03)
7.2.3.4 Procedure Retrieve_Location_Info_VLR

The test "Retrieve location info from SGSN" takes the "Yes" exit if:
- there is an association established between the VLR and the SGSN.
The stored location information consists of:
- the service area ID (for UMTS) or cell ID (for GSM) or the tracking area ID and the E-UTRAN cell ID (for E-
UTRAN) of the cell in which the MS last established radio contact;
- the location number, geodetic information and geographical information derived from the service area ID or cell
ID if the VLR is capable of doing so (the mapping from service area ID or cell ID to location number is network-
specific and outside the scope of the UMTS and GSM standards);
- the age of the location information.
The output signal Send MS information towards the SGSN indicates that the required information is mobile location
information.
The received location information consists of:
- the service area ID (for UMTS) or cell ID(for GSM) received in the paging response message or in the Send MS
Information ack or the tracking area ID and the E-UTRAN cell ID (for E-UTRAN) received in the SGs service
request;
- the location number, geodetic information and geographical information derived from the service area ID or cell
ID if the VLR is capable of doing so (the mapping from cell ID to location number is network-specific and
outside the scope of the UMTS and GSM standards);
- the age of the location information.
The derivation of the location number, geodetic information and geographical information from the received service
area ID or cell ID is a VLR operator option (the mapping from service area ID or cell ID to location number is network-
specific and outside the scope of the UMTS and GSM standards).
7.2.3.5 Procedure Active_Info_Retrieval_VLR

- the VLR configuration requires paging via the SGSN during VLR restoration.
If the SGs interface is implemented and the conditions for paging over the SGs interface as specified in subclause
5.1.2.2 of 3GPP TS 29.118 [41] are fulfilled, the VLR shall send an SGs paging request to the MME. The VLR should
indicate the "SMS" service indicator in the SGs paging request if the LocationInformationEPS-Supported flag was
received in the Provide Subscriber Information request; otherwise the VLR should indicate the "CS" service indicator.
If the VLR indicates the "SMS" service indicator, the VLR should then send an SGs Release Request message to the
MME upon receipt of the SGs Service Request message (including the tracking area ID and E-UTRAN cell ID).
The VLR should return in the Provide Subscriber Information response the tracking area ID and E-UTRAN cell ID
received from the MME if the LocationInformationEPS-Supported flag was received in the Provide Subscriber
Information request and the UE uses the E-UTRAN radio access; otherwise the VLR should return the service area ID
(for UMTS) or cell ID (for GSM) received from UTRAN or GERAN.
NOTE: Using the "CS" service indicator leads the UE to fallback to GERAN or UTRAN radio access which can
affect on-going PS sessions of the user, e.g. suspend on-going PS sessions if the UE fallbacks to GERAN
radio access and Dual Transfer Mode is not supported, and which can cause extra Location Update
signalling in the network.
3GPP
Release 14 151 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 2: the output signal Page MS towards the SGSN includes or omits the Location area identity parameter depending
on the availability of this information. If it is omitted, the signal Page MS is sent to every SGSN to which the VLR is
connected.
The test "Report upon change of service area" takes the yes exit if the MSC has performed the Location Reporting
Control procedure with the Request Type IE set to "change of service area" [26].
If the test "Report upon change of service area" takes the no exit, then the MSC shall perform a Location Reporting
Control procedure with the Request Type IE set to "Direct".
3GPP
Release 14 152 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e s s P R N _ V L R P R N _ V L R 1 (8 )
P r o c e s s i n th e V L R t o h a n d l e
a r e q u e s t fo r a r o a m in g n u m b e r
I d le
S ig n a ls t o / f r o m t h e l e f t
a r e t o / f r o m th e H L R
o r th e o ld V L R ( M T R o a m in g F o r w a rd in g ) .
P ro v id e
R o a m in g
N um ber
C he ck_
1
P a ra m e te rs
No
R e s u lt =
P ass?
Yes
No OR
i n d ic a t o r
p re s e n t?
Yes
OR
s u p p o rte d ?
Yes No
C o n v e rt P L M N B C I f P L M N B C w a s S e t n e g a t iv e
t o b a s i c s e r v ic e i n c lu d e d in t h e re s p o n s e :
P r o v id e R o a m in g O R not
Num ber a ll o w e d
S e rv ic e No
s u p p o rte d
by VLR?
Yes
Yes IM S I P re -p a g in g S e t n e g a t iv e
know n s u p p o rte d re s p o n s e :
in V L R ? in V L R ? F a c il i ty
n o t s u p p o rte d
2 No
No Yes
M TRF P re -p a g in g
i n d ic a t o r No
a ll o w e d ?
Yes p re s e n t ?
Yes
S e t n e g a t iv e Yes IM S I P r o v i d e R o a m in g
re s p o n s e : No know n N um ber
A b s e n t S u b s c r ib e r in V L R ? n e g a t iv e
No re s p o n s e
C he ck_R eason_ C he ck_R eason_
I n _ S e r v in g _ 4 I n _ S e r v in g _ S e e T S 2 3 .1 1 6
1 N e t w o r k _ E n t it y N e t w o r k _ E n t it y
No No
R e s u lt = R e s u lt =
P u rg e d ? P u rg e d ?
Yes Yes
3 1 5 1 I d le
Figure 55a: Process PRN_VLR (sheet 1)
3GPP
Release 14 153 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e s s P R N _ V L R P R N _ V L R 2 (8 )
2
P r o c e s s i n th e V L R t o h a n d le
a r e q u e s t f o r a r o a m in g n u m b e r S i g n a ls t o th e l e f t
T ru e a r e t o th e H L R o r
S u b s c r ib e r d a ta th e o ld V L R ( M T R o a m in g
d o rm a n t Yes F o r w a r d in g ) .
A u th o riz e _ M T R F _ V L R
S e t n e g a t iv e F a ls e
re s p o n s e :
P u rg e d M S M T R F I n d ic a to r p r e s e n t ?
R e s u lt
1 No F a il
IM S I P ass
d e ta c h e d T ru e
9
F a ls e
Yes R o a m in g
in L A No
a ll o w e d ?
M T R o a m in g
9
R e tr y S u p p o r te d M SRN No
a v a i la b le ?
No
Yes Yes
D a ta M SC S e t n e g a t iv e S e t n e g a t iv e
c o n firm e d 9 re s p o n s e : re s p o n s e :
per VLR
by HLR? N o r o a m in g A bsent
F a ls e num ber s u b s c r ib e r
1 >1
T ru e No M o re Yes R e c e iv e d M S C
a u t h e n t ic a t i o n n u m b e r= S to re d 1
s e ts n e e d e d ? M S C n u m b e r?
Yes No
F e tc h _ F a ls e
C o n firm e d b y
A u t h e n t ic a ti o n _ r a d io c o n ta c t
S e ts_ V L R
T ru e
R e s to re _ U s e re c e iv e d U s e s to r e d
S u b s c r ib e r _ M S C num ber M S C num ber
D a ta _ V L R fo r M S R N fo r M S R N
9 A l lo c a t e
M SRN
C L I_ P R N _
S e e T S 2 3 .0 8 1
VLR
S e e T S 2 3 .0 7 8 CAM EL_
SET_SO A
C C B S _ H a n d le _
S e e T S 2 3 .0 9 3
P L M N B C , IS D N B C , S to r e PRN
IS D N L L C & I S D N H L C c o m p a t ib ili ty
( a s a v a il a b l e ) in f o
P ro v id e
R o a m in g
S to r e A le r ti n g
N um b er ack
P a t te r n
(if re c e iv e d )
M T R o a m in g
R e t r y S u p p o r te d o r
S to r e P g A
M T R F I n d ic a to r p r e s e n t Y e s
(if re c e iv e d
a n d s u p p o r te d ) No
6 Id le
3GPP
Release 14 154 3GPP TS 23.018 V14.0.0 (2017-03)
Figure 55b: Process PRN_VLR (sheet 2)
Process PRN_VLR PRN_VLR3(8)

3
Process in the VLR to handle
a request for a roaming number
No
MSRN
Signals to the left available
are to the HLR. Yes
Allocate Set negative

MSRN response:
No roaming
number
CAMEL_
See TS 23.078 1
SET_SOA
Create
IMSI
record
Location info Only if >1 MSC

confirmed per VLR
in HLR:=
False
Confirmed by radio contact:=False;
Data confirmed by HLR:=False;
IMSI detached:=False
If used
Allocate LMSI
by VLR
Store PLMN BC, ISDN BC,

compatibility ISDN LLC & ISDN HLC
info (as available)
Store Alerting Store PgA

Pattern (if received
(if received) and supported)
CLI_PRN_
6 See TS 23.081
VLR
Data False
CCBS_Handle_
confirmed See TS 23.093
PRN
by HLR?
True
More Yes Provide
authentication Roaming
sets needed? Number ack
No
Fetch_
Authentication_
Sets_VLR
Restore_
Subscriber_
Data_VLR
Idle
Figure 55c: Process PRN_VLR (sheet 3)
3GPP
Release 14 155 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the VLR to handle Signals to the right
a request for a roaming number 4 are to the MSC.
True
Subscriber data
dormant
False
Yes Set negative
IMSI
detached? response:
Purged MS
No
No Roaming
in LA 1
allowed?
Yes
No Yes
Location area
ID known?
True Data Paging

confirmed No
via SGSN
by HLR? possible?
False Yes
No More Set Paging
authentication via SGSN
sets needed? possible
Yes
Fetch_
Authentication_
Sets_VLR
Restore_
Subscriber_
Data_VLR
Search_For_ Page type=

Page MS circuit-switched
MS_VLR
call
Yes
Result=
Pass?
No
Yes
Absent
subscriber?
No
Set negative Yes
Location
response: cancelled?
Absent
subscriber Set negative
No response:
Purged MS
Wait_For_
1 7 1 Access_
Request
Figure 54d: Process PRN_VLR (sheet 4)
3GPP
Release 14 156 3GPP TS 23.018 V14.0.0 (2017-03)

a request for a roaming number 5
Create
IMSI
record
Location info
confirmed Only if >1 MSC
in HLR:= per VLR
False
Confirmed by radio contact:=False;

Data confirmed by HLR:=False;
IMSI detached:=False
If used
Allocate LMSI
by VLR

info (as available)
Fetch_
Authentication_
Sets_VLR
Restore_
Subscriber_
Data_VLR
Search_For_
MS_VLR
Yes
Result=
Pass?
No
Yes
Absent
subscriber?
Set negative No
response:
Absent
subscriber
Wait_For_
1 7 Access_
Request
Figure 54e: Process PRN_VLR (sheet 5)
3GPP
Release 14 157 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the VLR to handle Wait_For_ Signals to the left
a request for a roaming number Access_ are to the HLR;
Request signals to/from the right
are to/from the MSC or
to/from the new VLR
unless shown otherwise.
Page MS Process Page MS
via SGSN Access negative
Request response
No
MSRN
Page MS To SGSN
available?
MT Roaming Forwarding
supported?
Yes
Wait_For_ Yes
Access_ No
Request MSC location cancelled
per VLR with new VLR address?
No
Yes
1 >1
Yes Received MSC Provide
number= Stored to New VLR Roaming
MSC number? Number
No (MTRF Indicator)
False
Confirmed by Wait_For_
radio contact MSRN
True
Use received Use stored
MSC number MSC number
Provide Roaming Provide Roaming
for MSRN for MSRN
Number Negative Number Ack
Response
Allocate
MSRN
Provide Provide
Roaming Roaming
CAMEL_ Number Negative Number ack
See TS 23.078
SET_SOA Response

compatibility ISDN LLC & ISDN HLC Idle
info (as available)
Set negative Busy
response: subscriber?
Store Alerting
System Yes include MSRN
Pattern
failure
(if received) No 7
Process Access
Request Yes
CLI_PRN_ negative Absent
See TS 23.081
VLR response Subscriber?
No
CCBS_Handle_ Set negative Set negative
See TS 23.093 response: response:
PRN
No roaming Absent
number subscriber
Provide
Roaming
Number ack 1
Figure 54f: Process PRN_VLR (sheet 6)
3GPP
Release 14 158 3GPP TS 23.018 V14.0.0 (2017-03)

Signals to the left No

are to the HLR. MSRN
available?
Yes
Set negative
MSC response:
per VLR No roaming
number
1 >1
Yes
Received MSC
number= Stored 1
MSC number?
No
False
Confirmed by
radio contact
True
Use received Use stored
MSC number MSC number
for MSRN for MSRN
Allocate
MSRN
CAMEL_
See TS 23.078
SET_SOA

info (as available)
Store Alerting
Pattern
(if received)
CLI_PRN_
See TS 23.081
VLR
CCBS_Handle_
See TS 23.093
PRN
Provide
Roaming
Number ack
PAR pending:=False;
PAR successful:=False;
Fatal PAR error:=False
Idle
Figure 54g: Process PRN_VLR (sheet 7)
3GPP
Release 14 159 3GPP TS 23.018 V14.0.0 (2017-03)

Signals to/from the left PAR pending:=

are to/from the process ICH_VLR; True
are to/from the MSC
Process_
Access_
Request_VLR
No
Result=
Pass?
Yes
PAR successful:= PAR successful:=

True False
PAR pending:= PAR pending:=

False False
No
PAR Fatal PAR
Completed error?
Yes
Wait_For_ Fatal PAR Fatal PAR

Call_Arrival error:= True error:= False
Call Radio
arrived connection
released
Call PAR successful:= PAR

arrived False Completed
Fatal PAR
error:= False
Idle Idle
Figure 54h: Process PRN_VLR (sheet 8)
3GPP
Release 14 160 3GPP TS 23.018 V14.0.0 (2017-03)
Process Restore_Subscriber_Data_VLR RSD_VLR1(1)

Process in the VLR
to restore subscriber data

are to/from the HLR
Restore
Data
Wait_For_
Data
Restore Restore
Data ack Data negative
response
Update
Subscriber
Data
Update
HLR
number
Update MS If received
Not Reachable from HLR
indicator
Data
confirmed by
HLR:=True
Figure 56: Process Restore_Subscriber_Data_VLR
3GPP
Release 14 161 3GPP TS 23.018 V14.0.0 (2017-03)
Process PSI_VLR PSI_VLR1(2)

Process in the VLR to handle Signals to/from the left
a request from the HLR for are to/from the HLR;
subscriber information signals to/from the right
are to/from the MSC
Idle
Provide
Subscriber
Info
Check_
Parameters
No
Result=
Pass?
Yes
No
IMSI
known
in VLR?
Yes
No No
Subscriber Subscriber
state state
requested? requested?
Yes Yes
Yes
IMSI
detached?
No
No
Roaming
in LA
allowed?
Yes
Set subscriber Subscriber state:=

Network Subscriber state:=
state
determined Assumed idle
requested
not reachable
No
Location
info
requested?
Yes
Location info:=
Stored
location info
Obtain Provide Provide

Subscriber Subscriber Subscriber
Info Info ack Info negative
response
Wait_For_
Idle Idle
MSC_Response
Figure 57a: Process PSI_VLR (sheet 1)
3GPP
Release 14 162 3GPP TS 23.018 V14.0.0 (2017-03)
Process PSI_VLR PSI_VLR2(2)

Process in the VLR to handle Signals to/from the left
a request from the HLR for Wait_For_ are to/from the HLR;
subscriber information MSC_Response signals to/from the right
are to/from the MSC
Obtain
Subscriber
Info ack
No
Subscriber
state
received?
Yes
Set
subscriber
state
No
Active
retrieval
required?
Yes
No
Location
info
requested?
Yes
Active_Info_ Retrive_
Retrieval_ Location_
VLR Info_VLR
Provide
Subscriber
Info ack
Idle
Figure 57b: Process PSI_VLR (sheet 2)
3GPP
Release 14 163 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Retrieve_Location_Info_VLR RLI_VLR1(1)

Procedure in the VLR Signals to/from the right
to retrieve location information are to/from the SGSN
for a subscriber
Yes
Retrieve location
info from SGSN?
No
Location info:=
Send MS
Stored
information
location info
Wait_For_
SGSN_Response
Send MS Send MS
Information Information
negative ack
response
Location info:= Location info:=

Stored Received
location info location info
Derive location number,

geodetic information and
geographical information
Figure 58: Procedure Retrieve_Location_Info_VLR
3GPP
Release 14 164 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Active_Info_Retrieval_VLR AIR_VLR1(2)

Procedure in the VLR Signals to/from the right
to retrieve the current are to/from the MSC
location information for a subscriber
Set information
required
No
Paging
via SGSN
possible?
Yes
Set paging
via SGSN
possible
No Yes
Location
area ID
known?
Page type= Page type=

Search
Active information Active information Page MS
for MS
retrieval retrieval
Wait_For_ Wait_For_
Search_ Page_
Result Result
Figure 59a: Procedure Active_Info_Retrieval_VLR
3GPP
Release 14 165 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Active_Info_Retrieval_VLR AIR_VLR2(2)

Procedure in the VLR Wait_For_
to retrieve the current Search_
location information for a subscriber Result
Search Search
Search for for MS for MS
MS ack negative via SGSN
response
No
Roaming
in LA Page MS
allowed?
Yes
Subscriber
state:=Not
reachable Wait_For_
Search_
Result
Yes No Yes No
Location Location
info info
received? received?
Location info:= Location info:= Location info:= Location info:=

Received Stored Received Stored
location info location info location info location info
Wait_For_
Page_
Result
Page MS
Page MS Page MS
negative
ack via SGSN
response
Yes No
Location
info Page MS
received?
Location info:= Location info:= Wait_For_

Received Stored Page_
location info location info Result
Figure 59b: Procedure Active_Info_Retrieval_VLR (sheet 2)
3GPP
Release 14 166 3GPP TS 23.018 V14.0.0 (2017-03)
P r o c e d u re A u th o riz e _ M T R F _ V L R A M T _ V L R 1 (1 )
P r o c e d u r e i n th e V L R
t o a u th o r i z e a n M T R o a m in g
F o r w a r d in g r e q u e s t r e c e i v e d
i n P r o v i d e R o a m in g N u m b e r
f r o m o ld V L R
O n - g o in g M A P U p d a t e L o c a t i o n
p ro c e d u re
Yes
w a i t f o r M A P U p d a t e L o c a t io n r e s p o n s e
a n d c o m p le ti o n o f L o c a t i o n _ U p d a t e _ C o m p l e t i o n _ V L R p r o c e d u r e
No
" L A A llo w e d " f la g A N D

C o n fi r m e d b y R a d io C o n ta c t A N D
F a ls e D a t a C o n f ir m e d b y H L R A N D
M M L A I v a lid
T ru e
R e s u lt : = R e s u lt : =
F a il P ass
Figure 59b: Procedure Authorize_MTRF_VLR
3GPP
Release 14 167 3GPP TS 23.018 V14.0.0 (2017-03)
7.2.4 Functional requirements of MSC
7.2.4.1 Process Prepage_MSC
7.2.4.2 Procedure Prepaging_Page_MS_MSC

The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the
network.
The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.
The signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service
request for anything other than a circuit-switched call, or completed the location registration procedure.
7.2.4.3 Prepaging_Search_For_MS_MSC
network.
The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.
The signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service
request for anything other than a circuit-switched call, or completed the location registration procedure.
7.2.4.4 Process OSI_MSC

If the MS is engaged on a circuit-switched call, the state is busy, otherwise assumed idle.
7.2.4.5 Process RCL_MSC

This process runs when the MSC receives a Page MS message or a Search for MS message with a Page type indicating
Active Info Retrieval.
7.2.4.6 Procedure Active_Info_Retrieval_Page_MSC

network.
The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network.
The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting
Control procedure (see 3GPP TS 25.413 [27]) with the Request Type IE set to "Change of service area".
If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control
procedure with the Request Type IE set to "Direct".
7.2.4.7 Procedure Active_Info_Retrieval_Search_MSC

network.
The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network.
The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting
Control procedure (see 3GPP TS 25.413 [26]) with the Request Type IE set to "Change of service area".
If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control
procedure with the Request Type IE set to "Direct".
3GPP
Release 14 168 3GPP TS 23.018 V14.0.0 (2017-03)
7.2.4.8 Procedure Retrieve_IMEI_If_Required

If the IMEI is retrieved using an existing connection between the MS and the network (as opposed to a connection
which has been set up for active information retrieval), the Release transaction signal is relayed to the MSC process
which is supervising the existing connection.
Process Prepage_MSC PP_MSC1(1)

to handle a pre-paging are to/from the VLR;
request signals to the right
are to the BSS
Idle
Search
Page MS
for MS
Prepaging_ Prepaging_
Page_MS_MSC Search_for_
MS_MSC
Yes Yes
Result= Result=
Pass? Pass?
No
No
Process_
Idle Acces_ Idle
Request_MSC
No
Result=
Pass?
Yes
Start radio
Idle
guard timer
Wait_For_
Call_Arrival
Call Radio guard Release BSS released

timer Internal
arrived transaction the radio resource
expired
Release
transaction
Stop radio Radio Radio

guard timer connection connection
released released
Idle
Figure 60: Process Prepage_MSC
3GPP
Release 14 169 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Prepaging_Page_MS_MSC PPPMS_M1(1)

to page an MS in a
specified location area
Signals to/from the left Location No

are to/from the BSS; area ID
signals to/from the right known?
are to/from the VLR Yes
unless marked otherwise MS Yes Set negative
connection response:
exists? Unknown LAI
No
No Yes
Paging via
MS busy?
SGSN possible?
Yes No
In specified Set negative

Page response:
location area
Busy Subscriber
Page MS Set access Page MS

via SGSN connection negative
status response
Start Page Result:= Result:=

response Pass Fail
timer
Wait_For_
Page_
Response
Cancel MS Page CM For circuit-

Location connection response Service switched call
established timer expired Request
CM To process
Service OCH_MSC
Request
Set negative Set access Set negative Set negative

response: connection response: response:
Location Cancelled status Absent Busy Subscriber
Subscriber (NDUB)
Page MS Page MS Page MS
negative negative negative
response response response

Fail Pass Fail Fail
Figure 61: Procedure Prepaging_Page_MS_MSC
3GPP
Release 14 170 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Prepaging_Search_For_MS_MSC PPSMS_M1(1)

to page an MS in
all location areas
Signals to/from the left MS Yes

are to/from the BSS; connection
signals to/from the right exists?
are to/from the VLR No
unless marked otherwise No Yes
Paging via
MS busy?
SGSN possible?
Yes No
Page MS Set negative

via SGSN response:
Busy Subscriber
In all location areas Set access Page MS

or in PgA if PgA received Page connection negative
and supported status response

response Pass Fail
timer
Wait_For_
Page_
Response
MS Page CM For circuit-

connection response Service switched call
CM To process
Service OCH_MSC
Request
Set access Set negative Set negative

connection response: response:
status Absent Busy Subscriber
Subscriber (NDUB)
Page MS Page MS
negative negative
response response

Pass Fail Fail
Figure 62: Procedure Prepaging_Search_For_MS_MSC
3GPP
Release 14 171 3GPP TS 23.018 V14.0.0 (2017-03)
Process OSI_MSC OSI_MSC1(1)

Process in the MSC to handle Signals to/from the left
a request from the VLR for are to/from the VLR
information on the subscriber's
location and state
Idle
Obtain
Subscriber
Info
Subscriber No
state
requested?
Yes
Set
subscriber
state
Obtain
Subscriber
Info ack
Idle
Figure 63: Process OSI_MSC
3GPP
Release 14 172 3GPP TS 23.018 V14.0.0 (2017-03)
Process AIR_MSC AIR_MSC1(1)

Process in the MSC to retrieve Signals to/from the left
any one or more of the current location, are to/from the VLR
MS classmark and IMEI of a subscriber
Idle
Search
Page MS
for MS
Active_Info_ Active_Info_
Retrieval_ Retrieval_
Search_MSC Page_MSC
Idle
Figure 64: Process AIR_MSC
3GPP
Release 14 173 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Active_Info_Retrieval_Page_MSC AIRP_MSC1(2)

to page an MS in a specified are to/from the BSS;
location area for Active signals to/from the right
Location Retrieval are to/from the VLR
No
Location
area ID
known?
Yes
Yes
MS
connection
exists?
No
No
Retrieve_
Paging via
IMEI_If_
SGSN possible?
Required
Yes
Yes
In specified Page MS GSM
Page
location area via SGSN Access?
No
No
Start Page Location
response info
timer requested?
Yes
Yes
Wait_For_ Report on
Page_ change of
Response service area?
No
Page response MS Location

CM Service For circuit-
timer connection Reporting
Request switched call
expired established Control
Wait_For_
CM Service To process
Location_
Request OCH_MSC
Report
Retrieve_ Retrieve_
Location
IMEI_If_ IMEI_If_
Report
Required Required
Location info:=
Release
Received
transaction
location info

response: response:
Absent Unknown LAI
subscriber
Page MS Page MS
Page MS Page MS Page MS
negative negative
ack ack ack
response response
Figure 65: Procedure Active_Info_Retrieval_Page_MSC
3GPP
Release 14 174 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Active_Info_Retrieval_Search_MSC AIRS_MSC1(1)

to page an MS in all are to/from the BSS;
location areas for Active signals to/from the right
Location Retrieval are to/from the VLR
Yes
MS
connection
exists?
No
No
Retrieve_
Paging via
IMEI_If_
SGSN possible?
Required
Yes
Yes
Search
In all GSM
Page for MS
location areas Access?
via SGSN
No
No
Start Page Location
response info
timer requested?
Yes
Yes
Wait_For_ Report on
Page_ change of
Response service area?
No
Page response MS Location

CM Service For circuit-
timer connection Reporting
Request switched call
expired established Control
Wait_For_
CM Service To process
Location_
Request OCH_MSC
Report
Retrieve_ Retrieve_
Location
IMEI_If_ IMEI_If_
Report
Required Required
Location info:=
Release
Received
transaction
location info
Set negative
response:
Absent
subscriber
Search Search Search Search

for MS for MS for MS for MS
negative ack ack ack
response
Figure 66: Procedure Active_Info_Retrieval_Search_MSC
3GPP
Release 14 175 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Retrive_IMEI_If_Required RIIR1(1)

to retrieve the IMEI of the MS are to/from the BSS
if requested by the VLR
No
IMEI
requested?
Yes
Send
IMEI
Wait_For_
IMEI
Release
IMEI
transaction
IMEI:= Release To supervising process,

Received IMEI transaction if required
Figure 66bis: Procedure Retrieve_IMEI_If_Required
3GPP
Release 14 176 3GPP TS 23.018 V14.0.0 (2017-03)
7.3 MT call
7.3.1.1 Process ICH_MSC

Sheet 1: the task "Release Resources" refers to any resources that may have been allocated for the call due to Pre-
Paging.
Sheet 1: the rules for converting the ISDN BC/LLC/HLC to a bearer service or teleservice are specified in
3GPP TS 29.007 [30].
Sheet 1: the task "Store UUS information (if received)" is executed only if the VMSC supports UUS.
Sheet 1: the variables TCH allocated, ACM sent, Answer sent and Network connect sent are global data, accessible to
the procedures Establish_Terminating_TCH_If_Required, Send_ACM_If_Required, Send_Answer_If_Required and
Send_Network_Connect_If_Required.
Sheet 1: the variables UUS result sent, UUS1 implicit active, UUS1 explicit active, UUS2 active, UUS3 active and
UUS CF interaction are specific to UUS. They are accessible to all UUS specific procedures.
Sheet 1: the handling starting with the input signal "Continue CAMEL handling" is specific to CAMEL phase 3 or later.
If the VMSC does not support CAMEL phase 3 or later, this signal will not be received from the VLR.
Sheet 1: the procedure CAMEL_ICH_MSC_INIT is specific to CAMEL phase 3 or later; it is specified in

3GPP TS 23.078 [12].
Sheet 1: The variable "On_Hold" is used only if the VMSC supports Call Hold.
Sheet 1, sheet 4, sheet 9: the process CAMEL_ICH_LEG1_MSC is specific to CAMEL phase 4 or later; it is specified
in 3GPP TS 23.078 [12].
Sheet 2: the procedure Process_Access_Request_MSC is specified in subclause 7.1.1.2.
Sheet 2: the signal input Complete Call will be received in the state Wait_For_Page_Request only if the MSC/VLR
supports pre-paging.
Sheet 2, sheet 3: the suggested mapping from values of the Send Info For Incoming Call negative response information
element to values of the ISUP release cause (see ITU-T Recommendation Q.850 [37]) is shown in table 2. The mapping
used is a matter for the network operator, depending on the telephony signalling system used.
Table 2: Suggested mapping of Send Info For Incoming Call (SIFIC)

negative responses to ISUP release causes
SIFIC negative response ISUP release cause number ISUP release cause name
Absent subscriber 20 Subscriber absent
Busy subscriber 17 User busy
CUG reject (Called party SS 21 Call rejected
interaction violation)
Forwarding violation 21 Call rejected
Impossible call completion 111 Protocol error, unspecified
No subscriber reply 19 No answer from user (user alerted)
System failure 111 Protocol error, unspecified
Unallocated roaming number 111 Protocol error, unspecified
Sheet 2, sheet 3, sheet 6, sheet 8, sheet 10, sheet 12: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC
supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL
phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?".
Sheet 2, sheet 5, sheet 8, sheet 10, sheet 11, sheet 12: the procedure CAMEL_MT_GMSC_DISC6 is called if the
VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12].
3GPP
Release 14 177 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 3: the procedure CAMEL_MT_GMSC_DISC5 is called if the VMSC supports CAMEL phase 3 or later; it is
specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from
the "No" exit of the test "Result=Reconnect?".
Sheet 3: the procedure CD_Reject is specific to Call Deflection; it is specified in 3GPP TS 23.072 [11].
Sheet 3: the procedure Process_Call_Waiting is specific to Call Waiting; it is specified in 3GPP TS 23.083 [16].
Sheet 3: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports
CAMEL phase 3 or later.
Sheet 3: if the VMSC does not support CAMEL phase 3 or later, the procedure Complete_Call_In_MSC and the
procedure Process_Call_Waiting will not return a "Reconnect" result.
Sheet 3: the processing in the branch starting with the input signal"Process Call Waiting" is specific to Call Wait. If the
VMSC does not support Call Waiting, this signal will not be received from the VLR.
Sheet 3, sheet 10: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 3, sheet 5, sheet 6, sheet 11, sheet 12, sheet 13: the procedure CCBS_Check_Last_Call is specific to CCBS; it is
Sheet 3: the procedure UUS_ICH_Check_Support is specific to UUS; it is specified in 3GPP TS 23.087 [20].
Sheet 4: the procedure CAMEL_ICH_LEG2_MSC isspecific to CAMEL phase 4 or later; it is specified in

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

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

3GPP TS 23.078 [12].
- If the VLR does not support CAMEL or no CAMEL information is available for the subscriber, then ORLCF
may take place ('ORLCF' result from CAMEL_Check_ORLCF_VMSC).
- If CAMEL information is available for the subscriber and the GMSC supports the required CAMEL phase, then
ORLCF may take place. The Resume Call Handling request shall include the relevant CAMEL information
('ORLCF' result from CAMEL_Check_ORLCF_VMSC).
- If CAMEL information is available for the subscriber but the GMSC does not support the required CAMEL
phase, then ORLCF shall not take place ('VMSCCF' result from CAMEL_Check_ORLCF_VMSC).
Sheet 5: the procedure Handle_ORLCF_VMSC is specific to Support of Optimal Routeing. It is specified in

3GPP TS 23.079 [13]. If the VMSC does not support Optimal Routeing, processing continues from the "Continue" exit
of the test "Result?".
Sheet 5, sheet 6, sheet 11: the procedures CD_Failure and CD_Success are specific to Call Deflection; they are
Sheet 5: If MT Roaming Forwarding is supported and the MT Roaming Forwarding Indicator is received from the VLR,
the MSC stops any on-going Camel transaction.
Sheet 6: the procedure CAMEL_MT_VMSC_Notify_CF is specific to CAMEL phase 3 or later; it is specified in

3GPP TS 23.078 [12].
Sheet 6: If the VMSC does not support CAMEL phase 3 or later, processing starts with the possible call of the
procedure CCBS_Check_Last_Call.
Sheet 6: The task "set redirection information" includes the mapping of the MSISDN parameter received in the Send
Info For Incoming Call ack message to the redirecting number of the IAM message and the setting of the presentation
indicator of the redirecting number of the IAM message according to the value of the Redirecting presentation
parameter received in the Send Info For Incoming Call ack message.
3GPP
Release 14 178 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 6: it is an operator option whether to send an Address Complete message if the VLR returns forwarding
information. If the VMSC sends an Address Complete message, it shall include the called party's status field of the
Backward call indicator set to "no indication".
Sheet 6, sheet 8: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 6: the procedure Activate_CF_Process is specified in subclause 7.2.1.7.
Sheet 6: the procedure UUS_ICH_Set_Info_In_IAM is specific to UUS, it is specified in 3GPP TS 23.087 [20].
Sheet 6: 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.

3GPP TS 23.078 [12].
Sheet 7: The processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL
phase 3 or later, the input signal Int_Release Call will not be received.
Sheet 8: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later; it is
specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from
the "Pass" exit of the test "Result?".
Sheet 8: the procedure Handle_COLP_Forwarding_Interaction_MSC is specified in subclause 7.2.1.6.
Sheet 8: the procedure Send_Answer_If_Required is specified in subclause 7.2.1.4.
Sheet 8: the procedure Send_Network_Connect_If_Required is specified in subclause 7.2.1.5.
Sheet 8: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later; it is specified in

Sheet 10: the procedure CCBS_MT_MSC_Check_Forwarding is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 11: the processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL
phase 3 or later, the input signal Send Info For MT Reconnected Call ack will not be received.
Sheet 11: the procedure Handle_ORLCF_VMSC is specific to OR; it is specified in 3GPP TS 23.079 [13]. If the VMSC
does not support OR, processing continues from the "No" exit of the test "Result = Forwarding Failed?".
Sheet 13, sheet 14: the procedure CAMEL_MT_GMSC_DISC1 is called if the VMSC supports CAMEL phase 3 or
later; it is specified in 3GPP TS 23.078 [12].
Sheet 13, sheet 14: the procedure CAMEL_MT_GMSC_DISC2 is called if the VMSC supports CAMEL phase 3 or
later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing
continues from the "No" exit of the test "Result=Reconnect?".
Sheet 13: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in 3GPP TS 23.087 [20].
Sheet 14: after the VMSC has sent an IAM to the process MT_CF_MSC, it acts as a transparent relay for messages
received from the GMSC and the process MT_CF_MSC. Any message other than Address Complete, Connect, Answer
or Release causes no change of state in the process ICH_MSC.
Sheet 15: The processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL
phase 3 or later, the input signal Int_Release Call will not be received.
Sheet 16: the procedure Process_Hold_Request is specific to Call Hold; it is specified in 3GPP TS 23.083[16].
Sheet 16: the procedure Process_Retrieve_request is specific to Call_Hold; it is specified in 3GPP TS 23.083[16].
7.3.1.2 Procedure Page_MS_MSC

Sheet 1: the test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS
and the network.
3GPP
Release 14 179 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 1: for an SMS or SS page, the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to
the page still exists.
Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls, because the VLR will
always use a page type of "circuit-switched call", but the more generalized procedure Page_MS_MSC is equally
applicable to paging for SMS delivery or network-initiated SS procedures.
Sheet 1: If the MSC supports the option to delay Mobile Terminating CM request during a location update procedure
(see 3GPP TS 24.008 [13] section 4.5.1.3.1 Mobile Terminating CM Activity):
If location update procedure is ongoing for the MS,
If the "follow-on" indicator is received and MSC supports "follow-on" feature, the Page_MS_MSC procedure
should return FAIL after sending Page MS negative response (cause Busy Subscriber) to VLR.
Otherwise, the MSC should delay the launching of Page_MS_MSC procedure until the location update
procedure ends.
- If the result of location update is successful and location update is not through Gs interface, then
Page_MS_MSC procedure returns with PASS.
- If the result of location update is successful and location update is through Gs interface, then Page_MS_MSC
continues from the beginning of the procedure.
- If the result of location update is not successful, then the procedure should return FAIL after sending Page
MS negative response (cause Absent Subscriber) to VLR.
Sheet 2: the procedure Check_MT_Multicall_MSC 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=Not provisioned?".
Sheet 2: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the
established phase (called party answer).
Sheet 2: the test Call waiting" takes the "Yes" exit if a waiting call has been offered to the subscriber but the outcome of
offering the call has not been determined.
Sheet 2: if there is one established call, the negative response Busy Subscriber (More calls possible) includes the basic
service which applies for the established call. If there are two or more established calls (the Multicall case), the negative
response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls
(See 3GPP TS 23.135 [25]).
Sheet 3: the signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM
service request for anything other than a circuit-switched call, or completed the location registration procedure.
Sheet 4: A MSC not implementing the MT Roaming Retry feature and the MT Roaming Forwarding feature may not
immediately stop paging upon receipt of a Cancel Location message.
7.3.1.3 Procedure Search_For_MS_MSC

Sheet 1: the test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS
and the network.
Sheet 1: for an SMS or SS page, the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to
the page still exists.
Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls, because the VLR will
always use a page type of "circuit-switched call", but the more generalized procedure Search_For_MS_MSC is equally
applicable to paging for SMS delivery or network-initiated SS procedures.
Sheet 1: If the MSC supports the option to delay the Mobile Terminating CM request during a location update
procedure (see 3GPP TS 24.008 [13] section 4.5.1.3.1 Mobile Terminating CM Activity):
If location update procedure is ongoing for the MS, and if the "follow-on" indicator is received and the MSC supports
the "follow-on" feature, the Search_MS_MSC procedure should return FAIL after sending Search MS negative
response (cause Busy Subscriber) to VLR.
3GPP
Release 14 180 3GPP TS 23.018 V14.0.0 (2017-03)
Otherwise, the MSC should delay the launching of Search_MS_MSC procedure until location update procedure ends.
- If the result of location update is successful and location update is not through Gs interface, then the
Search_MS_MSC procedure returns with PASS.
- If the result of location update is successful and location update is through Gs interface, then the procedure
continues from the beginning of the Page_MS_MSC procedure.
- If the result of the location update is not successful, then the procedure should return FAIL after sending the
Search MS negative response (cause Absent Subscriber) to VLR.
Sheet 2: the procedure Check_MT_Multicall_MSC 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=Not provisioned?".
Sheet 2: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the
established phase (called party answer).
Sheet 2: the test "Call waiting" takes the "Yes" exit if a waiting call has been offered to the subscriber but the outcome
of offering the call has not been determined.
Sheet 2: if there is one established call, the negative response Busy Subscriber (More calls possible) includes the basic
service which applies for the established call. If there are two or more established calls (the Multicall case), the negative
response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls
(See 3GPP TS 23.135 [25]).
Sheet 3: the signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM
service request for anything other than a circuit-switched call, or completed the location registration procedure.
Sheet 4 : A MSC not implementing the MT Roaming Retry feature and the MT Roaming Forwarding feature may not
immediately stop paging upon receipt of a Cancel Location message.
7.3.1.4 Procedure Complete_Call_In_MSC

Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP.
Sheet 1: the VMSC derives the PLMN bearer capability required for the call according to the rules defined in
3GPP TS 29.007 [30].
Sheet 1, sheet 2: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of
information in the Set-up and Call Confirmed messages.
Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS, it is specified in 3GPP TS 23.087 [20].
Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 2: the procedure Establish_Terminating_TCH_Multicall is specific to Multicall; it is specified in

3GPP TS 23.135 [25].
Sheet 2: the test "Result=Rejected?" can take the "Yes" exit only if the procedure
Establish_Terminating_TCH_Multicall was called.
Sheet 2, sheet 3, sheet 4, sheet 5, sheet 6, sheet 7: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC
supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL
phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?".
Sheet 2, sheet 3, sheet 6, sheet 9, sheet 10: the procedure CAMEL_MT_GMSC_DISC6 is called if the VMSC supports
CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12].
Sheet 2, sheet 5, sheet 9: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 3, sheet 5: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 3: the procedure CAMEL_Start_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in
3GPP TS 23.078 [12].
3GPP
Release 14 181 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 3: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later; it is specified in

Sheet 3, sheet 6: the procedure UUS_ICH_Check_Support 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 3: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS.
Sheet 3: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 3, sheet 6: the procedure Establish_Terminating_TCH_Multicall 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 4, sheet 7: the procedure Handle_AoC_MT_MSC is specific to AoC. If the VMSC does not support AoC,
processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 4, sheet 7: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or
later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing
continues from the "Yes" exit of the test "Result=Pass?".
Sheet 4, sheet 7: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP.
Sheet 4: the procedure Send_Network_Connect_If_Required is specified in subclause 7.2.1.5.
Sheet 5, sheet 11: the processing in the branch starting with the input "CD Request" is specific to Call Deflection; if the
VMSC does not support Call Deflection the input is discarded.
Sheet 5, sheet 11: the procedure Handling_CD_MSC is specific to Call Deflection; it is specified in
3GPP TS 23.072 [11].
Sheet 6: the procedure CAMEL_Stop_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in
3GPP TS 23.078 [12].
Sheet 7: the procedure Send_Answer_If_Required is specified in subclause 7.2.1.4.
Sheet 8: the input signal "CAMEL TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or
later.
Sheet 8, sheet 11: the procedure UUS_ICH_Check_Forwarding 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 9, sheet 10: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in

3GPP TS 23.087 [20].
Sheet 11: 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 3GPP TS 23.087 [20].
Sheet 11: the procedure CD_UUS_Interaction is specific to Call Deflection; it is specified in 3GPP TS 23.072 [11].
7.3.1.5 Void
7.3.1.6 Procedure Set_CLIP_Info_MSC

The originating exchange may release the call or the MS may terminate the transaction with the network by sending a
Release transaction message while a response is awaited from the process CLIP_MAF002. The message is saved for
processing after return from the procedure.
3GPP
Release 14 182 3GPP TS 23.018 V14.0.0 (2017-03)
7.3.1.7 Void
7.3.1.8 Procedure Establish_Terminating_TCH_If_Required

The procedure TCH_Check is specified in subclause 7.1.1.14.
7.3.1.9 Procedure Handle_AoC_MT_MSC
7.3.1.10 Procedure Set_COL_Presentation_Indicator_MSC

The originating exchange may release the call or the MS may terminate the transaction with the network by sending a
Release transaction message while a response is awaited from the process COLP_MAF041. The message is saved for
processing after return from the procedure.
3GPP
Release 14 183 3GPP TS 23.018 V14.0.0 (2017-03)
Process ICH_MSC ICH_MSC1(17)

to handle an incoming (MT) call are to/from the BSS;
are to/from the VLR
Idle
Release Initial
From GMSC From GMSC
Resources Address
Convert ISDN BC/LLC/HLC

Release (if present) to bearer
Resources service/teleservice & CS BC;
Store UUS information (if received)
Send Info
Release
For Incoming
MSRN
Call
ACM sent:=False;
Idle Answer sent:=False;
BOR:=False;
Network connect sent:=False;
TCH allocated:=False;
UUS1 result sent:=False;
UUS1 implicit active:=False;
Wait_For_ UUS1 explicit active:=False;
Page_Request UUS2 active:=False;
UUS3 active:=False;
UUS CF interaction:=False;
Call answered := False;
On_Hold:=False
Continue
CAMEL
Handling
CAMEL_
ICH_MSC_ See TS 23.078
INIT
Result?
Leg1_only Reconnect MSRN Aborted Fail
Leg1_status Set Suppress Set

:= Set-up VT-CSI cause
CAMEL_ICH_ Send Info For Send Info

LEG1_MSC MT Reconnected For Incoming Release
(Leg1_Status) Call Call
Release call
resources
Idle
Wait_For_
Wait_For_
Reconnected_ Idle
Page_Request
Call_Result
See TS 23.078
Figure 67a: Process ICH_MSC (sheet 1)
3GPP
Release 14 184 3GPP TS 23.018 V14.0.0 (2017-03)

to handle an incoming (MT) call are to/from the GMSC;
Wait_For_ signals to/from the right
Page_Request are to/from the VLR
Send Info Send Info

For Incoming Call is to be Search Complete
Page MS For Incoming
Call negative forwarded For MS Call
Call Ack
response
Set Page_ Search_For_

1 2
cause MS_MSC MS_MSC
Yes Yes
Result= Result=
See TS 23.078
Pass? Pass?
No No
No No
Result= Result=
Fail? Fail
CAMEL_ Yes Process_ Yes CAMEL_

MT_GMSC_ Access_ MT_GMSC_
DISC6 Request_MSC DISC6
Release call Result= Release call

resources Pass? resources
No
Yes
CAMEL_ Wait_For_ Wait_For_ CAMEL_ Wait_For_

MT_GMSC_ Idle MT_Call_ MT_Call_ MT_GMSC_ MT_Call_ Idle
DISC4 Result Result DISC4 Result
Yes Yes
Result= Result=
See TS 23.078
Reconnect? Reconnect?
No No
Send Info For

Release MT Reconnected Release
Call
Release call Release call

resources resources
Wait_For_
Idle Reconnected_ Idle
Call_Result
See TS 23.078 See TS 23.078
Figure 67b: Process ICH_MSC (sheet 2)
3GPP
Release 14 185 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC Wait_For_
to handle an incoming (MT) call MT_Call_
Result
Send Info Process

For Incoming Complete
2 Call
Call negative Call
Waiting
response
Process_
Complete_
CD_Reject See TS 23.072 See TS 23.083 Call_
Call_In_MSC
Waiting
CCBS_Set_ Yes Yes

Result= Result=
Diagnostic_ See TS 23.093
Pass? Pass?
For_Release
No Store CW Treatment
indicator for this call No
if received in SII2
UUS_ICH_
Support Call answered
:= True
Set
cause
Call setup Call Call setup
To Subs_FSM To Subs_FSM To Subs_FSM
failed established failed
Cause= Yes
No Subscriber
Reply?
5
No
CAMEL_ CAMEL_ Yes Yes

Result= Result=
MT_GMSC_ MT_GMSC_
Fail Fail
DISC4 DISC5
No Wait_For_
MT_Call_ No
No
Result= Result
Reconnect? Yes Yes
Result= Result=
Yes Reconnect? Reconnect?
Send Info For No Send Info For

MT Reconnected Release MT Reconnected No
Call Call
Wait_For_ Wait_For_
Reconnected_ Reconnected_
Call_Result Call_Result
Release
See TS 23.078 See TS 23.078
transaction Signals to/from the left
are to/from the GMSC;
are to/from the VLR
CCBS_Check_ unless marked otherwise
See TS 23.093
Last_Call
Release
call
resources
Idle
Figure 67c: Process ICH_MSC (sheet 3)
3GPP
Release 14 186 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC
to handle an incoming (MT) call
5

No
Yes
Leg1_status
:= Active
CAMEL_ICH_ Wait_For_
See TS 23.078
LEG1_MSC Clear
(Leg1_Status)
CAMEL_ICH_
See TS 23.078
LEG2_MSC
Idle
Figure 67d: Process ICH_MSC (sheet 4)
3GPP
Release 14 187 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e s s IC H _ M S C IC H _ M S C 5 (1 8 )
P r o c e s s i n th e M S C S ig n a ls t o / f r o m t h e le f t
t o h a n d le a n in c o m i n g ( M T ) c Wa lla it _ F o r _ a r e t o / f r o m th e G MSC;
M T _ C a ll _ s i g n a ls t o / f r o m th e r ig h t
R e s u lt a r e t o / f r o m th e VLR
S e n d In f o C a ll is t o b e
1 F o r In c o m in g fo rw a rd e d
C a ll a c k
M T R o a m in g
F o rw a rd in g s u p p o rte d
yes
No
C A M E L_C heck_
S e e T S 2 3 .0 7 9
O R LC F_VM S C
M T R o a m in g F o r w a r d i n g
I n d i c a t o r r e c e iv e d
No
VMSCCF
Yes M T R o a m in g
R e s u lt ?
R e t r y s u p p o r te d
I n it ia l A d d r e s s O R LC F
M essage No
Yes
to n e w M S C H a n d le _
S e e T S 2 3 .0 7 9
M T R o a m in g O R LC F_VM S C
R e try In d ic a to r No
re c e iv e d
Yes C o n ti n u e A c c e p te d
W a it _ F o r _
R e s u lt ?
M TR F_A C M
F o r w a r d i n g F a i le d
H a n d le _
O R LC F_VM S C
C D _ F a il u r e S e e T S 2 3 .0 7 2 C D _ S uccess S e e T S 2 3 .0 7 2
W a it _ F o r _
R e le a s e _
F ro m _ G M S C
W a it _ F o r _
R e le a s e _
R e le a s e F ro m _ G M S C
3 R e le a s e
CAM EL_
M T_G M SC_
D IS C 6
CAM EL_
M T_G M SC_ S e e T S 2 3 .0 7 8
R e le a s e c a ll D IS C 6
re s o u rc e s
C C B S _C heck_ S e e T S 2 3 .0 9 3
L a s t_ C a l l
I d le
R e le a s e c a ll
re s o u rc e s
I d le
Figure 67e: Process ICH_MSC (sheet 5)
3GPP
Release 14 188 3GPP TS 23.018 V14.0.0 (2017-03)

3
Process in the MSC Signals to the right
to handle an incoming (MT) call are to the VLR
Yes
Type of forwarding=
Reconnect?
No
CAMEL_
MT_VMSC_ See TS 23.078
Notify_CF
Yes
Result=
4
Reconnect?
No
CCBS_Check_
See TS 23.093
Last_Call
Set
redirection
information
Send_ACM_
If_Required
Activate_
CF_Process
Fail Pass
Result?
Release
UUS_ICH_
Release Set_Info_ See TS 23.087
In_IAM
CAMEL_ Initial
MT_GMSC_ See TS 23.078 Address To process MT_CF_MSC
DISC4 Message
Yes CAMEL_Store_
Result= Destination_ See TS 23.078
Reconnect? Address
(False, True)
No
Send Info For

MT Reconnected CD_Failure See TS 23.072 CD_Success See TS 23.072
Call
Wait_For_
CCBS_Check_ Wait_For_
Reconnected_ See TS 23.093
Last_Call Forward_ACM
Call_Result
Idle
Figure 67f: Process ICH_MSC (sheet 6)
3GPP
Release 14 189 3GPP TS 23.018 V14.0.0 (2017-03)

Wait_For_MT_Call_Result, are to/from the VLR
Wait_For_Reconnected_Call_Result unless marked otherwise
Int_Release_
From gsmSSF
Call
Abort
Release
Release
To BSS
Transaction
Release
call
resources
Idle
Figure 67g: Process ICH_MSC (sheet 7)
3GPP
Release 14 190 3GPP TS 23.018 V14.0.0 (2017-03)

Wait_For_ are to/from the process MT_CF_MSC
Forward_ACM unless marked otherwise
Address
Connect
Complete
Send_ACM_
If_Required
CAMEL_MT_
See TS 23.078
MSC_ALERTING
Result?
Answer Else
Pass
Wait_For_
Forward_Answer
Release Release Answer
CAMEL_ CAMEL_ CAMEL_

Release See TS 23.078 MT_GMSC_ MT_GMSC_ See TS 23.078 See TS 23.078 MT_GMSC_
DISC4 ANSWER ANSWER
CAMEL_
Else Else
MT_GMSC_ See TS 23.078 Result? Result?
DISC6
Pass Pass
Handle_COLP_ Handle_COLP_
No Result= Release Reconnect
Forwarding_ Result? Forwarding_
Reconnect?
Interaction_MSC Interaction_MSC
Yes Fail
Set COLP Set COLP

Release presentation Release 6 presentation
indicator indicator
Send_Network_
Send_Answer_
Idle Connect_
If_Required
If_Required
6
Call answered
:= True
Send Info For

Release call
To VLR MT Reconnected 7
resources
Call
Wait_For_
Idle Reconnected_
Call_Result
Figure 67h: Process ICH_MSC (sheet 8)
3GPP
Release 14 191 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC
to handle an incoming (MT) call
7

No
Yes
Leg1_status
:= Active
CAMEL_ICH_ Wait_For_
See TS 23.078
LEG1_MSC Clear
(Leg1_Status)
CAMEL_ICH_
See TS 23.078
LEG2_CF_MSC
Idle
Figure 67i: Process ICH_MSC (sheet 9)
3GPP
Release 14 192 3GPP TS 23.018 V14.0.0 (2017-03)

to handle an incoming (MT) call Wait_For_ are to/from the GMSC;
Forward_ACM signals to/from the right
Release Release
CAMEL_
Release MT_GMSC_ See TS 23.078
DISC4
Yes
CAMEL_
Result=
See TS 23.078 MT_GMSC_
Reconnect?
DISC6
No
CCBS_MT_ Send Info For

See TS 23.093 MSC_Check_ MT Reconnected To VLR
Forwarding Call
Wait_For_
Reconnected_
Call_Result
Send Info For

MT Reconnected
Call negative
response
CCBS_Set_
See TS 23.093 Diagnostic_ Set cause
For_Release
Release Release
Int_Exception To gsmSSF
Release call
resources
Idle
Figure 67j: Process ICH_MSC (sheet 10)
3GPP
Release 14 193 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC Wait_For_ Signals from the left
to handle an incoming (MT) call Reconnected_ are from the GMSC;
Call_Result signals from the right
are from the VLR
Send Info For MT

Reconnected
Call ack
True
Call
answered
False
Handle_
See TS 23.079
ORLCF_VMSC
No Yes
Result=
Accepted?
No
Result=
Forwarding
Failed?
Yes
4 See TS 23.072 CD_Failure CD_Success See TS 23.072
Wait_For_
Release_From_
GMSC
Release
CAMEL_
DISC6
CCBS_Check_
See TS 23.093
Last_Call
Release call
resources
Idle
Figure 67k: Process ICH_MSC (sheet 11)
3GPP
Release 14 194 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC Wait_For_ Signals to/from the left
to handle an incoming (MT) call MT_Call_ are to/from the GMSC;
Result signals to/from the right
are to/from the BSS
Release
Release
transaction
CAMEL_ CAMEL_
MT_GMSC_ See TS 23.078 MT_GMSC_ See TS 23.078
DISC6 DISC4
Yes
Result=
Reconnect?
No
Release
Release
transaction
CCBS_Check_
See TS 23.093
Last_Call
Send Info For

Abort To VLR MT Reconnected To VLR
Call
Release
call
resources
Wait_For_
Idle Reconnected_
Call_Result
Figure 67l: Process ICH_MSC (sheet 12)
3GPP
Release 14 195 3GPP TS 23.018 V14.0.0 (2017-03)

to handle an incoming (MT) call Wait_For_Clear are to/from the GMSC;
are to/from the BSS
Release
Release
transaction
UUS_MSC_ CAMEL_
Check_ See TS 23.087 MT_GMSC_ See TS 23.078
UUS1_UUI DISC2
Yes
Release Result=
transaction Reconnect?
No
CAMEL_ UUS_MSC_
See TS 23.078 MT_GMSC_ See TS 23.087 Check_
DISC1 UUS1_UUI
Send Info For

Release MT Reconnected To VLR
Call
CCBS_Check_
See TS 23.093
Last_Call
Release
call
resources
Call
To Subs_FSM
cleared
Wait_For_
Idle Reconnected_
Call_Result
Figure 67m: Process ICH_MSC (sheet 13)
3GPP
Release 14 196 3GPP TS 23.018 V14.0.0 (2017-03)

to handle an incoming (MT) call Wait_For_ are to/from the GMSC;
Forward_Clear signals to/from the right
Release Release
CAMEL_
Release MT_GMSC_ See TS 23.078
DISC2
Yes
CAMEL_
Result=
Reconnect?
DISC1
No
Send Info For

Release MT Reconnected To VLR
Call
Release
call
resources
Wait_For_
Idle Reconnected_
Call_Result
Wait_For_Forward_ACM,
Wait_For_Forward_Answer,
Wait_For_Forward_Clear
* *
- -
Figure 67n: Process ICH_MSC (sheet 14)
3GPP
Release 14 197 3GPP TS 23.018 V14.0.0 (2017-03)

Wait_For_Forward_ACM, Wait_For_
Wait_For_Forward_Clear Clear
Int_Release_ Int_Release_
From gsmSSF From gsmSSF
Call Call
Release
Release To the BSS
transaction
Release Release
Release Release
call call
resources resources
Call
Idle To Subs_FSM
cleared
Idle
Figure 67o: Process ICH_MSC (sheet 15)
3GPP
Release 14 198 3GPP TS 23.018 V14.0.0 (2017-03)

to handle an incoming (MT) call are to/from the BSS
Wait_For_
Clear
Hold Retrieve
request request
Hold Hold
Yes No No Yes
Process_ Process_
See 3G TS Hold Retrieve See 3G TS
Hold_ Retrieve_
23.083 reject reject 23.083
Request Request
Wait_For_
Clear
Figure 67p: Process ICH_MSC (sheet 16)
3GPP
Release 14 199 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC Signals from the left
to handle an incoming (MT) call are from the BSS;
signals to the right
are to the Subs_FSM process.
Wait_For_
Clear
ECT MPTY
request request
ECT MPTY
request request
Wait_For_
Clear
Figure 67q: Process ICH_MSC (sheet 17)
3GPP
Release 14 200 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e s s IC H _ M S C IC H _ M S C 1 8 (1 8 )
P r o c e s s i n th e M S C S ig n a ls to / f r o m th e le ft
t o h a n d le a n in c o m i n g ( M T ) c a ll a r e t o / f r o m th e GM SC;
s ig n a ls to / f r o m th e r i g h t
a r e t o / f r o m th e new M S C
W a it _ F o r _ W a it_ F o r_ M T R F _ A C M
M TR F_A C M W a it_ fo r_ M T R F _ A n s w e r
W a it_ F o r_ M T R F _ C le a r
A d d re s s
C on nect R e le a s e R e le a s e
C o m p le t e
S end_A C M _ S e n d _ N e tw o rk _
C o n n e c t_ R e le a s e R e le a s e
If_ R e q u ire d
If_ R e q u ire d
W a it _ F o r _ R e le a s e c a ll
M TR F_A nsw e r re s o u rc e s
A nsw er I d le
S e n d _ A n s w e r_
If_ R e q u ire d
C a ll a n s w e re d
:= T r u e
W a it _ F o r _
M T R F _ C le a r
Figure 67r: Process ICH_MSC (sheet 18)
3GPP
Release 14 201 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Page_MS_MSC PAGE_M1(3)

Procedure in the MSC signals to/from the right
to page an MS in a are to/from the VLR
specified location area unless marked otherwise
Location No
area ID
known?
Yes Set negative
response:
Call No
Unknown LAI
still
exists?
Yes Set negative
Yes response:
MS System
connection Failure
exists?
No
Clear received:= SMS or SS

False page?
Yes
No
No
Paging via
SGSN possible?
Yes
In specified
Page
location area
Page MS Request
To Subs_FSM
via SGSN call status
Set access Page MS

connection negative
status response

response Pass Fail
timer
Wait_For_ Wait_For_
Page_ Call_Status
Response
Figure 68a: Procedure Page_MS_MSC (sheet 1)
3GPP
Release 14 202 3GPP TS 23.018 V14.0.0 (2017-03)

to page an MS in a Call_Status are to/from the BSS;
specified location area signals to/from the right
are to/from the VLR
Call status From process Subs_FSM
Check_MT_
See TS 23.135
Multicall_MSC
Yes
Result=
Offered?
No
Yes Result=
More calls
possible?
No
Result= No
not
provisioned?
Yes
Yes
Call in
setup?
No
No Yes
Call
waiting?
Set negative More calls Set negative

response: possible response:
Busy subscriber Busy subscriber
(NDUB)
Page Set access

MS negative connection
response status
Result:= Result:=
Fail Pass
Figure 68b: Procedure Page_MS_MSC (sheet 2)
3GPP
Release 14 203 3GPP TS 23.018 V14.0.0 (2017-03)

to page an MS in a Page_ are to/from the BSS;
specified location area Response signals to/from the right
are to/from the VLR

connection Release From GMSC response Service switched call
True True CM
Clear Clear To process
Abort Service
received received OCH_MSC
Request
False False
True
Clear
received
False

response: response:
Absent Busy Subscriber
Subscriber (NDUB)
Set access Release Page MS Page MS

connection transaction negative negative
status response response
Result:= Result:= Clear received:= Result:= Result:= Result:= Result:=

Pass Aborted True Aborted Fail Fail Aborted
Wait_For_
Page_
Response
Figure 68c: Procedure Page_MS_MSC (sheet 3)
3GPP
Release 14 204 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e d u re P a g e _ M S _ M S C P A G E _ M 4 (4 )
P r o c e d u r e i n th e M S C S ig n a ls t o / f r o m t h e le f t
t o p a g e a n M S in a a r e t o / f r o m th e BSS;
s p e c i f ie d l o c a t io n a r e a s i g n a ls t o / f r o m th e r ig h t
W a it _ F o r _ a r e t o / f r o m th e VLR
P age_ u n le s s m a r k e d o th e r w i s e
R esponse
C an cel
L o c a t io n
T ru e
C le a r
re c e iv e d
F a ls e
S e t n e g a t iv e R e le a s e
re s p o n s e : tra n s a c tio n
L o c a t io n C a n c e l le d
i n c l u d e s th e f o l l o w in g p a r a m e te r s P age M S
if r e c e iv e d in th e C a n c e l L o c a tio n n e g a t iv e
m e s s a g e fro m th e V L R : re s p o n s e
- M T R F S u p p o r t e d A n d A u t h o r i z e d f la g
- M T R F S u p p o r t e d A n d N o t A u th o r i z e d f l a g
- new V LR num ber R e s u lt : = R e s u lt : =
- new LM SI F a il A b o rte d
Figure 68d: Procedure Page_MS_MSC (sheet 4)
3GPP
Release 14 205 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Search_For_MS_MSC SRCH_M1(4)

to search for an MS are to/from the BSS;
(page in all location areas) signals to/from the right
are to/from the VLR
Call No
still
exists?
Yes
MS Yes
connection
exists?
No
Yes
Clear received:= SMS or SS
False page?
No
No
Paging via
SGSN possible?
Yes
Search for MS Request Set negative

To Subs_FSM response:
via SGSN call status
System
Failure
In all location areas Set access Search For

or in PgA if PgA received Page connection MS negative
and supported status response

response Pass Fail
timer
Wait_For_ Wait_For_
Search_ Call_Status
Response
Figure 69a: Procedure Search_For_MS_MSC (sheet 1)
3GPP
Release 14 206 3GPP TS 23.018 V14.0.0 (2017-03)

to search for an MS Call_Status are to/from the BSS;
(page in all location areas) signals to/from the right
are to/from the VLR
Call status From process Subs_FSM
Check_MT_
See TS 23.135
Multicall_MSC
Yes
Result=
Offered?
No
Yes Result=
More calls
possible?
No
No
Result=
not provisioned
Yes
Yes
Call in
setup?
No
No Yes
Call
waiting?
Set negative More calls Set negative

response: possible response:
Busy Subscriber Busy Subscriber
(NDUB)
Search For Set access

MS negative connection
response status
Result:= Result:=
Fail Pass
Figure 69b: Procedure Search_For_MS_MSC (sheet 2)
3GPP
Release 14 207 3GPP TS 23.018 V14.0.0 (2017-03)

to search for an MS Search_ are to/from the BSS;
(page in all location areas) Response signals to/from the right
are to/from the VLR

connection Release From GMSC response Service switched call
True True CM
Clear Clear To process
Abort Service
received received OCH_MSC
Request
False False
True
Search Release Clear
For MS ack transaction received
False

response: response:
Absent Busy Subscriber
Subscriber (NDUB)
Set access Search Search

connection For MS For MS
status negative negative
response response
Result:= Result:= Clear received:= Result:= Result:= Result:= Result:=

Pass Aborted True Aborted Fail Fail Aborted
Wait_For_
Search_
Response
Figure 69c: Procedure Search_For_MS_MSC (sheet 3)
3GPP
Release 14 208 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e d u re S e a rc h _ F o r_ M S _ M S C S R C H _ M 4 (4 )
P r o c e d u r e i n th e M S C S ig n a ls t o / f r o m t h e le f t
to s e a rc h fo r a n M S a r e t o / f r o m th e BSS;
( p a g e in a l l lo c a t i o n a r e a s ) s i g n a ls t o / f r o m th e r ig h t
W a it _ F o r _ a r e t o / f r o m th e VLR
S e a rc h _ u n le s s m a r k e d o th e r w i s e
R esponse
C an cel
L o c a t io n
T ru e
C le a r
re c e iv e d
F a ls e
S e t n e g a t iv e R e le a s e
re s p o n s e : tra n s a c tio n
L o c a t io n C a n c e l le d
i n c l u d e s th e f o l l o w in g p a r a m e te r s S e a rc h fo r M S
if r e c e iv e d in th e C a n c e l L o c a tio n n e g a t iv e
m e s s a g e fro m th e V L R : re s p o n s e
- M T R F S u p p o r t e d A n d A u t h o r i z e d f la g
- M T R F S u p p o r t e d A n d N o t A u th o r i z e d f l a g
- new V LR num ber R e s u lt : = R e s u lt : =
- new LM SI F a il A b o rte d
Figure 69d: Procedure Search_For_MS_MSC (sheet 4)
3GPP
Release 14 209 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Complete_Call_In_MSC CCI_MSC1(11)

to complete an MT call are to/from the BSS;
on request from the VLR signals to/from the right
are to/from the VLR
Set_CLIP_
Info_MSC
Derive required
See TS 29.007
PLMN BC
Setup
UUS_ICH_UUS1_
Implicit_ See TS 23.087
Active
CCBS_Report_
See TS 23.093
Not_Idle
Wait_For_
Setup_
Response
Setup Int_Release_
From gsmSSF
failure Call
Set negative
response:
Absent
Subscriber
Complete
Call
negative
response
Result:=
Fail
Figure 70a: Procedure Complete_Call_In_MSC (sheet 1)
3GPP
Release 14 210 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call Setup_ are to/from the BSS;
on request from the VLR Response signals to/from the right
are to/from the VLR
Call
Confirmed
Multicall
supported
in MSC?
No Yes
Establish_ Establish_
Terminating_ Terminating_TCH_ See TS 23.135
TCH_If_ Multicall
Required
Yes
Result=
Fail?
No
Yes CAMEL_
Result=
Aborted
DISC4
No
Yes Yes
Result= Result=
Abort
Rejected? Reconnect?
No No
CAMEL_ Set negative

MT_GMSC_ See TS 23.078 response:
DISC6 Radio
congestion
CCBS_ICH_MSC_ Complete
See TS 23.093 Call
Report_Failure
negative
response

Aborted Reconnect Fail
Wait_For_
4
Alerting
Figure 70b: Procedure Complete_Call_In_MSC (sheet 2)
3GPP
Release 14 211 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call Wait_For_ are to/from the BSS;
on request from the VLR Alerting signals to/from the right
are to/from the VLR
Alerting Connect
UUS_ICH_ UUS_ICH_
See TS 23.087 See TS 23.087
Check_Support Check_Support
No No
Result= Result=
Pass? Pass?
Yes Yes
CCBS_ICH_MSC_ CCBS_ICH_MSC_
See TS 23.093 1 See TS 23.093
Report_Success Report_Success
No
Establish_
NRCT
Terminating_ See TS 23.135
provided?
TCH_Multicall
Yes
Yes
Start No Reply Result=
Call Timer Pass?
No
CAMEL_
See TS 23.078 3
Start_TNRy
Yes
Send_ACM_ Result=
4
If_Required Aborted?
No
CAMEL_
UTU2Cnt:=0 See TS 23.078 MT_GMSC_
DISC4
CAMEL_MT_ Yes Result=

See TS 23.078
MSC_ALERTING Reconnect?
No
Reconnect
Result? Release Abort
Answer Fail Release
Pass
CAMEL_
A Release To GMSC Abort See TS 23.078 MT_GMSC_
DISC6

Aborted Reconnect Aborted Aborted
Wait_for_
Answer
Figure 70c: Procedure Complete_Call_In_MSC (sheet 3)
3GPP
Release 14 212 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call 3 are to/from the BSS;
are to/from the VLR
Handle_AoC_
MT_MSC
No
Result=
Pass?
2
Yes
CAMEL_
Connect
MT_GMSC_ See TS 23.078 Set cause
ack
DISC4
No
CAMEL_
Result=
Reconnect?
ANSWER
Yes
Reconnect
Result?
Fail Release
Pass
Set_COL_
Release To GMSC Presentation_
Indicator_MSC
Send_Network_
To GMSC Connect_If_ To GMSC Release
Required
Complete
Call Abort
ack

Aborted Pass Reconnect Aborted
Figure 70d: Procedure Complete_Call_In_MSC (sheet 4)
3GPP
Release 14 213 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call Wait_For_ are to/from the BSS;
on request from the VLR Alerting signals to/from the right
are to/from the VLR
Alerting
1 CD_Request
failure
Release CCBS_ICH_MSC_
See TS 23.093
transaction Report_Success
Set cause
CAMEL_
MT_GMSC_ See TS 23.078 Handling_CD_MSC See TS 23.072
DISC4
Yes
Result=
Reconnect?
No
CCBS_ICH_MSC_
See TS 23.093
Report_Failure
Complete
Abort Call
negative
response
Release To GMSC

Reconnect Aborted Fail
Figure 70e: Procedure Complete_Call_In_MSC (sheet 5)
3GPP
Release 14 214 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call Wait_for_ are to/from the BSS;
on request from the VLR Answer signals to/from the right
are to/from the VLR
A Connect
CAMEL_
See TS 23.078
Stop_TNRy
UUS_ICH_
Support
No
Result=
Pass?
Yes
Establish_
Terminating_ See TS 23.135 1
TCH_Multicall
Yes
Result=
Pass?
No
Yes
Result=
Aborted?
No
CAMEL_
DISC4
Yes
Result=
Reconnect?
Release Abort
CAMEL_
Abort See TS 23.078 MT_GMSC_
DISC6

Reconnect Aborted Aborted
Figure 70f: Procedure Complete_Call_In_MSC (sheet 6)
3GPP
Release 14 215 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call 5 are to/from the BSS;
are to/from the VLR
Handle_AoC_
MT_MSC
No
Result=
2
Pass?
Yes
CAMEL_
Connect
MT_GMSC_ See TS 23.078 Set cause
ack
DISC4
Yes
CAMEL_
Result=
Reconnect?
ANSWER
Yes
Reconnect
Result?
Fail Release
Pass
Set_COL_
Release To GMSC Presentation_
Indicator_MSC
Send_Answer_
To GMSC To GMSC Release
If_Required
Complete
Call Abort
ack

Aborted Pass Reconnect Aborted
Figure 70g: Procedure Complete_Call_In_MSC (sheet 7)
3GPP
Release 14 216 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the MSC Wait_for_ Signals to/from the left
to complete an MT call Answer are to/from the BSS;
are to/from the VLR
No Reply CAMEL TNRy

Call Timer expired
expired
UUS_ICH_
Forwarding
No
Result=
Pass?
Yes
Set negative Release

response: transaction
No subscriber
reply
Complete
Call 2
negative
response
Release
transaction
Result:=
Fail
Figure 70h: Procedure Complete_Call_In_MSC (sheet 8)
3GPP
Release 14 217 3GPP TS 23.018 V14.0.0 (2017-03)

Procedure in the MSC Wait_For_Setup_Response, Signals to/from the left
to complete an MT call Wait_For_Alerting are to/from the BSS;
are to/from the VLR
Release
Release From GMSC
transaction
CCBS_ICH_MSC_ CAMEL_
See TS 23.093 MT_GMSC_ See TS 23.078
Report_Failure
DISC6
No
User CCBS_ICH_MSC_
See TS 23.093
busy? Report_Failure
Yes
Set negative UUS_MSC_ UUS_MSC_

response: Check_ See TS 23.087 Check_ See TS 23.087
Busy subscriber UUS1_UUI UUS1_UUI
(UDUB)
Complete Release
Call Release To GMSC
transaction
negative
response
Abort
Result:= Result:=
Fail Aborted
Figure 70i: Procedure Complete_Call_In_MSC (sheet 9)
3GPP
Release 14 218 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call Answer are to/from the BSS;
are to/from the VLR
Release
From GMSC Release
transaction
UUS_MSC_
See TS 23.087 Check_
UUS1_UUI
Release
transaction
No CAMEL_
User
busy?
DISC6
Yes
UUS_ICH_ UUS_MSC_
See TS 23.087 Check_ Check_ See TS 23.087
Forwarding UUS1_UUI
No
Result=
Release To GMSC
Pass?
Yes
UUS_MSC_ Set negative

See TS 23.087 Check_ response:
UUS1_UUI Busy subscriber
(UDUB)
Complete
1 Call Abort
negative
response
Result:= Result:=
Fail Aborted
Figure 70j: Procedure Complete_Call_In_MSC (sheet 10)
3GPP
Release 14 219 3GPP TS 23.018 V14.0.0 (2017-03)

to complete an MT call Wait_For_ Wait_For_Alerting,
on request from the VLR Answer Wait_For_Answer

are to/from the BSS; Int_Release_
CD Request From gsmSSF
signals to/from the right Call
are to/from the VLR
UUS_ICH_
Check_ See TS 23.087 Abort
Forwarding
No
Result= Release
Pass? transaction
Yes
CD_UUS_ Handling_
See TS 23.072 See TS 23.072 Release To GMSC
Interaction CD_MSC
Complete
Call Result:=
2
negative Aborted
response
Result:=
Fail
Wait_For_
Answer
User to User to
User User
UUS_MSC_ UUS_MSC_
See TS 23.087 Check_UUS2_ Check_UUS2_ See TS 23.087
UUI_to_NW UUI_to_MS
Wait_For_
Answer
Figure 70k: Procedure Complete_Call_In_MSC (sheet 11)
3GPP
Release 14 220 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Set_CLIP_Info_MSC CAINF_M1(1)

to determine the CLIP
information to be sent to the MS

Initiate
CLIP_MAF002
handling
of CLIP
Wait_For_
CLIP_Info
Release Continue
From BSS call Release From GMSC
transaction
handling
Figure 71: Procedure Set_CLIP_Info_MSC
Figure 72: Void
3GPP
Release 14 221 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Establish_Terminating_TCH_If_Required ETTCIR1(1)

Procedure in the terminating VMSC Signals to/from the left
to establish a Traffic Channel are to/from the BSS;
if one has not been established signals to/from the right
for this call are to/from the GMSC
TCH_Check
Result
Fail Use existing Allocate Reject Aborted
Result:= Result:= Allocate Result:= Result:=

Fail Pass channel Rejected Aborted
Wait_For_
Allocation_
Complete
Release Allocation Allocation

Release
transaction failure complete
Release Release
transaction transaction

Fail Pass Aborted
Figure 73: Procedure Establish_Terminating_TCH_If_Required
3GPP
Release 14 222 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_AoC_MT_MSC AOCMT_M1(1)

to handle AoC signalling are to/from the BSS;
towards the MS for an MT call signals from the right
are from the AoC timer function.
Yes
AoC(I)
provisioned?
No
Set No
AoC(C)
charging provisioned?
parameters
Yes
Send Set
Charging charging
Parameters parameters
Send
Charging
Parameters
Start AoC
acknowledgment
timer
Wait_For_
Charging_
Parameters_
Ack
Charging Release AoC

Parameters connection acknowledgment
ack timer expired
Release
transaction
Result:= Result:=
Pass Fail
Figure 74: Procedure Handle_AoC_MT_MSC
3GPP
Release 14 223 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Set_COL_Presentation_Indicator_MSC COIND_M1(1)

to determine the COL
presentation indicator value

Initiate
COLR_MAF041
handling
of COLR
Wait_For_
COLR_Info
Release Continue
From BSS call Release From GMSC
transaction
handling
Figure 75: Procedure Set_COL_Presentation_Indicator MSC
3GPP
Release 14 224 3GPP TS 23.018 V14.0.0 (2017-03)
7.3.2.1 Process ICH_VLR

Sheet 1: if the MSRN received in the Send Info For Incoming Call is not allocated or there is no IMSI record for the
IMSI identified by the MSRN or the MS is marked as "Subscriber data dormant" (e.g. due to super-charger), this is
treated as an unknown MSRN.
Sheet 1: MT roaming retry is not triggered for an incoming call that arrives at the old VLR after the receipt of the MAP
Send Identification request from the new VLR but before the receipt of the MAP Cancel Location from the HLR. The
"Cancel Location received" flag enables to differentiate for a subscriber whose subscriber data is dormant whether a
Cancel Location has been received or not from the HLR.
Sheet 1: the procedure CAMEL_ICH_VLR is specific to CAMEL phase 3 or later; it is specified in

3GPP TS 23.078 [12]. If the VLR does not support CAMEL phase 3 or later, processing continues from the possible
call of the procedure CCBS_ICH_Set_CCBS_Call_Indicator. .
Sheet 1: If the MSRN is not allocated, "GMSC supports MT Roaming Retry" takes "No" exit.
Sheet 1: If no IMSI record is found, the " Subscriber data dormant" check takes the "False" exit.
Sheet 1: A VLR not supporting the flag "Subscriber data dormant" shall behave as if the flag is set to false.
Sheet 1: the procedure CCBS_ICH_Set_CCBS_Call_Indicator is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 1: the VLR derives the basic service required for the call according to the rules defined in 3GPP TS 29.007 [30].
Sheet 1, sheet 2, sheet 5: the procedure CCBS_ICH_VLR_Report_Failure is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 1, sheet 3: the procedure CCBS_ICH_Report_Not_Reachable is specific to CCBS; it is specified in

3GPP TS 23.093 [23].
Sheet 2: this process communicates with the matching instance of the process PRN_VLR, which is linked by the
MSRN.
- there is an association established for the MS between the MSC/VLR and the SGSN.
Sheet 3: the test "NDUB?" takes the "Yes" exit if the Page MS negative response or the Search for MS negative
response had the value Busy Subscriber (NDUB).
Sheet 3: the procedure Get_CW_Subscription_Info_VLR is specific to Call Waiting. If the VLR does not support Call
Waiting, processing continues from the "No" exit of the test "CW available?".
Sheet 3: the procedure Get_CW_Subscription_Info_Multicall_VLR is specific to Multicall; it is specified in

3GPP TS 23.135 [34]. If the VLR does not support both Multicall and Call Waiting, processing continues from the
"No" exit of the test "CW available?".
Sheet 3: the VLR uses the basic service returned in the Page MS negative response or the Search for MS negative
response Busy Subscriber (More calls possible) to determine whether call waiting is available.
Sheet 3: the procedure Get_LI_Subscription_Info_MT_VLR is specific to CLIP and COLR. If the VLR supports
neither CLIP nor COLR, the procedure call is omitted.
Sheet3: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC; it is specified in subclause 7.1.2.15.
Sheet 3 sheet 6: the procedure CLI_ICH_VLR_Add_CLI is specific to Enhanced CLI Handling. It is specified in
3GPP TS 23.081 [14].
Sheet 3: the procedure CCBS_ICH_Handle_NDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. If the
VLR does not support CCBS, processing continues from the "Forward" exit of the test "Result".
3GPP
Release 14 225 3GPP TS 23.018 V14.0.0 (2017-03)
Sheet 3: the procedure Process_Access_Request_VLR is specified in subclause 7.1.2.2.
Sheet 3: the output signal Page MS towards the SGSN includes the Location area identity parameter.
Sheet 3: if the VLR does not support CUG, handling continues from the "No" exit of the test "CUG info present?".
Sheet 3: the "MT Roaming Forwarding Supported" check takes the "Yes" exit if both the MSC and the VLR support
that feature. If both the MT Roaming Retry and the MT Roaming Forwarding procedures are supported, and if the
conditions for using these procedures are met, the VLR can decide based on operator policy which procedure to follow.
Sheet 3: MT Roaming Forwarding is possible towards the new VLR if the conditions defined in subclause 5.2.3 are
fulfilled. If so, the old VLR sends a MAP Provide Roaming Number request to the new VLR whose address was
received in the MAP Cancel Location message or the MAP Send Identification message. In addition to the requirements
specified in subclause 10.2.3 of 3GPP TS 29.002 [29], the MAP Provide Roaming Number request shall not include the
"OR Interrogation" parameter when being sent as part of the MT Roaming Forwarding call after successful retrieval of
routeing information procedure.
Sheet 4, sheet 6: the procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later; it is specified in
Sheet 5, sheet 6: the procedure CD_Authorization is specific to Call Deflection, it is specified in 3GPP TS 23.072 [11].
If the VLR does not support Call Deflection, processing continues from the "Yes" exit of the test "Result=Aborted?".
Sheet 5, sheet 6: the procedure CCBS_ICH_Handle_UDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 6: the test "NDUB?" is executed only if the VLR supports CCBS. If the VLR does not support CCBS, processing
continues from connector 5.
Sheet 7: the procedure CCBS_ICH_Set_CCBS_Target is specific to CCBS; it is specified in 3GPP TS 23.093 [23].
Sheet 7: the procedure Handle_CFNRc is specified in subclause 7.2.2.11.
Sheet 8: the procedure Forward_CUG_Check is specific to CUG; it is specified in subclause 7.2.2.6. If the VLR does
not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?".
Sheet 8: the procedures CAMEL_O_CSI_Check_VLR, and CAMEL_D_CSI_Check_VLR are specific to CAMEL

phase 3 or later; they are specified in 3GPP TS 23.078 [12].
7.3.2.2 Void
7.3.2.3 Procedure Search_For_MS_VLR

The test "Paging via SGSN possible" takes the "yes" exit if:
- the VLR configuration requires paging via the SGSN during VLR restoration.
The output signal Page MS towards the SGSN omits the Location area identity parameter. It is sent to every SGSN to
which the VLR is connected.
7.3.2.4 Procedure Get_CW_Subscription_Info_VLR

The VMSC may abort the transaction with the VLR while a response is awaited from the process MAF013. The
message is saved for processing after return from the procedure.
7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR

The VMSC may abort the transaction with the VLR while a response is awaited from the process CLIP_MAF001 or the
process COLR_MAF040. The message is saved for processing after return from the procedure.
3GPP
Release 14 226 3GPP TS 23.018 V14.0.0 (2017-03)
7.3.2.6 Procedure Handle_CFB

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

7.3.2.7 Procedure Handle_CFNRy

The test "Normal call" refers to the value of the indicator returned by the process MAF009.
3GPP
Release 14 227 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e s s IC H _ V L R IC H _ V L R 1 (8 )
P ro c e s s in V L R B to S ig n a ls t o / f r o m t h e l e f t
h a n d le a r e q u e s t fo r in fo r m a ti o n a r e t o / f r o m th e M S C
f o r a n in c o m i n g ( M T ) c a l l
I d le
R e le a s e S e n d In f o
M SRN F o r In c o m in g
C a ll
No
R e le a s e M SRN
M SRN know n?
Yes
M T R o a m in g
R e t r y s u p p o r te d
I d le CAM EL_ S e e T S 2 3 .0 7 8
IC H _ V L R
No Yes
N o G M S C s u p p o r ts
Yes M T R o a m in g R e try
R e s u lt =
F a il ?
T ru e
No no Yes
S u b s c r ib e r
C C B S _ IC H _ d a ta d o rm a n t
S e e T S 2 3 .0 9 3 " C a n c e l L o c a tio n re c e iv e d "
S e t_ C C B S _ f la g = t r u e
C a l l_ I n d i c a t o r F a ls e
yes
D a ta F a ls e S e t n e g a t iv e
I d le c o n fi r m e d re s p o n s e :
by HLR U n a ll o c a te d s e t M T R o a m in g
T ru e R o a m in g N u m b e r R e try In d ic a t o r
D e r i v e r e q u ir e d S e t n e g a t iv e
S e e T S 2 9 .0 0 7 re s p o n s e :
b a s ic s e r v ic e S e n d In f o
S y s te m
F o r In c o m in g
F a il u r e
C a ll A c k
T ru e
S u b s c r ib e r C C B S _ IC H _ V L R _
d a ta d o rm a n t R e p o r t _ F a ilu r e
I d le
F a ls e
Yes
IM S I S e e T S 2 3 .0 9 3
d e ta c h e d ?
No
No R o a m in g
in L A
a ll o w e d ?
C C B S _ IC H _ S e n d In f o
R e p o rt_ N o t_ F o r In c o m in g
R e a c h a b le C a ll n e g a tiv e
re s p o n s e
1 10 I d le
Figure 76a: Process ICH_VLR (sheet 1)
3GPP
Release 14 228 3GPP TS 23.018 V14.0.0 (2017-03)
Process ICH_VLR ICH_VLR2(8)

10
Process in VLRB to
handle a request for information
for an incoming (MT) call Signals to the left
are to the VMSC;
Prepaging are to/from the process PRN_VLR.
supported?
Yes No
True
PAR
pending
False
Wait_For_
PAR_Completed
PAR
completed
True
PAR
successful
False
Call
arrived
True
Fatal PAR
11
error
False
Set negative No Yes

Location
response: area ID
Impossible call known?
completion
No
CCBS_ICH_VLR_ Paging via
See TS 23.093
Report_Failure SGSN possible?
Yes
Send Info Set Paging

For Incoming via SGSN
Call negative possible
response
Search_For_ Page type=

Idle Page MS
MS_VLR circuit-switched call
Yes
Result=
Pass?
No
Yes
Result=
Fail?
No
CCBS_ICH_VLR_
See TS 23.093
Report_Failure
Wait_For_
Idle 2 Access_
Request
Figure 76b: Process ICH_VLR (sheet 2)
3GPP
Release 14 229 3GPP TS 23.018 V14.0.0 (2017-03)
P ro c e s s IC H _ V L R IC H _ V L R 3 (8 )
P ro c e s s in V L R B to S i g n a ls t o / f r o m th e le f t
h a n d le a r e q u e s t f o r i n f o r m a t io n a r e t o / fr o m th e V M S C .
f o r a n in c o m in g ( M T ) c a l l
W a it _ F o r _
A ccess_
R eque st
P age M S P age M S
n e g a tiv e 2 A b ort
v ia S G S N
re s p o n s e
L o c a t io n Yes
C a n c e l le d ?
12 13 P age M S To SG SN
No
A bsent
s u b s c r ib e r ? W a it _ F o r _
Yes 12 S e e T S 2 3 .0 9 3 C C B S _ IC H _ V L R _
No A ccess_ R e p o r t _ F a ilu r e
C C B S _ IC H _
S e e T S 2 3 .0 9 3 R eque st
R e p o r t_ N o t_
R e a c h a b le
No
B usy M T R o a m i n g F o r w a r d in g Id le
s u b s c r ib e r ? S u p p o rte d ? Yes
Yes No
M T R o a m i n g F o r w a r d in g
3 1
No p o s s i b l e to w a r d n e w V L R ?
Yes yes
M T R o a m i n g R e tr y
NDUB?
S u p p o rte d ?
No
No
Yes
M u lt ic a ll P ro v id e R o a m in g
s u p p o rte d N um b er To ne w VL R
G M S C s u p p o r ts
in V L R ? ( M T R F I n d ic a to r )
M T R o a m in g
R e try No
No Yes Yes
W a it _ F o r _
fro m n e w V L R
G e t_ C W _ G e t_ C W _ M SRN
s e t M T R o a m in g
S u b s c r ip t io n _ S u b s c r ip t io n _ I n f o _ R e t r y In d i c a t o r
In f o _ V L R M u l ti c a l l _ V L R
No S e n d In fo P ro v id e R o a m in g
CW P ro v id e R o a m in g
a v a i la b le ? F o r In c o m in g N u m b e r n e g a ti v e N um b er Ack
C a ll A c k re s p o n s e
Yes
9
s e t M T R o a m in g
Id le
F o r w a r d i n g I n d ic a to r
G e t _ L I_ C C B S _ IC H _
S u b s c r ip t io n _ S e e T S 2 3 .0 9 3
H a n d le _ N D U B S e n d In fo
In f o _ M T _ V L R i n c l u d in g M S R N F o r In c o m in g
C a ll A c k
G e t_ A o C _ R e le a s e
S u b s c r ip t io n _ R e s u lt 13
In f o _ V L R Id le
F o rw a rd
4 8 5
Figure 76c: Process ICH_VLR (sheet 3)
3GPP
Release 14 230 3GPP TS 23.018 V14.0.0 (2017-03)
Process ICH_VLR Wait_For_

ICH_VLR4(8)
Access_
Process in VLRB to Request Signals to/from the left
handle a request for information are to/from the VMSC.
for an incoming (MT) call
Process
Access
Request
Process_
Access_
Request_VLR
No
Result=
11
Pass?
Yes
Yes
CUG
info
present?
Translate CUG
No As defined in CCBS_ICH_VLR_
interlock See TS 23.093
TS 23.085 Report_Failure
to index
Yes
Success? Idle
CAMEL_CHECK No
_SII2_CDTI
Yes
Result =
Pass?
No
CFNRy No
A&O?
Yes
Provide
NRCT 3
value
Get_LI_
Subscription_
Info_MT_VLR
Get_AoC_ Set negative

Subscription_ response:
Info_VLR System failure
CLI_ICH_VLR_ CCBS_ICH_VLR_
See TS 23.081 See TS 23.093
Add_CLI Report_Failure
Send Info
Complete For Incoming
Call Call negative
response
Wait_For_
Complete_Call_ Idle
Result
Figure 76d: Process ICH_VLR (sheet 4)
3GPP
Release 14 231 3GPP TS 23.018 V14.0.0 (2017-03)

Process in VLRB to Wait_for_ Signals to/from the left
handle a request for information Complete_Call are to/from the VMSC.
for an incoming (MT) call Result
Complete
Complete
Abort Call negative
Call ack
response
Yes
Busy
Idle
subscriber?
No
CCBS_ICH_
See TS 23.093
Handle_UDUB
Yes
Absent
subscriber?
No
Yes
Radio
congestion?
No
Yes
No
subscriber
reply?
No
CD_ CCBS_ICH_VLR_
See TS 23.072 See TS 23.093
Authorization Report_Failure
No
Result=
Aborted?
Yes
No Set negative
Result= response: 6 1 5
Fail? Impossible call
completion
Yes
Send Info
For Incoming
Call negative
response
7 Idle
Figure 76e: Process ICH_VLR (sheet 5)
3GPP
Release 14 232 3GPP TS 23.018 V14.0.0 (2017-03)

4
Process in VLRB to Signals to/from the left
handle a request for information are to/from the VMSC.
CAMEL_CHECK
See TS 23.078
_SII2_CDTI
Yez
Result =
Pass?
No
No CFNRy
A&O?
Yea
Set NRCT
CLI_ICH_VLR_
See TS 23.081
Add_CLI
Process
Call
Waiting
Wait_For_
PCW_Result
Process Process
Call Abort Call Waiting
Waiting ack negative
response
Yes
Busy
Idle
subscriber?
No
Yes
No
subscriber NDUB?
reply?
Yes
No No
CD_
See TS 23.072 9
Authorization
No
Result=
Aborted?
Yes
No Set negative
Result= response: CCBS_ICH_
See TS 23.093
Fail? Impossible call Handle_UDUB
completion
Yes Send Info

For Incoming
Call negative
response
7 Idle 6 5
Figure 76f: Process ICH_VLR (sheet 6)
3GPP
Release 14 233 3GPP TS 23.018 V14.0.0 (2017-03)

Process in VLRB to Signals to the left
handle a request for information are to the VMSC 1
Handle_CFNRc
Yes
Result=
Fail?
Handle_CFB
Set negative No
response:
Forwarding
Violation
Result=
Yes Forward?
Result= No
Fail? Yes
No Set negative Set negative

response: response:
Forwarding Absent
Violation Subscriber 7
8 Handle_CFNRy
No Yes
Result= Result=
Forward? Fail?
Yes No
CCBS_ICH_ Set negative

Set_CCBS_ See TS 23.093 response:
Target Forwarding No
Violation Result=
Forward?
Set negative Set negative Yes

response: response:
Busy No Subscriber
Subscriber Reply
CCBS_ICH_ Send Info

Set_CCBS_ See TS 23.093 For Incoming
Target Call negative
response
7 Idle 7
Figure 76g: Process ICH_VLR (sheet 7)
3GPP
Release 14 234 3GPP TS 23.018 V14.0.0 (2017-03)

Process in VLRB to Signals to the left
handle a request for information 7 are to the VMSC.
Forward_
CUG_Check
No
Result=
Call
allowed?
Yes
Set negative
Set result:
response:
Forward
CUG reject
Set
forwarding
information
CAMEL_
O_CSI_ See TS 23.078
CHECK_VLR
CAMEL_
D_CSI_ See TS 23.078
CHECK_VLR
Send Info Send Info

For Incoming For Incoming
Call ack Call negative
response
Idle Idle
Figure 76h: Process ICH_VLR (sheet 8)
Figure 77: Void
3GPP
Release 14 235 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Search_For_MS_VLR SRCH_V1(1)

to search for an MS
(i.e. page in all location areas)

are to/from the MSC No
Paging via
SGSN possible?
Yes
Set paging
via SGSN
possible
Search Page type=

For MS Circuit-switched call
PgA is sent if PgA supported and received

Wait_For_
Search_Result
Search Search Search for MS

For MS Abort
For MS ack via SGSN
negative
response
Update
Location To SGSN Page MS
Area ID

Pass Fail Aborted
Wait_For_
Search_Result
Figure 78: Procedure Search_For_MS_VLR
3GPP
Release 14 236 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Get_CW_Subscription_Info_VLR CWI_VLR1(1)

information for the
Call Waiting service

initiate
MAF013
handling
of CW
Wait_For_
CW_Info
process
From MSC Abort call
waiting
Figure 79: Procedure Get_CW_Subscription_Info_VLR
3GPP
Release 14 237 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Get_LI_Subscription_Info_MT_VLR GLI_MTV1(1)

information for the CLIP
& COLR line identification
services for an MT call
Initiate
handling To process CLIP_MAF001
of CLIP
Wait_For_
CLIP_Info
Continue
From MSC Abort call From process CLIP_MAF001
handling
Initiate
handling To process COLR_MAF040
of COLR
Wait_For_
COLR_Info
Continue
From MSC Abort call From process COLR_MAF040
handling
Figure 80: Procedure Get_LI_Subscription_Info_MT_VLR
3GPP
Release 14 238 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_CFB H_CFB1(1)

on Busy

MAF008
CAMEL_CHECL
See TS 23.078
_SII2_CDTI
No
Result =
Pass?
Yes
initiate
handling
of CFB
Wait_For_
CFB_Result
continue
call
handling
Yes
Error?
No
Yes
Normal
call
busy?
No

Fail Forward Busy
Figure 81: Procedure Handle_CFB
3GPP
Release 14 239 3GPP TS 23.018 V14.0.0 (2017-03)
Procedure Handle_CFNRy H_CFNRy1(1)

on No subscriber Reply

initiate
MAF009
handling
of CFNRy
Wait_For_
CFNRy_Result
continue
call
handling
Yes
Error?
No
No
Normal
call?
Yes

Fail No reply Forward
Figure 82: Procedure Handle_CFNRy
3GPP
Release 14 240 3GPP TS 23.018 V14.0.0 (2017-03)
7.4 Subs_FSM
7.4.1.1 Process Subs_FSM

One instance of the process Subs_FSM runs for each subscriber who is involved in at least one call. It monitors the state
of any ongoing calls for that subscriber. The individual call control processes OCH_MSC and ICH_MSC submit
supplementary service requests received from the MS to the process Subs_FSM, which then responds appropriately.
The process Subs_FSM interacts with the processes OCH_MSC and ICH_MSC as specified in subclauses 7.1.1 and
7.3.1.
Sheet 5, sheet 6, sheet 7, sheet 8, sheet 9, sheet 11, sheet 12, sheet 15: processing on this page will occur only if the
VMSC supports HOLD.
Sheet 8: the procdure Handle_MPTY is specific to MPTY; it is specified in 3GPP TS 23.084 [17].
Sheet 8: the procedure Handle_ECT_Active is specific to ECT; it is specified in 3GPP TS 23.091 [22].
Sheet 10: processing on this page will occur only if the VMSC supports Multicall.
Sheet 12: the procedure Handle_ECT_Alerting is specific to ECT; it is specified in 3GPP TS 23.091 [22].
Sheet 13, sheet 14: processing on this page will occur only if the VMSC supports both HOLD and Multicall.
3GPP
Release 14 241 3GPP TS 23.018 V14.0.0 (2017-03)
7.4.1.1.1 Macro Check_Ongoing_Calls
7.4.1.1.2 Macro Update_Non_Speech_Calls_Status
7.4.1.1.3 Macro Increment_Call_Counter
7.4.1.1.4 Macro Decrement_Call_Counter
Process Subs_FSM SFSM1(18)

Process in the serving MSC Signals to/from the left are
to control the call states on a per to/from either process OCH_MSC
subscriber basis. or process ICH_MSC
Speech_Call_Cnt:=0
Non_Speech_Call_Cnt:=0
Speech_CallA:=Null
Speech_CallB:=Null
Non_Speech_Calls:=Null
OG_Call_Alerting:=False
Idle
Non speech Speech

TCH TCH
required required
Non_Speech_ Speech_CallA:=
Calls:=Setup Setup
Allocate
TCH
Setup_
Pending
Figure 83a: Process Subs_FSM (sheet 1)
3GPP
Release 14 242 3GPP TS 23.018 V14.0.0 (2017-03)

Setup_
Pending
Call Call setup

established failed
Increment_ Speech_CallA:=Null
Call_Counter Speech_CallB:=Null
Non_Speech_Calls:=Null
Non_Speech Speech
Non_Speech_ Speech_CallA:=
Calls:=Active Active
Idle_
Data_Call_ Call_Active Idle
Active
Figure 83b: Process Subs_FSM (sheet 2)
3GPP
Release 14 243 3GPP TS 23.018 V14.0.0 (2017-03)

Idle_
Data_Call_
Active
Non speech Speech Call

TCH TCH cleared
required required
Non-Speech_ Speech_CallA:=
Calls:=Setup Setup
Allocate
TCH
Data_Call_
Active_
Setup_Pending
Call Call Call setup

cleared established failed
Decrement_ Increment_ Decrement_

Call_Counter Call_Counter Call_Counter
Speech, Non_Speech Speech,

Non_Speech Speech Non_Speech
Check_ Speech_CallA:= Non_Speech_ Check_

Ongoing_Calls Active Calls:=Active Ongoing_Calls
Calls_Ongoing Calls_Ongoing
No_Calls_Ongoing No_Calls_Ongoing
Data_Call_ Setup_ Idle_

Active_ Call_Active Data_Call_ Idle
Pending
Setup_Pending Active
Figure 83c: Process Subs_FSM (sheet 3)
3GPP
Release 14 244 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Active
Hold Non speech Speech Call

request TCH TCH cleared
required required
Hold Allocate TCH already Decrement_

ack TCH allocated Call_Counter
Speech, Non_Speech
Check_
Ongoing_Calls
Calls_Ongoing No_Calls_Ongoing
Yes Ongoing
speech
call?
No
Speech_CallA:= Non_Speech_ Speech_CallA:= Speech_CallA:=Null

Held Calls:=Setup Null Speech_CallB:=Null
Call_Active_ Idle_
Call_Held Data_Call_ Call_Active Data_Call_ Idle
Setup_Pending Active
Figure 83d: Process Subs_FSM (sheet 4)
3GPP
Release 14 245 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held
Call Call Retrieve

From held call
cleared cleared request
Non- No
Speech_Call_Cnt:= Non_Speech_Call_Cnt:=
Speech_Call_Cnt - 1 Non_Speech_Call_Cnt - 1 speech call
using TCH?
Yes
Speech_CallA:= Update_Non_ Retrieve Retrieve

Null Speech_ reject ack
Calls_Status
Yes Non_Speech_ Speech_CallA:=

Call_Count Active
= 0?
No
Idle_
Idle Data_Call_ Call_Held Call_Active
Active
Figure 83e: Process Subs_FSM (sheet 5)
3GPP
Release 14 246 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held
Speech Non speech

TCH TCH
required required
Non- No
speech call
using TCH?
Yes
TCH Allocate TCH

available TCH available
Speech_CallB:= Non_Speech_
Setup Calls:=Setup
Call_Held_ Call_Held_
Setup_Pending Data_Call_
Setup_Pending
Figure 83f: Process Subs_FSM (sheet 6)
3GPP
Release 14 247 3GPP TS 23.018 V14.0.0 (2017-03)

subscriber basis. or process ICH_MSC; signals from
the right are internal MSC signals
Call_Held_ unless marked otherwise
Call_Active
Retrieve Non speech Hold Speech

request TCH request TCH
required required
Retrieve Allocate TCH already

reject TCH allocated
Non_Speech_ Handle_ Se 3G TS
Calls:=Setup Timed_Call_ 23.083
Swap
Call_Held_ Call_Held_Call_ Call_Held_

Call_Active Active_Data_Call Call_Active
Setup_Pending
Retr_req, T_Expr Hold_Clr

Result?
Active_Clr
Call_Held_
Call_Held Call_Active
Call_Active
Figure 83g: Process Subs_FSM (sheet 7)
3GPP
Release 14 248 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_
Call_Active
MPTY ECT
request request
MPTY ECT
Yes No No Yes
Handle_ MPTY ECT Handle_ECT_

See TS 23.084 See TS 23.091
MPTY reject reject Active
Fail
Call_Held_
Result Result
Call_Active
Pass
End End_Active End_Held Fail
No Yes
Non-speech
call ongoing?
Idle_ Call_Held_ Call_Held_

Idle Data_Call_ Call_Active Call_Held Idle
Call_Active Call_Active
Active
Figure 83h: Process Subs_FSM (sheet 8)
3GPP
Release 14 249 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_
Call_Active
Call Call
From held call
cleared cleared
Speech_Call_Cnt:= Decrement_
Speech_Call_Cnt - 1 Call_Counter
Non_Speech
Speech
Speech_CallA:=Active Update_Non_ Speech_CallB:=

Speech_CallB:=Null Speech_ Null
Calls_Status
Call_Held_
Call_Active Call_Held
Call_Active
Figure 83i: Process Subs_FSM (sheet 9)
3GPP
Release 14 250 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Active_
Data_Call_
Setup_Pending
Call Call setup Call Retrieve Hold

established failed cleared request request
Non_Speech_Call_Cnt:= Retrieve Hold

Non_Speech_Call_Cnt + 1 reject ack
Non_Speech_ Update_Non_ Decrement_

Calls:=Active Speech_ Call_Count
Calls_Status
Speech
Non_Speech
Yes
Non-speech
call ongoing?
No
Speech_CallA:= Update_Non_
Null Speech_
Calls_Status
Data_Call_ Call_Active_ Call_Held_

Call_Active Active_ Setup_Pending Data_Call_ Setup_Pending
Setup_Pending Setup_Pending
Figure 83j: Process Subs_FSM (sheet 10)
3GPP
Release 14 251 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_
Setup_Pending
Call setup Call Call

failed established cleared
OG_Call_ OG_Call_ OG_Call_

Alerting:=False Alerting:=False Alerting:=False
Yes
Speech Increment_ Decrement_
call? Call_Count Call_Count
No Non_Speech Speech Speech,

Non_Speech
Non- No
Non_Speech_ Speech_CallB:= Check_
speech call Calls:=Active Active Ongoing_Calls
ongoin?
Yes Calls_Ongoing
No_Calls_Ongoing
Yes
Speech_CallB:= Non_Speech_ Non_Speech_ Speech Speech_CallA:=Setup
Null Calls:=Active Calls:=Null call ongoing? Speech_CallB:=Null
No
Call_Held_ Call_Held_ Data_Call_

Call_Held Active_ Setup_Pending
Call_Active Setup_Pending
Setup_Pending
Figure 83k: Process Subs_FSM (sheet 11)
3GPP
Release 14 252 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_
Setup_Pending
Alerting in Hold Retrieve ECT

progress request request request
Hold Retrieve
reject reject ECT
supported?
Yes No
Handle_ECT_ ECT
See TS 23.091
Alerting reject
Pass Fail
Result
OG_Call_ OG_Call_
Alerting:=True Alerting:=False
Call_Held_ Call_Held_ Call_Held_

Idle
Setup_Pending Setup_Pending Setup_Pending
Figure 84l: Process Subs_FSM (sheet 12)
3GPP
Release 14 253 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_Call_
Active_Data_Call_
Setup_Pending
Call Call setup Hold Retrieve

established failed request request
Non_Speech_Call_Cnt:= See 3G TS Handle_ Retrieve

Non_Speech_Call_Cnt + 1 23.083 Timed_Call_ reject
Swap
Non_Speech_ Update_Non_ Call_Held_Call_

Calls:=Active Speech_ Active_Data_Call_
Calls_Status Setup_Pending
Retr_req, T_Expr Hold_Clr

Result
Active_Clr
Call_Held_ Call_Held_Call_ Call_Held_ Call_Active_

Call_Active Active_Data_Call_ Setup_Pending Data_Call_
Setup_Pending Setup_Pending
Figure 84m: Process Subs_FSM (sheet 13)
3GPP
Release 14 254 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_Call_
Active_Data_Call_
Setup_Pending
Call Call Call

From held call From active call
cleared cleared cleared
Speech_Call_Cnt:= Non_Speech_Call_Cnt:= Speech_Call_Cnt:=

Speech_Call_Cnt - 1 Non_Speech_Call_Cnt - 1 Speech_Call_Cnt - 1
Yes No
Speech_CallA:=Active Speech Speech_CallA:=Held
Speech_CallB:=Null call ongoing? Speech_CallB:=Null
Speech_CallB:=
Null
Call_Active_ Call_Held_Call_ Call_Held_

Data_Call_ Active_Data_Call Setup_Pending Data_Call_
Setup_Pending Setup_Pending Setup_Pending
Figure 84n: Process Subs_FSM (sheet 14)
3GPP
Release 14 255 3GPP TS 23.018 V14.0.0 (2017-03)

Call_Held_
Data_Call_Setup_
Pending
Call setup Call Call Hold Retrieve

failed established cleared request request
Update_Non_ Non- No
Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt:= Hold
Speech_ Non_Speech_Call_Cnt + 1 Non_Speech_Call_Cnt - 1 reject speech call
Calls_Status using TCH?
Yes
Update_Non_ Retrieve Retrieve

Speech_ reject ack
Calls_Status
Yes
Speech call Speech_CallA:=
ongoing? Active
No
Speech_CallA:=
Null
Data_Call_Setup_ Call_Held_ Call_Active_

Call_Held Data_Call_Setup_ Data_Call_
Pending
Pending Setup_Pending
Figure 84o: Process Subs_FSM (sheet 14)
3GPP
Release 14 256 3GPP TS 23.018 V14.0.0 (2017-03)

Request
call status
Call status
Figure 84p: Process Subs_FSM (sheet 14)
3GPP
Release 14 257 3GPP TS 23.018 V14.0.0 (2017-03)

Except for the following states:

* "Call Held Call Active"
"Call Held Setup Pending"
ECT
request
ECT
reject
Figure 84q: Process Subs_FSM (sheet 14)
3GPP
Release 14 258 3GPP TS 23.018 V14.0.0 (2017-03)

Except for the following state:

*
"Call Held Call Active"
MPTY
request
MPTY
reject
Figure 84r: Process Subs_FSM (sheet 14)
3GPP
Release 14 259 3GPP TS 23.018 V14.0.0 (2017-03)
Macrodefinition Check_Ongoing_Calls COC1(1)

Macro to check if there are any speech
or non-speech calls remaining (and also
update the Non_Speech_Calls status variable.
Non_ >=1
Speech_Call_
Cnt
Non_Speech_
Calls:=Null
>=1
Speech_
Call_Cnt
No_Calls_ Calls_
Ongoing Ongoing
Figure 85: Macro Check_Ongoing_Calls
3GPP
Release 14 260 3GPP TS 23.018 V14.0.0 (2017-03)
Macrodefinition Update_Non_Speech_Calls_Status Upd_NSC_Stat1(1)

Macro to update the Non_Speeh_Calls
variable depending on whether there are
any non-speech calls ongoing or not.
Yes No
Non-speech
call ongoing?
Non_Speech_ Non_Speech_
Calls:=Active Calls:=Null
Figure 86: Macro Update_Non_Speech_Calls_Status
3GPP
Release 14 261 3GPP TS 23.018 V14.0.0 (2017-03)
Macrodefinition Increment_Call_Counter Inc_Call_Cnt1(1)

Macro to increment the correct counter
depedning on the type of the current call.
No Yes
Speech
call?
Non_Speech_Call_Cnt:= Speech_Call_Cnt:=
Non_Speech_Call_Cnt + 1 Speech_Call_Cnt + 1
Non_
Speech
Speech
Figure 87: Macro Increment_Call_Counter
3GPP
Release 14 262 3GPP TS 23.018 V14.0.0 (2017-03)
Macrodefinition Decrement_Call_Counter Inc_Call_Cnt1(1)

Macro to decrement the correct counter
depedning on the type of the current call.
No Yes
Speech
call?
Non_Speech_Call_Cnt:= Speech_Call_Cnt:=
Non_Speech_Call_Cnt - 1 Speech_Call_Cnt - 1
Non_
Speech
Speech
Figure 88: Macro Decrement_Call_Counter
3GPP
Release 14 263 3GPP TS 23.018 V14.0.0 (2017-03)
7.5 TO call
7.5.1 Functional requirements of inter-connecting MSC
7.5.1.1 Process TO_MSC

Sheet 1: the procedure CAMEL_TOC_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 "Pass" exit of the test "Result=?". The procedure call formal
parameter First or NotFirst indicates whether the procedure was called earlier in the same call.
Sheet 1, sheet 4: the procedure CAMEL_TOC_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 trunk triggering, processing continues from the "Pass" exit
of the test "Result?". The procedure call formal parameter First or NotFirst indicates whether the procedure was
called earlier in the same call.

Sheet 1, sheet 2, sheet 3: 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 4: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1; it is specified in

3GPP TS 23.078 [12].
Sheet 1, sheet2, sheet 4: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later; it is
Sheet 1, sheet 7: 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 1, sheet 2: The variable Return_Place indicates at which detection point the additional digit collection is.
Sheet 1, sheet 2: The inter-digit timer is a MSC internal timer to wait for additional dialling from the incoming side.
At the expiry of the timer, the MSC/gsmSSF may report digits to the gsmSCF (if the event detection point is armed).
This timer is used for the SDL modelling purposes only and it may not present the actual implementations.
Sheet 2: Number_of_Digits is the Collected_Info specific reporting criterion. The gsmSCF specifies the criterion. The
process CS_gsmSSF sends the parameter to the TO_MSC process.
Sheet 2: ST digit is the ISUP value for a digit indicating that the Called Party Number is complete.
Sheet 3: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later; they
Sheet 3: 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 3: the procedure UUS_MSC_Clear_UUS is specific to UUS; it is specified in 3GPP TS 23.087 [20]. Commented [DM1]: Is this relevant for TO calls? It is to check
any CFNRy and UUS interaction, but cant decide if CFNRy would
ever be appliable at this point?
Sheet 3: 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"
Sheet 4: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later; it is specified in

3GPP TS 23.078 [12].
CAMEL.
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].
3GPP
Release 14 264 3GPP TS 23.018 V14.0.0 (2017-03)
the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=CAMEL handling?".
the MSC does not support CAMEL, processing continues from the "No" exit of the test "Result=Reconnect?" .
CAMEL.
Sheet 6: after the process TO_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.
Sheet 7: the process CAMEL_MT_CF_LEG2_MSC is specific to CAMEL phase 4 or later; it is specified in

3GPP TS 23.078 [12].
3GPP
Release 14 265 3GPP TS 23.018 V14.0.0 (2017-03)
Process TO_MSC TOMSC1(7)

to handle are to/from the originating switch;
trunk originated call. signals to/from the right
are to/from the destination exchange or
Idle MT_GMSC or ICH_MSC process depending on
the called number.
Initial
Address
CAMEL_TOC_
MSC_INIT See TS 23.078
B (First)
4 Result?
Leg1
More_Digits Fail ELSE
The duration is a MSC
Pass
specific and/or interface
Leg1_status specific value Start
C
:= Set-up Inter_Digit_timer
CAMEL_TOC_
Dialled_Services See TS 23.078
CAMEL_TOC_ Return_Place :=
See TS 23.078 (First)
LEG1_MSC Init
(Leg1_status)
Result?
Idle Leg1_only Abort Fail Wait_For_SAM
CAMEL_
4 See TS 23.078
OCH_MSC1
No
Result=
Idle
Reconnect?
Yes
1 2 Release
Pass More_Digits
MOBILE_NUMBER_ Start
See TS 23.066 PORTABILITY_ Inter_Digit_timer
IN_OQoD
CAMEL_Store_
See TS 23.078 Destination_
Address
(False, False)
MSC_Coord_ Return_Place :=
setup DialledServices
Wait_For_
Wait_For_SAM Idle
ACM
Figure 7.5.1a: Process TO_MSC (sheet 1)
3GPP
Release 14 266 3GPP TS 23.018 V14.0.0 (2017-03)

to handle Wait_For_SAM are to/from the originating switch;
MT_GMSC or ICH_MSC process depending on
the called number.
SAM Inter_Digit_timer from SELF
Stop
Inter_Digit_timer
(Dialled number length >=

Number_of_Digits)
OR Yes
(ST digit received) CAMEL_Store_
See TS 23.078 Destination_
No
Address
Start (False, False)
Inter_Digit_timer
Wait_For_SAM
Digits are waited based on timer

for modelling purposes.
Once timer expires, new digits are Return_Place?
reported to gsmSCF. Dialled_Services
There may be vendor specic differences
in this issue. Init
CAMEL_TOC_ CAMEL_TOC_
See TS 23.078 MSC_INIT Dialled_Services See TS 23.078
(NotFirst) (NotFirst)
B C
Figure 7.5.1b: Process TO_MSC (sheet 2)
3GPP
Release 14 267 3GPP TS 23.018 V14.0.0 (2017-03)

to handle ACM are to/from the originating switch;
Address the called number.
Complete
Connect
CAMEL_
See TS 23.078 SAM
Start_TNRy
UUS_MSC_ CAMEL_Store_
See TS 23.087 Destination_ See TS 23.078
Clear_UUS
Address
(False, False)
CAMEL_CF_
See TS 23.078
MSC_ALERTING
Answer Result? Else SAM
Pass
Address Address
Complete Complete
-
Wait_For_
Answer
Answer
CAMEL_ UUS_MSC_
See TS 23.078 See TS 23.087
Stop_TNRy Clear_UUS
CAMEL_CF_ CAMEL_CF_
See TS 23.078 See TS 23.078
MSC_ANSWER MSC_ANSWER
Result? Else Else Result?
Pass
Pass
Reconnect
UUS_MSC_ Release
See TS 23.087 Result?
Clear_UUS
Fail
Answer 2 Release Connect
A Idle A
Figure 7.5.1c: Process TO_MSC (sheet 3)
3GPP
Release 14 268 3GPP TS 23.018 V14.0.0 (2017-03)

to handle are to/from the originating switch;
trunk originated call. Wait_For_ACM, signals to/from the right
Wait_For_Answer are to/from the destination exchange or
the called number.
Release Release From gsmSSF Int_ReleaseCall
CAMEL trunk CAMEL trunk

triggering supported? triggering supported?
No Yes No Yes
Yes
Release cause=
No

See TS 23.078
No
Result=
Reconnect?
Yes
CAMEL_
See TS 23.078 Release
Stop_TNRy
Release
call
resources
Idle
Figure 7.5.1d: Process TO_MSC (sheet 4)
3GPP
Release 14 269 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC Wait_For _
to handle Answer Signals to/from the left
trunk originated call.
are to/from the originating switch;
TNRy the called number.
Internal
expired
3 Release
CAMEL_OCH_
See TS 23.078 2
MSC2
Release Reconnect
Result?
Fail
CAMEL_TOC_
Release See TS 23.078 Dialled_Services
(First)
Abort Pass
Result?
Fail
Release CAMEL_
call See TS 23.078 1
OCH_MSC1
resources
Yes
Result=
Idle
Reconnect?
No
Release 2
Idle
Figure 7.5.1e: Process TO_MSC (sheet 5)
3GPP
Release 14 270 3GPP TS 23.018 V14.0.0 (2017-03)

to handle Clear are to/from the originating switch;
the called number.
Release Release Int_ReleaseCall From gsmSSF
See TS 23.078 See TS 23.078 Release
MSC_DISC1 MSC_DISC2
Result= Result=
CAMEL Yes Yes CAMEL
Handling? Handling?
No No
Yes
Result=
Reconnect?
No
Release
call
resources
Idle
* *
- -
Figure 7.5.1f: Process TO_MSC (sheet 6)
3GPP
Release 14 271 3GPP TS 23.018 V14.0.0 (2017-03)

Process in the MSC
to handle
trunk originated call.
A
No
Yes
CAMEL_MT_
See TS 23.078
CF_LEG2_MSC
When this process calls

CAMEL_MF_RECONNECT_MSC
the formal call parameters "BOR" and Leg1_status Wait_For_
"Forwarding" in := Active Clear
CAMEL_Store_Destination_Address
shall be "False".
CAMEL_TOC_
See TS 23.078 LEG1_MSC
(Leg1_status)
Idle
Figure 7.5.1g: Process TO_MSC (sheet 7)
8 Contents of messages
This clause specifies the content of each message shown in clauses 5 and 7, except for the following messages, which
are not specific to call handling:
On the D interface (VLR-HLR):
- Abort;
- Activate Trace Mode;
- Authentication Failure Report;
3GPP
Release 14 272 3GPP TS 23.018 V14.0.0 (2017-03)
- Insert Subscriber Data;
- Send Authentication Info;
- Send Authentication Info ack;
- Send Authentication Info negative response;
In the tables which follow, information elements are shown as mandatory (M), conditional (C) or optional (O). A
mandatory information element shall always be present. A conditional information element shall be present if certain
conditions are fulfilled; if those conditions are not fulfilled it shall be absent. An optional element may be present or
absent, at the discretion of the application at the sending entity.
Some messages which are defined in this clause are used for other services or features. The specifications (referred to
below as "derived specifications") for those services or features may simply refer to the present document for the
definition of the message; in this case the requirements for the presence of each information element are as defined in
this clause. If the specification for a service or feature requires information elements in a message additional to those
specified in this clause, the requirements for the presence of the additional information elements are specified in the
relevant specification. If the specification for a service or feature has different requirements for the presence of an
information element in a message which is specified in this clause, then the following principles apply:
- If the information element is shown as mandatory in this clause, it shall always be present.
- If the information element is shown as conditional or optional in this clause, but mandatory in the derived
specification, it shall always be present in the context of the service or feature defined in the derived
specification.
- If the information element is shown as conditional or optional in this clause, and the conditions in the derived
specification require the information element to be present, it shall be present even if the conditions in this clause
do not require it to be present.
8.1 Messages on the B interface (MSC-VLR)

8.1.1 Abort
The following information element is required:
Information element name Required Description

Abort reason M Indicates the reason for the procedure being aborted.
8.1.2 Authenticate
The following information elements are required for authentication of a UMTS UE:

RAND(I) M Random number challenge to be sent to the MS
(3GPP TS 33.102 [32])
AUTN(I) M Authentication token to be sent to the MS (3GPP TS 33.102 [32])
3GPP
Release 14 273 3GPP TS 23.018 V14.0.0 (2017-03)
The following information elements are required for authentication of a GSM MS:

RAND M Random number challenge to be sent to the MS
(3GPP TS 43.020 [1])
CKSN M Cipher key sequence number to be sent to the MS
(3GPP TS 43.020 [1])
8.1.3 Authenticate ack

The following information element is required for authentication of a UMTS UE:

RES(I) M Result returned by the MS (3GPP TS 33.102 [32])
The following information element is required for authentication of a GSM MS:

SRES M Signature result returned by the MS (3GPP TS 43.020 [1])
8.1.4 Authenticate negative response

The negative response information element can take the following value:
- wrong network signature.
8.1.5 Call arrived

This message contains no information elements.
8.1.6 Check IMEI

8.1.7 Check IMEI ack


Equipment status M Indicates whether the ME is black-listed, grey-listed or white-listed
8.1.8 Check IMEI negative response

The negative response information element can take the following values:
- System failure;
- Unknown equipment.
3GPP
Release 14 274 3GPP TS 23.018 V14.0.0 (2017-03)
8.1.9 Complete Call

The following information elements are required:

MSISDN C MSISDN of the MS for which the Complete Call is sent. Shall be
present for an ordinary MO call, for an MT call and for an
emergency call when the MS is registered in the VLR; otherwise
shall be absent.
IMEI C IMEI of the mobile for which the Complete Call is sent. Shall be
present for an emergency call when the mobile is identified only by
its IMEI; otherwise shall be absent.
Category C Category of the MS for which the Complete Call is sent. Shall be
present for an ordinary MO call and for an emergency call when
the MS is registered in the VLR; otherwise shall be absent.
PLMN bearer capability C Shall be present for an MT call according to the rules defined in
3GPP TS 29.007 [30].
ISDN bearer capability C Shall be present for an MT call if it was received in the Provide
Roaming Number; otherwise shall be absent.
ISDN low layer compatibility C Shall be present for an MT call if it was received in the Provide
ISDN high layer compatibility C Shall be present for an MT call if it was received in the Provide
CLIP provision C Indicates that CLIP is provisioned. Shall be present for an MT call
if CLIP is provisioned; otherwise shall be absent.
CLIR override provision C Indicates that the CLIR override subscription option of CLIP is
provisioned. Shall be present for an MT call if CLIP is provisioned
with the CLIR override subscription option and the MS is
registered in the HPLMN country; otherwise shall be absent.
CLIR provision C Indicates that CLIR is provisioned. Shall be present for an MO call
if CLIR is provisioned; otherwise shall be absent.
CLIR mode C Indicates the mode in which CLIR is provisioned: permanent,
temporary (default presentation allowed) or temporary (default
presentation restricted). Shall be present for an MO call if CLIR is
provisioned; otherwise shall be absent.
COLP provision C Indicates that COLP is provisioned. Shall be present for an MO
call if COLP is provisioned; otherwise shall be absent.
COLR override provision C Indicates that the COLR override subscription option of COLP is
provisioned. Shall be present for an MO call if COLP is provisioned
with the COLR override subscription option and the MS is
registered in the HPLMN country; otherwise shall be absent.
COLR provision C Indicates that COLR is provisioned. Shall be present for an MT call
if COLR is provisioned; otherwise shall be absent.
No Reply Condition Timer C Value of timer to be used to determine the No subscriber reply
condition. Shall be present for an MT call if the Call Forwarding on
No Reply service is active and operative; otherwise shall be
absent.
CUG index C For the definition of this IE, see 3GPP TS 23.085 [18]. May be
present (as a network operator option) for an ordinary MO call if
the call is a CUG call; shall be present for an MT call if the call is a
CUG call; otherwise shall be absent.
CUG interlock C For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be
present for an ordinary MO call if the call is a CUG call; otherwise
shall be absent.
CUG outgoing access C For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be
present for an ordinary MO call if the call is a CUG call with
outgoing access; otherwise shall be absent.
Advice of Charge provision C Indicates whether Advice of Charge (Information) or Advice of
Charge (Charging) is provisioned. Shall be present for an ordinary
MO call or an MT call if Advice of Charge is provisioned; otherwise
shall be absent.
Alerting Pattern C Shall be present for an MT call if it was received in the Provide
Roaming Number and if the feature is supported by the MSC/VLR;
otherwise shall be absent.
3GPP
Release 14 275 3GPP TS 23.018 V14.0.0 (2017-03)

NAEA preferred Carrier Id O The preferred carrier identity identifying the carrier to be used to
route the interexchange call if the call requires routing via an
interexchange carrier. This parameter may be included at the
discretion of the VLR operator.
8.1.10 Complete Call ack

8.1.11 Complete Call negative response

- Absent subscriber;
- Busy subscriber;
- No subscriber reply;
- Radio congestion.
8.1.12 Forward New TMSI


TMSI M TMSI to be sent to the MS.
8.1.13 Forward New TMSI ack

8.1.14 Forward New TMSI negative response

- TMSI reallocation failure.
8.1.15 Obtain Subscriber Info


IMSI M IMSI of the MS for which information is required.
Subscriber state requested C Indicates that the VLR requires state information for the MS. Shall
be present if state information is required; otherwise shall be
absent.
8.1.16 Obtain Subscriber Info ack

3GPP
Release 14 276 3GPP TS 23.018 V14.0.0 (2017-03)

Subscriber state C Indicates whether the MS is busy (i.e. engaged on a circuit-
switched call) or assumed idle. Shall be present if the VLR
requested state information; otherwise shall be absent.
8.1.17 Page MS

IMSI M IMSI of the MS to be paged.
Location area ID M Location area in which the MS is to be paged.
Page type M Indicates whether the paging is for a circuit-switched call, MT SMS
delivery, SS activity or Active Location Retrieval.
Requested information C Indicates the information requested by the VLR one or more of:
- Location;
- MS classmark;
- IMEI.
Shall be present if the Page type is Active Information Retrieval;
Paging via SGSN possible C Indicates that paging via the SGSN is possible. Shall be present if
the VLR determines that the MS can be paged via the SGSN;
TMSI O TMSI to be broadcast to identify the MS.
Call Priority O This parameter indicates the eMLPP priority of the call (see 3GPP
TS 23.067 [39]). This parameter should be present if the VLR
supports the eMLPP feature and if the Call Priority was received in
the MAP_PROVIDE_ROAMING_NUMBER request or in the MAP
PROVIDE_SUBSCRIBER_INFO request.
8.1.18 Page MS ack


Location area ID M Location area in which the MS responded to the page.
Serving cell ID M Identity of the cell in which the served subscriber is located. Shall
be present if the MS uses GSM radio access; otherwise shall be
absent.
Service area ID C Service area identity of the cell in which the served subscriber is
located. Shall be present if the MS uses UMTS radio access;
MS classmark M MS classmark 2 as defined in 3GPP TS 24.008 [26].
IMEI (with software version) C IMEISV as defined in 3GPP TS 23.003 [5]. Shall be present if the
IMEI was requested in the Page MS message and the MSC
retrieved it from the MS; otherwise shall be absent.
8.1.19 Page MS negative response

- Busy subscriber (More calls possible);
3GPP
Release 14 277 3GPP TS 23.018 V14.0.0 (2017-03)
- Busy subscriber (NDUB);
- System failure;
- Unknown location area ID.
The Page MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for
the established call.
8.1.20 Page MS via SGSN


eMLPP priority O Circuit-switched paging priority.
Channel type O Type of channel required for the call.
8.1.21 Process Access Request


CM service type M Indicates the type of access required: normal MO call, emergency
call or page response. Other values (short message service and
SS request) defined for this IE are not considered in the present
document.
Access connection status M Indicates whether or not the connection to the MS is ciphered and
whether or not it is authenticated.
Current location area ID M Identity of the location area from which the access request was
received.
Service area ID C Identity of the service area (for UMTS access) in use by the served
subscriber. Shall be present for UMTS access; otherwise shall be
absent.
Serving cell ID C Identity of the cell (for GSM access) in use by the served
subscriber. Shall be present for GSM access; otherwise shall be
absent.
IMSI C IMSI of the MS requesting the access. For normal MO call or page
response, one of IMSI or TMSI shall be present. For emergency
call, one of IMSI, TMSI or IMEI shall be present.
TMSI C TMSI of the MS requesting the access. For normal MO call or
page response, one of IMSI or TMSI shall be present. For
emergency call, one of IMSI, TMSI or IMEI shall be present.
IMEI C IMEI of the MS requesting the access. For normal MO call or page
response, one of IMSI or TMSI shall be present. For emergency
call, one of IMSI, TMSI or IMEI shall be present.
CKSN C Cipher key sequence number of the MS requesting the access.
Shall be present if TMSI is present; otherwise shall be absent.
CSG Id C Identifier of the closed subscriber group. Shall be present if the
serving cell is a CSG cell or a hybrid cell.
Cell Access Mode C Indicates that the serving cell operates in Hybrid Access mode.
Shall be present if the serving cell is a Hybrid cell.
8.1.22 Process Access Request ack

3GPP
Release 14 278 3GPP TS 23.018 V14.0.0 (2017-03)

IMSI C IMSI of the MS requesting the access. For normal MO call or page
response, shall be present. For emergency call, one of IMSI or
IMEI shall be present.
IMEI C IMEI of the MS requesting the access. For normal MO call or page
response, shall be absent. For emergency call, one of IMSI or
IMEI shall be present.
MSISDN O MSISDN of the MS requesting the access.
CSG Membership Status C Indicates the Membership status of the UE to a particular CSG.
Shall be present if the serving cell is a Hybrid cell.
8.1.23 Process Access Request negative response

- Roaming not allowed;
- System failure;
- Unidentified subscriber;
- Illegal equipment;
- Illegal subscriber;
- Not authorized for this CSG.
8.1.24 Process Call Waiting


MSISDN M MSISDN of the MS for which the Process Call Waiting is sent.
PLMN bearer capability C Shall be present according to the rules defined in
3GPP TS 29.007 [30].
ISDN bearer capability C Shall be present if it was received in the Provide Roaming Number
for the waiting call; otherwise shall be absent.
ISDN low layer compatibility C Shall be present if it was received in the Provide Roaming Number
ISDN high layer compatibility C Shall be present if it was received in the Provide Roaming Number
CLIP provision C Indicates that CLIP is provisioned. Shall be present if CLIP is
CLIR override provision C Indicates that the CLIR override subscription option of CLIP is
provisioned. Shall be present if CLIP is provisioned with the CLIR
override subscription option and the MS is registered in the
HPLMN country; otherwise shall be absent.
COLR provision C Indicates that COLR is provisioned. Shall be present if COLR is
No Reply Condition Timer C Value of timer to be used to determine the No subscriber reply
condition. Shall be present if the Call Forwarding on No Reply
service is active and operative; otherwise shall be absent.
CUG index C For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be
present if the waiting call is a CUG call; otherwise shall be absent.
Advice of Charge provision C Indicates whether Advice of Charge (Information) or Advice of
Charge (Charging) is provisioned. Shall be present if Advice of
Charge is provisioned; otherwise shall be absent.
3GPP
Release 14 279 3GPP TS 23.018 V14.0.0 (2017-03)
8.1.25 Process Call Waiting ack

8.1.26 Process Call Waiting negative response

- Busy subscriber (UDUB);
- No subscriber reply.
8.1.27 Provide IMEI

8.1.28 Provide IMEI ack


IMEI M IMEISV (as defined in 3GPP TS 23.003 [5]) of the ME involved in
the access request.
8.1.29 Provide IMSI

8.1.30 Provide IMSI ack


IMSI M IMSI of the MS involved in the access request.
8.1.31 Radio connection released

8.1.32 Search For MS

3GPP
Release 14 280 3GPP TS 23.018 V14.0.0 (2017-03)

IMSI M IMSI of the MS to be paged in all location areas.
Page type M Indicates whether the paging is for a circuit-switched call, MT SMS
delivery, SS activity or Active Location Retrieval.
Requested information C Indicates the information requested by the VLR one or more of:
- Location;
- MS classmark;
- IMEI.
Shall be present if the Page type is Active Information Retrieval;
Paging via SGSN possible C Indicates that paging via the SGSN is possible. Shall be present if
the VLR determines that the MS can be paged via the SGSN;
Paging area O May be present if the Paging type is circuit switched call, if the
Paging Area function is supported and if the paging area is
available; otherwise it shall be absent. It indicates the set of
Location Areas in which the MS is to be paged on the A interface if
Location area ID is not known in VLR.
TS 23.067 [39]). This parameter should be present if the VLR
supports the eMLPP feature and if the Call Priority was received in
the MAP_PROVIDE_ROAMING_NUMBER request or in the MAP
PROVIDE_SUBSCRIBER_INFO request.
8.1.33 Search For MS ack


Location area ID M Location area in which the MS responded to the page.
Serving cell ID C Identity of the cell in which the served subscriber is located. Shall
be present if the MS uses GSM radio access; otherwise shall be
absent.
Service area ID C Service area identity of the cell in which the served subscriber is
located. Shall be present if the MS uses UMTS radio access;
MS classmark M MS classmark 2 as defined in 3GPP TS 24.008 [26].
IMEI was requested in the Page MS message and the MSC
retrieved it from the MS; otherwise shall be absent.
8.1.34 Search For MS negative response

- Busy subscriber (More calls possible);
- System failure.
The Search For MS negative response Busy subscriber (More calls possible) also indicates the basic service which
applies for the established call.
3GPP
Release 14 281 3GPP TS 23.018 V14.0.0 (2017-03)
8.1.35 Search for MS via SGSN


eMLPP priority O Circuit-switched paging priority.
Channel type O Type of channel required for the call.
8.1.36 Send Info For Incoming Call


MSRN M Mobile Station Roaming Number received in the IAM.
Bearer service C Bearer service required for the MT call. Shall be present if the
MSC was able to derive a bearer service from ISDN BC/LLC/HLC
information received in the IAM; otherwise shall be absent.
Teleservice C Teleservice required for the MT call. Shall be present if the MSC
was able to derive a teleservice from ISDN BC/LLC/HLC
information received in the IAM; otherwise shall be absent.
Dialled number C Number dialled by the calling subscriber. Shall be present if it was
received in the IAM; otherwise shall be absent.
Number of forwarding C Number of times the incoming call has already been forwarded.
Shall be present if it was received in the IAM; otherwise shall be
absent.
present if it was received in the IAM; otherwise shall be absent.
present if it was received in the IAM; otherwise shall be absent.
MT Roaming Forwarding C Indication that the MSC supports the MT Roaming Forwarding
Supported feature. Shall be present if the MSC supports that feature,
3GPP
Release 14 282 3GPP TS 23.018 V14.0.0 (2017-03)
8.1.37 Send Info For Incoming Call ack


IMSI M IMSI of the B subscriber.
Forwarded-to number C E.164 number of the C subscriber. Shall be present if the call is to
be forwarded other than for MT roaming retry reason.
Forwarding reason C Indication of why the call has been forwarded (on call deflection,
on mobile subscriber busy, on mobile subscriber not reachable or
on no subscriber reply). Shall be present if the call is to be
forwarded other than for MT roaming retry reason.
Notification to calling party C Indication of whether the calling party is to be notified that the call
has been forwarded. Shall be present if the call is to be forwarded
other than for MT roaming retry reason.
Notification to forwarding party C Indication of whether the forwarding party is to be notified that the
call has been forwarded. Shall be present if the call is to be
forwarded on mobile subscriber busy or on no subscriber reply;
Forwarded-to subaddress C Subaddress of the C subscriber (see 3GPP TS 23.003 [5]). Shall
be present if a forwarded-to subaddress is stored in the VLR in
association with the forwarded-to number; otherwise shall be
absent.
Redirecting presentation C Indication of whether the MSISDN of B subscriber shall be
presented to the C subscriber. Shall be present if the call is to be
forwarded, otherwise shall be absent.
MSISDN C E.164 number which identifies the B subscriber. It will be used to
create the redirecting number presented to the C subscriber. Shall
be present if the call is to be forwarded, otherwise shall be absent.
present if the VLR has determined that the forwarded call is to be
treated as a CUG call in accordance with the rules in 3GPP
TS 23.085 [18], otherwise shall be absent.
present if the VLR has determined that the forwarded call is to be
treated as a CUG call with outgoing access in accordance with the
rules in 3GPP TS 23.085 [18], otherwise shall be absent.
route the interexchange call if the forwarded call requires routing
via an interexchange carrier. This parameter may be included at
the discretion of the VLR operator.
MT Roaming Retry Indicator C Indication that the call is forwarded for MT roaming retry. All other
forwarding parameters are not relevant if this IE is present.
MT Roaming Forwarding Indicator C Indication that the call is forwarded for MT Roaming Forwarding.
All other forwarding parameters are not relevant if this IE is
present.
MSRN for MT Roaming C Mobile Station Roaming Number received in the MAP PROVIDE
Forwarding ROAMING NUMBER response from the new VLR. Shall be
present if the MT Roaming Forwarding Indicator is present,
8.1.38 Send Info For Incoming Call negative response

- Busy subscriber;
- CUG reject (Called party SS interaction violation);
- Forwarding violation;
3GPP
Release 14 283 3GPP TS 23.018 V14.0.0 (2017-03)
- Impossible call completion;
- No subscriber reply;
- System failure;
- Unallocated roaming number;
8.1.39 Send Info For Outgoing Call


Called number M E.164 number of the call destination.
Bearer service C Bearer service required for the MO call, derived from the PLMN
bearer capability information received in the set-up request from
the MS. One of bearer service or teleservice shall be present.
Teleservice C Teleservice required for the MO call, derived from the PLMN
bearer capability information received in the set-up request from
the MS or from the emergency set-up request from the MS. One of
bearer service or teleservice shall be present.
CUG index C For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be
present if it was received in the set-up request from the MS.
Suppress preferential CUG C For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be
Suppress CUG outgoing access C For the definition of this IE, see 3GPP TS 23.085 [18]. Shall be
8.1.40 Send Info For Outgoing Call negative response

- Bearer service not provisioned;
- Call barred (Operator determined barring);
- Call barred (Supplementary service barring);
- CUG reject (Inconsistent access information - index incompatible with basic service);
- CUG reject (Inconsistent access information - no CUG selected);
- CUG reject (Outgoing calls barred within the CUG);
- CUG reject (Unknown CUG index);
- Teleservice not provisioned.
8.1.40A Send UESBI-Iu to Access Network


IMEI (with software version) C IMEISV as defined in 3GPP TS 23.003 [5].
3GPP
Release 14 284 3GPP TS 23.018 V14.0.0 (2017-03)
8.1.41 Start security procedures

The following information elements are required for a UMTS connection:

CK M Ciphering key to be used to cipher communication over the radio
link (see 3GPP TS 33.102 [32]).
IK M Integrity key to be used to verify the integrity of messages
transferred over the radio link (see 3GPP TS 33.102 [32]).
The following information elements are required for a GSM connection:

Ciphering mode M Indicates whether ciphering of the radio connection is required,
and if so which ciphering algorithm is to be used.
Kc C Ciphering key to be used if ciphering of the radio connection is
required. Shall be present if the ciphering mode indicates that
ciphering of the radio connection is required, otherwise shall be
absent.
8.1.42 Trace subscriber activity


Trace reference M Reference number to be included with tracing reports which the
VMSC sends to the OMC
Trace type M For the definition of this IE, see 3GPP TS 52.008 [3]
8.1.43 Use existing TMSI

8.1.44 Release MSRN


MSRN M Mobile Station Roaming Number received with the message
RELEASE RESOURCES.
8.2 Messages on the C interface (MSC-HLR)

8.2.1 Send Routeing Info
3GPP
Release 14 285 3GPP TS 23.018 V14.0.0 (2017-03)

MSISDN M MSISDN of the B subscriber (see 3GPP TS 23.003 [5]).
Alerting Pattern C Shall be present if received in a Connect operation from the
gsmSCF; otherwise shall be absent.
present if the GMSC received it in the IAM and the GMSC
supports CUG, otherwise shall be absent.
present if the GMSC received it in the IAM and the GMSC
supports CUG, otherwise shall be absent.
Number of forwarding C Number of times the incoming call has already been forwarded.
Shall be present if it was received in the IAM; otherwise shall be
absent.
ISDN BC C ISDN bearer capability. Shall be present if the GMSC received it in
the IAM, otherwise shall be absent.
ISDN LLC C ISDN lower layer compatibility. Shall be present if the GMSC
received it in the IAM, otherwise shall be absent.
ISDN HLC C ISDN higher layer compatibility. Shall be present if the GMSC
received it in the IAM, otherwise shall be absent.
Pre-paging supported C Shall be present if the GMSC supports pre-paging, otherwise shall
be absent.
TS 23.067 [39]). This parameter should be present if the GMSC
supports the eMLPP feature and if the call is an eMLPP call. The
eMLPP priority levels A and B shall be mapped to the Call priority
level 0.
3GPP
Release 14 286 3GPP TS 23.018 V14.0.0 (2017-03)
8.2.2 Send Routeing Info ack


IMSI M IMSI of the B subscriber (see 3GPP TS 23.003 [5]).
Roaming number C E.164 number required to route the call to VMSCB (see 3GPP
TS 23.003 [5]). Shall be present if the HLR received it in the
Provide Roaming Number ack and the call is not subject to early
CF, otherwise shall be absent.
Forwarded-to number C E.164 number of the C subscriber. Shall be present if the HLR has
determined that the call is to be forwarded, otherwise shall be
absent.
Forwarded-to subaddress C Subaddress of the C subscriber (see 3GPP TS 23.003 [5]). Shall
be present if the HLR has determined that the call is to be
forwarded and a forwarded-to subaddress is stored in the HLR in
association with the forwarded-to number, otherwise shall be
absent.
Notification to calling party C Indication of whether the calling party is to be notified that the call
has been forwarded. Shall be present if the HLR has determined
that the call is to be forwarded, otherwise shall be absent.
Forwarding reason C Indication of why the call has been forwarded (unconditionally or
on mobile subscriber not reachable). Shall be present if the HLR
has determined that the call is to be forwarded, otherwise shall be
absent.
Redirecting presentation C Indication of whether the MSISDN of B subscriber shall be
presented to the C subscriber. Shall be present if the HLR has
determined that the call is to be forwarded, otherwise shall be
absent.
MSISDN C E.164 number which identifies the B subscriber (basic MSISDN). It
will be used to create the redirecting number presented to the C
subscriber. Shall be present if the HLR has determined that the
call is to be forwarded, otherwise shall be absent.
present if the HLR has determined that the call is to be treated as
a CUG call in accordance with the rules in 3GPP TS 23.085 [18],
present if the HLR has determined that the call is to be treated as
a CUG call with outgoing access in accordance with the rules in
3GPP TS 23.085 [18], otherwise shall be absent.
route the interexchange call if the call requires routing via an
interexchange carrier. This parameter may be included at the
discretion of the HLR operator.
8.2.3 Send Routeing Info negative response

- Bearer service not provisioned;
- Call barred (Operator determined barring);
- Call barred (Supplementary service barring);
- Call barred (Anonymous Call Rejection);
- CUG reject (Called party SS interaction violation);
- CUG reject (Incoming calls barred within CUG);
3GPP
Release 14 287 3GPP TS 23.018 V14.0.0 (2017-03)
- CUG reject (Requested basic service violates CUG constraints);
- CUG reject (Subscriber not member of CUG);
- Data missing;
- Facility not supported;
- Forwarding violation
- Number changed;
- System Failure;
- Teleservice not provisioned;
- Unexpected data value;
- Unknown subscriber.
8.3 Messages on the D interface (VLR-HLR)

8.3.1 Provide Roaming Number
3GPP
Release 14 288 3GPP TS 23.018 V14.0.0 (2017-03)

IMSI M IMSI of the B subscriber (see 3GPP TS 23.003 [5]).
MSC number M E.164 number which identifies VMSCB (see 3GPP TS 23.003 [5]).
MSISDN O E.164 number which identifies the B subscriber.
It shall be present if the following 3 conditions are all satisfied:
1. the MSISDN is different from the basic MSISDN;
2. the subscriber has VT-CSI stored in HLR;
3. the VLR has indicated support for CAMEL Phase 3 or later.
It may be present if the HLR requires it to be included in the call
data record.
LMSI C Local Mobile Subscriber Identity. Shall be present if the LMSI was
sent to HLRB at location updating.
PLMN bearer capability C Information to define the PLMN bearer capability required for the
call. For alternate speech/facsimile group 3 calls this information
element shall contain one PLMN bearer capability, as specified in
3GPP TS 29.007 [30]. May be present if the HLR can determine
the required PLMN bearer capability from ISDN compatibility
information received in the Send Routeing Info message, or from
the MSISDN if a multi-numbering scheme is used; otherwise shall
be absent. If the ISDN BC and ISDN LLC IEs are present, the
PLMN bearer capability IE shall be absent.
ISDN BC C ISDN bearer capability. May be present if the HLR received it in
the Send Routeing Info message, otherwise shall be absent. If the
PLMN bearer capability IE is present, the ISDN BC IE shall be
absent.
ISDN LLC C ISDN lower layer compatibility. May be present if the HLR received
it in the Send Routeing Info message, otherwise shall be absent. If
the PLMN bearer capability IE is present, the ISDN LLC IE shall be
absent.
ISDN HLC C ISDN higher layer compatibility. Shall be present if the HLR
received it in the Send Routeing Info message, otherwise shall be
absent.
Alerting Pattern C Shall be present if the HLR has determined an alerting category or
an alerting level for the MT call configuration; otherwise shall be
absent.
Pre-paging supported C Shall be present if the HLR has determined that pre-paging is
supported in the GMSC and the HLR, otherwise shall be absent.
Paging area O Shall be present if the Paging Area function is supported and if the
paging area is stored in HLR (see 3GPP TS 23.012); otherwise it
shall be absent. It indicates the set of Location Areas in which the
MS is to be paged on the A interface if Location area ID is not
known in VLR.
TS 23.067 [39]). This parameter should be present if the HLR
supports this parameter and if the Call Priority was received in the
MAP_SEND_ROUTING_INFORMATION request.
8.3.2 Provide Roaming Number ack


Roaming number M E.164 number required to route the call to VMSCB (see 3GPP
TS 23.003 [5]).
8.3.3 Provide Roaming Number negative response

3GPP
Release 14 289 3GPP TS 23.018 V14.0.0 (2017-03)
- Data missing;
- Facility not supported;
- No roaming number available;
- OR not allowed;
- Unexpected data value.
8.3.4 Provide Subscriber Info


IMSI M IMSI of the subscriber for whom information is requested (see
3GPP TS 23.003 [5]).
LMSI C Local Mobile Subscriber Identity. Shall be present if the LMSI was
sent to the HLR at location updating.
Requested information M Indicates which of the following information the HLR requires:
- location information;
- subscriber state;
- IMEI (with software version);
- MS classmark.
Active location retrieval requested C Indicates that the HLR requires active location retrieval. Shall be
absent if the requested information does not indicate that the HLR
requires location information.
Location Information in EPS C Indicates by its presence that Location Information in EPS is
Supported supported. Shall be absent if the requested information does not
indicate that the HLR requires location information.
Shall be present if the Provide Subscriber Info message is
triggered by the receipt of a Any Time Interrogation Request that
includes the same IE.
May be present otherwise, if the HLR requires location information
and the requesting entity in the HPLMN (e.g. gsmSCF) is known to
support Location Information in EPS.
Call Priority O Indicates the eMLPP priority of the call (see 3GPP TS 23.067
[39]). Should be present if the HLR supports this parameter and if
the Call Priority was received in the
MAP_SEND_ROUTING_INFORMATION request.
8.3.5 Provide Subscriber Info ack

3GPP
Release 14 290 3GPP TS 23.018 V14.0.0 (2017-03)

Location information C Information to define the location of the MS: see definition in
subclause 8.3.5.1. Shall be present if location information was
requested and is available; otherwise shall be absent.
Subscriber state C Indicates whether the MS is busy (i.e. engaged on a circuit-
switched call), network determined not reachable (IMSI detached
or roaming in a prohibited location area) or assumed idle. Shall be
present if subscriber state was requested; otherwise shall be
absent.
IMEI was requested, otherwise shall be absent.
MS classmark C MS classmark 2 as defined in 3GPP TS 24.008 [26]. Shall be
present if the MS classmark was requested, otherwise shall be
absent.
3GPP
Release 14 291 3GPP TS 23.018 V14.0.0 (2017-03)
8.3.5.1 Location information

The compound information element Location information consists of the following subordinate information elements:

Location number C For a definition of this information element, see
ITU-T Recommendation Q.763 [35]. Shall be present if the VLR
can derive it from the stored service area identity (for UMTS) or
cell global identity (for GSM) or location area identity; otherwise
shall be absent. The mapping from service area identity or cell ID
and location area to location number is network-specific and
outside the scope of the UMTS and GSM standards.
Service area ID C Service area identity of the cell in which the MS is currently in
radio contact or in which the MS was last in radio contact. Shall be
present if the MS uses UMTS radio access and the subscriber
record is marked as confirmed by radio contact; otherwise shall be
absent. See subclause 7.2.3.5.
Cell ID C Cell global identity of the cell in which the MS is currently in radio
contact or in which the MS was last in radio contact. Shall be
present if the MS uses GSM radio access and the subscriber
record is marked as confirmed by radio contact; otherwise shall be
Geographical information C For a definition of this information element, see
3GPP TS 23.032 [7] . Shall be present if the VLR can derive it
from the stored service area identity, cell global identity or location
area identity; otherwise shall be absent.
Geodetic information C This information element corresponds to the Calling Geodetic
Location defined in ITU-T Recommendation Q.763 [35]. Shall be
present if the VLR can derive it from the stored service area
identity, cell global identity or location area identity; otherwise shall
be absent.
VLR number O E.164 number which identifies the VLR (see 3GPP TS 23.003 [5]).
If the HLR receives it from the VLR it shall ignore it.
Age of location information C Measured in minutes. Shall be present if available in the
MSC/VLR; otherwise shall be absent.
Current Location Retrieved C Shall be present when location information was obtained after a
successful paging procedure for Active Location Retrieval.
E-UTRAN Cell ID C E-UTRAN cell global identity of the cell in which the MS is
currently in radio contact or in which the MS was last in radio
contact. Shall be present if the MS uses E-UTRAN radio access
and the subscriber record is marked as confirmed by radio contact;
otherwise shall be absent. See subclause 7.2.3.5.
Tracking area ID C Tracking area identity of the cell in which the MS is currently in
radio contact or in which the MS was last in radio contact. Shall be
present if the MS uses E-UTRAN radio access; otherwise shall be
8.3.6 Provide Subscriber Info negative response

- Data missing;
- Unexpected data value.
8.3.7 Restore Data

3GPP
Release 14 292 3GPP TS 23.018 V14.0.0 (2017-03)

IMSI M IMSI of the subscriber for whom data are to be restored (see
3GPP TS 23.003 [5]).
LMSI O LMSI of the subscriber for whom data are to be restored (see
3GPP TS 23.003 [5]). May be included if required by the
requesting VLR.
8.3.8 Restore Data ack


HLR number M E.164 number which identifies the HLR (see 3GPP TS 23.003 [5]).
MS not reachable flag C Indicates whether the VLR should notify the HLR when the MS
next establishes radio contact. Shall be present if the
corresponding indicator is set in the HLR record for the subscriber;
8.3.9 Restore Data negative response

- System failure;
- Unknown subscriber.
8.4 Messages on the F interface (MSC-EIR)

8.4.1 Check IMEI

IMEI M IMEI of the ME whose status is to be checked (see
3GPP TS 23.003 [5]).
8.4.2 Check IMEI ack


Equipment status M Indicates whether the ME is black-listed, grey-listed or white-listed
8.4.3 Check IMEI negative response

- Unknown equipment.
3GPP
Release 14 293 3GPP TS 23.018 V14.0.0 (2017-03)
8.5 Messages on the MSC internal interface

This interface can carry ISUP messages received from the process MT_GMSC or the process ICH_MSC and to be
forwarded to a destination exchange, and ISUP messages received from the destination exchange and to be forwarded to
the process MT_GMSC or the process ICH_MSC. In addition, it carries the following inter-process messages.
8.5.1 CF cancelled
8.5.2 Perform Call Forwarding


Forwarded-to number M E.164 number of the C subscriber.
OR call M Indicates whether the call which is to be forwarded was subject to
basic OR as specified in 3GPP TS 23.079 [13]
8.5.3 Perform Call Forwarding ack


Forwarded-to number M E.164 number of the C subscriber. Note: this number may be
different from the Forwarded-to number received in the Perform
Call Forwarding, as a result of CAMEL handling.
8.5.4 Perform Call Forwarding negative response

- Call forwarding failed.
8.6 Messages on the VLR internal interface

This interface carries messages between corresponding instances of the processes PRN_VLR and ICH_VLR. The
correlation between the process instances is done by the MSRN.
8.6.1 Call arrived

8.6.2 PAR completed

3GPP
Release 14 294 3GPP TS 23.018 V14.0.0 (2017-03)
8.7 Messages on the Gs interface

8.7.1 Page MS

eMLPP priority C Circuit-switched paging priority. Shall be present if it was received
in the Page MS via SGSN request or Search for MS via SGSN
request; otherwise shall be absent.
TMSI C TMSI to be broadcast to identify the MS. Shall be present if it was
received in the Page MS via SGSN request or Search for MS via
SGSN request; otherwise shall be absent.
Location area identity C Location area identity of the location area where the mobile is
registered, according to the subscriber data in the VLR. Shall be
present if the VLR can supply it; otherwise shall be absent.
Channel type C Type of channel required for the call. Shall be present if it was
received in the Page MS via SGSN request or Search for MS via
SGSN request; otherwise shall be absent.
8.7.2 Send MS information


Information requested M Information required for the specified MS.
8.7.3 Send MS information ack


Service area ID C Service area ID (for UMTS access) of the cell in which the MS last
established radio contact. Shall be present if the MS uses UMTS
access; otherwise shall be absent.
Cell ID C Cell ID (for GSM access) of the cell in which the MS last
established radio contact. Shall be present if the MS uses GSM
access; otherwise shall be absent.
Location information age M (note) Time in minutes since the MS last established a radio transaction
NOTE: Although they are optional in the protocol, these IEs are mandatory in this context.
8.7.4 Send MS information negative response

- No response from SGSN.
3GPP
Release 14 295 3GPP TS 23.018 V14.0.0 (2017-03)
8.8 Messages on the E interface (GMSC-VMSC)

8.8.1 Release Resources

MSRN M Mobile Station Roaming Number.
3GPP
Release 14 296 3GPP TS 23.018 V14.0.0 (2017-03)
Annex A (informative):
Handling of an IAM at an MSC
An MSC which receives an IAM from an originating exchange may react in three different ways:
- It acts as a transit exchange, i.e. it relays the IAM to a destination exchange determined by analysis of the called
party address, and thereafter relays other telephony signalling between the originating and destination exchange
until the connection is released. This behaviour is not specific to UMTS or GSM.
- It acts as a terminating exchange, i.e. it attempts to connect the call to an MS currently registered in the service
area of the MSC.
- It acts as a GMSC, i.e. it interrogates an HLR for information to route the call. If the HLR returns routeing
information, the MSC uses the routeing information from the HLR to construct an IAM, which it sends to a
destination exchange determined by analysis of the routeing information from the HLR.
Sheet 1: when the MSC co-ordinating setup procedure has decided whether the MSC is to act as a terminating VMSC, a
GMSC or a transit exchange, it forwards the IAM to an idle instance of the appropriate process.
3GPP
Release 14 297 3GPP TS 23.018 V14.0.0 (2017-03)
procedure MSC_coord_setup 1(1)

Procedure in the MSC to
handle an incoming IAM
and trigger the correct
application process
Called party address No

in MSRN range
Incoming IAM was
for this MSC?
routed with routeing
Yes number for MNP?
No
Yes
Recover No
HLR address
ported number derivable?
from IAM
Yes
To process Initial Initial To process Initial To destination

ICH_MSC Address Address MT_GMSC Address determined by
routeing tables
Figure 84a: Process MSC_Coord (sheet 1)
3GPP
Release 14 298 3GPP TS 23.018 V14.0.0 (2017-03)
Annex B (informative):
Change history
Change history
TSG CN# Spec CR Phase Version New Version Subject/Comment
Apr 1999 GSM 03.18 7.0.0 Transferred to 3GPP CN1
CN#03 23.018 3.0.0 Approved at CN#03
CN#04 23.018 001 3.0.0 3.1.0 Notification of Call Forwarding to the
gsmSCF
CN#05 23.018 002r4 3.1.0 3.2.0 Addition of the description for Pre-Paging
CN#05 23.018 006 3.1.0 3.2.0 Removal of TDP criteria from Resume Call
Handling
CN#05 23.018 007r1 3.1.0 3.2.0 GMSC CAMEL phases in Provide Roaming
Number
CN#05 23.018 023 3.1.0 3.2.0 Separation of success & failure cases for
OR of late call forwarding
CN#05 23.018 024 3.1.0 3.2.0 Notification of Call Forwarding to the
gsmSCF before activating call forwarding
process
CN#06 23.018 004r2 3.2.0 3.3.0 Introduction of the Super-Charger Concept
in TS 23.018
CN#06 23.018 027r3 3.2.0 3.3.0 Introduction of CAMEL Phase 3
CN#07 23.018 025r7 3.3.0 3.4.0 Addition of the description for Multicall
CN#07 23.018 026r2 3.3.0 3.4.0 Alternative solution for ALR
CN#07 23.018 030 3.3.0 3.4.0 Correction of the SDL diagrams for Pre-
paging
CN#07 23.018 032r1 3.3.0 3.4.0 Inclusion of D-CSI check in HLR/VLR
CN#07 23.018 033 3.3.0 3.4.0 Initialization of Backward Call indicator
CN#07 23.018 034 3.3.0 3.4.0 Correction of the result of the procedure
CAMEL_ICH_MSC_INIT
CN#07 23.018 037 3.3.0 3.4.0 Clarification of N-CSI in Core NW
CN#07 23.018 039r2 3.3.0 3.4.0 Replacement of references to GSM with
references to UMTS
CN#07 23.018 043r1 3.3.0 3.4.0 Clarification of NPDB error detection and
MNP specific call handling
CN#07 23.018 044 3.3.0 3.4.0 Setting the Destination Address for MO calls
CN#07 23.018 047 3.3.0 3.4.0 O-CSI and D-CSI checks for ORLCF calls
CN#07 23.018 048 3.3.0 3.4.0 Correction of CF Notification
CN#07 23.018 049 3.3.0 3.4.0 Introduction of Authentication Failure Report
CN#07 23.018 050r3 3.3.0 3.4.0 ISUP release cause value
CN#08 23.018 045r1 3.4.0 3.5.0 Correction of CAMEL Incoming Call
Handling
CN#08 23.018 051r4 3.4.0 3.5.0 Improvement of Active Retrieval of Location
Information procedure
CN#08 23.018 052r2 3.4.0 3.5.0 North American Service Provider Number
Portability impacts for MNP
CN#09 23.018 053 3.5.0 3.6.0 Correction of connector numbering in
process ICH_MSC
CN#09 23.018 054 3.5.0 3.6.0 Correction of the SDL diagram for Pre-
paging
CN#09 23.018 056 3.5.0 3.6.0 Correction to process ICH_VLR
CN#09 23.018 057r3 3.5.0 3.6.0 Handling of the Call Diversion Treatment
Indicator
CN#09 23.018 059r1 3.5.0 3.6.0 Modifications to procedure obtain routeing
address.
CN#09 23.018 060 3.5.0 3.6.0 Corrections to process ICH_VLR
CN#09 23.018 061r2 3.5.0 3.6.0 Update of CAMEL references
CN#09 23.018 063r1 3.5.0 3.6.0 Correction of procedure
Obtain_Routeing_Address for the reconnect
case
CN#09 23.018 055r4 R4 3.6.0 4.0.0 Inclusion of call hold in basic call handling.
CN#10 23.018 064 Rel-4 4.0.0 4.1.0 Tidying up of Process Subs_FSM and inter-
process signals
3GPP
Release 14 299 3GPP TS 23.018 V14.0.0 (2017-03)
Change history
CN#11 23.018 065 Rel-4 4.1.0 4.2.0 Incorporation of MPTY and ECT into the
Subs_FSM process
CN#11 23.018 067 Rel-4 4.1.0 4.2.0 Removal of CW descriptions
CN#11 23.018 069 Rel-4 4.1.0 4.2.0 Paging not via the SGSN correction
CN#12 23.018 074 Rel-4 4.2.0 4.3.0 Initialization of variable to monitor activation
of CSI's
CN#12 23.018 072 Rel-5 4.3.0 5.0.0 Handling of MultiCall in MPTY procedure
CN#13 23.018 077 Rel-5 5.0.0 5.1.0 Addition of missing process
Update_Location_VLR
CN#13 23.018 Rel-5 5.0.0 5.1.0 Editorial clean up
CN#14 23.018 081 Rel-5 5.1.0 5.2.0 Handling of Reconnect on Leg2 Disconnect
CN#14 23.018 091r2 Rel-5 5.1.0 5.2.0 Corrections in the ATI mechanism
description
CN#15 23.018 082r2 Rel-5 5.2.0 5.3.0 Introduction of CAMEL Phase 4
CN#15 23.018 088r2 Rel-5 5.2.0 5.3.0 Handling of CUG calls in non-supporting
networks
CN#15 23.018 093r1 Rel-5 5.2.0 5.3.0 MSISDN in Provide Roaming Number in
case of MSP
CN#15 23.018 098 Rel-5 5.2.0 5.3.0 Correction on the Active Location Retrieval
description
CN#15 23.018 100r1 Rel-5 5.2.0 5.3.0 Transferring the MS classmark & IMEI to the
gsmSCF
CN#17 23.018 109r1 Rel-5 5.3.0 5.4.0 Determining the basic service for MT calls
CN#17 23.018 110 Rel-5 5.3.0 5.4.0 Minor corrections to Process ICH_MSC
CN#17 23.018 111 Rel-5 5.3.0 5.4.0 Setting of Leg1_Status variable
CN#18 23.018 112r1 Rel-5 5.4.0 5.5.0 Clarification of requirements for the
presence of IEs in messages
CN#19 23.018 118 Rel-5 5.5.0 5.6.0 Correction in the ATI mechanism description
CN#20 23.018 115r2 Rel-5 5.6.0 5.7.0 Stopping No_Answer timer in the case of
forwarding notification
CN#20 23.018 122 Rel-5 5.6.0 5.7.0 Release Result from
CAMEL_MT_GMSC_Notify_CF
CN#20 23.018 124 Rel-5 5.6.0 5.7.0 Addition of procedure to retrieve UE-specific
behaviour data
CN#21 23.018 128 Rel-5 5.7.0 5.8.0 Corrections to "Early UE" handling
CN#21 23.018 133 Rel-5 5.7.0 5.8.0 HLR Interrogation for SCUDIF calls
CN#21 23.018 132 Rel-6 5.8.0 6.0.0 Removal of SIWF material
CN#22 23.018 126r1 Rel-6 6.0.0 6.1.0 Collective CR for Rel-6 Enhanced Dialled
Services
CN#22 23.018 135 Rel-6 6.1.0 6.2.0 Incorrect implementation of CR 133
CN#22 23.018 137 Rel-6 6.1.0 6.2.0 Default Basic Service for gsmSCF-initiated
calls
CN#25 23.018 141r1 Rel-6 6.2.0 6.3.0 Pre-Paging Resource Optimization
CN#25 23.018 143r1 Rel-6 6.2.0 6.3.0 Add CAMEL_Stop_TNRyin Procedure
OG_Call_Setup _MSC (sheet 4)
CN#27 23.018 144 Rel-6 6.3.0 6.4.0 Management Based Activation Impacts
CT#28 23.018 145r1 Rel-7 6.4.0 7.0.0 Trunk Originated CAMEL triggering - SDLs
CT#29 23.018 146 Rel-7 7.0.0 7.1.0 Trunk Originated CAMEL: Inter-digit timer
stop/reset SDL correction
CT#30 23.018 0147 Rel-7 7.1.0 7.2.0 Incorrect References
CT#33 23.018 0150 Rel-7 7.2.0 7.3.0 Correction to the IC_CUG_Check
Procedure
CT#34 23.018 0155 Rel-7 7.3.0 7.4.0 Optional Suppress Terminating Services Bit
String in SRI
CT#36 23.018 0157r4 Rel-7 7.4.0 7.5.0 Mobile Termination whilst the MS is moving
to another MSC
CT#36 23.018 0159 Rel-7 7.4.0 7.5.0 PLMN BC in PRN for alternate speech/fax -
alignment with TS 29.007
CT#37 23.018 0160 Rel-7 7.5.0 7.6.0 Procedure Check_OG_Barring
0162 Missing SRIack negative response to ISUP
release cause mapping in GMSC
CT#40 23.018 0163r2 Rel-8 7.6.0 8.0.0 Paging optimization with A/Iu flex
CT#41 23.018 0164r1 Rel-8 8.0.0 8.1.0 eMLPP Priority in MAP SRI, PRN and PSI
request
3GPP
Release 14 300 3GPP TS 23.018 V14.0.0 (2017-03)
Change history
CT#42 23.018 Rel-8 8.1.0 8.1.1 Copyright Notification updated
CT#45 23.018 0166 Rel-8 8.1.1 8.2.0 PSI negative response
CT#46 - - 8.2.0 9.0.0 Update to Rel-9 version (MCC)
CT#47 23.018 0167r4 Rel-9 9.0.0 9.1.0 Mobile Termination on Pre-paging whilst the
MS is moving to another MSC
CT#49 23.018 0168r2 Rel-9 9.1.0 9.2.0 SRI Negative Response Error
CT#49 23.018 0170 Rel-9 9.1.0 9.2.0 Correction for SMS via SGs charging
23.018 Rel-9 9.2.0 9.2.1 History table version numbers corrected
CT#50 23.018 0171 Rel-10 9.2.1 10.0.0 MT Roaming Retry
CT#51 23.018 0174r2 Rel-10 10.0.0 10.1.0 Mobile Terminating Roaming Forwarding
CT#51 23.018 0173 Rel-10 10.0.0 10.1.0 MT Roaming Retry and Super Charger
CT#52 23.018 0180 Rel-10 10.1.0 10.2.0 Paging optimization with A/Iu flex
CT#52 23.018 0175r3 Rel-10 10.1.0 10.2.0 Mobile Terminating Roaming Forwarding for
Pre-paging
CT#52 23.018 0176 Rel-10 10.1.0 10.2.0 New LMSI handling for MTRF
CT#52 23.018 0177r1 Rel-10 10.1.0 10.2.0 SDL changes for MTRF after retrieval of
routeing information
CT#52 23.018 10.2.0 10.2.1 Editorial correction of overlapping CRs C4-
111418 and C4-111415 implementation
after CT#52. 5.2.4 was re-numbered as
figure 4d in order to align with previous
figure number in serction 5.2.3.
CT#53 23.018 0181r1 Rel-11 10.2.1 11.0.0 Addition of Anonymous Call Rejection in the
CS domain
CT#53 23.018 0182r2 Rel-11 10.2.1 11.0.0 HLR/HSS domain selection function
alignment with Stage 2 requirement
CT#54 23.018 0188r1 Rel-11 11.0.0 11.1.0 Provide Subscriber Information handling for
UE under LTE
CT#54 23.018 0183r1 Rel-11 11.0.0 11.1.0 Cause code mapping
CT#54 23.018 0185 Rel-11 11.0.0 11.1.0 CSG access control in CS domain
CT#55 23.018 0189r4 Rel-11 11.1.0 11.2.0 Termination of VT-CSI Dialogue during
MTRR and MTRF Procedures
CT#56 23.018 0190r1 Rel-11 11.2.0 11.3.0 MTRF upon establishment of SGs
association
CT#56 23.018 0191r1 Rel-11 11.2.0 11.3.0 Subclause number correction on MTRF
CT#59 23.018 0195r3 Rel-11 11.3.0 11.4.0 MTRF for normal 2G and 3G MT call
CT#59 23.018 0193r1 Rel-12 11.4.0 12.0.0 MTRR for normal 2G/3G MT call
CT#59 23.018 0196r1 Rel-12 11.4.0 12.0.0 MTRF for normal 2G and 3G MT call
CT#60 23.018 0197 Rel-12 12.0.0 12.1.0 MM Abort intead of CM Service Reject after
CM service acceptance
CT#61 23.018 0198r2 12.1.0 12.2.0 MTRF Optimal Routing when the GMSC
and new MSC/VLR are the same node
CT#70 23.018 - Rel-13 12.2.0 13.0.0 Update to Rel-13 version (MCC)
2017-03 23.018 - Rel-14 13.0.0 14.0.0 Update to Rel-14 version (MCC)
3GPP

E00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

E00

Uploaded by

Copyright:

Available Formats

3GPP TS 23.018 V14.0.

3rd Generation Partnership Project;

3GPP support office address

No part may be reproduced except as authorized by written permission.

7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC .................................................................................... 40

7.2.4.8 Procedure Retrieve_IMEI_If_Required ...................................................................................................168

8.1.29 Provide IMSI....................................................................................................................................................279

Annex A (informative): Handling of an IAM at an MSC ................................................................. 296

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 Indicates a TSG approved Release 1999 document under change control;

4 Indicate a TSG approved Release 4 document under change control.

- For a specific reference, subsequent revisions do not apply.

[1] 3GPP TS 43.020: "Security related Network Functions".

[4] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[5] 3GPP TS 23.003: "Numbering, addressing and identification".

[6] 3GPP TS 23.012: "Location management procedures".

[7] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".

[11] 3GPP TS 23.072: "Call deflection Supplementary Service; Stage2".

[14] 3GPP TS 23.081: "Line identification Supplementary Services; Stage 2 ".

[24] 3GPP TS 23.116: "Super-charger technical realization; Stage 2".

[25] 3GPP TS 23.135: "Multicall supplementary service; Stage 2".

[25a] 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities".

[27] 3GPP TS 25.413: "UTRAN Iu interface RANAP signalling".

[29] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[32] 3GPP TS 33.102: "3G Security; Security architecture ".

[43] 3GPP TS 23.007: "Restoration procedures".

3 Definitions and abbreviations

A subscriber: the calling mobile subscriber

B subscriber: the mobile subscriber originally called by the A subscriber

A&O Active & Operative

GPRS General Packet Radio Service

4.1 Architecture for an MO call

Radio I/F signalling Iu or A I/F signalling IAM (ISUP)

Figure 1: Architecture for a basic mobile originated call

- establishes a traffic channel to the MS; and

4.2 Architecture for an MT call

Figure 2: Architecture for a basic mobile terminated call

4.3 Architecture for a TO call

Figure 4.3.1: Architecture for a basic trunk originated call

5.1 Information flow for an MO call

MSA BSSA VMSCA VLRA

Figure 3: Information flow for a basic mobile originated call

The network then waits for the call to be cleared.

5.2 Information flow for retrieval of routeing information for an

HLRB decides whether pre-paging is supported according to the following criteria:

- GMSCB has indicated that it supports pre-paging; and

5.2.1 Mobile Terminating Roaming Retry Call after successful Retrieval of

In that case, upon receipt of:

- a MAP Cancel Location procedure while on-going paging,

SRI (B, GMSC@,call Ref.,Roaming retry)1

Insert Subscriber Data (multiple)

HLR delays the sending of PRN

Insert Subscriber Data (continued)

New VMSC/VLR may delay setup until

Normal MT call procedure follows.

5.2.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing

In that case, upon receipt of:

- a MAP Cancel Location procedure while on-going pre-paging,

PRN Negative Response 3

2nd SRI (B, basic call interrogation) 5

HLR delays the sending of PRN