3GPP TS 23.018

3GPP TS 23.018 V3.12.
0 (2003-03)
Technical Specification
3rd Generation Partnership Project;

Technical Specification Group Core Network;
Basic call handling;
Technical realization
(Release 1999)
GLOBAL SYSTEM FOR

MOBILE COMMUNICATIONS
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 1999 2 3GPP TS 23.018 V3.12.0 (2003-03)
Keywords
UMTS, 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.
2003, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA, TTC)
All rights reserved.
3GPP
Release 1999 3 3GPP TS 23.018 V3.12.0 (2003-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
5 Information flows...................................................................................................................................12
5.1 Information flow for an MO call ........................................................................................................................... 13
5.2 Information flow for retrieval of routeing information for an MT call ................................................................. 15
5.3 Information flow for an MT call............................................................................................................................ 16
6 Principles for interactions with supplementary services ........................................................................19
6.1 Call Deflection service (3GPP TS 23.072)............................................................................................................ 19
6.2 Line identification services (3GPP TS 23.081) ..................................................................................................... 19
6.2.1 Calling Line Identification Presentation (CLIP) .............................................................................................. 19
6.2.2 Calling Line Identification Restriction (CLIR)................................................................................................ 19
6.2.3 Connected Line Identification Presentation (COLP) ....................................................................................... 19
6.2.4 Connected Line Identification Restriction (COLR) ......................................................................................... 19
6.3 Call forwarding services (3GPP TS 23.082) ......................................................................................................... 19
6.3.1 Call Forwarding Unconditional (CFU) ............................................................................................................ 19
6.3.2 Call Forwarding on mobile subscriber Busy (CFB) ........................................................................................ 20
6.3.3 Call Forwarding on No Reply (CFNRy).......................................................................................................... 20
6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)..................................................................... 20
6.4 Call wait (3GPP TS 23.083) .................................................................................................................................. 20
6.5 Call hold (3GPP TS 23.083).................................................................................................................................. 20
6.6 Multiparty (3GPP TS 23.084) ............................................................................................................................... 20
6.7 Closed user group (3GPP TS 23.085).................................................................................................................... 20
6.8 Advice of charge (3GPP TS 23.086) ..................................................................................................................... 20
6.9 User-to-user signalling (3GPP TS 23.087)............................................................................................................ 20
6.10 Call barring (3GPP TS 23.088)........................................................................................................................ 21
6.10.1 Barring of outgoing calls ................................................................................................................................. 21
6.10.2 Barring of incoming calls ................................................................................................................................ 21
6.11 Explicit Call Transfer (3GPP TS 23.091) ........................................................................................................ 21
6.12 Completion of Calls to Busy Subscriber (3GPP TS 23.093) ........................................................................... 21
6.13 Multicall (3GPP TS 23.135) ............................................................................................................................ 21
7 Functional requirements of network entities ..........................................................................................21
7.1 MO call.................................................................................................................................................................. 22
7.1.1 Functional requirements of serving MSC ........................................................................................................ 22
7.1.1.1 Process OCH_MSC ......................................................................................................................................... 22
7.1.1.2 Procedure Process_Access_Request_MSC...................................................................................................... 22
7.1.1.3 Procedure OG_Call_Setup_MSC .................................................................................................................... 23
7.1.1.4 Procedure Obtain_IMSI_MSC......................................................................................................................... 24
7.1.1.5 Procedure Authenticate_MSC ......................................................................................................................... 24
7.1.1.6 Procedure Obtain_IMEI_MSC ........................................................................................................................ 24
7.1.1.7 Procedure Check_IMEI_MSC ......................................................................................................................... 24
7.1.1.8 Procedure Establish_Originating_TCH_If_Required ...................................................................................... 25
7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC .......................................................................................... 25
7.1.1.10 Procedure Send_Alerting_If_Required ...................................................................................................... 25
7.1.1.11 Procedure Set_COLP_Info_MSC .............................................................................................................. 25
3GPP
Release 1999 4 3GPP TS 23.018 V3.12.0 (2003-03)
7.1.1.12 Procedure Send_Access_Connect_If_Required ......................................................................................... 25

7.1.1.13 Procedure Handle_AoC_MO_MSC........................................................................................................... 25
7.1.2 Functional requirements of VLR ..................................................................................................................... 49
7.1.2.1 Process OCH_VLR.......................................................................................................................................... 49
7.1.2.2 Procedure Process_Access_Request_VLR ...................................................................................................... 49
7.1.2.3 Procedure OG_Call_Subscription_Check_VLR.............................................................................................. 49
7.1.2.4 Procedure Obtain_Identity_VLR ..................................................................................................................... 49
7.1.2.5 Procedure Obtain_IMSI_VLR ......................................................................................................................... 49
7.1.2.6 Procedure Authenticate_VLR.......................................................................................................................... 49
7.1.2.7 Procedure Obtain_Authentication_Sets_VLR ................................................................................................. 50
7.1.2.8 Procedure Start_Tracing_VLR ........................................................................................................................ 50
7.1.2.9 Procedure Check_IMEI _VLR ........................................................................................................................ 50
7.1.2.10 Procedure Obtain_IMEI _VLR .................................................................................................................. 50
7.1.2.11 Process Fetch_Authentication_Sets_VLR.................................................................................................. 50
7.1.2.12 Procedure Check_BAOC ........................................................................................................................... 50
7.1.2.13 Procedure OG_CUG_Check ...................................................................................................................... 50
7.1.2.14 Procedure Get_LI_Subscription_Info_MO_VLR ...................................................................................... 50
7.1.2.15 Procedure Get_AoC_Subscription_Info_VLR........................................................................................... 50
7.1.2.16 Procedure Check_OG_Barring................................................................................................................... 50
7.1.2.17 Process Update_Location_VLR ................................................................................................................. 50
7.2 Retrieval of routeing information for MT call....................................................................................................... 77
7.2.1 Functional requirements of GMSC .................................................................................................................. 77
7.2.1.1 Process MT_GMSC......................................................................................................................................... 77
7.2.1.2 Procedure Obtain_Routeing_Address.............................................................................................................. 79
7.2.1.3 Procedure Send_ACM_If_Required ................................................................................................................ 79
7.2.1.4 Procedure Send_Answer_If_Required............................................................................................................. 79
7.2.1.5 Procedure Send_Network_Connect_If_Required ............................................................................................ 80
7.2.1.6 Procedure Handle_COLP_Forwarding_Interaction_MSC .............................................................................. 80
7.2.1.7 Procedure Activate_CF_Process...................................................................................................................... 80
7.2.1.8 Process MT_CF_MSC..................................................................................................................................... 80
7.2.1.9 Macro CUG_Support_Check_GMSC.............................................................................................................. 81
7.2.2 Functional requirements of HLR ................................................................................................................... 104
7.2.2.1 Process SRI_HLR .......................................................................................................................................... 104
7.2.2.2 Procedure Check_Parameters ........................................................................................................................ 104
7.2.2.3 Procedure Subscription_Check_HLR ............................................................................................................ 105
7.2.2.4 Procedure First_Forwarding_HLR ................................................................................................................ 105
7.2.2.5 Procedure PRN_Error_HLR .......................................................................................................................... 105
7.2.2.6 Procedure Forward_CUG_Check .................................................................................................................. 105
7.2.2.7 Procedure Derive_Requested_Basic_Service_HLR ...................................................................................... 105
7.2.2.8 Procedure Check_IC_Barring........................................................................................................................ 105
7.2.2.9 Procedure IC_CUG_Check............................................................................................................................ 105
7.2.2.10 Procedure Handle_CFU ........................................................................................................................... 105
7.2.2.11 Procedure Handle_CFNRc ....................................................................................................................... 106
7.2.3 Functional requirements of VLR ................................................................................................................... 122
7.2.3.1 Process PRN_VLR ........................................................................................................................................ 122
7.2.3.2 Process Restore_Subscriber_Data_VLR........................................................................................................ 122
7.2.3.3 Process PSI_VLR .......................................................................................................................................... 122
7.2.3.4 Procedure Retrieve_Location_Info_VLR ...................................................................................................... 123
7.2.3.5 Procedure Retrieve_Current_Location_VLR ................................................................................................ 123
7.2.4 Functional requirements of MSC................................................................................................................... 137
7.2.4.1 Process Prepage_MSC................................................................................................................................... 137
7.2.4.2 Procedure Prepaging_Page_MS_MSC .......................................................................................................... 137
7.2.4.3 Prepaging_Search_For_MS_MSC................................................................................................................. 137
7.2.4.4 Process OSI_MSC ......................................................................................................................................... 137
7.2.4.5 Process RCL_MSC ........................................................................................................................................ 137
7.2.4.6 Procedure Current_Location_Page_MSC...................................................................................................... 137
7.2.4.7 Procedure Current_Location_Search_MSC................................................................................................... 137
7.3 MT call ................................................................................................................................................................ 145
7.3.1 Functional requirements of serving MSC ...................................................................................................... 145
7.3.1.1 Process ICH_MSC......................................................................................................................................... 145
7.3.1.2 Procedure Page_MS_MSC ............................................................................................................................ 147
7.3.1.3 Procedure Search_For_MS_MSC.................................................................................................................. 148
3GPP
Release 1999 5 3GPP TS 23.018 V3.12.0 (2003-03)
7.3.1.4 Procedure Complete_Call_In_MSC .............................................................................................................. 148

7.3.1.5 Procedure Process_Call_Waiting_MSC ........................................................................................................ 149
7.3.1.6 Procedure Set_CLIP_Info_MSC ................................................................................................................... 151
7.3.1.7 Procedure Derive_GSM_BC_MSC ............................................................................................................... 151
7.3.1.8 Procedure Establish_Terminating_TCH_If_Required................................................................................... 151
7.3.1.9 Procedure Handle_AoC_MT_MSC............................................................................................................... 151
7.3.1.10 Procedure Set_COL_Presentation_Indicator_MSC ................................................................................. 151
7.3.2 Functional requirements of VLR ................................................................................................................... 193
7.3.2.1 Process ICH_VLR ......................................................................................................................................... 193
7.3.2.2 Procedure Derive_Requested_Basic_Service_VLR ...................................................................................... 194
7.3.2.3 Procedure Search_For_MS_VLR .................................................................................................................. 194
7.3.2.4 Procedure Get_CW_Subscription_Info_VLR ............................................................................................... 194
7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR .......................................................................................... 194
7.3.2.6 Procedure Handle_CFB ................................................................................................................................. 194
7.3.2.7 Procedure Handle_CFNRy ............................................................................................................................ 194
8 Contents of messages ...........................................................................................................................209
8.1 Messages on the B interface (MSC-VLR)........................................................................................................... 209
8.1.1 Abort.............................................................................................................................................................. 209
8.1.2 Authenticate................................................................................................................................................... 209
8.1.3 Authenticate ack ............................................................................................................................................ 210
8.1.4 Authenticate negative response...................................................................................................................... 210
8.1.5 Call arrived .................................................................................................................................................... 210
8.1.6 Check IMEI ................................................................................................................................................... 210
8.1.7 Check IMEI ack ............................................................................................................................................. 210
8.1.8 Check IMEI negative response ...................................................................................................................... 210
8.1.9 Complete Call ................................................................................................................................................ 210
8.1.10 Complete Call ack.......................................................................................................................................... 212
8.1.11 Complete Call negative response................................................................................................................... 212
8.1.12 Forward New TMSI....................................................................................................................................... 212
8.1.13 Forward New TMSI ack ................................................................................................................................ 212
8.1.14 Forward New TMSI negative response ......................................................................................................... 212
8.1.15 Obtain Subscriber Info................................................................................................................................... 213
8.1.16 Obtain Subscriber Info ack ............................................................................................................................ 213
8.1.17 Page MS......................................................................................................................................................... 213
8.1.18 Page MS ack .................................................................................................................................................. 213
8.1.19 Page MS negative response ........................................................................................................................... 213
8.1.20 Page MS via SGSN........................................................................................................................................ 215
8.1.21 Process Access Request ................................................................................................................................. 215
8.1.22 Process Access Request ack........................................................................................................................... 215
8.1.23 Process Access Request negative response.................................................................................................... 216
8.1.24 Process Call Waiting...................................................................................................................................... 216
8.1.25 Process Call Waiting ack ............................................................................................................................... 216
8.1.26 Process Call Waiting negative response ........................................................................................................ 216
8.1.27 Provide IMEI ................................................................................................................................................. 216
8.1.28 Provide IMEI ack........................................................................................................................................... 217
8.1.29 Provide IMSI ................................................................................................................................................. 217
This message contains no information elements.8.1.30 Provide IMSI ack................................................................. 217
8.1.30 Provide IMSI ack........................................................................................................................................... 218
8.1.31 Radio connection released ............................................................................................................................. 218
8.1.32 Search For MS ............................................................................................................................................... 218
8.1.33 Search For MS ack......................................................................................................................................... 218
8.1.34 Search For MS negative response.................................................................................................................. 218
8.1.35 Search for MS via SGSN ............................................................................................................................... 219
8.1.36 Send Info For Incoming Call ......................................................................................................................... 219
8.1.37 Send Info For Incoming Call ack................................................................................................................... 220
8.1.38 Send Info For Incoming Call negative response ............................................................................................ 221
8.1.39 Send Info For Outgoing Call.......................................................................................................................... 221
8.1.40 Send Info For Outgoing Call negative response ............................................................................................ 221
8.1.41 Start security procedures................................................................................................................................ 222
8.1.42 Trace subscriber activity................................................................................................................................ 222
8.1.43 Use existing TMSI ......................................................................................................................................... 222
3GPP
Release 1999 6 3GPP TS 23.018 V3.12.0 (2003-03)
8.2 Messages on the C interface (MSC-HLR)........................................................................................................... 223

8.2.1 Send Routeing Info ........................................................................................................................................ 223
8.2.2 Send Routeing Info ack.................................................................................................................................. 224
8.2.3 Send Routeing Info negative response........................................................................................................... 225
8.3 Messages on the D interface (VLR-HLR) ........................................................................................................... 226
8.3.1 Provide Roaming Number ............................................................................................................................. 226
8.3.2 Provide Roaming Number ack....................................................................................................................... 226
8.3.3 Provide Roaming Number negative response ................................................................................................ 226
8.3.4 Provide Subscriber Info ................................................................................................................................. 227
8.3.5 Provide Subscriber Info ack........................................................................................................................... 227
8.3.5.1 Location information ..................................................................................................................................... 228
8.3.6 Provide Subscriber Info negative response .................................................................................................... 228
8.3.7 Restore Data................................................................................................................................................... 228
8.3.8 Restore Data ack ............................................................................................................................................ 229
8.3.9 Restore Data negative response ..................................................................................................................... 229
8.4 Messages on the F interface (MSC-EIR)............................................................................................................. 229
8.4.1 Check IMEI ................................................................................................................................................... 229
8.4.2 Check IMEI ack ............................................................................................................................................. 229
8.4.3 Check IMEI negative response ...................................................................................................................... 229
8.5 Messages on the MSC internal interface ............................................................................................................. 230
8.5.1 CF cancelled .................................................................................................................................................. 230
8.5.2 Perform Call Forwarding ............................................................................................................................... 230
8.5.3 Perform Call Forwarding ack......................................................................................................................... 230
8.5.4 Perform Call Forwarding negative response.................................................................................................. 230
8.6 Messages on the VLR internal interface.............................................................................................................. 230
8.6.1 Call arrived .................................................................................................................................................... 230
8.6.2 PAR completed .............................................................................................................................................. 230
8.7 Messages on the Gs interface .............................................................................................................................. 231
8.7.1 Page MS......................................................................................................................................................... 231
8.7.2 Send MS information..................................................................................................................................... 231
8.7.3 Send MS information ack .............................................................................................................................. 231
8.7.4 Send MS information negative response ....................................................................................................... 231
Annex A (informative): Handling of an IAM at an MSC .................................................................232

Annex B: Change history ....................................................................................................................235
3GPP
Release 1999 7 3GPP TS 23.018 V3.12.0 (2003-03)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP)..
The present document specifies the technical realisation 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 3.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 Indicates TSG approved 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 1999 8 3GPP TS 23.018 V3.12.0 (2003-03)
1 Scope
The present document specifies the technical realisation 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.
In the present document, the term MS is used to denote a UMTS 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 23.07x, 23.08x and 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 specification of the handling of data calls re-routed to a SIWFS is described in 3GPP TS 23.054 [8].
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 [25], 3GPP TS 25.413 [26], GSM 08.08 [2] and 3GPP TS 29.002 [28]), 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] GSM 03.20: " Digital cellular telecommunications system (Phase 2+); Security related network
functions".
[2] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile-services Switching
Centre - Base Station System (MSC - BSS) interface Layer 3 specification".
[3] GSM 12.08: "Digital cellular telecommunications system (Phase 2+); 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] 3GPP TS 23.054: "Shared Inter Working Function (SIWF) - Stage 2 ".
[9] 3GPP TS 23.060: "General Packet Radio Service; Service description; Stage 2".
3GPP
Release 1999 9 3GPP TS 23.018 V3.12.0 (2003-03)
[10] 3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical Realisation Stage
2"
[11] 3GPP TS 23.072: "Call Deflection (CD) supplementary service; Stage2".
[12] 3GPP TS 23.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) -
Phase 3; Stage 2".
[13] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical Realisation".
[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 Services - 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.093: "Technical realisation of Completion of Calls to Busy Subscriber (CCBS) -
Stage 2".
[23] 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2".
[24] 3GPP TS 23.135: "Multicall supplementary service; Stage 2".
[25] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-Stage 3".
[26] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".
[27] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".
[28] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[29] 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)".
[30] 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)".
[31] 3GPP TS 33.102: "3G Security; Security Architecture ".
[32] ITU-T Recommendation Q.761 (1999): " Signalling System No. 7 - ISDN User Part functional
description ".
[33] ITU-T Recommendation Q.762 (1999): "Signalling System No. 7 - ISDN User Part general
functions of messages and signals".
[34] ITU-T Recommendation Q.763 (1999): "Signalling System No. 7 - ISDN User Part formats and
codes".
[35] ITU-T Recommendation Q.764 (1999): " Signalling System No. 7 - ISDN user part signalling
procedures".
[36] ITU-T Recommendation Q.850 (1996): "Usage of cause and location in the Digital Subscriber
Signalling System No. 1 and the Signalling System No. 7 ISDN User Part".
3GPP
Release 1999 10 3GPP TS 23.018 V3.12.0 (2003-03)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following 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.
Circuit-Switched Bearer Capability: The 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.
Location Information: Information to define the whereabouts of the MS, and the age of the information defining the
whereabouts.
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
CS BC Circuit-Switched Bearer Capability
CUG Closed User Group
CW Call Waiting
FTN Forwarded-To Number
FTNW Forwarded-To NetWork
GMSCB Gateway MSC of the B subscriber
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
3GPP
Release 1999 11 3GPP TS 23.018 V3.12.0 (2003-03)
PRN Provide Roaming Number

