3GPP TS 03.18

3rd Generation Partnership Project;
Technical Specification Group Core Network;

3GPP TS 03.18
Digital cellular telecommunications system (PhaseV7.5.0
2+);(2003-12)
Basic call handling;
Technical Specification
Technical realization
(Release 1998)
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 1998 2 3GPP TS 03.18 V7.5.0 (2003-12)
Keywords
GSM, basic, call
3GPP
Postal address
3GPP support office address

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

The copyright and the foregoing restriction extend to reproduction in
all media.
© 2004, 3GPP Organizational Partners (ARIB, CCSA, ETSI, T1, TTA,TTC).

All rights reserved.
3GPP
Release 1998 3 3GPP TS 03.18 V7.5.0 (2003-12)
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.............................................................................................................................12
5.2 Information flow for retrieval of routeing information for an MT call...................................................................14
5.3 Information flow for an MT call.............................................................................................................................15
6 Principles for interactions with supplementary services.......................................................................17
6.1 Call Deflection service (GSM 03.72)......................................................................................................................17
6.2 Line identification services (GSM 03.81)...............................................................................................................18
6.2.1 Calling Line Identification Presentation (CLIP)................................................................................................18
6.2.2 Calling Line Identification Restriction (CLIR).................................................................................................18
6.2.3 Connected Line Identification Presentation (COLP).........................................................................................18
6.2.4 Connected Line Identification Restriction (COLR)..........................................................................................18
6.3 Call forwarding services (GSM 03.82)...................................................................................................................18
6.3.1 Call Forwarding Unconditional (CFU)..............................................................................................................18
6.3.2 Call Forwarding on mobile subscriber Busy (CFB)..........................................................................................18
6.3.3 Call Forwarding on No Reply (CFNRy)...........................................................................................................18
6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)......................................................................18
6.4 Call wait (GSM 03.83)............................................................................................................................................18
6.5 Call hold (GSM 03.83)............................................................................................................................................19
6.6 Multiparty (GSM 03.84).........................................................................................................................................19
6.7 Closed user group (GSM 03.85).............................................................................................................................19
6.8 Advice of charge (GSM 03.86)...............................................................................................................................19
6.9 User-to-user signalling (GSM 03.87)......................................................................................................................19
6.10 Call barring (GSM 03.88)..................................................................................................................................19
6.10.1 Barring of outgoing calls...................................................................................................................................19
6.10.2 Barring of incoming calls..................................................................................................................................19
6.11 Explicit Call Transfer (GSM 03.91)..................................................................................................................19
6.12 Completion of Calls to Busy Subscriber (GSM 03.93).....................................................................................19
7 Functional requirements of network entities.........................................................................................20
7.1 MO call....................................................................................................................................................................20
7.1.1 Functional requirements of serving MSC..........................................................................................................20
7.1.1.1 Process OCH_MSC...........................................................................................................................................20
7.1.1.2 Procedure Process_Access_Request_MSC.......................................................................................................21
7.1.1.3 Procedure OG_Call_Setup_MSC......................................................................................................................21
7.1.1.4 Procedure Obtain_IMSI_MSC..........................................................................................................................22
7.1.1.5 Procedure Authenticate_MSC...........................................................................................................................22
7.1.1.6 Procedure Obtain_IMEI_MSC..........................................................................................................................22
7.1.1.7 Procedure Check_IMEI_MSC...........................................................................................................................22
7.1.1.8 Procedure Establish_Originating_TCH_If_Required........................................................................................23
7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC............................................................................................23
7.1.1.10 Procedure Send_Alerting_If_Required........................................................................................................23
7.1.1.11 Procedure Set_COLP_Info_MSC................................................................................................................23
7.1.1.12 Procedure Send_Access_Connect_If_Required..........................................................................................23
7.1.1.13 Procedure Handle_AoC_MO_MSC............................................................................................................23
3GPP
Release 1998 4 3GPP TS 03.18 V7.5.0 (2003-12)
7.1.2 Functional requirements of VLR.......................................................................................................................46

7.1.2.1 Process OCH_VLR............................................................................................................................................46
7.1.2.2 Procedure Process_Access_Request_VLR........................................................................................................46
7.1.2.3 Procedure OG_Call_Subscription_Check_VLR...............................................................................................46
7.1.2.4 Procedure Obtain_Identity_VLR.......................................................................................................................46
7.1.2.5 Procedure Obtain_IMSI_VLR...........................................................................................................................46
7.1.2.6 Procedure Authenticate_VLR............................................................................................................................46
7.1.2.7 Procedure Obtain_Authentication_Sets_VLR...................................................................................................47
7.1.2.8 Procedure Start_Tracing_VLR..........................................................................................................................47
7.1.2.9 Procedure Check_IMEI _VLR..........................................................................................................................47
7.1.2.10 Procedure Obtain_IMEI _VLR....................................................................................................................47
7.1.2.11 Process Fetch_Authentication_Sets_VLR...................................................................................................47
7.1.2.12 Procedure Check_BAOC.............................................................................................................................47
7.1.2.13 Procedure OG_CUG_Check........................................................................................................................47
7.1.2.14 Procedure Get_LI_Subscription_Info_MO_VLR........................................................................................47
7.1.2.15 Procedure Get_AoC_Subscription_Info_VLR............................................................................................47
7.1.2.16 Procedure Check_OG_Barring....................................................................................................................47
7.2 Retrieval of routeing information for MT call........................................................................................................73
7.2.1 Functional requirements of GMSC....................................................................................................................73
7.2.1.1 Process MT_GMSC...........................................................................................................................................73
7.2.1.2 Procedure Obtain_Routeing_Address...............................................................................................................74
7.2.1.3 Procedure Send_ACM_If_Required..................................................................................................................75
7.2.1.4 Procedure Send_Answer_If_Required..............................................................................................................75
7.2.1.5 Procedure Send_Network_Connect_If_Required.............................................................................................75
7.2.1.6 Procedure Handle_COLP_Forwarding_Interaction_MSC................................................................................76
7.2.1.7 Procedure Activate_CF_Process.......................................................................................................................76
7.2.1.8 Process MT_CF_MSC.......................................................................................................................................76
7.2.2 Functional requirements of HLR.......................................................................................................................98
7.2.2.1 Process SRI_HLR..............................................................................................................................................98
7.2.2.2 Procedure Check_Parameters............................................................................................................................98
7.2.2.3 Procedure Subscription_Check_HLR................................................................................................................98
7.2.2.4 Procedure First_Forwarding_HLR....................................................................................................................99
7.2.2.5 Procedure PRN_Error_HLR..............................................................................................................................99
7.2.2.6 Procedure Forward_CUG_Check......................................................................................................................99
7.2.2.7 Procedure Derive_Requested_Basic_Service_HLR..........................................................................................99
7.2.2.8 Procedure Check_IC_Barring............................................................................................................................99
7.2.2.9 Procedure IC_CUG_Check...............................................................................................................................99
7.2.2.10 Procedure Handle_CFU...............................................................................................................................99
7.2.2.11 Procedure Handle_CFNRc...........................................................................................................................99
7.2.3 Functional requirements of VLR.....................................................................................................................115
7.2.3.1 Process PRN_VLR..........................................................................................................................................115
7.2.3.2 Process Restore_Subscriber_Data_VLR.........................................................................................................115
7.2.3.3 Process PSI_VLR............................................................................................................................................115
7.2.3.4 Procedure Retrieve_Location_Info_VLR........................................................................................................115
7.2.4 Functional requirements of MSC....................................................................................................................123
7.2.4.1 Process OSI_MSC...........................................................................................................................................123
7.3 MT call..................................................................................................................................................................124
7.3.1 Functional requirements of serving MSC........................................................................................................124
7.3.1.1 Process ICH_MSC...........................................................................................................................................124
7.3.1.2 Procedure Page_MS_MSC..............................................................................................................................125
7.3.1.3 Procedure Search_For_MS_MSC...................................................................................................................125
7.3.1.4 Procedure Complete_Call_In_MSC................................................................................................................126
7.3.1.5 Procedure Process_Call_Waiting_MSC..........................................................................................................127
7.3.1.6 Procedure Set_CLIP_Info_MSC.....................................................................................................................127
7.3.1.7 Procedure Derive_GSM_BC_MSC.................................................................................................................128
7.3.1.8 Procedure Establish_Terminating_TCH_If_Required....................................................................................128
7.3.1.9 Procedure Handle_AoC_MT_MSC................................................................................................................128
7.3.1.10 Procedure Set_COL_Presentation_Indicator_MSC...................................................................................128
7.3.2 Functional requirements of VLR.....................................................................................................................154
7.3.2.1 Process ICH_VLR...........................................................................................................................................154
7.3.2.2 Procedure Derive_Requested_Basic_Service_VLR........................................................................................155
3GPP
Release 1998 5 3GPP TS 03.18 V7.5.0 (2003-12)
7.3.2.3 Procedure Search_For_MS_VLR....................................................................................................................155

7.3.2.4 Procedure Get_CW_Subscription_Info_VLR.................................................................................................155
7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR............................................................................................155
7.3.2.6 Procedure Handle_CFB...................................................................................................................................155
7.3.2.7 Procedure Handle_CFNRy..............................................................................................................................155
8 Contents of messages..........................................................................................................................168
8.1 Messages on the B interface (MSC-VLR)............................................................................................................168
8.1.1 Abort................................................................................................................................................................168
8.1.2 Authenticate.....................................................................................................................................................168
8.1.3 Authenticate ack..............................................................................................................................................168
8.1.4 Check IMEI.....................................................................................................................................................168
8.1.5 Check IMEI ack...............................................................................................................................................169
8.1.6 Check IMEI negative response........................................................................................................................169
8.1.7 Complete Call..................................................................................................................................................169
8.1.8 Complete Call ack............................................................................................................................................170
8.1.9 Complete Call negative response.....................................................................................................................170
8.1.10 Forward New TMSI.........................................................................................................................................170
8.1.11 Forward New TMSI ack..................................................................................................................................170
8.1.12 Forward New TMSI negative response...........................................................................................................170
8.1.13 Obtain Subscriber Info.....................................................................................................................................171
8.1.14 Obtain Subscriber Info ack..............................................................................................................................171
8.1.15 Page MS...........................................................................................................................................................171
8.1.16 Page MS negative response.............................................................................................................................171
8.1.17 Page MS via SGSN..........................................................................................................................................172
8.1.18 Process Access Request...................................................................................................................................172
8.1.19 Process Access Request ack............................................................................................................................172
8.1.20 Process Access Request negative response.....................................................................................................173
8.1.21 Process Call Waiting.......................................................................................................................................173
8.1.22 Process Call Waiting ack.................................................................................................................................173
8.1.23 Process Call Waiting negative response..........................................................................................................173
8.1.24 Provide IMEI...................................................................................................................................................173
8.1.25 Provide IMEI ack.............................................................................................................................................174
8.1.26 Provide IMSI...................................................................................................................................................174
8.1.27 Provide IMSI ack.............................................................................................................................................174
8.1.28 Search For MS.................................................................................................................................................174
8.1.29 Search For MS ack..........................................................................................................................................174
8.1.30 Search For MS negative response...................................................................................................................174
8.1.31 Search for MS via SGSN.................................................................................................................................175
8.1.32 Send Info For Incoming Call...........................................................................................................................175
8.1.33 Send Info For Incoming Call ack....................................................................................................................176
8.1.34 Send Info For Incoming Call negative response..............................................................................................177
8.1.35 Send Info For Outgoing Call...........................................................................................................................177
8.1.36 Send Info For Outgoing Call negative response..............................................................................................177
8.1.37 Set ciphering mode..........................................................................................................................................178
8.1.38 Trace subscriber activity..................................................................................................................................178
8.1.39 Use existing TMSI...........................................................................................................................................178
8.2 Messages on the C interface (MSC-HLR)............................................................................................................178
8.2.1 Send Routeing Info..........................................................................................................................................178
8.2.2 Send Routeing Info ack...................................................................................................................................179
8.2.3 Send Routeing Info negative response............................................................................................................180
8.3 Messages on the D interface (VLR-HLR).............................................................................................................181
8.3.1 Provide Roaming Number...............................................................................................................................181
8.3.2 Provide Roaming Number ack........................................................................................................................181
8.3.3 Provide Roaming Number negative response..................................................................................................181
8.3.4 Provide Subscriber Info...................................................................................................................................182
8.3.5 Provide Subscriber Info ack............................................................................................................................182
8.3.5.1 Location information.......................................................................................................................................182
8.3.6 Provide Subscriber Info negative response.....................................................................................................182
8.3.7 Restore Data....................................................................................................................................................184
8.3.8 Restore Data ack..............................................................................................................................................184
8.3.9 Restore Data negative response.......................................................................................................................184
3GPP
Release 1998 6 3GPP TS 03.18 V7.5.0 (2003-12)
8.4 Messages on the F interface (MSC-EIR)..............................................................................................................184

8.4.1 Check IMEI.....................................................................................................................................................184
8.4.2 Check IMEI ack...............................................................................................................................................184
8.4.3 Check IMEI negative response........................................................................................................................184
8.5 Messages on the MSC internal interface...............................................................................................................185
8.5.1 CF cancelled....................................................................................................................................................185
8.5.2 Perform Call Forwarding.................................................................................................................................185
8.5.3 Perform Call Forwarding ack..........................................................................................................................185
8.5.4 Perform Call Forwarding negative response...................................................................................................185
8.6 Messages on the Gs interface................................................................................................................................185
8.6.1 Page MS...........................................................................................................................................................185
8.6.2 Send MS information.......................................................................................................................................186
8.6.3 Send MS information ack................................................................................................................................186
8.6.4 Send MS information negative response.........................................................................................................186
Annex A (informative): Handling of an IAM at an MSC................................................................187

Annex B (informative): Change History.............................................................................................190
3GPP
Release 1998 7 3GPP TS 03.18 V7.5.0 (2003-12)
Foreword
This Technical Specification (TS) has been produced by the Special Mobile Group (SMG).
The present document specifies the technical realisation of the handling of calls originated by a GSM mobile subscriber
and calls directed to a GSM mobile subscriber, up to the point where the call is established within the digital cellular
telecommunications system (Phase 2+).
The contents of the present document may be subject to continuing work within SMG and may change following formal
SMG approval. Should SMG modify the contents of the present document it will then be re-submitted for formal
approval procedures by ETSI with an identifying change of release date and an increase in version number as follows:
Version 7.x.y
where:
7 GSM Phase 2+ Release 1998;
x the second digit is incremented for changes of substance, i.e. technical enhancements, corrections, updates,
etc.
y the third digit is incremented when editorial only changes have been incorporated in the specification;
3GPP
Release 1998 8 3GPP TS 03.18 V7.5.0 (2003-12)
1 Scope
The present document specifies the technical realisation of the handling of calls originated by a GSM mobile subscriber
and calls directed to a GSM mobile subscriber, up to the point where the call is established. Normal release of the call
after establishment is also specified.
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 GSM supplementary services on the handling of a call are described in the relevant
GSM 03.7x, GSM 03.8x and GSM 03.9x 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 (GSM 03.78 [8]) and optimal routeing (GSM 03.79 [10]). The use of the Provide
Subscriber Information message flow is shown in GSM 03.78 [8] and GSM 03.79 [10].
The specification of the handling of data calls re-routed to a SIWFS is described in GSM 03.54 [4].
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 this specification and the corresponding stage 3 specifications (GSM 04.08 [20],
GSM 08.08 [22] and GSM 09.02 [23]), 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.
 A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
 For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of

telecommunication services supported by a GSM Public Land Mobile Network (PLMN)".
[2] GSM 03.03: "Digital cellular telecommunications system (Phase 2+); Numbering, addressing &
identification".
[3] GSM 03.20: "Digital cellular telecommunications system (Phase 2+); Security related network
functions".
[4] GSM 03.54 (TS 101 252): "Digital cellular telecommunications system (Phase 2+);Description for
the use of a Shared Inter Working Function /SIWF) in a GSM PLMN Stage 2".
[5] GSM 03.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio
Service; Service description; Stage 2".
[6] GSM 03.66: "Digital cellular telecommunications system (Phase 2+); Support of Mobile Number
Portability (MNP); Technical Realization – Stage 2".
[7] GSM 03.72: "Digital cellular telecommunications system; Call Deflection (CD) supplementary
service; Stage2".
3GPP
Release 1998 9 3GPP TS 03.18 V7.5.0 (2003-12)
[8] GSM 03.78 (TS 101 044): "Digital cellular telecommunications system (Phase 2+); Customized

Applications for Mobile network Enhanced Logic (CAMEL) - Stage 2".
[9] GSM 03.78: "Digital cellular telecommunications system (Phase 2+); Customized Applications for
Mobile network Enhanced Logic (CAMEL) - Phase 2; Stage 2".
[10] GSM 03.79 (TS 101 045): "Digital cellular telecommunications system (Phase 2+); Support of

Optimal Routeing (SOR); Technical Realization".
[11] GSM 03.81: "Digital cellular telecommunications system (Phase 2+); Line identification
supplementary services - Stage 2".
[12] GSM 03.82: "Digital cellular telecommunications system (Phase 2+); Call Forwarding (CF)
[13] GSM 03.83: "Digital cellular telecommunications system (Phase 2+); Call Waiting (CW) and Call
Hold (HOLD) supplementary services - Stage 2".
[14] GSM 03.84: "Digital cellular telecommunications system (Phase 2+); Multi Party (MPTY)
[15] GSM 03.85: "Digital cellular telecommunications system (Phase 2+); Closed User Group (CUG)
[16] GSM 03.86: "Digital cellular telecommunications system (Phase 2+); Advice of Charge (AoC)
[17] GSM 03.87: "Digital cellular telecommunications system (Phase 2+); User –to-User Signalling
(UUS) Supplementary Services - Stage 2".
[18] GSM 03.88: "Digital cellular telecommunications system (Phase 2+); Call Barring (CB)
supplementary services - Stage 2 (GSM 03.88)".
[19] GSM 03.93: "Digital cellular telecommunications system (Phase 2+); Technical realization of
Completion of Calls to Busy Subscriber (CCBS) - Stage 2".
[20] GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface
layer 3 specification".
[21] GSM 07.01: "Digital cellular telecommunications system (Phase 2+); General on Terminal
Adaptation Functions (TAF) for Mobile Stations (MS)".
[22] GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile-services Switching
Centre - Base Station System (MSC - BSS) interface Layer 3 specification".
[23] GSM 09.02: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part
(MAP) specification".
[24] GSM 09.07: "Digital cellular telecommunications system (Phase 2+); General requirements on
interworking between the Public Land Mobile Network (PLMN) and the Integrated Services
Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
[25] GSM 09.10: "Digital cellular telecommunications system (Phase 2+); 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) (GSM 09.10)".
[26] GSM 12.08: "Digital cellular telecommunications system (Phase 2+); Subscriber and equipment
trace (GSM 12.08)".
[27] ETS 300 356-1 (1995): "Integrated Services Digital Network (ISDN); Signalling System No. 7;
ISDN User Part (ISUP) version 2 for the international interface; Part 1: Basic services".
[28] 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 1998 10 3GPP TS 03.18 V7.5.0 (2003-12)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
A subscriber: calling mobile subscriber.
B subscriber: mobile subscriber originally called by the A subscriber.
C subscriber: subscriber to whom the B subscriber has requested that calls be forwarded. The C subscriber may be
fixed or mobile.
Location Information: information to define the whereabouts of the MS, and the age of the information defining the
whereabouts.
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
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
PRN Provide Roaming Number
SGSN Serving GPRS support node
SIFIC Send Information For Incoming Call
3GPP
Release 1998 11 3GPP TS 03.18 V7.5.0 (2003-12)
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.
Radio I/F signalling '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 this specification, 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.
NOTE: When the non-loop method is used for data calls, the IAM is sent to the SIWFS.
3GPP
Release 1998 12 3GPP TS 03.18 V7.5.0 (2003-12)
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 GSM 03.60 [5]) 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 GSM networks is that a call to a GSM 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
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 "A" interface between
BSSA and VMSCA is shown by dashed lines; signalling over the B interface between VMSCA and VLRA is shown by
chain lines; and ISUP signalling between VMSCA and the destination exchange is shown by solid lines.
3GPP
Release 1998 13 3GPP TS 03.18 V7.5.0 (2003-12)
MSA BSSA VMSCA VLRA
CM service req
CM service req
Process access req
Authenticate
Authenticate
Authenticate (note 1)
Authenticate resp
Authenticate resp
Authenticate ack
Set cipher mode

