Basic Call Handling GSM 03.18

Page 1 GSM 03.18 Version 2.1.
0: February 1997
GSM TECHNICAL SPECIFICATION

Source: ETSI TC-SMG ICS: 33.020
GSM 03.18
February 1997 Version 2.1.0
Reference: TS/SMG-0xxxxxQ
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2+); Basic call handling Technical Realisation (GSM 03.18)
ETSI
European Telecommunications Standards Institute ETSI Secretariat Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
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. European Telecommunications Standards Institute 1997. All rights reserved.
Page 2 GSM 03.18 Version 2.1.0: February 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to "ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3 GSM 03.18 Version 2.1.0: February 1997 Blank page
Contents
Foreword ....................................................................................................................................................... 8 1 Scope ....................................................................................................................................................... 10 2 Normative references............................................................................................................................... 10 3 Definitions, symbols and abbreviations.................................................................................................... 11 3.1 Definitions ................................................................................................................................... 11 3.2 Abbreviations .............................................................................................................................. 12 4 Architecture.............................................................................................................................................. 13 4.1 Architecture for an MO call ......................................................................................................... 13 4.2 Architecture for an MT call.......................................................................................................... 14 5 Information flows...................................................................................................................................... 15 5.1 Information flow for an MO call................................................................................................... 15 5.2 Information flow for retrieval of routeing information for an MT call ........................................... 17 5.3 Information flow for an MT call ................................................................................................... 18 6 Principles for interactions with supplementary services........................................................................... 20 6.1 Line identification services (GSM 03.81) .................................................................................... 20 6.1.1 Calling Line Identification Presentation (CLIP)......................................................... 20 6.1.2 Calling Line Identification Restriction (CLIR)............................................................ 20 6.1.3 Connected Line Identification Presentation (COLP)................................................. 20 6.1.4 Connected Line Identification Restriction (COLR) ................................................... 20 6.2 Call forwarding services (GSM 03.82) ........................................................................................ 20 6.2.1 Call Forwarding Unconditional (CFU)....................................................................... 20 6.2.2 Call Forwarding on mobile subscriber Busy (CFB) .................................................. 20 6.2.3 Call Forwarding on No Reply (CFNRy) .................................................................... 20 6.2.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc).............................. 20 6.3 Call wait (GSM 03.83)................................................................................................................. 21 6.4 Call hold (GSM 03.83) ................................................................................................................ 21 6.5 Multiparty (GSM 03.84)............................................................................................................... 21 6.6 Closed user group (GSM 03.85)................................................................................................. 21 6.7 Advice of charge (GSM 03.86) ................................................................................................... 21 6.8 Call barring (GSM 03.88)............................................................................................................ 21 6.8.1 Barring of outgoing calls........................................................................................... 21 6.8.2 Barring of incoming calls .......................................................................................... 21 6.9 Explicit Call Transfer (GSM 03.91) ............................................................................................. 21 7 Functional requirements of network entities ............................................................................................ 22 7.1 MO call........................................................................................................................................ 22 7.1.1 Functional requirements of serving MSC ................................................................. 22 7.1.1.1 Process OCH_MSC.......................................................................... 22 7.1.1.2 Procedure Process_Access_Request_MSC .................................... 22 7.1.1.3 Procedure Set_CLI_Presentation_Indicator_MSC ........................... 23 7.1.1.4 Procedure Set_COLP_Info_MSC ..................................................... 23 7.1.1.5 Procedure Handle_AoC_MO_MSC .................................................. 23 7.1.1.6 Procedure Obtain_IMSI_MSC .......................................................... 23 7.1.1.7 Procedure Authenticate_MSC .......................................................... 23 7.1.1.8 Procedure Obtain_IMEI_MSC .......................................................... 23 7.1.1.9 Procedure Check_IMEI_MSC........................................................... 23 7.1.2 Functional requirements of VLR............................................................................... 38 7.1.2.1 Process OCH_VLR........................................................................... 38 7.1.2.2 Procedure Process_Access_Request_VLR ..................................... 38 7.1.2.3 Procedure Check_BAOC.................................................................. 38 7.1.2.4 Procedure OG_CUG_Check ............................................................ 38
Page 5 GSM 03.18 Version 2.1.0: February 1997 7.1.2.5 Procedure Check_OG_Barring .........................................................38 7.1.2.6 Procedure Get_LI_Subscription_Info_MO_VLR ...............................38 7.1.2.7 Procedure Get_AoC_Subscription_Info_VLR ...................................38 7.1.2.8 Procedure Obtain_Identity_VLR........................................................38 7.1.2.9 Procedure Obtain_IMSI_VLR............................................................38 7.1.2.10 Procedure Authenticate_VLR..........................................................38 7.1.2.11 Procedure Obtain_Authentication_Sets_VLR .................................39 7.1.2.12 Procedure Start_Tracing_VLR ........................................................39 7.1.2.13 Procedure Check_IMEI _VLR .........................................................39 7.1.2.14 Procedure Obtain_IMEI _VLR.........................................................39 7.1.2.15 Process Fetch_Authentication_Sets_VLR ......................................39 7.2 Retrieval of routeing information for MT call ...............................................................................64 7.2.1 Functional requirements of GMSC ...........................................................................64 7.2.1.1 Process MT_GMSC ..........................................................................64 7.2.1.2 Procedure Handle_COLP_Forwarding_Interaction_MSC.................64 7.2.2 Functional requirements of HLR ...............................................................................69 7.2.2.1 Process SRI_HLR .............................................................................69 7.2.2.2 Procedure Check_Parameters..........................................................69 7.2.2.3 Procedure Subscription_Check_HLR................................................69 7.2.2.4 Procedure First_Forwarding_HLR.....................................................69 7.2.2.5 Procedure PRN_Error_HLR ..............................................................69 7.2.2.6 Procedure Forward_CUG_Check .....................................................69 7.2.2.7 Procedure Derive_Requested_Basic_Service_HLR .........................69 7.2.2.8 Procedure Check_IC_Barring ...........................................................69 7.2.2.9 Procedure IC_CUG_Check ...............................................................69 7.2.2.10 Procedure Handle_CFU ..................................................................69 7.2.2.11 Procedure Handle_CFNRc..............................................................69 7.2.3 Functional requirements of VLR ...............................................................................83 7.2.3.1 Process PRN_VLR............................................................................83 7.2.3.2 Process Restore_Subscriber_Data_VLR ..........................................83 7.2.3.3 Process PSI_VLR..............................................................................83 7.2.4 Functional requirements of MSC ..............................................................................90 7.2.4.1 Process OSI_MSC ............................................................................90 7.3 MT call.........................................................................................................................................92 7.3.1 Functional requirements of serving MSC..................................................................92 7.3.1.1 Process ICH_MSC ............................................................................92 7.3.1.2 Procedure Page_MS_MSC ...............................................................92 7.3.1.3 Procedure Search_For_MS_MSC.....................................................93 7.3.1.4 Procedure Complete_Call_In_MSC ..................................................93 7.3.1.5 Procedure Process_Call_Waiting_MSC ...........................................93 7.3.1.6 Procedure Set_CLIP_Info_MSC .......................................................93 7.3.1.7 Procedure Derive_GSM_BC_MSC ...................................................93 7.3.1.8 Procedure Handle_AoC_MT_MSC ...................................................93 7.3.1.9 Procedure Set_COL_Presentation_Indicator_MSC ..........................93 7.3.2 Functional requirements of VLR .............................................................................114 7.3.2.1 Process ICH_VLR ...........................................................................114 7.3.2.2 Procedure Derive_Requested_Basic_Service_VLR .......................114 7.3.2.3 Procedure Search_For_MS_VLR....................................................114 7.3.2.4 Procedure Get_CW_Subscription_Info_VLR ..................................114 7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR ..............................114 7.3.2.6 Procedure Handle_CFB ..................................................................114 7.3.2.7 Procedure Handle_CFNRy..............................................................114 8 Contents of messages............................................................................................................................127 8.1 Messages on the B interface (MSC-VLR) .................................................................................127 8.1.1 Abort 127 8.1.2 Authenticate ............................................................................................................127 8.1.3 Authenticate ack .....................................................................................................127 8.1.4 Check IMEI .............................................................................................................127 8.1.5 Check IMEI ack.......................................................................................................127 8.1.6 Check IMEI negative response ...............................................................................127 8.1.7 Complete Call .........................................................................................................128 8.1.8 Complete Call ack...................................................................................................130
Page 6 GSM 03.18 Version 2.1.0: February 1997 8.1.9 Complete Call negative response .......................................................................... 130 8.1.10 Forward New TMSI .............................................................................................. 130 8.1.11 Forward New TMSI ack........................................................................................ 130 8.1.12 Forward New TMSI negative response ................................................................ 130 8.1.13 Obtain Subscriber Info.......................................................................................... 130 8.1.14 Obtain Subscriber Info ack ................................................................................... 130 8.1.15 Page MS............................................................................................................... 130 8.1.16 Page MS negative response ................................................................................ 131 8.1.17 Process Access Request ..................................................................................... 131 8.1.18 Process Access Request ack............................................................................... 131 8.1.19 Process Access Request negative response....................................................... 132 8.1.20 Process Call Waiting ............................................................................................ 132 8.1.21 Process Call Waiting ack ..................................................................................... 132 8.1.22 Process Call Waiting negative response.............................................................. 132 8.1.23 Provide IMEI......................................................................................................... 132 8.1.24 Provide IMEI ack .................................................................................................. 132 8.1.25 Provide IMSI......................................................................................................... 133 8.1.26 Provide IMSI ack .................................................................................................. 133 8.1.27 Search For MS ..................................................................................................... 133 8.1.28 Search For MS ack .............................................................................................. 133 8.1.29 Search For MS negative response....................................................................... 133 8.1.30 Send Info For Incoming Call................................................................................. 133 8.1.31 Send Info For Incoming Call ack .......................................................................... 134 8.1.32 Send Info For Incoming Call negative response .................................................. 134 8.1.33 Send Info For Outgoing Call................................................................................. 135 8.1.34 Send Info For Outgoing Call negative response .................................................. 135 8.1.35 Set ciphering mode .............................................................................................. 135 8.1.36 Trace subscriber activity....................................................................................... 135 8.1.37 Use existing TMSI ................................................................................................ 135 8.2 Messages on the C interface (MSC-HLR) ................................................................................ 136 8.2.1 Send Routeing Info................................................................................................. 136 8.2.2 Send Routeing Info ack .......................................................................................... 136 8.2.3 Send Routeing Info negative response .................................................................. 136 8.3 Messages on the D interface (VLR-HLR) ................................................................................. 137 8.3.1 Provide Roaming Number ...................................................................................... 137 8.3.2 Provide Roaming Number ack ............................................................................... 137 8.3.3 Provide Roaming Number negative response ....................................................... 137 8.3.4 Provide Subscriber Info .......................................................................................... 138 8.3.5 Provide Subscriber Info ack ................................................................................... 138 8.3.5.1 Location information ....................................................................... 138 8.3.8 Provide Subscriber Info negative response............................................................ 139 8.3.6 Restore Data .......................................................................................................... 139 8.3.7 Restore Data ack ................................................................................................... 139 8.3.8 Restore Data negative response............................................................................ 139 8.3.9 Provide Subscriber Info negative response............................................................ 139 8.4 Messages on the F interface (MSC-EIR).................................................................................. 139 8.4.1 Check IMEI............................................................................................................. 139 8.4.2 Check IMEI ack ...................................................................................................... 139 8.4.3 Check IMEI negative response .............................................................................. 139 Annex A (Informative) Handling of an IAM at an MSC.............................................................................. 141 History ....................................................................................................................................................... 144
Foreword
This ETSI GSM Technical Specification has been produced by the TC SMG Technical Committee of the European Telecommunications Standards Institute (ETSI).
Scope
This standard 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 setup (OACSU) are not described in this specification. The details of the effects of GSM supplementary services on the handling of a call are described in the relevant 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 [5] and optimal routeing [6]. The use of the Provide Subscriber Information message flow is shown in [5] and [6]. The logical separation of the MSC and VLR (shown in clauses 4, 5 & 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 ([14], [16] & [17]), the stage 3 specification shall prevail.
2
[1]
Normative references
ETS 300 500 (1994): " European digital cellular telecommunications system (Phase 2); Principles of telecommunication services supported by a GSM Public Land Mobile Network (PLMN) (GSM 02.01). ETS 300 523 (1994): " European digital cellular telecommunications system (Phase 2); Numbering, addressing & identification (GSM 03.03). ETS 300 534 (1994): " European digital cellular telecommunications system (Phase 2); Security related network functions (GSM 03.20). GSM 03.32: " Digital cellular telecommunications system (Phase 2+); Universal Geographical Area Description (GAD) (GSM 03.32). GSM 03.78: Digital cellular telecommunications system (phase 2+); Customised Applications for Mobile network Enhanced Logic (CAMEL) (GSM 03.78) GSM 03.79: European digital cellular telecommunications system (Phase 2+); Support of Optimal Routeing (SOR) Technical Realisation (GSM 03.79) ETS 300 542 (1994): " European digital cellular telecommunications system (Phase 2); Line identification supplementary services - Stage 2 (GSM 03.81). ETS 300 543 (1994): European digital cellular telecommunications system (Phase 2); Call Forwarding (CF) supplementary services - Stage 2 (GSM 03.82). ETS 300 544 (1994): European digital cellular telecommunications system (phase 2); Call Waiting (CW) and Call Hold (HOLD) supplementary services Stage 2 (GSM 03.83). ETS 300 545 (1994): European digital cellular telecommunications system (phase 2); Multi Party (MPTY) supplementary services - Stage 2 (GSM 03.84). ETS 300 546 (1994): European digital cellular telecommunications system (phase 2); Closed User Group (CUG) supplementary services - Stage 2 (GSM 03.85).
[2]
[3]
[4]
[5]
[6]
[7]
[8]
[9]
[10]
[11]
Page 11 GSM 03.18 Version 2.1.0: February 1997 [12] ETS 300 547 (1994): European digital cellular telecommunications system (phase 2); Advice of Charge (AoC) supplementary services - Stage 2 (GSM 03.86). ETS 300 548 (1994): European digital cellular telecommunications system (Phase 2); Call Barring (CB) supplementary services - Stage 2 (GSM 03.88) ETS 300 557 (1995): European digital cellular telecommunications system (Phase 2); Mobile radio interface layer 3 specification (GSM 04.08) ETS 300 582 (1994): European digital cellular telecommunications system (Phase 2); General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) (GSM 07.01) ETS 300 590 (1995): European digital cellular telecommunications system (Phase 2); Mobile-services Switching Centre - Base Station System (MSC BSS) interface Layer 3 specification (GSM 08.08) ETS 300 599 Fourth Edition (1996): European digital cellular telecommunications system (Phase 2); Mobile Application Part (MAP) specification (GSM 09.02) ETS 300 604 (1994): European 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) (GSM 09.07) ETS 300 607 (1994): European 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) ETS 300 627 (1996): European digital cellular telecommunications system (Phase 2); Subscriber and equipment trace (GSM 12.08) 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 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
[13]
[14]
[15]
[16]
[17]
[18]
[19]
[20]
[21]
[22]
3
3.1
Definitions, symbols and abbreviations