SGSN Serving GPRS support node
SIFIC Send Information For Incoming Call
SIFOC Send Information For Outgoing Call
SIWF Shared Inter Working Function
SIWFS SIWF Server. SIWFS is the entity where the used IWU is located.
SRI Send Routeing Information
UDUB User Determined User Busy
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.
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.
3GPP
Release 1999 12 3GPP TS 23.018 V3.12.0 (2003-03)
NOTE: When the non-loop method is used for data calls, the IAM is sent to the SIWFS.
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.
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.
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 [31] or the GSM ciphering mechanism defined in
GSM 03.20 [1], as appropriate.
3GPP
Release 1999 13 3GPP TS 23.018 V3.12.0 (2003-03)
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.
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
Figure 3: Information flow for a basic mobile originated call
3GPP
Release 1999 14 3GPP TS 23.018 V3.12.0 (2003-03)
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.
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 [31] for UMTS and GSM 03.20 [1] for
GSM. VLRA may also initiate security procedures at this stage, as described in 3GPP TS 33.102 [31] for UMTS
GSM 03.20 [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 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 [31] for UMTS and GSM 03.20 [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 1999 15 3GPP TS 23.018 V3.12.0 (2003-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.
GMSC HLRB VLRB VMSCB BSSB MSB
IAM
SRI
PRN (note 1)
Page MS
Page
Page
Chan req
Imm ass
Page resp
MS conn
Process estab
PRN ack access req
(note 2)
SRI ack
Start security
procedures
Process
access req ack Start security
procedures Security control
command
Security control
response
IAM
Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call
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.
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 1999 16 3GPP TS 23.018 V3.12.0 (2003-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. 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.
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 1999 17 3GPP TS 23.018 V3.12.0 (2003-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
Figure 5: Information flow for a basic mobile terminated call
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.
3GPP
Release 1999 18 3GPP TS 23.018 V3.12.0 (2003-03)
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.
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 recognises 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 [31] for UMTS and
GSM 03.20 [1] for GSM. VLRB may also initiate security procedures at this stage, as described in 3GPP
TS 33.102 [31] for UMTS and GSM 03.20 [1] for GSM.
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.
3GPP
Release 1999 19 3GPP TS 23.018 V3.12.0 (2003-03)
6 Principles for interactions with supplementary

services
This clause specifies the principles used to describe the invocation of the GSM supplementary services which were
standardised 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
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.2 and 7.3.1.
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 [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
3GPP
Release 1999 20 3GPP TS 23.018 V3.12.0 (2003-03)
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
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.
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.
3GPP
Release 1999 21 3GPP TS 23.018 V3.12.0 (2003-03)
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 and MAF023 (3GPP TS 23.088 [21])
as described in subclause 7.2.2.
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 MS;
- 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 [26], for interworking with
the UTRAN and DTAP, which is specified in 3GPP TS 24.008 [25], for interworking with the MS.
The protocols used over the A interface are BSSMAP, which is specified in GSM 08.08 [2], for interworking with the
BSS and DTAP, which is specified in 3GPP TS 24.008 [25], for interworking with the MS.
The protocol used over the C, D & F interfaces is MAP, which is specified in 3GPP TS 29.002 [28].
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[32], Q.762 [33], Q.763 [34] and Q.764 [35]; other telephony signalling
systems may be used instead.
3GPP
Release 1999 22 3GPP TS 23.018 V3.12.0 (2003-03)
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;
- 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 [22].
7.1.1.2 Procedure Process_Access_Request_MSC

Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC, the VMSC may encapsulate the request for the
IMEI in the Start 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 [30].
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.
3GPP
Release 1999 23 3GPP TS 23.018 V3.12.0 (2003-03)
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 GSM bearer capability negotiated between the VMSC and the MS to a GSM basic
service according to the rules defined in 3GPP TS 27.001 [27].
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].
Sheet 1: the procedure Check_OG_Multicall_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [24]. If the
VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Pass?".
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 [22].
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 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 "Yes" exit of
the test "Result=Pass?".
Sheet 3: the procedure CCBS_Check_OG_Call is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. 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 [22].
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 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 6: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS; they are
specified in 3GPP TS 23.093 [22]. 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 1999 24 3GPP TS 23.018 V3.12.0 (2003-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?".
7.1.1.4 Procedure Obtain_IMSI_MSC

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

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

The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If a
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
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.
3GPP
Release 1999 25 3GPP TS 23.018 V3.12.0 (2003-03)
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 partys 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 1999 26 3GPP TS 23.018 V3.12.0 (2003-03)
Process O CH _M S C OC H_M S C1(1)

Proc ess in the MS C to
handle an outgoing c al l request
Idl e
Signal s from the left
are from the BSS
CM
s erv ice
reques t
Proc es s_
Access _
Request_M SC
No
Resu lt=
Pas s?
Ye s
W ait _For_
Setup
CM
S etup Serv ice
Abort
CC BS_R ep ort_
See TS 23.093 Not_Idle
TC H al located:=
False
OG_Ca ll_
Setu p_M SC
CC BS_Check _
See TS 23.093 Las t_C al l
Rele as e
call
resourc es
Idl e
Figure 6: Process OCH_MSC
3GPP
Release 1999 27 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P rocess_Access_Reque st_MSC PA R_MS C1(3)

Procedure in t he M SC
to handle a reques t from
the MS for system access
P rocess
A ccess
Si gnal s to/from the l eft R eques t
are to/fr om the BSS;
si gnal s to/from the ri ght
are to/fro m the VLR.
W ait_F or_
P AR_R esult
Trac e
Provide
Authenticate Subscriber
IMSI
Activi ty
Tracing
Obtain_IM SI_ Authentic ate_
MS C M SC Active :=
TR UE
No No
Res ult= R esult =
Pass? Pass ?
Yes Yes
R esult:= R esul t:=

Fail F ail
W ait_For_ W ait_For_ W ai t_For_

PAR _Resul t PA R_R esult PAR _Resul t
W ait_F or_
P AR_R esult
CM Start
serv ice secu ri ty
abort proc edur es
C ipheri ng
R equired:=
True
Abort
R es ult:=
Fail
W ait_For_
PA R_R esult
Figure 7a: Procedure Process_Access_Request_MSC (sheet 1)
3GPP
Release 1999 28 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he M SC W ait_F or_ Signals to/from the left
to handle a reques t from P AR_R esult are to/from the BSS;
the MS for system access si gnals to/from the right
are to/from the VL R.
Proce ss Acces s Process

Abort Request Ac cess
negati ve R equ es t ac k
response
Yes Fals e
C M Serv ice type= C ipheri ng
P age R esponse? requi red
No True
Map negativ e Yes

C M Ser vic e type =
response to Page R esp ons e?
rejec t c aus e
No
Rel eas e C M Service

transac tion R eject
Start
Resu lt:= CM Serv ice
Fail security Accept
proc edures
W ait_For_
T MS I_
R ealloc ation
CM Us e
Provi de C heck Forward
servic e IMEI S etup IMEI Abort N ew T MSI Exis ting
abort TMSI
Obtain_IMEI_ C heck _IM EI_ M ap negative

re sponse to
MS C MSC
re ject cause
No No
Res ult= R esult= C M Servic e R ea lloca te
Abort
Pass? Pass ? R eject TM SI
Yes Yes
R esult:= R esult:= R esult:= R es ult:=

Fail F ail F ai l Pass
W ai t_For_ W ait_For_
W a it_For_
TM SI_ T MS I_ TM SI_Ack
R eal location R eall ocation
Figure 7b: Procedure Process_Access_Request_MSC (sheet 2)
3GPP
Release 1999 29 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he M SC W ait_F or_ Signals to /from the l eft
to handle a reques t from TM SI_Ac k are to/from the BSS;
the MS for system access sig nal s to/from the right
are to/from the VLR .
CM TM SI TM SI
servic e Setup A bort R eall oc ation R eallocation
abort Fa ilure Com ple te
For ward Forward

Abort N ew T MSI New TM SI
negativ e ack
re spons e
R esult:= R esul t:= R es ult:=

Fail F ail Pass
Figure 7c: Procedure Process_Access_Request_MSC (sheet 3)
3GPP
Release 1999 30 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure OG_Call_Setup_MSC OCS_MSC1(9)

Proc edure in the originating VMSC
t o set up an outgoi ng c all after a Setup
message has been received from the MS
Alert ing sent :=False

Backward call indicator: =No indic ation
MS connec ted: =False
Reconnec t:=False
UUS1 result sent :=False
CAMEL_Invocation:=False
UUS_OCH_
Check_ See TS 23. 087
Set up
Conver t
CS BC to
basic servic e
CAMEL_N_CSI
CHECK_MSC
Check_OG _
See TS 23. 135
Multicall_MSC
No
Result=
Pass ?
Yes
Release Send Info For

transaction Out going Call
CCBS_O CH_
See TS 23. 093
Report_F ailure
Wait _F or_
MO_Call_
Result
Figure 8a: Procedure OG_Call_Setup_MSC (sheet 1)
3GPP
Release 1999 31 3GPP TS 23.018 V3.12.0 (2003-03)
P ro c e d u re O G _ C a ll_ S e t up _ M S C O C S _ M S C 2 (9 )
P ro c ed u r e in th e o r ig in a tin g V M S C
to s e t u p a n o u tgo i n g ca ll a fte r a S etu p
W a it_ Fo r_
me s sa g e h a s b ee n r e ce iv e d fr o m th e M S
M O _ C a ll _
R e su lt
Re l e as e C o m p le te S e n d In fo F o r
O u tg o in g C al l
tra n sa c ti o n C all
n e g a ti ve
re s po n se
C o n ve r t CS B C
to ch a n n e l
r e q u ir e me n t
C all Re le a se
A b o rt P r o ce e d in g tra n sa c ti o n
E st ab l is h_
O r ig i n at in g _
T CH _ If_
R e q u ir e d
No
R e su l t=
P as s?
Ye s
CC B S _ O C H_ C CB S _O CH _
S e e TS 2 3 .0 9 3 Re p o r t_F a ilu r e R ep o r t_F a il u re S e e T S 2 3 .0 93
Figure 8b: Procedure OG_Call_Setup _MSC (sheet 2)
3GPP
Release 1999 32 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure OG _Call_Setup_M S C OC S_MS C3(9)

Proc edure in the originatin g VMSC Signals to/from the left
to s et up an outgoi ng call after a Setup 1 are to/from the BSS;
mes sage h as been receiv ed from the M S si gnals to/from the right
are to/from the des tination exchange.
S et_C LI_
P resentation_
Indic ato r_
M SC
No
R esul t=
C all allow ed?
Yes
R el ease C AM EL_OC H_
See TS 23.078 3
transac tion M SC _INIT
No
R esul t= R econnec t:=
P as s? Tr ue
Yes
C AM EL_MO_
D i alled_ See TS 23.078
Servic es
No
R esul t=
P as s?
Yes
C C BS_Check _
See TS 23.093
OG _C all
No
R esul t=
P as s?
Yes
M OB ILE_N U M BER_
R elease
transacti on P OR TABILITY_ See TS 23.066
IN _OQoD
U U S_OC H_
S et_Info_ See TS 23.087
In_IAM
Initi al
A ddress
D estinati on address:=
IAM.Ca lled Par ty Address
C AM EL_Store_
CC BS_OC H _
See TS 23.093 D estinati on_ See TS 23.078
Repor t_F ailure
A ddress
(F alse, Fals e)
W ait_F or_
AC M
Figure 8c: Procedure OG_Call_Setup _MSC (sheet 3)
3GPP
Release 1999 33 3GPP TS 23.018 V3.12.0 (2003-03)

Proc edure in the originatin g VMSC Signal s to/from the l eft
to s et up an outgoi ng call after a Setup are to/from the BSS;
mes sage h as been receiv ed from the M S W ait_Fo r_ signal s to/from the ri ght
AC M are to/from the des tination exchange.
A ddress
C onnect
C omplete
C C BS_OC H_ C CBS _O CH _
See T S 23.093 See TS 23.093
R eport_Succes s R eport_Succes s
C AM EL_
See T S 23.078
S tart_T N Ry
Send_
A lerting_If_
R equired
No
R esul t=
P as s?
Yes
Rele as e
U TU 2C nt:=0
transacti on
W ait_Fo r_
Rel eas e
A ns wer
A ns wer
C AM EL_OC H_
See TS 23.078
M SC _AN SW ER
Figure 8d: Procedure OG_Call_Setup _MSC (sheet 4)
3GPP
Release 1999 34 3GPP TS 23.018 V3.12.0 (2003-03)

2
Proc edure in the originatin g VMSC Signals from the l eft
to s et up an outgoi ng call after a Setup are fro m the BSS
mes sage h as been receiv ed from the M S
No
R esult=
Pass ?
Yes
Yes
Res ult= Set_C OLP_
R ec onnec t? Info_M SC
No
H andle_AoC _
3 MO_MSC
Send_Acc es s_
C onnect_If_
R equired
Yes
R esult=
F ail?
No
R esult= No
C onnec t
s ent?
Yes
W ait_For_
C onnec t_Ack
C onnec t
Ack
MS c onnected:=
True
Store C W t reatme nt
indicator fo r this c all
if received in SII2
W ait_For_
C lear
Figure 8e: Procedure OG_Call_Setup _MSC (sheet 5)
3GPP
Release 1999 35 3GPP TS 23.018 V3.12.0 (2003-03)

mes sage h as been receiv ed from the M S W ait_Fo r_ signal s to/from the ri ght
AC M are to/from the destinati on exc hange
unless oth erw ise m arke d.
Releas e F rom Int_R eleas e_

R elease des ti nati on From gsm SSF
transac ti on C al l
exc hange
CC BS_OC H _ C C BS_Check _ CC BS_OC H _

See T S 23.093 If_C C BS_ See TS 23.093 S ee GS M 03.93
Report_F ailure Report_F ailure
P os sible
Store C C BS
R esult
C AMEL Phase 2 C AM EL Phase 2

or hi gher or hi gher
supported? s upported?
No Yes No Yes
Yes R elease cause =

N o ans wer
fro m user?
No
C AME L_O CH _ C AMEL_O CH _ C AM EL_OC H_ C AM EL_OC H_

4
M SC_D ISC 3 MS C_D ISC4 MSC _D ISC 3 MSC 1
No
R esult= Rel eas e
See TS 23.078
R econnect? transac tion
Yes
3
C C BS
C C BS P os sible
R esult
C CBS N ot
Possible
C CB S_
R elease
Rel eas e Ac ti vation_ See TS 23.093 Rel eas e
transaction
MSC
Figure 8f: Procedure OG_Call_Setup _MSC (sheet 6)
3GPP
Release 1999 36 3GPP TS 23.018 V3.12.0 (2003-03)

Proc edure in the originatin g VMSC W ait_Fo r_C onnect_ Ac k Signal s to/from the l eft are to/f rom the BS S;
to s et up an outgoi ng call after a Setup W ait_For_Answer signal s to/from the ri ght
mes sage h as been receiv ed from the M S are to/from the destination exc hange
unless otherw ise marke d.
Releas e In t_R el eas e_

R elease F rom gsmSSF
transac ti on C all
C AMEL Phase 2 C AM EL Phase 2

or hi gher or higher
supported? s upported?
No Yes No Yes
Yes
R eleas e c aus e=
N o a nswer from user?
No
C AME L_O CH _ C AMEL_O CH _ C AMEL_OC H_ C AMEL_OC H_ Releas e

See TS 23.078
M SC_D ISC 3 MS C_D ISC4 M SC _D ISC3 MSC 1 transac ti on
U US _M SC _ No
R esult=
Check _ See T S 23.087
R econnect?
U US 1_U UI
Yes
U U S_M SC_
See TS 23.087 C heck_ 3
U U S1_U UI
R elease
Rel eas e Releas e
transaction
Figure 8g: Procedure OG_Call_Setup _MSC (sheet 7)
3GPP
Release 1999 37 3GPP TS 23.018 V3.12.0 (2003-03)

mes sage h as been receiv ed from the M S signal s to/from the ri ght
are to/from the destinati on exc hange
unless oth erw ise m arke d.
W ait_F or_
A ns wer
Us er to U ser to TN R y
Internal
Us er U ser expired
4
U US _MSC _
Chec k_UU S2_ See T S 23.087 R elease
UU I_to_N W
U U S_M SC_
C AM EL_O CH _
See TS 23.087 C heck_ UU S2_ See TS 23.078
MSC 2
U U I_to_M S
R elease Re connec t
R esult?
C onti nue,
F ail
R elease
trans action
W ait_For_
Answe r 3
Figure 8h: Procedure OG_Call_Setup _MSC (sheet 8)
3GPP
Release 1999 38 3GPP TS 23.018 V3.12.0 (2003-03)

mes sage h as been receiv ed from the M S signal s to/from the ri ght
are to/from the destination exc hange
W ait_Fo r_
unless otherw ise marke d.
C lear
Releas e Int_R el eas e_

R elease from g sm SSF
transac ti on C all
U US _M SC _ U U S_M SC_
Releas e
Check _ See T S 23.087 C heck_ See TS 23.087
transac ti on
U US 1_U UI U U S1_UU I
C AME L_O CH _ C AM EL_OC H_

M SC_D ISC1 See T S 23.078 M SC _D ISC 2 See TS 23.078
Yes
R esul t=
R econnect?
No
Res ult= Yes Yes R esul t=

CA MEL C AM EL 3
handling? handling?
No No
R elease
Rel eas e Re lease
trans action
Figure 8i: Procedure OG_Call_Setup _MSC (sheet 9)
3GPP
Release 1999 39 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure O btain_IMS I_M S C OIM SI_M 1(1)

to obtain the IMS I from the M S
and re lay it to the VLR
Si gnal s to/from the l eft

Si gnal s to/from the right Send
are to/fr om the VLR IM SI
W ait_F or_
IM SI
Send IMSI
Send IMSI R elease
ack transacti on negati ve
res ponse
Re lease
transac tion
Provi de
A bort
IM SI ack
R es ult:= R esul t:=

Pass A borted
Figure 9: Procedure Obtain_IMSI_MSC
3GPP
Release 1999 40 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Au thenticate_M S C A UT _MSC 1(1)

to obtain an authentic ation
response from the M S

Si gnal s to/from the right Authenticate
are to/fr om the VLR
W ait_F or_
Auth_R espons e
Auth enti cate

Au thentic ate R elease
res ponse
Authenticate
Authentic ate
A bort negat ive
ack
res po ns e
R elease
transa ction
W ait_For_ R esult:=
Auth_Resul t Aborted
Authentic ation Authenticati on

accepted reject ed
Authenticati on
rejected
R es ult:=
Pass
Figure 10: Procedure Authenticate_MSC
3GPP
Release 1999 41 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure O btain_IME I_M S C OIM EI_M 1(1)

to obtain the IME I from the M S

Si gnal s to/from the right Send
are to/fr om the VLR IM EI
W ait_F or_
IM EI
Send IMEI
Se nd IM EI R elease
res ponse
R elease
transa ction
Provide
A bort
IM EI ack

Pass A borted
Figure 11: Procedure Obtain_IMEI_MSC
3GPP
Release 1999 42 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C heck_IM EI_M S C CIME I_M1(1)

Procedure in t he M SC to c heck the
IMEI and relay the res ult to t he VLR
Yes
IM EI
Signal s to/from the l eft av ai lable?
are to/from the BSS; No
signal s to/from the ri ght
are to/from the VL R
unless ma rked otherw ise.
Send IMEI
W ait_F or_
IM EI
CM Send IMEI
Send I MEI
servic e negative
ack
abort response
R elease
transacti on Ch eck IM EI To EIR
W a it_for_
Abort C heck_IM EI_
Resu lt
C heck IMEI
R esult:= Rel eas e Ch eck IM EI
Aborted transaction negativ e F rom EIR ack From EIR
respons e
C heck IMEI Ch eck IM EI

Abort negativ e
ack
respons e
R es ult:= R esult:=
Aborted Pass
Figure 12: Procedure Check_IMEI_MSC
3GPP
Release 1999 43 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure E stablish_Originating_T CH _If_Required E OT CIR1(1)

Proc edure in the origi na ti ng VM SC Signals to /from the l eft
to es tablish a Traffic C hannel are to/from the BSS
if one ha s n ot been establi shed
for this c al l
True
TC H
allocated
False
Allocate R esult:=
c hannel Pass
W ait_For_
Al location_
C om plete
Release Allocation All ocation

transacti on failure com plete
R elease TC H all oc ated:=

trans action Tr ue
R esult:= R esult:=
F ai l Pass
Figure 13: Procedure Establish_Originating_TCH_If_Required
3GPP
Release 1999 44 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S et_CLI_P resentation_Indicator_M S C CA IND_M 1(1)

to determi ne the C LI
presentation i ndi cator v al ue
Si gnal s to/from the right

are to/fro m the proc ess
Initi ate
C LIR _M AF004
handli ng
of C LIR
W ait_F or_
C LIR_Info
C onti nue
R elease C lear
From BSS cal l
transac tion c all
handling
R esul t:= R esult:=

C all not C all
allow ed all owed
Figure 14: Procedure Set_CLI_Presentation_Indicator_MSC
3GPP
Release 1999 45 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure S end_A lerting_If_Required S ALT IR 1(1)

Procedure to s end an Sign al s to the l eft
Aler ting mess age to the MS are to the B SS
if one is req uired for thi s cal l
True
Al erting sent
Fals e
True A ccess
C onnect
s ent
Fals e
Ye s
Bac kward call indicator=
no indication?
No
U US_MSC _ U U S_OC H_Set_

See TS 23.087 Check _ A lert_And_ See TS 23.087
U US1_U UI C onnect_Param
No
R esul t=
P as s?
Yes
Progres s A lerti ng
A lerting s ent:=
True

Pas s F ai l
Figure 15: Procedure Send_Alerting_If_Required
3GPP
Release 1999 46 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S et_CO LP _Info_M S C CO INF_M 1(1)

to determi ne the C OLP
inform ati on to be s ent to the M S
Si gnal s to/from the right

are to/fro m the proces s
Initi ate
C OLP_M AF 006
handli ng
of C OLP
W ait_F or_
C OLP_Info
C ontinue From
Re lease
From BSS c all R elease desti nation
transac ti on
handli ng exchange
Figure 16: Procedure Set_COLP_Info_MSC
3GPP
Release 1999 47 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure H andle_A oC_M O_MSC A oC M O_M 1(1)

to handle AoC signalling
tow ards the M S for an M O call
Ye s
A oC(I)
provi sioned?
No
Set
charging
param eters
No
AoC (C )
provi sioned?
Yes
S et
c harging
pa ram ete rs
Ack now ledgment A cknow ledgment

required:= required: =
Fals e True
Figure 17: Procedure Handle_AoC_MO_MSC
3GPP
Release 1999 48 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Se nd_Access_Connect_If_R equired SA CO NIR1(1)

Proc edure to s end a Signal s to/from the l eft
C onnect m essage are to/from the BSS;
to the MS signals to/from the ri ght
if one is req uired for thi s cal l are to/from the destination exc hange
T rue Fal se
MS
c onn ec ted
U U S_O CH _
Set_Alert_An d_ See TS 23.087
C onnect_Par am
Faci lity C onnect
No No
Acknow ledgm ent Ac knowledgm ent
required? req ui red?
Yes Yes
Sta rt AoC Start AoC

acknow ledgme nt ack now ledgm ent
timer tim er
W ai t_For_ W ait_For_
Ao C_Ac k_F AoC _Ack_C
Charging AoC C hargi ng Ao C

Rel eas e R elease Connect
Param eters transac tion a cknowledgment Parameters tra ns action Ack acknow ledgm ent
ack timer expired ac k tim er expired
R elease Releas e
transaction transac ti on
R elease Re lease
R esult:= R esult:=
R esu lt:= R esult:=
Faci lity C onnec t
F ail Fai l
sent s ent
Figure 18: Procedure Send_Access_Connect_If_Required
3GPP
Release 1999 49 3GPP TS 23.018 V3.12.0 (2003-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 2: the process Subscriber_Present_VLR is described in 3GPP TS 29.002 [28].
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 [22].
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 [24]. 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 1999 50 3GPP TS 23.018 V3.12.0 (2003-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 MAF019, 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 1999 51 3GPP TS 23.018 V3.12.0 (2003-03)
Process O CH _V LR OC H_VLR 1(1)

Proc es s in the VLR
to handle an outgo ing
(M O) c all s etup request

are to/fro m the MSC.
Idle
P rocess
A ccess
R eques t
P rocess _
A ccess _
R eques t_VLR
No
R esul t=
Pas s
Yes
W ait_F or_
Idle
S IF OC
S end Info
F or Outgoing Abort
C all
Yes
E mergency
Idle
c all?
No
Com plete O G_Call_

S ubs cri ption_
C al l
C heck _VLR
Idl e Idle
Figure 7.1.2.1: Process OCH_VLR
3GPP
Release 1999 52 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P rocess_Access_Reque st_VLR PA R_V LR1(5)

Procedure i n t he VLR
No
Identity
k now n?
Yes
Obtain_
Identi ty_VLR
Yes
R esult=
Pass?
No
Yes No
Id entity = R esult=
IM EI? Fail?
No
Yes
No
Authentication
required?
Yes
Authentic at e_
VLR
No
R esul t=
P as s?
Yes
IM SI
detached:=
Fa lse
C onfir med by Set negative Set negativ e

R es ult:=
R adio Contact:= r esponse: res pon se:
Aborted
True Sys tem U nidentifi ed
F ailure Subsc riber
2 1 3 3
Figure7.1.2.2a: Procedure Process_Access_Request_VLR (sheet 1)
3GPP
Release 1999 53 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Process_Access_Request_VLR PAR_VLR2(5)

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 1999 54 3GPP TS 23.018 V3.12.0 (2003-03)

to handle a reques t from 4 5
Si gnal s to the l ef t
are to the M SC .
Sta rt
securi ty
procedures
Identity:=
IMSI
Proces s
Access
Request ack
No
IME I c hec k
requi red?
Yes
Check _
IM EI_VLR
No
Res ult=
Pass?
Yes
TM SI No No
R esult=
reallocation Fail?
required?
Yes Yes
C C BS_R eport_
See TS 23.093
M S_Ac tivity
U se IM SI
Forward
N ew TM SI E xisti ng detac hed :=
T MSI Tr ue
Freeze Set negativ e

R esul t:= R es ult:=
exis ti ng res pon se:
Pas s Aborted
TM SI Illegal
Equipm ent
W ai t_For_
3
TM SI_Ack
Figure 7.1.2.2c: Procedure Process_Access_Request_VLR (sheet 3)
3GPP
Release 1999 55 3GPP TS 23.018 V3.12.0 (2003-03)

Si gnal s from the left W ait_For_

are from the M SC. 2
TM SI_Ack
Yes
Res ult=
Aborted? Forward Forward
No N ew T MSI N ew TM SI
R esu lt:= ack negati ve
A borted res ponse
Res ult= Yes

Procedur e
Error? U nfreeze
existing
No Set negative T MSI
response:
Sy stem
Res ult= Yes F ailure
U nk nown
Subscriber? C CBS _R eport_
See T S 23.093
No M S_Activ ity
Res ult= Yes

U ni dentified
Subscriber? R esult:=
No Set negative Pass
response:
U ni de nti fied
S ubs cri ber
Set negative
response:
I llegal
S ubs cri ber
Figure 7.1.2.2d: Procedure Process_Access_Request_VLR (sheet 4)
3GPP
Release 1999 56 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he VLR
to handle a reques t from 3
the M S for system access
Signal s to the lef t

are to the M SC . No
C M s ervice type
=Em erge nc y call?
Yes
Emerg enc y call

setup allowed
w ithout S IM?
No
Yes
No
IM EI
r equired?
Yes
O btai n_
IM EI_VLR
No
R esul t=
P as s?
Yes
Yes
Identity:= R esult=
IM EI F ail?
No
P rocess Pro cess Ac cess

A ccess Re ques t
R eques t ac k negati ve
res ponse
C C BS_R eport_
See TS 23.093
M S_Ac tivity
R esul t:= R esult: = R esult:=

Pas s Aborted Fail
Figure 7.1.2.2e: Procedure Process_Access_Request_VLR (sheet 5)
3GPP
Release 1999 57 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure OG _Call_Subscription_Check_VLR O CS CVLR 1(2)

to perf orm subscriptio n
checks for an outgoi ng call

are to the M SC No
Bas ic
s ervi ce
provis ioned?
Yes
Set negativ e
C heck _O G_ Bearer servic e
See T S 23.135 re sponse:
M ulti call_VLR or telese rvi ce
Basic servic e
not provi sioned
No
R esul t=
P as s?
Yes
C heck_
B AO C
R esul t= Yes
C al l
barred?
No
Set negativ e
OG _C U G_
re sponse:
C heck
C all barred
R esul t= No
C al l
al low ed?
Yes
Get_LI_ Set negativ e

S ubs cri ption_ re sponse:
Info_MO_VLR C UG reject
G et_AoC _
S ubs cri ption_
Info_VLR
U U S_OC H_
C heck_
Provis ion
No
R esul t=
P as s?
Yes
Send In fo
For Outgo ing
Cal l negative
res ponse
Figure 7.1.2.3a: Procedure OG_Call_Subscription_Check_VLR (sheet 1)
3GPP
Release 1999 58 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure OG _Call_Subscription_Check_VLR O CS CVLR 2(2)

Procedure in t he VLR Signals to the left
to perf orm subscriptio n are to the MS C
checks for an outgoi ng call 1
C AMEL_
See TS 23.078
OC H _VLR
Yes
R esult=
F ail?
No
C heck _O G_
Barri ng
Yes
C al l
barred?
No
Set negativ e
res ponse:
C all barred
Send Info
C om plete
For Outgoing
C al l
C all negative
res ponse
Figure 7.1.2.3b: Procedure OG_Call_Subscription_Check _VLR (sheet 2)
3GPP
Release 1999 59 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Obtain_Identity_VLR OID_VL R1(1)

to obtain the identity of an MS
Yes
Identity =
IM SI?
No
Identifi cation
al low ed?
No
Yes
O btai n_
IM SI_VLR
No
R esul t=
P as s?
Yes
No
IM SI
k now n?
Yes
R es ult:= R esul t:= R esult:=

Fail Pas s Abort ed
Figure 7.1.2.4: Procedure Obtain_Identity_VLR
3GPP
Release 1999 60 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure O btain_IMS I_V LR O IM S I_V 1(1)

Proces s in the VLR
to obtain the IMS I
from the MS v ia the M SC
Signal s to/from the l eft

are to/fro m the M SC.
P rovi de
IM SI
W ait_F or_
IM SI
Provide
IM SI ack Abort
Pass Aborted
Figure 7.1.2.5: Procedure Obtain_IMSI_VLR
3GPP
Release 1999 61 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Au thenticate_V LR A UT _VLR1(2)

to authentic ate an MS
via the MS C

are to/fro m the M SC. Yes
Auth enti cation
sets available?
No
O btai n_
A uthentic ation_
S ets _VLR
No
R esul t=
P as s? 2
Yes
Yes
Res ult=
Authenticate
Aborted?
No
Yes Res ult= W ait_F or_

R esult:=
Pr ocedure Authentic ate_
Aborted
Error? R esult
No
R es ult:= R es ult:= Authenticate

Authenticate
Procedure U nk nown ac k negative Abort
Error Subscriber re spons e
No Authentication
R eceived SR ES=
fail ure
ex pec ted SR ES?
re port
Yes
Mo re No More No
authentic ation auth entication
sets needed? sets needed?
Yes Yes
F etch_ Fetch_
A uthentic at ion_ Authenti cation_
S ets _VLR Sets_VLR
Authenticati on
ac cepted
R esult:= R es ult:=
Pas s Aborted
Figure 7.1.2.6a: Procedure Authenticate_VLR (sheet 1)
3GPP
Release 1999 62 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Au thenticate_V LR A UT _VLR2(2)

to authentic ate an MS 1
via the MS C

are to the M SC . Yes
Identity=IM SI?
No
R etry No
w ith
IMSI?
Yes
O btain_
IMSI_VLR
No
R esult=
P as s?
Yes
No
IMSI
k now n?
Yes
IMSI Yes
m atches
T MS I?
No
Authentica ti on Authentic ation

accepted rejected
Authentic ation
failure
report
R es ult:= R es ult:= Identity:= R es ult:=

Aborted U nidentified IMSI Ill ega l
Sub scriber Subscriber
Figure 7.1.2.6b: Procedure Authenticate_VLR (sheet 2)
3GPP
Release 1999 63 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure O btain_Authentication_ Sets_V LR O AS_ VLR1(2)

to obtain authentication
sets from the HLR
Signal s to/from the right

are to/from the HLR
Send
Authenticati on
Info
W ait_F or_
A uthentic at ion_
S ets
Send Send
Authentic ation Authenti cation
Info ac k Info negative
res po ns e
Yes No
Em pty U nknown
res ult? Subsc ri ber?
No Yes
Authentic ati on No
sets available
in VLR ?
Yes
Yes R e-us e No
o ld
s ets ?
R es ult:= R esult:= R esult:=

Procedure U nknown
Pass
Error Subsc riber
Figure 7.1.2.7a: Procedure Obtain_Authentication_Sets_VLR (sheet 1)
3GPP
Release 1999 64 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure O btain_Authentication_ Sets_V LR O AS_ VLR2(2)

to obtain authentication
sets from the HLR
Signal s to/from the l eft W ait_F or_

are to/fro m the M SC; A uthentic ation_
Signal s to/from the right S ets
are to/from the HLR
Abort Abort
No
Authentic ati on
Abort sets avail able?
Yes
Yes R e-use No
old
se ts?

Proc edure
Aborted Pas s
Error
Figure 7.1.2.7b: Procedure Obtain_Authentication_Sets_VLR (sheet 2)
3GPP
Release 1999 65 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S tart_T racing_VLR S T _T R _V 1(1)

to requ es t the M SC to
start activ ity traci ng

are to the M SC . No
T racing
ac tive?
Yes
T race
S ubs criber
Act ivity
Figure 7.1.2.8: Procedure Start_Tracing_VLR
3GPP
Release 1999 66 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C heck_IM EI_V LR CIME I_V1(1)

to requ es t the M SC to
check an IM EI

are to/fro m the MS C
C heck
IM EI
W ait_F or_
C heck _IMEI_
R esult
C heck
Check
Abort IM EI negat ive IM EI ack
response
No
Serv ice
gran ted?
Yes

Aborted F ail Pass
Figure 7.1.2.8: Procedure Check_IMEI_VLR
3GPP
Release 1999 67 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure O btain_IME I_V LR O IM E I_V 1(1)

Proces s in the VLR
to obtain the IMS I
from the MS v ia the M SC

P rovi de
IM EI
W ait_F or_
IM EI
Provide
IM EI ack Abort
Pass Aborted
Figure 7.1.2.9: Procedure Obtain_IMEI _VLR
3GPP
Release 1999 68 3GPP TS 23.018 V3.12.0 (2003-03)
Process Fetch_Au thentic ation_Sets_V LR F AS _VLR 1(1)

Proces s in the VLR
to retriev e authentica tion
sets from the HLR
O biain_
A uthentic ation_
S ets _VLR
Figure 7.1.2.10: Process Fetch_Authentication_Sets_VLR
3GPP
Release 1999 69 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C heck_B AOC CB A OC 1(1)

Proc edure to c hec k call
request against OD BAOC
and SS BAOC

are to/fro m the proces s Ye s
M AF017 O perator determined BAO C
impos ed?
No
R es ult:= Initi ate

Call barred handling
(OD B) of BAO C
W ait_F or_
B AOC_
R esponse
C ontinue
From MS C Abort c all
handling
Ye s
C all
ba rred?
No
R es ult:=
R esult:=
Call barred C all allow ed
(SS barring )
Figure 7.1.2.11: Procedure Check_BAOC
3GPP
Release 1999 70 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure O G_CU G_Check OG _C UG 1(1)

Procedure to carry out
CU G authori sation check
for an outgoi ng (M O) c all

outgoing
C UG _M AF 014
c al l
requ es t
W ait_For_
C U G_Re spons e
r esponse com plete cal l rejec t

From MS C Abort to cal l (conditi onal call
r eques t C U G info) (c aus e)
R esult := R esult:=
C all al low ed Ca ll barred
Figure 7.1.2.12: Procedure OG_CUG_Check
3GPP
Release 1999 71 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure G et_LI_Subscription_Info_M O_VLR G LI_MO V 1(1)

to retrieve subscription
inform ati on for the C LIR
& C OLP line identifi cation
servi ces for an M O c al l
Initi ate
handl ing T o process CLIR _M AF003
of C LIR
W ait_F or_
C LIR_Info
C ontinue
From MS C Abort c all F rom process CLIR _M AF003
handli ng
Initi ate
handl ing T o process CO LP_M AF 005
of C OLP
W ait_F or_
C OLP_Info
C ontinue
From MS C Abort c all F rom proc es s C OLP_M AF005
handli ng
Figure 7.1.2.13: Procedure Get_LI_Subscription_Info_MO_VLR
3GPP
Release 1999 72 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure G et_AoC_S ubscription_Info_V LR GA OC I_V 1(1)

to determi ne the subs cri ption
to Adv ice of C harge s erv ices
Yes
A oC(I)
provisioned?
No
No
AoC (C )
provisioned?
Yes
Set indicator: S et i ndicator: Set indic ator:

AoC not A oC (C) AoC (I)
prov isi oned provisioned provis ioned
Figure 7.1.2.14: Procedure Get_AoC_Subscription_Info_VLR
3GPP
Release 1999 73 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C heck_OG _B arring CO B 1( 3)

request against SS barring
and OD B c ategori es
Yes
Operator determ ined
BOIC imposed?
No No
Desti na tion address C C =
Loc al C C?
Yes
Yes
BOIC -exH C im posed?
Yes No
Loc al C C?
No
1
No
HPLM N CC ?
Yes
Yes
BOIZC imposed?
No No
Dest ination address Z C =
Local ZC ?
Yes
Yes
BOIZC -exHC i mposed?
Yes No
Dest ination address Z C =
Local ZC ?
No
1
No
HPLM N CC ?
Yes
R esult:=
C all barred
(O DB)
Figure 7.1.2.15a: Procedure Check_OG_Barring (sheet 1)
3GPP
Release 1999 74 3GPP TS 23.018 V3.12.0 (2003-03)

request against SS barring 1
No Operato r deter mined

BO IC - exHC &BOIZ C
impos ed?
Yes
2
Yes
D esti nati on address ZC =
Loc al ZC ?
No
Yes
D esti nati on addres s C C =
Local CC ?
No
2
No
D esti nati on addres s C C =
H PLM N C C ?
Yes
R es ult:=
Cal l barred
(O DB)
Figure 7.1.2.15b: Procedure Check_OG_Barring (sheet 2)
3GPP
Release 1999 75 3GPP TS 23.018 V3.12.0 (2003-03)

2
Yes
C al l
barred?
No
Initiate
handli ng T o process M AF 018
of BOIC
W ait_Fo r_
B OIC_
R esponse
C ontinue
Fr om MSC Abo rt c al l F rom proces s M AF018
handli ng
Yes
C al l
barred?
No
Initiate
handli ng T o process M AF 020
of BOIC -exH C
W ait_Fo r_
B OIC-exHC _
R esponse
C ontinue
Fr om MSC Abo rt c al l F rom proces s M AF020
handli ng
Yes
C al l
barred?
No

Ca ll barred
C all allow ed
(SS barri ng)
Figure 7.1.2.15c: Procedure Check_OG_Barring (sheet 3)
3GPP
Release 1999 76 3GPP TS 23.018 V3.12.0 (2003-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.16: Process Update_Location_VLR
3GPP
Release 1999 77 3GPP TS 23.018 V3.12.0 (2003-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 [36]) is shown in table 1. The mapping used is a matter
for the network operator, depending on the telephony signalling system used.
Table 1: Suggested mapping of Send Routeing Info (SRI) negative responses to ISUP release causes
SRI negative response ISUP release cause number ISUP release cause name
Absent subscriber 20 Subscriber absent
Bearer service not provisioned 57 Bearer capability not authorised
Call barred (ODB) 21 Call rejected
Call barred (SS barring) 21 Call rejected
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 authorised
Unexpected data value 111 Protocol error, unspecified
Unknown subscriber 1 Unallocated (unassigned) number
26 Misrouted call to a ported number (note)
3GPP
Release 1999 78 3GPP TS 23.018 V3.12.0 (2003-03)
NOTE: 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.
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 partys 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 partys status field of the
Backward call indicator set to "no indication".
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_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 [22].
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 [22].
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.
3GPP
Release 1999 79 3GPP TS 23.018 V3.12.0 (2003-03)
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 [22].
Sheet 1: the procedure CLI_MT_GMSC is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14].
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 CAMEL_MT_GMSC_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12].
Sheet 3: the procedure CAMEL_MT_GMSC_Notify_CF is specific to CAMEL phase 2 or later; it is specified in 3GPP
TS 23.078 [12]. If the GMSC does not support CAMEL phase 2 or later, processing continues from the "Continue" exit
of the test "Result".
Sheet 3: the procedure CCBS_MT_GMSC_Check_CCBS_Indicators is specific to CCBS; it is specified in 3GPP

TS 23.093 [22].
Sheet 3: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal
Routeing.
Sheet 3: 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 3: the procedure MNP_MT_GMSC_Check_MNP_Indicators is specific to Mobile Number Portability; it is

Sheet 4: the task "BOR:=OR" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.
Sheet 4: the procedures CCBS_MT_GMSC_Remove_Indicators_Store_FWT is specific to CCBS; it is specified in

3GPP TS 23.093 [22].
Sheet 4: 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 4: the procedure CAMEL_MT_MSC_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP

TS 23.078 [12].
Sheet 4: the procedure CAMEL_MT_GMSC_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS
23.078 [12].
Sheet 4: the task "OR:= True" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.
7.2.1.3 Procedure Send_ACM_If_Required

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

3GPP
Release 1999 80 3GPP TS 23.018 V3.12.0 (2003-03)
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?".
Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is


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 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later; they
are specified in 3GPP TS 23.078 [12].
Sheet 2: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If
the MSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 2: the procedure UUS_MSC_Clear_UUS is specific to UUS; it is specified in 3GPP TS 23.087 [20].
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.
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?" .
Sheet 5: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports
CAMEL.
3GPP
Release 1999 81 3GPP TS 23.018 V3.12.0 (2003-03)
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
7.2.1.9 Macro CUG_Support_Check_GMSC
3GPP
Release 1999 82 3GPP TS 23.018 V3.12.0 (2003-03)
Process MT_GMSC MT_GMSC1(7)

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
Idle unless marked otherwise
Initial
1
Address
CUG_Support_
Check_GMSC ACM sent:=False
Fail Reconnect:=
Pass Answer sent:=False True
Network connect sent:=False
Reconnect:=False
Resume call:=False
UU S CF Interaction:=False
MNP_MT_GMSC_
Set_MNP_ See TS 23.066
Parameters
OR_Set_ORA_
See TS 23.079
Parameters
CAMEL_Set_
See TS 23.078
ORA_Parameters
Obtain_Routeing_Address
(Called party address, Reference address,
OR, Own PLMN, Routeing address,
Destination address, Result)
Yes
Result=
Forward?
No
Yes
Result=
Fail?
No
Set
cause Result= Yes
Routeing
number?
No
Release
Yes Initial Address Initial Address

Result=
(Routeing (Routeing To process MT_CF_MSC
Aborted?
Address) Address)
No
Initial Address CAMEL_Store_
(Routeing Destination_ See TS 23.078
Address) Address
(OR, False)
Release CAMEL_Store_ Send_ACM_ Send_ACM_ To originating

call Destination_ See TS 23.078
If_R equired If_Required exchange
resources Address
(OR, False)
Wait_For_ Wait_For_ Wait_For_

Idle
ACM ACM Forward_ACM
Figure 35a: Process MT_GMSC (sheet 1)
3GPP
Release 1999 83 3GPP TS 23.018 V3.12.0 (2003-03)
Process M T _GM S C M T _GM S C2(7)

Proces s in the GMS C to W ait_ For_ Signal s from the right are
handle a mobile-terminated AC M from the destinati on exc hange
call reques t
A ddress
C onn ec t
C omplete
S end_AC M_
If_R equired
C AMEL_
See TS 23.078 S tart_TN R y
W ait_ For_
A ns wer
A ns wer
C AMEL_
See TS 23.078
S top_T N Ry
C AMEL_M T_ C AMEL_MT _
See TS 23.078 GM SC _AN SW ER GM SC _ANSW ER See TS 23.078
Fail R econnectRec onn ec t F ail

R esult? R esult?
Pass Pa ss
Idle 1 Idle
S et dest ination Set destin ation

a ddress addres s
p aram et er parameter
Send_Ne twork _
S end_Ans wer_
If_R equired C onn ect_If_
R equ ired
W ait_For_
C lear
Figure 35b: Process MT_GMSC (sheet 2)
3GPP
Release 1999 84 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the GMS C to
handle a mobile-terminated
W ait_ For_ Signals f rom the right are
call reques t
Forward_ACM from the proc ess MT_CF_MSC
A ddress
Connect
Complete
S end _ACM_
If_Required
W ait_ For_
Forward_
A ns wer
A ns wer
CAMEL_MT_ CAMEL_MT_
See TS 23.078 See TS 23.078
GMSC_ANSWER GMSC_ANSW ER
Fail Reconnect Rec onnect Fail

Result? Result?
Pass Pas s
Handle_COLP_ Handle_COLP_
Idle Forwardin g_ 1 Forwarding_ Id le
Interac tion_MSC Interaction_MSC
Set COLP Set CO LP

presentation pres entation
indicator indicator
S et des tination Set destination

a ddress addres s
p arameter parameter
S end _Ans wer_ Send_Network_

Conne ct_ If_
If_Required
Required
W ait_For_
Clear
Figure 35c: Process MT_GMSC (sheet 3)
3GPP
Release 1999 85 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the GMS C to W ait_For_ACM , Signal s to/from the right
handle a mobile-terminated W a it_For_ Ans wer are to/from the destinatio n M SC
call reques t unless m arked otherwi se
R esume
R efer to TS 23.079 for
C all
m ess age co ntents
H andli ng
C C BS_MT _GMSC_
C heck_C C BS_ See TS 23.093
P os sible
R esum e call :-
True
OR _H andl e_
See TS 23.079
RCH
Yes
R esul t=
F ail?
No
Yes
R esul t=
R efuse?
No
Yes
R esul t=
R econnect?
No
W ait_Fo r_
- 1 Idle
F orw ard_AC M
Figure 35d: Process MT_GMSC (sheet 4)
3GPP
Release 1999 86 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the GMS C to W ait_Fo r_ Signal s t o/from the left
handle a mobile-terminated A ns wer are to/from the originat ing MSC;
call reques t signals to/from the right
are to/from the destinatio n M SC
unless m arked otherwi se
T N Ry
Internal
expi red
2 R elease
C AM EL_M T_
G MS C_D ISC5 See TS 23.078
R elease R econnect
R esul t?
Con tinue,
Fail
Releas e
R eleas e c al l
resourc es
Idle 1
Figure 35e: Process MT_GMSC (sheet 5)
3GPP
Release 1999 87 3GPP TS 23.018 V3.12.0 (2003-03)
Process MT_GMS C MT_G MSC 6(7)

Proces s in the GMS C to Signals to/from the left
handl e a mobile-terminated are to/from the originat ing exchange;
call reques t signal s to/from the right
W ait_For_ACM, are to/from the destination exc hange
W ait_For_Forward_A CM, or process MT_ CF _MS C
W ait_For_Answer, unless marked otherwi se
W ait_For_Forward_A ns wer
In t_Releas e_
Releas e Release From gsmSSF
Call
CCBS_MT _GMSC_
Check_CCBS_ See TS 23.093
P os sible
CAMEL phase 2 CAMEL phase 2

or higher or higher
supported? s upport ed?
No Yes No Yes
Yes
Release c aus e=
No an swer from user?
No
CAME L_MT _ CAMEL_MT_ CAMEL_MT_ CAMEL_MT _

GMSC_DISC3 GMSC_DISC6 G MSC_DISC3 G MS C_DIS C4 See TS 23.078
No
Result=
Releas e
Reconnect?
Yes
CCBS_Set_
Diagn ostic_
For_Release
Releas e Release 1 Releas e
Releas e c all
resourc es
Idle
Figure 35f: Process MT_GMSC (sheet 6)
3GPP
Release 1999 88 3GPP TS 23.018 V3.12.0 (2003-03)

Process in the GMSC to Signals to/from the left
handle a mobile-terminated Wait_For_ are to/from the originating exchange;
c all r equest Clear signals to/from the right
are to/from the destination exchange
or the process MT_CF_MSC
unless marked otherwise
Int_Releas e_
Release Release From gsmSSF
Call
CAMEL_MT_ CAMEL_MT_
See TS 23.078 See TS 23.078
GM SC_DISC1 GM SC_DISC2
Yes Reconnect CAMEL handling

Result=
CAMEL Result? Release
handling?
No Normal handli ng
Release 1 Release Release
Release call
resources
Wait_F or_
Idle
Clear
Resume W ait_For_ACM,
Call W ait_For_Forward_AC M,
Handling W ait_For_Answer,
W ait_For_Forward_Ans wer,
W ait_For_Clear
Set negativ e
response: OR * *
not allowed
Resume Call
Handling - -
negative
response
Wait_F or_
-
Clear
Figure 35g: Process MT_GMSC (sheet 7)
3GPP
Release 1999 89 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure O btain_Routeing_Address O RA1(4)

Procedure in a G MSC Procedure Obtain _Routeing_Addres s
to determine the address FPA R IN I nput addres s, Referen ce address ,
to whic h a call should be routed Own P LMN
IN/OUT Rou teing address,
Destination address , OR, Result
MOB ILE_NUMB ER_

See TS 23.066 P ORTABILITY_
IN_TQo D
Result= Yes
Number
ported?
No
CCBS_MT_ Ro uteing
See TS 23.093 GMSC_Ch ec k_ addres s:=
CCBS_Call routein g number
True Result:=
Reconnect Ro uteing
numbe r
Fals e
CLI_MT_
See TS 23.081
G MS C
Pre-paging
s uppo rted
in GMSC?
No Yes
S et Pre-paging
s uppo rted
S end
To HLR Routeing
Info
W ait_for_
Routeing_ 1
Info
Figure 36a: Procedure Obtain_Routeing_Address (sheet 1)
3GPP
Release 1999 90 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure O btain_Routeing_A ddress O RA 2( 4)

Procedure in a G MSC Si gnals to/from the l eft
to determi ne the address are to/from the ori ginating exchange;
W ait_for_
to w hic h a cal l should be routed si gnals to/from the ri ght
R outeing_ are to/from the HLR
Info
Send
Releas e R outei ng
Info negative
response
OR _H andl e_SR I_
R es ult:=
N egative_R esponse See TS 23.079
Aborted
(Ow n P LM N )
Yes
R esul t=
P as s?
No
No E rror =
U nknow n R esult:= Pas s
s ubs cri ber?
Yes
M OB ILE_N U MB ER_
See T S 23.066 P ORT ABILITY_
IN _QoH R
N o R esul t=
N um ber
ported?
Yes
R outeing
addr ess:=
routeing num ber
R esul t:=
R es ult:=F ail R outeing
num ber
Figure 36b: Procedure Obtain_Routeing_Address (sheet 2)
3GPP
Release 1999 91 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Obtain_Routeing_Address Wait _for_

ORA3(4)
Routeing_
Proc edure in a G MSC Inf o
t o determine the address
t o whic h a call s hould be routed
Send
Routeing From HLR
Inf o ac k
CAMEL
1
supported?
No Yes
No MSR N CAMEL_MT_
See TS 23. 078 3
recei ved? GM SC_INIT
Yes
Yes
Result=
3
MSR N
No CCBS_MT _
GM SC_Check_ See TS 23. 093
CCBS_
Indicators
Yes Result=
Aborted
Store Forwarding
Result:= No Int errogat ion
Aborted Required
indicat or
No
MSRN contains
a Rout ei ng number?
No Yes
Result=
Fail
CAMEL_FTN
MNP_MT _GMSC _ Routeing
Yes Check_MNP_ address :=
Result See TS 23. 066
Indicators MSRN
GSM_FTN
Yes
CAMEL_
MT_G MSC_ Result=
See TS 23. 078
Notify_C F Fail?
No
Continue Fail
Routeing Destination
Result address: = address :=
MSR N VMSC address
Reconnect
Result:=
Recpnnect := Result:= Routeing Result: =
True Fail number Pass
2 1
Figure 36c: Procedure Obtain_Routeing_Address (sheet 3)
3GPP
Release 1999 92 3GPP TS 23.018 V3.12.0 (2003-03)
Pro c e d u re O bta in _ R o u te in g_ A dd r e ss O R A 4( 4)
Pr ocedure in a G MS C
to de term i ne the add ress
to w h ic h a cal l should be r outed 2
BO R:=O R
A ctiv ate_
C F_ Proces s
Y es
R esu lt=
F ail?
No
C C B S_MT _
R esult:=
GM S C _R emov e_ See TS 23.093 A borted
Indic ators_
S tor e_FW T
R oute_Perm itted
( OR ,F TN , See TS 23.079
R eference
A ddr ess)
Fal se
R oute
pe rm itted
C A ME L phase 2
Tr ue
or hi gh er
su ppor ted?
No Y es
C A M E L_MT _ C AME L_M T _
Se e T S 23.078 GM SC _D ISC 3 G M S C _DIS C 4 S ee T S 23.0 78
T o p rocess CF
M T_ CF _MS C cancel led
R outeing R outei ng
addr ess:= addres s:=
F TN R efere nce
addres s
D esti nation D estin ation

addr ess:= addres s:=
F TN R efere nce
addres s
OR :=T rue OR :=Fals e
R esu lt:= R esult:=

F orw ard P ass
Figure 36d: Procedure Obtain_Routeing_Address (sheet 4)
3GPP
Release 1999 93 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S end_A CM_If_Required S AC M IR 1(1)

Procedure to send an Sig nal s to the left
Address C om plete M es sage are to the originating ex change
to the precedi ng exc han ge i f
one i s requi red for this call
True
AC M
s ent
Fals e
True N etwork
c onn ec t
s ent
Fals e
C all A ddr ess

Progres s C om plete
A CM sent:=
True
Figure 37: Procedure Send_ACM_If_Required
3GPP
Release 1999 94 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S end_A nsw er_If_Required S AN M IR 1(1)

Procedure to send an Sig nal s to the left
Ans wer M es sage are to the originating ex change
True
A ns wer
s ent
False
True N etwor k
c onnect
s ent
False
C al l
Progres s Answ er
Ans wer s ent:=

True
Figure 38: Procedure Send_Answer_If_Required
3GPP
Release 1999 95 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S end_N etwork_Connect_If_Required S NCO NIR1(1)

Proc edure to s end a Sig nal s to the left
C onnect M essage are to the originating ex change
True N etwork
c onne ct
s ent
Fals e
True
A ns wer
s ent
Fals e
AC M
s ent
True
Fals e
C al l
Ans wer C onnec t
Progress
An swer sent:= C onnect sent:=

True True
Figure 39: Procedure Send_Network_Connect_If_Required
3GPP
Release 1999 96 3GPP TS 23.018 V3.12.0 (2003-03)
Pro cedure H andle_C OLP_F orwarding_Interaction_MS C CO IN T_M 1(1)

Procedure in t he GM SC or VMSC
to handle the intera ction betw een
COLP and Ca ll F orw arding
Signal s to/from the right Initi ate

are to/fro m the proces s handli ng
C OLP_M AF 039 of C OLP
W ait_F or_
C OLP_Info
c onti nue
From origi nating exc han ge
Re lease or desti nati on ex change c all
handli ng
Figure 40: Procedure Handle_COLP_Forwarding_Interaction_MSC
3GPP
Release 1999 97 3GPP TS 23.018 V3.12.0 (2003-03)
Pro cedure A ctivate_CF _P rocess AC F P1(1)

Procedure in t he MSC Signal s to/from the l eft
to i nitiate the p rocess whic h are to/from the origi nating exchange;
handles call forw ardi ng si gnals to/from the ri ght
are to/from the pr oc ess M T_C F_M SC
unless m arked othe rw ise
P erform c all
forwarding
(BOR , FTN )
W ait_F or_
C F_R esponse
Perform call
Perform c all Int_R el eas e_
Releas e forw arding ack forwardi ng C all From gsmSSF
negative
respons e
CF
Re lease
cancelled
CF
cancelled
R es ult:= Resu lt:= R esul t:= R esult:=

Fai l Pas s F ail Fail
Figure 41: Procedure Activate_Call_Forwarding_Process
3GPP
Release 1999 98 3GPP TS 23.018 V3.12.0 (2003-03)
Process M T _CF _M SC M T CF M S C1(5)

Proc es s in the MS C Si gnals to/from the l eft
to handle c all forwar di ng are to/from the parent proc ess;
si gnals to/from the ri ght
Idle
P erform c al l
forwarding
C AM EL_CF _
See TS 23.078
M SC _INIT
No
R esul t=
P as s?
Yes
C AM EL_CF _
See TS 23.078
D ialled_Serv ices
A bort F ai l
R esul t?
Pass
P erform c al l No
C AMEL_ Res ult=
forwarding See T S 2 3.078
OC H _M SC 1 Fail?
ack (F TN )
Yes
No
W ait_F or_ R esult=
Idl e
IAM R econnect?
Yes
Ini tial CF Perform C all

1 2 Forwardi ng
Address cance lled
neg ati ve
response
M OBILE_NU M BER_ C AMEL phas e 2

See TS 23.066 POR TABILITY_ or hi gher
IN_O QoD supported?
Initial
Address
No Yes
CAM EL_Store_
C AMEL_OC H_ C AM EL_OCH _
See TS 23.078 Des tination_ See TS 23.078 See TS 23.078
M SC _D ISC 3 MSC _DISC 4
Address
(BO R, True)
W ai t_For_
Idle Idle
ACM
Figure 42a: Process MT_CF_MSC (sheet 1)
3GPP
Release 1999 99 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in the MS C W ait_For_ Si gnals to/from the l eft
to handle c all forwar di ng AC M are to/from the parent proc ess;
Address
Co nnect
Com plete
CAM EL_
See T S 23 .078
Start_TN R y
UU S_M SC_ U US _M SC _
Clea r_U US See T S 23 .087 Cl ear_U U S See T S 23.087
A ddr ess
C om plete
W ait _For_
Ans wer
Ans wer
CAM EL_
Stop _T N Ry See T S 23 .078
CAM EL_C F_ C AME L_C F_

See T S 23 .078 See T S 23.078
MSC _AN SW E R MSC_AN SW ER
No No
Resu lt= Re sult=
Pas s? Pass?
Ye s Yes
Yes
UU S_M SC_ R esult=
See TS 23.087 Clea r_U US R econnect?
No
A ns wer Co nnect
W ait _For_ W ait_For_

Idle 2
Clea r Cl ear
Figure 42b: Process MT_CF_MSC (sheet 2)
3GPP
Release 1999 100 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in the MS C Sig nal s to/from the l eft
W ait_For_A CM , si gnals to/from the ri ght
W ait_For_A ns wer are to/from the destinatio n exc hange
Int_O_
Rel eas e R elease F rom gsm SSF
Rel eas e
C AM EL phase 2 C AMEL phas e 2

or hi gher or hi gher
supported? s upporte d?
No Yes No Yes
Yes
R elease caus e=
N o an swer from user?
No
C AME L_O CH _ C AMEL_OC H _ C AM EL_OC H_ C AM EL_OC H_

M SC_D ISC3 MS C_D ISC4 MSC _D ISC 3 M SC 1 See TS 23.078
No
R esult =
R econnect?
Yes
C AM EL_
See TS 23.078 Releas e
Stop_TN R y
Releas e R elease 2 Rel eas e
R elease
c all
resourc es
Idle
Figure 42c: Process MT_CF_MSC (sheet 3)
3GPP
Release 1999 101 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in the MS C W ait_F or _ Sig nal s to/from the l eft
to handle c all forwar di ng A ns wer are to/from the parent proc ess;
are to/from the destinatio n exc hange
T N Ry
Internal
expired
3 R elease
C AM EL_OC H_
M SC 2 See TS 23.078 2
R elease R econnect
R esul t?
Fail
C AMEL_C F_
Releas e See T S 2 3.078 D ial led_
Serv ices
Abort Pass
R esult?
F ail
R elease C AMEL_
c al l See T S 2 3.078 1
OC H _M SC 1
r esourc es
Yes
R esult=
Idle
R econnect?
No
Perform Cal l
Forwarding 2
negative
res ponse
Idle
Figure 42d: Process MT_CF_MSC (sheet 4)
3GPP
Release 1999 102 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in the MS C Si gnals to/from the l eft
unless marked othe rw ise
W ait_Fo r_
C lear
Int_O_
Rel eas e R elease From gsmSSF
Re lease
C AMEL _O CH _ C AM EL_OC H_
Se e T S 23.078 See TS 23.078 Re lease
MS C_D ISC1 M SC _D ISC 2
Res ult= Yes Yes R esul t=

CA MEL C AM EL
H andl ing? H andling?
No No
Yes
R esul t=
R econnect?
No
Rel eas e R elease 2 Re lease
R elease
c all
resourc es
Idle
* *
- -
Figure 42e: Process MT_CF_MSC (sheet 5)
3GPP
Release 1999 103 3GPP TS 23.018 V3.12.0 (2003-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 43: Macro CUG_Support_Check_GMSC
3GPP
Release 1999 104 3GPP TS 23.018 V3.12.0 (2003-03)
7.2.2 Functional requirements of HLR
7.2.2.1 Process SRI_HLR

Sheet 1: the procedures Check_Parameters, Subscription_Check_HLR, Handle_OR_HLR_CF and CAMEL_HLR_INIT
can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info
negative response message. This negative response parameter is global data, accessible by the process SRI_HLR.
Sheet 1: the procedure Handle_OR_HLR_CF is specific to Support of Optimal Routeing; it is specified in 3GPP
TS 23.079 [13]. If the HLR does not support Optimal Routeing, processing continues from the "No" exit of the test
"Result=Forward?".
Sheet 1: the procedure CAMEL_HLR_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the HLR
does not support CAMEL, processing continues from the "No" exit of the test"Result=Fail?".
Sheet 2: the procedure First_Forwarding_HLR can set the negative response parameter which is used by the process
SRI_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global
data, accessible by the process SRI_HLR.
Sheet 2: the procedure 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 CCBS_Handling_HLR is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. 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: 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 4: the procedure PRN_Error_HLR can set the negative response parameter which is used by the process
SRI_HLR to construct the Send Routeing Info negative response message. This negative response parameter is global
data, accessible by the process SRI_HLR.
Sheet 4: the procedure Forward_CUG_Check is specific to CUG. If the HLR does not support CUG, processing
continues from the "Yes" exit of the test "Result=Call allowed?".
Sheet 4: 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 4: 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 4: 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 4: the procedure CAMEL_D_CSI_CHECK_HLR is specific to CAMEL phase 3 or later; it is specified in 3GPP
TS 23.078 [12].
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".
3GPP
Release 1999 105 3GPP TS 23.018 V3.12.0 (2003-03)
7.2.2.3 Procedure Subscription_Check_HLR

It is an implementation option to carry out the check for operator determined barring of incoming calls before the check
on provisioning of the requested basic service.
The 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 [22]. 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 [23]. 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 Procedure Derive_Requested_Basic_Service_HLR

The rules for deriving a Circuit-switched bearer capability from ISDN compatibility information or the MSISDN of the
B subscriber are specified in 3GPP TS 29.007 [29]. If a GSM bearer capability cannot be derived from the ISDN
compatibility information or the MSISDN of the B subscriber, the HLR applies a default basic service according to the
requirements of the operator.
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.
3GPP
Release 1999 106 3GPP TS 23.018 V3.12.0 (2003-03)
The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later; it is specified in

3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes"
exit of the test "Result = Pass?".
7.2.2.11 Procedure Handle_CFNRc

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

3GPP
Release 1999 107 3GPP TS 23.018 V3.12.0 (2003-03)
Proc ess SR I_HLR S RI_H LR1(4)

Proces s in the H LR to handl e Signals to /from t he left
a request for routeing inform ation are to/from the GM SC;
si gnals to/from the rig ht
are to/from the VLR
Idle
Send
R outei ng
Info
C heck_
Parame ters
No
R esul t=
P as s?
Yes
S ubs cri ption_

C heck_H LR
Yes
R esul t=
F ail?
No
See TS 23.079 OR _H LR_C F
Yes
R esul t=
F ail?
No
Yes
R esul t=
F orw ard?
No
C AM EL_
See TS 23.078
H LR _IN IT
Yes
R esul t=
F ail?
No
3 1 2 1
Figure 44a: Process SRI_HLR (sheet 1)
3GPP
Release 1999 108 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the H LR to handl e Signals to /from the l eft
a request for routeing inform ation 3 are to/from the GMSC;
are to/from the VLR
F i rst_
Fo rw arding_
H LR
Yes
R esult=
F ail?
No
Yes CA MEL_
R esult=
F orw ard? See TS 23.078 CS I_C heck_
HLR
No
C AM EL_ Yes Res ult=

See TS 23.078 C SI_C hec k_ 2 CSI
H LR activ e?
No
R esult=
C SI 4
Yes ac tive?
No
C C BS_H andl ing_

4 H LR See TS 23.093
Yes
R esult =
F orw ard
No
No
R esult =
OK
Yes
1 5 2 1
Figure 44b: Process SRI_HLR (sheet 2)
3GPP
Release 1999 109 3GPP TS 23.018 V3.12.0 (2003-03)

5
Proces s in the H LR to handl e Signals to /from the l eft
a request for routeing inform ation are to/from the GMSC;
are to/from the VLR
OR _H LR_
See TS 23.079
Interrogate _VLR
Yes
R esul t=
F ail?
No
Yes
R esul t=
F orw ard?
No
Yes
GS M BC =
N U LL?
No
S et
G SM BC
parameter
A lerting No
P attern
required?
Yes
S et
A lerting
P attern
C LI_HLR _
See T S 23.081
S et_C LI
Pre-pagi ng
supported
in HLR ?
Yes No
Pre-pagi ng No
supported
in GMSC?
Yes
S et Pre-paging
s uppo rted
P rovi de
R oami ng
N um ber
W ait_Fo r_
2 1
M SR N
Figure 44c: Process SRI_HLR (sheet 3)
3GPP
Release 1999 110 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the H LR to handl e W ait_F or_ Signals to /from t he left
a request for routeing inform ation M SR N are to/from the GM SC;
are to/from the VLR
Provide P rovi de
Roaming R oami ng
Number ac k N um ber negati ve
response
P RN _Error_
1
H LR
Yes
R esul t=
2 F ail?
No
F orw ard_
C U G_C hec k
R esul t= No
C all
allow ed?
Yes
Routeing R outeing Yes

F orw ardi ng
address := 4 address:=
enquiry?
MSR N F TN
No
Yes C AM EL_
F orw arding
C SI_Check _ See TS 23.078
enquiry?
H LR
No
C AM EL_T _ R esult = No
See TS 23.078 C SI_C HE CK_ C SI
H LR ac ti ve?
Yes
C AM EL_O_
See TS 23.078 C SI_C HE CK_
H LR
C AM EL_D_ C all ed party SS Set negativ e

See TS 23.078 C SI_C HE CK_ i nteraction res pons e:
H LR v iolation CU G reject
Send Send Send Send

Routeing R outei ng R outeing Routeing
Info ac k Info ack Info ack Info negativ e
res ponse
Idl e Idle Idle Id le
Figure 44d: Process SRI_HLR (sheet 4)
3GPP
Release 1999 111 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C heck_P aram eters Chk_Pa r1(1)

Proc edure to c hec k
the param eters o f a
recei ved m ess age
No
All required
parameters present?
Yes
No Set negativ e
All parameter values
ac ceptable? res pons e:
Data mi ssing
Yes
Set negativ e
re sponse:
U nex pec ted
data value

Pas s Fai l
Figure 45: Procedure Check_Parameters
3GPP
Release 1999 112 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S ubsc ription_Check _H LR S C_HLR 1(1)

Procedure in t he H LR
to m ake subsc rip tion
check s for a mobile-
term inated call
No
MS
k now n?
Yes Set neg ati ve
response:
U nknown
subsc rib er
Yes
N umber
c hanged?
No Set neg ati ve
response:
N umber
changed
D eri ve_R equested_
Bas ic_Servi ce_ HLR
R equested N o
s ervice
provi sioned?
Yes Set neg ati ve Bearer serv ice
response: or
ser vic e not Teleserv ice
provis ioned
C heck _IC _
Barring
R esul t= Yes
C all
ba rred?
No Set neg ati ve
response:
C all barred
IC _C UG_
C heck
R esul t= No
C all
allow ed?
Set neg ati ve
Yes response:
C UG reject

Pas s Fail
Figure 46: Procedure Subscription_Check_HLR
3GPP
Release 1999 113 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure F irst_F orwarding_HLR F F_H LR1(1)

to handle c all forwar di ng
before interrogation of t he VLR
H andle_C FU
Yes
R esul t=
F ail?
No Set negativ e
re sponse:
Fo rw arding
Yes violation
R esul t=
F orw ard?
No
No
M S not
reachable?
Yes
H andle_C FN Rc
Yes
R esul t=
F ail?
No Set negativ e
re sponse:
Fo rw arding
violation
No
R esul t=
F orw ard?
Yes Set negativ e

re sponse:
Absent
subsc ribe r
R esult:= R es ult:= R esul t:= R es ult:=

Forward Continue F orwa rd Fail
Figure 47: Procedure First_Forwarding_HLR
3GPP
Release 1999 114 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure PR N_E rror_H LR P RN_ E_H1(1)

to handle a negati ve respons e
for a roaming num ber request
C CB S_R eport_
See TS 23.093
PR N _Failure
Negativ e Yes
response =OR
not al lowed??
No Set negativ e
res pons e:
OR not
allo wed
N egativ e Yes
respons e= Faci lity
not s up ported?
No
Yes N egative Set negativ e

response=Absent res pons e:
su bs cri ber? Fac ili ty n ot
No supported
Negativ e No
response=N o
roami ng
number? Yes
Set negativ e
Handle_C FN R c H an dle_C FN Rc res pons e:
System
failu re
Fail Forw ard Forward F ai l

Res ult? R esul t?
N ot reachable Not re ac hable
Set n egativ e Super_C harged_ Set negativ e

res pon se: SRI_Error_ res pons e:
Forwarding HLR Forwarding
violation violati on
Yes
Res ult=
Purged?
No
Se t negative Set negative

respons e: response:
Absent Sys tem
subscriber fai lure
R esult:= R esult:= R es ult:=

Fail F orw ard Fail
Figure 48: Procedure PRN_Error_HLR
3GPP
Release 1999 115 3GPP TS 23.018 V3.12.0 (2003-03)
Pro cedure F orw ard_C UG_Check F W D _CUG 1(1)

Procedure to carry out
CU G authori sation check
for a forw arded cal l
No C U G provi si oned for

forw ard ing subscriber against
reque sted basic servic e
Yes
C U G info prov ided i n Yes

ro utei ng i nform ation
re quest
No
P erform
F orw arding CU G As de fined in TS 23.085
au thorisation
CUG Pas s
au thorisation
r es ult
Fail
R es ult:= R esul t:= R esult: =

Cal l allo wed C all barr ed C all allow ed
U pda te C UG
i nf o As defi ned in T S 23.085
Figure 49: Procedure Forward _CUG_Check
3GPP
Release 1999 116 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure D erive_Reque sted_B asic_S ervice_HLR DR BS _H1(1)

Proc edure in the H LR to
deriv e the requeste d basi c
serv ice for an incom ing
(M T ) call accordi ng to the
rules of GSM 09.07
No Exhaustiv e
ISD N co mpatibi lity
informati on av ailable?
Yes
No
M ulti -
num beri ng?
Yes
A pply GSM BC D eriv e GSM B C from

GSM BC: =NU LL fo r this ISD N compati bili ty
M SISD N inf ormation
D eriv e basic
Basic serv ice:=
se rvi ce from
de fault
GSM BC
Figure 50: Procedure Derive_Requested_Basic_Service_HLR
3GPP
Release 1999 117 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure C heck_IC_Barring CIB 1(2)

Yes
Operato r determ ined
BAIC im posed?
No
Yes
Operato r determ ined
BIC -R oam im posed?
No
No MS registered
in H PLM N
country?
Yes
Yes Operato r determ ined

BIC -R oam HZ
im pos ed?
No
No MS registered
in H PLM N
zone?
Yes
R esult:=
Ca ll barred
(O DB)
Figure 51a: Procedure Check_IC_Barring (sheet 1)
3GPP
Release 1999 118 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure C heck_IC_Barring CIB 2(2)

request against SS barring 1
Initi ate
handl ing T o process MAF 022
of BAIC
W ait_F or_
B AIC _
R esponse
C ontinue
c all F rom proce ss M AF022
handli ng
Yes
C all
ba rred?
No
Initi ate
handl ing T o process MAF 023
of BIC -R oam
W ait_F or_
BIC -Roam_
R esponse
C ontinue
c all F rom proce ss M AF023
handli ng
Yes
C all
ba rred?
No

C all barred C all allow ed
(S S ba rri ng)
Figure 51b: Procedure Check_IC_Barring (sheet 2)
3GPP
Release 1999 119 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure IC_CUG_Check IC_CUG1(1)

Procedure to carry out Signals to/from the right
CU G authorisation check are to/from the process
for an incoming (MT) call CUG_MAF015
No SRI
contains CUG
info?
Yes
HLR
supports CUG?
Yes
No
Yes Outgoing incoming
Access
call
present?
No
Wait_For_
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 1999 120 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Handle_CFU H_CFU1(1)

Proc edure in the HLR
t o handle Call Forwarding
Uncondit ional
Signals to/f rom t he right

are to/f rom t he process
MAF007
CAMEL_CHECK
See TS 23. 078
_SI I2_C DTI
No
Result =
Pass ?
Yes
initiate
handling
of CFU
Wait_F or_
CFU _Result
continue
call
handling
Yes
Error?
No
Normal Yes
call?
No

Fail Forward Continue
Figure 53: Procedure Handle_CFU
3GPP
Release 1999 121 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Handle_CFNRc H_CFNRc1(1)

Proc edure in the HLR
or VLR to handle Call
Forwarding on Mobile
Subsc riber Not Reachable

MAF010
CAMEL_CHECK
See TS 23. 078
_SI I2_C DTI
No
Result =
Pass ?
Yes
initiate
handling
of CFNRc
Wait_F or_
CFN Rc_Res ult
continue
call
handling
Yes
Error?
No
Yes
Mobile subs criber
not reachable?
No

Fail Forward Not reachable
Figure 54: Procedure Handle_CFNRc
3GPP
Release 1999 122 3GPP TS 23.018 V3.12.0 (2003-03)
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 [23]. If the VLR does not support Super-Charger, processing continues from the "No" exit of the test
"Result=Purged?".
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 [22].
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 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 neither location
information nor subscriber state, the VLR treats this as a missing parameter.
3GPP
Release 1999 123 3GPP TS 23.018 V3.12.0 (2003-03)
7.2.3.4 Procedure Retrieve_Location_Info_VLR

The variable Current location retrieved is used to indicate that the location information was obtained by paging the MS.
The test "Retrieve location info from SGSN" takes the "Yes" exit if:
- there is an association established between the MSC/VLR and the SGSN.
The stored location information consists of:
- the service area ID (for UMTS) or cell ID (for GSM) 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 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;
- 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 output signal Send MS information towards the SGSN indicates that the required information is mobile 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 Retrieve_Current_Location_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 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 1999 124 3GPP TS 23.018 V3.12.0 (2003-03)
Process PR N_VLR P RN_ VLR1(8)

Proces s in the VLR to handl e
a request for a roam ing num ber
Idle
are to/fro m the HLR .
Provide
R oaming
N um ber
C heck_
1
Parameters
No
R esult=
P as s?
Yes
No OR
i ndicator
present?
Yes
OR
s upported?
Yes No
If C S B C w as Set n egativ e
C onvert C S BC
in cluded in the res pon se:
to basic service
Provid e R oam ing OR n ot
N um ber allowed
Service No
s upported
by VLR?
Yes
Pre-paging Set n egativ e

s upported res pon se:
i n VLR? Faci li ty
not s uppo rted
No Yes
No
Pre-paging
al low ed?
Yes
Yes IMSI Yes IMSI Provide Roaming
known k now n N um ber
in VLR ? i n VLR? nega ti ve
No No response
Check _Reason_ C heck_R eason_

2 In_S ervi ng_ 4 In_Serving_ See TS 23.116
N etw ork _E ntity N etw or k_Entity
No No
Res ult= R esult=
Purged? P urged?
Yes Yes
3 1 5 1 Idle
Figure 55a: Process PRN_VLR (sheet 1)
3GPP
Release 1999 125 3GPP TS 23.018 V3.12.0 (2003-03)
Process PR N_ VLR P RN_ VLR2(8 )

2
True
IM SI
Signal s to the lef t detached
are to the H LR . Fa ls e
R oaming No
i n LA
al low ed?
Ye s
No
M SR N
av ailable?
Ye s
Se t negativ e Set negative

M SC
per VLR res pon se: res pons e:
N o roam ing Absent
numbe r subscrib er
1 >1
Ye s R e ceived M SC
nu m ber= Stored 1
M SC num b er?
No
Fal se
C o nfirmed by
radi o contac t
True
U se re ceiv ed U se stored
M SC numb er M SC nu mber
fo r M SR N for MSR N
A lloca te
M SR N
C AM EL_
See TS 23.078
SET _SOA
S tore C S BC, ISD N BC ,

c om p ati bi lity ISD N L LC & ISDN H LC
i nfo (as avail able)
Store A lerting
P attern
(if re cei ved)
C LI_PR N_
See TS 23.081
VLR
C C BS_H and le_

See TS 23.093
PR N
Provide
R oamin g
N um be r ack
Figure 55b: Process PRN_VLR (sheet 2)
3GPP
Release 1999 126 3GPP TS 23.018 V3.12.0 (2003-03)

3
No
M SR N
Signal s to the lef t available
are to the H LR . Ye s
Set n egativ e
A lloca te
res pons e:
M SR N
No roami ng
nu mber
C AM EL_
See TS 23.078 1
SET _SOA
C reate
IM SI
record
Location i nfo
O nl y if >1 M SC
c onfi rmed per VL R
i n HLR :=
Fal se
C onfirm ed by radio co ntact:=Fal se;

D ata confirm e d by H L R:=F alse;
IM SI detac hed:= False
If used
Allocate LM SI
by VLR
S tore C S BC, ISD N BC ,

c om p ati bi lity ISD N L LC & ISDN H LC
Store A lerting
P attern
(if re cei ved)
C LI_PR N_
6 See TS 23.081
VLR
D a ta Fals e
C C BS_H and le_
confirm ed See TS 23.093
PR N
by HLR ?
True
M ore Yes Provide

au thenti cation R oamin g
sets needed? N um be r ack
No
F et ch_
A uth entic ati on_
S ets _VL R
R estore_
S ubs cri ber_
D ata_VLR
Idle
Figure 55c: Process PRN_VLR (sheet 3)
3GPP
Release 1999 127 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the VLR to handl e Signal s to the right
a request for a roam ing num ber 4 are to the M SC .
Yes
IM SI
detached?
No
No R oaming
i n LA
al low ed?
Ye s
No Yes
Locat ion are a
ID know n?
True Data Paging

No
confirme d vi a S GS N
by H LR? po ssible?
Fals e Yes
No More Set Paging
authe ntic ati on vi a S GSN
sets needed ? possib le
Yes
Fe tch_
Authentication_
Sets_VLR
R es tore_
Subscribe r_
Data_VLR
Search_Fo r_ Page type=

Page MS ci rc uit-sw i tc hed
MS _VLR
cal l
Yes
Res ult=
Pass?
No
Yes
Absent
subscribe r?
No
Set n egativ e
res pon s e:
Absen t
subsc riber
W ait_For_
1 7 Ac cess_
R eque st
Figure 55d: Process PRN_VLR (sheet 4)
3GPP
Release 1999 128 3GPP TS 23.018 V3.12.0 (2003-03)

a request for a roam ing num ber 5
C rea te
IM SI
r ecord
L oca tion info

O nl y if >1 M SC
c onfirme d
per VLR
i n HLR :=
Fa lse
C on firm ed by radio contact:=F al se ;

D ata confirm ed by H LR:=F als e;
IM SI detac hed:= Fa lse
If used
Al locate LM SI
by VLR
S tore C S BC , ISD N BC ,
c om pati bility ISD N LLC & ISDN H LC
F etch_
A uthentic ation_
S ets _VL R
R estore_
S ubs cri ber_
D ata_VLR
S earch_For_
M S_VLR
Yes
R esul t=
P as s?
No
Ye s
A bs ent
s ubs cri ber?
Se t negative No
respons e:
Absent
subscribe r
W a it_For_
1 7 Ac cess_
R equ es t
Figure 55e: Process PRN_VLR (sheet 5)
3GPP
Release 1999 129 3GPP TS 23.018 V3.12.0 (2003-03)

Proces s in the VLR to handl e W ait_F o r_ Sign als to the l eft
a request for a roam ing num ber A ccess _ are to the H LR ;
R eques t sig nals to/from th e right
are to/from the MS C
unless shown otherw ise.
Process Page MS
Pa ge MS
Access negative
vi a SGSN
Request res po nse
No Yes
MSR N Busy
Page MS To SGSN
available ? subsc riber?
Ye s No
W ait_For_
MSC
Acc es s_ 7
per VLR
R e quest
1 >1
Ye s R eceiv e d M SC Yes
Absent
num ber= S tored Subscriber?
M SC n u mber?
No No
False
C onfirme d by
radio contact
True
Us e r eceiv ed U se stored Se t neg ati ve
MS C num ber M SC numb e r response:
for M SR N fo r M SRN Sys tem
fail ure
Proc ess Ac cess

Alloc ate
R e quest
MSR N
ne gative
re spons e
Set n egativ e Set n egative

CAM EL_
See T S 23 .078 res pon se: resp ons e:
SE T_SOA
No roami ng Abse nt
numbe r subscriber
Store C S BC , ISD N B
compati bili ty ISD N LLC & ISD 1
info (as avai lable)
Store Alerti ng
Pattern
(if recei ved)
CLI_PR N_
See T S 23 .081
VLR
CC BS_H an dle_
See T S 23 .093
PR N
P rovi de
R oam ing
N um ber ack
Figure 55f: Process PRN_VLR (sheet 6)
3GPP
Release 1999 130 3GPP TS 23.018 V3.12.0 (2003-03)

Signal s to the lef t No

M SR N
are to the H LR . a v ai lable?
Yes
Set ne gativ e
M SC
res pons e:
p e r VLR
No ro aming
numb er
1 >1
Yes R eceived M SC
num be r= S tored 1
M SC num ber?
No
Fa lse
C onfirmed by
radi o contact
True
U se receiv ed U se stored
M SC num ber M SC number
f or M SR N for M SR N
A lloc ate
M SR N
C AM EL_
See TS 23.078
SET _SOA
S tore C S BC , ISD N BC ,
c om pati bility ISD N LLC & ISDN H LC
Store A lerti ng
P attern
( if recei ved)
C LI_PR N_
See TS 23.081
VLR
C C BS_H andle_
See TS 23.093
PR N
P rovi de
R oami ng
N um ber ack
PAR pendin g:=Fal se;

PAR succ e ssful := False;
Fatal P AR e rror: =Fals e
Idle
Figure 55g: Process PRN_VLR (sheet 7)
3GPP
Release 1999 131 3GPP TS 23.018 V3.12.0 (2003-03)

Signal s to/from the l eft PAR pen ding:=

are to/from the proc ess IC H_VLR ; True
sig nals to/from the ri ght
P rocess _
A ccess _
R eques t_VLR
No
R esul t=
P as s?
Yes
PAR succ essful := PAR succes sful:=

True Fals e
PAR pen ding:= PAR pending :=

Fa lse Fals e
No
PAR Fatal PA R
C om pleted error?
Yes
W ait_F o r_ Fatal PA R Fatal PAR

C all_Arr iv al error:= True er ror:= Fa lse
R adio
Cal l
co nnec tion
a rrived
released
Call PAR succe ssful := PAR

arrived Fal se C o m pleted
F atal PAR
error:= False
Idle Idle
Figure 55h: Process PRN_VLR (sheet 8)
3GPP
Release 1999 132 3GPP TS 23.018 V3.12.0 (2003-03)
Process R estore_Subscriber_D ata_VLR RS D_ VLR1(1)

Proces s in the VLR
to restore s ubs criber data

are to/from the HLR
R estore
D ata
W ait_Fo r_
D ata
R estore
Restore
Data ack D ata n egativ e
re spons e
Update
Sub scriber
Data
Update
HLR
number
Update MS
If receiv ed
Not Re ac habl e from HLR
indic ator
D ata
confir med by
H LR :=True
Figure 56: Process Restore_Subscriber_Data_VLR
3GPP
Release 1999 133 3GPP TS 23.018 V3.12.0 (2003-03)
Process P S I_VLR P SI_ VLR1(2)

Proces s in the VLR to handl e Signals to /from the l eft
a request from th e H LR for are to/from the H LR;
subscriber information si gnals to/from the rig ht
are to/from the MSC
Idle
Provide
Sub scriber
Info
Check _
Pa ram ete rs
No
Res ult=
Pass?
Yes
No
IMSI
known
in VLR ?
Yes
Subscriber No No Subsc riber

state state
requested? reques ted?
Yes Yes
Yes
IMSI
deta ch ed?
No
Roam ing No
in LA
allow ed?
Yes
Set subscriber S ubs criber state:=

Subsc riber state :=
state N etw ork
Assumed idl e
requested determined
not reac hab le
Location No
i nfo
reques te d?
Yes
R etrieve_
Loc ation_
Info_VLR
Obtai n Prov ide Provide

Subscriber Subsc ribe r Subscriber
Info Info ack Info negativ e
response
W ait_For_
Idle Idle
MS C_R esponse
Figure 57a: Process PSI_VLR (sheet 1)
3GPP
Release 1999 134 3GPP TS 23.018 V3.12.0 (2003-03)
Process P S I_VLR P SI_ VLR2(2)

Proces s in the VLR to handl e W ait_Fo r_ Signals to /from t he left
a request from th e H LR for M SC _R espons e are to/from the H LR;
subscriber information si gnals to/from the rig ht
are to/from the MS C
Obtain
S ubs criber
Info ack
S ubs cri ber No

s tate
receiv ed?
Yes
S et
s ubs cri ber
s tate
Location No
i nfo
requested?
Yes
R etri eve_
Loc at ion_
Info_VLR
Provide
Subs cri ber
Info ack
Idle
Figure 57b: Process PSI_VLR (sheet 2)
3GPP
Release 1999 135 3GPP TS 23.018 V3.12.0 (2003-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
Current location
retrieved:=
False
Yes
Retrieve l ocation
info from SGSN?
No
Yes
Current
Send MS
location
information requested?
No
Retrieve_
Wait_For_
Current_
SGSN_R esponse Location_VLR
Send MS False
Send MS Current
Information Information location
negativ e ack retrieved
response
True
No
Current Current Location info:=
location location Retrieved
requested? requested? location info
Yes
No
No
Cell ID Location info:= Derive location number,
or SAI Stored geodetic information and
recei ved? location info geographical information
Yes
No Yes
MS state=
Ready?
Retrieve_
Current_
Location_VLR
False True
Current
location
retrieved
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 1999 136 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Retrieve_Current_Location_VLR RCL_VLR1(1)

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

Active location Active location Page MS
for MS
retrieval retrieval
Wait_For_ Wait_For_
Search_ Page_
Result Result
Search f or Search Search Page MS Page MS Page MS

for MS for MS negative
MS ack ack via SGSN
negative via SGSN response
response
Roaming No
in LA
allowed?
Yes
Current location Subscriber Current location

retrieved:= state:=Not Page MS retrieved:= Page MS
True reachable True
Wait_For_ Wait_For_
Search_ Page_
Result Result
Figure 59: Procedure Retrieve_Current_Location_VLR
3GPP
Release 1999 137 3GPP TS 23.018 V3.12.0 (2003-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
7.2.4.6 Procedure Current_Location_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 [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".
7.2.4.7 Procedure Current_Location_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 1999 138 3GPP TS 23.018 V3.12.0 (2003-03)
Process Prepage_MSC PP_MSC1(1)

Proc es s in t he MSC Signals to/f rom the lef t
t o handle a pre-paging are to/f rom t he VLR;
request s ignals t o the right
are to t he BSS
Idle
Search
Page MS
for MS
Prepaging_
Prepaging_ Search_for_
Page_M S_MSC MS_MSC
Yes Yes
Result= Result=
Pass ? Pass ?
No
No
Proc ess _
Idle Acces_ Idle
Request _MSC
No
Result=
Pass ?
Yes
Start radio
Idle
guard timer
Wait_F or_
Call_Arrival
Radio guard
Call timer Release BSS released
I nternal
arriv ed expired transaction t he radio resource
Release
transaction
Radio Radio
Stop radio connec tion connec tion
guard timer released released
Idle
Figure 60: Process Prepage_MSC
3GPP
Release 1999 139 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P repaging_P age_M S _MS C P PP MS_M 1(1)

Procedure in t he MSC
to page a n M S in a
specified l ocation area
Signal s to/from the l eft Loc ati on No

are to/fro m the BSS; area ID
signals to/from the ri ght known?
are to/from the VLR Yes
MS Yes Set negativ e
connection res ponse:
exis ts ? U nknown LAI
No
No Yes
Pagi ng vi a
M S busy?
SGSN possi ble?
Yes No
Set negative
In specified
l oc ation area Pa ge response:
Busy S ubs criber
Page MS Set acces s Page MS

c onnection negat ive
vi a SGS N
s tatus res po ns e
Sta rt Page
response
Pas s Fai l
tim er
W ait_For_
Pa ge_
Res ponse
MS Page CM
For circui t-
connection response Serv ice
swi tched cal l
establis hed ti mer e xp ired R equest
CM To process
Serv ice
OC H_MSC
R equest
Se t ac ce ss Set negat ive Set negativ e

connection r esponse: res ponse:
status A bs ent Busy Subsc ribe r
S ubs cri ber (N D U B)
P age M S Page MS
negative negat ive
response res po ns e

Pa ss F ail Fai l
Figure 61: Procedure Prepaging_Page_MS_MSC
3GPP
Release 1999 140 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P repaging_S earch_For_MS _M S C P PS MS_M 1(1)

Signal s to/from the l eft MS Yes

are to/fro m the BSS; connection
signals to/from the ri ght exis ts ?
are to/from the VLR No
No Yes
Paging vi a
M S busy?
SGSN possi bl e?
Yes No
Set negativ e
Page MS
res ponse:
vi a SGS N
Busy Subsc ribe r
Set acces s Page MS

In speci fied
loc ation area Page c onnection negat ive
s tatus res po ns e
Sta rt Page R esul t:= R esult:=

response
Pas s Fai l
tim er
W ait_For_
Pa ge_
Res ponse
MS Page CM For circui t-

connection response Serv ice swi tched cal l
establis hed ti mer e xp ired R equest
CM
To process
Serv ice
OC H_MSC
R equest
Se t ac ce ss Set negat ive Set negativ e

connection r esponse: res ponse:
status A bs ent Busy Subsc ribe r
S ubs cri ber (N D U B)
P age M S Page MS
negative negat ive
response res po ns e

Pa ss F ail Fai l
Figure 62: Procedure Prepaging_Search_For_MS_MSC
3GPP
Release 1999 141 3GPP TS 23.018 V3.12.0 (2003-03)
Process O SI_MSC O SI_M S C1(1)

Proc es s in the MS C to hand le Signals to /from t he left
a request from the VLR for are to/from the VLR
inform ation on the subscriber's
location and state
Idle
Obtain
Subs cri ber
Info
S ubs cri ber No

s tate
requested?
Yes
S et
s ubs criber
s tate
Obtain
Subs cri ber
Info ack
Idle
Figure 63: Process OSI_MSC
3GPP
Release 1999 142 3GPP TS 23.018 V3.12.0 (2003-03)
P ro c e s s R C L _ M S C R C L _ M S C 1( 1)
P ro c es s in th e MS C S ig n a ls to /fr o m t he l eft
to r etr i ev e th e cu r re n t a re to /fr om th e V L R
lo ca tio n o f a su b sc rib e r
Id le
S e ar ch
P a g e MS
fo r MS
Cu r re n t_ C u rr e n t_
L o ca tio n _ L o c ati o n_
Se a r ch _ M S C Page_M SC
Id le
Figure 64: Process RCL_MSC
3GPP
Release 1999 143 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Current_Location_Page_MSC CLPage_M1(1)

Procedure in the MSC Signals to/from the left
to page an MS in a specified are to/from the BSS/RAN;
location area for Active signals to/from the right
Location Retrieval are to/from the VLR
No
Location
area ID
known?
Yes
MS
connection
exists?
Yes
No
No
Paging via
SGSN possible?
Yes
In specified Page MS
Page
location area via SGSN
Start Page
response
timer
Wait_For_
Page_
Response
Yes
Page response MS
For circuit- CM Service timer connection GSM
switched call Request expired established Access?
No
To process CM Service Release Report of change of

OCH_MSC Request transaction service area active
Yes
?
No
Set negative Set negative

Set negative
response: response: Location response:
Busy Absent Reporting Control
Unknown LAI
subscriber subscriber
Wait_For_Location
Page MS Page MS Page MS
Page MS _Report
negative negative negative
response response ack
response
Location
Report
No
SAI
received ?
Set negative
response: Yes
Unknown LAI
Page MS
Ack
Page MS
negative
response
Figure 65: Procedure Current_Location_Page_MSC
3GPP
Release 1999 144 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Current_Location_Search_MSC CLS_MSC1(1)

Procedure in the MSC Signals to/from the left
to page an MS in a specified are to/from the BSS/RAN;
location area for Active signals to/from the right
Location Retrieval are to/from the VLR
Yes
MS
connection
exists?
No
No
Paging via
SGSN possible?
Yes
Yes
In all Search MS GSM
Page
location area via SGSN Access?
No
Start Page
response
timer Yes
Report on
change of
service area?
No
Wait_For_
Page_
Response
Page response MS Location

For circuit- CM Service
timer connection Reporting
switched call Request
expired established Control
Wait_For_
To process CM Service Release
Location_
OCH_MSC Request transaction
Report
Location
Report
Yes No
SAI
received?
Set negative Set negative Set negative

response: response: response:
Busy Absent Busy Subscriber
subscriber subscriber
Search MS Search MS Search MS

Search MS
negative negative negative
ack
response response response
Figure 66: Procedure Current_Location_Search_MSC
3GPP
Release 1999 145 3GPP TS 23.018 V3.12.0 (2003-03)
7.3 MT call
7.3.1 Functional requirements of serving MSC
7.3.1.1 Process ICH_MSC

Sheet 1: the rules for converting the ISDN BC/LLC/HLC to a bearer service or teleservice are specified in 3GPP
TS 29.007 [29].
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 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 [36]) 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 5, sheet 7, sheet 8, sheet 10: 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 4, sheet 7, sheet 8, 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 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 task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports
CAMEL phase 3 or later.
3GPP
Release 1999 146 3GPP TS 23.018 V3.12.0 (2003-03)
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_MSC 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 CW this signal will not be received from the VLR.
Sheet 3, sheet 8, the procedure CD_Reject is specific to Call Deflection; it is specified in 3GPP TS 23.072 [11].
Sheet 3, sheet 8: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS; it is specified in 3GPP

TS 23.093 [22].
Sheet 3, sheet 4, sheet 10, sheet 11: the procedure CCBS_Check_Last_Call is specific to CCBS; it is specified in 3GPP
TS 23.093 [22].
Sheet 4: the procedure UUS_ICH_Check_Support is specific to UUS; it is specified in 3GPP TS 23.087 [20].
Sheet 4: 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 4: 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 "ResultForwarding Failed?".
Sheet4, sheet 9: the procedures CD_Failure and CD_Success are specific to Call Deflection; they are specified in 3GPP
TS 23.072 [11].
Sheet 5: 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 5: 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 5: 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.
Sheet 5: 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 partys status field of the
Backward call indicator set to "no indication".
Sheet 5, sheet 7: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 5: the procedure Activate_CF_Process is specified in subclause 7.2.1.7.
Sheet 5: the procedure UUS_ICH_Set_Info_In_IAM is specific to UUS, it is specified in 3GPP TS 23.087 [20].
Sheet 5: 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 5; the procedure CD_Success is specific to Call Deflection; it is specified in 3GPP TS 23.0 72 [11].
3GPP
Release 1999 147 3GPP TS 23.018 V3.12.0 (2003-03)
Sheet 6: 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 7: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later; it is
Sheet 7: the procedure Handle_COLP_Forwarding_Interaction is specified in subclause 7.2.1.6.
Sheet 7: the procedure Send_Answer_If_Required is specified in subclause 7.2.1.4.
Sheet 7: the procedure Send_Network_Connect_If_Required is specified in subclause 7.2.1.5.
Sheet 8: the procedure CCBS_MT_MSC_Check_Forwarding is specific to CCBS; it is specified in 3GPP

TS 23.093 [22].
Sheet 9: 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 9: the procedure Handle_ORLCF_MSC 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 11, sheet 12: 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 11, sheet 12: 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 11: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in 3GPP TS 23.087 [20].
Sheet 12: 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 13: 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.
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.
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 generalised procedure Page_MS_MSC is equally
applicable to paging for SMS delivery or network-initiated SS procedures.
Sheet 1: the test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.
Sheet 1: the procedure Check_MT_Multicall_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [24]. If
the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Not provisioned?".
Sheet 1: 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 1: 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 1: 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 [24]).
3GPP
Release 1999 148 3GPP TS 23.018 V3.12.0 (2003-03)
Sheet 2: 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.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 generalised procedure Search_For_MS_MSC is equally
applicable to paging for SMS delivery or network-initiated SS procedures.
Sheet 1: the test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.
Sheet 1: the procedure Check_MT_Multicall_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [24]. If
the VMSC does not support Multicall, processing continues from the Yes exit of the test Result=Not provisioned?.
Sheet 1: 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 1: 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 1: 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 [24]).
Sheet 2: 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.3.1.4 Procedure Complete_Call_In_MSC

Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP.
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 [22].
Sheet 2: the procedure Establish_Terminating_TCH_Multicall1 is specific to Multicall; it is specified in 3GPP

TS 23.135 [24].
Sheet 2: the test "Result=Rejected?" can take the "Yes" exit only if the procedure
Establish_Terminating_TCH_Multicall1 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 [22].
Sheet 3, sheet 5: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS; it is specified in 3GPP

TS 23.093 [22].
3GPP
Release 1999 149 3GPP TS 23.018 V3.12.0 (2003-03)
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].
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_Multicall2 is specific to Multicall; it is specified in 3GPP

TS 23.135 [24]. 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 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?".
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 Procedure Process_Call_Waiting_MSC

Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP.
Sheet 1: 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 Call Confirmed message indicates "busy" for the successful case.

TS 23.135 [24]. If the VMSC does not support Multicall, processing continues from the Yes exit of the test
Result=Pass?.
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 [22].
3GPP
Release 1999 150 3GPP TS 23.018 V3.12.0 (2003-03)
Sheet 2, sheet 3, sheet 5: the procedure UUS_ICH_Check_Support is specific to UUS; it is specified in 3GPP
"Result=Pass?" where the test follows the procedure call.
Sheet 2: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS; it is specified in 3GPP TS 23.093 [22].
Sheet 2: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS.
Sheet 2: 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].
Sheet 2: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 2, sheet 8: 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 2, sheet 8: the procedure Handling_CD_MSC is specific to Call Deflection; it is specified in 3GPP
TS 23.072 [11].
Sheet 2, sheet 3, 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 4, sheet 8: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS; it is specified in
3GPP TS 23.093 [22].
Sheet 3, sheet 7: the Release transaction (reject) message covers all unsuccessful cases not otherwise indicated.

TS 23.087 [20].
Sheet 4, sheet 8: 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 5: 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].

TS 23.135 [34].
Sheet 6: 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 6: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later; it is
the "Yes" exit of the test "Result=Pass?" on sheet 6.
Sheet 6: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP.
Sheet 7: the input signal "CAMEL TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or later.
Sheet 7: the procedure CAMEL_MT_GMSC_DISC5 is called if the VMSC supports CAMEL phase 3 or later; it is
Sheet 7, sheet 8: the procedure UUS_ICH_Check_Forwarding is specific to UUS; it is specified in 3GPP

"Result=Pass?".
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 8: the procedure CD_UUS_Interaction is specific to Call Deflection; it is specified in GSM 23.0 72 [11].
3GPP
Release 1999 151 3GPP TS 23.018 V3.12.0 (2003-03)
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.
7.3.1.7 Procedure Derive_GSM_BC_MSC
7.3.1.8 Procedure Establish_Terminating_TCH_If_Required
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 1999 152 3GPP TS 23.018 V3.12.0 (2003-03)
Process ICH_MSC ICH_MSC1(13)

Process in the MSC Signals to/from the left
to handle an incoming (MT) c all are to/from the BSS;
signals to/from the right
are to/from the VLR
Idle
Initial
From GMSC
Address
Convert ISDN BC/LLC/HLC

(if present) to bearer
service/teleservi ce & CS BC;
Store UUS information (i f received)
Send Info
For Incoming
Call
ACM sent:=False;
Answer sent:=False;
BOR :=False;
Network c onnect sent:=False;
TCH alloc ated:=False;
UUS1 result sent:=False;
UUS1 implicit active:=F alse;
Wait_F or_ UUS1 explicit active:=F alse;
Page_R equest UUS2 active:=False;
UUS3 active:=False;
UUS C F interaction:=False;
Call answered := False
Continue
CAMEL
Handling
CAMEL_
ICH_MSC_ See TS 23.078
INIT
Result?
Reconnect MSR N Aborted Fail
Set Suppress Set

VT-CSI cause
Send Info For Send Info

MT R econnected For Incoming Release
Call Call
Release call
resources
Wait_For_
Wait_F or_
Reconnected_ Idle
Call_Result Page_R equest
Figure 67a: Process ICH_MSC (sheet 1)
3GPP
Release 1999 153 3GPP TS 23.018 V3.12.0 (2003-03)
Pro c ess IC H _ M SC I C H_ M S C 2 (1 3 )
Proc es s in the MS C W ait_Fo r_ S ignal s t o/fr om the left
to ha ndle an incom i ng ( M T) call P age_R equest are to/fr om th e GM SC;
signa ls to/fr om the rig ht
are to/fr om th e V LR
Send Info Send In fo

C all is to b e S earc h Com plete
For In coming P age M S F or Inco m ing
for war ded For M S C all
Ca ll ne gative C all Ack
res ponse
S et P age_ Searc h_For_

1 2
cause M S_ M S C M S _M SC
Yes Ye s
R esu lt= Re su lt=
P as s? Pass?
No No
No No
R esu lt= Re su lt=
F ail? Fail
CAM EL_ Ye s P rocess _ Y es CA ME L_

MT _GM S C_ A ccess_ MT _GM S C_
DIS C 6 R equest_M S C DISC 6
Release call R esult= Rel ease call

re so ur ces P as s? res our ce s
No
Yes
CA ME L_ W ait_ For_ W ait_For _ C A M E L_ W ait_For _

M T_GM SC _ Idl e M T _ Cal l_ M T_ Call _ M T_GM S C _ M T_C all_ Id le
DIS C 4 R esult R esult D IS C4 Resu lt
Y es Y es
Re sult= R esult=
R econnect? R econnect?
No No
Send Info For

Rel eas e M T Rec onnected R elease
C all
Re lease cal l R elease c al l

res our ces r esources
W ait_ For_
Idle R eco nnec te d_ Idle
C al l_R es ult
Figure 67b: Process ICH_MSC (sheet 2)
3GPP
Release 1999 154 3GPP TS 23.018 V3.12.0 (2003-03)

Process in the MSC Wait_For_ Signals to/from the left
to handle an incoming (MT) c all MT_Call_ are to/from the GM SC;
Result signals to/from the right
are to/from the VLR
Send Info Process

For Incoming Complete Call
2
Call negati ve Call
Waiting
response
Proc ess_
Complete_ Call_
CD_Reject See TS 23.072
Call_In_MSC
Waiting_MSC
Yes Yes
CCBS_Set_
Diagnostic_ Result= Result=
See TS 23.093
Pass? Pass?
For_Release
No No
Store CW Treatment
indicator for this call
UUS_ICH_ if rec eived in SII2
Check_ See TS 23.087
Suppor t
Call answered
:= True
Set
cause
Wait_F or_
Yes Clear
Cause=
No Subscriber
Yes Yes
Reply?
Result= Result=
No Fail Fail
No
CAMEL_ CAMEL_ Wait_F or_
MT_GMSC_ MT_GMSC_ No MT_Call_
DISC4 DISC5 Result
Yes Yes
Result= Result=
No Reconnect? Reconnect?
Result=
Reconnect? No No
Yes
Send Info For
MT Rec onnected
Send Info For Call
MT R ec onnected Release
Call
Wait_F or_
Reconnected_
Wait_F or_ Call_Res ult
Reconnected_
Call_Result
Release
transaction
CCBS_Check_
See TS 23.093
Last_Call
Release
call
resources
Idle
Figure 67c: Process ICH_MSC (sheet 3)
3GPP
Release 1999 155 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in t he MSC Signals to/f rom the lef t
t o handle an inc oming (MT) c all are to/f rom the GM SC;
Wait _F or_ s ignals to/from the right
MT_Call_ are to/f rom the VLR
Result
Send Info
For I ncoming Call is to be
1
Call ack f orwarded
CAMEL_Chec k_
See TS 23. 079
OR LCF_VMSC
VMSCCF
Result?
OR LCF
Handle_
See TS 23. 079
OR LCF_VMSC
Continue Accepted
Result?
Forwarding Failed
3 CD_Failure See TS 23. 072 CD_Suc ces s See TS 23. 072
Wait _F or_
Release_
From_G MSC
Release
CAMEL_
MT_G MSC_ See TS 23. 078
DISC6
CCBS_Check_
See TS 23. 093
Last_Call
Release call
resources
Idle
Figure 67d: Process ICH_MSC (sheet 4)
3GPP
Release 1999 156 3GPP TS 23.018 V3.12.0 (2003-03)

3
Proc es s in t he MSC Signals to t he r ight
t o handle an inc oming (MT) c all are to t he VLR
unless marked otherwis e
Yes
Ty pe of forwarding=
Reconnec t?
No
CAMEL_
MT_VM SC_ See TS 23. 078
Notify_C F
Yes
Result=
4
Reconnect ?
No
CCBS_Check_
See TS 23. 093
Last_Call
Set
redirecti on
informat ion
Send_ACM_
If _Required
Activate_
CF_Proc ess
No
Result=
Fail?
Yes
CAMEL_ UUS_I CH_

MT_G MSC_ See TS 23. 078 Set _Inf o_ See TS 23. 087
DISC4 In_IAM
Yes
Init ial
Result= Address To process MT_CF_MSC
Reconnect ? Message
No
CAMEL_St ore_
CD_Failure See TS 23. 072 Destination_ See TS 23. 078
Address
(False, T rue)
Send Inf o For

MT R ec onnec ted CCBS_Check_
See TS 23. 093 CD_Suc ces s See TS 23. 072
Call Last_Call
Wait _F or_
Reconnect ed_ Wait_F or_
Idle
Forward_ACM
Call_Res ult
Figure 67e: Process ICH_MSC (sheet 5)
3GPP
Release 1999 157 3GPP TS 23.018 V3.12.0 (2003-03)
Proc es s in the MS C W a it_F or_M T_C all_ Res ul t, S ignals to /fr om t he left
to ha ndle an incom i ng ( M T) call W a it_F or_R ec onne cte d_C all_R es ult are to/from the GM SC;
si gnals to/fr om th e rig ht
are to/fr om the VL R
unless m a r ked other wise
Int_R elease_
F r om gsm S S F
C all
A bor t
R ele ase
R ele ase
T o B SS
T ran sac ti on
R el ea se
c all
r esourc e s
Idle
Figure 67f: Process ICH_MSC (sheet 6)
3GPP
Release 1999 158 3GPP TS 23.018 V3.12.0 (2003-03)

Process in the MSC
to handle an incoming (MT) c all Wait_For_
Forward_ACM
Signals to/from the left

are to/from the GMSC;
signals to/from the right
are to/from the process MT_CF_MSC Address
Connect
unless marked otherwise Complete
Send_ACM_
If_Required
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 ANSW ER ANSW ER
Yes Yes
CAMEL_
Result= Result=
MT_GMSC_ See TS 23.078
Fail? Fail?
DISC6
No No
No
Result=
Idle
Reconnect?
Yes
Yes Yes
Result= Result=
Release
Reconnect? Reconnec t?
No No
Send Info For Handle_COLP_ Send Info For Handle_COLP_

To VLR MT R econnected Forwarding_ To VLR MT R econnected Forwarding_
Call Interaction_MSC Call Interaction_MSC
Wait_F or_ Set COLP Wait_For_ Set COLP

Reconnected_ presentation Reconnected_ presentation
Call_Result indicator Call_Result indicator
Send_Network_
Release call Send_Answer_
Connect_
resources If_Required
If_Required
Call answered
Idle
:= True
Wait_For_
Forward_Clear
Figure 67g: Process ICH_MSC (sheet 7)
3GPP
Release 1999 159 3GPP TS 23.018 V3.12.0 (2003-03)
Proc es s in the MS C W ait_Fo r_ Si gna ls to/fr o m the l eft
to ha ndle an incom i ng ( M T) call F orw ard_A C M ar e to /fr om the GM S C ;
si gnals to/fr om the ri ght
ar e to /fr om the pr oc e ss M T_C F_M SC
unless m ar ked othe rw ise
Rel eas e R elease
C A M EL_
Rel eas e M T _ GM SC _ S ee TS 23.078
D ISC4
CA ME L_ Yes
R esul t=
Se e TS 23 .078 MT _GM SC_ R econnect?
DIS C 6
No
C C B S _MT _ Send In fo F or
S ee T S 23.093 M SC _C hec k_ M T R econnected T o VL R
F orw ardi ng C all
W ait_For _
R econnected_
C all _Re sul t
Send In fo F or
M T R econnected
C all neg ative
r espons e
C C B S _Set_
S ee T S 23.093 D i agnostic_ S et cau se
F or_ R elease
R elease R e lease
Int_Exception T o gs mS SF
R ele as e c al l
r esourc es
Idle
Figure 67h: Process ICH_MSC (sheet 8)
3GPP
Release 1999 160 3GPP TS 23.018 V3.12.0 (2003-03)

Process in the MSC Wait_For_ Signals from the left
to handle an incoming (MT) c all 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
OR LCF_VMSC
No Yes
Result=
Accepted?
No
Result=
Forwarding
Failed??
Yes
4 See TS 23.072 CD_Failure CD_Suc cess See TS 23.072
Wait_For_
Release_From_
GM SC
Release
CAMEL_
DISC6
CCBS_Check_
See TS 23.093
Last_Call
Release call
resources
Idle
Figure 67i: Process ICH_MSC (sheet 9)
3GPP
Release 1999 161 3GPP TS 23.018 V3.12.0 (2003-03)
Proc ess IC H_MSC ICH_M S C10(13)

Proc es s in the MS C W ait_Fo r_ Signals to /from t he left
to handle an incomi ng (M T) call M T _Cal l_ are to/from the GM SC;
R esult si gnals to/from the rig ht
are to/from the BSS
R elease
R elease
trans action
CAM EL_ C AMEL_

MT _GMSC_ See T S 23 .078 M T_GM SC _ See TS 23.078
DISC 6 D ISC4
Yes
R esult=
R econnect?
No
Release
R elease
transacti on
C C BS_Check _
See TS 23.093
Last_C all
Send Info F or
A bor t T o VLR M T R econnected To VLR
C all
R elease
c all
resourc es
W ait_For_
Idle R econnected_
C all _Resul t
Figure 67j: Process ICH_MSC (sheet 10)
3GPP
Release 1999 162 3GPP TS 23.018 V3.12.0 (2003-03)
Pro c ess IC H _ M SC I C H_ M S C 1 1 (1 3 )
Proc es s in the MS C W ait_Fo r_ S ignal s t o/fr om the left
to ha ndle an incom i ng ( M T) call C lea r are to/fr om th e GM SC;
signa ls to/fr om the rig ht
are to/from th e B SS
unless m ar ke d other wi se
R elease
R elease
tr ans action
UU S_M S C_ C A M E L_
Check_ S ee T S 23 .087 M T_GM SC _ S ee TS 2 3.078
UU S1_U UI D ISC2
Yes
Release R esult=
transacti on R econnect?
No
CAM EL_ U U S _M SC_

See TS 23.078 MT _GM S C_ S ee T S 23.087 C hec k_
DIS C 1 U U S 1_UU I
S end Info F or
R e lease M T R econ nected To V LR
C a ll
C C B S _Check _
Last_ C all S ee TS 23.093
R ele ase
c all
r esourc es
W a it_For _
Idle R econnected_
C all _Resul t
Figure 67k: Process ICH_MSC (sheet 11)
3GPP
Release 1999 163 3GPP TS 23.018 V3.12.0 (2003-03)
Proc ess IC H_MSC ICH_M S C12(13)

Proc es s in the MS C W ait_Fo r_ Signal s to/from the l eft
to handle an incomi ng (M T) call F orw ard_C lear are to/from the GMSC ;
are to/from the pr oc ess M T_C F_M SC
R elease R elease
C AMEL_
Release M T_GM SC _ See TS 23.078
D ISC2
CAM EL_ Yes

R esult=
See TS 23.078 MT _GMSC_ R econnect?
DISC 1
No
Send Info F or
R elease M T R econnected To VLR
C all
R elease
c all
resourc es
W ait_For_
Idle R econnected_
C all _Resul t
W ait_For_Forw ard_A CM ,
W ait_For_Forw ard_A nswer,
W ait_For_Forward_Clear
* *
- -
Figure 67l: Process ICH_MSC (sheet 12)
3GPP
Release 1999 164 3GPP TS 23.018 V3.12.0 (2003-03)
Pro c ess IC H _ M SC I C H_ M S C 1 3 (1 3 )
Proc es s in the MS C W ait_For _For war d_A CM , Si gna ls to/fr o m the l eft
to ha ndle an incom i ng ( M T) call W ait_Fo r_For w ar d_Cle ar ar e to /fr om the GM S C ;
si gnals to/fr om the ri ght
ar e to /fr om the pr oc e ss M T_C F_M SC
unless m ar ked othe rw ise
Int_R el ease _
F r om gsm S SF
C al l
R ele ase
R elease
R elease
c al l
r eso urc es
Idle
W ait_F or_ S ignal s to /fr om the l eft

C lear are to/fr om the G M S C ;
si gnals to /fr om the ri ght
are to/from the B S S
un less m ar ked othe rw ise
Int_R el ease _
C al l F r om gsm S SF
R ele ase
tr ansaction
R elease
R elease
c al l
r eso urc es
Idle
Figure 67m: Process ICH_MSC (sheet 13)
3GPP
Release 1999 165 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P age_M S _MS C P AGE _M1(2)

Signal s to/from the l eft Loc ati on No

are to/fro m the BSS; area ID
signals to/from the ri ght known?
are to/from the VLR Yes Set negative
unless m arked othe rw ise resp ons e:
C al l No
Unk now n LAI
still
exis ts ?
Yes Set negativ e
Yes res pons e:
MS System
connection Fai lure
exis ts ?
No
Ye s
Cl ear re ceived:= S MS or SS
False page?
No
No Yes
Pagi ng vi a
MS busy?
SGSN possi ble?
Yes No
C heck _MT_
M ulticall_ MSC See TS 23.135
Yes
In specified R esult =
Pa ge
l oc ation area Offered?
No
R esult = No
Page MS
M ore c alls
vi a SGS N
poss ibl e?
Yes R esult= No
not
provi si one d?
Yes
Yes
C all in
setup?
No
No Yes
C all
w aiting?
Set negati ve Set negativ e

M ore c alls
response: possi ble res pons e:
Busy S ubs criber Busy Subsc riber
(N D UB )
Set acces s Page MS

c onnection negativ e
s tatus response
Sta rt Page
R esult:= R es ult:=
response
Pas s Fail
tim er
W ait_For_
Pa ge_
Res ponse
Figure 68a: Procedure Page_MS_MSC (sheet 1)
3GPP
Release 1999 166 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P age_M S _MS C P AGE _M2(2)

Procedure in t he MSC W ait_For_ Signals to /from the l eft
to page a n M S in a Page_ are to/from the BSS;
specified l ocation area R esponse si gnals to/from the rig ht
are to/from the VLR
MS Page CM
For circuit-
connecti on R elease F rom GMSC re spons e Service
switched call
established timer expi red Re quest
True True CM
Clear C lear To pro cess
A bor t Serv ice
rec ei ved receiv ed OC H_M SC
Re quest
False False
True
Cl ear
rec eived
Fa lse
Set neg ati ve Set n egativ e

response: res pon se:
Absent Busy Subsc riber
Subsc ribe r (N D UB )
Set a ccess Releas e Page MS Page MS

connecti on negative negative
transac ti on
status re spons e res ponse
R esult:= R es ult:= C l ear rec ei ved:= R esult:= R esult:= R esult:= R es ult:=

Pass Aborted T rue A borted F ai l Fail Aborted
W ait_ For_
Page_
R esponse
Figure 68b: Procedure Page_MS_MSC (sheet 2)
3GPP
Release 1999 167 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S earch_F or_M S _M S C S RCH _M 1(2)

Procedure in t he MSC Signals to /from t he left
to search for an MS are to/from the BSS;
(page in all locati on areas) si gnals to/from the rig ht
are to/from the VLR
C al l No
still
exis ts ?
Yes
MS Yes Set negative

connection resp ons e:
exis ts ? System
No Fail ure
Yes
Cl ear re ceived:= S MS or SS
False page?
No
No Yes
Paging via
SGSN possi bl e? M S busy?
Yes No
C heck _MT_
See TS 23.135
M ulticall_ MSC
Search for MS
vi a SGS N
Yes
R esult =
Offered?
No
R esult = No
M ore c alls
poss ibl e?
Yes R esult= No
not
provi si one d?
Yes
Yes
C all in
setup?
No
No Yes
C all
w aiting?
Set negati ve M ore c alls Set negativ e

response: possi ble res pons e:
Busy S ubs criber Busy Subsc riber
(N D UB )
Set acces s Search

In al l
Page c onnection For M S
location areas
s tatus negativ e
response
Sta rt Page
response
Pas s Fail
tim er
W ait_For_
Se arch_
Res ponse
Figure 69a: Procedure Search_For_MS_MSC (sheet 1)
3GPP
Release 1999 168 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S earch_F or_M S _M S C S RCH _M 2(2)

Procedure in t he MSC W ait_For_ Signals to /from the l eft
to search for an MS Search_ are to/from the BSS;
(page in all locati on areas) R esponse si gnals to/from the rig ht
are to/from the VLR
MS Page CM
For circuit-
connecti on R elease F rom GMSC re spons e Service
switched call
established timer expi red Re quest
True True CM
Clear C lear To pro cess
A bor t Serv ice
rec ei ved receiv ed OC H_M SC
Re quest
False False
True
Searc h Releas e Cl ear
For MS ack transac ti on rec eived
Fa lse
Set neg ati ve Set n egativ e

response: res pon se:
Absent Busy Subsc riber
Subsc ribe r (N D UB )
Set a ccess Searc h Searc h

connecti on F or M S For M S
status negative negative
re spons e res ponse
R esult:= R es ult:= C l ear rec ei ved:= R esult:= R esult:= R esult:= R es ult:=

Pass Aborted T rue A borted F ai l Fail Aborted
W ait_ For_
Search_
R esponse
Figure 69b: Procedure Search_For_MS_MSC (sheet 2)
3GPP
Release 1999 169 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C om plete_C all_In _M S C CC I_M S C1(11)

Procedure in t he MSC Signal s t o/from the left
to c omplete an MT ca ll are to/from the BSS;
on request from the VLR signals to/from the right
are to/from the VLR
unless marked otherwi se
Set_C LIP_
Inf o_MSC
D eri ve_
C S_BC _MS C
S etup
U U S_IC H _U US1_
Im plicit_ See TS 23.087
A ctive
C C BS_R eport_
See TS 23.093
N ot_Idl e
W ait_F or_
S etup_
R esponse
S etup Int_R elease_

From gsmSSF
fai lure C all
Set negat ive

r esponse:
A bs ent
S ubs cri ber
C om plete
C al l
negative
response
R esul t:=
F ail
Figure 70a: Procedure Complete_Call_In_MSC (sheet 1)
3GPP
Release 1999 170 3GPP TS 23.018 V3.12.0 (2003-03)
P ro c e d u re C om p le te _ C all_ In _M S C C C I_ M S C 2 (1 1 )
P ro ce d u r e in t h e M S C W a i t_ Fo r_ S ig n a ls to /fr o m t he l eft
to c o mp l e te an M T ca ll S e tu p_ a re to /fro m th e B S S ;
o n r e q u e st fro m th e V L R Re s po n se si g n a ls to /fr om th e rig ht
a re to /fr om th e V L R
C al l
C on fi rm e d
Mu l ti ca l l
su p p o rte d
in M SC ?
No Ye s
E sta b li sh _ E s tab l is h_
Te rm i n at in g _ T e rm i na tin g _ TC H_ S e e TS 2 3 .1 3 5
TC H_ If_ M u l tica l l1
Re q u ir e d
Ye s
Re s u lt=
Fa il ?
No
Ye s CA ME L_
Re s u lt=
A b o rte d M T_ G M S C _ S e e T S 2 3 .0 78
DIS C 4
No
Ye s Ye s
Re s u lt= Re su lt=
Re j e cte d? A bo r t R e co n n e ct?
No No
C AM EL_ S e t n eg a tiv e
M T _ G M S C_ S e e TS 2 3 .0 7 8 re s p on s e:
D IS C6 R a d io
co n g e sti on
C C B S _ ICH _ M S C _ Co mp l e te
S e e TS 2 3 .0 9 3 C a ll
R e p o rt_ Fa ilu r e
n e g ati ve
re s po n se
R e su l t:= R e su lt:= R e su lt:=

A bo r te d R e co n n e ct Fa i l
W a i t_ Fo r_
4
A le r ti n g
Figure 70b: Procedure Complete_Call_In_MSC (sheet 2)
3GPP
Release 1999 171 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Complete_Call_In_MSC CCI_MSC3(11)

Proc edure in the MSC Signals to/f rom t he lef t
t o complete an MT call Wait _F or_ are to/f rom the BSS;
on request from the VLR Alert ing s ignals t o/from the right
are to/f rom the VLR
Alerting Connect
UUS_I CH_ UUS_I CH_

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
Terminat ing_TCH_ See TS 23.135
provi ded?
Multicall2
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_
UTU 2Cnt: =0 See TS 23.078 MT_GMSC_
DISC4
Yes
Wait _f or_ Result=
Answer Reconnect ?
Release Abort
CAMEL_
Abort See TS 23. 078 MT_G MSC_
DI SC6

Reconnect Aborted Abort ed
Figure 70c: Procedure Complete_Call_In_MSC (sheet 3)
3GPP
Release 1999 172 3GPP TS 23.018 V3.12.0 (2003-03)
P ro ce d u r e in t h e M S C S ig n a ls to /fr o m t he l eft
to c o mp l e te an M T ca ll 3 a re to /fro m th e B S S ;
o n r e q u e st fro m th e V L R si g n a ls to /fr om th e rig ht
u n le ss m a r ke d o the r wi se
H a n d le _ A o C _
M T _ MS C
No
R e su l t=
P as s?
2
Ye s
C AM EL_
C o n n ec t
M T_ G M S C _ S e e TS 2 3 .0 7 8 S e t c a us e
ac k
D IS C4
C AM EL_ No
R e su lt=
S e e T S 2 3 .0 78 M T _ G M SC _
R e co n n e ct?
AN SW ER
Ye s
No
R e su l t=
P as s?
Ye s
No S e t_ C O L _
Re s u lt=
R ec o n ne c t? P re se n ta tio n _
In d ic a to r_ M S C
Yes
S en d _ N e two rk _
To G M S C C o n n e ct_ If _ To G MS C Re l e as e
R e q u ir e d
C o m p le te
C all A b o rt
ac k
R es u lt:= R es u lt:= R e su l t:= R e su lt: = R es u lt:=

A b o rte d Re c o nn e ct Pas s R e co n n e ct A b o rte d
Figure 70d: Procedure Complete_Call_In_MSC (sheet 4)
3GPP
Release 1999 173 3GPP TS 23.018 V3.12.0 (2003-03)

Proc edure in the MSC Signals to/f rom the lef t
t o complete an MT call Wait _F or_ are to/f rom the BSS;
on request from the VLR Alert ing s ignals to/from the right
are to/f rom the VLR
Alert ing
1 CD_Request
failure
Release CCBS_ICH _MSC_

See TS 23. 093
transaction Report _Success
Set cause
CAMEL_
MT_G MSC_ See TS 23. 078 Handling_C D_MSC See TS 23. 072
DISC4
Yes
Result=
Reconnect?
No
CCBS_ICH _MSC_
See TS 23. 093
Report _F ailure
Complet e
Abort Call
negativ e
response
Release To GMSC

Reconnect Aborted Fail
Figure 70e: Procedure Complete_Call_In_MSC (sheet 5)
3GPP
Release 1999 174 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he MSC W ait_for_ Signals to /from the l eft
to c omplete an MT ca ll A ns wer are to/from the BSS;
on request from the VLR si gnals to/from the rig ht
are to/from the VLR
C onnec t
C AM EL_
See TS 23.078
S top_TN R y
U U S_ICH _
C heck_ See TS 23.087
S upport
No
R esul t=
P as s?
Yes
Est abl is h_
T erm i nating_ TC H_ See TS 23.135 1
M ulti call2
Yes
R esul t=
P as s?
No
Yes
R esul t=
A borted?
No
C AM EL_
See T S 23.078 M T _GMSC _
D ISC4
Yes
R esul t=
R econnect?
R elease Abort
C AME L_
A bor t See T S 23 .078 MT_GMSC _
D ISC 6
Resu lt:= R esul t:= R esult:=

Reco nnect A borted Aborted
Figure 70f: Procedure Complete_Call_In_MSC (sheet 6)
3GPP
Release 1999 175 3GPP TS 23.018 V3.12.0 (2003-03)
P ro ce d u r e in t h e M S C S ig n a ls to /fr o m t he l eft
to c o mp l e te an M T ca ll 5 a re to /fro m th e B S S ;
o n r e q u e st fro m th e V L R si g n a ls to /fr om th e rig ht
u n le ss m a r ke d o the r wi se
H a n d le _ A o C _
M T _ MS C
No
R e su l t=
2
P as s?
Ye s
C AM EL_
C o n n ec t
M T_ G M S C _ S e e TS 2 3 .0 7 8 S e t c a us e
ac k
D IS C4
C AM EL_ Yes
R e su lt=
S e e T S 2 3 .0 78 M T _ G M SC _
R e co n n e ct?
AN SW ER
Ye s
No
R e su l t=
P as s?
Ye s
No S e t_ C O L _
Re s u lt=
R ec o n ne c t? P re se n ta tio n _
In d ic a to r_ M S C
Yes
S e nd _ A n s we r_
To G M S C T o G MS C Re l e as e
If_ R e qu ir ed
C o m p le te
C all A b o rt
ac k
R es u lt:= R es u lt:= R e su l t:= R e su lt: = R es u lt:=

A b o rte d Re c o nn e ct Pas s R e co n n e ct A b o rte d
Figure 70g: Procedure Complete_Call_In_MSC (sheet 7)
3GPP
Release 1999 176 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C om plete_C all_In _MSC CC I_MSC8(11)

Procedure in t he MSC W ait_for_ Signals to/from the left
on request from the VLR signals to/from the right
are to/from the VLR
unless ma rked otherwise
No Reply
CAM EL TNRy
Call Time r
expired
expired
UUS_ICH_
Forwarding
No
Result=
P as s?
Yes
Set negative
Re lease
response: transac tion
No subsc riber
reply
Complete
Call 2
negative
response
Release
trans action
Result:=
Fail
Figure 70h: Procedure Complete_Call_In_MSC (sheet 8)
3GPP
Release 1999 177 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he MSC W ait_For_Setup_R esponse, Signals to /from the l eft
to c omplete an MT ca ll W ait_For_Ale rting are to/from the BSS;
on request from the VLR si gnals to/from the rig ht
are to/from the VLR
Releas e
Rel eas e From GM SC
transaction
CC BS_IC H_M SC _ CA ME L_
See T S 2 3.093 M T_GM SC _ See T S 23.078
Report _F ailur e
DISC 6
No
Us er CC BS_IC H _M SC _
bus y? Report_F ailu re See T S 23.093
Yes
Se t negative U U S_MSC_ U US _MSC _

resp ons e: C heck_ See TS 23.087 Ch ec k_ See T S 23.087
Bu sy subscriber U U S1_UU I U US 1_U U I
(U D UB)
Complete Rel eas e

C all R elease T o G MS C
transac tion
negativ e
response
Abort
Fail Aborted
Figure 70i: Procedure Complete_Call_In_MSC (sheet 9)
3GPP
Release 1999 178 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure C om plete_C all_In _MSC CC I_MSC10(11)

Procedure in t he MSC W ait_Fo r_ Signals to /from t he left
on request from the VLR signals to/from the rig ht
are to/from the VLR
Release
From GMSC Re lease
transaction
UUS _MSC_
See TS 23 .087 Ch ec k_
UUS 1_UUI
Re lease
transac tion
No CA ME L_
User
See TS 23 .078 MT_GMSC_
bus y?
DI SC6
Ye s
UUS_ICH_ UUS_MSC_
See TS 23.087 Check_ Check_ See TS 23.087
Forwarding UUS1_UUI
No
Resu lt=
Release To G MS C
Pas s?
Ye s
UUS_MSC_ Set negative

See TS 23.087 Check _ response:
UUS1_UUI Bus y subscriber
(UDUB)
Complete
1 Call Abort
negativ e
response
Resu lt:= Result:=

Fail A borted
Figure 70j: Procedure Complete_Call_In_MSC (sheet 10)
3GPP
Release 1999 179 3GPP TS 23.018 V3.12.0 (2003-03)

Proc edure in the MSC
t o complete an MT call Wait _F or_ W ait_For_Alert ing,
on request from the VLR Answer W ait_For_Answer
Signals to/f rom t he lef t

are to/f rom t he BSS; Int _Releas e_
CD R equest From gsmSSF
s ignals t o/from the right Call
are to/f rom t he VLR
UUS_I CH_
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
Complet e
Call Result:=
2
negativ e Aborted
response
Result:=
Fail
Wait _F or_
Answer
User t o User t o
User User
UUS_M SC_ UUS_M SC_

See TS 23. 087 Check_UUS2_ Check_UUS2_ See TS 23. 087
UUI_t o_NW UUI_t o_MS
Wait _F or_
Answer
Figure 70k: Procedure Complete_Call_In_MSC (sheet 11)
3GPP
Release 1999 180 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure P rocess_Call_W aiting_M S C PC W _M SC 1(8)

Procedure in t he MSC Si gnals to/from the l eft
to handle a Process C all W aiti ng are to/from the BSS;
request from the VLR si gnals to/from the ri ght
are to/from the VLR
unless ma rked otherw is e
C W T reatme nt i ndicator No
for existing call set to
CW Allowed?
Yes
Yes
C all being
s et up
No
Set_C LIP_
In fo_M SC
D eri ve_
C S_BC _MS C
Set negative
S etup response:
Busy
s ubs cri ber(N DU B)
U U S_ICH _U US 1_ Process
See TS 23.087 Im pl ici t_ C all W aiti ng
A ctive negative
respons e
C C BS_R eport_ R esul t:=

See TS 23.093
N ot_Id le F ail
W ait_F or_
S etup_
R esponse
C al l
C onfirmed
Es tablis h_
See TS 23.135 T erm inat ing_TC H_
Mult icall 1
No
R esult=
P as s?
Yes
Yes
R esul t=
Aborted?
No
W ait_F or_
4 5
A lerti ng
Figure 71a: Procedure Process_Call_Waiting_MSC (sheet 1)
3GPP
Release 1999 181 3GPP TS 23.018 V3.12.0 (2003-03)
Proced ure P ro cess_Call_ W aiting _M S C PC W _M SC 2( 8)

Procedure in t he M SC Signal s to /from the l eft
to ha ndle a Process C all W a iti ng are to/from the BSS;
requ est from the VL R si gnals to /from the ri ght
are to/from the VLR
un less ma rked otherw ise
W ait_For_
2 4
A lerti ng
Alertin g
Alerti ng C D Request Set c ause
failure
U US _IC H _ CA ME L_
C C BS_ ICH _M SC_
Ch ec k_ See T S 2 3.087 Se e TS 23 .093 M T_GM SC _ See T S 23.093
R eport_ Succes s
Support DI SC 4
No Yes
Re sult= H andli ng_ Re su lt=
Se e TS 23 .072
Pass? C D_ MSC R eco nnect?
No
Yes
Process
Releas e R es ult:=
For w aiting c al l C all W aiting
transac ti on Rec onn ec t
negative
response
R esult:=
2
F ai l
CC BS_IC H _M SC _ CC BS_IC H _M SC _
See T S 2 3.093 See T S 23.093
Re port_S ucce ss Repo rt_F ail ure
To GM SC of
UT U2 Cnt:=0 Re lea se
wai ting call
No
N RC T
Abort
provi ded?
Yes
Start Start R esu lt:=

No R e ply Acceptan ce
Aborted
C all T im er tim er
CA ME L_
See T S 2 3.078
Start_TN R y
Send_ACM _ To GM SC o f
If_Required waiting call
W a it_For_
Acceptance
Figure 71b: Procedure Process_Call_Waiting_MSC (sheet 2)
3GPP
Release 1999 182 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he M SC W ait_Fo r_ Signals to /from t he left
to ha ndle a Process C all W a iti ng S etu p_ are to/from the BSS;
requ est from the VL R R esponse si gnals to/from th e rig ht
R elease R e lease
Int_R eleas e_
transacti on Se tup fail ure trans action From gsm SSF
C all
(rej ect) (U D U B)
UU S_IC H_ C lear U U S_ICH _

See TS 23.087 Check_ pending C hec k_ See TS 2 3.087
Support c al l Support
CAM EL_
MT _GM SC_ See T S 23 .078
DISC 4
Yes
Resu lt=
Reco nne c t?
No
Set neg ati ve

CC BS_ICH _M SC _
See T S 23 .093 response:
Report_F ailure
Busy
subs cri ber(U D U B)
Process
T o GM SC of
R elease C all W aiting
w aiti ng c al l
negative
respons e
C C BS_IC H _M SC_
Abort See T S 23.093
R epo rt_ Failure
R es ult:= Resu lt:= R esult: =

Rec onn ec t Aborted F ai l
Figure 71c: Procedure Process_Call_Waiting_MSC(sheet 3)
3GPP
Release 1999 183 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he M SC W ait_For_Setup_R esponse, Signals to /from t he left
to ha ndle a Process C all W a iti ng W ait_For_Ale rting are to/from the BSS;
requ est from the VL R si gnals to/from th e rig ht
F rom GM SC o f
R elease
w aiti ng c al l
C C BS_ICH _M SC_
See TS 23.093
R eport_Fai lure
U U S_M SC_
C heck_ See TS 23.087
U U S1_UU I
R elease
F or wa iting cal l
transacti on
C AM EL_
M T _GM SC_ See TS 23.078
D ISC6
A bort
R eleas e c all
F or wa iting cal l
r esourc es
R esul t:=
A borted
Figure 71d: Procedure Process_Call_Waiting_MSC(sheet 4)
3GPP
Release 1999 184 3GPP TS 23.018 V3.12.0 (2003-03)

Procedure in t he MSC W ait_for _ Signal s t o/from the left
to handle a Process C all W aiti ng Ac ceptanc e are to/from the BSS;
request from the VLR signals to/from the right
are to/from the VLR
Int_R eleas e_
From gsm SSF C onnec t
C al l
C AM EL_
Abort See TS 23.078
S top_T NR y
U U S_ICH _
Rel eas e
transac ti on C heck_ See TS 23.087
S upport
No
To G MSC of R esul t=
Rel eas e
w aiting cal l P as s?
Yes
R es ult:= M ulticall T o G MSC of

s upported Releas e
Aborted w aiting cal l
i n M SC ?
No Yes
Es tabl is h_ Establi sh_

Te rminating_ T erminating_T CH _ See TS 23.135
T CH _If_ M ulticall2
R equired
3 2
Figure 71e: Procedure Process_Call_Waiting_MSC(sheet 5)
3GPP
Release 1999 185 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Process_Call_Waiting_MSC PCW_MSC6(8)

3
Procedure in the MSC Signals to the r ight
to handle a Process Call Waiting are to the VLR
request from the VLR
Yes No
Result=
Pass?
5
Yes
Handle_AoC_ Result=
MT_MSC Aborted?
No
No
Result=
Pass?
Yes
CAMEL_
Connect
ack
DISC4
Yes
CAMEL_ CAMEL_
Result=
See TS 23.078 MT_GMSC_ See TS 23.078 MT_GMSC_
Reconnect?
ANSW ER DISC6
No
Yes
Result= To GMSC of
Release Abort
Reconnect? waiting call
No
Release call
Abort For waiting call
resources

Reconnect Aborted Aborted
No
Result=
Pass?
Yes
Set_COL_
Presentation_
Indicator_MSC
Send_
To GMSC of To GMSC of
Answer_If_ Release
waiting call waiting call
Required
Process Call
Abort
Waiting ack
Result:= Result:=
Pass Aborted
Figure 71f: Procedure Process_Call_Waiting_MSC(sheet 6)
3GPP
Release 1999 186 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Process_Call_W aiting_MSC PC W _MSC 7(8)

Procedure in t he MSC Signals t o/from the left
to handle a Process Call W aiting are to/from the BSS;
request from the VLR W ait_for_ signals to/from the right
Ac ceptanc e are to/from the VLR
1
Re lease Release No Reply
Ac ceptanc e CAMEL TNRy
transac tion transaction Call Timer
timer expired expired
(bus y) (reject) expired
UUS_ICH_
See TS 23.087 Check _
Forwarding
No
Res ult=
Pass?
Yes
Set negative
Release
For wait ing call resp ons e:
tra ns action
No s ubs criber
reply
CAMEL_ CAMEL_ Proces s

MT_GMSC_ See TS 23.078 MT_GMSC_ See TS 23.078 Call W aiting
DISC4 DISC5 negativ e
response
UUS _ICH_ Yes

Result= Releas e
Chec k_ See TS 23.087 For waiting call
Recon nec t? transac tion
Forwarding
No
No UUS_ICH_
Result= Result:= Res ult:=
Pass? Reconnect Fail
Forwarding
Yes
Set n egativ e UUS_MSC_

To GMSC of
res pon se: Check _ Release
waiting c all
Busy UUS1_UUI
subsc riber(UDUB )
Process
Ca ll W aiting 2 A bort
negative
res ponse
Result:= Result:=
Fail A borted
Figure 71g: Procedure Process_Call_Waiting_MSC(sheet 7)
3GPP
Release 1999 187 3GPP TS 23.018 V3.12.0 (2003-03)

to handle a Process C all W aiti ng are to/from the BSS;
request from the VLR signals to/from the right
are to/from the VLR
W ait_For_
Acceptance
From GMSC of U ser T o From G MSC of Us er To

Re lease C D R equest
waiting cal l U ser activ e c al l Us er
U US _MSC _ UU S_IC H_ U U S_M SC_ U US _M SC _

C hec k_ See T S 23.087 Check_ See T S 23 .087 C hec k_U US 2_ See TS 23.087 Check _UU S2_
U US 1_U U I Forw ardi ng U U I_to_N W UU I_to_M S
No
Re lease Resu lt= W ait_For_
transac tion For w aiti ng c all Pas s? Acceptance
Ye s
Handling_ C D _U US_ W ai t_For_Se tup_R esponse,

See TS 23.072 Se e GSM 03.72
CD _MS C Inter action W ait_For_Alerti ng
C AME L_
From G MSC of
M T_GM SC _ See T S 23.078 Rel eas e
waiti ng call
D ISC 6
Process
CC BS_IC H _MSC _
Abort Call W ai ti ng See TS 23.093
Report_F ailure
negativ e
response
U US_MSC _
R elease call
res ources For w aiti ng c all See TS 23.087 Check _
U US1_U UI
R esult:= Resu lt:= Rel eas e

F or wa iting cal l
Aborted Fail transac tion
CA MEL_
1 See TS 23.078 MT _GM SC_
DISC 6
Abort
Rel ease call

F or wa iting cal l
res ources
R es ult:=
Aborted
Figure 71h: Procedure Process_Call_Waiting_MSC(sheet 8)
3GPP
Release 1999 188 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S et_CLIP_Info_MS C CA INF_M 1( 1)

to determi ne the C LIP
inform ati on to be s ent to the MS

Initi ate
C LIP _M AF 002
handli ng
of C LIP
W ait_F or_
C LIP_Info
C ontinue
Re lease
transac ti on From BSS c all Re lease From GM SC
handli ng
Figure 72: Procedure Set_CLIP_Info_MSC
3GPP
Release 1999 189 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure D erive_CS _BC _M S C DR BC _M 1(1)

Proc edure in the MSC to
deriv e th e reque ste d G SM BC
for an inc om ing (M T) c all
according to the ru les of
GSM 0 9.07
No C S BC derived from
ISD N co mpatibi lity
info rmation?
Yes
Yes
C S BC recei ved
in PR N ?
No
U se C S BC U se C S BC
Omit C S B C
from Setup r ecei ved derived from
i n PR N ISD N compati bili ty
inf ormation
Figure 73: Derive_CS_BC_MSC
3GPP
Release 1999 190 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure E stablish_T erm inating_T C H_If_Required E T TC IR 1(1)

Procedure in t he term inati ng VM SC Signals to /from t he left
to es tablish a Traffic C hannel are to/from the BSS;
if one ha s n ot been established sig nals to/from the right
for this c all are to/from the GM SC
True
TC H
al located
Fals e
Al locate R esult:=
c hannel Pass
W ait_Fo r_
Allocatio n_
C om plete
Releas e A lloc ation Al locati on

Re lease
transac tion fa ilure com plete
R elease T C H al located:= Rel eas e

transacti on True transac tion
R esu lt:= R esult := R esult:=

F ail Pass Aborted
Figure 74: Procedure Establish_Terminating_TCH_If_Required
3GPP
Release 1999 191 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure H andle_A oC _MT _MS C A OCMT _M 1(1)

to handle AoC signalling are to/from the BSS;
towards the M S for an M T c al l signal s from the right
are from the AoC ti mer function.
Yes
A oC(I)
provi sioned?
No
Set No
AoC (C )
charging provi sioned?
param eters
Yes
Send S et
Charging c harging
Param eters pa ramete rs
Send
C harging
Parameters
S tart AoC
ac knowl edg ment
ti mer
W ait_F or_
C harging_
Parame ters_
Ac k
C harging R elease AoC

Param eters ack no wledgm ent
c onne ction
ack tim er expired
R elease
trans action

Pass F ail
Figure 75: Procedure Handle_AoC_MT_MSC
3GPP
Release 1999 192 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S et_CO L_P resentation_Indicator_M S C CO IN D_M 1(1)

to determi ne the C OL
presentation i ndi cator v alue

Initi ate
C OLR _M AF 041
handli ng
of C OLR
W ait_F or_
C OLR _Info
C ontinue
Release
transac tion From BSS c all Re lease From GM SC
handli ng
Figure 76: Procedure Set_COL_Presentation_Indicator MSC
3GPP
Release 1999 193 3GPP TS 23.018 V3.12.0 (2003-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, this is treated as an unknown MSRN.
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: the procedure CCBS_ICH_Set_CCBS_Call_Indicator is specific to CCBS; it is specified in 3GPP

TS 23.093 [22].
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 [22].
Sheet 1, sheet 3: the procedure CCBS_ICH_Report_Not_Reachable is specific to CCBS; it is specified in 3GPP

TS 23.093 [22].
Sheet 2: this process communicates with the matching instance of the process PRN_VLR, which is linked by the MSRN.
Sheet 2: the test "Paging via SGSN possible" takes the "yes" exit if:
- 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 [22]. If the
VLR does not support CCBS, processing continues from the "Forward" exit of the test "Result".
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 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?".
3GPP
Release 1999 194 3GPP TS 23.018 V3.12.0 (2003-03)
Sheet 5, sheet 6: the procedure CCBS_ICH_Handle_UDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [22].
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 [22].
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 Procedure Derive_Requested_Basic_Service_VLR

If the VLR did not receive a basic service for the call in the Send Info For Incoming Call, and did not receive a GSM
bearer capability in the Provide Roaming Number, it applies a default basic service according to the requirements of the
operator.
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.
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 1999 195 3GPP TS 23.018 V3.12.0 (2003-03)
Process ICH_VLR ICH_VLR1(8)

Proc es s in VLRB to Signals to/f rom the lef t
handle a request f or inf ormation are to/f rom t he MSC
f or an i ncoming (MT) call
Idle
Send Info
For I ncoming
Call
No
MSR N
known?
Yes
CAMEL_
See TS 23. 078
ICH_VLR
Yes Result=
Fail?
No
CCBS_ICH _ Set negat ive

Set _CCBS_ See TS 23. 093 respons e:
Call_Indicator Unallocat ed
Roaming Number
False
Data
Idle confirmed
by H LR
True
Set negativ e
Derive_Reques ted_ response:
Basic _Service_VLR System
Failure
Yes
IMSI CCBS_ICH _VLR_
See TS 23. 093
detac hed? Report_F ailure
No
No
Roaming
in LA
allowed?
Yes
CCBS_ICH _ Send Inf o

Report _Not_ For I ncoming
Reachable Call negative
respons e
1 10 I dle
Figure 77a: Process ICH_VLR (sheet 1)
3GPP
Release 1999 196 3GPP TS 23.018 V3.12.0 (2003-03)

10
Proc es s in VLRB to
handle a request f or inf ormation
f or an i ncoming (MT) call Signals to t he lef t
are to t he VMSC;
Signals to/f rom the right
Prepaging are to/f rom t he proces s PRN_VLR.
supported?
Yes No
True
PAR
pending
False
Wait_F or_
PAR_Complet ed
PAR
complet ed
True
PAR
succ ess ful
False
Call
arriv ed
True
Fatal PAR
11
error
False
Set negativ e No Yes

Locat ion
response: area ID
Impossible call known?
complet ion
No
CCBS_ICH _VLR_ Paging v ia
See TS 23. 093
Report_F ailure SGSN possible?
Yes
Send Info Set Paging

For I ncoming via SG SN
Call negati ve possible
response
Search_For_ Page type=

Idle Page MS
MS_VLR c ircuit -switched call
Yes
Result=
Pass ?
No
Yes
Result=
Fail?
No
CCBS_ICH _VLR_
See TS 23. 093
Report_F ailure
Wait _F or_
Idle 2 Access_
Request
Figure 77b: Process ICH_VLR (sheet 2)
3GPP
Release 1999 197 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in VLRB to Signals to/f rom the left
handle a request f or inf ormation are t o/f rom the VMSC.
Wait _F or_
Access_
Request
Page MS
negativ e Page MS
2 Abort
response via SG SN
Absent
Page MS To SG SN
subscriber ?
Yes
No
No
CCBS_ICH _ Wait _F or_
Busy CCBS_I CH_VLR_
See TS 23. 093 Report _Not _ Access_ See TS 23. 093
subscriber ? Report _Failure
Reachable Request
Yes
3
1 Idle
Yes
NDUB?
No
Multic all
s upport ed
in VLR?
No Yes
Get _CW _ Get_CW _

Subsc ript ion_ Subsc ript ion_Info_
Inf o_VLR Multicall_VLR
No
CW
available?
Yes
Get _LI _
Subsc ript ion_ CCBS_ICH _
See TS 23.093
Inf o_MT_VLR Handle_NDUB
Release
Get _AoC_
Subsc ript ion_ Result
Inf o_VLR
Forward
4 8 5
Figure 77c: Process ICH_VLR (sheet 3)
3GPP
Release 1999 198 3GPP TS 23.018 V3.12.0 (2003-03)
Process ICH_VLR Wait _F or_

ICH_VLR4(8)
Access_
Proc es s in VLRB to Request Signals to/from t he lef t
handle a request f or inf ormation are to/from t he VMSC.
Proc ess
Access
Request
Proc ess _
Access_
Request _VLR
No
Result=
11
Pass ?
Yes
Yes
CUG
info
present?
Translat e CUG
No interlock As defined in CCBS_IC H_VLR_
See TS 23. 093
to index TS 23.085 Report _F ailure
Yes
Succ ess? Idle
CAMEL_CHECK No
_SI I2_C DTI
Yes
Result =
Pass ?
No
CFN Ry No
A&O?
Yes
Prov ide
NRCT 3
value
Get _LI _
Subsc ript ion_
Inf o_MT_VLR
Get _AoC_ Set negativ e

Subsc ript ion_ response:
Inf o_VLR System f ai lure
CLI_ICH_VLR_ CCBS_ICH _VLR_

See TS 23.081 See TS 23. 093
Add_CLI Report _F ailure
Send Inf o
Complet e For I ncoming
Call Call negati ve
response
Wait _F or_
Complet e_Call_ Idle
Result
Figure 77d: Process ICH_VLR (sheet 4)
3GPP
Release 1999 199 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in VLRB to Wait_f or_ Signals to/f rom the left
handle a request f or inf ormation Complet e_Call are t o/f rom the VMSC.
f or an i ncoming (MT) call Result
Complet e
Complet e Call negati ve
Abort
Call ack response
Yes
Busy
Idle
subscriber ?
No
CCBS_I CH_
See TS 23. 093
Handle_UDUB
Yes
Absent
subscriber ?
No
Yes
Radio
conges tion?
No
Yes
No
subscriber
reply ?
No
CD_ CCBS_IC H_VLR_

See TS 23. 072 See TS 23. 093
Aut horization Report _F ailure
No
Result=
Aborted?
Yes
No Set negativ e
Result= response: 6 1 5
Fail? Impossible call
completion
Yes
Send Inf o
For I ncoming
Call negati ve
response
7 Idle
Figure 77e: Process ICH_VLR (sheet 5)
3GPP
Release 1999 200 3GPP TS 23.018 V3.12.0 (2003-03)

4
Proc es s in VLRB to Signals to/f rom the left
handle a request f or inf ormation are t o/f rom the VMSC.
CAMEL_CHECK
See TS 23. 078
_SI I2_C DTI
Yez
Result =
Pass ?
No
No CFN Ry
A&O ?
Yea
Set NRCT
CLI_ICH_VLR_
See TS 23. 081
Add_CLI
Proc ess
Call
Wait ing
Wait_F or_
PCW_Result
Proc ess Proc ess

Call Abort Call W ait ing
Waiting ack negativ e
response
Yes
Busy
Idle
subscriber ?
No
Yes
No
subscriber NDUB?
reply ?
Yes
No No
CD_
See TS 23. 072 9
Aut horization
No
Result=
Aborted?
Yes
No Set negativ e
Result= response: CCBS_ICH _
See TS 23. 093
Fail? Impossible call Handle_UDUB
completion
Yes Send Info

For I ncoming
Call negati ve
response
7 Idle 6 5
Figure 77f: Process ICH_VLR (sheet 6)
3GPP
Release 1999 201 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in VLRB to Signals to t he left
handle a request f or inf ormation are to t he VMSC 1
Handle_CFNRc
Yes
Result=
Fail?
Handle_CFB
Set negativ e No
response:
Forwarding
Violat ion
Result=
Yes Forward?
Result= No
Fail? Yes
No Set negativ e Set negativ e

response: response:
Forwarding Absent
Violat ion Subsc riber 7
8 Handle_CFNRy
No Yes
Result= Result=
Forward? Fail?
Yes No
CCBS_ICH _ Set negativ e

Set_CCBS_ See TS 23. 093 response:
Target Forwarding No
Violat ion Result=
Forward?
Set negativ e Set negativ e Yes

response: response:
Busy No Subsc riber
Subsc riber Reply
CCBS_ICH _ Send Inf o

Set _CCBS_ See TS 23. 093 For I ncoming
Target Call negati ve
response
7 Idle 7
Figure 77g: Process ICH_VLR (sheet 7)
3GPP
Release 1999 202 3GPP TS 23.018 V3.12.0 (2003-03)

Proc es s in VLRB to Signals to t he left
handle a request f or inf ormation 7 are to t he VMSC.
Forward_
CUG _Check
No
Result=
Call
allowed?
Yes
Set negat ive

Set result: response:
Forward CUG rejec t
Set
forwarding
informat ion
CAMEL_
O_C SI_ See TS 23. 078
CHECK_VLR
CAMEL_
D_CSI _ See TS 23. 078
CHECK_VLR
Send Info Send Inf o

For I ncoming For I ncoming
Call ack Call negati ve
response
Idle Idle
Figure 77h: Process ICH_VLR (sheet 8)
3GPP
Release 1999 203 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure D erive_Reque sted_B asic_S ervice_VLR DR BS _V1(1)

Proc edure in the V LR to
deriv e the requeste d basi c
serv ice for an incom ing
(M T) call
Yes
Ba si c servic e inc luded in
Send Info F or Incomin g C all?
No
Basic serv ice:= Yes

C S BC received in
BS received in Provide R oaming N um ber
SIFIC
No
Bas ic s ervice:=
B as ic se rvi ce:=
BS deriv ed from default
CS BC
Figure 78: Procedure Derive_Requested_Basic_Service_VLR
3GPP
Release 1999 204 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure S earch_F or_M S _V LR S RCH _V1(1)

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

are to/fro m the MS C No
Pagin g v ia
SGSN possi ble?
Yes
S et paging
v ia SGSN
poss ible
Search Pa ge type=
F or M S C ircuit-sw itched call
W ait_Fo r_
S earch_R es ult
Search S ear ch Search f or MS

F or M S Abort
For MS ack via S GSN
n egativ e
response
Up date
Location T o SGS N Page M S
Are a ID
R esult:= Resu lt:= R esult: =

Pass Fail Aborted
W ait_For_
Search _Result
Figure 79: Procedure Search_For_MS_VLR
3GPP
Release 1999 205 3GPP TS 23.018 V3.12.0 (2003-03)
Proc edure G et_CW _Subscription_Info_VLR CW I_VLR1(1)

inform ati on for th e
C al l W aiting servic e

initiate
M AF013
handling
of C W
W ait_For_
C W _Info
process
From MS C Abort c al l
w aiti ng
Figure 80: Procedure Get_CW_Subscription_Info_VLR
3GPP
Release 1999 206 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Get_LI_Subscription_Info_M T_V LR GLI_MT V 1(1)

inform ation for the C LIP
& C OLR li ne i dentificati on
serv ices for an MT call
Initi ate
handl ing T o process CLIP_MAF001
of C LIP
W ait_F or_
C LIP_Info
C ontinue
From MS C Abort c all F rom proc es s C LIP _M AF 001
handli ng
Initi ate
handl ing T o process CO LR _MAF040
of C OLR
W ait_F or_
C OLR _Info
C ontinue
From MS C Abort c all F rom process CO LR _M AF040
handli ng
Figure 81: Procedure Get_LI_Subscription_Info_MT_VLR
3GPP
Release 1999 207 3GPP TS 23.018 V3.12.0 (2003-03)
Procedure Handle_CFB H_CFB1(1)

Proc edure in the VLR
t o handle Call Forwarding
on Bus y

MAF008
CAMEL_CHECL
See TS 23. 078
_SI I2_C DTI
No
Result =
Pass ?
Yes
initiate
handling
of CFB
Wait_F or_
CFB_Res ult
continue
call
handling
Yes
Error?
No
Yes
Normal
call
busy?
No

Fail Forward Busy
Figure 82: Procedure Handle_CFB
3GPP
Release 1999 208 3GPP TS 23.018 V3.12.0 (2003-03)
Pro cedure H andle_C FN Ry H_C FN Ry1( 1)

to handle C all F orw ardi ng
on N o subscriber Repl y

i nitiate
M AF009
handli ng
of C FN R y
W ait_F or_
C FN R y_R es ult
c onti nue
c all
handli ng
Yes
E rror?
No
No
N orm al
c all?
Yes

Fail N o re ply Forward
Figure 83: Procedure Handle_CFNRy
3GPP
Release 1999 209 3GPP TS 23.018 V3.12.0 (2003-03)
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;
- 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.
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 MS:

RAND(I) M Random number challenge to be sent to the MS (3GPP
TS 33.102 [31])
AUTN(I) M Authentication token to be sent to the MS (3GPP TS 33.102 [31])
The following information elements are required for authentication of a GSM MS:

RAND M Random number challenge to be sent to the MS (GSM 03.20 [1])
CKSN M Cipher key sequence number to be sent to the MS
(GSM 03.20 [1])
3GPP
Release 1999 210 3GPP TS 23.018 V3.12.0 (2003-03)
8.1.3 Authenticate ack

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

RES(I) M Result returned by the MS (3GPP TS 33.102 [31])
The following information element is required

for authentication of a GSM MS:

SRES M Signature result returned by the MS (GSM 03.20 [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.
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
3GPP
Release 1999 211 3GPP TS 23.018 V3.12.0 (2003-03)
present for an ordinary MO call and for an emergency call when

the MS is registered in the VLR; otherwise shall be absent.
GSM bearer capability C Shall be present for an MT call if it was received in the Provide
Roaming Number; otherwise shall be absent.
ISDN bearer capability C Shall be present for an MT call if it was received in the Provide
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.
(continued)
3GPP
Release 1999 212 3GPP TS 23.018 V3.12.0 (2003-03)
The following information elements are required (concluded):

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.
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.
3GPP
Release 1999 213 3GPP TS 23.018 V3.12.0 (2003-03)
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

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.
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.
8.1.18 Page MS ack

The following information elements are required :

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;
8.1.19 Page MS negative response

- Busy subscriber (More calls possible);
3GPP
Release 1999 214 3GPP TS 23.018 V3.12.0 (2003-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.
3GPP
Release 1999 215 3GPP TS 23.018 V3.12.0 (2003-03)
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.
8.1.22 Process Access Request ack


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.
3GPP
Release 1999 216 3GPP TS 23.018 V3.12.0 (2003-03)
8.1.23 Process Access Request negative response

- Roaming not allowed;
- System failure;
- Unidentified subscriber;
- Illegal equipment;
- Illegal subscriber.
8.1.24 Process Call Waiting


MSISDN M MSISDN of the MS for which the Process Call Waiting is sent.
GSM bearer capability C Shall be present if it was received in the Provide Roaming Number
for the waiting call; otherwise shall be absent.
ISDN bearer capability C Shall be present if it was received in the Provide Roaming Number
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.
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

3GPP
Release 1999 217 3GPP TS 23.018 V3.12.0 (2003-03)
8.1.28 Provide IMEI ack


IMEI M IMEI of the ME involved in the access request.
8.1.29 Provide IMSI
3GPP
Release 1999 218 3GPP TS 23.018 V3.12.0 (2003-03)
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


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.
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;
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;
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 1999 219 3GPP TS 23.018 V3.12.0 (2003-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 GSM bearer service required for the MT call. Shall be present if
the MSC was able to derive a GSM bearer service from ISDN
BC/LLC/HLC information received in the IAM; otherwise shall be
absent.
Teleservice C GSM teleservice required for the MT call. Shall be present if the
MSC was able to derive a GSM 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.
3GPP
Release 1999 220 3GPP TS 23.018 V3.12.0 (2003-03)
8.1.37 Send Info For Incoming Call ack


IMSI M IMSI of the B subscriber.
Forwarded-to number M E.164 number of the C subscriber.
Forwarding reason M 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).
Notification to calling party M Indication of whether the calling party is to be notified that the call
has been forwarded.
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.
3GPP
Release 1999 221 3GPP TS 23.018 V3.12.0 (2003-03)
8.1.38 Send Info For Incoming Call negative response

- Busy subscriber;
- CUG reject (Called party SS interaction violation);
- Forwarding violation;
- 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 GSM
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 GSM 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.
3GPP
Release 1999 222 3GPP TS 23.018 V3.12.0 (2003-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 [31]).
IK M Integrity key to be used to verify the integrity of messages
transferred over the radio link (see 3GPP TS 33.102 [31]).
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 GSM 12.08 [3]
8.1.43 Use existing TMSI

3GPP
Release 1999 223 3GPP TS 23.018 V3.12.0 (2003-03)
8.2 Messages on the C interface (MSC-HLR)

8.2.1 Send Routeing Info

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 HPLMN
supports CUG, otherwise shall be absent.
present if the GMSC received it in the IAM and the HPLMN
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.
3GPP
Release 1999 224 3GPP TS 23.018 V3.12.0 (2003-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.
3GPP
Release 1999 225 3GPP TS 23.018 V3.12.0 (2003-03)
8.2.3 Send Routeing Info negative response

- Bearer service not provisioned;
- Call barred (Operator determined barring);
- Call barred (Supplementary service barring);
- CUG reject (Called party SS interaction violation);
- CUG reject (Incoming calls barred within CUG);
- 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.
3GPP
Release 1999 226 3GPP TS 23.018 V3.12.0 (2003-03)
8.3 Messages on the D interface (VLR-HLR)

8.3.1 Provide Roaming Number

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.
GSM bearer capability C Information to define the GSM bearer capability required for the
call. For alternate speech/fax, alternate speech/data or speech
followed by data calls this information element shall contain two
GSM bearer capabilities, as specified in 3GPP TS 24.008. May be
present if the HLR can determine the required GSM 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 GSM 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
GSM 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 GSM 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.
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

- Data missing;
3GPP
Release 1999 227 3GPP TS 23.018 V3.12.0 (2003-03)
- 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 whether the HLR requires location information,
subscriber state or both location information and subscriber state.
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.
8.3.5 Provide Subscriber Info ack


Location information C Information to define the location of the MS: see definition in
clause 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.
3GPP
Release 1999 228 3GPP TS 23.018 V3.12.0 (2003-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 [34]. 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.
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
absent.
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 [34]. 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.
8.3.6 Provide Subscriber Info negative response

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


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.
3GPP
Release 1999 229 3GPP TS 23.018 V3.12.0 (2003-03)
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 1999 230 3GPP TS 23.018 V3.12.0 (2003-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 1999 231 3GPP TS 23.018 V3.12.0 (2003-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 1999 232 3GPP TS 23.018 V3.12.0 (2003-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 process 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.
Sheet 2: after the MSC co-ordinating process has sent an IAM to an instance of the process MT_GMSC or ICH_MSC,
it acts as a transparent relay for messages received from the originating exchange and the process instance (denoted by
"offspring"). After the MSC co-ordinating process has relayed a Release message, it returns to the idle state.
Sheet 2: after the MSC co-ordinating process has sent an IAM to a destination exchange, it acts as a transparent relay
for messages received from the originating exchange and the destination exchange. After the MSC co-ordinating
process has relayed a Release message, it returns to the idle state.
3GPP
Release 1999 233 3GPP TS 23.018 V3.12.0 (2003-03)
Process MSC _Coord C oord_M1(2)

Proc ess in the MSC to
ha ndle an incoming IAM
and trigger the correc t
application process
ID LE
Initial From
Addres s originating
exchange
Called party address No

in MSRN range
for t hi s MSC?
Yes
No Inc oming IAM was

routed with ro utei ng
n umber for MN P?
Yes
Recov er No
HLR address
ported number
d eriv able?
from IAM
Yes
T o process Initial Initi al T o process Initial To des tination

IC H_ MSC Addres s A ddress MT _G MS C Addres s determined by
rou teing tables
Relay_ Relay_
I nformation_ Information_
I nternally External ly
Figure 84a: Process MSC_Coord (sheet 1)
3GPP
Release 1999 234 3GPP TS 23.018 V3.12.0 (2003-03)
Process M S C_Coord Coord_M 2(2)

Proc ess in the MS C to R el ay_
handle an inco mi ng IA M Infor mati on_
and tri gger the correct Inter nal ly
appl ic ati on process
From
Re lease originating R elease F rom of fspring
exchange
To
Re lease To offspring R elease origi nati ng
exchange
From
ID LE * originating ID LE * From of fspri ng
ex change
To
- To of fspri ng - originating
ex change
R el ay_ R elay_
Inform ation_ Inform ation_
Internall y Internal ly
R el ay_
Infor mati on_
E xt ernall y
From F rom
Re lease originating R elease des ti nati on
exchange exchange
To To
Re lease desti nati on R elease origi nati ng
exchange exchange
From From
ID LE * originating ID LE * desti nati on
ex change ex change
To To
- destination - originating
ex change ex change
R el ay_ R elay_
Inform ation_ Inform ation_
Externally Externally
Figure 82b: Process MSC_Coord (sheet 2)
3GPP
Release 1999 235 3GPP TS 23.018 V3.12.0 (2003-03)
Annex B:
Change history
Change history
TSG CN# Spec Version CR <Phase> New Version Subject/Comment

Apr 1999 GSM 03.18 7.0.0 Transferred to 3GPP CN1
CN#03 23.018 R99 3.0.0 Approved at CN#03
CN#04 23.018 3.0.0 001 R99 3.1.0 Notification of Call Forwarding to the
gsmSCF
CN#05 23.018 3.1.0 002r4 R99 3.2.0 Addition of the description for Pre-Paging
CN#05 23.018 3.1.0 006 R99 3.2.0 Removal of TDP criteria from Resume Call
Handling
CN#05 23.018 3.1.0 007r1 R99 3.2.0 GMSC CAMEL phases in Provide Roaming
Number
CN#05 23.018 3.1.0 023 R99 3.2.0 Separation of success & failure cases for
OR of late call forwarding
CN#05 23.018 3.1.0 024 R99 3.2.0 Notification of Call Forwarding to the
gsmSCF before activating call forwarding
process
CN#06 23.018 3.2.0 004r2 R99 3.3.0 Introduction of the Super-Charger Concept
in TS 23.018
23.018 3.2.0 027r3 R99 3.3.0 Introduction of CAMEL Phase 3
CN#07 23.018 3.3.0 025r7 R99 3.4.0 Addition of the description for Multicall
23.018 3.3.0 026r2 R99 3.4.0 Alternative solution for ALR
23.018 3.3.0 030 R99 3.4.0 Correction of the SDL diagrams for Pre-
paging
23.018 3.3.0 032r1 R99 3.4.0 Inclusion of D-CSI check in HLR/VLR
23.018 3.3.0 033 R99 3.4.0 Initialisation of Backward Call indicator
23.018 3.3.0 034 R99 3.4.0 Correction of the result of the procedure
CAMEL_ICH_MSC_INIT
23.018 3.3.0 037 R99 3.4.0 Clarification of N-CSI in Core NW
23.018 3.3.0 039r2 R99 3.4.0 Replacement of references to GSM with
references to UMTS
23.018 3.3.0 043r1 R99 3.4.0 Clarification of NPDB error detection and
MNP specific call handling
23.018 3.3.0 044 R99 3.4.0 Setting the Destination Address for MO calls
23.018 3.3.0 047 R99 3.4.0 O-CSI and D-CSI checks for ORLCF calls
23.018 3.3.0 048 R99 3.4.0 Correction of CF Notification
23.018 3.3.0 049 R99 3.4.0 Introduction of Authentication Failure Report
23.018 3.3.0 050r3 R99 3.4.0 ISUP release cause value
CN#08 23.018 3.4.0 045r1 R99 3.5.0 Correction of CAMEL Incoming Call
Handling
23.018 3.4.0 051r4 R99 3.5.0 Improvement of Active Retrieval of Location
Information procedure
23.018 3.4.0 052r2 R99 3.5.0 North American Service Provider Number
Portability impacts for MNP
CN#09 23.018 3.5.0 053 R99 3.6.0 Correction of connector numbering in
process ICH_MSC
23.018 3.5.0 054 R99 3.6.0 Correction of the SDL diagram for Pre-
paging
23.018 3.5.0 056 R99 3.6.0 Correction to process ICH_VLR
23.018 3.5.0 057r3 R99 3.6.0 Handling of the Call Diversion Treatment
Indicator
23.018 3.5.0 059r1 R99 3.6.0 Modifications to procedure obtain routeing
address.
23.018 3.5.0 060 R99 3.6.0 Corrections to process ICH_VLR
23.018 3.5.0 061r2 R99 3.6.0 Update of CAMEL references
23.018 3.5.0 063r1 R99 3.6.0 Correction of procedure
Obtain_Routeing_Address for the reconnect
case
CN#11 23.018 3.6.0 068 R99 3.7.0 Paging not via the SGSN correction
3GPP
Release 1999 236 3GPP TS 23.018 V3.12.0 (2003-03)
Change history
TSG CN# Spec Version CR <Phase> New Version Subject/Comment

CN#12 23.018 3.7.0 073 R99 3.8.0 Initialisation of variable to monitor activation
of CSIs
CN#13 23.018 3.8.0 075 R99 3.9.0 Addition of missing process
Update_Location_VLR
CN#13 23.018 3.8.0 R99 3.9.0 Editorial clean up
CN#14 23.018 3.9.0 078 R99 3.10.0 Missing connector in procedure
Process_Call_Waiting_MSC
CN#14 23.018 3.9.0 079 R99 3.10.0 Handling of Reconnect on Leg2 Disconnect
CN#14 23.018 3.9.0 089r2 R99 3.10.0 Corrections in the ATI mechanism
description
CN#15 23.018 3.10.0 086r2 R99 3.11.0 Handling of CUG calls in non-supporting
networks
CN#15 23.018 3.10.0 096 R99 3.11.0 Correction on the Active Location Retrieval
description
CN#15 23.018 3.10.0 101r1 R99 3.11.0 MSISDN in Provide Roaming Number in
case of MSP
CN#19 23.018 3.11.0 116r1 R99 3.12.0 Correction to wrong implementation of
approved CR 089r2 and 096
3GPP

3GPP TS 23.018

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

3GPP TS 23.018

Uploaded by

Copyright:

Available Formats

3GPP TS 23.018 V3.12.

3rd Generation Partnership Project;

GLOBAL SYSTEM FOR

3GPP support office address

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

7.1.1.12 Procedure Send_Access_Connect_If_Required ......................................................................................... 25

7.3.1.4 Procedure Complete_Call_In_MSC .............................................................................................................. 148

8.2 Messages on the C interface (MSC-HLR)........................................................................................................... 223

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

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 Indicates TSG approved document under change control.

For a specific reference, subsequent revisions do not apply.

[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 (CD) supplementary service; Stage2".

[13] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical Realisation".

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

[23] 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2".

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

[26] 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling".

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

[31] 3GPP TS 33.102: "3G Security; Security Architecture ".

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

PRN Provide Roaming Number

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

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

GMSC HLRB VLRB VMSCB BSSB MSB

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

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

5.3 Information flow for an MT call

GMSCB VLRB VMSCB BSSB MSB

Figure 5: Information flow for a basic mobile terminated call

- 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

6.1 Call Deflection service (3GPP TS 23.072)

6.2 Line identification services (3GPP TS 23.081)

6.2.2 Calling Line Identification Restriction (CLIR)

6.2.3 Connected Line Identification Presentation (COLP)

6.2.4 Connected Line Identification Restriction (COLR)

6.3 Call forwarding services (3GPP TS 23.082)

6.3.2 Call Forwarding on mobile subscriber Busy (CFB)

6.3.3 Call Forwarding on No Reply (CFNRy)

6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)

6.4 Call wait (3GPP TS 23.083)