(note 2)
Process access req
Start ciphering
Cipher mode cmd ack
(note 3)
(note 3)
Cipher mode comp
Cipher mode comp
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
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: Ciphering may be initiated at any stage after authentication; its position in this message flow diagram is
an example.
NOTE 3: If ciphering is not required, 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.
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 ciphering or explicitly after ciphering
has started; this is not shown in this message flow diagram.
3GPP
Release 1998 14 3GPP TS 03.18 V7.5.0 (2003-12)
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 GSM 03.20 [3]. VLRA may also initiate ciphering at
this stage, as described in GSM 03.20 [3].
If VLRA determines that MSA is allowed service, it sends a Process access request ack to VMSCA. If VMSCA has
received a Set cipher mode message from VLRA, the Process access request ack message triggers a Start ciphering
command message towards BSSA; otherwise VMSCA sends a CM service accept message towards BSSA.
If BSSA receives a Start ciphering command from VMSCA, it initiates ciphering as described in GSM 03.20 [3]; when
ciphering is successfully initiated, MSA interprets this in the same way as a CM service accept. If ciphering is not
required at this stage, BSSA relays the CM service accept to MSA.
When MSA has received the CM service accept, or ciphering has 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 GSM 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 Alert 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.
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 is shown by chain lines.
GMSC HLRB VLRB VMSCB

IAM
SRI
PRN
PRN ack
SRI ack
IAM
Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call
3GPP
Release 1998 15 3GPP TS 03.18 V7.5.0 (2003-12)
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. HLRB sends a request for a roaming number
(PRN) to VLRB. 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 "A" interface 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 1998 16 3GPP TS 03.18 V7.5.0 (2003-12)
GMSCB VLRB VMSCB BSSB MSB

IAM
SIFIC
Page MS
Page
Page
Chan req
Imm ass
Page resp
MS conn
Process estab
access req
Set cipher
mode (note 1)
Process
access req ack Start
ciphering Cipher mode
(note 2) command
Cipher mode
complete
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: Ciphering may be initiated at any stage after the network has accepted the page response; its position in
this message flow diagram is an example.
NOTE 2: If ciphering is not required, the MSC may send a "start ciphering" request indicating that no ciphering is
required.
NOTE 3: This message flow diagram assumes that the MS has already been authenticated on location registration.
If this is not so (for the first MT call after VLR restoration), the network may initiate authentication after
the MS responds to paging.
NOTE 4: The network may request the IMEI from the MS, and may check the IMEI, at any stage after the MS
responds to paging, either as part of the procedure to start ciphering or explicitly after ciphering has
started; this is not shown in this message flow diagram.
3GPP
Release 1998 17 3GPP TS 03.18 V7.5.0 (2003-12)
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
GSM 03.60 [5]) 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 GSM 03.20 [3]. VLRB may also initiate
ciphering at this stage, as described in GSM 03.20 [3].
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 ciphering command message towards BSSB; if VMSCB has not received a Set
cipher mode message from VLRB, the Start ciphering command indicates no ciphering.
VLRB then sends a Complete call message to VMSCB. VMSCB sends a Set-up message towards MSB. The Set-up
message may include bearer capability information for the call.
When MSB receives the Set-up message from BSSB, it responds with a Call confirmed message. The Call Confirmed
message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be
changed. When VMSCB receives the Call confirmed message via BSSB, it sends an Allocate channel message to
BSSB. BSSB instructs MSB to tune to a traffic channel by sending an Assignment command. When MSB has tuned to
the specified traffic channel it responds with an Assignment complete, message, which BSSB relays to VMSCB as an
Allocation complete, and sends an Alerting message to indicate that the called user is being alerted. VMSCB sends an
ACM to GMSCB, which relays it to the originating exchange.
When the called user answers, MSB sends a Connect message, which BSSB relays to VMSCB. VMSCB:
- responds with a Connect ack message towards MSB;
- sends an ANM to GMSCB, which relays it to the originating exchange;
- sends a Complete call ack to VLRB.
The network then waits for the call to be cleared.
6 Principles for interactions with supplementary

services
This clause specifies the principles used to describe the invocation of the GSM supplementary services which were
standardised when this specification was drafted. Registration, erasure, activation, deactivation and interrogation are
call-independent operations; they are therefore outside the scope of this specification. Descriptions may be found in the
stage 2 specifications for each supplementary service.
In the modelling used in this specification, 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
this specification use the data to define the contents of messages to other entities. The basic call handling processes
defined in this specification 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 (GSM 03.72)

The basic call handling processes ICH_MSC and ICH_VLR interact with the CD supplementary service (GSM 03.72)
as described in subclauses 7.3.1 and 7.3.2 respectively.
3GPP
Release 1998 18 3GPP TS 03.18 V7.5.0 (2003-12)
6.2 Line identification services (GSM 03.81)

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 (GSM 03.81 [11]) 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 (GSM 03.81 [11]) 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 (GSM 03.81 [11]) 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 [11] 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 (GSM 03.81 [11]) as described in subclauses 7.3.2 and 7.3.1.
6.3 Call forwarding services (GSM 03.82)

6.3.1 Call Forwarding Unconditional (CFU)
The basic call handling process SRI_HLR interacts with the process MAF007(GSM 03.82 [12]) as described in
subclause 7.2.2
6.3.2 Call Forwarding on mobile subscriber Busy (CFB)

The basic call handling process ICH_VLR interacts with the process MAF008 (GSM 03.82 [12]) as described in
subclause 7.3.2
6.3.3 Call Forwarding on No Reply (CFNRy)

The basic call handling process ICH_VLR interacts with the process MAF009 (GSM 03.82 [12]) as described in
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 (GSM 03.82 [12]) as
described in subclauses 7.2.2 and 7.3.2.
6.4 Call wait (GSM 03.83)

The basic call handling process ICH_VLR interacts with the process MAF013(GSM 03.83 [13]) as described in
subclause 7.3.2. Further details of the handling of call waiting are given in subclauses 7.3.1 and 7.3.2.
3GPP
Release 1998 19 3GPP TS 03.18 V7.5.0 (2003-12)
6.5 Call hold (GSM 03.83)

Invocation of call hold before a basic call has been established will be rejected.
6.6 Multiparty (GSM 03.84)

Invocation of multiparty before a basic call has been established will be rejected.
6.7 Closed user group (GSM 03.85)

The basic call handling process OCH_VLR interacts with the process CUG_MAF014 (GSM 03.85 [15]) as described in
subclause 7.1.2.
The basic call handling process SRI_HLR interacts with the process CUG_MAF015 (GSM 03.85 [15]) as described in
subclause 7.2.2.
The interactions between call forwarding and CUG (GSM 03.85 [15]) are handled as described in subclause 7.2.2.6.
6.8 Advice of charge (GSM 03.86)

The interactions between Advice of Charge (GSM 03.86 [16]) and MO calls are handled as described in
subclauses 7.1.1 and 7.1.2.
The interactions between Advice of Charge (GSM 03.86 [16]) and MT calls are handled as described in
subclauses 7.3.1 and 7.3.2.
6.9 User-to-user signalling (GSM 03.87)

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

6.10.1 Barring of outgoing calls
The basic call handling process OCH_VLR interacts with the processes MAF017, MAF018 and MAF020
(GSM 03.88 [18]) 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 (GSM 03.88 [18]) as
described in subclause 7.2.2.
6.11 Explicit Call Transfer (GSM 03.91)

There is no interaction between Explicit Call Transfer and the basic call handling described in this specification.
6.12 Completion of Calls to Busy Subscriber (GSM 03.93)

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.2 respectively.
3GPP
Release 1998 20 3GPP TS 03.18 V7.5.0 (2003-12)
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 three different types of interface:
- the A interface, used to interwork between the MSC and the BSS or the 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 A interface are BSSMAP, which is specified in GSM 08.08 [22], for interworking with the
BSS and DTAP, which is specified in GSM 04.08 [20], for interworking with the MS.
The protocol used over the C, D & F interfaces is MAP, which is specified in GSM 09.02 [23].
For the purposes of this specification, the protocol used over telephony signalling interfaces is ISUP, which is specified
in ETS 300 356-1 [27]; other telephony signalling systems may be used instead.
This specification 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 this
specification, 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 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.
For the entities which support CAMEL, the references to GSM 03.78 are to the version of GSM 03.78 for the
appropriate phase of CAMEL.
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.
3GPP
Release 1998 21 3GPP TS 03.18 V7.5.0 (2003-12)
The procedures CCBS_Report_Not_Idle and CCBS_Check_Last_Call are specific to CCBS; they are specified in
GSM 03.93 [19].
7.1.1.2 Procedure Process_Access_Request_MSC

Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC, the VMSC may encapsulate the request for the
IMEI in the Start ciphering request; the BSS relays the response in the Cipher Mode complete message to the MSC.
Sheet 2: the VMSC maps the negative response received on the B interface to the appropriate reject cause according to
the rules defined in ETS 300 607 [25].
Sheet 2: The Start ciphering request may indicate one of several ciphering algorithms, or no ciphering.
Sheet 2, sheet 3: At any stage, the MS may terminate the transaction with the network by sending a CM service abort
message.
Sheet 2, sheet 3: if the VMSC receives a Set-up message from the MS while the access request is being handled, the
message is saved for processing after the access request has been handled.
7.1.1.3 Procedure OG_Call_Setup_MSC

Sheet 1: the variables Alerting sent, MS connected and Reconnect are global data, accessible to the procedures
CCBS_Check_OG_Call, CCBS_OCH_Report_Failure, CCBS_OCH_Report_Success,
CCBS_Check_If_CCBS_Possible, Send_Alerting_If_Required and Send_Access_Connect_If_Required.
Sheet 1: the VMSC converts the GSM bearer capability negotiated between the VMSC and the MS to a GSM basic
service according to the rules defined in GSM 07.01 [21].
Sheet 1: the variable UUS1 result sent is specific to UUS. This variable is accessible to all UUS specific procedures.
Sheet 1: the procedure UUS_OCH_Check_Setup is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 1, sheet 2, sheet 5: the procedure CCBS_OCH_Report_Failure is specific to CCBS; it is specified in

GSM 03.93 [19].
Sheet 1, sheet 5, sheet 6, sheet 8: at any stage after the Set-up has been received, the MS may terminate the transaction
with the network by sending a Release transaction request.
Sheet 2: the procedure Set_CLI_Presentation_Indicator_MSC is specific to CLIR. If the VMSC does not support CLIR,
processing continues from the "Yes" exit of the test "Result=Call allowed?".
Sheet 2: the procedure CAMEL_OCH_MSC_INIT is specific to CAMEL; it is specified in GSM 03.78 for

CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL, processing
continues from the "Yes" exit of the test "Result=Pass?".
Sheet 2: the procedure CCBS_Check_OG_Call is specific to CCBS; it is specified in GSM 03.93 [19]. If the VMSC
does not support CCBS, processing continues from the "Yes" exit of the test "Result=Pass?".
Sheet 2: the procedure UUS_OCH_Set_Info_In_IAM is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 2: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is

specified in GSM 03.66 [6].
Sheet 3: the procedure CCBS_OCH_Report_Success is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 3, sheet 6: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2; they
are specified in GSM 03.78 for CAMEL Phase 2 [9].
Sheet 3: the task "UTU2Cnt := 0" is executed only if the VMSC supports UUS
Sheet 4: the procedure CAMEL_OCH_MSC_ANSWER is specific to CAMEL; it is specified in GSM 03.78 for

Sheet 4: the procedure Set_COLP_Info_MSC is specific to COLP.
3GPP
Release 1998 22 3GPP TS 03.18 V7.5.0 (2003-12)
Sheet 4: the procedure Handle_AoC_MO_MSC is specific to AoC.
Sheet 5: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS; they are
specified in GSM 03.93 [19]. The task "Store CCBS Result" is executed only if the VMSC supports CCBS. If the
VMSC does not support CCBS, processing continues from the "CCBS Not Possible" exit of the test "CCBS Result".
Sheet 5, sheet 6: the procedures CAMEL_OCH_MSC_DISC3 and CAMEL_OCH_MSC_DISC4 are specific to

CAMEL; they are specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]
respectively.
Sheet 5, sheet 6: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2; it is specified in GSM 03.78 for
CAMEL Phase 2 [9]. If the VMSC does not support CAMEL phase 2, processing continues from the "No" exit of the
test "Result=Reconnect?".
Sheet 5, sheet 6, sheet 8: the processing in the branch beginning with the Int_Release_Call input will occur only if the
MSC supports CAMEL.
Sheet 6, sheet 8: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 7: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2, and will
occur only if the VMSC supports CAMEL phase 2. The procedure CAMEL_OCH_MSC2 is specified in GSM 03.78
for CAMEL Phase 2 [9].
Sheet 7: the input signal User To User is specific to UUS; it is discarded if the VMSC does not support UUS.
Sheet 7: the procedures UUS_MSC_Check_UUS2_UUI_to_MS and UUS_MSC_Check_UUS2_UUI_to_NW are

specific to UUS; they are specified in GSM 03.87 [17].
Sheet 8: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL; it is specified in GSM 03.78 for

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,
3GPP
Release 1998 23 3GPP TS 03.18 V7.5.0 (2003-12)
Release Complete or Disconnect. The VMSC aborts the transaction with the VLR and returns an aborted result to the
parent process.
7.1.1.8 Procedure Establish_Originating_TCH_If_Required
7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC

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

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

they are specified in GSM 03.87 [17]. If the VMSC does not support UUS, processing continues from the "Yes" exit of
the test "Result=Pass?".
If no useful information would be carried in the Progress message, it is not sent.
7.1.1.11 Procedure Set_COLP_Info_MSC

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

The test "Acknowledgement required" refers to the result returned by the procedure Handle_AoC_MSC. If the VMSC
does not support AoC, processing continues from the "No" exit of the test "Acknowledgement required".
The procedure UUS_OCH_Set_Alert_And_Connect_Param is specific to UUS, it is specified in GSM 03.87 [17]. If the

VMSC does not support UUS, processing continues from the "Yes" exit of the test "Result=Pass?".
If no useful information would be carried in the Facility message, it is not sent.
7.1.1.13 Procedure Handle_AoC_MO_MSC

The charging parameters and the Boolean variable Acknowledgement required are global data which can be read by the
parent process.
3GPP
Release 1998 24 3GPP TS 03.18 V7.5.0 (2003-12)
Process OCH_MSC OCH_MSC1(1)
Process in the MSC to

handle an outgoing call request
Idle
Signals from the left
are from the BSS
CM
service
request
Process_
Access_
Request_MSC
No
Result=
Pass?
Yes
Wait_For_
Setup
CM
Setup Service
Abort
CCBS_Report_
See GSM 03.93
Not_Idle
TCH allocated:=
False
OG_Call_
Setup_MSC
CCBS_Check_
See GSM 03.93
Last_Call
Release
call
resources
Idle
Figure 6: Process OCH_MSC
3GPP
Release 1998 25 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Process_Access_Request_MSC PAR_MSC1(3)

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

PAR_Result PAR_Result PAR_Result
Wait_For_
PAR_Result
CM Set
service Ciphering
abort Mode
Ciphering
Required:=
TRUE
Abort
Result:=
Fail
Wait_For_
PAR_Result
Figure 7a: Procedure Process_Access_Request_MSC (sheet 1)
3GPP
Release 1998 26 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in the MSC Signals to/from the left
Wait_For_ are to/from the BSS;
PAR_Result signals to/from the right
Process Access Process

Abort Request Access
negative Request ack
response
Yes No
CM Service type= Ciphering
Page Response? required?
No Yes
Yes
Map negative
CM Service type=
response to
Page Response?
reject cause
No
Release CM Service
transaction Reject
Result:= Start CM Service

Fail ciphering Accept
Wait_For_
TMSI_
Reallocation
CM Use
Provide Check Forward
service Setup Abort Existing
IMEI IMEI New TMSI
abort TMSI
Map negative
Obtain_IMEI_ Check_IMEI_
response to
MSC MSC
reject cause
No No
Result= Result= CM Service Reallocate
Abort
Pass? Pass? Reject TMSI
Yes Yes
Result:= Result:= Result:= Result:=

Fail Fail Fail Pass
Wait_For_ Wait_For_
Wait_For_
TMSI_ TMSI_
TMSI_Ack
Reallocation Reallocation
Figure 7b: Procedure Process_Access_Request_MSC (sheet 2)
3GPP
Release 1998 27 3GPP TS 03.18 V7.5.0 (2003-12)

TMSI_Ack signals to/from the right
CM TMSI TMSI
service Setup Abort Reallocation Reallocation
abort Failure Complete
Forward Forward
Abort New TMSI New TMSI
negative ack
response
Result:= Result:= Result:=

Fail Fail Pass
Figure 7c: Procedure Process_Access_Request_MSC (sheet 3)
3GPP
Release 1998 28 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure OG_Call_Setup_MSC OCS_MSC1(8)