Definitions
A subscriber: The calling mobile subscriber. B subscriber: The mobile subscriber originally called by the A subscriber. C subscriber: The subscriber to whom the B subscriber has requested that calls be forwarded. The C subscriber may be fixed or mobile. Location Information: Information to define the whereabouts of the MS, and the age of the information defining the whereabouts.
Page 12 GSM 03.18 Version 2.1.0: February 1997 3.2 Abbreviations Active & Operative Address Complete Message ANswer Message Advice of Charge Bearer Capability Barring of Outgoing International Calls except those directed to the HPLMN Country & Barring of Outgoing InterZonal Calls Barring of Outgoing InterZonal Calls Barring of Outgoing InterZonal Calls except those directed to the HPLMN Country Call Forwarding on Busy Call Forwarding on mobile subscriber Not Reachable Call Forwarding on No Reply Call Forwarding Unconditional Calling Line Identity Presentation Calling Line Identity Restriction COnnected Line identity Presentation COnnected Line identity Restriction Closed User Group Call Waiting Forwarded-To Number Forwarded-To NetWork Gateway MSC of the B subscriber Higher Layer Compatibility The HLR of the B subscriber The HPLMN of the B subscriber Initial Address Message Interrogating PLMN - the PLMN containing GMSCB Lower Layer Compatibility Mobile Originated MultiParTY Mobile Terminated Network Determined User Busy No Reply Call Timer Provide Roaming Number Send Information For Incoming Call Send Information For Outgoing Call Send Routeing Information User Determined User Busy The VLR of the A subscriber The VLR of the B subscriber The Visited MSC of the A subscriber The Visited MSC of the B subscriber The Visited PLMN of the A subscriber The Visited PLMN of the B subscriber
A&O ACM ANM AoC BC BOIC-exHC&BOIZC BOIZC BOIZC-exHC CFB CFNRc CFNRy CFU CLIP CLIR COLP COLR CUG CW FTN FTNW GMSCB HLC HLRB HPLMNB IAM IPLMN LLC MO MPTY MT NDUB NRCT PRN SIFIC SIFOC SRI UDUB VLRA VLRB VMSCA VMSCB VPLMNA VPLMNB
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.
Air I/F signalling BSSA MS
'A' I/F signalling VMSCA
IAM (ISUP)
SIFOC/ack
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 air 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 SIFOC ack. 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.
Page 14 GSM 03.18 Version 2.1.0: February 1997 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. 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.
IAM (ISUP)
IPLMN GMSCB
IAM (ISUP)
'A' I/F signalling VMSCB SIFIC Page/ack Complete call VLRB VPLMNB BSSB
Air I/F signalling
MS
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 air 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
5.1
Information flows
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 air 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.
MSA CM service req
BSSA CM service req
VMSCA
VLRA
Process access req Authenticate (note 1)
Authenticate Authenticate Authenticate resp Authenticate ack
Authenticate ack Authenticate accept Set cipher mode (note 2) Start ciphering (note 3) Process access req ack
Cipher mode cmd (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
Page 16 GSM 03.18 Version 2.1.0: February 1997 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. Ciphering may be initiated at any stage after authentication; its position in this message flow diagram is an example. 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. 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.
NOTE 2:
NOTE 3:
NOTE 4:
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 [3]. VLRA may also initiate ciphering at this stage, as described in [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 [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 Setup message containing the B subscriber address via BSSA to VMSCA. MSA also uses the Setup 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 air 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.
Page 17 GSM 03.18 Version 2.1.0: February 1997 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.
IAM
GMSCB SRI
HLRB PRN PRN ack SRI ack IAM
VLRB
VMSCB
Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call When GMSCB receives an IAM, it analyses the called party address. If GMSCB can derive an HLR address from the B party address, it sends a request for routeing information (SRI) to HLRB. 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.
Page 18 GSM 03.18 Version 2.1.0: February 1997 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 air interface between VMSCB or BSSB and MSB is shown by dotted lines.
GMSCB IAM
VLRB
VMSCB
BSSB
MSB
SIFIC Page MS Page Page Chan req Imm ass Page resp Process access req Set cipher mode (note 1) Process access req ack Start ciphering (note 2) MS conn estab
Cipher mode command Cipher mode complete
Complete call Setup
Call conf Allocate channel
Assignment command Assignment
Allocation complete ACM
complete Alerting 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.
Page 19 GSM 03.18 Version 2.1.0: February 1997 NOTE 2: If ciphering is not required, the MSC may send a start ciphering request indicating that no ciphering is required. 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. 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.
NOTE 3:
NOTE 4:
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 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 [3]. VLRB may also initiate ciphering at this stage, as described in [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 Setup message towards MSB. The Setup message may include bearer capability information for the call. When MSB receives the Setup 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.
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 6.1.1 Line identification services (GSM 03.81) Calling Line Identification Presentation (CLIP)
The basic call handling processes ICH_VLR and ICH_MSC interact with the processes CLIP_MAF001 and CLIP_MAF002 [7] as described in subclauses 7.3.2 and 7.3.1. 6.1.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 [7] as described in subclauses 7.1.1 and 7.1.2. 6.1.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 [7] 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 [7] as described in subclauses 7.2.1 and 7.3.1. 6.1.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 [7] as described in subclauses 7.3.2 and 7.3.1. 6.2 6.2.1 Call forwarding services (GSM 03.82) Call Forwarding Unconditional (CFU)
The basic call handling process SRI_HLR interacts with the process MAF007 [8] as described in subclause 7.2.2 6.2.2 Call Forwarding on mobile subscriber Busy (CFB)
The basic call handling process ICH_VLR interacts with the process MAF008 [8] as described in subclause 7.3.2 6.2.3 Call Forwarding on No Reply (CFNRy)
The basic call handling process ICH_VLR interacts with the process MAF009 [8] as described in subclause 7.3.2 6.2.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc)
The basic call handling processes SRI_HLR and ICH_VLR interact with the process MAF010 [8] as described in subclauses 7.2.2 and 7.3.2
Page 21 GSM 03.18 Version 2.1.0: February 1997 6.3 Call wait (GSM 03.83)
The basic call handling process ICH_VLR interacts with the process MAF013 [9] as described in subclause 7.3.2. Further details of the handling of call waiting are given in subclauses 7.3.1 & 7.3.2. 6.4 Call hold (GSM 03.83)
Invocation of call hold before a basic call has been established will be rejected. 6.5 Multiparty (GSM 03.84)
Invocation of multiparty before a basic call has been established will be rejected. 6.6 Closed user group (GSM 03.85)
The basic call handling process OCH_VLR interacts with the process CUG_MAF014 [11] as described in subclause 7.1.2. The basic call handling process SRI_HLR interacts with the process CUG_MAF015 [11] as described in subclause 7.2.2. The interactions between call forwarding and CUG [11] are handled as described in subclause 7.2.2.6. 6.7 Advice of charge (GSM 03.86)
The interactions between Advice of Charge [12] and MO calls are handled as described in subclauses 7.1.1 and 7.1.2. The interactions between Advice of Charge [12] and MT calls are handled as described in subclauses 7.3.1 and 7.3.2. 6.8 6.8.1 Call barring (GSM 03.88) Barring of outgoing calls
The basic call handling process OCH_VLR interacts with the processes MAF017, MAF018 and MAF020 [13] as described in subclause 7.1.2. 6.8.2 Barring of incoming calls
The basic call handling process SRI_HLR interacts with the processes MAF022 and MAF023 [13] as described in subclause 7.2.2. 6.9 Explicit Call Transfer (GSM 03.91) Explicit Call Transfer and the basic call handling described in this
There is no interaction between specification.
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 [16], for interworking with the BSS and DTAP, which is specified in [14], for interworking with the MS. The protocol used over the C, D & F interfaces is MAP, which is specified in [17]. For the purposes of this specification, the protocol used over telephony signalling interfaces is ISUP, which is specified in [21]; 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. 7.1 7.1.1 7.1.1.1 MO call Functional requirements of serving MSC Process OCH_MSC
Sheet 1: the MSC converts the GSM bearer capability negotiated between the MSC and the MS to a GSM basic service according to the rules defined in [15]. Sheet 2, sheet 4: at any stage after the Setup has been received, the MS may terminate the transaction with the network by sending a Release transaction request. 7.1.1.2 Procedure Process_Access_Request_MSC
Sheet 1, sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC, the MSC 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 MSC maps the negative response received on the B interface to the appropriate reject cause according to the rules defined in [19].
Page 23 GSM 03.18 Version 2.1.0: February 1997 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 MSC receives a Setup 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 Set_CLI_Presentation_Indicator_MSC
The MS may terminate the transaction with the network by sending a Release transactionmessage while a response is awaited from the process CLIR_MAF004. The message is saved for processing after return from the procedure. 7.1.1.4 Procedure Set_COLP_Info_MSC
The MS may terminate the transaction with the network by sending a Release transactionmessage while a response is awaited from the process COLP_MAF006. The message is saved for processing after return from the procedure. 7.1.1.5 Procedure Handle_AoC_MO_MSC
The charging parameters and the Boolean variable Acknowledgment required are global data which can be read by the parent process. 7.1.1.6 Procedure Obtain_IMSI_MSC
The MS may terminate the transaction with the network while the MSC 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 MSC aborts the transaction with the VLR and returns an aborted result to the parent process. 7.1.1.7 Procedure Authenticate_MSC
The MS may terminate the transaction with the network while the MSC 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 MSC aborts the transaction with the VLR and returns an aborted result to the parent process. 7.1.1.8 Procedure Obtain_IMEI_MSC
The MS may terminate the transaction with the network while the MSC is waiting for the MS to return its IMEI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The MSC aborts the transaction with the VLR and returns an aborted result to the parent process. 7.1.1.9 Procedure Check_IMEI_MSC
The MS may terminate the transaction with the network while the MSC is waiting for the MS to return its IMEI. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The MSC aborts the transaction with the VLR and returns an aborted result to the parent process. The MS may terminate the transaction with the network while the MSC is waiting for the result of the IMEI check from the EIR. If a CC connection has not been established, the MS uses CM Service Abort; otherwise it uses a Release, Release Complete or Disconnect. The MSC aborts the transaction with the VLR and returns an aborted result to the parent process.

Process OCH_MSC
Process in the MSC to handle an outgoing call request
OCH_MSC1(4)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR.
Idle
CM service request
Process_ Access_ Request_MSC
No Result= Pass? Yes
Wait_For_ Setup
Setup
CM Service Abort
Convert GSM BC to basic service
Send Info For Outgoing Call
Release call resources
Wait_For_ MO_Call_ Result
Idle
Figure 6a: Process OCH_MSC (sheet 1)

Process OCH_MSC
Process in the MSC to handle an outgoing call request Wait_For_ MO_Call_ Result
OCH_MSC2(4)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise
Release transaction
Complete Call
Send Info For Outgoing Call negative response
Abort
Convert GSM BC to channel requirement
Release transaction
Release Call Resources
Call Proceeding
Idle
Allocate channel
Idle
Wait_For_ Allocation_ Complete
Release transaction
Allocation failure
Allocation complete
Set_CLI_ Presentation_ Indicator_ MSC
No Result= call allowed?
Yes
Release transaction
Initial Address
Towards destination exchange
Idle
Wait_For_ ACM
Figure 6b: Process OCH_MSC (sheet 2)

Process OCH_MSC
Wait_For_ ACM Process in the MSC to handle an outgoing call request
OCH_MSC3(4)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange.
Address Complete
Connect
Alert
Wait_For_ ANM
Answer
Set_COLP_ Info_MSC
Wait_For_ AoC_Ack
Handle_AoC_ MO_MSC
Charging Parameters ack
Release transaction
Connect Ack
AoC acknowledgment timer expired
Connect
Release transaction
No Acknowledgment required? Yes
Wait_For_ Connect_Ack
Release
Start AoC acknowledgment timer
Connect Ack
Wait_For_ AoC_Ack
Wait_For_ Clear
Idle
Figure 6c: Process OCH_MSC (sheet 3)

Process OCH_MSC
Process in the MSC to handle an outgoing call request
OCH_MSC4(4)
Wait_For_ACM, Wait_For_ANM, Wait_For_Connect_Ack, Wait_For_Clear
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange
Release transaction
Release
From destination exchange
Release
Release transaction
Idle
Figure 6d: Process OCH_MSC (sheet 4)

Procedure Process_Access_Request_MSC
Procedure in the MSC to handle a request from the MS for system access
PAR_MSC1(3)
Process Access Request
Wait_For_ PAR_Result
Provide IMSI
Authenticate
Trace Subscriber Activity
Obtain_IMSI_ MSC
Authenticate_ MSC
Tracing Active:= TRUE
Result:= Fail
Result:= Fail
CM service abort
Set Ciphering Mode
Ciphering Required:= TRUE
Abort
Result:= Fail
Figure 7a: Procedure Process_Access_Request_MSC (sheet 1)

Procedure in the MSC to handle a request from the MS for system access Wait_For_ PAR_Result Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR.
PAR_MSC2(3)
Abort
Process Access Request negative response
Process Access Request ack
No CM Service type= Page Response? No Ciphering required? Yes
Map negative response to reject cause
Yes CM Service type= Page Response? No
Release transaction
CM Service Reject
Result:= Fail
Start ciphering
CM Service Accept
Wait_For_ TMSI_ Reallocation
CM service abort
Provide IMEI
Setup
Check IMEI
Abort
Forward New TMSI
Use Existing TMSI
Obtain_IMEI_ MSC
Check_IMEI_ MSC
Map negative response to reject cause
No Abort Result= Pass? Yes
No Result= Pass? Yes CM Service Reject Reallocate TMSI
Result:= Fail
Result:= Fail
Result:= Fail
Result:= Pass
Wait_For_ TMSI_Ack
Figure 7b: Procedure Process_Access_Request_MSC (sheet 2)

Procedure in the MSC to handle a request from the MS for system access Wait_For_ TMSI_Ack
PAR_MSC3(3)
CM service abort
Setup
Abort
TMSI Reallocation Failure
TMSI Reallocation Complete
Abort
Forward New TMSI negative response
Forward New TMSI ack
Result:= Fail
Result:= Fail
Result:= Pass
Figure 7c: Procedure Process_Access_Request_MSC (sheet 3)

Procedure Set_CLI_Presentation_Indicator_MSC
Procedure in the MSC to determine the CLI presentation indicator value
CAIND_M1(1)
Signals to/from the right are to/from the process CLIR_MAF004
Initiate handling of CLIR
Wait_For_ CLIR_Info
Release transaction
From BSS
Clear call
Continue call handling
Result:= Call not allowed
Result:= Call allowed
Figure 8: Procedure Set_CLI_Presentation_Indicator_MSC

Procedure Set_COLP_Info_MSC
Procedure in the MSC to determine the COLP information to be sent to the MS
COINF_M1(1)
Signals to/from the right are to/from the process COLP_MAF006
Initiate handling of COLP
Wait_For_ COLP_Info
Release transaction
From BSS
Release
Figure 9: Procedure Set_COLP_Info_MSC

Procedure Handle_AoC_MO_MSC
Procedure in the MSC to handle AoC signalling towards the MS for an MO call
AoCMO_M1(1)
Yes AoC(I) provisioned? No Set charging parameters
No AoC(C) provisioned? Yes
Set charging parameters
Acknowledgment required:= False
Acknowledgment required:= True
Figure 10: Procedure Handle_AoC_MO_MSC

Procedure Obtain_IMSI_MSC
Procedure in the MSC to obtain the IMSI from the MS and relay it to the VLR
OIMSI_M1(1)
Signals to/from the left are to/from the BSS; Signals to/from the right are to/from the VLR
Send IMSI
Wait_For_ IMSI
Send IMSI ack
Release transaction
Send IMSI negative response
Release transaction
Provide IMSI ack
Abort
Result:= Pass
Result:= Aborted
Figure 11: Procedure Obtain_IMSI_MSC

Procedure Authenticate_MSC
Procedure in the MSC to obtain the IMSI from the MS and relay it to the VLR
AUT_MSC1(1)
Authenticate
Wait_For_ Auth_Response
Authenticate ack
Release transaction
Authenticate negative response
Release transaction
Authenticate ack
Abort
Wait_For_ Auth_Result
Result:= Aborted
Authentication accepted
Authentication rejected
Result:= Pass
Figure 12: Procedure Authenticate_MSC

Procedure Obtain_IMEI_MSC
Procedure in the MSC to obtain the IMEI from the MS and relay it to the VLR
OIMEI_M1(1)
Send IMEI
Wait_For_ IMEI
Send IMEI ack
Release transaction
Send IMEI negative response
Release transaction
Provide IMEI ack
Abort
Result:= Pass
Result:= Aborted
Figure 13: Procedure Obtain_IMEI_MSC

Procedure Check_IMEI_MSC
Procedure in the MSC to check the IMEI and relay the result to the VLR
CIMEI_M1(1)
Yes Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise. IMEI available? No
Send IMEI
Wait_For_ IMEI
CM service abort
Send IMEI negative response
Send IMEI ack
Release transaction
Check IMEI
To EIR
Abort
Wait_for_ Check_IMEI_ Result
Result:= Aborted
Release transaction
Check IMEI negative response
From EIR
Check IMEI ack
From EIR
Abort
Check IMEI ack
Result:= Aborted
Result:= Pass
Figure 14: Procedure Check_IMEI_MSC
Page 38 GSM 03.18 Version 2.1.0: February 1997 7.1.2 7.1.2.1 Functional requirements of VLR Process OCH_VLR
Sheet 2: 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 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.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 [17]. 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 5: it is a network operator decision whether emergency calls are allowed from an ME with no SIM. 7.1.2.3 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.4 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.5 Procedure Check_OG_Barring
Sheet 2: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF018 or MAF019, the message is saved for handling after return from the procedure. 7.1.2.6 Procedure Get_LI_Subscription_Info_MO_VLR
If the VLR receives an Abort message from the MSC while it is awaiting a response from the process CLIR_MAF0003 or CLIR_MAF005, the message is saved for handling after return from the procedure. 7.1.2.7 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.8 Procedure Obtain_Identity_VLR
It is a network operator decision whether open (unciphered) identification of the MS by its IMSI is allowed. 7.1.2.9 7.1.2.10 Procedure Obtain_IMSI_VLR 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.
Page 39 GSM 03.18 Version 2.1.0: February 1997 7.1.2.11 7.1.2.12 7.1.2.13 Procedure Obtain_Authentication_Sets_VLR Procedure Start_Tracing_VLR 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. Procedure Obtain_IMEI _VLR Process Fetch_Authentication_Sets_VLR
7.1.2.14 7.1.2.15

Process OCH_VLR
Process in the VLR to handle an outgoing (MO) call setup request
OCH_VLR1(2)
Signals to/from the left are to/from the MSC. Idle
Process_ Access_ Request_VLR
No Result= Pass Yes
Wait_For_ SIFOC
Idle
Figure 15a: Process OCH_VLR (sheet 1)

Process OCH_VLR
Process in the VLR to handle an outgoing (MO) call setup request Wait_For_ SIFOC
OCH_VLR2(2)
Signals to/from the left are to/from the MSC.
Send Info For Outgoing Call
Abort
Yes Emergency call? No Basic service provisioned? Yes Set negative response: Basic service not provisioned No Idle
Check_ BAOC
Bearer service or teleservice
Yes Call barred? No Set negative response: Call barred
OG_CUG_ Check
No Call allowed? Yes Set negative response: CUG reject
Check_OG_ Barring
Yes Call barred? No Get_LI_ Subscription_ Info_MO_VLR Set negative response: Call barred
Get_AoC_ Subscription_ Info_VLR
Complete Call
Idle
Idle
Figure 15b: Process OCH_VLR (sheet 2)

Procedure Process_Access_Request_VLR
Procedure in the VLR to handle a request from the MS for system access
PAR_VLR1(5)
No Identity known? Yes
Obtain_ Identity_VLR
Yes Result= Pass? No
Yes Identity= IMEI? No Yes No 6 Authentication required? Yes Result= Fail?
No
Authenticate_ VLR
IMSI detached:= False
Confirmed by Radio Contact:= True
Set negative response: System Failure
Set negative response: Unidentified Subscriber
Result:= Aborted
Figure 16a: Procedure Process_Access_Request_VLR (sheet 1)

Procedure in the VLR to handle a request from the MS for system access 1
PAR_VLR2(5)
True
Location info confirmed in HLR False
Update_ Location_VLR
No
Mobile Not Reachable Flag set? Yes
Subscriber_ 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
Figure 16b: Procedure Process_Access_Request_VLR (sheet 2)

Procedure in the VLR to handle a request from the MS for system access 4 5
PAR_VLR3(5)
Signals to the left are to the MSC.
Set Ciphering Mode
Identity:= IMSI
No IMEI check required? Yes
Check_ IMEI_VLR
TMSI reallocation required? Yes
No Result= Fail? Yes
No
Forward New TMSI
Use Existing TMSI
IMSI detached:= True
Freeze existing TMSI
Result:= Pass
Set negative response: Illegal Equipment
Result:= Aborted
Wait_For_ TMSI_Ack
Figure 16c: Procedure Process_Access_Request_VLR (sheet 3)

Procedure in the VLR to handle a request from the MS for system access
PAR_VLR4(5)
Signals from the left are from the MSC.
Wait_For_ TMSI_Ack
Yes Result= Aborted? No Result:= Aborted Result= Procedure Error? No Yes Unfreeze existing TMSI Forward New TMSI ack Forward New TMSI negative response
Set negative response: System Failure Yes
Result= Unknown Subscriber? No
Result:= Pass
Result= Unidentified Subscriber? No
Yes
Set negative response: Unidentified Subscriber
Set negative response: Illegal Subscriber
Figure 16d: Procedure Process_Access_Request_VLR (sheet 4)

Procedure in the VLR to handle a request from the MS for system access 3
PAR_VLR5(5)
Signals to the left are to the MSC. CM service type =Emergency call? Yes
No
Emergency call setup allowed without SIM? No Yes No IMEI required? Yes
Obtain_ IMEI_VLR
Yes Identity:= IMEI Result= Fail? No
Process Access Request negative response
Result:= Pass
Result:= Aborted
Result:= Fail
Figure 16e: Procedure Process_Access_Request_VLR (sheet 5)

Procedure Check_BAOC
Procedure to check call request against ODBAOC and SS BAOC
CBAOC1(1)
Signals to/from the right are to/from the process MAF017
Yes Operator determined BAOC imposed? No
Result:= Call barred (ODB)
Initiate handling of BAOC
Wait_For_ BAOC_ Response
From MSC
Abort
Yes Call barred? No
Result:= Call barred (SS barring)
Figure 17: Procedure Check_BAOC

Procedure OG_CUG_Check
Procedure to carry out CUG authorisation check for an outgoing (MO) call
OG_CUG1(1)
Signals to/from the right are to/from the process CUG_MAF014
outgoing call request
Wait_For_ CUG_Response
From MSC
Abort
response to call request
complete call (conditional CUG info)
reject call (cause)
Result:= Call barred
Figure 18: Procedure OG_CUG_Check

Procedure Check_OG_Barring
Procedure to check call request against SS barring and ODB categories
COB1(3)
Yes Operator determined BOIC imposed? No Destination address CC= Local CC? Yes No
1 Yes Operator determined BOIC-exHC imposed? Yes Destination address CC= Local CC? No 1 No Destination address CC= HPLMN CC? Yes No
1 Yes Operator determined BOIZC imposed? No Destination address ZC= Local ZC? Yes No
1 Yes Operator determined BOIZC-exHC imposed? Yes Destination address ZC= Local ZC? No 1 No Destination address CC= HPLMN CC? Yes Result:= Call barred (ODB) No
Figure 19a: Procedure Check_OG_Barring (sheet 1)

Procedure to check call request against SS barring and ODB categories 1
COB2(3)
No
Operator determined BOIC-exHC&BOIZC imposed? Yes
2 Yes Destination address ZC= Local ZC? No
Yes Destination address CC= Local CC? No 2 No Destination address CC= HPLMN CC? Yes Result:= Call barred (ODB)
Figure 19b: Procedure Check_OG_Barring (sheet 2)

2 Procedure to check call request against SS barring and ODB categories Yes Call barred? No
COB3(3)
Initiate handling of BOIC
To process MAF018
Wait_For_ BOIC_ Response
From MSC
Abort
From process MAF018
Yes Call barred? No
Initiate handling of BOIC-exHC
To process MAF020
Wait_For_ BOIC-exHC_ Response
From MSC
Abort
From process MAF020
Yes Call barred? No
Figure 19c: Procedure Check_OG_Barring (sheet 3)

Procedure Get_LI_Subscription_Info_MO_VLR
Procedure in the VLR to retrieve subscription information for the CLIR & COLP line identification services for an MO call
GLI_MOV1(1)
Initiate handling of CLIR
To process CLIR_MAF003
Wait_For_ CLIR_Info
From MSC
Abort
From process CLIR_MAF003
Initiate handling of COLP
To process COLP_MAF005
Wait_For_ COLP_Info
From MSC
Abort
From process COLP_MAF005
Figure 20: Procedure Get_LI_Subscription_Info_MO_VLR

Procedure Get_AoC_Subscription_Info_VLR
Procedure in the VLR to determine the subscription to Advice of Charge services
GAOCI_V1(1)
Yes AoC(I) provisioned? No
Set indicator: AoC not provisioned
Set indicator: AoC(C) provisioned
Set indicator: AoC(I) provisioned
Figure 21: Procedure Get_AoC_Subscription_Info_VLR

Procedure Obtain_Identity_VLR
Procedure in the VLR to obtain the identity of an MS
OID_VLR1(1)
Yes Identity= IMSI? No
Identification allowed?
No Yes
Obtain_ IMSI_VLR
No IMSI known? Yes
Result:= Fail
Result:= Pass
Result:= Aborted
Figure 22: Procedure Obtain_Identity_VLR

Procedure Obtain_IMSI_VLR
Process in the VLR to obtain the IMSI from the MS via the MSC
OIMSI_V1(1)
Signals to/from the left are to/from the MSC. Provide IMSI
Wait_For_ IMSI
Provide IMSI ack
Abort
Result:= Pass
Result:= Aborted
Figure 23: Procedure Obtain_IMSI_VLR

Procedure Authenticate_VLR
Procedure in the VLR to authenticate an MS via the MSC
AUT_VLR1(2)
Signals to/from the left are to/from the MSC. Authentication sets available? No
Yes
Obtain_ Authentication_ Sets_VLR
No Result= Pass? Yes Result= Aborted? No Authenticate Yes Result:= Aborted Yes 2
Result= Procedure Error? No Wait_For_ Authenticate_ Result
Result:= Procedure Error
Result:= Unknown Subscriber Authenticate ack
Abort
No Received SRES= expected SRES? Yes More authentication sets needed? Yes Fetch_ Authentication_ Sets_VLR No More authentication sets needed? Yes No
Fetch_ Authentication_ Sets_VLR
Result:= Pass
Result:= Aborted
Figure 24a: Procedure Authenticate_VLR (sheet 1)

Procedure Authenticate_VLR
Procedure in the VLR to authenticate an MS via the MSC 1
AUT_VLR2(2)
Signals to the left are to the MSC. Identity=IMSI? No
Yes
Retry with IMSI? Yes
No
Obtain_ IMSI_VLR
No IMSI known? Yes
IMSI matches TMSI? No
Yes
Result:= Aborted
Result:= Unidentified Subscriber
Identity:= IMSI
Result:= Illegal Subscriber
Figure 24b: Procedure Authenticate_VLR (sheet 2)

Procedure Obtain_Authentication_Sets_VLR
Procedure in the VLR to obtain authentication sets from the HLR
OAS_VLR1(2)
Signals to/from the right are to/from the HLR
Send Authentication Info
Wait_For_ Authentication_ Sets
Send Authentication Info ack
Send Authentication Info negative response
Yes Empty result? No
No Unknown Subscriber? Yes
Authentication sets available in VLR? Yes
No
Yes
Re-use old sets?
No
Result:= Pass
Result:= Unknown Subscriber
Figure 25a: Procedure Obtain_Authentication_Sets_VLR (sheet 1)

Procedure Obtain_Authentication_Sets_VLR
Procedure in the VLR to obtain authentication sets from the HLR
OAS_VLR2(2)
Signals to/from the left are to/from the MSC; Signals to/from the right are to/from the HLR
Wait_For_ Authentication_ Sets
Abort
Abort
No Abort Authentication sets available? Yes
Yes
Re-use old sets?
No
Result:= Aborted
Result:= Pass
Figure 25b: Procedure Obtain_Authentication_Sets_VLR (sheet 2)

Procedure Start_Tracing_VLR
Procedure in the VLR to request the MSC to start activity tracing
ST_TR_V1(1)
Signals to the left are to the MSC. Tracing active? Yes
No
Trace Subscriber Activity
Figure 26: Procedure Start_Tracing_VLR

Procedure Check_IMEI_VLR
Procedure in the VLR to request the MSC to check an IMEI
CIMEI_V1(1)
Signals to/from the left are to/from the MSC Check IMEI
Wait_For_ Check_IMEI_ Result
Abort
Check IMEI ack
No Service granted? Yes
Result:= Aborted
Result:= Fail
Result:= Pass
Figure 27: Procedure Check_IMEI_VLR

Procedure Obtain_IMEI_VLR
Process in the VLR to obtain the IMSI from the MS via the MSC
OIMEI_V1(1)
Signals to/from the left are to/from the MSC Provide IMEI
Wait_For_ IMEI
Provide IMEI ack
Abort
Result:= Pass
Result:= Aborted
Figure 28: Procedure Obtain_IMEI _VLR

Process Fetch_Authentication_Sets_VLR
Process in the VLR to retrieve authentication sets from the HLR
FAS_VLR1(1)
Obiain_ Authentication_ Sets_VLR
Figure 29: Process Fetch_Authentication_Sets_VLR
Page 64 GSM 03.18 Version 2.1.0: February 1997 7.2 7.2.1 7.2.1.1 Retrieval of routeing information for MT call Functional requirements of GMSC Process MT_GMSC
Sheet 1: the suggested mapping from values of the Send Routeing Info negative response information element to values of the ISUP release cause (see [22]) is shown in table 1. The mapping used is a matter for the network operator, depending on the telephony signalling system used. Sheet 3: after the GMSC has sent an IAM to the destination VMSC or the forwarded-to exchange, it acts as a transparent relay for messages received from the originating exchange and the destination VMSC or the forwarded-to exchange. Any message other than Address Complete, Connect, Answer or Release causes no change of state in the process MT_GMSC. Table 1: Suggested mapping of Send Routeing Info (SRI) negative responses to ISUP release causes SRI negative response Absent subscriber Bearer service not provisioned Call barred (ODB) Call barred (SS barring) CUG reject (Called party SS interaction violation) CUG reject (Incoming calls barred within CUG) CUG reject (Subscriber not member of CUG) CUG reject (Requested basic service violates CUG constraints) Data missing Facility not supported Forwarding violation Number changed System failure Teleservice not provisioned Unexpected data value Unknown subscriber 7.2.1.2 ISUP release cause number 20 57 21 21 21 55 87 87 ISUP release cause name Subscriber absent Bearer capability not authorised Call rejected Call rejected Call rejected Incoming calls barred within CUG User not member of CUG User not member of CUG
111 69 21 22 111 57 111 1
Protocol error, unspecified Requested facility not implemented Call rejected Number changed Protocol error, unspecified Bearer capability not authorised Protocol error, unspecified Unallocated (unassigned) number
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.

Process MT_GMSC
Process in the GMSC to handle a mobile-terminated call request
MT_GMSC1(3)
Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the HLR unless otherwise marked
Idle
Initial Address
From originating exchange
Send Routeing Info
Wait_For_ Routeing_ Info
Release
Send Routeing Info negative response
Send Routeing Info ack
Forwarding indication received? Yes
No
Set cause
Construct Initial Address Message
Release
Set redirection information
Initial Address
Towards destination MSC
Initial Address
Idle
Wait_For_ Forward_ACM
Wait_For_ ACM
Figure 30a: Process MT_GMSC (sheet 1)

Process MT_GMSC
Process in the GMSC to handle a mobile-terminated call request Wait_For_ ACM Wait_For_ Forward_ACM
MT_GMSC2(3)
Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange
Address Complete
Connect
Address Complete
Connect
Address Complete
Address Complete
Wait_For_ Answer
Wait_For_ Forward_ Answer
Answer
Answer
Handle_COLP_ Forwarding_ Interaction_MSC
Set COLP presentation indicator
Answer
Connect
Answer
Connect
Wait_For_ Clear
Wait_For_ Clear
Figure 30b: Process MT_GMSC (sheet 2)

Process MT_GMSC
Process in the GMSC to handle a mobile-terminated call request Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer, Wait_For_Forward_Answer, Wait_For_Clear
MT_GMSC3(3)
Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange
Release
Release
Release
Release
Idle
Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer, Wait_For_Forward_Answer, Wait_For_Clear
Figure 30c: Process MT_GMSC (sheet 3)

Procedure Handle_COLP_Forwarding_Interaction_MSC
Procedure in the GMSC or VMSC to handle the interaction between COLP and Call Forwarding
COINT_M1(1)
Signals to/from the right are to/from the process COLP_MAF039
initiate handling of COLP
Wait_For_ COLP_Info
Release
From originating exchange or destination exchange
continue call handling
Figure 31: Procedure Handle_COLP_Forwarding_Interaction_MSC
Page 69 GSM 03.18 Version 2.1.0: February 1997 7.2.2 7.2.2.1 Functional requirements of HLR Process SRI_HLR
Sheet 1: The procedures Check_Parameters, Subscription_Check_HLR and 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 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. 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. The negative response Call barred indicates whether the reason is operator determined barring or supplementary service barring, according to the result returned by the procedure Check_IC_Barring. The negative response CUG reject indicates whether the reason is: Incoming calls barred within CUG; Requested basic service violates CUG constraints; Subscriber not member of CUG
according to the cause returned by the procedure IC_CUG_Check. 7.2.2.4 7.2.2.5 7.2.2.6 7.2.2.7 Procedure First_Forwarding_HLR Procedure PRN_Error_HLR Procedure Forward_CUG_Check 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 [18]. 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 7.2.2.9 7.2.2.10 Procedure Check_IC_Barring Procedure IC_CUG_Check 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.

Process SRI_HLR
Process in the HLR to handle a request for routeing information
SRI_HLR1(2)
Idle Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR
Send Routeing Info
Check_ Parameters
No Result= Pass?
Yes Subscription_ Check_HLR
Yes Result= Fail?
No First_ Forwarding_ HLR
Yes Result= Fail?
No Yes Result= Forward?
No
Yes GSM BC= NULL?
No
Set GSM BC parameter
Provide Roaming Number
Wait_For_ MSRN
Figure 32a: Process SRI_HLR (sheet 1)

Process SRI_HLR
Process in the HLR to handle a request for routeing information
SRI_HLR2(2)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR
Wait_For_ MSRN
Provide Roaming Number ack
Provide Roaming Number negative response
PRN_Error_ HLR
Yes 2 Result= Fail? No
Forward_ CUG_Check
No Call allowed? Yes
Routeing address:= MSRN
Routeing address:= FTN
Set negative response: CUG reject
Called party SS interaction violation
Idle
Idle
Idle
Figure 32b: Process SRI_HLR (sheet 2)

Procedure Check_Parameters
Procedure to check the parameters of a received message
Chk_Par1(1)
No All required parameters present? Yes
No All parameter values acceptable? Yes
Set negative response: Data missing
Set negative response: Unexpected data value
Result:= Pass
Result:= Fail
Figure 33: Procedure Check_Parameters

Procedure Subscription_Check_HLR
Procedure in the HLR to make subscription checks for a mobileterminated call
SC_HLR1(1)
No MS known? Yes Set negative response: Unknown subscriber
Yes Number changed? No Set negative response: Number changed
Derive_Requested_ Basic_Service_HLR
Requested service provisioned? Yes
No
Set negative response: service not provisioned
Bearer service or Teleservice
Check_IC_ Barring
Yes Call barred? No Set negative response: Call barred
IC_CUG_ Check
No Call allowed? Set negative response: CUG reject
Yes
Result:= Pass
Result:= Fail
Figure 34: Procedure Subscription_Check_HLR

Procedure First_Forwarding_HLR
Procedure in the HLR to handle call forwarding before interrogation of the VLR
FF_HLR1(1)
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
Result:= Forward
Result:= Continue
Result:= Forward
Result:= Fail
Figure 35: Procedure First_Forwarding_HLR

Procedure PRN_Error_HLR
Procedure in the HLR to handle a negative response for a roaming number request
PRN_E_H1(1)
Negative response=Facility not supported? No
Yes
Set negative response: Facility not supported Negative response=Absent subscriber?
Yes
No
Negative response=No roaming number? Yes
No
Set negative response: System failure
Handle_CFNRc
Handle_CFNRc
Yes Result= Fail? Set negative response: Forwarding violation No Result= Fail? No
Yes
Set negative response: Forwarding violation
No Result= Forward? Set negative response: Absent subscriber Yes Result= Forward? Yes
No
Result:= Fail
Result:= Forward
Result:= Fail
Figure 36: Procedure PRN_Error_HLR

Procedure Forward_CUG_Check
Procedure to carry out CUG authorisation check for a forwarded call
FWD_CUG1(1)
No
CUG provisioned for forwarding subscriber against requested basic service Yes
CUG info provided in routeing information request No
Yes
Perform Forwarding CUG authorisation
As defined in GSM 03.85
CUG authorisation result Fail
Pass
Result:= Call barred
Update CUG info
As defined in GSM 03.85
Figure 37: Procedure Forward _CUG_Check

Procedure Derive_Requested_Basic_Service_HLR
Procedure in the HLR to derive the requested basic service for an incoming (MT) call according to the rules of GSM 09.07
DRBS_H1(1)
No
Exhaustive ISDN compatibility information available? Yes
No Multinumbering? Yes
GSM BC:=NULL
Apply GSM BC for this MSISDN
Derive GSM BC from ISDN compatibility information
Basic service:= default
Derive basic service from GSM BC
Figure 38: Procedure Derive_Requested_Basic_Service_HLR

Procedure Check_IC_Barring
Procedure to check call request against SS barring and ODB categories
CIB1(2)
Yes Operator determined BAIC imposed? No
Yes Operator determined BIC-Roam imposed? No No MS registered in HPLMN country? Yes
1 Yes
Operator determined BIC-RoamHZ imposed? No
No
MS registered in HPLMN zone? Yes
Result:= Call barred (ODB)
Figure 39a: Procedure Check_IC_Barring (sheet 1)

Procedure Check_IC_Barring
Procedure to check call request against SS barring and ODB categories 1
CIB2(2)
Initiate handling of BAIC
To process MAF022
Wait_For_ BAIC_ Response
From process MAF022
Yes Call barred? No
Initiate handling of BIC-Roam
To process MAF023
Wait_For_ BIC-Roam_ Response
From process MAF023
Yes Call barred? No
Figure 39b: Procedure Check_IC_Barring (sheet 2)

Procedure IC_CUG_Check
Procedure to carry out CUG authorisation check for an incoming (MT) call
IC_CUG1(1)
Signals to/from the right are to/from the process CUG_MAF015
incoming call
To process CUG_MAF015
Wait_For_ CUG_Response
response to call request
complete call (conditional CUG info)
reject call (cause)
Result:= Call barred (cause)
Figure 40: Procedure IC_CUG_Check

Procedure Handle_CFU
Procedure in the HLR to handle Call Forwarding Unconditional
H_CFU1(1)
initiate handling of CFU
Wait_For_ CFU_Result
Yes Error? No
No Normal call? Yes
Result:= Fail
Result:= Continue
Result:= Forward
Figure 41: Procedure Handle_CFU

Procedure Handle_CFNRc
Procedure in the HLR or VLR to handle Call Forwarding on Mobile Subscriber Not Reachable
H_CFNRc1(1)
initiate handling of CFNRc
Wait_For_ CFNRc_Result
Yes Error? No
No Mobile subscriber not reachable? Yes
Result:= Fail
Result:= Continue
Result:= Forward
Figure 42: Procedure Handle_CFNRc
Page 83 GSM 03.18 Version 2.1.0: February 1997 7.2.3 7.2.3.1 Functional requirements of VLR Process PRN_VLR
Sheet 1: the procedure Check_Parameters is specified in subclause 7.2.2.2. 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.15. 7.2.3.2 7.2.3.3 Process Restore_Subscriber_Data_VLR Process PSI_VLR
Sheet 1: the procedure Check_Parameters is specified in subclause 7.2.2.2. Sheet 2: the task 'Set Location Info' encompasses: Insertion of the cell ID if it was received from the MSC, otherwise retrieval of the stored location area ID; Derivation of the location number and geographical infornmation from the cell ID or location area ID if the VLR is capable of doing so; Insertion of the age of the location information received from the MSC; Insertion of the VLR number.
Sheet 2: the task Set subscriber state consists of inserting the subscriber state if it was received from the MSC, otherwise inserting the state Network determined not reachable.

Process PRN_VLR
Process in the VLR to handle a request for a roaming number
PRN_VLR1(3)
Idle Signals to/from the left are to/from the HLR. Provide Roaming Number
Check_ Parameters
No Result= Pass? Yes No OR indicator present? Yes
OR supported?
Yes Convert GSM BC to basic service If GSM BC was included in the Provide Roaming Number
No Set negative response: OR not allowed
Service supported by VLR? Yes
No
No
IMSI known in VLR? Yes
Set negative response: Facility not supported
Yes 2 IMSI detached? No
Roaming in LA allowed? Yes
No
Set negative response: Absent subscriber
Figure 43a: Process PRN_VLR (sheet 1)

Process PRN_VLR
Process in the VLR to handle a request for a roaming number 2
PRN_VLR2(3)
No Signals to the left are to the HLR. MSRN available Yes Set negative response: No roaming number
Allocate MSRN
Create IMSI record
Data confirmed by HLR:= False
Confirmed by radio contact:= False
Idle
Location info confirmed in HLR:= False
Only if >1 MSC per VLR
IMSI detached:= False
Allocate LMSI
If used by VLR
Store compatibility info
GSM BC, ISDN BC, ISDN LLC & ISDN HLC (as available)
Provide Roaming Number ack Yes More authentication sets needed? No
Fetch_ Authentication_ Sets_VLR
Restore_ Subscriber_ Data_VLR
Idle
Figure 43b: Process PRN_VLR (sheet 2)

Process PRN_VLR
3 Process in the VLR to handle a request for a roaming number
PRN_VLR3(3)
No Signals to the left are to the HLR. MSRN available Yes
MSC per VLR 1 >1
Set negative response: No roaming number
Yes Received MSC number= Stored MSC number No
False Confirmed by radio contact True Idle
Use received MSC number for MSRN
Use stored MSC number for MSRN
Allocate MSRN
Store compatibility info
GSM BC, ISDN BC, ISDN LLC & ISDN HLC (as available)
Data confirmed by HLR True
False
Idle
Figure 43c: Process PRN_VLR (sheet 3)

Process Restore_Subscriber_Data_VLR
Process in the VLR to restore subscriber data
RSD_VLR1(1)
Signals to/from the left are to/from the HLR Restore Data
Wait_For_ Data
Restore Data ack
Restore Data negative response
Update Subscriber Data
Update HLR number
Update MS Not Reachable indicator
If received from HLR
Data confirmed by HLR:=True
Figure 44: Process Restore_Subscriber_Data_VLR

Process PSI_VLR
Process in the VLR to handle a request from the HLR for subscriber information
PSI_VLR1(2)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the MSC Idle
Provide Subscriber Info
Check_ Parameters
No Result= Pass? Yes IMSI known in VLR? Yes Subscriber state requested? Yes Yes IMSI detached? No Roaming in LA allowed? Yes No No No Subscriber state requested? Yes No
Set subscriber state requested
Subscriber atate:= Network determined not reachable
Subscriber state:= Assumed idle
Location info requested? Yes
No
Set subscriber state requested
Obtain Subscriber Info
Provide Subscriber Info ack
Provide Subscriber Info negative response
Wait_For_ MSC_Response
Idle
Idle
Figure 45a: Process PSI_VLR (sheet 1)

Process PSI_VLR
Process in the VLR to handle a request from the HLR for subscriber information Wait_For_ MSC_Response
PSI_VLR2(2)
Signals to/from the left are to/from the HLR; signals to/from the right are to/from the MSC
Obtain Subscriber Info ack
Location info received? Yes
No
Set location info
Subscriber state received? Yes
No
Set subscriber state
Idle
Figure 45b: Process PSI_VLR (sheet 2)
Page 90 GSM 03.18 Version 2.1.0: February 1997 7.2.4 7.2.4.1 Functional requirements of MSC Process OSI_MSC
If the MS is engaged on a circuit-switched call, the state is busy, otherwise assumed idle.

Process OSI_MSC
Process in the MSC to handle a request from the VLR for information on the subscriber's location and state
OSI_MSC1(1)
Signals to/from the left are to/from the VLR
Idle
Obtain Subscriber Info
No
Set age of location info
MS in radio contact? Yes
No
Set cell global identity
Subscriber state requested? Yes
No
Set subscriber state
Idle
Figure 46: Process OSI_MSC
Page 92 GSM 03.18 Version 2.1.0: February 1997 7.3 7.3.1 7.3.1.1 MT call Functional requirements of serving MSC Process ICH_MSC
Sheet 1: the rules for converting the ISDN BC/LLC/HLC to a GSM bearer service or teleservice are specified in [18]. Sheet 1: the procedure Process_Access_Request_MSC is specified in subclause 7.1.1.2. 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 [22]) 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 Absent subscriber Busy subscriber CUG reject (Called party SS interaction violation) Forwarding violation Impossible call completion No subscriber reply System failure Unallocated roaming number ISUP release cause number 20 17 21 21 111 19 111 111 ISUP release cause name Subscriber absent User busy Call rejected Call rejected Protocol error, unspecified No answer from user (user alerted) Protocol error, unspecified Protocol error, unspecified
Sheet 3: the procedure Handle_COLP_Forwarding_Interaction is specified in subclause 7.2.1.2. Sheet 5: after the VMSC has sent an IAM to the forwarded-to exchange, it acts as a transparent relay for messages received from the GMSC and the forwarded-to exchange. 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: 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 setup 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 sevice request for anything other than a circuit-switched call, or completed the location registration procedure.
Page 93 GSM 03.18 Version 2.1.0: February 1997 7.3.1.3 Procedure Search_For_MS_MSC
Sheet 1: For an SMS or SS page, the test 'Call still exists' takes the 'Yes' exit if the SMS or SS transaction which led to the page still exists. Sheet 1: the test SMS or SS page is not required for the handling of circuit-switched calls, because the VLR will always use a page type of circuit-switched call, but the more generalised procedure Search_For_MS_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures. Sheet 1: the test MS busy takes the Yes exit if the MS is engaged on a circuit-switched call. Sheet 1: the test Call in setup 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 sevice 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 MSC 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. 7.3.1.5 Procedure Process_Call_Waiting_MSC
Sheet 1: the MSC 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 Call Confirmed message indicates 'busy' for the successful case. Sheets 1 & 2: the Release transaction (reject) message covers all unsuccessful cases not otherwise indicated. 7.3.1.6 Procedure Set_CLIP_Info_MSC
The originating exchange may release the call or the MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIP_MAF002. The message is saved for processing after return from the procedure. 7.3.1.7 7.3.1.8 7.3.1.9 Procedure Derive_GSM_BC_MSC Procedure Handle_AoC_MT_MSC 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.

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call
ICH_MSC1(5)
Idle
Initial Address
From GMSC
Convert ISDN BC/LLC/HLC (if present) to GSM bearer service/teleservice & GSM BC
Send Info For Incoming Call
Wait_For_ Page_Request
Send Info For Incoming Call negative response
Page MS
Search For MS
Set cause
Page_ MS_MSC
Search_For_ MS_MSC
Yes Release To GMSC Result= Pass? No Process_ Access_ Request_MSC
No Release call resources Result= Fail? Yes Result= Pass? Yes Wait_For_ MT_Call_ Result Wait_For_ MT_Call_ Result No Result= Fail Yes Wait_For_ MT_Call_ Result
No
Idle
Release Idle
To GMSC
Idle
Idle
Figure 47a: Process ICH_MSC (sheet 1)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_ MT_Call_ Result
ICH_MSC2(5)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise Process Call Waiting
Complete Call
Set cause
Complete_ Call_In_MSC
Process_ Call_ Waiting_MSC
Yes To GMSC Release Result= Pass? Result= Pass?
Yes
No
No
Yes Release transaction Result= Fail No
Yes Result= Fail No
Wait_For_ Clear
Wait_For_ MT_Call_ Result
Wait_For_ Clear
Idle
Idle
Idle
Send Info For Incoming Call ack
Call is to be forwarded
Set redirection information
Address complete
Initial Address Message
Towards exchange defined by forwarded-to number
Wait_For_ ACM
Figure 47b: Process ICH_MSC (sheet 2)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_ ACM
ICH_MSC3(5)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the destination exchange
Release
Release
Address Complete
Connect
Release
Release
Address Complete
Start Answer guard timer
Idle
Wait_For_ Answer
Release
Release
Answer
Release
Release
Idle
Answer
Connect
Wait_For_ Forwarded_Clear
Figure 47c: Process ICH_MSC (sheet 3)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_MT_Call_Result, Wait_For_Clear
ICH_MSC4(5)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless otherwise indicated
Release transaction
Release
From GMSC
Release
To GMSC
Release transaction
Abort
Idle
Wait_For_ Forwarded_Clear
Release
From GMSC
Release
Release
Release
To GMSC
Idle
Figure 47d: Process ICH_MSC (sheet 4)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_ACM, Wait_For_Answer, Wait_For_Forwarded_Clear
ICH_MSC5(5)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the destination exchange
Figure 47e: Process ICH_MSC (sheet 5)

Procedure Page_MS_MSC
Procedure in the MSC to page an MS in a specified location area
PAGE_M1(2)
Location area ID known? Yes
No
Set negative response: Unknown LAI No
Call still exists? Yes
Set negative response: System Failure Yes
MS connection exists? No
Yes SMS or SS page? No
MS busy? Yes No
Yes Call in setup? No
Yes Call waiting? No
Clear received:= False
Set negative response: Busy Subscriber
More calls possible
Set negative response: Busy Subscriber (NDUB)
In specified location area
Page
Set access connection status
Page MS negative response
Start Page response timer
Result:= Pass
Result:= Fail
Wait_For_ Page_ Response
Figure 48a: Procedure Page_MS_MSC (sheet 1)

Procedure Page_MS_MSC
Procedure in the MSC to page an MS in a specified location area Wait_For_ Page_ Response
PAGE_M2(2)
MS connection established
Release
From GMSC
Page response timer expired
CM Service Request
For circuitswitched call
True Clear received False Abort
True Clear received False
CM Service Request
To process OCH_MSC
Set negative response: Absent Subscriber
Release transaction
Result:= Pass
Result:= Aborted
Clear received:= True
Result:= Aborted
Result:= Fail
Result:= Fail
Result:= Aborted
Wait_For_ Page_ Response
Figure 48b: Procedure Page_MS_MSC (sheet 2)

Procedure Search_For_MS_MSC
Procedure in the MSC to search for an MS (page in all location areas)
SRCH_M1(2)
Call still exists? Yes
No
MS connection exists? No
Yes
Yes SMS or SS page? No
Yes MS busy? No Yes Call in setup? No
Yes Call waiting? No
Clear received:= False
Set negative response: Busy Subscriber
More calls possible
In all location areas
Page
Search For MS negative response
Start Page response timer
Result:= Pass
Result:= Fail
Wait_For_ Search_ Response
Figure 49a: Procedure Search_For_MS_MSC (sheet 1)

Procedure Search_For_MS_MSC
Procedure in the MSC to search for an MS (page in all location areas) Wait_For_ Search_ Response
SRCH_M2(2)
MS connection established
Release
From GMSC
Page response timer expired
CM Service Request
For circuitswitched call
True Clear received False Abort
CM Service Request
To process OCH_MSC
True Search For MS ack Release transaction Clear received False
Result:= Pass
Result:= Aborted
Clear received:= True
Result:= Aborted
Result:= Fail
Result:= Fail
Result:= Aborted
Wait_For_ Search_ Response
Figure 49b: Procedure Search_For_MS_MSC (sheet 2)

Procedure Complete_Call_In_MSC
Procedure in the MSC to complete an MT call on request from the VLR
CCI_MSC1(4)
Set_CLIP_ Info_MSC
Derive_ GSM_BC_ MSC
Setup
Wait_For_ Setup_ Response
Call Confirmed
Setup failure
Allocate channel
Complete Call negative response
Result:= Fail
Figure 50a: Procedure Complete_Call_In_MSC (sheet 1)

Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Allocation_ Complete
CCI_MSC2(4)
Allocation Complete
Allocation failure
Wait_For_ Alerting
Set negative response: Radio congestion
Alerting
Connect
Alerting failure
No NRCT provided? Yes Handle_AoC_ MT_MSC Abort Result:= Fail
No Start No Reply Call Timer Result= Pass? Yes Release To GMSC
Address Complete
To GMSC
Connect ack
Result:= Aborted
Wait_for_ Answer
Set_COL_ Presentation_ Indicator_MSC
To GMSC
Connect
Release
To GMSC
Complete Call ack
Abort
Result:= Pass
Result:= Aborted
Figure 50b: Procedure Complete_Call_In_MSC (sheet 2)

Procedure in the MSC to complete an MT call on request from the VLR Wait_for_ Answer
CCI_MSC3(4)
No Reply Call Timer expired
Connect
Set negative response: No subscriber reply
Handle_AoC_ MT_MSC
Result:= Fail
Connect ack
Answer
To GMSC
Release
To GMSC
Complete Call ack
Abort
Result:= Pass
Result:= Aborted
Figure 50c: Procedure Complete_Call_In_MSC (sheet 3)

Procedure in the MSC to complete an MT call on request from the VLR Wait_For_Setup_Response, Wait_For_Assignment_Complete, Wait_For_Alerting, Wait_For_Answer
CCI_MSC4(4)
Release transaction
Release
From GMSC
No User busy? Yes Release transaction
Set negative response: Busy subscriber (UDUB)
Release
To GMSC
Abort
Result:= Fail
Result:= Aborted
Figure 50d: Procedure Complete_Call_In_MSC (sheet 4)

Procedure Process_Call_Waiting_MSC
Procedure in the MSC to handle a Process Call Waiting request from the VLR Yes Call being set up No Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise Set negative response: Busy subscriber
PCW_MSC1(3)
Set_CLIP_ Info_MSC
Derive_ GSM_BC_ MSC
Process Call Waiting negative response
Setup
Result:= Fail
Wait_For_ Setup_ Response
Call Confirmed
Release transaction (UDUB)
Release transaction (reject)
Setup failure
Wait_For_ Alerting
Set negative response: Busy subscriber
Clear pending call
Process Call Waiting negative response Alerting Alerting failure Result:= Fail Release To GMSC of waiting call
No NRCT provided? Yes Abort Abort
Start No Reply Call Timer
Start Acceptance timer
Release
To GMSC of waiting call
Result:= Aborted
Address Complete
Result:= Aborted
Wait_For_ Acceptance
Figure 51a: Procedure Process_Call_Waiting_MSC (sheet 1)

Procedure in the MSC to handle a Process Call Waiting request from the VLR Wait_for_ Acceptance
PCW_MSC2(3)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise No
Connect
Assignment required? Yes
Allocate channel
Allocation Complete
Allocation failure
Handle_AoC_ MT_MSC
Connect ack
Release
Abort
Answer
Result:= Aborted
Process Call Waiting ack
Result:= Pass
Figure 51b: Procedure Process_Call_Waiting_MSC(sheet 2)

Procedure in the MSC to handle a Process Call Waiting request from the VLR Wait_for_ Acceptance
PCW_MSC3(3)
Release transaction (busy)
Release transaction (reject)
Acceptance timer expired
No Reply Call Timer expired
Clear pending call
Set negative response: Busy subscriber
Release
Set negative response: No subscriber reply
Abort
Result:= Fail
Result:= Aborted
Result:= Fail
Wait_For_Setup_Response, Wait_For_Assignment_Complete, Wait_For_Alerting, Wait_For_Acceptance
Release
From GMSC of waiting call
Clear pending call
Abort
Result:= Aborted
Figure 51c: Procedure Process_Call_Waiting_MSC(sheet 3)

Procedure Set_CLIP_Info_MSC
Procedure in the MSC to determine the CLIP information to be sent to the MS
CAINF_M1(1)
Signals to/from the right are to/from the process CLIP_MAF002
Initiate handling of CLIP
Wait_For_ CLIP_Info
Release transaction
From BSS
Release
From GMSC
Figure 52: Procedure Set_CLIP_Info_MSC

Procedure Derive_GSM_BC_MSC
Procedure in the MSC to derive the requested GSM BC for an incoming (MT) call according to the rules of GSM 09.07
DRBC_M1(1)
No
GSM BC derived from ISDN compatibility information? Yes
Yes GSM BC received in PRN? No
Omit GSM BC from Setup
Use GSM BC received in PRN
Use GSM BC derived from ISDN compatibility information
Figure 53: Derive_GSM_BC_MSC

Procedure Handle_AoC_MT_MSC
Procedure in the MSC to handle AoC signalling towards the MS for an MT call
AOCMT_M1(1)
Signals to/from the left are to/from the BSS; signals from the right are from the AoC timer function.
Yes AoC(I) provisioned? No
Send Charging Parameters
Send Charging Parameters
Start AoC acknowledgment timer
Wait_For_ Charging_ Parameters_ Ack
Charging Parameters ack
Release connection
AoC acknowledgment timer expired
Release transaction
Result:= Pass
Result:= Fail
Figure 54: Procedure Handle_AoC_MT_MSC

Procedure Set_COL_Presentation_Indicator_MSC
Procedure in the MSC to determine the COL presentation indicator value
COIND_M1(1)
Signals to/from the right are to/from the process COLR_MAF041
Initiate handling of COLR
Wait_For_ COLR_Info
Release transaction
From BSS
Release
From GMSC
Figure 55: Procedure Set_COL_Presentation_Indicator MSC
Page 114 GSM 03.18 Version 2.1.0: February 1997 7.3.2 7.3.2.1 Functional requirements of VLR 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 2: the procedure Process_Access_Request_VLR is specified in subclause 7.1.2.2. 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 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_AoC_Subscription_Info_VLR is specified in subclause 7.1.2.7. Sheet 5: the procedure Handle_CFNRc is specified in subclause 7.2.2.11. Sheet 6: the procedure Forward_CUG_Check is specified in subclause 7.2.2.6. 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 7.3.2.4 Procedure Search_For_MS_VLR Procedure Get_CW_Subscription_Info_VLR
The MSC 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 MSC 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.

Process ICH_VLR
Process in VLRB to handle a request for information for an incoming (MT) call
ICH_VLR1(6)
Idle
Send Info For Incoming Call
No MSRN known? Yes Data confirmed by HLR True False
Derive_Requested_ Basic_Service_VLR
Set negative response: Unallocated Roaming Number
Yes IMSI detached? No Roaming in LA allowed? Yes No Location area ID known? Yes No
Search_For_ MS_VLR
Page MS
Page type= circuit-switched call
Yes Result= Fail? No
Idle
Wait_For_ Access_ Request
Idle
Figure 56a: Process ICH_VLR (sheet 1)

Process ICH_VLR
Process in VLRB to handle a request for information for an incoming (MT) call Wait_For_ Access_ Request
ICH_VLR2(6)
Abort
Yes Absent subscriber? No 1
Process_ Access_ Request_VLR
No Result= Pass? No Busy subscriber? Yes 3 CUG info present? No Yes NDUB? No Translate CUG interlock to index As defined in GSM 03.85 Yes Idle Yes
Get_CW_ Subscription_ Info_VLR
Yes Success? Yes No CFNRy A&O? No Provide NRCT value 3 No
CW available?
Yes
Get_LI_ Subscription_ Info_MT_VLR
Get_LI_ Subscription_ Info_MT_VLR
Complete Call
Wait_For_ Complete_Call_ Result
Idle
Figure 56b: Process ICH_VLR (sheet 2)

Process ICH_VLR
Process in VLRB to handle a request for information for an incoming (MT) call Wait_for_ Complete_Call Result
ICH_VLR3(6)
Complete Call ack
Abort
Yes Busy subscriber? No
Yes Absent subscriber? No
Yes Radio congestion? No
No subscriber reply? No
Yes
Set negative response: Impossible call completion
Idle
Idle
Figure 56c: Process ICH_VLR (sheet 3)

Process ICH_VLR
4 Process in VLRB to handle a request for information for an incoming (MT) call Signals to/from the left are to/from the MSC.
ICH_VLR4(6)
No CFNRy A&O?
Yea
Set NRCT
Process Call Waiting
Wait_For_ PCW_Result
Abort
Yes Busy subscriber? No
No subscriber reply? No
Yes
Set negative response: Impossible call completion
Idle
Idle
Figure 56d: Process ICH_VLR (sheet 4)

Process ICH_VLR
Process in VLRB to handle a request for information for an incoming (MT) call 1
ICH_VLR5(6)
Handle_CFNRc
5 Yes Result= Fail? Set negative response: Forwarding Violation No Result= Forward? Yes Result= Fail? No Set negative response: Forwarding Violation No Result= Forward? Yes Set negative response: Busy Subscriber Set negative response: Absent Subscriber 7 Yes No
Handle_CFB
Handle_CFNRy
Yes Result= Fail? Set negative response: Forwarding Violation No Result= Forward? Set negative response: No Subscriber Reply Yes No
Idle
Figure 56e: Process ICH_VLR (sheet 5)

Process ICH_VLR
Process in VLRB to handle a request for information for an incoming (MT) call 7 Signals to the left are to the MSC.
ICH_VLR6(6)
Forward_ CUG_Check
No Call allowed? Yes
Set result: Forward
Set negative response: CUG reject
Set forwarding information
Idle
Idle
Figure 56f: Process ICH_VLR (sheet 6)

Procedure Derive_Requested_Basic_Service_VLR
Procedure in the VLR to derive the requested basic service for an incoming (MT) call
DRBS_V1(1)
Yes Basic service included in Send Info For Incoming Call? No
Basic service:= BS received in SIFIC
Yes GSM BC received in Provide Roaming Number No
Basic service:= BS derived from GSM BC
Basic service:= default
Figure 57: Procedure Derive_Requested_Basic_Service_VLR

Procedure Search_For_MS_VLR
Procedure in the VLR to search for an MS (i.e. page in all location areas)
SRCH_V1(1)
Signals to/from the left are to/from the MSC Search For MS Page type= Circuit-switched call
Wait_For_ Search_Result
Search For MS ack
Abort
Update Location Area ID
Result:= Pass
Result:= Fail
Result:= Aborted
Figure 58: Procedure Search_For_MS_VLR

Procedure Get_CW_Subscription_Info_VLR
Procedure in the VLR to retrieve subscription information for the Call Waiting service
CWI_VLR1(1)
initiate handling of CW
Wait_For_ CW_Info
From MSC
Abort
process call waiting
Figure 59: Procedure Get_CW_Subscription_Info_VLR

Procedure Get_LI_Subscription_Info_MT_VLR
Procedure in the VLR to retrieve subscription information for the CLIP & COLR line identification services for an MT call
GLI_MTV1(1)
Initiate handling of CLIP
To process CLIP_MAF001
Wait_For_ CLIP_Info
From MSC
Abort
From process CLIP_MAF001
Initiate handling of COLR
To process COLR_MAF040
Wait_For_ COLR_Info
From MSC
Abort
From process COLR_MAF040
Figure 60: Procedure Get_LI_Subscription_Info_MT_VLR

Procedure Handle_CFB
Procedure in the VLR to handle Call Forwarding on Busy
H_CFB1(1)
initiate handling of CFB
Wait_For_ CFB_Result
Yes Error? No
Normal call busy? Yes
No
Result:= Fail
Result:= Continue
Result:= Forward
Figure 61: Procedure Handle_CFB

Procedure Handle_CFNRy
Procedure in the VLR to handle Call Forwarding on No subscriber Reply
H_CFNRy1(1)
initiate handling of CFNRy
Wait_For_ CFNRy_Result
Yes Error? No
No Normal call? Yes
Result:= Fail
Result:= Continue
Result:= Forward
Figure 62: Procedure Handle_CFNRy
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 8.1.1 Messages on the B interface (MSC-VLR) Abort
The following information element is required: Information element name Abort reason 8.1.2 Authenticate Required M Description Indicates the reason for the procedure being aborted.
The following information elements are required: Information element name RAND CKSN 8.1.3 Authenticate ack Required M M Description Random number challenge to be sent to the MS [3] Cipher key sequence number to be sent to the MS [3]
The following information element is required: Information element name SRES 8.1.4 Check IMEI Required M Description Signature result returned by the MS [3]
This message contains no information elements. 8.1.5 Check IMEI ack
The following information element is required: Information element name Equipment status Required M Description Indicates whether the ME is black-listed, grey-listed or white-listed
8.1.6
The negative response information element can take the following values: System failure; Unknown equipment.
Page 128 GSM 03.18 Version 2.1.0: February 1997 8.1.7 Complete Call
The following information elements are required:
Page 129 GSM 03.18 Version 2.1.0: February 1997 Information element name MSISDN Required C Description 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 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 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. Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. Shall be present for an MT call if it was received in the Provide Roaming Number; otherwise shall be absent. Indicates that CLIP is provisioned. Shall be present for an MT call if CLIP is provisioned; otherwise shall be absent. 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. Indicates that CLIR is provisioned. Shall be present for an MO call if CLIR is provisioned; otherwise shall be absent. 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. Indicates that COLP is provisioned. Shall be present for an MO call if COLP is provisioned; otherwise shall be absent. 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. Indicates that COLR is provisioned. Shall be present for an MT call if COLR is provisioned; otherwise shall be absent. 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. For the definition of this IE, see [11]. 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. For the definition of this IE, see [11]. Shall be present for an ordinary MO call if the call is a CUG call; otherwise shall be absent. For the definition of this IE, see [11]. Shall be present for an ordinary MO call if the call is a CUG call with outgoing access; otherwise shall be absent. 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.
IMEI
Category
GSM bearer capability ISDN bearer capability ISDN low layer compatibility ISDN high layer compatibility CLIP provision CLIR override provision
C C C C C C
CLIR provision CLIR mode
C C
COLP provision COLR override provision
C C
COLR provision No Reply Condition Timer
C C
CUG index
CUG interlock
CUG outgoing access
Advice of Charge provision
Page 130 GSM 03.18 Version 2.1.0: February 1997 8.1.8 Complete Call ack
This message contains no information elements. 8.1.9 Complete Call negative response
The negative response information element can take the following values: 8.1.10 Absent subsccriber; Busy subscriber; No subscriber reply; Radio congestion. Forward New TMSI
The following information element is required: Information element name TMSI 8.1.11 Required M Description TMSI to be sent to the MS.
Forward New TMSI ack
This message contains no information elements. 8.1.12 Forward New TMSI negative response
The negative response information element can take the following value: 8.1.13 TMSI reallocation failure. Obtain Subscriber Info
The following information elements are required: Information element name IMSI Location information requested Subscriber state requested Required M C Description IMSI of the MS for which information is required. Indicates that the VLR requires location information for the MS. Shall be present if location information is required; otherwise shall be absent. 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
The following information elements are required: Information element name Cell global identity Required C Description Identity of the cell from which the MS established a radio transaction. Shall be present if the VLR requested location information and the mobile is currently engaged on a radio transaction; otherwise shall be absent. Time in minutes since the MS last established a radio transaction. Shall be present if the VLR requested location information; otherwise shall be absent. Indicates whether the MS is busy (i.e. engaged on a circuitswitched call) or assumed idle. Shall be present if the VLR requested state information; otherwise shall be absent.
Age of location information
Subscriber state
8.1.15
Page MS
Page 131 GSM 03.18 Version 2.1.0: February 1997 Information element name IMSI Location area ID Page type TMSI 8.1.16 Required M M M O Page MS negative response Description IMSI of the MS to be paged. Location area in which the MS is to be paged. Indicates whether the paging is for a circuit-switched call, MT SMS delivery or SS activity TMSI to be broadcast to identify the MS.
The negative response information element can take the following values: Absent subscriber; 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. 8.1.17 Process Access Request
The following information elements are required: Information element name CM service type Required M Description 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. Indicates whether or not the connection to the MS is ciphered and whether or not it is authenticated. Identity of the location area from which the access request was received. 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 of the MS requesting the access. For normal MO call or page response, one of IMSI or TMSI shall be present. For emergency call, one of IMSI, TMSI or IMEI shall be present. IMEI 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. Cipher key sequence number of the MS requesting the access. Shall be present if TMSI is present; otherwise shall be absent.
Access connection status Current location area ID IMSI
M M C
TMSI
IMEI
CKSN
8.1.18
The following information elements are required: Information element name IMSI Required C Description 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 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 of the MS requesting the access.
IMEI
MSISDN
Page 132 GSM 03.18 Version 2.1.0: February 1997 8.1.19 Process Access Request negative response
The negative response information element can take the following values: 8.1.20 Roaming not allowed; System failure; Unidentified subscriber; Illegal equipment; Illegal subscriber. Process Call Waiting
The following information elements are required: Information element name MSISDN GSM bearer capability ISDN bearer capability ISDN low layer compatibility ISDN high layer compatibility CLIP provision CLIR override provision Required M C C C C C C Description MSISDN of the MS for which the Process Call Waiting is sent. Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. Shall be present if it was received in the Provide Roaming Number for the waiting call; otherwise shall be absent. Indicates that CLIP is provisioned. Shall be present if CLIP is provisioned; otherwise shall be absent. 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. Indicates that COLR is provisioned. Shall be present if COLR is provisioned; otherwise shall be absent. 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. For the definition of this IE, see [11]. Shall be present if the waiting call is a CUG call; otherwise shall be absent. 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.
COLR provision No Reply Condition Timer
C C
CUG index Advice of Charge provision
C C
8.1.21
This message contains no information elements. 8.1.22 Process Call Waiting negative response
The negative response information element can take the following values: 8.1.23 Busy subscriber; No subscriber reply. Provide IMEI
This message contains no information elements. 8.1.24 Provide IMEI ack
The following information element is required:
Page 133 GSM 03.18 Version 2.1.0: February 1997 Information element name IMEI 8.1.25 Provide IMSI Required M Description IMEI of the ME involved in the access request.
This message contains no information elements. 8.1.26 Provide IMSI ack
The following information element is required: Information element name IMSI 8.1.27 Search For MS Required M Description IMSI of the MS involved in the access request.
The following information elements are required: Information element name IMSI Page type TMSI 8.1.28 Search For MS ack Required M M O Description IMSI of the MS to be paged in all location areas. Indicates whether the paging is for a circuit-switched call, MT SMS delivery or SS activity TMSI to be broadcast to identify the MS.
The following information element is required: Information element name Location area ID 8.1.29 Required M Description Location area in which the MS responded to the page.
The negative response information element can take the following values: Absent subscriber; Busy subscriber (More calls possible); Busy subscriber (NDUB); System failure.
The Search For MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call. 8.1.30 Send Info For Incoming Call
Page 134 GSM 03.18 Version 2.1.0: February 1997 Information element name MSRN Bearer service Required M C Description Mobile Station Roaming Number received in the IAM. 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. 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. Number dialled by the calling subscriber. Shall be present if it was received in the IAM; otherwise shall be absent. Number of times the incoming call has already been forwarded. Shall be present if it was received in the IAM; otherwise shall be absent. For the definition of this IE, see [11]. Shall be present if it was received in the IAM; otherwise shall be absent. For the definition of this IE, see [11]. Shall be present if it was received in the IAM; otherwise shall be absent.
Teleservice
Dialled number Number of forwarding
C C
CUG interlock CUG outgoing access
C C
8.1.31
The following information elements are required: Information element name IMSI Forwarded-to number Forwarding reason Required M M M Description IMSI of the B subscriber. E.164 number of the C subscriber. Indication of why the call has been forwarded (on mobile subscriber busy, on mobile subscriber not reachable or on no subscriber reply). Indication of whether the calling party is to be notified that the call has been forwarded. 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; otherwise shall be absent. Subaddress of the C subscriber (see [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. For the definition of this IE, see [11]. Shall be present if the VLR has determined that the forwarded call is to be treated as a CUG call in accordance with the rules in [11], otherwise shall be absent. For the definition of this IE, see [11]. Shall be present if the VLR has determined that the forwarded call is to be treated as a CUG call with outgoing access in accordance with the rules in [11], otherwise shall be absent.
Notification to calling party Notification to forwarding party
M C
Forwarded-to subaddress
CUG interlock
CUG outgoing access
8.1.32
The negative response information element can take the following values: Absent subscriber; Busy subscriber; CUG reject (Called party SS interaction violation); Forwarding violation; Impossible call completion; No subscriber reply; System failure; Unallocated roaming number;
Page 135 GSM 03.18 Version 2.1.0: February 1997 8.1.33 Send Info For Outgoing Call
The following information elements are required: Information element name Called number Bearer service Required M C Description E.164 number of the call destination. 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 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. For the definition of this IE, see [11]. Shall be present if it was received in the setup request from the MS. For the definition of this IE, see [11]. Shall be present if it was received in the setup request from the MS. For the definition of this IE, see [11]. Shall be present if it was received in the setup request from the MS.
Teleservice
CUG index Suppress preferential CUG Suppress CUG outgoing access 8.1.34
C C C
The negative response information element can take the following values: 8.1.35 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. Set ciphering mode
The following information element is required: Information element name Ciphering mode Kc Required M C Description Indicates whether ciphering of the radio connection is required, and if so which ciphering algorithm is to be used. 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.36
Trace subscriber activity
The following information elements are required: Information element name Trace reference Trace type 8.1.37 Use existing TMSI Required M M Description Reference number to be included with tracing reports which the MSC sends to the OMC For the definition of this IE, see [20]
This message contains no information elements.
Page 136 GSM 03.18 Version 2.1.0: February 1997 8.2 8.2.1 Messages on the C interface (MSC-HLR) Send Routeing Info
The following information elements are required: Information element name MSISDN CUG interlock CUG outgoing access Number of forwarding Required M C C C Description MSISDN of the B subscriber (see [2]). For the definition of this IE, see [11]. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. For the definition of this IE, see [11]. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. 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 bearer capability. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. ISDN lower layer compatibility. Shall be present if the GMSC received it in the IAM, otherwise shall be absent. ISDN higher layer compatibility. Shall be present if the GMSC received it in the IAM, otherwise shall be absent.
ISDN BC ISDN LLC ISDN HLC
C C C
8.2.2
The following information elements are required: Information element name IMSI Roaming number Required M C Description IMSI of the B subscriber (see [2]). E.164 number required to route the call to VMSCB (see [2]). Shall be present if the HLR received it in the Provide Roaming Number ack, otherwise shall be absent. 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. Subaddress of the C subscriber (see [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. 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. 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. For the definition of this IE, see [11]. Shall be present if the HLR has determined that the call is to be treated as a CUG call in accordance with the rules in [11], otherwise shall be absent. For the definition of this IE, see [11]. Shall be present if the HLR has determined that the call is to be treated as a CUG call with outgoing access in accordance with the rules in [11], otherwise shall be absent.
Forwarded-to number
Forwarded-to subaddress
Notification to calling party
Forwarding reason
CUG interlock
CUG outgoing access
8.2.3
The negative response information element can take the following values: Absent subscriber; Bearer service not provisioned; Call barred (Operator determined barring);
Page 137 GSM 03.18 Version 2.1.0: February 1997 8.3 8.3.1 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. Messages on the D interface (VLR-HLR) Provide Roaming Number
The following information elements are required: Information element name IMSI MSC number MSISDN Required M M O Description IMSI of the B subscriber (see [2]). E.164 number which identifies VMSCB (see [2]). E.164 number which identifies the B subscriber. May be present if the HLR requires it to be included in the call data record. Local Mobile Subscriber Identity. Shall be present if the LMSI was sent to HLRB at location updating. 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 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 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 higher layer compatibility. Shall be present if the HLR received it in the Send Routeing Info message, otherwise shall be absent.
LMSI GSM bearer capability
C C
ISDN BC
ISDN LLC
ISDN HLC
8.3.2
The following information element is required: Information element name Roaming number Required M Description E.164 number required to route the call to VMSCB (see [2]).
8.3.3
The negative response information element can take the following values:
Page 138 GSM 03.18 Version 2.1.0: February 1997 8.3.4 Absent subscriber; Data missing; Facility not supported; No roaming number available; OR not allowed; Unexpected data value. Provide Subscriber Info
The following information elements are required: Information element name IMSI LMSI Requested information Required M C M Description IMSI of the subscriber for whom information is requested (see [2]). Local Mobile Subscriber Identity. Shall be present if the LMSI was sent to the HLR at location updating. Indicates whether the HLR requires location information, subscriber state or both location information and subscriber state.
8.3.5
The following information elements are required: Information element name Location information Required C Description 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. Indicates whether the MS is busy (i.e. engaged on a circuitswitched 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.
Subscriber state
8.3.5.1
Location information
The compound information element Location information consists of the following subordinate information elements: Information element name Location number Required C Description For a definition of this information element, see [21]. Shall be present if the VLR can derive it from the stored cell global identity or location area identity; otherwise shall be absent. Cell global identity of the cell in which the MS last established a radio transaction. Shall be present if the MSC/VLR can supply it; otherwise shall be absent. Shall be absent if Location area ID is present. Identity of the location area in which the MS last established a radio transaction. Shall be present if the MSC/VLR can supply it; otherwise shall be absent. Shall be absent if Cell ID is present. For a definition of this information element, see [4]. Shall be present if the VLR can derive it from the stored cell global identity or location area identity; otherwise shall be absent. E.164 number which identifies the VLR (see [2]). Measured in minutes.
Cell ID
Location area ID
Geographical information
VLR number Age of location information
M M
Page 139 GSM 03.18 Version 2.1.0: February 1997 8.3.6 Provide Subscriber Info negative response
The negative response information element can take the following values: 8.3.7 Unexpected data value. Restore Data
The following information elements are required: Information element name IMSI LMSI Required M O Description IMSI of the subscriber for whom data are to be restored (see [2]). LMSI of the subscriber for whom data are to be restored (see [2]). May be included if required by the requesting VLR.
8.3.8
Restore Data ack
The following information elements are required: Information element name HLR number MS not reachable flag Required M C Description E.164 number which identifies the HLR (see [2]). 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; otherwise shall be absent.
8.3.9
Restore Data negative response
The negative response information element can take the following values: 8.3.10 System failure; Unknown subscriber. Provide Subscriber Info negative response
The negative response information element can take the following values: 8.4 8.4.1 Data missing; Unexpected data value. Messages on the F interface (MSC-EIR) Check IMEI
The following information element is required: Information element name IMEI 8.4.2 Check IMEI ack Required M Description IMEI of the ME whose status is to be checked (see [2]).
The following information element is required: Information element name Equipment status Required M Description Indicates whether the ME is black-listed, grey-listed or white-listed
8.4.3
The negative response information element can take the following value:
Page 140 GSM 03.18 Version 2.1.0: February 1997 Unknown equipment.
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 coordinating 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 coordinating 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 coordinating process has relayed a Release message, it returns to the idle state. Sheet 2: after the MSC coordinating 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 coordinating process has relayed a Release message, it returns to the idle state.

Process MSC_Coord
Process in the MSC to handle an incoming IAM and trigger the correct application process IDLE
Coord_M1(2)
Initial Address
Called party address in MSRN range for this MSC? Yes
No
No HLR address derivable? Yes
Initial Address
To process ICH_MSC
Initial Address
To process MT_GMSC
Initial Address
To destination determined by routeing tables
Relay_ Information_ Internally
Relay_ Information_ Externally
Figure 63a: Process MSC_Coord (sheet 1)

Process MSC_Coord
Process in the MSC to handle an incoming IAM and trigger the correct application process Relay_ Information_ Internally
Coord_M2(2)
Release
Release
From offspring
Release
To offspring
Release
To originating exchange
IDLE
IDLE
From offspring
To offspring
Release
Release
Release
To destination exchange
Release
IDLE
IDLE
To destination exchange
Figure 63b: Process MSC_Coord (sheet 2)
History
Document history
Date January 1997 Status Proposed version 2.1.0 Comment Presented to SMG3, Dresden

Basic Call Handling GSM 03.18

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Basic Call Handling GSM 03.18

Diunggah oleh

Hak Cipta:

Format Tersedia

Page 1 GSM 03.18 Version 2.1.

GSM TECHNICAL SPECIFICATION

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

Page 2 GSM 03.18 Version 2.1.0: February 1997

Page 3 GSM 03.18 Version 2.1.0: February 1997 Blank page

Page 4 GSM 03.18 Version 2.1.0: February 1997

Page 7 GSM 03.18 Version 2.1.0: February 1997 Blank page

Page 8 GSM 03.18 Version 2.1.0: February 1997

Page 9 GSM 03.18 Version 2.1.0: February 1997 Blank page

Page 10 GSM 03.18 Version 2.1.0: February 1997

Definitions, symbols and abbreviations

Page 13 GSM 03.18 Version 2.1.0: February 1997

Air I/F signalling BSSA MS

'A' I/F signalling VMSCA

Air I/F signalling

Send Routeing Info/ack Provide Roaming Number/ack

Page 15 GSM 03.18 Version 2.1.0: February 1997

MSA CM service req

BSSA CM service req

Process access req Authenticate (note 1)

Authenticate Authenticate Authenticate resp Authenticate ack

Cipher mode cmd (note 3) Cipher mode comp

Figure 3: Information flow for a basic mobile originated call

HLRB PRN PRN ack SRI ack IAM

Cipher mode command Cipher mode complete

Complete call Setup

Call conf Allocate channel

Assignment command Assignment

Allocation complete ACM

complete Alerting Connect

ANM Connect ack Complete call ack

The network then waits for the call to be cleared.

Page 20 GSM 03.18 Version 2.1.0: February 1997

Principles for interactions with supplementary services

There is no interaction between specification.

Page 22 GSM 03.18 Version 2.1.0: February 1997

Functional requirements of network entities

Page 24 GSM 03.18 Version 2.1.0: February 1997

Process_ Access_ Request_MSC

No Result= Pass? Yes

Convert GSM BC to basic service

Send Info For Outgoing Call

Release call resources

Wait_For_ MO_Call_ Result

Figure 6a: Process OCH_MSC (sheet 1)

Page 25 GSM 03.18 Version 2.1.0: February 1997

Send Info For Outgoing Call negative response

Convert GSM BC to channel requirement

Release Call Resources

Release Call Resources

Wait_For_ Allocation_ Complete

Set_CLI_ Presentation_ Indicator_ MSC

No Result= call allowed?

Towards destination exchange

Release Call Resources

Figure 6b: Process OCH_MSC (sheet 2)

Page 26 GSM 03.18 Version 2.1.0: February 1997

Charging Parameters ack

AoC acknowledgment timer expired

No Acknowledgment required? Yes

Start AoC acknowledgment timer

Release call resources

Figure 6c: Process OCH_MSC (sheet 3)