Procedure in the originating VMSC
to set up an outgoing call after a Setup
message has been received from the MS
Alerting sent:=False
MS connected:=False
Reconnect:=False
UUS1 result sent:=False
UUS_OCH_
Check_ See GSM 03.87
Setup
Convert
GSM BC to
basic service
Send Info For

Outgoing Call
Wait_For_
MO_Call_
Result
Send Info For

Release Complete Outgoing Call
transaction Call negative
response
Convert GSM BC
to channel
requirement
Call Release
Abort
Proceeding transaction
Establish_
Originating_
TCH_If_
Required
No
Result=
Pass?
Yes
CCBS_OCH_ CCBS_OCH_
See GSM 03.93 See GSM 03.93
Report_Failure Report_Failure
Figure 8a: Procedure Outgoing_Call_Setup_MSC (sheet 1)
3GPP
Release 1998 29 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in the originating VMSC Signals to/from the left
to set up an outgoing call after a Setup 1 are to/from the BSS;
message has been received from the MS signals to/from the right
are to/from the destination exchange.
Set_CLI_
Presentation_
Indicator_
MSC
No
Result=
Call allowed?
Yes
Release CAMEL_OCH_
See GSM 03.78 3
transaction MSC_INIT
Result= Reconnect:=
Pass? True
No
Yes
CCBS_Check_
See GSM 03.93
OG_Call
No
Result=
Pass?
Yes
MOBILE_NUMBER_
Release
PORTABILITY_ See GSM 03.66
transaction
IN_OQoD
UUS_OCH_
Set_Info_ See GSM 03.87
In_IAM
CCBS_OCH_ Initial
See GSM 03.93
Report_Failure Address
Wait_For_
ACM
Figure 8b: Procedure Outgoing_Call_Setup _MSC (sheet 2)
3GPP
Release 1998 30 3GPP TS 03.18 V7.5.0 (2003-12)

to set up an outgoing call after a Setup are to/from the BSS;
message has been received from the MS signals to/from the right
Wait_For_ are to/from the destination exchange.
ACM
Address
Connect
Complete
CCBS_OCH_ CCBS_OCH_
Report_Success Report_Success
CAMEL_
See GSM 03.78
Start_TNRy
Send_
Alerting_If_
Required
No
Result=
Pass?
Yes
Release
UTU2Cnt:=0
transaction
Wait_For_
Release
Answer
Answer
Figure 8c: Procedure Outgoing_Call_Setup _MSC (sheet 3)
3GPP
Release 1998 31 3GPP TS 03.18 V7.5.0 (2003-12)

2
Signals from the left
are from the BSS
CAMEL_OCH_
See GSM 03.78
MSC_ANSWER
No
Result=
Pass?
Yes
Yes
Result= Set_COLP_
Reconnect? Info_MSC
No
Handle_AoC_
3
MO_MSC
Send_Access_
Connect_If_
Required
Yes
Result=
Fail?
No
No
Result=
Connect
sent?
Yes
Wait_For_
Connect_Ack
Connect
Ack
MS connected:=
True
Wait_For_
Clear
Figure 8d: Procedure Outgoing_Call_Setup _MSC (sheet 4)
3GPP
Release 1998 32 3GPP TS 03.18 V7.5.0 (2003-12)

ACM signals to/from the right
are to/from the destination exchange
unless otherwise marked.
From
Release Int_Release_
Release destination From gsmSSF
transaction Call
exchange
CCBS_Check_
CCBS_OCH_ CCBS_OCH_
See GSM 03.93 If_CCBS_ See GSM 03.93 See GSM 03.93
Possible
Store CCBS
Result
CAMEL CAMEL
Phase 2 Phase 2
Supported? Supported?
No Yes No Yes
Yes
Release cause=
No answer
from user?
No
CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_

4
MSC_DISC3 MSC_DISC4 MSC_DISC3 MSC1
No
Result= Release
See GSM 03.78
Reconnect? transaction
Yes
CCBS
CCBS Possible
Result
CCBS Not
Possible
CCBS_
Release
Release Activation_ See GSM 03.93 Release
transaction
MSC
Figure 8e: Procedure Outgoing_Call_Setup _MSC (sheet 5)
3GPP
Release 1998 33 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in the originating VMSC Signals to/from the left are to/from the BSS;
Wait_For_Connect_Ack signals to/from the right
Wait_For_Answer are to/from the destination exchange
Release From gsmSSF
transaction Call
CAMEL CAMEL
Phase 2 Phase 2
Supported? Supported?
No Yes No Yes
Yes
Release cause=
No answer from user?
No
CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ Release

See GSM 03.78
MSC_DISC3 MSC_DISC4 MSC_DISC3 MSC1 transaction
No
UUS_MSC_
Result=
Reconnect?
UUS1_UUI
Yes
UUS_MSC_
See GSM 03.87 Check_ 3
UUS1_UUI
Release
Release Release
transaction
Figure 8f: Procedure Outgoing_Call_Setup _MSC (sheet 6)
3GPP
Release 1998 34 3GPP TS 03.18 V7.5.0 (2003-12)

Answer signals to/from the right
User to
User to TNRy
User Internal
User expired
UUS_MSC_
Check_UUS2_ See GSM 03.87 4 Release
UUI_to_NW
UUS_MSC_
CAMEL_OCH_
See GSM 03.87 Check_UUS2_ See GSM 03.78
MSC2
UUI_to_MS
Release Reconnect
Result?
Continue,
Fail
Release
transaction
Wait_For_
3
Answer
Figure 8g: Procedure Outgoing_Call_Setup _MSC (sheet 7)
3GPP
Release 1998 35 3GPP TS 03.18 V7.5.0 (2003-12)

Clear signals to/from the right
Release from gsmSSF
transaction Call
UUS_MSC_ UUS_MSC_
Release
Check_ See GSM 03.87 Check_ See GSM 03.87
transaction
UUS1_UUI UUS1_UUI
CAMEL_OCH_ CAMEL_OCH_
MSC_DISC1 MSC_DISC2
Yes
Result=
Reconnect?
No
Yes Yes
Result= Result=
CAMEL CAMEL 3
handling? handling?
No No
Release
Release Release
transaction
Figure 8h: Procedure Outgoing_Call_Setup _MSC (sheet 8)
3GPP
Release 1998 36 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_IMSI_MSC OIMSI_M1(1)

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

Signals to/from the right
are to/from the VLR Send
IMSI
Wait_For_
IMSI
Send IMSI
Send IMSI Release
negative
ack transaction
response
Release
transaction
Provide
Abort
IMSI ack
Result:= Result:=
Pass Aborted
Figure 9: Procedure Obtain_IMSI_MSC
3GPP
Release 1998 37 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Authenticate_MSC AUT_MSC1(1)

to obtain an authentication
response from the MS

are to/from the VLR
Authenticate
Wait_For_
Auth_Response
Authenticate
Authenticate Release
negative
ack transaction
response
Release
transaction
Authenticate
Abort
ack
Wait_For_ Result:=
Auth_Result Aborted
Authentication Authentication
accepted rejected
Authentication
rejected
Result:=
Pass
Figure 10: Procedure Authenticate_MSC
3GPP
Release 1998 38 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_IMEI_MSC OIMEI_M1(1)

to obtain the IMEI from the MS

are to/from the VLR Send
IMEI
Wait_For_
IMEI
Send IMEI
Send IMEI Release
negative
ack transaction
response
Release
transaction
Provide
Abort
IMEI ack
Result:= Result:=
Pass Aborted
Figure 11: Procedure Obtain_IMEI_MSC
3GPP
Release 1998 39 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_IMEI_MSC CIMEI_M1(1)
Procedure in the MSC to check the

IMEI and relay the result to the VLR
Yes
IMEI
Signals to/from the left available?
signals to/from the right No
are to/from the VLR
unless marked otherwise.
Send IMEI
Wait_For_
IMEI
CM Send IMEI
Send IMEI
service negative
ack
abort response
Release
Check IMEI To EIR
transaction
Wait_for_
Abort Check_IMEI_
Result
Check IMEI
Result:= Release Check IMEI
negative From EIR From EIR
Aborted transaction ack
response
Check IMEI
Check IMEI
Abort negative
ack
response
Result:= Result:=
Aborted Pass
Figure 12: Procedure Check_IMEI_MSC
3GPP
Release 1998 40 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Establish_Originating_TCH_If_Required EOTCIR1(1)

to establish a Traffic Channel Signals to/from the left
if one has not been established are to/from the BSS
for this call
True
TCH
allocated
False
Allocate Result:=
channel Pass
Wait_For_
Allocation_
Complete
Release Allocation Allocation

transaction failure complete
Release TCH allocated:=

transaction True
Result:= Result:=
Fail Pass
Figure 13: Procedure Establish_Originating_TCH_If_Required
3GPP
Release 1998 41 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Set_CLI_Presentation_Indicator_MSC CAIND_M1(1)

to determine the CLI
presentation indicator value

are to/from the process
CLIR_MAF004 Initiate
handling
of CLIR
Wait_For_
CLIR_Info
Continue
Release Clear
From BSS call
transaction call
handling
Result:= Result:=
Call not Call
allowed allowed
Figure 14: Procedure Set_CLI_Presentation_Indicator_MSC
3GPP
Release 1998 42 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Send_Alerting_If_Required SALTIR1(1)

Procedure to send an
Signals to the left
Alerting message to the MS
are to the BSS
if one is required for this call
True
Alerting sent
False
True
Access
Connect
sent
No
Yes
Backward call indicator=
no indication?
No
UUS_MSC_ UUS_OCH_Set_
See GSM 03.87 Check_ Alert_And_ See GSM 03.87
UUS1_UUI Connect_Param
No
Result=
Pass?
Yes
Progress Alerting
Alerting sent:=
True
Result:= Result:=
Pass Fail
Figure 15: Procedure Send_Alerting_If_Required
3GPP
Release 1998 43 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Set_COLP_Info_MSC COINF_M1(1)

to determine the COLP
information to be sent to the MS

COLP_MAF006 Initiate
handling
of COLP
Wait_For_
COLP_Info
Continue From
Release
From BSS call Release destination
transaction
handling exchange
Figure 16: Procedure Set_COLP_Info_MSC
3GPP
Release 1998 44 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_AoC_MO_MSC AoCMO_M1(1)

to handle AoC signalling
towards the MS for an MO call
Yes
AoC(I)
provisioned?
No
Set
charging
parameters
No
AoC(C)
provisioned?
Yes
Set
charging
parameters
Acknowledgment Acknowledgment
required:= required:=
False True
Figure 17: Procedure Handle_AoC_MO_MSC
3GPP
Release 1998 45 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Send_Access_Connect_If_Required SACONIR1(1)

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

acknowledgment acknowledgment
timer timer
Wait_For_ Wait_For_
AoC_Ack_F AoC_Ack_C
Charging AoC Charging AoC

Release Release Connect
Parameters acknowledgment Parameters acknowledgment
transaction transaction Ack
ack timer expired ack timer expired
Release Release
transaction transaction
Release Release
Result:= Result:=
Result:= Result:=
Facility Connect
Fail Fail
sent sent
Figure 18: Procedure Send_Access_Connect_If_Required
3GPP
Release 1998 46 3GPP TS 03.18 V7.5.0 (2003-12)
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 processes Update_Location_VLR and Subscriber_Present_VLR are described in GSM 09.02 [23].
Sheet 2: it is a network operator decision (subject to MoU requirements) whether a connection should 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

GSM 03.93 [19].
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 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 GSM 03.87 [17]. 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 GSM 03.78 for

CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. 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 1998 47 3GPP TS 03.18 V7.5.0 (2003-12)
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.
3GPP
Release 1998 48 3GPP TS 03.18 V7.5.0 (2003-12)
Process OCH_VLR OCH_VLR1(1)

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

are to/from the MSC.
Idle
Process
Access
Request
Process_
Access_
Request_VLR
No
Result=
Pass
Yes
Wait_For_
Idle
SIFOC
Send Info
For Outgoing Abort
Call
Yes
Emergency
Idle
call?
No
OG_Call_
Complete
Subscription_
Call
Check_VLR
Idle Idle
Figure 19: Process OCH_VLR
3GPP
Release 1998 49 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Process_Access_Request_VLR PAR_VLR1(5)

Procedure in the VLR
No
Identity
known?
Yes
Obtain_
Identity_VLR
Yes
Result=
Pass?
No
Yes No
Identity= Result=
IMEI? Fail?
No
Yes
No
Authentication
required?
Yes
Authenticate_
VLR
No
Result=
Pass?
Yes
IMSI
detached:=
False
Confirmed by Set negative Set negative

response: response: Result:=
Radio Contact:=
System Unidentified Aborted
True
Failure Subscriber
2 1 3 3
Figure 20a: Procedure Process_Access_Request_VLR (sheet 1)
3GPP
Release 1998 50 3GPP TS 03.18 V7.5.0 (2003-12)

to handle a request from 1
True
Location info
confirmed
in HLR
False
Update_
See GSM 09.02
Location_VLR
No
Mobile Not
Reachable
Flag set?
Yes
Subscriber_
See GSM 09.02
Present_VLR
False
Data confirmed
by HLR
True Set negative

response:
Unidentified
Subscriber
No
Roaming allowed
in current LA?
Yes Set negative

response:
Roaming
Not Allowed
No
Tracing
required?
Yes
Start_
Tracing_VLR
No
Ciphering
required?
Yes
4 5 3
Figure 20b: Procedure Process_Access_Request_VLR (sheet 2)
3GPP
Release 1998 51 3GPP TS 03.18 V7.5.0 (2003-12)

to handle a request from 4 5
Signals to the left

are to the MSC.
Set
Ciphering
Mode
Identity:=
IMSI
Process
Access
Request ack
No
IMEI check
required?
Yes
Check_
IMEI_VLR
No
Result=
Pass?
Yes
No No
TMSI
Result=
reallocation
Fail?
required?
Yes Yes
CCBS_Report_
See GSM 03.93
MS_Activity
Use IMSI
Forward
Existing detached:=
New TMSI
TMSI True
Freeze Set negative

Result:= response: Result:=
existing
Pass Illegal Aborted
TMSI
Equipment
Wait_For_
3
TMSI_Ack
Figure 20c: Procedure Process_Access_Request_VLR (sheet 3)
3GPP
Release 1998 52 3GPP TS 03.18 V7.5.0 (2003-12)

Signals from the left Wait_For_

2
are from the MSC. TMSI_Ack
Yes
Result=
Aborted? Forward
Forward
New TMSI New TMSI
No negative
ack
Result:= response
Aborted
Yes
Result=
Procedure
Error? Unfreeze
existing
No Set negative TMSI
response:
System
Failure
Yes
Result=
Unknown
Subscriber?
CCBS_Report_
See GSM 03.93
No MS_Activity
Yes
Result=
Unidentified
Subscriber?
Result:=
No Set negative Pass
response:
Unidentified
Subscriber
Set negative
response:
Illegal
Subscriber
Figure 20d: Procedure Process_Access_Request_VLR (sheet 4)
3GPP
Release 1998 53 3GPP TS 03.18 V7.5.0 (2003-12)

to handle a request from 3
Signals to the left

are to the MSC. No
CM service type
=Emergency call?
Yes
Emergency call
setup allowed
without SIM?
No
Yes
No
IMEI
required?
Yes
Obtain_
IMEI_VLR
No
Result=
Pass?
Yes
Yes
Identity:= Result=
IMEI Fail?
No
Process Process Access

Access Request
Request ack negative
response
CCBS_Report_
See GSM 03.93
MS_Activity

Pass Aborted Fail
Figure 20e: Procedure Process_Access_Request_VLR (sheet 5)
3GPP
Release 1998 54 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure OG_Call_Subscription_Check_VLR OCSCVLR1(2)

to perform subscription
checks for an outgoing call
No
Basic
Signals to the left
service
are to the MSC
provisioned?
Yes
Set negative
Check_ response: Bearer service
BAOC Basic service or teleservice
not provisioned
Yes
Result=
Call
barred?
No
Set negative
OG_CUG_
response:
Check
Call barred
No
Result=
Call
allowed?
Yes
Get_LI_ Set negative

Subscription_ response:
Info_MO_VLR CUG reject
Get_AoC_
Subscription_
Info_VLR
UUS_OCH_
Check_
Provision
No
Result=
Pass?
Yes
Send Info
For Outgoing
Call negative
response
Figure 21a: Procedure OG_Call_Subscription_Check_VLR (sheet 1)
3GPP
Release 1998 55 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure OG_Call_Subscription_Check_VLR OCSCVLR2(2)

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

are to the MSC
No
O-CSI
present?
Yes
CAMEL_
See GSM 03.78
OCH_VLR
Yes
Result=
Fail?
No
Check_OG_
Barring
Yes
Call
barred?
No
Set negative
response:
Call barred
Send Info
Complete For Outgoing
Call Call negative
response
Figure 21b: Procedure OG_Call_Subscription_Check _VLR (sheet 2)
3GPP
Release 1998 56 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_Identity_VLR OID_VLR1(1)

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

Fail Pass Aborted
Figure 22: Procedure Obtain_Identity_VLR
3GPP
Release 1998 57 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_IMSI_VLR OIMSI_V1(1)

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

Provide
IMSI
Wait_For_
IMSI
Provide
Abort
IMSI ack
Result:= Result:=
Pass Aborted
Figure 23: Procedure Obtain_IMSI_VLR
3GPP
Release 1998 58 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Authenticate_VLR AUT_VLR1(2)

to authenticate an MS
via the MSC

are to/from the MSC. Yes
Authentication
sets available?
No
Obtain_
Authentication_
Sets_VLR
No
Result=
2
Pass?
Yes Yes
Result=
Aborted?
No
Authenticate
Yes
Result=
Result:=
Procedure
Aborted
Error?
No
Wait_For_
Authenticate_
Result
Result:= Result:=
Procedure Unknown
Error Subscriber
Authenticate
Abort
ack
No
Received SRES=
expected SRES? No
More
authentication
Yes
sets needed?
No Yes
More
authentication
sets needed?
Yes
Fetch_
Authentication_
Fetch_ Sets_VLR
Authentication_
Sets_VLR
Authentication
accepted
Result:= Result:=
Pass Aborted
Figure 24a: Procedure Authenticate_VLR (sheet 1)
3GPP
Release 1998 59 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Authenticate_VLR AUT_VLR2(2)

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

are to the MSC. Yes
Identity=IMSI?
No
No
Retry
with
IMSI?
Yes
Obtain_
IMSI_VLR
No
Result=
Pass?
Yes
No
IMSI
known?
Yes
Yes
IMSI
matches
TMSI?
No
accepted rejected
Result:= Result:=
Result:= Identity:=
Unidentified Illegal
Aborted IMSI
Subscriber Subscriber
Figure 24b: Procedure Authenticate_VLR (sheet 2)
3GPP
Release 1998 60 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_Authentication_Sets_VLR OAS_VLR1(2)

to obtain authentication
sets from the HLR

are to/from the HLR
Send
Authentication
Info
Wait_For_
Authentication_
Sets
Send Send
Info ack Info negative
response
Yes No
Empty Unknown
result? Subscriber?
No Yes
No
Authentication
sets available
in VLR?
Yes
Yes No
Re-use
old
sets?
Result:= Result:=
Result:=
Procedure Unknown
Pass
Error Subscriber
Figure 25a: Procedure Obtain_Authentication_Sets_VLR (sheet 1)
3GPP
Release 1998 61 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_Authentication_Sets_VLR OAS_VLR2(2)

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

are to/from the MSC; Authentication_
Signals to/from the right Sets
are to/from the HLR
Abort Abort
No
Authentication
Abort
sets available?
Yes
Yes No
Re-use
old
sets?
Result:=
Result:= Result:=
Procedure
Aborted Pass
Error
Figure 25b: Procedure Obtain_Authentication_Sets_VLR (sheet 2)
3GPP
Release 1998 62 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Start_Tracing_VLR ST_TR_V1(1)

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

are to the MSC. No
Tracing
active?
Yes
Trace
Subscriber
Activity
Figure 26: Procedure Start_Tracing_VLR
3GPP
Release 1998 63 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_IMEI_VLR CIMEI_V1(1)

to request the MSC to
check an IMEI

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

Aborted Fail Pass
Figure 27: Procedure Check_IMEI_VLR
3GPP
Release 1998 64 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_IMEI_VLR OIMEI_V1(1)

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

are to/from the MSC
Provide
IMEI
Wait_For_
IMEI
Provide
Abort
IMEI ack
Result:= Result:=
Pass Aborted
Figure 28: Procedure Obtain_IMEI _VLR
3GPP
Release 1998 65 3GPP TS 03.18 V7.5.0 (2003-12)
Process Fetch_Authentication_Sets_VLR FAS_VLR1(1)

Process in the VLR
to retrieve authentication
sets from the HLR
Obiain_
Authentication_
Sets_VLR
Figure 29: Process Fetch_Authentication_Sets_VLR
3GPP
Release 1998 66 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_BAOC CBAOC1(1)

Procedure to check call
request against ODBAOC
and SS BAOC

Yes
MAF017
Operator determined BAOC
imposed?
No
Result:= Initiate
Call barred handling
(ODB) of BAOC
Wait_For_
BAOC_
Response
Continue
From MSC Abort call
handling
Yes
Call
barred?
No
Result:=
Result:=
Call barred
Call allowed
(SS barring)
Figure 30: Procedure Check_BAOC
3GPP
Release 1998 67 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure OG_CUG_Check OG_CUG1(1)

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

CUG_MAF014 outgoing
call
request
Wait_For_
CUG_Response
response complete call reject

From MSC Abort to call (conditional call
request CUG info) (cause)
Result:= Result:=
Call allowed Call barred
Figure 31: Procedure OG_CUG_Check
3GPP
Release 1998 68 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Get_LI_Subscription_Info_MO_VLR GLI_MOV1(1)

to retrieve subscription
information for the CLIR
& COLP line identification
services for an MO call
Initiate
handling To process CLIR_MAF003
of CLIR
Wait_For_
CLIR_Info
Continue
From MSC Abort call From process CLIR_MAF003
handling
Initiate
handling To process COLP_MAF005
of COLP
Wait_For_
COLP_Info
Continue
From MSC Abort call From process COLP_MAF005
handling
Figure 32: Procedure Get_LI_Subscription_Info_MO_VLR
3GPP
Release 1998 69 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Get_AoC_Subscription_Info_VLR GAOCI_V1(1)

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

AoC not AoC(C) AoC(I)
provisioned provisioned provisioned
Figure 33: Procedure Get_AoC_Subscription_Info_VLR
3GPP
Release 1998 70 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_OG_Barring COB1(3)

request against SS barring
and ODB categories
Yes
Operator determined
BOIC imposed?
No No
Destination address CC=
Local CC?
Yes
Yes
Operator determined
BOIC-exHC imposed?
Yes No
Local CC?
No
1
No
HPLMN CC?
Yes
Yes
Operator determined
BOIZC imposed?
No No
Destination address ZC=
Local ZC?
Yes
Yes
Operator determined
BOIZC-exHC imposed?
Yes No
Local ZC?
No
1
No
HPLMN CC?
Yes
Result:=
Call barred
(ODB)
Figure 34a: Procedure Check_OG_Barring (sheet 1)
3GPP
Release 1998 71 3GPP TS 03.18 V7.5.0 (2003-12)

request against SS barring 1
and ODB categories
No
Operator determined
BOIC-exHC&BOIZC
imposed?
Yes
2
Yes
Local ZC?
No
Yes
Local CC?
No
2
No
HPLMN CC?
Yes
Result:=
Call barred
(ODB)
Figure 34b: Procedure Check_OG_Barring (sheet 2)
3GPP
Release 1998 72 3GPP TS 03.18 V7.5.0 (2003-12)

2
and ODB categories
Yes
Call
barred?
No
Initiate
handling To process MAF018
of BOIC
Wait_For_
BOIC_
Response
Continue
From MSC Abort call From process MAF018
handling
Yes
Call
barred?
No
Initiate
of BOIC-exHC
Wait_For_
BOIC-exHC_
Response
Continue
From MSC Abort call From process MAF020
handling
Yes
Call
barred?
No
Result:=
Result:=
Call barred
Call allowed
(SS barring)
Figure 34c: Procedure Check_OG_Barring (sheet 3)
3GPP
Release 1998 73 3GPP TS 03.18 V7.5.0 (2003-12)
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 OR_Set_ORA_Parameters is specific to Support of Optimal Routeing; it is specified in

GSM 03.79 [10].
Sheet 1: the procedure CAMEL_Set_ORA_Parameters is specific to CAMEL; it is specified in GSM 03.78 for

CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9].
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 [28]) 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
Sheet 1: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in
the Perform Call Forwarding ack.
Sheet 1: it is an operator option whether to send an Address Complete message if the HLR returns forwarding
information. If the GMSC sends an Address Complete message, it shall include the called party’s status field of the
Backward call indicator set to "no indication".
3GPP
Release 1998 74 3GPP TS 03.18 V7.5.0 (2003-12)
Sheet 1: it is an operator option whether to send an Address Complete message if the Number Portability Database
returns a routeing number. If the GMSC sends an Address Complete message, it shall include the called party’s status
field of the Backward call indicator set to "no indication".
Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2; they are
specified in GSM 03.78 for CAMEL Phase 2 [9].
Sheet 2, sheet 3: the procedure CAMEL_MT_GMSC_ANSWER is specific to CAMEL; it is specified in GSM 03.78

for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the 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

GSM 03.93 [19].
Sheet 5: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2, and will
occur only if the GMSC supports CAMEL phase 2. The procedure CAMEL_MT_GMSC_DISC5 is specified in
GSM 03.78 for CAMEL phase 2 [9].
Sheet 6: the procedures CAMEL_MT_GMSC_DISC3, CAMEL_MT_GMSC_DISC4 and

CAMEL_MT_GMSC_DISC6 are specific to CAMEL; they are specified in GSM 03.78 for CAMEL Phase 1 [8]
(CAMEL_MT_GMSC_DISC3) and GSM 03.78 for CAMEL Phase 2 [9] (CAMEL_MT_GMSC_DISC4 and
CAMEL_MT_GMSC_DISC6).
Sheet 6: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 5: the procedures CAMEL_MT_GMSC_DISC1 and CAMEL_MT_GMSC_DISC2 are specific to CAMEL; they
are specified in GSM 03.78 [8]. If the GMSC does not support CAMEL, processing continues from the "No" exit of the
test "Result=CAMEL handling?".
Sheet 6: 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 GSM 03.78 for

CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the GMSC does not support CAMEL, processing
Sheet 7: the procedure CAMEL_MT_GMSC_DISC2 is specific to CAMEL; it is specified in GSM 03.78 for

CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the GMSC does not support CAMEL, processing
continues from the "Normal handling" exit of the test "Result?".
Sheet 7: in the upper subtree, the processing in the branch beginning with the Int_Release_Call input will occur only if
the GMSC supports CAMEL.
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.
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 GSM 03.93 [19].
Sheet 1: the procedure CLI_MT_GMSC is specific to Enhanced CLI Handling. It is specified in GSM 03.81 [11].
3GPP
Release 1998 75 3GPP TS 03.18 V7.5.0 (2003-12)
Sheet 2: the procedure OR_Handle_SRI_Negative_Response is specific to Support of Optimal Routeing. It is specified

in GSM 03.79 [10]. 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 2: the procedure CAMEL_MT_GMSC_INIT is specific to CAMEL; it is specified in GSM 03.78 for

Sheet 2: the procedure CCBS_MT_GMSC_Check_CCBS_Indicators is specific to CCBS; it is specified in

GSM 03.93 [19].
Sheet 2: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal
Routeing.
Sheet 2: the task "Destination address:=VMSC address" is executed only if the GMSC supports Optimal Routeing of
mobile-to-mobile calls.
Sheet 2: The decision "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: if the GMSC does not support CAMEL and the Send Routeing Info ack contains neither an MSRN nor an
FTN, processing continues from the "No" exit of the test "CMN?".
Sheet 3: the procedure CCBS_MT_GMSC_Remove_Indicators is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 3, sheet 4: the procedure Route_Permitted is specific to Support of Optimal Routeing. It is specified in
GSM 03.79 [10]. If the GMSC does not support Optimal Routeing, processing continues from the "True" exit of the test
"Route permitted".
Sheet 3: the tasks "Destination address:=CMN" and "OR:= True" are executed only if the GMSC supports Optimal
Routeing of mobile-to-mobile calls.
Sheet 3, sheet 4: the procedures CAMEL_MT_MSC_DISC3 and CAMEL_MT_MSC_DISC4 are specific to CAMEL;
they are specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9] respectively.
Sheet 4: the procedure CAMEL_MT_GMSC_Notify_CF is specific to CAMEL phase 2; it is specified in GSM 03.78

for CAMEL Phase 2 [9]. If the GMSC does not support CAMEL, processing continues from the "Continue" exit of the
test "Result?".
Sheet 4: the procedure CCBS_MT_GMSC_Remove_Indicators_Store_FWT is specific to CCBS; it is specified in

GSM 03.93 [19].
Sheet 4: the tasks "Destination address:=FTN" and "OR:=True" are 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

7.2.1.5 Procedure Send_Network_Connect_If_Required

3GPP
Release 1998 76 3GPP TS 03.18 V7.5.0 (2003-12)
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 GSM 03.78 for
CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. If the MSC does not support CAMEL, processing
Sheet 1: the procedures CAMEL_OCH_MSC_DISC3 and CAMEL_OCH_MSC_DISC4 are specific to CAMEL; they
are specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9] respectively.
Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is

Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2; they are
specified in GSM 03.78 for CAMEL Phase 2 [9].
Sheet 2: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL; it is specified in GSM 03.78 for

Sheet 2: the procedure UUS_MSC_Clear_UUS is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 3: the procedures CAMEL_OCH_MSC_DISC3 and CAMEL_OCH_MSC_DISC4 are specific to CAMEL; they
are specified in GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9] respectively.
Sheet 3: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2; it is specified in GSM 03.78 for
CAMEL Phase 2 [9].
Sheet 3: the procedure CAMEL_Stop TNRy is specific to CAMEL phase 2; it is specified in GSM 03.78 for
CAMEL Phase 2 [9].
Sheet 3: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports
CAMEL.
Sheet 4: the input signal TNRy expired and all the subsequent processing are specific to Support of CAMEL phase 2,
and will occur only if the GMSC supports CAMEL phase 2. The procedure CAMEL_OCH_MSC2 is specified in
GSM 03.78 for CAMEL Phase 2 [9].


continues from the "No" exit of the test "Result=Reconnect?" .
Sheet 5: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports
CAMEL.
Sheet 5: after the process MT_CF_MSC has sent an IAM to the forwarded-to exchange, it acts as a relay for messages
received from the parent process and the forwarded-to exchange. Any message other than Address Complete, Connect,
Answer or Release causes no change of state in the process MT_GMSC
3GPP
Release 1998 77 3GPP TS 03.18 V7.5.0 (2003-12)
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
unless marked otherwise
Idle
Initial
1
Address
ACM sent:=False
Reconnect:= Answer sent:=False
True Network connect sent:=False
Reconnect:=False
Resume call:=False
UUS CF Interaction:=False
OR_Set_ORA_
See GSM 03.79
Parameters
CAMEL_Set_
See GSM 03.78
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
Yes
Result=
Set
Number
cause
ported?
No
Yes
Initial Address Initial Address
Result=
Release (Routeing (Routeing To process MT_CF_MSC
Aborted?
Address) Address)
No
Release Initial Address

Send_ACM_ Send_ACM_ To originating
call (Routeing
If_Required If_Required exchange
resources Address)
Wait_For_ Wait_For_ Wait_For_

Idle
ACM ACM Forward_ACM
Figure 35a: Process MT_GMSC (sheet 1)
3GPP
Release 1998 78 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the GMSC to
Wait_For_ Signals from the right are
handle a mobile-terminated
ACM from the destination exchange
call request
Address
Connect
Complete
Send_ACM_
If_Required
CAMEL_
See GSM 03.78
Start_TNRy
Wait_For_
Answer
Answer
CAMEL_
See GSM 03.78
Stop_TNRy
CAMEL_MT_ CAMEL_MT_
GMSC_ANSWER GMSC_ANSWER
Fail Reconnect Reconnect Fail

Result? Result?
Pass Pass
Idle 1 Idle
Set destination Set destination

address address
parameter parameter
Send_Network_
Send_Answer_
Connect_If_
If_Required
Required
Wait_For_
Clear
Figure 35b: Process MT_GMSC (sheet 2)
3GPP
Release 1998 79 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the GMSC to
call request
Wait_For_ Signals from the right are
Forward_ACM from the process MT_CF_MSC
Address
Connect
Complete
Send_ACM_
If_Required
Wait_For_
Forward_
Answer
Answer
CAMEL_MT_ CAMEL_MT_
GMSC_ANSWER GMSC_ANSWER
Fail Reconnect Reconnect Fail

Result? Result?
Pass Pass
Handle_COLP_ Handle_COLP_
Idle Forwarding_ 1 Forwarding_ Idle
Interaction_MSC Interaction_MSC
Set COLP Set COLP

presentation presentation
indicator indicator
Set destination Set destination

address address
parameter parameter
Send_Network_
Send_Answer_
Connect_If_
If_Required
Required
Wait_For_
Clear
Figure 35c: Process MT_GMSC (sheet 3)
3GPP
Release 1998 80 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the GMSC to Signals to/from the right
Wait_For_ACM,
handle a mobile-terminated are to/from the destination MSC
Wait_For_Answer
call request unless marked otherwise
Resume
Refer to GSM 03.79 for
Call
message contents
Handling
CCBS_MT_GMSC_
Check_CCBS_ See GSM 03.93
Possible
Resume call:-
True
OR_Handle_
See GSM 03.79
RCH
Yes
Result=
Fail?
No
Yes
Result=
Refuse?
No
Yes
Result=
Reconnect?
No
Wait_For_
- 1 Idle
Forward_ACM
Figure 35d: Process MT_GMSC (sheet 4)
3GPP
Release 1998 81 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_For_ are to/from the originating MSC;
Answer signals to/from the right
call request
are to/from the destination MSC
TNRy
Internal
expired
2 Release
CAMEL_MT_
See GSM 03.78
GMSC_DISC5
Release Reconnect
Result?
Continue,
Fail
Release
Release call
resources
Idle 1
Figure 35e: Process MT_GMSC (sheet 5)
3GPP
Release 1998 82 3GPP TS 03.18 V7.5.0 (2003-12)

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

See GSM 03.78
GMSC_DISC3 GMSC_DISC6 GMSC_DISC3 GMSC_DISC4
No
Result=
Release
Reconnect?
Yes
CCBS_Set_
Diagnostic_
For_Release
Release Release 1 Release
Release call
resources
Idle
Figure 35f: Process MT_GMSC (sheet 6)
3GPP
Release 1998 83 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_For_ are to/from the originating exchange;
Clear signals to/from the right
call request
or the process MT_CF_MSC
Int_Release_
Call
CAMEL_MT_ CAMEL_MT_
GMSC_DISC1 GMSC_DISC2
Yes Reconnect CAMEL handling

Result=
CAMEL Result? Release
handling?
No Normal handling
Release 1 Release Release
Release call
resources
Idle
Wait_For_ACM,
Wait_For_Forward_ACM,
Wait_For_Answer,
Wait_For_Forward_Answer,
Wait_For_Clear
* *
- -
Figure 35g: Process MT_GMSC (sheet 7)
3GPP
Release 1998 84 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Obtain_Routeing_Address ORA1(4)

Procedure in a GMSC Procedure Obtain_Routeing_Address
to determine the address FPAR IN Input address, Reference address,
to which a call should be routed Own PLMN
IN/OUT Routeing address,
Destination address, OR, Result
MOBILE_NUMBER_
PORTABILITY_
IN_TQoD
Yes
Result=
Number
ported?
No
CCBS_MT_ Routeing
See GSM 03.93 GMSC_Check_ address:=
CCBS_Call routeing number
True
Result:=
Reconnect Number
ported
False
CLI_MT_
See GMSC 03.81
GMSC
Send
Routeing
Info
Wait_for_
Routeing_ 1
Info
Figure 36a: Procedure Obtain_Routeing_Address (sheet 1)
3GPP
Release 1998 85 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in a GMSC
to determine the address
to which a call should be routed

Wait_for_
are to/from the originating exchange;
Routeing_
Info
are to/from the HLR
Send
Routeing
Release
Info negative
response
OR_Handle_SRI_
Negative_Response See GSM 03.79
(Own PLMN)
Yes
Result=
Pass?
No
No
Error=
Unknown
subscriber?
Yes
MOBILE_NUMBER_
PORTABILITY_
IN_QoHR
No
Result=
Number
ported?
Yes
Routeing
address:=
routeing number
Result:=
Result:=
Result:=Fail Number Result:=Pass
Aborted
ported
Figure 36b: Procedure Obtain_Routeing_Address (sheet 2)
3GPP
Release 1998 86 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in a GMSC Wait_for_
to determine the address Routeing_
to which a call should be routed Info
Send
Routeing 1
Info ack
CAMEL_MT_
See GSM 03.78
GMSC_INIT
Result?
Fail Aborted MSRN GSM_FTN CMN CAMEL_FTN
CCBS_MT_
Result:= Result:=
2 GMSC_Remove_ See GSM 03.93 3
Fail Aborted
Indicators
CCBS_MT_ Route_Permitted
GMSC_Check_ See GSM 03.93 (OR,FTN, See GSM 03.79
CCBS_ Reference
Indicators Address)
Store Forwarding False

Interrogation Route
Required permitted
indicator
True
No
CAMEL
MSRN contains
phase 2
a Routeing number?
supported?
Yes
No Yes
CAMEL_MT_ CAMEL_MT_
Routeing Routeing Routeing Routeing

address:= address:= address:= address:=
MSRN MSRN CMN Reference
address
Destination Destination Destination

address:= address:= address:=
VMSC address CMN Reference
address
OR:=True OR:=False
Result:=
Number
Pass Pass Pass
ported
Figure 36c: Procedure Obtain_Routeing_Address (sheet 3)
3GPP
Release 1998 87 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in a GMSC
to determine the address
2
to which a call should be routed
CAMEL_
3 MT_GMSC_
Notify_CF
Continue Fail
Result
Reconnect
Activate_ Reconnect:= Result:=

CF_Process True Fail
Yes
Result=
1
Fail?
No
CCBS_MT_
GMSC_Remove_ Result:=
See GSM 03.93
Indicators_ Aborted
Store_FWT
Route_Permitted
(OR,FTN,
See GSM 03.79
Reference
Address)
False
Route
permitted
True CAMEL
phase 2
supported?
No Yes
CAMEL_MT_ CAMEL_MT_
To process CF
MT_CF_MSC cancelled
Routeing
Routeing
address:=
address:=
Reference
FTN
address
Destination
Destination
address:=
address:=
Reference
FTN
address
OR:=True OR:=False
Result:= Result:=
Forward Pass
Figure 36d: Procedure Obtain_Routeing_Address (sheet 4)
3GPP
Release 1998 88 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Send_ACM_If_Required SACMIR1(1)

Address Complete Message Signals to the left
to the preceding exchange if are to the originating exchange
one is required for this call
True
ACM
sent
False
True
Network
connect
sent
False
Call Address
Progress Complete
ACM sent:=
True
Figure 37: Procedure Send_ACM_If_Required
3GPP
Release 1998 89 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Send_Answer_If_Required SANMIR1(1)

Answer Message Signals to the left
True
Answer
sent
False
True
Network
connect
sent
False
Call
Answer
Progress
Answer sent:=
True
Figure 38: Procedure Send_Answer_If_Required
3GPP
Release 1998 90 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Send_Network_Connect_If_Required SNCONIR1(1)

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

True True
Figure 39: Procedure Send_Network_Connect_If_Required
3GPP
Release 1998 91 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_COLP_Forwarding_Interaction_MSC COINT_M1(1)

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

are to/from the process handling
COLP_MAF039 of COLP
Wait_For_
COLP_Info
continue
From originating exchange
Release call
or destination exchange
handling
Figure 40: Procedure Handle_COLP_Forwarding_Interaction_MSC
3GPP
Release 1998 92 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Activate_CF_Process ACFP1(1)

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

Fail Pass Fail Fail
Figure 41: Procedure Activate_Call_Forwarding_Process
3GPP
Release 1998 93 3GPP TS 03.18 V7.5.0 (2003-12)
Process MT_CF_MSC MTCFMSC1(5)

Process in the MSC are to/from the parent process;
to handle call forwarding signals to/from the right
Idle
Perform call
forwarding
CAMEL_CF_
See GSM 03.78
MSC_INIT
No
Result=
Pass?
Yes
No
Perform call
Result=
forwarding
Fail?
ack(FTN)
Yes
Perform Call
Wait_For_ Forwarding
IAM negative
response
Initial CF
1
Address cancelled
MOBILE_NUMBER_ CAMEL
See GSM 03.66 PORTABILITY_ phase 2
IN_OQoD supported?
No Yes
Initial CAMEL_OCH_ CAMEL_OCH_

Address MSC_DISC3 MSC_DISC4
Wait_For_
Idle Idle
ACM
Figure 42a: Process MT_CF_MSC (sheet 1)
3GPP
Release 1998 94 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the MSC Wait_For_ are to/from the parent process;
to handle call forwarding ACM signals to/from the right
Address
Connect
Complete
CAMEL_
See GSM 03.78
Start_TNRy
UUS_MSC_ UUS_MSC_
Clear_UUS Clear_UUS
Address
Complete
Wait_For_
Answer
Answer
CAMEL_
See GSM 03.78
Stop_TNRy
CAMEL_CF_ CAMEL_CF_
MSC_ANSWER MSC_ANSWER
No No
Result= Result=
Pass? Pass?
Yes Yes
Yes
UUS_MSC_ Result=
See GSM 03.87
Clear_UUS Reconnect?
No
Answer Connect
Wait_For_ Wait_For_
Idle 1
Clear Clear
Figure 42b: Process MT_CF_MSC (sheet 2)
3GPP
Release 1998 95 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the MSC are to/from the parent process;
to handle call forwarding signals to/from the right
Wait_For_ACM, are to/from the destination exchange
Wait_For_Answer unless marked otherwise
Int_O_
Release
CAMEL CAMEL
phase 2 phase 2
supported? supported?
No Yes No Yes
Yes
Release cause=
No
CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_ CAMEL_OCH_

See GSM 03.78
MSC_DISC3 MSC_DISC4 MSC_DISC3 MSC1
No
Result=
Reconnect?
Yes
CAMEL_
See GSM 03.78 Release
Stop_TNRy
Release
call
resources
Idle
Figure 42c: Process MT_CF_MSC (sheet 3)
3GPP
Release 1998 96 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the MSC Wait_For _ are to/from the parent process;
to handle call forwarding Answer signals to/from the right
TNRy
Internal
expired
2 Release
CAMEL_OCH_
See GSM 03.78
MSC2
Release Reconnect
Result?
Fail
Release
Release
call
resources
Idle 1
Figure 42d: Process MT_CF_MSC (sheet 4)
3GPP
Release 1998 97 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the MSC Wait_For_ are to/from the parent process;
to handle call forwarding Clear signals to/from the right
Int_O_
Release
CAMEL_OCH_ CAMEL_OCH_
See GSM 03.78 See GSM 03.78 Release
MSC_DISC1 MSC_DISC2
Yes Yes
Result= Result=
CAMEL CAMEL
Handling? Handling?
No No
Yes
Result=
Reconnect?
No
Release
call
resources
Idle
* *
- -
Figure 42e: Process MT_CF_MSC (sheet 5)
3GPP
Release 1998 98 3GPP TS 03.18 V7.5.0 (2003-12)
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

GSM 03.79 [10]. 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 GSM 03.78 for

CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9]. 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 GSM 03.78 for

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 GSM 03.93 [19]. 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 GSM 03.79 [10]. 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 GSM 03.81 [11].
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 GSM 03.78 for

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 GSM 03.78 for CAMEL Phase 1 [8] and GSM 03.78 for CAMEL Phase 2 [9].
7.2.2.2 Procedure Check_Parameters

If any parameters required by the rules in clause 8 are missing from the message, the procedure sets the negative
response to "Data missing". If any parameter has a value which is not in the set of values expected for the parameter, the
procedure sets the negative response to "Unexpected data value".
7.2.2.3 Procedure Subscription_Check_HLR

It is an implementation option to carry out the check for operator determined barring of incoming calls before the check
on provisioning of the requested basic service.
3GPP
Release 1998 99 3GPP TS 03.18 V7.5.0 (2003-12)
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 procedure IC_CUG_Check is specific to CUG. If the HLR does not support GUG, processing continues from the
"Yes" exit of the test "Result=Call allowed?".
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 GSM 03.93 [19]. The procedure does
not return a value; the following tests are on the value of the Provide Roaming Number negative response.
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 GSM bearer capability from ISDN compatibility information or the MSISDN of the B
subscriber are specified in GSM 09.07 [24]. 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.
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 1998 100 3GPP TS 03.18 V7.5.0 (2003-12)
Process SRI_HLR SRI_HLR1(4)

Process in the HLR to handle are to/from the GMSC;
a request for routeing information signals to/from the right
are to/from the VLR
Idle
Send
Routeing
Info
Check_
Parameters
No
Result=
Pass?
Yes
Subscription_
Check_HLR
Yes
Result=
Fail?
No
See GSM 03.79 OR_HLR_CF
Yes
Result=
Fail?
No
Yes
Result=
Forward?
No
CAMEL_
See GSM 03.78
HLR_INIT
Yes
Result=
Fail?
No
3 1 2 1
Figure 43a: Process SRI_HLR (sheet 1)
3GPP
Release 1998 101 3GPP TS 03.18 V7.5.0 (2003-12)

3
are to/from the VLR
First_
Forwarding_
HLR
Yes
Result=
Fail?
No
Yes
CAMEL_
Result=
See GSM 03.78 CSI_Check_
Forward?
HLR
No
Yes
CAMEL_ Result=
See GSM 03.78 CSI_Check_ 2 CSI
HLR active?
No
Result=
CSI 4
active?
Yes
No
CCBS_Handling_
4 See GSM 03.93
HLR
Yes
Result =
Forward
No
No
Result =
OK
Yes
1 5 2 1
Figure 43b: Process SRI_HLR (sheet 2)
3GPP
Release 1998 102 3GPP TS 03.18 V7.5.0 (2003-12)

5
are to/from the VLR
OR_HLR_
See GSM 03.79
Interrogate_VLR
Yes
Result=
Fail?
No
Yes
Result=
Forward?
No
Yes
GSM BC=
NULL?
No
Set
GSM BC
parameter
No
Alerting
Pattern
required?
Yes
Set
Alerting
Pattern
CLI_HLR_
See GSM 03.81
Set_CLI
Provide
Roaming 2 1
Number
Wait_For_
MSRN
Figure 43c: Process SRI_HLR (sheet 3)
3GPP
Release 1998 103 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the HLR to handle Wait_For_ are to/from the GMSC;
a request for routeing information MSRN signals to/from the right
are to/from the VLR
Provide Provide
Roaming Roaming
Number ack Number negative
response
PRN_Error_
1
HLR
Yes
Result=
2
Fail?
No
Forward_
CUG_Check
No
Result=
Call
allowed?
Yes
Yes
Routeing
Forwarding
address:=
enquiry?
FTN
No
Yes
CAMEL_
Forwarding
CSI_Check_ See GSM 03.78
enquiry?
HLR
No
No
CAMEL_T_ Result=
See GSM 03.78 CSI_CHECK_ CSI
HLR active?
Yes
CAMEL_O_
See GSM 03.78 CSI_CHECK_
HLR
Routeing Called party SS Set negative

address:= 4 interaction response:
MSRN violation CUG reject
Send Send Send Send

Routeing Routeing Routeing Routeing
Info ack Info ack Info ack Info negative
response
Idle Idle Idle Idle
Figure 43d: Process SRI_HLR (sheet 4)
3GPP
Release 1998 104 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_Parameters Chk_Par1(1)

Procedure to check
the parameters of a
received message
No
All required
parameters present?
Yes
No
Set negative
All parameter values
response:
acceptable?
Data missing
Yes
Set negative
response:
Unexpected
data value
Result:= Result:=
Pass Fail
Figure 44: Procedure Check_Parameters
3GPP
Release 1998 105 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Subscription_Check_HLR SC_HLR1(1)

Procedure in the HLR
to make subscription
checks for a mobile-
terminated call
No
MS
known?
Yes Set negative

response:
Unknown
subscriber
Yes
Number
changed?
No Set negative
response:
Number
changed
Derive_Requested_
Basic_Service_HLR
No
Requested
service
provisioned?
Yes Set negative Bearer service
response: or
service not Teleservice
provisioned
Check_IC_
Barring
Yes
Result=
Call
barred?
No
Set negative
response:
Call barred
IC_CUG_
Check
No
Result=
Call
allowed?
Set negative
Yes
response:
CUG reject
Result:= Result:=
Pass Fail
Figure 45: Procedure Subscription_Check_HLR
3GPP
Release 1998 106 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure First_Forwarding_HLR FF_HLR1(1)

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

response:
Absent
subscriber

Forward Continue Forward Fail
Figure 46: Procedure First_Forwarding_HLR
3GPP
Release 1998 107 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure PRN_Error_HLR PRN_E_H1(1)

to handle a negative response
for a roaming number request
CCBS_Report_
See GSM 03.93
PRN_Failure
Yes
Negative
response=OR
not allowed??
No Set negative
response:
OR not
allowed
Yes
Negative
response=Facility
not supported?
No Set negative
response:
Facility not
supported
Yes
Negative
response=Absent
subscriber?
No
Negative No
response=No
roaming
number?
Yes Set negative
response:
System
failure
Handle_CFNRc Handle_CFNRc
Yes Yes
Result= Result=
Fail? Fail?
Set negative No No Set negative

response: response:
Forwarding Forwarding
violation violation
No No
Result= Result=
Forward? Forward?
Set negative Yes Yes Set negative

response: response:
Absent System
subscriber failure

Fail Forward Fail
Figure 47: Procedure PRN_Error_HLR
3GPP
Release 1998 108 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Forward_CUG_Check FWD_CUG1(1)

for a forwarded call
No
CUG provisioned for
forwarding subscriber against
requested basic service
Yes
Yes
CUG info provided in
routeing information
request
No
Perform
Forwarding CUG As defined in GSM 03.85
authorisation
Pass
CUG
authorisation
result
Fail

Call allowed Call barred Call allowed
Update CUG
As defined in GSM 03.85
info
Figure 48: Procedure Forward _CUG_Check
3GPP
Release 1998 109 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Derive_Requested_Basic_Service_HLR DRBS_H1(1)

Procedure in the HLR to
derive the requested basic
service for an incoming
(MT) call according to the
rules of GSM 09.07
No
Exhaustive
ISDN compatibility
information available?
Yes
No
Multi-
numbering?
Yes
Apply GSM BC Derive GSM BC from

GSM BC:=NULL for this ISDN compatibility
MSISDN information
Derive basic
Basic service:=
service from
default
GSM BC
Figure 49: Procedure Derive_Requested_Basic_Service_HLR
3GPP
Release 1998 110 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_IC_Barring CIB1(2)

and ODB categories
Yes
Operator determined
BAIC imposed?
No
Yes
Operator determined
BIC-Roam imposed?
No
No
MS registered
in HPLMN
country?
Yes
Yes
Operator determined
BIC-RoamHZ
imposed?
No
No
MS registered
in HPLMN
zone?
Yes
Result:=
Call barred
(ODB)
Figure 50a: Procedure Check_IC_Barring (sheet 1)
3GPP
Release 1998 111 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Check_IC_Barring CIB2(2)

request against SS barring 1
and ODB categories
Initiate
of BAIC
Wait_For_
BAIC_
Response
Continue
call From process MAF022
handling
Yes
Call
barred?
No
Initiate
of BIC-Roam
Wait_For_
BIC-Roam_
Response
Continue
call From process MAF023
handling
Yes
Call
barred?
No
Result:=
Result:=
Call barred
Call allowed
(SS barring)
Figure 50b: Procedure Check_IC_Barring (sheet 2)
3GPP
Release 1998 112 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure IC_CUG_Check IC_CUG1(1)

for an incoming (MT) call

CUG_MAF015
incoming To process
call CUG_MAF015
Wait_For_
CUG_Response
response complete call reject

to call (conditional call
request CUG info) (cause)
Result:=
Result:=
Call barred
Call allowed
(cause)
Figure 51: Procedure IC_CUG_Check
3GPP
Release 1998 113 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_CFU H_CFU1(1)

to handle Call Forwarding
Unconditional

MAF007 initiate
handling
of CFU
Wait_For_
CFU_Result
continue
call
handling
Yes
Error?
No
No
Normal
call?
Yes

Fail Continue Forward
Figure 52: Procedure Handle_CFU
3GPP
Release 1998 114 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_CFNRc H_CFNRc1(1)

or VLR to handle Call
Forwarding on Mobile
Subscriber Not Reachable

MAF010 initiate
handling
of CFNRc
Wait_For_
CFNRc_Result
continue
call
handling
Yes
Error?
No
No
Mobile subscriber
not reachable?
Yes

Fail Not reachable Forward
Figure 53: Procedure Handle_CFNRc
3GPP
Release 1998 115 3GPP TS 03.18 V7.5.0 (2003-12)
7.2.3.1 Process PRN_VLR

Sheet 1: the procedure Check_Parameters is specified in subclause 7.2.2.2.
Sheet 1, sheet 3: the procedure CAMEL_SET_SOA is specific to CAMEL; it is specified in GSM 03.78 for
Sheet 2, sheet 3: the task "Store alerting pattern (if received)" is executed only if the VLR supports the feature Network
Indication of Alerting.
Sheet 2, sheet 3: the procedure CLI_PRN_VLR is specific to Enhanced CLI Handling. It is specified in
GSM 03.81 [11].
Sheet 2, sheet 3: the procedure CCBS_Handle_PRN is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 2: the number of unused authentication sets which triggers the VLR to request further authentication sets from the
HLR is an operator option.
Sheet 2: the process Fetch_Authentication_Sets_VLR is specified in subclause 7.1.2.11.
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.
7.2.3.4 Procedure Retrieve_Location_Info_VLR

The test "Retrieve location info from SGSN" takes the "Yes" exit if:
- the Gs interface is implemented; and
- there is an association established between the MSC/VLR and the SGSN.
The stored location information consists of:
- the cell ID of the cell in which the MS last established radio contact;
- the location number and geographical information derived from the 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 GSM standard);
- 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 and geographical information from the received cell ID is a VLR operator option
(the mapping from cell ID to location number is network-specific and outside the scope of the GSM standard).
3GPP
Release 1998 116 3GPP TS 03.18 V7.5.0 (2003-12)
Process PRN_VLR PRN_VLR1(3)
Process in the VLR to handle

a request for a roaming number
Idle
are to/from the HLR.
Provide
Roaming
Number
Check_
Parameters
No
Result=
Pass?
Yes
No
OR
indicator
present?
Yes
OR
supported?
Yes No
If GSM BC was Set negative

Convert GSM BC included in the response:
to basic service Provide Roaming OR not
Number allowed
No
Service
supported
by VLR?
Yes
No Set negative
IMSI
known response:
in VLR? Facility
not supported
No Yes
MSRN
available
Yes Yes
IMSI
detached?
CAMEL_
See GSM 03.78
SET_SOA No
Set negative No
Roaming
response: Allocate
1 in LA
No roaming MSRN
allowed?
number
Yes Set negative
response:
Provide Roaming Absent
Create
Number subscriber
IMSI
negative record
response
Idle 2 3 1
Figure 54a: Process PRN_VLR (sheet 1)
3GPP
Release 1998 117 3GPP TS 03.18 V7.5.0 (2003-12)

2
Data
confirmed
by HLR:=
Signals to the left False
are to the HLR.
Confirmed
by radio
contact:=
False
Location info
confirmed Only if >1 MSC
in HLR:= per VLR
False
IMSI
detached:=
False
If used
Allocate LMSI
by VLR
Store GSM BC, ISDN BC,

compatibility ISDN LLC & ISDN HLC
info (as available)
Store Alerting
Pattern
(if received)
CLI_PRN_
See GSM 03.81
VLR
CCBS_Handle_
See GSM 03.93 4
PRN
Provide
Roaming
Number ack
Yes
More
authentication
sets needed?
No
Fetch_
Authentication_
Sets_VLR
Restore_
Subscriber_
Data_VLR
Idle
Figure 54b: Process PRN_VLR (sheet 2)
3GPP
Release 1998 118 3GPP TS 03.18 V7.5.0 (2003-12)

3
MSRN
available
Signals to the left No
are to the HLR. Yes
Set negative
CAMEL_ response:
See GSM 03.78
SET_SOA No roaming
number
Provide Roaming
MSC Number
per VLR negative
response
>1
1
Received MSC
number= Stored Idle
MSC number?
Yes
No
Confirmed by
radio contact
False
True
Use received Use stored
MSC number MSC number
for MSRN for MSRN
Allocate
MSRN
Store GSM BC, ISDN BC,

compatibility ISDN LLC & ISDN HLC
info (as available)
Store Alerting
Pattern
(if received)
CLI_PRN_
See GSM 03.81
VLR
CCBS_Handle_
See GSM 03.93
PRN
Provide
Roaming
Number ack
Data
confirmed
by HLR
False
True
Idle 4
Figure 54c: Process PRN_VLR (sheet 3)
3GPP
Release 1998 119 3GPP TS 03.18 V7.5.0 (2003-12)
Process Restore_Subscriber_Data_VLR RSD_VLR1(1)
Process in the VLR

to restore subscriber data

are to/from the HLR
Restore
Data
Wait_For_
Data
Restore
Restore
Data negative
Data ack
response
Update
Subscriber
Data
Update
HLR
number
Update MS
If received
Not Reachable
from HLR
indicator
Data
confirmed by
HLR:=True
Figure 55: Process Restore_Subscriber_Data_VLR
3GPP
Release 1998 120 3GPP TS 03.18 V7.5.0 (2003-12)
Process PSI_VLR PSI_VLR1(2)

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

Network Subscriber state:=
state
determined Assumed idle
requested
not reachable
No
Location
info
requested?
Yes
Retrieve_
Location_
Info_VLR
Obtain Provide Provide

Subscriber Subscriber Subscriber
Info Info ack Info negative
response
Wait_For_
Idle Idle
MSC_Response
Figure 56a: Process PSI_VLR (sheet 1)
3GPP
Release 1998 121 3GPP TS 03.18 V7.5.0 (2003-12)
Process PSI_VLR PSI_VLR2(2)

Process in the VLR to handle Signals to/from the left
Wait_For_ are to/from the HLR;
a request from the HLR for
MSC_Response signals to/from the right
subscriber information
are to/from the MSC
Obtain
Subscriber
Info ack
No
Subscriber
state
received?
Yes
Set
subscriber
state
No
Location
info
requested?
Yes
Retrieve_
Location_
Info_VLR
Provide
Subscriber
Info ack
Idle
Figure 56b: Process PSI_VLR (sheet 2)
3GPP
Release 1998 122 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Retrieve_Location_Info_VLR RLI_VLR1(1)

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

Stored Received
location info location info
Derive location number

and geographical information
from cell ID
Figure 57: Procedure Retrieve_Location_Info_VLR
3GPP
Release 1998 123 3GPP TS 03.18 V7.5.0 (2003-12)
7.2.4 Functional requirements of MSC
7.2.4.1 Process OSI_MSC

If the MS is engaged on a circuit-switched call, the state is busy, otherwise assumed idle.
Process OSI_MSC OSI_MSC1(1)

Process in the MSC to handle
a request from the VLR for Signals to/from the left
information on the subscriber's are to/from the VLR
location and state
Idle
Obtain
Subscriber
Info
No
Subscriber
state
requested?
Yes
Set
subscriber
state
Obtain
Subscriber
Info ack
Idle
Figure 58: Process OSI_MSC
3GPP
Release 1998 124 3GPP TS 03.18 V7.5.0 (2003-12)
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 GSM bearer service or teleservice are specified in
GSM 09.07 [24].
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 procedure Process_Access_Request_MSC is specified in subclause 7.1.1.2.
Sheet 1, sheet 2: 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 [28]) 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: 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 2, the procedure CD_Reject is specific to Call Deflection; it is specified in GSM 03.72 [7].
Sheet 2, sheet 4: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS; it is specified in

GSM 03.93 [19].
Sheet 2: the procedure UUS_ICH_Check_Support is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 2, sheet 3, sheet 5: the procedure CCBS_Check_Last_Call is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 3: the procedure CAMEL_Check_ORLCF_VMSC is specific to CAMEL phase 2; it is specified in GSM 03.78

for CAMEL Phase 2 [9]. If the VMSC does not support CAMEL, processing continues from the “ORLCF” exit of the
test “Result?”
Sheet 3: the procedure Handle_ORLCF_VMSC is specific to Support of Optimal Routeing. It is specified in

TS 100 045 [10]. If the VMSC does not support Optimal Routeing, processing continues from the "Continue" exit of the
test "Result?".
Sheet 3; the procedures CD_Failure and CD_Success are specific to Call Deflection; they are specified in
GSM 03.72 [7].
3GPP
Release 1998 125 3GPP TS 03.18 V7.5.0 (2003-12)
Sheet 3: 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 3: it is an operator option whether to send an Address Complete message if the VLR returns forwarding
information. If the VMSC sends an Address Complete message, it shall include the called party’s status field of the
Backward call indicator set to "no indication".
Sheet 3, sheet 4: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 3: the procedure Activate_CF_Process is specified in subclause 7.2.1.7.
Sheet 3: the procedure UUS_ICH_Set_Info_In_IAM is specific to UUS, it is specified in GSM 03.87 [17].
Sheet 3: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in
the Perform Call Forwarding ack.
Sheet 4: the procedure CCBS_MT_MSC_Check_Forwarding is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 4: the procedure Handle_COLP_Forwarding_Interaction is specified in subclause 7.2.1.6.
Sheet 4: the procedure Send_Answer_If_Required is specified in subclause 7.2.1.4.
Sheet 4: the procedure Send_Network_Connect_If_Required is specified in subclause 7.2.1.5.
Sheet 5: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 6: 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.
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 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: the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the
established call.
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.
3GPP
Release 1998 126 3GPP TS 03.18 V7.5.0 (2003-12)
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 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: the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the
established call.
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: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of
information in the Setup and Call Confirmed messages.
Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS, it is specified in GSM 03.87 [17].
Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 1, sheet 2, sheet 4: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS; it is specified in

GSM 03.93 [19].
Sheet 2: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 2, sheet 5: 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 5: the procedure Handling_CD_MSC is specific to Call Deflection; it is specified in GSM 03.72 [7].
Sheet 2, sheet 3: the procedure UUS_ICH_Check_Support is specific to UUS, it is specified in GSM 03.87 [17]. If the
VMSC does not support UUS, the execution continues from the “Yes” exit of the test “Result=Pass?”.
Sheet 2: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS.
Sheet 2: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 2, sheet 3: 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 2, sheet 3: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP.
Sheet 2: the procedure Send_Network_Connect_If_Required is specified in subclause 7.2.1.5.
Sheet 3, sheet 5: the procedure UUS_ICH_Check_Forwarding is specific to UUS, it is specified in GSM 03.87 [17]. If
the VMSC does not support UUS, the execution continues from the "Yes" exit of the test "Result=Pass?".
Sheet 4, sheet 5: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 5: the procedures UUS_MSC_Check_UUS2_UUI_to MS and UUS_MSC_Check_UUS2_UUI_to NW are

specific to UUS, they are specified in GSM 03.87 [17].
Sheet 5: the procedure CD_UUS_Interaction is specific to Call Deflection; it is specified in GSM 03. 72 [7].
3GPP
Release 1998 127 3GPP TS 03.18 V7.5.0 (2003-12)
7.3.1.5 Procedure Process_Call_Waiting_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 Setup and Call Confirmed messages.
Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS; it is specified in GSM 03.87 [17].
Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 2, sheet 3, sheet 4: the procedure UUS_ICH_Check_Support is specific to UUS; it is specified in

GSM 03.87 [17]. If the VMSC does not support UUS, the execution continues from the "Yes" exit of the test
"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 GSM 03.93 [19].
Sheet 2, sheet 5: 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 5: the procedure Handling_CD_MSC is specific to Call Deflection; it is specified in GSM 03.72 [7].
Sheet 2: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS.
Sheet 2, sheet 5: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS; it is specified in

GSM 03.93 [19].
Sheet 2: the Call Confirmed message indicates "busy" for the successful case.
Sheet 2: the procedure Send_ACM_If_Required is specified in subclause 7.2.1.3.
Sheet 2, sheet 4: the Release transaction (reject) message covers all unsuccessful cases not otherwise indicated.
Sheet 3: the procedure Handle_AoC_MT_MSC is specific to AoC. If the VMSC does not support AoC, processing
Sheet 3: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP.
Sheet 4, sheet 5: the procedure UUS_ICH_Check_Forwarding is specific to UUS; it is specified in GSM 03.87 [17]. If
the VMSC does not support UUS, the execution continues from the "Yes" exit of the test "Result=Pass?".
Sheet 5: the procedures UUS_MSC_Check_UUS1_UUI, UUS_MSC_Check_UUS2_UUI_to_MS and

UUS_MSC_Check_UUS2_UUI_to_NW are specific to UUS; they are specified in GSM 03.87 [17].
Sheet 5: the procedure CD_UUS_Interaction is specific to Call Deflection; it is specified in GSM 03. 72 [7].
7.3.1.6 Procedure Set_CLIP_Info_MSC

The originating exchange may release the call or the MS may terminate the transaction with the network by sending a
Release transaction message while a response is awaited from the process CLIP_MAF002. The message is saved for
processing after return from the procedure.
3GPP
Release 1998 128 3GPP TS 03.18 V7.5.0 (2003-12)
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 1998 129 3GPP TS 03.18 V7.5.0 (2003-12)
Process ICH_MSC ICH_MSC1(6)

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

(if present) to GSM bearer
service/teleservice & GSM BC;
Store UUS information (if received)
Send Info
For Incoming
Call
TCH allocated:=False;
ACM sent:=False;
Answer sent:=False;
Network connect sent:=False;
UUS1 result sent:=False;
UUS1 implicit active:=False;
UUS1 explicit active:=False;
Wait_For_ UUS2 active:=False;
Page_Request UUS3 active:=False;
UUS CF interaction:=False
Send Info Send Info

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

1
cause MS_MSC MS_MSC
Yes Yes
Result= Result=
Release To GMSC
Pass? Pass?
No No
Process_
Access_
Request_MSC
No No
Release call Result= Result=
resources Fail? No Fail
Result=
Yes Pass? Yes
Yes
Wait_For_
Release call
MT_Call_
resources
Wait_For_ Wait_For_ Result
Release call
Idle MT_Call_ MT_Call_
resources
Result Result
Release To GMSC Idle
Idle
Release call
resources
Idle
Figure 59a: Process ICH_MSC (sheet 1)
3GPP
Release 1998 130 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_For_
MT_Call_ are to/from the VLR
Result unless marked otherwise
Send Info Process

For Incoming Complete
Call
Call negative Call
Waiting
response
Process_
Complete_
CD_Reject See GSM 03.72 Call_
Call_In_MSC
Waiting_MSC
CCBS_Set_
Diagnostic_ See GSM 03.93
For_Release
Yes
UUS_ICH_
Result=
Pass?
Support
No
Yes
Set Result= Wait_For_
cause Pass? Clear
No
Yes Yes
Release Wait_For_ Result= Result=
transaction Clear Fail Fail
No No
Wait_For_
Release To GMSC MT_Call_
Result
CCBS_Check_
See GSM 03.93
Last_Call
Release
call
resources
Idle
Figure 59b: Process ICH_MSC (sheet 2)
3GPP
Release 1998 131 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_For_
MT_Call_
Process in the MSC Result Signals to/from the left
to handle an incoming (MT) call are to/from the BSS;
are to/from the VLR
Send Info
Call is to be
1 For Incoming
forwarded
Call ack
CAMEL_Check_
ORLCF_VMSC
VMSCCF ORLCF
Result?
CAMEL_ORLCF
Set O-CSI
parameter
Handle_
See GSM 03.79
ORLCF_VMSC
Continue Accepted
Result?
Forwarding failed
CCBS_Check_
See GSM 03.93
Last_Call
Set
redirection
information
Send_ACM_
If_Required
Activate_
CD_Failure See GSM 03.72 CD_Success See GSM 03.72
CF_Process
No
Wait_For_
Result=
Release_
Fail?
From_GMSC
Yes
UUS_ICH_
CD_Failure See GSM 03.72 Set_Info_ See GSM 03.87 Release From GMSC
In_IAM
Initial
CCBS_Check_ CCBS_Check_
See GSM 03.93 Address To process MT_CF_MSC See GSM 03.93
Last_Call Last_Call
Message
Release call
CD_Success See GSM 03.72
resources
Wait_For_
Idle Idle
Forward_ACM
Figure 59c: Process ICH_MSC (sheet 3)
3GPP
Release 1998 132 3GPP TS 03.18 V7.5.0 (2003-12)

Process in the MSC are to/from the GMSC;
Wait_For_ are to/from the process MT_CF_MSC
Forward_ACM
Address
Release Release Connect
Complete
CCBS_MT_
Send_ACM_
See GSM 03.93 MSC_Check_
If_Required
Forwarding
CCBS_Set_
See GSM 03.93 Diagnostic_
For_Release
Release Release
Release call
resources
Wait_For_
Idle
Forward_Answer
Release Release Answer
Handle_COLP_ Handle_COLP_
Release Release Forwarding_ Forwarding_
Interaction_MSC Interaction_MSC
Set COLP Set COLP

presentation presentation
indicator indicator
Send_Network_
Release call Send_Answer_
Connect_
resources If_Required
If_Required
Wait_For_
Idle
Forward_Clear
Figure 59d: Process ICH_MSC (sheet 4)
3GPP
Release 1998 133 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_For_ Signals to/from the left
MT_Call_
Result
are to/from the GMSC
unless otherwise indicated
Release
Release
transaction
Release
Release
transaction
CCBS_Check_
See GSM 03.93
Last_Call
Abort To VLR
Release
call
resources
Idle
Wait_For_
Clear
Release
Release
transaction
UUS_MSC_ UUS_MSC_
UUS1_UUI UUS1_UUI
Release
Release
transaction
CCBS_Check_
See GSM 03.93
Last_Call
Release
call
resources
Idle
Figure 59e: Process ICH_MSC (sheet 5)
3GPP
Release 1998 134 3GPP TS 03.18 V7.5.0 (2003-12)
Process in the MSC

to handle an incoming (MT) call Signals to/from the left
are to/from the GMSC;
are to/from the process MT_CF_MSC
Wait_For_
Forward_Clear
Release Release
Release Release
Release
call
resources
Idle
Wait_For_Forward_ACM,
Wait_For_Forward_Answer,
Wait_For_Forward_Clear
* *
- -
Figure 59f: Process ICH_MSC (sheet 6)
3GPP
Release 1998 135 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Page_MS_MSC PAGE_M1(2)

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

Location
are to/from the BSS; area ID
signals to/from the right known?
are to/from the VLR
unless marked otherwise Yes
Set negative
response:
Unknown LAI
No
Call
still
exists?
Yes Set negative
response:
System
Failure
Yes
MS
connection
exists?
No
Yes
Clear received:= SMS or SS
False page?
No
No Yes
Paging via
MS busy?
SGSN possible?
No
Yes
Yes
In specified Call in
Page
location area setup?
No
Yes
Page MS Call
via SGSN waiting?
No
Set negative Set negative

More calls response:
response:
possible Busy Subscriber
Busy Subscriber
(NDUB)
Set access Page MS

connection negative
status response
Start Page
Result:= Result:=
response
Pass Fail
timer
Wait_For_
Page_
Response
Figure 60a: Procedure Page_MS_MSC (sheet 1)
3GPP
Release 1998 136 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Page_MS_MSC PAGE_M2(2)

Procedure in the MSC Wait_For_ Signals to/from the left
to page an MS in a Page_ are to/from the BSS;
specified location area Response signals to/from the right
are to/from the VLR
MS Page CM
For circuit-
connection Release From GMSC response Service
switched call
established timer expired Request
True True
CM
Clear Clear To process
Abort Service
received received OCH_MSC
Request
False False
True
Clear
received
False

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

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

Pass Aborted True Aborted Fail Fail Aborted
Wait_For_
Page_
Response
Figure 60b: Procedure Page_MS_MSC (sheet 2)
3GPP
Release 1998 137 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Search_For_MS_MSC SRCH_M1(2)

to search for an MS are to/from the BSS;
(page in all location areas) signals to/from the right
are to/from the VLR
No
Call
still
exists?
Yes
Yes Set negative

MS
connection response:
exists? System
Failure
No
Yes
Clear received:= SMS or SS
False page?
No
No Yes
Paging via
MS busy?
SGSN possible?
No
Yes
Yes
Call in
setup?
No
Yes
Search for MS Call
via SGSN waiting?
No

More calls response:
response:
possible Busy Subscriber
Busy Subscriber
(NDUB)
Set access Search

In all For MS
Page connection
location areas negative
status
response
Start Page
Result:= Result:=
response
Pass Fail
timer
Wait_For_
Search_
Response
Figure 61a: Procedure Search_For_MS_MSC (sheet 1)
3GPP
Release 1998 138 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Search_For_MS_MSC SRCH_M2(2)

Procedure in the MSC Wait_For_ Signals to/from the left
to search for an MS Search_ are to/from the BSS;
(page in all location areas) Response signals to/from the right
are to/from the VLR
MS Page CM
For circuit-
connection Release From GMSC response Service
switched call
established timer expired Request
True True
CM
Clear Clear To process
Abort Service
received received OCH_MSC
Request
False False
True
Search Release Clear
For MS ack transaction received
False

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

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

Pass Aborted True Aborted Fail Fail Aborted
Wait_For_
Search_
Response
Figure 61b: Procedure Search_For_MS_MSC (sheet 2)
3GPP
Release 1998 139 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Complete_Call_In_MSC CCI_MSC1(5)

to complete an MT call
on request from the VLR
Set_CLIP_
Info_MSC

signals to/from the right Derive_
are to/from the VLR GSM_BC_
unless marked otherwise MSC
Setup
UUS_ICH_UUS1_
Implicit_ See GSM 03.87
Active
CCBS_Report_
See GSM 03.93
Not_Idle
Wait_For_
Setup_
Response
Call Setup
Confirmed failure
Establish_
Terminating_
TCH_If_
Required
Yes
Result=
Fail?
No
Yes Set negative Set negative

Result= response: response:
Aborted Radio Absent
congestion Subscriber
No
Complete
Abort Call
negative
response
CCBS_ICH_MSC_
See GSM 03.93
Report_Failure
Result:= Result:=
Aborted Fail
Wait_For_
Alerting
Figure 62a: Procedure Complete_Call_In_MSC (sheet 1)
3GPP
Release 1998 140 3GPP TS 03.18 V7.5.0 (2003-12)

Alerting signals to/from the right
are to/from the VLR
Alerting
Alerting Connect 1 CD_Request
failure
UUS_ICH_ UUS_ICH_ Release

See GSM 03.87
Check_Support Check_Support transaction
No No
Result= Result=
Set cause
Pass? Pass?
Yes Yes
CCBS_ICH_MSC_
1 See GSM 03.93
Report_Success
CCBS_ICH_MSC_ CCBS_ICH_MSC_ CCBS_ICH_MSC_

See GSM 03.93 See GSM 03.93 See GSM 03.93
Report_Success Report_Success Report_Failure
No
NRCT Handle_AoC_
Abort See GSM 03.72 Handling_CD_MSC
provided? MT_MSC
Yes
Complete
Start No Reply Call
Release To GMSC
Call Timer negative
response
Send_ACM_ Result= Result:= Result:=

To GMSC
If_Required Pass? Aborted Fail
No
Yes
Connect
UTU2Cnt:=0
ack
Set_COL_
Wait_for_
Presentation_
Answer
Indicator_MSC
Send_Network_
To GMSC Connect_If_ Release To GMSC
Required
Complete
Call Abort
ack
Result:= Result:=
Pass Aborted
Figure 62b: Procedure Complete_Call_In_MSC (sheet 2)
3GPP
Release 1998 141 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_for_
Answer Signals to/from the left
to complete an MT call are to/from the BSS;
on request from the VLR signals to/from the right
are to/from the VLR
No Reply
Call Timer Connect
expired
UUS_ICH_ UUS_ICH_
Forwarding Support
No No
Result= Result=
2
Pass? Pass?
Yes Yes
Set negative
response: Release Handle_AoC_
1 Set cause
No subscriber transaction MT_MSC
reply
Complete No
Call Result=
2
negative Pass?
response
Yes
Release Connect
transaction ack
Set_COL_
Result:=
Presentation_
Fail
Indicator_MSC
Send_Answer_
To GMSC Release To GMSC
If_Required
Complete
Call Abort
ack
Result:= Result:=
Pass Aborted
Figure 62c: Procedure Complete_Call_In_MSC (sheet 3)
3GPP
Release 1998 142 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_For_Setup_Response, are to/from the BSS;
Wait_For_Alerting signals to/from the right
are to/from the VLR
Release
Release From GMSC
transaction
CCBS_ICH_MSC_ CCBS_ICH_MSC_
User
busy?
Yes
Yes
UUS_MSC_ UUS_MSC_
UUS1_UUI UUS1_UUI
Set negative
response: Release
Release To GMSC
Busy subscriber transaction
(UDUB)
Complete
Call Abort
negative
response
Result:= Result:=
Fail Aborted
Figure 62d: Procedure Complete_Call_In_MSC (sheet 4)
3GPP
Release 1998 143 3GPP TS 03.18 V7.5.0 (2003-12)

to complete an MT call are to/from the BSS;
on request from the VLR signals to/from the right
Wait_For_ are to/from the VLR
Answer unless marked otherwise
Release
From GMSC Release CD Request
transaction
UUS_MSC_ UUS_ICH_
See GSM 03.87 Check_ Check_ See GSM 03.87
UUS1_UUI Forwarding
No
User Release Result=
busy? transaction Pass?
No
Yes
Yes
UUS_ICH_ UUS_MSC_
Forwarding UUS1_UUI
Handling_
Release To GMSC See GSM 03.72
CD_MSC
No Complete
Result= CD_UUS_ Call
Abort See GSM 03.72
Pass? Interaction negative
response
Yes
Set negative UUS_MSC_

response: Result:= Result:=
Check_
Busy subscriber Aborted Fail
UUS1_UUI
(UDUB)
Complete
Call 1 2
negative
response
Result:= Wait_For_
Fail Answer
User to User to
User User
UUS_MSC_ UUS_MSC_
See GSM 03.87 Check_UUS2_ Check_UUS2_ See GSM 03.87
UUI_to_NW UUI_to_MS
Wait_For_
Answer
Figure 62e: Procedure Complete_Call_In_MSC (sheet 5)
3GPP
Release 1998 144 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Process_Call_Waiting_MSC PCW_MSC1(5)

to handle a Process Call Waiting
request from the VLR
Yes
Call being
Signals to/from the left set up
signals to/from the right No
are to/from the VLR
Set negative
Set_CLIP_ response:
Info_MSC Busy
subscriber(NDUB)
Derive_ Process
GSM_BC_ Call Waiting
MSC negative
response
Result:=
Setup
Fail
UUS_ICH_UUS1_
Implicit_ See GSM 03.87
Active
CCBS_Report_
See GSM 03.93
Not_Idle
Wait_For_
Setup_
Response
Figure 63a: Procedure Process_Call_Waiting_MSC (sheet 1)
3GPP
Release 1998 145 3GPP TS 03.18 V7.5.0 (2003-12)

to handle a Process Call Waiting are to/from the BSS;
request from the VLR Wait_For_ signals to/from the right
Setup_ are to/from the VLR
Response unless marked otherwise
2
Release Release
Call
Setup failure transaction transaction
Confirmed
(reject) (UDUB)
Set cause
Clear UUS_ICH_
Wait_For_
pending Check_
Alerting
call Support
UUS_ICH_
Alerting
Alerting CD Request See GSM 03.87 Check_
failure
Support
UUS_ICH_ Set negative

CCBS_ICH_MSC_ CCBS_ICH_MSC_ response:
Check_ For waiting call See GSM 03.93 See GSM 03.93
Report_Success Report_Failure Busy
Support
subscriber(UDUB)
No Process
Result= Handling_ To GMSC of Call Waiting
See GSM 03.72 Release
Pass? CD_MSC waiting call negative
response
Yes
Process
Release Call Waiting CCBS_ICH_MSC_
Abort See GSM 03.93
transaction negative Report_Failure
response

2
Fail Aborted Fail
CCBS_ICH_MSC_
See GSM 03.93
Report_Success
UTU2Cnt:=0
No
NRCT
provided?
Yes
Start Start
No Reply Acceptance
Call Timer timer
Send_ACM_ To GMSC of
If_Required waiting call
Wait_For_
Acceptance
Figure 63b: Procedure Process_Call_Waiting_MSC (sheet 2)
3GPP
Release 1998 146 3GPP TS 03.18 V7.5.0 (2003-12)

Wait_for_ are to/from the BSS;
to handle a Process Call Waiting
Acceptance signals to/from the right
request from the VLR
are to/from the VLR
Connect
UUS_ICH_
Support
No
Result=
Pass?
Yes
Establish_
Terminating_ Release For waiting call
TCH_If_
Required
Yes No
Result=
2
Pass?
Yes
Handle_AoC_ Result=
MT_MSC Aborted?
No
No
Result=
Pass?
Yes
Connect
ack
Set_COL_
Presentation_
Indicator_MSC
Send_
To GMSC of To GMSC of
Answer_If_ Release Abort
waiting call waiting call
Required
Process Call Release call

Abort For waiting call
Waiting ack resources

Pass Aborted Aborted
Figure 63c: Procedure Process_Call_Waiting_MSC(sheet 3)
3GPP
Release 1998 147 3GPP TS 03.18 V7.5.0 (2003-12)

Procedure in the MSC are to/from the BSS;
to handle a Process Call Waiting signals to/from the right
request from the VLR are to/from the VLR
Wait_for_ unless marked otherwise
Acceptance
Release Release No Reply

Acceptance
transaction transaction 1 Call Timer
timer expired
(busy) (reject) expired
UUS_ICH_ UUS_ICH_
Check_ See GSM 03.87 See GSM 03.87 Check_
Forwarding Forwarding
No No
Result= Result=
Pass? Pass?
Yes Yes

UUS_MSC_
response: Release response:
Check_ For waiting call
Busy transaction No subscriber
UUS1_UUI
subscriber(UDUB) reply
Process Process
UUS_ICH_
Call Waiting Call Waiting
2 Check_ See GSM 03.87
negative negative
Forwarding
response response
Result:= To GMSC of Release

Release For waiting call
Fail waiting call transaction
Result:=
Abort
Fail
Result:=
Aborted
Figure 63d: Procedure Process_Call_Waiting_MSC(sheet 4)
3GPP
Release 1998 148 3GPP TS 03.18 V7.5.0 (2003-12)

to handle a Process Call Waiting are to/from the BSS;
request from the VLR signals to/from the right
are to/from the VLR
Wait_For_
Acceptance
From GMSC of User To User To

Release CD Request
waiting call User User
UUS_MSC_ UUS_ICH_ UUS_MSC_ UUS_MSC_

Check_ See GSM 03.87 Check_ See GSM 03.87 Check_UUS2_ See GSM 03.87 Check_UUS2_
UUS1_UUI Forwarding UUI_to_NW UUI_to_MS
No
Release Result=
For waiting call
transaction Pass?
Yes
Handling_ CD_UUS_ Wait_For_

Abort See GSM 03.72 See GSM 03.72
CD_MSC Interaction Acceptance
Process
Release call Call Waiting Wait_For_Setup_Response,
For waiting call
resources negative Wait_For_Alerting
response
Result:= Result:= From GMSC of

Release
Aborted Fail waiting call
CCBS_ICH_MSC_
1 See GSM 03.93
Report_Failure
UUS_MSC_
See GSM 03.87 Check_
UUS1_UUI
Release
For waiting call
transaction
Abort
Release call
For waiting call
resources
Result:=
Aborted
Figure 63e: Procedure Process_Call_Waiting_MSC(sheet 5)
3GPP
Release 1998 149 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Set_CLIP_Info_MSC CAINF_M1(1)

to determine the CLIP
information to be sent to the MS

CLIP_MAF002 Initiate
handling
of CLIP
Wait_For_
CLIP_Info
Continue
Release
From BSS call Release From GMSC
transaction
handling
Figure 64: Procedure Set_CLIP_Info_MSC
3GPP
Release 1998 150 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Derive_GSM_BC_MSC DRBC_M1(1)

Procedure in the MSC to
derive the requested GSM BC
according to the rules of
GSM 09.07
No
GSM BC derived from
ISDN compatibility
information?
Yes
Yes
GSM BC received
in PRN?
No
Use GSM BC Use GSM BC

Omit GSM BC derived from
received
from Setup ISDN compatibility
in PRN
information
Figure 65: Derive_GSM_BC_MSC
3GPP
Release 1998 151 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Establish_Terminating_TCH_If_Required ETTCIR1(1)

Procedure in the terminating VMSC Signals to/from the left
to establish a Traffic Channel are to/from the BSS;
if one has not been established signals to/from the right
for this call are to/from the GMSC
True
TCH
allocated
False
Allocate Result:=
channel Pass
Wait_For_
Allocation_
Complete
Release Allocation Allocation

Release
transaction failure complete
Release TCH allocated:= Release

transaction True transaction

Fail Pass Aborted
Figure 66: Procedure Establish_Terminating_TCH_If_Required
3GPP
Release 1998 152 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_AoC_MT_MSC AOCMT_M1(1)

to handle AoC signalling are to/from the BSS;
towards the MS for an MT call signals from the right
are from the AoC timer function.
Yes
AoC(I)
provisioned?
No
No
Set
AoC(C)
charging
provisioned?
parameters
Yes
Send Set
Charging charging
Parameters parameters
Send
Charging
Parameters
Start AoC
acknowledgment
timer
Wait_For_
Charging_
Parameters_
Ack
Charging AoC
Release
Parameters acknowledgment
connection
ack timer expired
Release
transaction
Result:= Result:=
Pass Fail
Figure 67: Procedure Handle_AoC_MT_MSC
3GPP
Release 1998 153 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Set_COL_Presentation_Indicator_MSC COIND_M1(1)

to determine the COL
presentation indicator value

COLR_MAF041 Initiate
handling
of COLR
Wait_For_
COLR_Info
Continue
Release
From BSS call Release From GMSC
transaction
handling
Figure 68: Procedure Set_COL_Presentation_Indicator MSC
3GPP
Release 1998 154 3GPP TS 03.18 V7.5.0 (2003-12)
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 CCBS_ICH_Set_CCBS_Call_Indicator is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 1: 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 1, sheet 2, sheet 3: the procedure CCBS_ICH_VLR_Report_Failure is specific to CCBS; it is specified in

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

GSM 03.93 [19].
Sheet 2: 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 2: 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 2: 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 2: 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.
Sheet 2: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC; it is specified in subclause 7.1.2.15.
Sheet 2 sheet 4: the procedure CLI_ICH_VLR_Add_CLI is specific to Enhanced CLI Handling. It is specified in
GSM 03.81 [11].
Sheet 2: the procedure CCBS_ICH_Handle_NDUB is specific to CCBS; it is specified in GSM 03.93 [19]. If the VLR
does not support CCBS, processing continues from the "Forward" exit of the test "Result".
Sheet 2: the procedure Process_Access_Request_VLR is specified in subclause 7.1.2.2.
Sheet 2: the output signal Page MS towards the SGSN includes the Location area identity parameter.
Sheet 2: if the VLR does not support CUG, handling continues from the "No" exit of the test "CUG info present?".
Sheet 3, sheet 4: the procedure CD_Authorization is specific to Call Deflection, it is specified in GSM 03.72 [7]. If the
VLR does not support Call Deflection, processing continues from the "Yes" exit of the test "Result=Aborted?".
Sheet 3, sheet 4: the procedure CCBS_ICH_Handle_UDUB is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 4: the test "NDUB?" is executed only if the VLR supports CCBS. If the VLR does not support CCBS, processing
continues from connector 5.
Sheet 5: the procedure CCBS_ICH_Set_CCBS_Target is specific to CCBS; it is specified in GSM 03.93 [19].
Sheet 5: the procedure Handle_CFNRc is specified in subclause 7.2.2.11.
Sheet 6: 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?".
3GPP
Release 1998 155 3GPP TS 03.18 V7.5.0 (2003-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 1998 156 3GPP TS 03.18 V7.5.0 (2003-12)
Process ICH_VLR ICH_VLR1(6)

Process in VLRB to
handle a request for information
Idle
Send Info
For Incoming
Call
No
MSRN
known?
Yes
CCBS_ICH_
Set_CCBS_ See GSM 03.93
Call_Indicator
False
Data
confirmed
by HLR
True

Derive_Requested_ response: response:
Basic_Service_VLR System Unallocated
Failure Roaming Number
IMSI CCBS_ICH_VLR_
See GSM 03.93
detached? Report_Failure
Yes
No
Yes
Roaming
in LA
allowed?
No
No Yes
Location
area ID
known?
Yes
Paging via
SGSN possible?
No
Set Paging
via SGSN
possible
Search_For_
MS_VLR
Page type=
Page MS
circuit-switched call
Yes
Result=
Pass?
No
Yes Send Info

CCBS_ICH_
Result= For Incoming
Report_Not_ See GSM 03.93
Fail? Call negative
Reachable
response
No
CCBS_ICH_VLR_
See GSM 03.93
Report_Failure
Wait_For_
Idle 2 Access_ 1 Idle
Request
Figure 69a: Process ICH_VLR (sheet 1)
3GPP
Release 1998 157 3GPP TS 03.18 V7.5.0 (2003-12)

Process in VLRB to Wait_For_
handle a request for information Access_
for an incoming (MT) call Request
Page MS Process
Page MS
negative 2 Access Abort
via SGSN
response Request
Page MS To SGSN
Yes
Process_
Absent
Access_
subscriber?
Request_VLR
CCBS_ICH_ Wait_For_
No
See GSM 03.93 Report_Not_ Access_
Reachable Request
No
Result=
Pass?
1 Yes
CCBS_ICH_VLR_
See GSM 03.93
No Report_Failure
Busy
subscriber? Yes
CUG
info
present?
Yes
3 Idle
No
Yes
NDUB?
Translate CUG
As defined in
interlock
No GSM 03.85
to index
Get_CW_
Subscription_
Yes
Info_VLR
Success?
Yes No
CFNRy
No A&O?
CW
available? No
Provide
NRCT 3
value
Yes
9
Get_LI_
Subscription_
Info_MT_VLR Set negative
CCBS_ICH_
See GSM 03.93 response:
Handle_NDUB
System failure
Get_AoC_
Subscription_
Get_LI_ Info_VLR
Subscription_
Release
Info_MT_VLR
CCBS_ICH_VLR_
Result See GSM 03.93
Report_Failure
CLI_ICH_VLR_
See GSM 03.81
Forward Add_CLI
Get_AoC_
Subscription_
Info_VLR Send Info
Complete For Incoming
Call Call negative
response
Wait_For_
4 8 5 Complete_Call_ Idle
Result
Figure 69b: Process ICH_VLR (sheet 2)
3GPP
Release 1998 158 3GPP TS 03.18 V7.5.0 (2003-12)

Process in VLRB to Wait_for_
handle a request for information Complete_Call
for an incoming (MT) call Result
Complete
Complete
Abort Call negative
Call ack
response
Yes
Busy
Idle
subscriber?
No
CCBS_ICH_
See GSM 03.93
Handle_UDUB
Yes
Absent
subscriber?
No
Yes
Radio
congestion?
No
Yes
No
subscriber
reply?
No
CD_ CCBS_ICH_VLR_
Authorization Report_Failure
No
Result=
Aborted?
Yes
No Set negative
Result= response: 6 1 5
Fail? Impossible call
completion
Yes
Send Info
For Incoming
Call negative
response
7 Idle
Figure 69c: Process ICH_VLR (sheet 3)
3GPP
Release 1998 159 3GPP TS 03.18 V7.5.0 (2003-12)

4
Process in VLRB to
No
CFNRy
A&O?
Yea
Set NRCT
CLI_ICH_VLR_
See GSM 03.81
Add_CLI
Process
Call
Waiting
Wait_For_
PCW_Result
Process Process
Call Abort Call Waiting
Waiting ack negative
response
Yes
Busy
Idle
subscriber?
No
Yes Yes
No
subscriber NDUB?
reply?
No No
CD_
See GSM 03.72
Authorization
9
No
Result=
Aborted?
Yes
No Set negative
Result= response: CCBS_ICH_
See GSM 03.93
Fail? Impossible call Handle_UDUB
completion
Yes
Send Info
For Incoming
Call negative
response
7 Idle 6 5
Figure 69d: Process ICH_VLR (sheet 4)
3GPP
Release 1998 160 3GPP TS 03.18 V7.5.0 (2003-12)

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

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

Set_CCBS_ See GSM 03.93 response:
Forwarding No
Target
Violation Result=
Forward?
Set negative Set negative Yes

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

Set_CCBS_ See GSM 03.93 For Incoming
Target Call negative
response
7 Idle 7
Figure 69e: Process ICH_VLR (sheet 5)
3GPP
Release 1998 161 3GPP TS 03.18 V7.5.0 (2003-12)

Process in VLRB to
Signals to the left
handle a request for information 7
are to the MSC.
Forward_
CUG_Check
No
Result=
Call
allowed?
Yes
Set negative
Set result:
response:
Forward
CUG reject
Set
forwarding
information
Send Info Send Info

For Incoming For Incoming
Call ack Call negative
response
Idle Idle
Figure 69f: Process ICH_VLR (sheet 6)
3GPP
Release 1998 162 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Derive_Requested_Basic_Service_VLR DRBS_V1(1)

Procedure in the VLR to
derive the requested basic
service for an incoming
(MT) call
Yes
Basic service included in
Send Info For Incoming Call?
No
Yes
Basic service:=
GSM BC received in
BS received in
Provide Roaming Number
SIFIC
No
Basic service:=
Basic service:=
BS derived from
default
GSM BC
Figure 70: Procedure Derive_Requested_Basic_Service_VLR
3GPP
Release 1998 163 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Search_For_MS_VLR SRCH_V1(1)

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

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

For MS Circuit-switched call
Wait_For_
Search_Result
Search
Search For MS Search for MS
Abort
For MS ack negative via SGSN
response
Update
Location To SGSN Page MS
Area ID

Pass Fail Aborted
Wait_For_
Search_Result
Figure 71: Procedure Search_For_MS_VLR
3GPP
Release 1998 164 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Get_CW_Subscription_Info_VLR CWI_VLR1(1)

information for the
Call Waiting service

MAF013 initiate
handling
of CW
Wait_For_
CW_Info
process
From MSC Abort call
waiting
Figure 72: Procedure Get_CW_Subscription_Info_VLR
3GPP
Release 1998 165 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Get_LI_Subscription_Info_MT_VLR GLI_MTV1(1)

information for the CLIP
& COLR line identification
services for an MT call
Initiate
handling To process CLIP_MAF001
of CLIP
Wait_For_
CLIP_Info
Continue
From MSC Abort call From process CLIP_MAF001
handling
Initiate
handling To process COLR_MAF040
of COLR
Wait_For_
COLR_Info
Continue
From MSC Abort call From process COLR_MAF040
handling
Figure 73: Procedure Get_LI_Subscription_Info_MT_VLR
3GPP
Release 1998 166 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_CFB H_CFB1(1)

on Busy

MAF008 initiate
handling
of CFB
Wait_For_
CFB_Result
continue
call
handling
Yes
Error?
No
No
Normal
call
busy?
Yes

Fail Busy Forward
Figure 74: Procedure Handle_CFB
3GPP
Release 1998 167 3GPP TS 03.18 V7.5.0 (2003-12)
Procedure Handle_CFNRy H_CFNRy1(1)

on No subscriber Reply

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

Fail No reply Forward
Figure 75: Procedure Handle_CFNRy
3GPP
Release 1998 168 3GPP TS 03.18 V7.5.0 (2003-12)
8 Contents of messages
This clause specifies the content of each message shown in clauses 5 & 7, except for the following messages, which are
not specific to call handling:
On the D interface (VLR-HLR):
- abort;
- activate Trace Mode
- 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:

RAND M Random number challenge to be sent to the MS (GSM 03.20 [3])
CKSN M Cipher key sequence number to be sent to the MS (GSM 03.20 [3])
8.1.3 Authenticate ack


SRES M Signature result returned by the MS (GSM 03.20 [3])
8.1.4 Check IMEI

This message contains no information elements.
3GPP
Release 1998 169 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.5 Check IMEI ack


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

The negative response information element can take the following values:
- system failure;
- unknown equipment.
8.1.7 Complete Call

MSISDN C MSISDN of the MS for which the Complete Call is sent. Shall be
present for an ordinary MO call, for an MT call and for an
emergency call when the MS is registered in the VLR; otherwise
shall be absent.
IMEI C IMEI of the mobile for which the Complete Call is sent. Shall be
present for an emergency call when the mobile is identified only by
its IMEI; otherwise shall be absent.
Category C Category of the MS for which the Complete Call is sent. Shall be
present for an ordinary MO call and for an emergency call when
the MS is registered in the VLR; otherwise shall be absent.
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.
(continued)
3GPP
Release 1998 170 3GPP TS 03.18 V7.5.0 (2003-12)
The following information elements are required (concluded):

No Reply Condition Timer C Value of timer to be used to determine the No subscriber reply
condition. Shall be present for an MT call if the Call Forwarding on
No Reply service is active and operative; otherwise shall be
absent.
CUG index C For the definition of this IE, see GSM 03.85 [15]. 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 GSM 03.85 [15]. 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 GSM 03.85 [15]. 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;
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.8 Complete Call ack

8.1.9 Complete Call negative response

- absent subscriber;
- busy subscriber;
- no subscriber reply;
- radio congestion.
8.1.10 Forward New TMSI


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

8.1.12 Forward New TMSI negative response

The negative response information element can take the following value:
- TMSI reallocation failure.
3GPP
Release 1998 171 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.13 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.14 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.15 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 or SS activity
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.16 Page MS negative response

- busy subscriber (More calls possible);
- 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 1998 172 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.17 Page MS via SGSN


eMLPP priority O Circuit-switched paging priority.
Channel type O Type of channel required for the call.
8.1.18 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 this
specification.
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.
Serving cell ID M Identity of the cell in use by the served subscriber.
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
IMEI C IMEI of the MS requesting the access. For normal MO call or page
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.19 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 1998 173 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.20 Process Access Request negative response

- roaming not allowed;
- system failure;
- unidentified subscriber;
- illegal equipment;
- illegal subscriber.
8.1.21 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 GSM 03.85 [15]. 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.22 Process Call Waiting ack

8.1.23 Process Call Waiting negative response

- busy subscriber (UDUB);
- no subscriber reply.
8.1.24 Provide IMEI

3GPP
Release 1998 174 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.25 Provide IMEI ack


IMEI M IMEI of the ME involved in the access request.
8.1.26 Provide IMSI

8.1.27 Provide IMSI ack


IMSI M IMSI of the MS involved in the access request.
8.1.28 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 or SS activity
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.29 Search For MS ack


Location area ID M Location area in which the MS responded to the page.
8.1.30 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 1998 175 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.31 Search for MS via SGSN


eMLPP priority O Circuit-switched paging priority.
Channel type O Type of channel required for the call.
8.1.32 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.
CUG interlock C For the definition of this IE, see GSM 03.85 [15]. Shall be present if
it was received in the IAM; otherwise shall be absent.
CUG outgoing access C For the definition of this IE, see GSM 03.85 [15]. Shall be present if
it was received in the IAM; otherwise shall be absent.
3GPP
Release 1998 176 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.33 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 GSM 03.03 [2]). 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.
the VLR has determined that the forwarded call is to be treated as
a CUG call in accordance with the rules in GSM 03.85 [15],
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
GSM 03.85 [15], 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 1998 177 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.34 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.35 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 Setup 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 Setup request from the MS or
from the emergency Setup request from the MS. One of bearer
service or teleservice shall be present.
CUG index C For the definition of this IE, see GSM 03.85 [15]. Shall be present if
it was received in the Setup request from the MS.
Suppress preferential CUG C For the definition of this IE, see GSM 03.85 [15]. Shall be present if
Suppress CUG outgoing access C For the definition of this IE, see GSM 03.85 [15]. Shall be present if
8.1.36 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 1998 178 3GPP TS 03.18 V7.5.0 (2003-12)
8.1.37 Set ciphering mode


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.38 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 [26]
8.1.39 Use existing TMSI

8.2 Messages on the C interface (MSC-HLR)

8.2.1 Send Routeing Info

MSISDN M MSISDN of the B subscriber (see GSM 03.03 [2]).
Alerting Pattern C Shall be present if received in a Connect operation from the
gsmSCF; otherwise shall be absent.
the GMSC received it in the IAM, otherwise shall be absent.
the GMSC received it 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.
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.
3GPP
Release 1998 179 3GPP TS 03.18 V7.5.0 (2003-12)
8.2.2 Send Routeing Info ack


IMSI M IMSI of the B subscriber (see GSM 03.03 [2]).
Roaming number C E.164 number required to route the call to VMSCB (see
GSM 03.03 [2]). Shall be present if the HLR received it in the
Provide Roaming Number ack, 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 GSM 03.03 [2]). 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.
the HLR has determined that the call is to be treated as a CUG call
in accordance with the rules in GSM 03.85 [15], otherwise shall be
absent.
the HLR has determined that the call is to be treated as a CUG call
with outgoing access in accordance with the rules in
GSM 03.85 [15], 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 1998 180 3GPP TS 03.18 V7.5.0 (2003-12)
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 1998 181 3GPP TS 03.18 V7.5.0 (2003-12)
8.3 Messages on the D interface (VLR-HLR)

8.3.1 Provide Roaming Number

IMSI M IMSI of the B subscriber (see GSM 03.03 [2]).
MSC number M E.164 number which identifies VMSCB (see GSM 03.03 [2]).
MSISDN O E.164 number which identifies the B subscriber. 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 GSM 04.08. 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.
8.3.2 Provide Roaming Number ack


Roaming number M E.164 number required to route the call to VMSCB (see
GSM 03.03 [2]).
8.3.3 Provide Roaming Number negative response

- data missing;
- facility not supported;
- no roaming number available;
- OR not allowed;
- unexpected data value.
3GPP
Release 1998 182 3GPP TS 03.18 V7.5.0 (2003-12)
8.3.4 Provide Subscriber Info


IMSI M IMSI of the subscriber for whom information is requested (see
GSM 03.03 [2]).
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.
8.3.5 Provide Subscriber Info ack


Location information C Information to define the location of the MS: see definition in
subclause 8.3.5.1. Shall be present if location information was
requested and is available; otherwise shall be absent.
Subscriber state C Indicates whether the MS is busy (i.e. engaged on a circuit-
switched call), network determined not reachable (IMSI detached
or roaming in a prohibited location area) or assumed idle. Shall be
present if subscriber state was requested; otherwise shall be
absent.
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
ETS 300 356-1 [27]. Shall be present if the VLR can derive it from
the stored cell global identity or location area identity; otherwise
shall be absent. The mapping from cell ID and location area to
location number is network-specific and outside the scope of the
GSM standard.
Cell ID or LAI C Cell global identity of the cell or Location Area identity in which the
MS is currently in radio contact or in which the MS was last in radio
contact. Shall be present if the subscriber record is marked as
confirmed by radio contact; otherwise shall be absent.
If CAMEL phase 1 or 2, or MAP pre-R99 is used in a 3G radio

access of R99 or later network element then this IE may contain
the 3G Service Area Identity (SAI). The encoding of SAI is identical
to the Cell Global ID.
Geographical information C For a definition of this information element, see
GSM 03.32 (Universal Geographical Area Description). Shall be
present if the VLR can derive it from the stored cell global identity
or location area identity; otherwise shall be absent.
VLR number O E.164 number which identifies the VLR (see GSM 03.03 [2]). 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.
8.3.6 Provide Subscriber Info negative response

- data missing;
3GPP
Release 1998 183 3GPP TS 03.18 V7.5.0 (2003-12)
- system failure;
- unexpected data value.
3GPP
Release 1998 184 3GPP TS 03.18 V7.5.0 (2003-12)
8.3.7 Restore Data


IMSI M IMSI of the subscriber for whom data are to be restored (see
GSM 03.03 [2]).
LMSI O LMSI of the subscriber for whom data are to be restored (see
GSM 03.03 [2]). May be included if required by the requesting
VLR.
8.3.8 Restore Data ack


HLR number M E.164 number which identifies the HLR (see GSM 03.03 [2]).
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
GSM 03.03 [2]).
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 1998 185 3GPP TS 03.18 V7.5.0 (2003-12)
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.
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 Gs interface

8.6.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.6.2 Send MS information


Information requested M Information required for the specified MS.
3GPP
Release 1998 186 3GPP TS 03.18 V7.5.0 (2003-12)
8.6.3 Send MS information ack


Cell ID M (note) Cell ID of the cell in which the MS last established radio contact
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.6.4 Send MS information negative response

- no response from SGSN.
3GPP
Release 1998 187 3GPP TS 03.18 V7.5.0 (2003-12)
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 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 1998 188 3GPP TS 03.18 V7.5.0 (2003-12)
Process MSC_Coord Coord_M1(2)

Process in the MSC to
handle an incoming IAM IDLE
and trigger the correct
application process
From
Initial
originating
Address
exchange
No
Called party address
in MSRN range
for this MSC?
Yes
No
Incoming IAM was
routed with routeing
number for MNP?
Yes
No
Recover
HLR address
ported number
derivable?
from IAM
Yes
Mark number as
subscribed in
this network
To destination
To process Initial Initial To process Initial
determined by
ICH_MSC Address Address MT_GMSC Address
routeing tables
Relay_ Relay_
Information_ Information_
Internally Externally
Figure 76a: Process MSC_Coord (sheet 1)
3GPP
Release 1998 189 3GPP TS 03.18 V7.5.0 (2003-12)
Process MSC_Coord Coord_M2(2)

Process in the MSC to Relay_
handle an incoming IAM Information_
and trigger the correct Internally
application process
From
Release originating Release From offspring
exchange
To
Release To offspring Release originating
exchange
From
IDLE * originating IDLE * From offspring
exchange
To
- To offspring - originating
exchange
Relay_ Relay_
Internally Internally
Relay_
Information_
Externally
From From
Release originating Release destination
exchange exchange
To To
Release destination Release originating
exchange exchange
From From
IDLE * originating IDLE * destination
exchange exchange
To To
- destination - originating
exchange exchange
Relay_ Relay_
Externally Externally
Figure 76b: Process MSC_Coord (sheet 2)
3GPP
Release 1998 190 3GPP TS 03.18 V7.5.0 (2003-12)
Annex B (informative):
Change History
SPEC SMG# CR PHASE VERS NEW_VERS SUBJECT
03.18 s25 A019 R97 5.3.0 6.0.0 Network's Indication of Alerting
03.18 s26 A021 R97 6.0.0 6.1.0 Release by A party for forwarded calls and CAMEL
03.18 s27 A022r1 R97 6.1.0 6.2.0 Corrections and alignments for CAMEL Phase 2 &
CCBS
6.1.0 s27 A024 R97 6.1.0 6.2.0 Provide Subscriber Info for GPRS subscribers
03.18 s27 A026 R97 6.1.0 6.2.0 Optionality of support for OR of basic mobile-to-mobile
calls
03.18 s27 A027r1 R97 6.1.0 6.2.0 Suppression of alerting to originating MS in the case of
early ACM
03.18 s27 A029 R97 6.1.0 6.2.0 Correction of handling for failure case of CCBS OG call
handling
03.18 S28 A034 R97 6.2.0 6.3.0 Correction of the 03.18 SDLs for Reconnect case for
MTC
03.18 s28 A030r5 R98 6.3.0 7.0.0 Introduction of Mobile Number Portability
03.18 s28 A032r3 R98 6.3.0 7.0.0 Introduction of CD supplementary service
03.18 s28 A038r1 R98 6.3.0 7.0.0 Introduction of Mobile Number Portability
03.18 s28 A039 R98 6.3.0 7.0.0 Introduction of Work Item CLI Enhancements
03.18 s28 A040r1 R98 6.3.0 7.0.0 Introduction of new subscription option for Call
Forwarding services
03.18 S28 A041r5 R98 6.3.0 7.0.0 Introduction of UUS Service
03.18 S29 A048 R98 7.0.0 7.1.0 Notification of Call Forwarding to the gsmSCF
03.18 s30 A051 R98 7.1.0 7.2.0 Removal of TDP criteria from call handling
03.18 s30 A053r1 R98 7.1.0 7.2.0 GMSC CAMEL phases in Provide Roaming Number
03.18 s30 A054 R98 7.1.0 7.2.0 Separation of success & failure cases for OR of late
call forwarding
03.18 s30 A055 R98 7.1.0 7.2.0 Notification of call forwarding to the gsmSCF before
activating call forwarding process
03.18 CN#07 A058 R98 7.2.0 7.3.0 Correction of CF Notification
03.18 CN#09 A063r1 R98 7.3.0 7.4.0 Corection of procedure Obtain_Routeing_Address for
the reconnect case
7.3.0 7.4.0 Conversion to 3GPP layout
03.18 CN#22 A071 R98 7.4.0 7.5.0 MAP and CAP 3G SAI mapping to 2G CellIDorLAI
Location Information parameter
3GPP

3GPP TS 03.18

Uploaded by

Copyright:

Available Formats

You might also like

3GPP TS 03.18

Uploaded by

Document Information

Original Description:

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 03.18

Uploaded by

Copyright:

Available Formats

3rd Generation Partnership Project;

Technical Specification Group Core Network;

GLOBAL SYSTEM FOR

3GPP support office address

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

© 2004, 3GPP Organizational Partners (ARIB, CCSA, ETSI, T1, TTA,TTC).

7.1.2 Functional requirements of VLR.......................................................................................................................46

7.3.2.3 Procedure Search_For_MS_VLR....................................................................................................................155

8.4 Messages on the F interface (MSC-EIR)..............................................................................................................184

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

7 GSM Phase 2+ Release 1998;

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

 For a non-specific reference, the latest version applies.

[1] GSM 02.01: "Digital cellular telecommunications system (Phase 2+); Principles of

[8] GSM 03.78 (TS 101 044): "Digital cellular telecommunications system (Phase 2+); Customized

[10] GSM 03.79 (TS 101 045): "Digital cellular telecommunications system (Phase 2+); Support of

[28] ITU-T Recommendation Q.850 (1996): "Usage of cause and location in the Digital Subscriber

3 Definitions and abbreviations

A subscriber: calling mobile subscriber.

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

A&O Active & Operative

SIFOC Send Information For Outgoing Call

4.1 Architecture for an MO call

Radio I/F signalling '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

Set cipher mode

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 MT

GMSC HLRB VLRB VMSCB

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 (GSM 03.72)

6.2 Line identification services (GSM 03.81)

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 (GSM 03.82)

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 (GSM 03.83)

6.5 Call hold (GSM 03.83)

6.6 Multiparty (GSM 03.84)

6.7 Closed user group (GSM 03.85)

6.8 Advice of charge (GSM 03.86)