ETSI TS 123 018 V3.11.

0 (2002-03)
Technical Specification

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Basic call handling; Technical realization (3GPP TS 23.018 version 3.11.0 Release 1999)

R

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

3GPP TS 23.018 version 3.11.0 Release 1999

1

ETSI TS 123 018 V3.11.0 (2002-03)

Reference
RTS/TSGN-0423018UR8

Keywords
GSM, UMTS

ETSI
650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editor@etsi.fr

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 2002. All rights reserved. DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members. TM TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. TM 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
TM TM TM

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

2

ETSI TS 123 018 V3.11.0 (2002-03)

Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http://webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under www.etsi.org/key .

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

3

ETSI TS 123 018 V3.11.0 (2002-03)

Contents
Intellectual Property Rights ................................................................................................................................2 Foreword.............................................................................................................................................................2 Foreword.............................................................................................................................................................7 1 2 3
3.1 3.2

Scope ........................................................................................................................................................8 References ................................................................................................................................................8 Definitions and abbreviations.................................................................................................................10
Definitions........................................................................................................................................................10 Abbreviations ...................................................................................................................................................10

4
4.1 4.2

Architecture............................................................................................................................................11
Architecture for an MO call .............................................................................................................................11 Architecture for an MT call..............................................................................................................................12

5
5.1 5.2 5.3

Information flows...................................................................................................................................12
Information flow for an MO call ......................................................................................................................13 Information flow for retrieval of routeing information for an MT call ............................................................15 Information flow for an MT call ......................................................................................................................16

6
6.1 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.10.1 6.10.2 6.11 6.12 6.13

Principles for interactions with supplementary services ........................................................................19
Call Deflection service (3GPP TS 23.072).......................................................................................................19 Line identification services (3GPP TS 23.081) ................................................................................................19 Calling Line Identification Presentation (CLIP) .........................................................................................19 Calling Line Identification Restriction (CLIR)...........................................................................................19 Connected Line Identification Presentation (COLP) ..................................................................................19 Connected Line Identification Restriction (COLR) ....................................................................................19 Call forwarding services (3GPP TS 23.082) ....................................................................................................19 Call Forwarding Unconditional (CFU) .......................................................................................................19 Call Forwarding on mobile subscriber Busy (CFB) ...................................................................................20 Call Forwarding on No Reply (CFNRy).....................................................................................................20 Call Forwarding on mobile subscriber Not Reachable (CFNRc)................................................................20 Call wait (3GPP TS 23.083).............................................................................................................................20 Call hold (3GPP TS 23.083).............................................................................................................................20 Multiparty (3GPP TS 23.084) ..........................................................................................................................20 Closed user group (3GPP TS 23.085) ..............................................................................................................20 Advice of charge (3GPP TS 23.086) ................................................................................................................20 User-to-user signalling (3GPP TS 23.087).......................................................................................................20 Call barring (3GPP TS 23.088) ........................................................................................................................21 Barring of outgoing calls ............................................................................................................................21 Barring of incoming calls ...........................................................................................................................21 Explicit Call Transfer (3GPP TS 23.091).........................................................................................................21 Completion of Calls to Busy Subscriber (3GPP TS 23.093)............................................................................21 Multicall (3GPP TS 23.135).............................................................................................................................21

7
7.1 7.1.1 7.1.1.1 7.1.1.2 7.1.1.3 7.1.1.4 7.1.1.5 7.1.1.6 7.1.1.7

Functional requirements of network entities ..........................................................................................21
MO call.............................................................................................................................................................22 Functional requirements of serving MSC ...................................................................................................22 Process OCH_MSC...............................................................................................................................22 Procedure Process_Access_Request_MSC ...........................................................................................22 Procedure OG_Call_Setup_MSC..........................................................................................................23 Procedure Obtain_IMSI_MSC..............................................................................................................24 Procedure Authenticate_MSC...............................................................................................................24 Procedure Obtain_IMEI_MSC..............................................................................................................24 Procedure Check_IMEI_MSC ..............................................................................................................24

ETSI

.........................................25 Procedure Handle_AoC_MO_MSC...............2....2....9 7..................2..................................................1......1 7.............49 Procedure Obtain_IMSI_VLR ........................1...............................................................1 7................2................................2........................................................1.............................3..............................104 Procedure Subscription_Check_HLR .2.......13 7....................................2........................................1...................5 7...2...........137 Procedure Prepaging_Page_MS_MSC...................................2........................................................................................3 7..........1 7...............................2.......................................................................................................................................................................................7 7...............................................2.................................122 Process Restore_Subscriber_Data_VLR....5 7......................................................................................................2...2.........50 Procedure Check_IMEI _VLR..............8 7..................8 7................1............9 7...........1.....................137 Prepaging_Search_For_MS_MSC .4 7.....1............................................5 7........2..123 Procedure Retrieve_Current_Location_VLR...............10 7......................3 7................2...........1 7...............................................10 7......................25 Functional requirements of VLR ..........................................6 7..................9 7.........................11 7.........018 version 3....................................................................................8 7........1..................................2................................................................................................................................122 Procedure Retrieve_Location_Info_VLR ...................105 Procedure First_Forwarding_HLR.......1...................2.................................8 7........2.............................................2........................................2 7...50 Procedure Check_BAOC ................1...................................105 Procedure Handle_CFU .................................50 Procedure Get_AoC_Subscription_Info_VLR...................2........................................25 Procedure Send_Access_Connect_If_Required...........3 7...........4 7..105 Procedure Forward_CUG_Check .......123 Functional requirements of MSC.......................................................1......................................................77 Procedure Obtain_Routeing_Address .........11 7........5 7.....1..11 7...................137 Process RCL_MSC ......2...........1...........................2......49 Procedure Obtain_Authentication_Sets_VLR............................................................................................77 Functional requirements of GMSC .............1......................2.......1.............2......1 7...............................2..................................................................49 Procedure Process_Access_Request_VLR .1...............................4..................3........................................................2...................3 Procedure Establish_Originating_TCH_If_Required ..................................4......11..................49 Process OCH_VLR ...................................................................................................................................12 7......................................................2.............................2...........................................2.............................2...........50 Procedure Obtain_IMEI _VLR ...........10 7...................................2..........3..................................1..145 ETSI ....2...............1.............2......................106 Functional requirements of VLR ...............104 Procedure Check_Parameters............105 Procedure IC_CUG_Check .....................4 7............................1..2 7...............137 Process OSI_MSC........2....................................49 Procedure Obtain_Identity_VLR .......1................................................................................................................................................................1....2......2 7.50 Process Update_Location_VLR.105 Procedure PRN_Error_HLR ...........................................7 7..........................105 Procedure Check_IC_Barring ...50 Retrieval of routeing information for MT call..............2..........4 7..............................................122 Process PRN_VLR....................80 Macro CUG_Support_Check_GMSC...................................................2...........................2.........2.................104 Process SRI_HLR .........2....................................................................1.................2........15 7................................................1................79 Procedure Send_ACM_If_Required .....1..............1............1......50 Process Fetch_Authentication_Sets_VLR ............4...2...............................1.....................................................1...............2 7..........................................................................................12 7......................2.........1............................................................................25 Procedure Send_Alerting_If_Required .........................3GPP TS 23.................2 7.....4....................................................1.......................4 7.......................................................3 7..........................25 Procedure Set_CLI_Presentation_Indicator_MSC...3.............................80 Procedure Activate_CF_Process ...................2..........................................................................................................................................................2........................................1................0 (2002-03) 7...........................2.......2 7..........137 Process Prepage_MSC ........50 Procedure Get_LI_Subscription_Info_MO_VLR .........................6 7.....2............2......................1............................2.......2...............3 7.............1..........2.........................1....4 7...........................................................................................................0 Release 1999 4 ETSI TS 123 018 V3.............50 Procedure Start_Tracing_VLR.............................3..............14 7....................................80 Process MT_CF_MSC .7 7.....105 Procedure Derive_Requested_Basic_Service_HLR ............2.......7 7...122 Process PSI_VLR..................................................................13 7.........................77 Process MT_GMSC ................................2....17 7...................2.......................................2................137 MT call ......2.....................................................................2........137 Procedure Current_Location_Search_MSC ......................................79 Procedure Send_Answer_If_Required ....................................................................................................2.2.............................................................................................4.........................49 Procedure Authenticate_VLR ......................9 7.............................................49 Procedure OG_Call_Subscription_Check_VLR ......................................................50 Procedure OG_CUG_Check ...................1.............................................16 7.........................2......2......................1.....................................................................................................................................11..............3 7.........................................................1 7.............................................................4...........................105 Procedure Handle_CFNRc..............................50 Procedure Check_OG_Barring ..79 Procedure Send_Network_Connect_If_Required ......1...137 Procedure Current_Location_Page_MSC ............2.....6 7.........................4......................................................80 Procedure Handle_COLP_Forwarding_Interaction_MSC......................................1....................................................2 7..............................2 7.............................................................................81 Functional requirements of HLR ...............5 7...........2.............................6 7...2.................1........................25 Procedure Set_COLP_Info_MSC ...

...3..................................................................................................................................3..210 Check IMEI ack ..........................1.1.............212 Obtain Subscriber Info..................................................................................................................................................3 7.........................22 8......................................................................194 Messages on the B interface (MSC-VLR)......................15 8.....221 8 8......................1......221 Send Info For Outgoing Call negative response ...........................3 7.............................6 7.................................219 Send Info For Incoming Call ack...................................6 7......................1..3..................................................1......................................................................................1...1.........................................................................1................................1.........................................................................25 8..............................39 8...............1 7.................................................194 Procedure Get_LI_Subscription_Info_MT_VLR ................................20 8........................21 8........................................1...................................................3...............212 Forward New TMSI ack ........213 Page MS................................................1................................1..............................................................................................194 Procedure Handle_CFB ........................219 Send Info For Incoming Call ..............................................10 7....................................30 8...4 7.................................................................................0 (2002-03) 7..................................................................................................35 8.......215 Process Access Request negative response...............................................................1........................................218 Search for MS via SGSN ..........................................................................................1.........................1....................................................................................218 Radio connection released ....210 Authenticate negative response..........................................................3........................................................................................209 Abort...........216 Process Call Waiting ack ....................................11.1...212 Forward New TMSI.............................0 Release 1999 5 ETSI TS 123 018 V3...............................1 7........................................................................................................................................2....................................................7 Functional requirements of serving MSC ......................1....................213 Page MS via SGSN.......................1.................................................217 Provide IMSI ack...............28 8.........10 8..................1...................................................................1.2 7................................145 Procedure Page_MS_MSC.....221 Send Info For Outgoing Call.....36 8.........................1...................................................151 Procedure Handle_AoC_MT_MSC ..................33 8...............................................................................................................................................................................................................................3.................1.....................151 Functional requirements of VLR ...........................................7 7........148 Procedure Process_Call_Waiting_MSC........................216 Provide IMEI ack................................................1..........26 8..............4 7.................................................................................1.................................................1.......................................9 7..........209 ETSI ................................................................215 Process Access Request ack..........1..............................................................................................................213 Page MS negative response .......................................3GPP TS 23...............215 Process Access Request ................2............................................................................................................................................................................................218 Search For MS ack..............151 Procedure Set_COL_Presentation_Indicator_MSC .................................16 8...........3......................216 Process Call Waiting negative response ..............................................................3.............212 Forward New TMSI negative response .....................................11 8........................................................................................................3..................................................................................................................................018 version 3.........................2.............................................................210 Check IMEI negative response .................8 7......1...............................................................................3.........11..........194 Procedure Get_CW_Subscription_Info_VLR...............................193 Process ICH_VLR..........................................5 8...209 Authenticate ack ....2..................................3......1..............3........1.....................................2.......................194 Procedure Search_For_MS_VLR .....................151 Procedure Establish_Terminating_TCH_If_Required ............23 8..............................................216 Process Call Waiting.....................................212 Complete Call negative response.......................................................................................................................................3....................................................................................................................................................5 7.................1............................................................38 8................................................................................1...........................29 8.............3 8..................1...218 Search For MS negative response.....................32 8.................37 8..194 Procedure Handle_CFNRy.........................24 8.......................17 8.......................218 Search For MS .............217 Provide IMSI ...............................149 Procedure Set_CLIP_Info_MSC....................................................220 Send Info For Incoming Call negative response .......................................................1.....................................3.........................................216 Provide IMEI ..........1.....1...1...........................................................1............................151 Procedure Derive_GSM_BC_MSC ..............213 Obtain Subscriber Info ack .............................12 8.............................................................1................................................5 7..................13 8..18 8...............27 8............3..1................................19 8..31 8...1..................................................1........210 Call arrived .................3.................210 Check IMEI ...1..........193 Procedure Derive_Requested_Basic_Service_VLR ...............................7 8....................4 8......................................1.......2 7..................1...................................................................................213 Page MS ack .............................3....9 8.......................................3.........147 Procedure Search_For_MS_MSC .2....2 7...................1 8..................40 Contents of messages ...................................................................1...........................210 Complete Call ....................................................................................................................................................................2................................................................2 8...................................................6 8......................................................................................145 Process ICH_MSC .................................................................................14 8.................................................8 8..34 8............1......1 7........1 8..................148 Procedure Complete_Call_In_MSC...1..............1............................................1..............3.....209 Authenticate.........................................................................................1.................................210 Complete Call ack...........................

.....................................................................................................................................................................................3 8....................................................227 Provide Subscriber Info ack.........................................................................42 8..................226 Provide Roaming Number ack....................................................................224 Send Routeing Info negative response.............................................1 8..................1 8...........................7.......................................................230 Perform Call Forwarding ack.....................................2 8................5............................................................231 Annex A (informative): Handling of an IAM at an MSC ............................................230 PAR completed ...............................3............3 8.0 (2002-03) 8..........................................................................1................................................................................................................1 8........5 8.....230 Perform Call Forwarding .............................................................................................................229 Check IMEI ...2 8..................41 8........................................4...............226 Provide Roaming Number negative response .................................................................................................1 8................................................................................228 Restore Data ack .....5.........................4 8.1 8...........5.............................3..................................4 8....226 Provide Roaming Number ...........3 8.................................................................................43 8......................................................................7...................222 Messages on the C interface (MSC-HLR).229 Messages on the F interface (MSC-EIR)...................................................3 8.................................6...............................................230 Messages on the Gs interface .......................................2 8...................................5 8.230 Call arrived .......7......................1................................................................................7..............231 Send MS information ack ...........225 Messages on the D interface (VLR-HLR) .....................................................235 History ...............................................................3GPP TS 23..........3 8..........................................1 8..............3.......................3...........2 8..............2...........................................................................................237 ETSI ..................229 Restore Data negative response ....................2 8...............229 Check IMEI ack .......4.......3..................231 Page MS...........................5..............................................................................................................................................................................................................................................................................................2........................................................................................11......................9 8..............................................226 Provide Subscriber Info ..............................................................................229 Check IMEI negative response .....4 8.....................6 8..........................7 8.................................................................................................................3....................................................................................3..............................2......................................................223 Send Routeing Info ack...............................................................................230 Messages on the VLR internal interface....................................................................4........8 8......228 Restore Data..............................................222 Use existing TMSI ...228 Provide Subscriber Info negative response ....................................................................................2 8..5............................................................................................................3.....................................................................231 Send MS information negative response ...........................................................223 Send Routeing Info ...........7 8............................................................................................................3...............................................................................222 Trace subscriber activity .................................................................................................................................................230 Perform Call Forwarding negative response..........................................................................11...........6...........................................................1.....................................2 8............230 CF cancelled ...4 Start security procedures..231 Send MS information...3 8..............................1 8..........................................6 8.............................................232 Annex B: Change history .........................018 version 3..3..................................................229 Messages on the MSC internal interface ..227 Location information...........................................................................................0 Release 1999 6 ETSI TS 123 018 V3................................

corrections. ETSI .11.018 version 3.0 (2002-03) Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). etc. y the second digit is incremented for all changes of substance. i. The present document specifies the technical realisation of the handling of calls originated by a 3G mobile subscriber and calls directed to a 3G mobile subscriber. z the third digit is incremented when editorial only changes have been incorporated in the specification. it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.11. Should the TSG modify the contents of the present document.3GPP TS 23.e. 2 presented to TSG for approval. technical enhancements. up to the point where the call is established within the 3GPP system.z where: x the first digit: 1 presented to TSG for information.0 Release 1999 7 ETSI TS 123 018 V3. 3 Indicates TSG approved document under change control.y. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval.. updates.

version number.07x.11. edition number.09x series of specifications.08x and 23. In the present document.079 [13]). 3GPP TS 25.3GPP TS 23. 3GPP TS 23. but is required for both CAMEL (3GPP TS 23.Stage 2 ". 3GPP TS 23. GSM 12. Service description. the latest version applies. GSM 08.079 [13]. [1] [2] [3] [4] [5] [6] [7] [8] [9] GSM 03. GSM 08. The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling.002 [28]).018 version 3. ETSI .003: "Numbering.054 [8]. 2 References • References are either specific (identified by date of publication. 5 and 7). Stage 2". Normal release of the call after establishment is also specified. The following documents contain provisions which.Base Station System (MSC .BSS) interface Layer 3 specification".008 [25].060: "General Packet Radio Service. 3GPP TS 23.905: " Vocabulary for 3GPP Specifications ". They do not impose any requirement except the definition of the externally visible behaviour. which is a single physical entity. 3GPP TS 23.20: " Digital cellular telecommunications system (Phase 2+). constitute provisions of the present document.413 [26].11. 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. The handling of DTMF signalling and Off-Air Call set-up (OACSU) are not described in the present document. a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. Mobile-services Switching Centre . The specification of the handling of data calls re-routed to a SIWFS is described in 3GPP TS 23. 3GPP TS 23. The logical separation of the MSC and VLR (shown in clauses 4.0 (2002-03) 1 Scope The present document specifies the technical realisation of the handling of calls originated by a UMTS or GSM mobile subscriber and calls directed to a UMTS or GSM mobile subscriber.0 Release 1999 8 ETSI TS 123 018 V3. 3GPP TR 21. Addressing and Identification". The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the relevant 23. as appropriate. the term MS is used to denote a UMTS or GSM MS. 23.08: "Digital cellular telecommunications system (Phase 2+). • For a non-specific reference. the stage 3 specification shall prevail.08 [2] and 3GPP TS 29.078 [12]) and optimal routeing (3GPP TS 23. through reference in this text. Security related network functions". subsequent revisions do not apply. • For a specific reference.08: "Digital cellular telecommunications system (Phase 2+).) or non-specific. The use of the Provide Subscriber Information message flow is shown in 3GPP TS 23. Subscriber and equipment trace". In the case of a reference to a 3GPP document (including a GSM document). up to the point where the call is established.012: "Location Management Procedures". etc. If there is any conflict between the present document and the corresponding stage 3 specifications (3GPP TS 24.078 [12] and 3GPP TS 23.054: "Shared Inter Working Function (SIWF) .032: "Universal Geographical Area Description (GAD)".

ITU-T Recommendation Q. 3GPP TS 24. 7 . 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Service .082: "Call Forwarding (CF) Supplementary Services .762 (1999): "Signalling System No.11. 3GPP TS 23. Core Network Protocols-Stage 3".Stage 2". ITU-T Recommendation Q. 3GPP TS 23.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)".Stage 2".Base Station System (MS . Stage2".MSC) Signalling Procedures and the Mobile Application Part (MAP)". Stage 2". 1 and the Signalling System No.072: "Call Deflection (CD) supplementary service. Security Architecture ".093: "Technical realisation of Completion of Calls to Busy Subscriber (CCBS) Stage 2". 3GPP TS 33. 3GPP TS 29.Stage 2".002: "Mobile Application Part (MAP) specification".007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".11. 3GPP TS 27.761 (1999): " Signalling System No.Stage 2".763 (1999): "Signalling System No.066: "Support of Mobile Number Portability (MNP).413: "UTRAN Iu Interface RANAP Signalling". Technical Realisation – Stage 2" 3GPP TS 23.010: "Information Element Mapping between Mobile Station .850 (1996): "Usage of cause and location in the Digital Subscriber Signalling System No. 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Service . Stage 2".ISDN user part signalling procedures".3GPP TS 23. 7 ISDN User Part". 7 . 3GPP TS 23.ISDN User Part formats and codes".087: "User –to-User Signalling (UUS) Supplementary Service .079: "Support of Optimal Routeing (SOR). Stage 2". 3GPP TS 23. 3GPP TS 23.018 version 3. ITU-T Recommendation Q.085: "Closed User Group (CUG) Supplementary Service . ITU-T Recommendation Q. 7 .0 Release 1999 9 ETSI TS 123 018 V3.008: "Mobile Radio Interface Layer 3 specification. 3GPP TS 23.ISDN User Part functional description ".102: "3G Security.081: "Line identification Supplementary Services .Stage 2".088: "Call Barring (CB) Supplementary Service .0 (2002-03) [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] 3GPP TS 23. [30] [31] [32] [33] [34] [35] [36] ETSI . 3GPP TS 29. 3GPP TS 23.BSS) and Base Station System .Mobile-services Switching Centre (BSS .764 (1999): " Signalling System No.078: "Customized Applications for Mobile network Enhanced Logic (CAMEL) Phase 3. 3GPP TS 23.116: "Super-Charger Technical Realisation.Stage 2".ISDN User Part general functions of messages and signals".Stage 2 ". 7 .083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services . 3GPP TS 23. 3GPP TS 23.135: "Multicall supplementary service. 3GPP TS 25. ITU-T Recommendation Q. 3GPP TS 29. Technical Realisation".Stage 2". 3GPP TS 23.

the PLMN containing GMSCB IWU Inter Working Unit LLC Lower Layer Compatibility MO Mobile Originated MPTY MultiParTY MT Mobile Terminated NDUB Network Determined User Busy NRCT No Reply Call Timer ETSI . B subscriber: The mobile subscriber originally called by the A subscriber. 3.1 Definitions and abbreviations Definitions For the purposes of the present document. C subscriber: The subscriber to whom the B subscriber has requested that calls be forwarded. The C subscriber may be fixed or mobile. the following abbreviations apply: A&O Active & Operative ACM Address Complete Message ANM ANswer Message AoC Advice of Charge BC Bearer Capability BOIC-exHC&BOIZC Barring of Outgoing International Calls except those directed to the HPLMN Country & Barring of Outgoing InterZonal Calls BOIZC Barring of Outgoing InterZonal Calls BOIZC-exHC Barring of Outgoing InterZonal Calls except those directed to the HPLMN Country CCBS Completion of Calls to Busy Subscriber CFB Call Forwarding on Busy CFNRc Call Forwarding on mobile subscriber Not Reachable CFNRy Call Forwarding on No Reply CFU Call Forwarding Unconditional CLIP Calling Line Identity Presentation CLIR Calling Line Identity Restriction COLP COnnected Line identity Presentation COLR COnnected Line identity Restriction CS BC Circuit-Switched Bearer Capability CUG Closed User Group CW Call Waiting FTN Forwarded-To Number FTNW Forwarded-To NetWork GMSCB Gateway MSC of the B subscriber GPRS General Packet Radio Service HLC Higher Layer Compatibility HLRB The HLR of the B subscriber HPLMNB The HPLMN of the B subscriber IAM Initial Address Message IPLMN Interrogating PLMN . Circuit-Switched Bearer Capability: The information transferred over the UMTS or GSM access interface to define the information transfer capabilities to be used between the MS and the network for a circuit-switched connection.018 version 3. the following definitions apply: A subscriber: The calling mobile subscriber.2 Abbreviations For the purposes of the present document. Location Information: Information to define the whereabouts of the MS.11.3GPP TS 23.11.0 (2002-03) 3 3. and the age of the information defining the whereabouts.0 Release 1999 10 ETSI TS 123 018 V3.

0 (2002-03) PRN SGSN SIFIC SIFOC SIWF SIWFS SRI UDUB VLRA VLRB VMSCA VMSCB VPLMNA VPLMNB Provide Roaming Number Serving GPRS support node Send Information For Incoming Call Send Information For Outgoing Call Shared Inter Working Function SIWF Server. 4. In figure 1 and throughout the present document. it responds with a Complete Call. When the user of an MS wishes to originate a call. as indicated in figure 1. In a given network. over an internal interface of the MSC/VLR.3GPP TS 23.1 and 4. VMSCA requests information to handle the outgoing call (SIFOC) from VLRA. 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 4 Architecture Subclauses 4.018 version 3. as appropriate. any telephony signalling system may be used. VMSCA: establishes a traffic channel to the MS. the MS establishes communication with the network using radio interface signalling. between the VMSC and the VLR and between the VMSC and the destination exchange.11. the term ISUP is used to denote the telephony signalling system used between exchanges.0 Release 1999 11 ETSI TS 123 018 V3.11. SIWFS is the entity where the used IWU is located. If VLRA determines that the outgoing call is allowed. and sends a message containing the address of the called party. Radio I/F signalling MS BSSA Iu or A I/F signalling VMSCA IAM (ISUP) SIFOC Complete call VPLMNA VLRA Figure 1: Architecture for a basic mobile originated call In figure 1 and throughout the present document.1 Architecture for an MO call A basic mobile originated call involves signalling between the MS and its VMSC via the BSS. A basic mobile-tomobile call is treated as the concatenation of an MO call and an MT call. ETSI . and constructs an ISUP IAM using the called party address and sends it to the destination exchange.2 show the architecture for handling a basic MO call and a basic MT call. the term BSS is used to denote a GSM BSS or a UTRAN.

0 Release 1999 12 ETSI TS 123 018 V3. VMSCB informs VLRB in the Page ack message.060 [9]) and there is an association between VLRB and the SGSN for the MS. VMSCB pages the MS using radio interface signalling.0 (2002-03) NOTE: When the non-loop method is used for data calls. 5 Information flows In this clause and clause 7. is in principle distinct from HPLMNB. and VMSCB establishes a traffic channel to the MS. containing GMSCB. VLRB instructs VMSCB to connect the call in the Complete call. the IAM is sent to the SIWFS. but the practice for at least the majority of current UMTS or GSM networks is that a call to an MS will be routed to a GMSC in HPLMNB.102 [31] or the GSM ciphering mechanism defined in GSM 03. When VMSCB receives the IAM. 4. the terms "security procedures" and "security control" denote the UMTS ciphering and integrity protection mechanism defined in 3GPP TS 33. The IPLMN. it requests routeing information from HLRB using the MAP protocol. containing HLRB. ETSI . as for the mobile originated case.11. it requests information to handle the incoming call (SIFIC) from VLRB. it requests VMSCB to page the MS. the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS.018 version 3. and VLRB returns a roaming number in the Provide Roaming Number Ack. If VLRB determines that the incoming call is allowed. Communication between VMSCB and the MS is via the BSS. HLRB returns the roaming number to GMSCB in the Send Routeing Info ack. also using the MAP protocol. When the MS responds. which it sends to VMSCB. HLRB requests a roaming number from VLRB.2 Architecture for an MT call A basic mobile terminated call involves signalling as indicated in figure 2.20 [1]. GMSCB uses the roaming number to construct an ISUP IAM. over an internal interface of the MSC/VLR.3GPP TS 23. as appropriate.11. IAM (ISUP) IPLMN GMSCB IAM (ISUP) VMSCB SIFIC Page/ack Complete call VLRB BSSB Radio I/F signalling MS VPLMNB Send Routeing Info/ack Provide Roaming Number/ack HLRB HPLMNB Figure 2: Architecture for a basic mobile terminated call When GMSCB receives an ISUP IAM. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see 3GPP TS 23.

018 version 3.3GPP TS 23.11.11. MSA BSSA VMSCA VLRA CM service req CM service req Process access req Authenticate (note 1) Authenticate Authenticate resp Authenticate Authenticate resp Authenticate ack Start security procedures (note 2) Process access req ack Security control cmd (note 3) Security control rsp Start security procedures (note 3) Security procedures complete Setup SIFOC Call proceeding Allocate channel Complete call Assignment cmd Assignment comp Allocation complete IAM ACM ANM Alert Connect Connect ack Figure 3: Information flow for a basic mobile originated call ETSI .1 Information flow for an MO call An example information flow for an MO call is shown in figure 3. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between BSSA and VMSCA is shown by dashed lines. Signalling over the radio interface between MSA and BSSA or VMSCA is shown by dotted lines.0 Release 1999 13 ETSI TS 123 018 V3. signalling over the B interface between VMSCA and VLRA is shown by chain lines. many variations are possible.0 (2002-03) 5. and ISUP signalling between VMSCA and the destination exchange is shown by solid lines.

102 [31] for UMTS GSM 03. which relays it to VMSCA. VLRA may then initiate authentication. at any stage during the establishment of an MO call. If VMSCA has received a Start security procedures message from VLRA.0 (2002-03) NOTE 1: Authentication may occur at any stage during the establishment of an MO call. to trigger BSSA and MSA to set up a traffic channel over the radio interface. If BSSA receives a Start security procedures message from VMSCA. it sends a Complete Call message to VMSCA. When the destination exchange returns an ISUP ANswer Message (ANM).11. VLRA may also initiate security procedures at this stage. Details of the handling are shown in clause 7. VMSCA translates this bearer capability into a basic service. and may check the IMEI. either as part of the procedure to start security procedures or explicitly after security procedures have started. When MSA has received the CM Service Accept. It is a network operator option whether to allow an emergency call when the mobile identifies itself by an IMEI. MSA also uses the Set-up message to indicate the bearer capability required for the call. When the traffic channel assignment process is complete (indicated by the Allocation complete message from BSSA to VMSCA).20 [1] for GSM. This option is not available for a UMTS connection [ffs]. If VLRA determines that MSA is allowed service. it initiates security procedures as described in 3GPP TS 33. The Call Proceeding message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be changed.102 [31] for UMTS and GSM 03. as described in 3GPP TS 33. If VLRA determines that the call should be connected. VMSCA sends a Process Access Request to VLRA. to instruct MSA to connect the speech path. otherwise VMSCA sends a CM Service Accept message towards BSSA. or security procedures have been successfully initiated. to indicate to the calling user that the B subscriber is being alerted. and sends an Allocate channel message to BSSA. its position in this message flow diagram is an example. the Process Access Request ack message triggers a Start security procedures message towards BSSA.0 Release 1999 14 ETSI TS 123 018 V3. and the mobile may identify itself by an IMEI. MSA sends a CM service request through the existing signalling connection for each new call. NOTE 3: If ciphering is not required for a GSM connection. the position in this message flow diagram is an example. When the destination exchange returns an ISUP Address Complete Message (ACM). ETSI . this is not shown in this message flow diagram. For an emergency call. and sends it to the destination exchange. using a Send Info For Outgoing Call (SIFOC) message containing the B subscriber address. VMSCA sends an Alerting message via BSSA to MSA. MSA interprets this in the same way as a CM Service Accept. VMSCA sends a Call Proceeding message via BSSA to MSA. a different CM service type (emergency call) is used. If the user originates one or more new MO calls in a multicall configuration.102 [31] for UMTS and GSM 03. to indicate that the call request has been accepted. as described in 3GPP TS 33. NOTE 2: Security procedures may be initiated at any stage after authentication. MSA establishes a signalling connection with BSSA.018 version 3.20 [1] for GSM. the MSC may send a CM service accept towards the MS. VMSCA sends to VLRA a request for information to handle the outgoing call.11. The network then waits for the call to be cleared.3GPP TS 23. and sends a Connection Management (CM) service request to BSSA. it sends a Process Access Request ack to VMSCA. If security procedures are not required at this stage. optionally it may instead send a "start ciphering" request indicating that no ciphering is required. MSA sends a Set-up message containing the B subscriber address via BSSA to VMSCA. NOTE 4: The network may request the IMEI from the MS. when security procedures have been successfully initiated. BSSA relays the CM Service Accept to MSA. When the user wishes to originate a call. and determines whether an interworking function is required. VMSCA constructs an ISUP IAM using the B subscriber address.20 [1] for GSM. VMSCA sends a Connect message via BSSA to MSA.

ETSI . If GMSCB supports pre-paging (i.0 (2002-03) 5. it analyses the called party address. ISUP signalling between the originating exchange and GMSCB. it indicates this by an information element in the SRI message.0 Release 1999 15 ETSI TS 123 018 V3. VMSCB releases the radio resource allocated for the MT call if the timer expires before the IAM is received. it is prepared to wait long enough for the SRI ack to allow pre-paging to be completed). NOTE 2: VMSCB starts the timer for the release of radio resources after it sends the Process Access Request message to VLRB. If GMSCB can derive an HLR address from the B party address. paging is initiated after VLRB has accepted the PRN message. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines. GMSC IAM SRI PRN Page MS Page Page Chan req Imm ass Page resp MS conn Process PRN ack SRI ack access req (note 2) Start security procedures Process access req ack Start security procedures Security control command Security control response IAM estab (note 1) HLRB VLRB VMSCB BSSB MSB Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call NOTE 1: If pre-paging is used.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.3GPP TS 23. signalling over the MAP interfaces between GMSCB and HLRB and between HLRB and VLRB. and between GMSCB and VMSCB is shown by solid lines. and signalling over the radio interface between BSSB and MSB is shown by dotted lines.11. When GMSCB receives an IAM.3.018 version 3. The paging procedure is described in subclause 5. it sends a request for routeing information (SRI) to HLRB.11.e. and over the B interface between VLRB and VMSCB is shown by chain lines.

and HLRB relays the roaming number to GMSCB in the SRI ack. if pre-paging is supported. it indicates this by an information element in the PRN message.3GPP TS 23.3 Information flow for an MT call An example information flow for an MT call is shown in figure 5. it is prepared to wait long enough for the PRN ack to allow pre-paging to be completed). many variations are possible. VLRB returns the roaming number in the PRN ack.11. GMSCB constructs an IAM using the roaming number. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines.11.0 Release 1999 16 ETSI TS 123 018 V3. and HLRB supports pre-paging (i. and sends it to VMSCB. HLRB sends a request for a roaming number (PRN) to VLRB. 5.018 version 3.0 (2002-03) HLRB decides whether pre-paging is supported according to the following criteria: GMSCB has indicated that it supports pre-paging. ETSI . signalling over the B interface between VMSCB and VLRB is shown by chain lines. ISUP signalling between GMSCB and VMSCB is shown by solid lines.e. and signalling over the radio interface between VMSCB or BSSB and MSB is shown by dotted lines.

3GPP TS 23. NOTE 2: If Security procedures are not required.11.0 Release 1999 17 ETSI TS 123 018 V3. the position in this message flow diagram is an example.018 version 3.11.0 (2002-03) GMSCB IAM VLRB SIFIC Page MS VMSCB BSSB MSB Page Page Chan req Imm ass Process access req Start security proc (note 1) Process access req ack MS conn estab Page resp Start security procedures (note 2) Security control command Security control response Call arrived (note 6) Complete call (note 5) Setup Call conf Allocate channel Allocation complete Assignment command Assignment complete Alerting Connect Connect ack ACM ANM Complete call ack Figure 5: Information flow for a basic mobile terminated call NOTE 1: Security procedures may be initiated at any stage after the network has accepted the page response. the MSC may send a Start security procedures message indicating that no ciphering is required. ETSI .

VLRB may also initiate security procedures at this stage. When VMSCB receives an IAM from GMSCB it sends to VLRB a request for information to handle the incoming call. ETSI . VMSCB sends a Process access request message to VLRB to indicate that MSB has responded to paging. VMSCB sends a page request to BSSB. NOTE 5: If a connection between MSCB and MSB has been established as a result of pre-paging. The Process access request ack message triggers a Start security procedures message towards BSSB. as described in 3GPP TS 33. If no radio connection exists. The Set-up message may include bearer capability information for the call.102 [31] for UMTS and GSM 03. The Call Confirmed message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be changed. as described in 3GPP TS 33. VMSCB sends an ACM to GMSCB. if VMSCB has not received a Start security procedures message from VLRB. and sends an Alerting message to indicate that the called user is being alerted. this is not shown in this message flow diagram. it sends a Process access request ack to VMSCB. it sends a channel request to BSSB. NOTE 4: The network may request the IMEI from the MS. and BSSB broadcasts the page on the paging channel. If VLRB recognises the roaming number.11. VMSCB sends a Set-up message towards MSB. it responds with a Call confirmed message. When VMSCB receives the Call confirmed message via BSSB. message. If a radio connection between the network and MSB is already established. which responds with an immediate assignment command. which relays it to the originating exchange. which BSSB relays to VMSCB as an Allocation complete. The network then waits for the call to be cleared. VLRB sends the Call arrived message to MSCB to stop the guard timer for the release of the radio connection. which BSSB relays to VMSCB. the network may initiate authentication after the MS responds to paging. VLRB may then initiate authentication.102 [31] for UMTS and GSM 03. When MSB has tuned to the specified traffic channel it responds with an Assignment complete. the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS. the paging procedure is not performed.018 version 3.0 Release 1999 18 ETSI TS 123 018 V3. and may check the IMEI. which relays it to the originating exchange. using a Send Info For Incoming Call (SIFIC) message containing the roaming number received in the IAM. If this is not so (for the first MT call after VLR restoration).060 [9]) and there is a valid association between VLRB and the SGSN for the MS. sends an ANM to GMSCB. it sends an Allocate channel message to BSSB. MSB then sends a page response on the signalling channel. and MSB is allowed service.11.20 [1] for GSM. either as part of the procedure to start security procedures or explicitly after security procedures have been started. When MSB receives the Set-up message from BSSB.0 (2002-03) NOTE 3: This message flow diagram assumes that the MS has already been authenticated on location registration. If VLRB determines that MSB is allowed service. If MSB detects the page. sends a Complete call ack to VLRB. at any stage after the MS responds to paging.3GPP TS 23. VMSCB: responds with a Connect ack message towards MSB. the Start security procedures message indicates no ciphering. VMSCB responds immediately to the page request.20 [1] for GSM. NOTE 6: If a connection between MSCB and MSB has been established as a result of pre-paging. MSB sends a Connect message. When the called user answers. BSSB instructs MSB to tune to a traffic channel by sending an Assignment command. BSSB relays this to VMSCB. it sends a request to VMSCB to page MSB. VLRB then sends a Complete call message to VMSCB. to instruct MSB to use the specified signalling channel. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see 3GPP TS 23.

Exceptions to this general principle are described later in this clause.2 6.3.082) Call Forwarding Unconditional (CFU) The basic call handling process SRI_HLR interacts with the process MAF007(3GPP TS 23.11. In the modelling used in the present document.1 and 7.3.0 Release 1999 19 ETSI TS 123 018 V3.3 6.2 and 7.2. they are therefore outside the scope of the present document. which handles data in the entity in which it runs.1 Call forwarding services (3GPP TS 23. each supplementary service which a network entity supports is managed by a supplementary service handler.1.0 (2002-03) 6 Principles for interactions with supplementary services This clause specifies the principles used to describe the invocation of the GSM supplementary services which were standardised when the present document was drafted.081) Calling Line Identification Presentation (CLIP) The basic call handling processes ICH_VLR and ICH_MSC interact with the processes CLIP_MAF001 and CLIP_MAF002 (3GPP TS 23. it bypasses the interaction with the handler for that supplementary service.4 Connected Line Identification Restriction (COLR) The basic call handling processes ICH_VLR and ICH_MSC interact with the processes COLR_MAF040 and COLR_MAF041 (3GPP TS 23.1.3.2.081 [14]) as described in subclauses 7. If a network entity does not support a supplementary service. 6.3GPP TS 23.1 and 7. 6.2 ETSI .3.3. 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 (3GPP TS 23.3. 6. 6.081 [14]) as described in subclauses 7.3.1.018 version 3.1. The call handling processes defined in the present document use the data to define the contents of messages to other entities.2. 6. deactivation and interrogation are call-independent operations.2 and 7.2.1 and 7.082 [15]) as described in subclause 7.1 Line identification services (3GPP TS 23.3.2. erasure.11.072 [11]) as described in subclauses 7.1 and 7.072) The basic call handling processes ICH_MSC and ICH_VLR interact with the CD supplementary service (3GPP TS 23.1.1 Call Deflection service (3GPP TS 23.2.081 [14]) as described in subclauses 7.081 [14]) as described in subclauses 7.2. Registration.2 Calling Line Identification Restriction (CLIR) The basic call handling processes OCH_MSC and OCH_VLR interact with the processes CLIR_MAF004 and CLIR_MAF003 (3GPP TS 23. The basic call handling processes MT_GMSC and ICH_MSC interact with the process COLP_MAF039 [14] as described in subclauses 7.1. Descriptions may be found in the stage 2 specifications for each supplementary service.2. The basic call handling processes defined in the present document interact with the supplementary service handlers as shown in the SDL diagrams and the supporting text.2 respectively. activation.

085 [18]) as described in subclause 7.2 and 7. MT_GMSC and ICH_MSC interact with the UUS supplementary service as described in subclauses 7.4 Call wait (3GPP TS 23.3.018 version 3. OCH_VLR.1 and 7.6 Multiparty (3GPP TS 23.3 Call Forwarding on No Reply (CFNRy) The basic call handling process ICH_VLR interacts with the process MAF009 (3GPP TS 23.1 and 7.2.1. 7.085) The basic call handling process OCH_VLR interacts with the process CUG_MAF014 (3GPP TS 23.0 (2002-03) 6.2.3.2 6.3.2.083) The basic call handling process ICH_VLR interacts with the process MAF013 (3GPP TS 23.1 respectively.2.086 [19]) and MT calls are handled as described in subclauses 7.3.082 [15]) as described in subclause 7. 6.085 [18]) are handled as described in subclause 7.1 and 7.2.083) Invocation of call hold before a basic call has been established will be rejected.2.11.3.1.1.1.3GPP TS 23.6.0 Release 1999 20 ETSI TS 123 018 V3.085 [18]) as described in subclause 7.2.8 Advice of charge (3GPP TS 23.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) The basic call handling processes SRI_HLR and ICH_VLR interact with the process MAF010 (3GPP TS 23.2.1 and 7. 6.2. 6.3.2. The interactions between Advice of Charge (3GPP TS 23.11.086 [19]) and MO calls are handled as described in subclauses 7.1.087) The basic call handling processes OCH_MSC.3.083 [16]) as described in subclause 7. ETSI .9 User-to-user signalling (3GPP TS 23.2. 7.2 6.3.3.3.1.2 Call Forwarding on mobile subscriber Busy (CFB) The basic call handling process ICH_VLR interacts with the process MAF008 (3GPP TS 23. Further details of the handling of call waiting are given in subclauses 7.7 Closed user group (3GPP TS 23.2 6.3.5 Call hold (3GPP TS 23. The interactions between call forwarding and CUG (3GPP TS 23.082 [15]) as described in subclauses 7. 6. The basic call handling process SRI_HLR interacts with the process CUG_MAF015 (3GPP TS 23.084) Invocation of multiparty before a basic call has been established will be rejected.086) The interactions between Advice of Charge (3GPP TS 23.2.082 [15]) as described in subclause 7. 6.

2 Barring of incoming calls The basic call handling process SRI_HLR interacts with the processes MAF022 and MAF023 (3GPP TS 23.1. Q. For the purposes of the present document.10 6. 6. 7. 7.12 Completion of Calls to Busy Subscriber (3GPP TS 23. D & F interfaces is MAP.2respectively.088 [21]) as described in subclause 7.0 Release 1999 21 ETSI TS 123 018 V3. which is specified in GSM 08.091) There is no interaction between Explicit Call Transfer and the basic call handling described in the present document.002 [28]. The protocols used over the Iu interface are RANAP.2. The C.1. 6. The entities described in this clause interwork with other entities over four different types of interface: The Iu interface.0 (2002-03) 6. which is specified in 3GPP TS 24. which is specified in 3GPP TS 24.093) The basic call handling processes OCH_MSC.088 [21]) as described in subclause 7. it does not duplicate the information in the SDL diagrams. used to interwork between the MSC and the UTRAN or the UMTS MS.3. 7. other telephony signalling systems may be used instead. used to interwork between an MSC and another exchange.1. 7.2.1 and 7. ETSI .11.1.761[32]. D & F interfaces. VLR & HLR (D) and MSC & EIR (F).1. the protocol used over telephony signalling interfaces is ISUP.11 Explicit Call Transfer (3GPP TS 23.11. 7. Q. MAF018 and MAF020 (3GPP TS 23.764 [35]. 7.1.008 [25].10.1. The A interface.13 Multicall (3GPP TS 23. 7.1 Call barring (3GPP TS 23.2. which is specified in ITU-T Recommendations Q. The protocols used over the A interface are BSSMAP. 6.10.2. which is specified in 3GPP TS 29. used to interwork between the MSC and the GSM BSS or the GSM MS. for interworking with the BSS and DTAP. MT_GMSC.3GPP TS 23. OCH_VLR.1 and 7. Telephony signalling interfaces.3. PRN_VLR. 7 Functional requirements of network entities The text in this clause is a supplement to the definition in the SDL diagrams.2.3. used to interwork between the MSC & HLR (C). SRI_HLR. OCH_VLR.08 [2]. for interworking with the MS. ICH_MSC and ICH_VLR interact with the CCBS supplementary service as described in subclauses 7.2.413 [26]. The protocol used over the C.2.018 version 3.088) Barring of outgoing calls The basic call handling process OCH_VLR interacts with the processes MAF017. ICH_MSC & ICH_VLR interact with the Multicall supplementary service as described in subclauses subclauses 7.008 [25]. for interworking with the UTRAN and DTAP. which is specified in 3GPP TS 25.2respectively. for interworking with the MS.135) The basic call handling processes OCH_MSC.3. 6.1.763 [34] and Q.3.2.762 [33].2.

e. the text associated with each SDL diagram specifies the handling which applies if the entity does not support an optional feature or service. Sheet 2: The Start security procedures message may indicate one of several ciphering algorithms.11.010 [30]. they are specified in 3GPP TS 23. it relays the IAM to a destination exchange determined by analysis of the called party address. If the HLR returns routeing information. the MSC uses the routeing information from the HLR to construct an IAM. The SDL diagrams in this clause show the handling for a number of optional features and services. it attempts to connect the call to an MS currently registered in the service area of the MSC. Sheet 2. the message is saved for processing after the access request has been handled. it interrogates an HLR for information to route the call.093 [22]. Each protocol defines supervision timers. the BSS relays the response in the Security procedures complete message to the MSC. the MS may terminate the transaction with the network by sending a CM service abort message. 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.018 version 3.0 Release 1999 22 ETSI TS 123 018 V3. This behaviour is not specific to UMTS or GSM. ETSI . If the handling consists of more than a call to a procedure specific to the feature or service.1.e. The procedures CCBS_Report_Not_Idle and CCBS_Check_Last_Call are specific to CCBS. and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. the VMSC may encapsulate the request for the IMEI in the Start security procedures message. If the handling consists only of a call to a procedure specific to the feature or service. Sheet 2. it is assumed that support for Operator Determined Barring and the Call Forwarding and Call Barring supplementary services is mandatory.3GPP TS 23.0 (2002-03) The present document shows the call handling application processes interworking with a protocol handler for each of the protocols listed above.1. sheet 3: At any stage.e. therefore. i.1 7. It acts as a terminating exchange. it is an application timer rather than a protocol timer.1. or (for GSM only) no ciphering. For simplicity of description.1. which it sends to a destination exchange determined by analysis of the routeing information from the HLR. the protocol handler reports timer expiry to the application as an error condition or negative response. the handling is as defined in the appropriate protocol specification. i.1 7.2 Procedure Process_Access_Request_MSC Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC. - Annex A describes the method which the MSC uses to decide how to process the IAM. It acts as a GMSC. If a supervision timer expires before a distant entity responds to a signal.1. accessible to the procedure Establish_Originating_TCH_If_Required. An MSC which receives an IAM from an originating exchange may react in three different ways: It acts as a transit exchange.1 MO call Functional requirements of serving MSC Process OCH_MSC The variable TCH allocated is global data. Sheet 2: the VMSC maps the negative response received on the B interface to the appropriate reject cause according to the rules defined in 3GPP TS 29. Where a timer is shown in the present document.11. 7. In general. i. sheet 3: if the VMSC receives a Set-up message from the MS while the access request is being handled. 7. the procedure call is omitted if the entity does not support an optional feature or service.

If the VMSC does not support CAMEL.11. sheet 9: at any stage after the Set-up has been received. it is specified in 3GPP TS 23. CCBS_OCH_Report_Failure. processing continues from the "Yes" exit of the test "Result=Call allowed?". Sheet 1. Sheet 1: the procedure Check_OG_Multicall_MSC is specific to Multicall. Sheet 3: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later.093 [22]. processing continues from the "Yes" exit of the test "Result=Pass?". If the VMSC does not support Multicall. If the VMSC does not support CCBS.078 [12]. Sheet 5: the procedure Handle_AoC_MO_MSC is specific to AoC. it is specified in 3GPP TS 23.0 Release 1999 23 ETSI TS 123 018 V3. the MS may terminate the transaction with the network by sending a Release transaction request. sheet 6. it is specified in 3GPP TS 23. MS connected and Reconnect are global data. accessible to the procedures CCBS_Check_OG_Call. Sheet 1: the procedure UUS_OCH_Check_Setup is specific to UUS. they are specified in 3GPP TS 23. Sheet 3: the procedure CCBS_Check_OG_Call is specific to CCBS. it is specified in 3GPP TS 23.093 [22].087 [20]. it is specified in 3GPP TS 23. Sheet 3: the procedure UUS_OCH_Set_Info_In_IAM is specific to UUS. it is specified in 3GPP TS 23.1. it is specified in 3GPP TS 23. Sheet 5: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports CAMEL phase 3 or later. Sheet 3: the procedure CAMEL_OCH_MSC_INIT is specific to CAMEL. processing continues from the "Yes" exit of the test "Result=Pass?". they are specified in 3GPP TS 23. sheet 6: the procedure CCBS_OCH_Report_Failure is specific to CCBS. sheet 2. Sheet 1. sheet 7: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later. This variable is accessible to all UUS specific procedures. processing continues from the "Yes" exit of the test "Result=Pass?". CCBS_Check_If_CCBS_Possible.018 version 3. Sheet 5: the procedure Set_COLP_Info_MSC is specific to COLP. ETSI .066 [10]. Sheet 3: the procedure Set_CLI_Presentation_Indicator_MSC is specific to CLIR.0 (2002-03) 7.078 [12]. sheet 3. If the VMSC does not support CLIR. Sheet 6: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS.078 [12]. If the VMSC does not support CAMEL phase 3 or later. Sheet 3: the procedure CCBS_OCH_Report_Success is specific to CCBS. Sheet 1: the VMSC converts the GSM bearer capability negotiated between the VMSC and the MS to a GSM basic service according to the rules defined in 3GPP TS 27. If the VMSC does not support CAMEL. Sheet 1: the procedure CAMEL_N_CSI_CHECK_MSC is specific to CAMEL Phase 3 or later. CCBS_OCH_Report_Success. it is specified in 3GPP TS 23.093 [22]. Sheet 1: the variable UUS1 result sent is specific to UUS.093 [22]. it is specified in 3GPP TS 23. Sheet 3: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability. If the VMSC does not support CCBS.3 Procedure OG_Call_Setup_MSC Sheet 1: the variables Alerting sent.1.001 [27]. processing continues from the "Yes" exit of the test "Result=Pass?". sheet 2.078 [12]. Sheet 4.11. it is specified in 3GPP TS 23.078 [12]. Sheet 3: the procedure CAMEL_MO_Dialled_Services is specific to CAMEL phase 3 or later.078 [12]. Send_Alerting_If_Required and Send_Access_Connect_If_Required. The task "Store CCBS Result" is executed only if the VMSC supports CCBS. processing continues from the "CCBS Not Possible" exit of the test "CCBS Result".087 [20]. it is specified in 3GPP TS 23. Sheet 4: the task "UTU2Cnt := 0" is executed only if the VMSC supports UUS Sheet 5: the procedure CAMEL_OCH_MSC_ANSWER is specific to CAMEL.135 [24]. processing continues from the "Yes" exit of the test "Result=Pass?". it is specified in 3GPP TS 23. sheet 7.3GPP TS 23.

they are specified in 3GPP TS 23. otherwise it uses a Release.1. it is specified in 3GPP TS 23. it is discarded if the VMSC does not support UUS. Sheet 7. otherwise it uses a Release. otherwise it uses a Release. If the VMSC does not support CAMEL.087 [20].078 [12]. processing continues from the "No" exit of the test "Result=CAMEL handling?". If a CC connection has not been established. it is specified in 3GPP TS 23.3GPP TS 23. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. Release Complete or Disconnect. If a CC connection has not been established. the MS uses CM Service Abort.6 Procedure Obtain_IMEI_MSC The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. If the VMSC does not support CAMEL. 7. it is specified in 3GPP TS 23. ETSI .11. processing continues from the "No" exit of the test "Result=CAMEL handling?".078 [12]. the MS uses CM Service Abort. the MS uses CM Service Abort. sheet 6: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2 or later.5 Procedure Authenticate_MSC The MS may terminate the transaction with the network while the VMSC is waiting for the MS to respond to an authentication request.7 Procedure Check_IMEI_MSC The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. 7. Sheet 8: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. Sheet 8: the procedures UUS_MSC_Check_UUS2_UUI_to_MS and UUS_MSC_Check_UUS2_UUI_to_NW are specific to UUS. otherwise it uses a Release. Sheet 8: the input signal User To User is specific to UUS.078 [12]. sheet 9: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS. it is specified in 3GPP TS 23.11.0 (2002-03) Sheet 6.1.4 Procedure Obtain_IMSI_MSC The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMSI. Sheet 6.1.078 [12]. sheet 7.1.078 [12]. otherwise it uses a Release. 7. sheet 9: the processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. it is specified in 3GPP TS 23.0 Release 1999 24 ETSI TS 123 018 V3. Sheet 9: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. 7. If a CC connection has not been established. Release Complete or Disconnect.1. If a CC connection has not been established. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.018 version 3. the MS uses CM Service Abort.1. sheet 7: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later. Sheet 6. Release Complete or Disconnect. sheet 7: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL Phase 1. The MS may terminate the transaction with the network while the VMSC is waiting for the result of the IMEI check from the EIR. Sheet 9: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL. it is specified in 3GPP TS 23. processing continues from the "No" exit of the test "Result=Reconnect?" Sheet 6.087 [20].1. Release Complete or Disconnect. If the VMSC does not support CAMEL phase 2 or later. If a CC connection has not been established.078 [12]. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.1. and will occur only if the VMSC supports CAMEL phase 2 or later. the MS uses CM Service Abort. Release Complete or Disconnect.

1.8 7. If no useful information would be carried in the Facility message.1. it is not sent. The procedures UUS_MSC_Check_UUS1_UUI and UUS_OCH_Set_Alert_And_Connect_Param are specific to UUS.3GPP TS 23. If the VMSC does not support AoC. ETSI .1. 7.0 (2002-03) 7. The message is saved for processing after return from the procedure. processing continues from the "Yes" exit of the test "Result=Pass?". 7.1. If no useful information would be carried in the Progress message.087 [20].1.9 Procedure Establish_Originating_TCH_If_Required Procedure Set_CLI_Presentation_Indicator_MSC The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIR_MAF004. If the VMSC does not support UUS. processing continues from the "No" exit of the test "Acknowledgement required".13 Procedure Handle_AoC_MO_MSC The charging parameters and the Boolean variable Acknowledgement required are global data which can be read by the parent process.1.1.1.1. processing continues from the "Yes" exit of the test "Result=Pass?".1.11 Procedure Set_COLP_Info_MSC The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process COLP_MAF006.12 Procedure Send_Access_Connect_If_Required The test "Acknowledgement required" refers to the result returned by the procedure Handle_AoC_MSC. The message is saved for processing after return from the procedure.11.1. they are specified in 3GPP TS 23. 7. If the VMSC does not support UUS.018 version 3. 7.0 Release 1999 25 ETSI TS 123 018 V3.087 [20].10 Procedure Send_Alerting_If_Required The test "Backward call indicator=no indication" refers to the called party’s status field in the backward call indicators parameter of the ISUP Address Complete message which triggered the call of the procedure Send_Alerting_If_Required. it is specified in 3GPP TS 23. it is not sent. The procedure UUS_OCH_Set_Alert_And_Connect_Param is specific to UUS.11.1.

0 Release 1999 26 ETSI TS 123 018 V3.3GPP TS 23.0 (2002-03) Process O CH _M S C Proc ess in the MS C to handle an outgoing c al l request OC H_M S C1(1) Idl e Signal s from the left are from the BSS CM s erv ice reques t Proc es s_ Access _ Request_M SC No Resu lt= Pas s? Ye s W ait _For_ Setup S etup CM Serv ice Abort See TS 23.11.093 CC BS_Check _ Las t_C al l Rele as e call resourc es Idl e Figure 6: Process OCH_MSC ETSI .018 version 3.093 CC BS_R ep ort_ Not_Idle TC H al located:= False OG_Ca ll_ Setu p_M SC See TS 23.11.

018 version 3.0 Release 1999 27 ETSI TS 123 018 V3. si gnal s to/from the ri ght are to/fro m the VLR.3GPP TS 23.0 (2002-03) Procedure P rocess_Access_Reque st_MSC Procedure in t he M SC to handle a reques t from the MS for system access P rocess A ccess R eques t PA R_MS C1(3) Si gnal s to/from the l eft are to/fr om the BSS.11. W ait_F or_ P AR_R esult Provide IMSI Authenticate Trac e Subscriber Activi ty Obtain_IM SI_ MS C Authentic ate_ M SC Tracing Active := TR UE No Res ult= Pass? Yes No R esult = Pass ? Yes R esult:= Fail R esul t:= F ail W ait_For_ PAR _Resul t W ait_For_ PA R_R esult W ai t_For_ PAR _Resul t W ait_F or_ P AR_R esult CM serv ice abort Start secu ri ty proc edur es C ipheri ng R equired:= True Abort R es ult:= Fail W ait_For_ PA R_R esult Figure 7a: Procedure Process_Access_Request_MSC (sheet 1) ETSI .11.

si gnals to/from the right are to/from the VL R.0 Release 1999 28 ETSI TS 123 018 V3. Abort Proce ss Acces s Request negati ve response Process Ac cess R equ es t ac k Yes C M Serv ice type= P age R esponse? No C ipheri ng requi red True Fals e Map negativ e response to rejec t c aus e Yes C M Ser vic e type = Page R esp ons e? No Rel eas e transac tion C M Service R eject Resu lt:= Fail Start security proc edures CM Serv ice Accept W ait_For_ T MS I_ R ealloc ation CM servic e abort Provi de IMEI S etup C heck IMEI Abort Forward N ew T MSI Us e Exis ting TMSI Obtain_IMEI_ MS C C heck _IM EI_ MSC M ap negative re sponse to re ject cause Abort Res ult= Pass? Yes No No R esult= Pass ? Yes C M Servic e R eject R ea lloca te TM SI R esult:= Fail R esult:= F ail R esult:= F ai l R es ult:= Pass W ai t_For_ TM SI_ R eal location W ait_For_ T MS I_ R eall ocation W a it_For_ TM SI_Ack Figure 7b: Procedure Process_Access_Request_MSC (sheet 2) ETSI .018 version 3.3GPP TS 23.11.11.0 (2002-03) Procedure P rocess_Access_Reque st_MSC Procedure in t he M SC to handle a reques t from the MS for system access W ait_F or_ P AR_R esult PA R_MS C2(3) Signals to/from the left are to/from the BSS.

11.11.0 (2002-03) Procedure P rocess_Access_Reque st_MSC Procedure in t he M SC to handle a reques t from the MS for system access W ait_F or_ TM SI_Ac k PA R_MS C3(3) Signals to /from the l eft are to/from the BSS.0 Release 1999 29 ETSI TS 123 018 V3.018 version 3. sig nal s to/from the right are to/from the VLR . CM servic e abort Setup A bort TM SI R eall oc ation Fa ilure TM SI R eallocation Com ple te Abort For ward N ew T MSI negativ e re spons e Forward New TM SI ack R esult:= Fail R esul t:= F ail R es ult:= Pass Figure 7c: Procedure Process_Access_Request_MSC (sheet 3) ETSI .3GPP TS 23.

11.0 Release 1999 30 ETSI TS 123 018 V3.018 version 3.11. 093 Wait _F or_ MO_Call_ Result Figure 8a: Procedure OG_Call_Setup_MSC (sheet 1) ETSI .0 (2002-03) Procedure OG_Call_Setup_MSC Proc edure in the originating VMSC t o set up an outgoi ng c all after a Setup message has been received from the MS OCS_MSC1(9) Alert ing sent :=False Backward call indicator: =No indic ation MS connec ted: =False Reconnec t:=False UUS1 result sent :=False CAMEL_Invocation:=False UUS_OCH_ Check_ Set up See TS 23.3GPP TS 23. 087 Conver t CS BC to basic servic e CAMEL_N_CSI CHECK_MSC Check_OG _ Multicall_MSC See TS 23. 135 No Result= Pass ? Yes Release transaction Send Info For Out going Call CCBS_O CH_ Report_F ailure See TS 23.

0 (2002-03) P ro c e d u re O G _ C a ll_ S e t up _ M S C P ro c ed u r e in th e o r ig in a tin g V M S C to s e t u p a n o u tgo i n g ca ll a fte r a S etu p me s sa g e h a s b ee n r e ce iv e d fr o m th e M S W a it_ Fo r_ M O _ C a ll _ R e su lt O C S _ M S C 2 (9 ) Re l e as e tra n sa c ti o n C o m p le te C all S e n d In fo F o r O u tg o in g C al l n e g a ti ve re s po n se C o n ve r t CS B C to ch a n n e l r e q u ir e me n t A b o rt C all P r o ce e d in g Re le a se tra n sa c ti o n E st ab l is h_ O r ig i n at in g _ T CH _ If_ R e q u ir e d R e su l t= P as s? Ye s No S e e TS 2 3 .11.0 Release 1999 31 ETSI TS 123 018 V3.0 9 3 CC B S _ O C H_ Re p o r t_F a ilu r e C CB S _O CH _ R ep o r t_F a il u re S e e T S 2 3 .0 93 1 Figure 8b: Procedure OG_Call_Setup _MSC (sheet 2) ETSI .11.018 version 3.3GPP TS 23.

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

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

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

078 Rel eas e transac tion 3 C C BS R esult C C BS P os sible C CBS N ot Possible R elease transaction C CB S_ Ac ti vation_ MSC Rel eas e See TS 23.3GPP TS 23.93 CC BS_OC H _ Report_F ailure Store C C BS R esult C AMEL Phase 2 or hi gher supported? No Yes No C AM EL Phase 2 or hi gher s upported? Yes Yes R elease cause = N o ans wer fro m user? No C AME L_O CH _ M SC_D ISC 3 C AMEL_O CH _ MS C_D ISC4 C AM EL_OC H_ MSC _D ISC 3 C AM EL_OC H_ MSC 1 4 No R esult= R econnect? Yes See TS 23. W ait_Fo r_ AC M Releas e transac ti on R elease F rom des ti nati on exc hange From gsm SSF Int_R eleas e_ C al l CC BS_OC H _ Report_F ailure See T S 23. signal s to/from the ri ght are to/from the destinati on exc hange unless oth erw ise m arke d.0 Release 1999 35 ETSI TS 123 018 V3.018 version 3.093 Rel eas e Figure 8f: Procedure OG_Call_Setup _MSC (sheet 6) ETSI .0 (2002-03) Procedure OG _Call_Setup_M S C Proc edure in the originatin g VMSC to s et up an outgoi ng call after a Setup mes sage h as been receiv ed from the M S OC S_MS C6(9) Signal s to/from the l eft are to/from the BSS.11.093 C C BS_Check _ If_C C BS_ P os sible See TS 23.093 S ee GS M 03.11.

Releas e transac ti on R elease F rom gsmSSF In t_R el eas e_ C all C AMEL Phase 2 or hi gher supported? No Yes No C AM EL Phase 2 or higher s upported? Yes Yes R eleas e c aus e= N o a nswer from user? No 4 C AME L_O CH _ M SC_D ISC 3 C AMEL_O CH _ MS C_D ISC4 C AMEL_OC H_ M SC _D ISC3 C AMEL_OC H_ MSC 1 See TS 23.0 (2002-03) Procedure OG _Call_Setup_M S C Proc edure in the originatin g VMSC to s et up an outgoi ng call after a Setup mes sage h as been receiv ed from the M S W ait_Fo r_C onnect_ Ac k W ait_For_Answer OC S_MS C7(9) Signal s to/from the l eft are to/f rom the BS S.087 U U S_M SC_ C heck_ U U S1_U UI 3 Rel eas e R elease transaction Releas e Figure 8g: Procedure OG_Call_Setup _MSC (sheet 7) ETSI .0 Release 1999 36 ETSI TS 123 018 V3.087 R esult= R econnect? Yes See TS 23.11. signal s to/from the ri ght are to/from the destination exc hange unless otherw ise marke d.018 version 3.078 Releas e transac ti on U US _M SC _ Check _ U US 1_U UI No See T S 23.11.3GPP TS 23.

087 R elease See TS 23.078 R elease R esult? Re connec t C onti nue.087 U U S_M SC_ C heck_ UU S2_ U U I_to_M S C AM EL_O CH _ MSC 2 See TS 23.3GPP TS 23.11. F ail R elease trans action W ait_For_ Answe r 3 Figure 8h: Procedure OG_Call_Setup _MSC (sheet 8) ETSI .11.0 Release 1999 37 ETSI TS 123 018 V3.0 (2002-03) Procedure OG _Call_Setup_M S C Proc edure in the originatin g VMSC to s et up an outgoi ng call after a Setup mes sage h as been receiv ed from the M S OC S_MS C8(9) Signal s to/from the l eft are to/from the BSS. signal s to/from the ri ght are to/from the destinati on exc hange unless oth erw ise m arke d.018 version 3. W ait_F or_ A ns wer Us er to Us er U ser to U ser 4 TN R y expired Internal U US _MSC _ Chec k_UU S2_ UU I_to_N W See T S 23.

087 U U S_M SC_ C heck_ U U S1_UU I See TS 23.018 version 3.3GPP TS 23.078 C AM EL_OC H_ M SC _D ISC 2 See TS 23.0 (2002-03) Procedure OG _Call_Setup_M S C Proc edure in the originatin g VMSC to s et up an outgoi ng call after a Setup mes sage h as been receiv ed from the M S W ait_Fo r_ C lear OC S_MS C9(9) Signal s to/from the l eft are to/from the BSS.11.11.078 R esul t= R econnect? No Yes Res ult= CA MEL handling? No Yes Yes R esul t= C AM EL handling? No 3 Rel eas e R elease trans action Re lease Figure 8i: Procedure OG_Call_Setup _MSC (sheet 9) ETSI .087 Releas e transac ti on C AME L_O CH _ M SC_D ISC1 See T S 23.0 Release 1999 38 ETSI TS 123 018 V3. signal s to/from the ri ght are to/from the destination exc hange unless otherw ise marke d. Releas e transac ti on R elease from g sm SSF Int_R el eas e_ C all U US _M SC _ Check _ U US 1_U UI See T S 23.

3GPP TS 23.018 version 3.11.0 Release 1999

39

ETSI TS 123 018 V3.11.0 (2002-03)

Proc edure O btain_IMS I_M S C
Procedure in t he M SC to obtain the IMS I from the M S and re lay it to the VLR Si gnal s to/from the l eft are to/fr om the BSS; Si gnal s to/from the right are to/fr om the VLR

OIM SI_M 1(1)

Send IM SI

W ait_F or_ IM SI

Send IMSI ack

R elease transacti on

Send IMSI negati ve res ponse

Re lease transac tion

Provi de IM SI ack

A bort

R es ult:= Pass

R esul t:= A borted

Figure 9: Procedure Obtain_IMSI_MSC

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

40

ETSI TS 123 018 V3.11.0 (2002-03)

Procedure Au thenticate_M S C
Procedure in t he M SC to obtain an authentic ation response from the M S and re lay it to the VLR Si gnal s to/from the l eft are to/fr om the BSS; Si gnal s to/from the right are to/fr om the VLR

A UT _MSC 1(1)

Authenticate

W ait_F or_ Auth_R espons e

Au thentic ate ack

R elease transacti on

Auth enti cate negati ve res ponse

Authentic ate ack

A bort

Authenticate negat ive res po ns e

R elease transa ction

W ait_For_ Auth_Resul t

R esult:= Aborted

Authentic ation accepted

Authenticati on reject ed

Authenticati on rejected

R es ult:= Pass

Figure 10: Procedure Authenticate_MSC

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

41

ETSI TS 123 018 V3.11.0 (2002-03)

Proc edure O btain_IME I_M S C
Procedure in t he M SC to obtain the IME I from the M S and re lay it to the VLR Si gnal s to/from the l eft are to/fr om the BSS; Si gnal s to/from the right are to/fr om the VLR

OIM EI_M 1(1)

Send IM EI

W ait_F or_ IM EI

Se nd IM EI ack

R elease transacti on

Send IMEI negati ve res ponse

R elease transa ction

Provide IM EI ack

A bort

R es ult:= Pass

R esul t:= A borted

Figure 11: Procedure Obtain_IMEI_MSC

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

42

ETSI TS 123 018 V3.11.0 (2002-03)

Procedure C heck_IM EI_M S C
Procedure in t he M SC to c heck the IMEI and relay the res ult to t he VLR

CIME I_M1(1)

Signal s to/from the l eft are to/from the BSS; signal s to/from the ri ght are to/from the VL R unless ma rked otherw ise.

IM EI av ai lable? No

Yes

Send IMEI

W ait_F or_ IM EI

CM servic e abort

Send IMEI negative response

Send I MEI ack

R elease transacti on

Ch eck IM EI

To EIR

Abort

W a it_for_ C heck_IM EI_ Resu lt

R esult:= Aborted

Rel eas e transaction

C heck IMEI negativ e respons e

F rom EIR

Ch eck IM EI ack

From EIR

Abort

C heck IMEI negativ e respons e

Ch eck IM EI ack

R es ult:= Aborted

R esult:= Pass

Figure 12: Procedure Check_IMEI_MSC

ETSI

11.3GPP TS 23.0 (2002-03) Procedure E stablish_Originating_T CH _If_Required Proc edure in the origi na ti ng VM SC to es tablish a Traffic C hannel if one ha s n ot been establi shed for this c al l E OT CIR1(1) Signals to /from the l eft are to/from the BSS TC H allocated False True Allocate c hannel R esult:= Pass W ait_For_ Al location_ C om plete Release transacti on Allocation failure All ocation com plete R elease trans action TC H all oc ated:= Tr ue R esult:= F ai l R esult:= Pass Figure 13: Procedure Establish_Originating_TCH_If_Required ETSI .018 version 3.11.0 Release 1999 43 ETSI TS 123 018 V3.

3GPP TS 23.0 (2002-03) Procedure S et_CLI_P resentation_Indicator_M S C Procedure in t he M SC to determi ne the C LI presentation i ndi cator v al ue Si gnal s to/from the right are to/fro m the proc ess C LIR _M AF004 CA IND_M 1(1) Initi ate handli ng of C LIR W ait_F or_ C LIR_Info R elease transac tion From BSS C lear c all C onti nue cal l handling R esul t:= C all not allow ed R esult:= C all all owed Figure 14: Procedure Set_CLI_Presentation_Indicator_MSC ETSI .11.018 version 3.11.0 Release 1999 44 ETSI TS 123 018 V3.

087 U US_MSC _ Check _ U US1_U UI U U S_OC H_Set_ A lert_And_ C onnect_Param See TS 23.018 version 3.087 R esul t= P as s? Yes No Progres s A lerti ng A lerting s ent:= True R esul t:= Pas s R esult:= F ai l Figure 15: Procedure Send_Alerting_If_Required ETSI .11.0 Release 1999 45 ETSI TS 123 018 V3.0 (2002-03) Proc edure S end_A lerting_If_Required Procedure to s end an Aler ting mess age to the MS if one is req uired for thi s cal l S ALT IR 1(1) Sign al s to the l eft are to the B SS True Al erting sent Fals e True A ccess C onnect s ent Fals e Ye s Bac kward call indicator= no indication? No See TS 23.3GPP TS 23.11.

11.0 Release 1999 46 ETSI TS 123 018 V3.11.0 (2002-03) Procedure S et_CO LP _Info_M S C Procedure in t he M SC to determi ne the C OLP inform ati on to be s ent to the M S Si gnal s to/from the right are to/fro m the proces s C OLP_M AF 006 CO INF_M 1(1) Initi ate handli ng of C OLP W ait_F or_ C OLP_Info Re lease transac ti on From BSS C ontinue c all handli ng R elease From desti nation exchange Figure 16: Procedure Set_COLP_Info_MSC ETSI .3GPP TS 23.018 version 3.

3GPP TS 23.018 version 3.11.0 (2002-03) Procedure H andle_A oC_M O_MSC Procedure in t he M SC to handle AoC signalling tow ards the M S for an M O call A oC M O_M 1(1) Ye s A oC(I) provi sioned? No Set charging param eters No AoC (C ) provi sioned? Yes S et c harging pa ram ete rs Ack now ledgment required:= Fals e A cknow ledgment required: = True Figure 17: Procedure Handle_AoC_MO_MSC ETSI .0 Release 1999 47 ETSI TS 123 018 V3.11.

0 (2002-03) Procedure Se nd_Access_Connect_If_R equired Proc edure to s end a C onnect m essage to the MS if one is req uired for thi s cal l SA CO NIR1(1) Signal s to/from the l eft are to/from the BSS. signals to/from the ri ght are to/from the destination exc hange T rue MS c onn ec ted Fal se U U S_O CH _ Set_Alert_An d_ C onnect_Par am See TS 23.0 Release 1999 48 ETSI TS 123 018 V3.11.3GPP TS 23.11.087 Faci lity C onnect No Acknow ledgm ent required? Yes No Ac knowledgm ent req ui red? Yes Sta rt AoC acknow ledgme nt timer Start AoC ack now ledgm ent tim er W ai t_For_ Ao C_Ac k_F W ait_For_ AoC _Ack_C Charging Param eters ack Rel eas e transac tion AoC a cknowledgment timer expired C hargi ng Parameters ac k R elease tra ns action Connect Ack Ao C acknow ledgm ent tim er expired R elease transaction Releas e transac ti on R elease Re lease R esult:= Faci lity sent R esu lt:= F ail R esult:= C onnec t s ent R esult:= Fai l Figure 18: Procedure Send_Access_Connect_If_Required ETSI .018 version 3.

6 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. If the VMSC does not support UUS.3 Procedure OG_Call_Subscription_Check_VLR Sheet 1: it is an implementation option to carry out the check for operator determined barring of all outgoing calls before the check on provisioning of the requested basic service. Sheet 2: it is a network operator decision (subject to MoU requirements) whether a GSM connection should be ciphered. Sheet 2: the process Subscriber_Present_VLR is described in 3GPP TS 29.2. Sheet 1: the procedure UUS_OCH_Check_Provision is specific to UUS.11. according to the result returned by the procedure Check_OG_Barring. processing continues from connector 1 to the call to the procedure Check_OG_Barring. If the VLR does not support CAMEL.2.093 [22]. the procedure call is omitted. Sheet 3: it is a network operator decision (subject to MoU requirements) how often an IMEI should be checked. 7. If the VLR does not support CUG.2. it is specified in 3GPP TS 23.1. processing continues from the "Yes" exit of the test "Result=Call allowed?". it is specified in 3GPP TS 23.018 version 3. Sheet 1: the procedure Get_LI_Subscription_Info_MO_VLR is specific to CLIR and COLP.1.2. it is specified in 3GPP TS 23.2 Functional requirements of VLR Process OCH_VLR Procedure Process_Access_Request_VLR Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated.1. 7. sheet 4. it is specified in 3GPP TS 23. If the VMSC does not support Multicall.0 Release 1999 49 ETSI TS 123 018 V3.1 7.1. ETSI .1. Sheet 3.002 [28].2.0 (2002-03) 7.3GPP TS 23.1. If the VLR supports neither CLIR nor COLP. Sheet 1: the procedure Check_OG_Multicall_VLR is specific to Multicall.5 7. Sheet 2: the negative response "call barred" indicates whether the reason is operator determined barring or supplementary service barring. Sheet 1: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC. Sheet 5: it is a network operator decision whether emergency calls are allowed from an ME with no SIM. Sheet 1: the procedure OG_CUG_Check is specific to CUG. sheet 5: the procedure CCBS_Report_MS_Activity is specific to CCBS.078 [12]. 7.4 Procedure Obtain_Identity_VLR It is a network operator decision whether open (non ciphered) identification of the MS by its IMSI is allowed. A UMTS connection shall always be ciphered.2 7. processing continues from the "Yes" exit of the test "Result=Pass?".2. processing continues from the "Yes" exit of the test "Result=Pass?".087 [20].1.11.135 [24]. Sheet 2: the procedure CAMEL_OCH_VLR is specific to CAMEL.

1.12 Procedure Obtain_IMEI _VLR Process Fetch_Authentication_Sets_VLR 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. greylisted. If the VLR does not support COLP.2.0 (2002-03) 7.2. but the network operator may decide to initiate tracing.012 [6].1.1.3GPP TS 23.2.2.2.10 7. it omits the signal interchange with the process COLP_MAF005.16 Procedure Check_OG_Barring Sheet 3: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF018 or MAF019.2.1. 7.018 version 3.1. 7. then service is granted.2.1.2.2.0 Release 1999 50 ETSI TS 123 018 V3.1. whitelisted. the message is saved for handling after return from the procedure.7 7.11 7.14 Procedure Get_LI_Subscription_Info_MO_VLR If the VLR does not support CLIR.2.1. the message is saved for handling after return from the procedure.17 Process Update_Location_VLR The procedure Update_HLR_VLR is described in 3GPP TS 23. 7. If the VLR receives an Abort message from the MSC while it is awaiting a response from the process CLIR_MAF003 or the process COLP_MAF005.9 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 granted.8 7.11. the message is saved for handling after return from the procedure.1. ETSI .15 Procedure Get_AoC_Subscription_Info_VLR The indicator of whether or not AoC is provisioned is global data which can be read by the parent process. the message is saved for handling after return from the procedure.11.2.1. 7. 7. then service is not granted. 7.13 Procedure OG_CUG_Check If the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF014. it omits the signal interchange with the process CLIR_MAF003.1.

0 (2002-03) Process O CH _V LR Proc es s in the VLR to handle an outgo ing (M O) c all s etup request Si gnal s to/from the l eft are to/fro m the MSC.1.3GPP TS 23. Idle OC H_VLR 1(1) P rocess A ccess R eques t P rocess _ A ccess _ R eques t_VLR R esul t= Pas s Yes No W ait_F or_ S IF OC Idle S end Info F or Outgoing C all Abort Yes E mergency c all? No Idle Com plete C al l O G_Call_ S ubs cri ption_ C heck _VLR Idl e Idle Figure 7.11.0 Release 1999 51 ETSI TS 123 018 V3.2.1: Process OCH_VLR ETSI .018 version 3.11.

1.2a: Procedure Process_Access_Request_VLR (sheet 1) ETSI .2.018 version 3.11.11.0 Release 1999 52 ETSI TS 123 018 V3.3GPP TS 23.0 (2002-03) Procedure P rocess_Access_Reque st_VLR Procedure i n t he VLR to handle a reques t from the MS for system access PA R_V LR1(5) Identity k now n? Yes No Obtain_ Identi ty_VLR Yes R esult= Pass? No Id entity = IM EI? No Yes R esult= Fail? No Yes Authentication required? Yes No Authentic at e_ VLR No R esul t= P as s? Yes IM SI detached:= Fa lse C onfir med by R adio Contact:= True Set negative r esponse: Sys tem F ailure Set negativ e res pon se: U nidentifi ed Subsc riber R es ult:= Aborted 2 1 3 3 Figure7.

018 version 3.1.11.2.11.0 (2002-03) Procedure Process_Access_Request_VLR 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 See TS 29.2b: Procedure Process_Access_Request_VLR (sheet 2) ETSI .0 Release 1999 53 ETSI TS 123 018 V3.002 Data confirmed by HLR True False Set negative response: Unidentified Subscriber No Roaming allowed in current LA? Yes No Tracing required? Yes Set negative response: Roaming Not Allowed Start_ Tracing_VLR Ciphering required? Yes No 4 5 3 Figure 7.3GPP TS 23.

0 (2002-03) Procedure P rocess_Access_Reque st_VLR Procedure i n t he VLR to handle a reques t from the MS for system access Si gnal s to the l ef t are to the M SC .3GPP TS 23.11.1.2c: Procedure Process_Access_Request_VLR (sheet 3) ETSI .11.2.093 No Forward N ew TM SI U se E xisti ng T MSI IM SI detac hed := Tr ue Freeze exis ti ng TM SI R esul t:= Pas s Set negativ e res pon se: Illegal Equipm ent R es ult:= Aborted W ai t_For_ TM SI_Ack 3 Figure 7.018 version 3.0 Release 1999 54 ETSI TS 123 018 V3. 4 5 PA R_V LR3(5) Sta rt securi ty procedures Identity:= IMSI Proces s Access Request ack No IME I c hec k requi red? Yes Check _ IM EI_VLR Res ult= Pass? Yes No TM SI reallocation required? Yes No R esult= Fail? Yes C C BS_R eport_ M S_Ac tivity See TS 23.

0 Release 1999 55 ETSI TS 123 018 V3.1.2.0 (2002-03) Procedure P rocess_Access_Reque st_VLR Procedure i n t he VLR to handle a reques t from the MS for system access Si gnal s from the left are from the M SC.093 Res ult= U ni dentified Subscriber? No Yes R esult:= Pass Set negative response: U ni de nti fied S ubs cri ber Set negative response: I llegal S ubs cri ber 3 Figure 7.018 version 3.11. PA R_V LR4(5) 2 W ait_For_ TM SI_Ack Res ult= Aborted? No Yes Forward N ew T MSI ack Forward N ew TM SI negati ve res ponse R esu lt:= A borted Yes Res ult= Procedur e Error? No Res ult= U nk nown Subscriber? No Yes Set negative response: Sy stem F ailure U nfreeze existing T MSI C CBS _R eport_ M S_Activ ity See T S 23.3GPP TS 23.11.2d: Procedure Process_Access_Request_VLR (sheet 4) ETSI .

0 Release 1999 56 ETSI TS 123 018 V3.0 (2002-03) Procedure P rocess_Access_Reque st_VLR Procedure in t he VLR to handle a reques t from the M S for system access Signal s to the lef t are to the M SC .093 C C BS_R eport_ M S_Ac tivity R esul t:= Pas s R esult: = Aborted R esult:= Fail Figure 7.1.2.11.2e: Procedure Process_Access_Request_VLR (sheet 5) ETSI . C M s ervice type =Em erge nc y call? Yes 3 PA R_V LR5(5) No Emerg enc y call setup allowed w ithout S IM? No Yes No IM EI r equired? Yes O btai n_ IM EI_VLR R esul t= P as s? Yes No Identity:= IM EI R esult= F ail? No Yes P rocess A ccess R eques t ac k Pro cess Ac cess Re ques t negati ve res ponse See TS 23.018 version 3.11.3GPP TS 23.

018 version 3.2.1.3a: Procedure OG_Call_Subscription_Check_VLR (sheet 1) ETSI .3GPP TS 23.11.0 Release 1999 57 ETSI TS 123 018 V3.135 C heck _O G_ M ulti call_VLR Set negativ e re sponse: Basic servic e not provi sioned No Bearer servic e or telese rvi ce R esul t= P as s? Yes C heck_ B AO C R esul t= C al l barred? No OG _C U G_ C heck Yes Set negativ e re sponse: C all barred No R esul t= C al l al low ed? Yes Get_LI_ S ubs cri ption_ Info_MO_VLR Set negativ e re sponse: C UG reject G et_AoC _ S ubs cri ption_ Info_VLR U U S_OC H_ C heck_ Provis ion No R esul t= P as s? Yes Send In fo For Outgo ing Cal l negative res ponse 1 Figure 7.0 (2002-03) Procedure OG _Call_Subscription_Check_VLR Procedure in t he VLR to perf orm subscriptio n checks for an outgoi ng call Signal s to the lef t are to the M SC O CS CVLR 1(2) No Bas ic s ervi ce provis ioned? Yes See T S 23.11.

0 (2002-03) Procedure OG _Call_Subscription_Check_VLR Procedure in t he VLR to perf orm subscriptio n checks for an outgoi ng call O CS CVLR 2(2) Signals to the left are to the MS C 1 C AMEL_ OC H _VLR See TS 23.0 Release 1999 58 ETSI TS 123 018 V3.3b: Procedure OG_Call_Subscription_Check _VLR (sheet 2) ETSI .11.11.078 R esult= F ail? No Yes C heck _O G_ Barri ng C al l barred? No Yes Set negativ e res ponse: C all barred C om plete C al l Send Info For Outgoing C all negative res ponse Figure 7.2.018 version 3.1.3GPP TS 23.

018 version 3.0 Release 1999 59 ETSI TS 123 018 V3.11.3GPP TS 23.1.2.0 (2002-03) Procedure Obtain_Identity_VLR Procedure in t he VLR to obtain the identity of an MS OID_VL R1(1) Yes Identity = IM SI? No Identifi cation al low ed? No Yes O btai n_ IM SI_VLR R esul t= P as s? Yes No No IM SI k now n? Yes R es ult:= Fail R esul t:= Pas s R esult:= Abort ed Figure 7.11.4: Procedure Obtain_Identity_VLR ETSI .

3GPP TS 23.018 version 3.5: Procedure Obtain_IMSI_VLR ETSI .11.11.0 (2002-03) Proc edure O btain_IMS I_V LR Proces s in the VLR to obtain the IMS I from the MS v ia the M SC Signal s to/from the l eft are to/fro m the M SC.0 Release 1999 60 ETSI TS 123 018 V3.1.2. P rovi de IM SI O IM S I_V 1(1) W ait_F or_ IM SI Provide IM SI ack Abort R es ult:= Pass R esult:= Aborted Figure 7.

6a: Procedure Authenticate_VLR (sheet 1) ETSI .11.2. Auth enti cation sets available? No A UT _VLR1(2) Yes O btai n_ A uthentic ation_ S ets _VLR No R esul t= P as s? Yes 2 Yes Res ult= Aborted? No Authenticate R esult:= Aborted Yes Res ult= Pr ocedure Error? No W ait_F or_ Authentic ate_ R esult R es ult:= Procedure Error R es ult:= U nk nown Subscriber Authenticate ac k Authenticate negative re spons e Abort R eceived SR ES= ex pec ted SR ES? Yes Mo re authentic ation sets needed? Yes F etch_ A uthentic at ion_ S ets _VLR No Authentication fail ure re port No No More auth entication sets needed? Yes Fetch_ Authenti cation_ Sets_VLR Authenticati on ac cepted R esult:= Pas s R es ult:= Aborted 1 Figure 7.018 version 3.1.11.0 Release 1999 61 ETSI TS 123 018 V3.0 (2002-03) Procedure Au thenticate_V LR Procedure in t he VLR to authentic ate an MS via the MS C Signal s to/from the l eft are to/fro m the M SC.3GPP TS 23.

11.1.11.3GPP TS 23.6b: Procedure Authenticate_VLR (sheet 2) ETSI .0 (2002-03) Procedure Au thenticate_V LR Procedure in t he VLR to authentic ate an MS via the MS C Signal s to the lef t are to the M SC .018 version 3. Identity=IM SI? No 1 A UT _VLR2(2) Yes R etry w ith IMSI? Yes No O btain_ IMSI_VLR No R esult= P as s? Yes No IMSI k now n? Yes IMSI m atches T MS I? No Yes Authentica ti on accepted Authentic ation rejected Authentic ation failure report R es ult:= Aborted R es ult:= U nidentified Sub scriber Identity:= IMSI R es ult:= Ill ega l Subscriber 2 Figure 7.2.0 Release 1999 62 ETSI TS 123 018 V3.

11.018 version 3.7a: Procedure Obtain_Authentication_Sets_VLR (sheet 1) ETSI .0 (2002-03) Procedure O btain_Authentication_ Sets_V LR Procedure in t he VLR to obtain authentication sets from the HLR Signal s to/from the right are to/from the HLR O AS_ VLR1(2) Send Authenticati on Info W ait_F or_ A uthentic at ion_ S ets Send Authentic ation Info ac k Send Authenti cation Info negative res po ns e Em pty res ult? No Yes No U nknown Subsc ri ber? Yes Authentic ati on sets available in VLR ? Yes No Yes R e-us e o ld s ets ? No R es ult:= Pass R esult:= Procedure Error R esult:= U nknown Subsc riber Figure 7.2.1.11.0 Release 1999 63 ETSI TS 123 018 V3.3GPP TS 23.

Signal s to/from the right are to/from the HLR W ait_F or_ A uthentic ation_ S ets Abort Abort Abort Authentic ati on sets avail able? Yes No Yes R e-use old se ts? No R es ult:= Aborted R esul t:= Pas s R esult:= Proc edure Error Figure 7.1.0 (2002-03) Procedure O btain_Authentication_ Sets_V LR Procedure in t he VLR to obtain authentication sets from the HLR O AS_ VLR2(2) Signal s to/from the l eft are to/fro m the M SC.018 version 3.2.3GPP TS 23.7b: Procedure Obtain_Authentication_Sets_VLR (sheet 2) ETSI .0 Release 1999 64 ETSI TS 123 018 V3.11.11.

3GPP TS 23. T racing ac tive? Yes S T _T R _V 1(1) No T race S ubs criber Act ivity Figure 7.0 (2002-03) Procedure S tart_T racing_VLR Procedure in t he VLR to requ es t the M SC to start activ ity traci ng Signal s to the lef t are to the M SC .018 version 3.2.1.0 Release 1999 65 ETSI TS 123 018 V3.8: Procedure Start_Tracing_VLR ETSI .11.11.

11.2.3GPP TS 23.11.8: Procedure Check_IMEI_VLR ETSI .1.0 Release 1999 66 ETSI TS 123 018 V3.0 (2002-03) Procedure C heck_IM EI_V LR Procedure in t he VLR to requ es t the M SC to check an IM EI Signal s to/from the l eft are to/fro m the MS C C heck IM EI CIME I_V1(1) W ait_F or_ C heck _IMEI_ R esult Abort C heck IM EI negat ive response Check IM EI ack No Serv ice gran ted? Yes R es ult:= Aborted R esul t:= F ail R esult:= Pass Figure 7.018 version 3.

0 (2002-03) Proc edure O btain_IME I_V LR Proces s in the VLR to obtain the IMS I from the MS v ia the M SC Signal s to/from the l eft are to/fro m the MS C P rovi de IM EI O IM E I_V 1(1) W ait_F or_ IM EI Provide IM EI ack Abort R es ult:= Pass R esult:= Aborted Figure 7.2.11.9: Procedure Obtain_IMEI _VLR ETSI .3GPP TS 23.1.018 version 3.0 Release 1999 67 ETSI TS 123 018 V3.11.

11.1.0 (2002-03) Process Fetch_Au thentic ation_Sets_V LR Proces s in the VLR to retriev e authentica tion sets from the HLR F AS _VLR 1(1) O biain_ A uthentic ation_ S ets _VLR Figure 7.3GPP TS 23.10: Process Fetch_Authentication_Sets_VLR ETSI .2.018 version 3.11.0 Release 1999 68 ETSI TS 123 018 V3.

11.018 version 3.3GPP TS 23.0 Release 1999 69 ETSI TS 123 018 V3.11: Procedure Check_BAOC ETSI .0 (2002-03) Procedure C heck_B AOC Proc edure to c hec k call request against OD BAOC and SS BAOC Signal s to/from the right are to/fro m the proces s M AF017 CB A OC 1(1) Ye s O perator determined BAO C impos ed? No R es ult:= Call barred (OD B) Initi ate handling of BAO C W ait_F or_ B AOC_ R esponse From MS C Abort C ontinue c all handling Ye s C all ba rred? No R es ult:= Call barred (SS barring ) R esult:= C all allow ed Figure 7.2.1.11.

12: Procedure OG_CUG_Check ETSI .1.2.11.018 version 3.3GPP TS 23.0 Release 1999 70 ETSI TS 123 018 V3.0 (2002-03) Proc edure O G_CU G_Check Procedure to carry out CU G authori sation check for an outgoi ng (M O) c all Signal s to/from the right are to/fro m the proces s C UG _M AF 014 OG _C UG 1(1) outgoing c al l requ es t W ait_For_ C U G_Re spons e From MS C Abort r esponse to cal l r eques t com plete cal l (conditi onal C U G info) rejec t call (c aus e) R esult := C all al low ed R esult:= Ca ll barred Figure 7.11.

11.0 Release 1999 71 ETSI TS 123 018 V3.13: Procedure Get_LI_Subscription_Info_MO_VLR ETSI .2.11.018 version 3.1.3GPP TS 23.0 (2002-03) Procedure G et_LI_Subscription_Info_M O_VLR Procedure in t he VLR to retrieve subscription inform ati on for the C LIR & C OLP line identifi cation servi ces for an M O c al l Initi ate handl ing of C LIR G LI_MO V 1(1) T o process CLIR _M AF003 W ait_F or_ C LIR_Info From MS C Abort C ontinue c all handli ng F rom process CLIR _M AF003 Initi ate handl ing of C OLP T o process CO LP_M AF 005 W ait_F or_ C OLP_Info From MS C Abort C ontinue c all handli ng F rom proc es s C OLP_M AF005 Figure 7.

0 (2002-03) Procedure G et_AoC_S ubscription_Info_V LR Procedure in t he VLR to determi ne the subs cri ption to Adv ice of C harge s erv ices GA OC I_V 1(1) A oC(I) provisioned? No Yes No AoC (C ) provisioned? Yes Set indicator: AoC not prov isi oned S et i ndicator: A oC (C) provisioned Set indic ator: AoC (I) provis ioned Figure 7.1.11.14: Procedure Get_AoC_Subscription_Info_VLR ETSI .2.11.0 Release 1999 72 ETSI TS 123 018 V3.3GPP TS 23.018 version 3.

15a: Procedure Check_OG_Barring (sheet 1) ETSI .1.11.0 (2002-03) Procedure C heck_OG _B arring Proc edure to c hec k call request against SS barring and OD B c ategori es CO B 1( 3) Yes Operator determ ined BOIC imposed? No No Desti na tion address C C = Loc al C C? Yes 1 Yes Operator determ ined BOIC -exH C im posed? No Yes Desti na tion address C C = Loc al C C? No 1 No Desti na tion address C C = HPLM N CC ? Yes 1 Yes Operator determ ined BOIZC imposed? No No Dest ination address Z C = Local ZC ? Yes 1 Yes Operator determ ined BOIZC -exHC i mposed? No Yes Dest ination address Z C = Local ZC ? No 1 No Desti na tion address C C = HPLM N CC ? Yes R esult:= C all barred (O DB) 1 Figure 7.3GPP TS 23.0 Release 1999 73 ETSI TS 123 018 V3.018 version 3.2.11.

0 (2002-03) Procedure C heck_OG _B arring Proc edure to c hec k call request against SS barring and OD B c ategori es 1 CO B 2( 3) No Operato r deter mined BO IC .0 Release 1999 74 ETSI TS 123 018 V3.11.exHC &BOIZ C impos ed? Yes 2 Yes D esti nati on address ZC = Loc al ZC ? No Yes D esti nati on addres s C C = Local CC ? No 2 No D esti nati on addres s C C = H PLM N C C ? Yes R es ult:= Cal l barred (O DB) 2 Figure 7.3GPP TS 23.11.018 version 3.15b: Procedure Check_OG_Barring (sheet 2) ETSI .2.1.

15c: Procedure Check_OG_Barring (sheet 3) ETSI .3GPP TS 23.11.11.1.0 (2002-03) Procedure C heck_OG _B arring Proc edure to c hec k call request against SS barring and OD B c ategori es Yes 2 CO B 3( 3) C al l barred? No Initiate handli ng of BOIC T o process M AF 018 W ait_Fo r_ B OIC_ R esponse Fr om MSC Abo rt C ontinue c al l handli ng F rom proces s M AF018 Yes C al l barred? No Initiate handli ng of BOIC -exH C T o process M AF 020 W ait_Fo r_ B OIC-exHC _ R esponse Fr om MSC Abo rt C ontinue c al l handli ng F rom proces s M AF020 Yes C al l barred? No R esult:= Ca ll barred (SS barri ng) R esul t:= C all allow ed Figure 7.018 version 3.0 Release 1999 75 ETSI TS 123 018 V3.2.

11.1.012 Figure 7.16: Process Update_Location_VLR ETSI .11.3GPP TS 23.018 version 3. UL_VLR1(1) Update_HLR_ VLR See TS 23.0 Release 1999 76 ETSI TS 123 018 V3.2.0 (2002-03) Process Update_Location_VLR Process in the VLR to update the location information in the HLR.

unspecified Requested facility not implemented Call rejected Number changed Protocol error.0 (2002-03) 7. The Send Routeing Info negative response information element received in the execution of the procedure Obtain_Routeing_Address is global data. Send_Answer_If_Required and Send_Network_Connect_If_Required.0 Release 1999 77 ETSI TS 123 018 V3. Sheet 1: the suggested mapping from values of the Send Routeing Info negative response information element to values of the ISUP release cause (see ITU-T Recommendation Q. Sheet 1: the variable UUS CF interaction is specific to UUS.11. it is specified in 3GPP TS 23.2 7. Sheet 1: the procedure MNP_MT_GMSC_Set_MNP_Parameters is specific to Mobile Number Portability. depending on the telephony signalling system used.079 [13]. 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 ISUP release cause number 20 57 21 21 21 55 87 87 111 69 21 22 111 57 111 1 26 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 Protocol error. Sheet 1: the procedure OR_Set_ORA_Parameters is specific to Support of Optimal Routeing. Network connect sent.1 Retrieval of routeing information for MT call Functional requirements of GMSC Process MT_GMSC Sheet 1: the variables ACM sent.3GPP TS 23. The mapping used is a matter for the network operator. Reconnect and Resume call are global data. Sheet 1: the parameters "Reference address". it is accessible to all UUS specific procedures in the GMSC.1.066 [10].018 version 3. it is specified in 3GPP TS 23.11.2. Sheet 1: the procedure CAMEL_Set_ORA_Parameters is specific to CAMEL. unspecified Bearer capability not authorised Protocol error. Answer sent. available to the parent process. Obtain_Routeing_Address. Send_ACM_If_Required.2. CCBS_Set_Diagnostic_For_Release. it is specified in 3GPP TS 23. The parameter "Destination address" is returned by the procedure Obtain_Routeing_Address only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.850 [36]) is shown in table 1.078 [12]. "OR" and "Own PLMN" are passed to the procedure Obtain_Routeing_Address only if the GMSC supports Optimal Routeing.1 7. accessible to the procedures CCBS_MT_GMSC_Check_CCBS Possible. unspecified Unallocated (unassigned) number Misrouted call to a ported number (note) ETSI .

018 version 3. Any message other than Address Complete. Sheet 6: the procedures CAMEL_MT_GMSC_DISC4 and CAMEL_MT_GMSC_DISC6 are specific to CAMEL phase 2 or later. If the GMSC sends an Address Complete message. Sheet 1: it is an operator option whether to send an Address Complete message if the Number Portability Database returns a routeing number. The procedure CAMEL_MT_GMSC_DISC5 is specified in 3GPP TS 23. and will occur only if the GMSC supports Optimal Routeing. Sheet 3: the procedure Handle_COLP_Forwarding_Interaction is specific to COLP.078 [12]. If the GMSC does not support CAMEL. Sheet 6.078 [12].11. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. it shall include the called party’s status field of the Backward call indicator set to "no indication". they are specified in 3GPP TS 23. it is specified in 3GPP TS 23.078 [12].078 [12].0 (2002-03) NOTE: If the Diagnostic parameter indicates “NPDB mismatch”. Sheet 5: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. processing continues from the "No" exit of the test "Result=CAMEL handling?". Sheet 6: the procedure CAMEL_MT_GMSC_DISC3 is specific to CAMELphase 1. If the GMSC sends an Address Complete message.079 [13]. Sheet 1: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in the Perform Call Forwarding ack.11. it shall include the called party’s status field of the Backward call indicator set to "no indication".093 [22]. it is specified in 3GPP TS 23. they are specified in 3GPP TS 23. MNP can require a specific ISUP release cause value. it is specified in 3GPP TS 23. Sheet 4: the input signal Resume Call Handling and all the subsequent processing on this sheet are specific to Support of Optimal Routeing. If the GMSC does not support CAMEL. and will occur only if the GMSC supports CAMEL phase 2 or later. Sheet 2.0 Release 1999 78 ETSI TS 123 018 V3. The procedure OR_Handle_RCH is specified in 3GPP TS 23. depending on national regulations. Connect. If the GMSC does not support CAMEL. Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. ETSI . Sheet 7: after the GMSC has sent an IAM to the destination VMSC or the forwarded-to exchange (via the process MT_CF_MSC).078 [12]. Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later. according to National Coding Standard. Sheet 7: the procedure CAMEL_MT_GMSC_DISC1 is specific to CAMEL.078 [12].078 [12].3GPP TS 23. it acts as a relay for messages received from the originating exchange and the destination VMSC or the process MT_CF_MSC. sheet 3: the procedure CAMEL_MT_GMSC_ANSWER is specific to CAMEL.093 [22]. Sheet 6: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS. it is specified in 3GPP TS 23. Sheet 1: it is an operator option whether to send an Address Complete message if the HLR returns forwarding information. under all other conditions the SRI negative response “unknown subscriber” shall be mapped to ISUP release cause number 1 “Unallocated (unassigned) number”.078 [12]. Answer or Release causes no change of state in the process MT_GMSC. If the IAM received from the originating exchange contained the HPLMN routing number for NAGNP then the SRI negative response “unknown subscriber” shall be mapped to ISUP release cause number 26 “Misrouted call to a ported number”. processing continues from the "Pass" exit of the test "Result". Sheet 2. sheet 6: the procedure CCBS_MT_GMSC_Check_CCBS_Possible is specific to CCBS. North American GSM Number Portability (NAGNP) requires the SRI negative response “unknown subscriber” to be treated differently under certain conditions. sheet 3: the task "Set destination address parameter" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. Sheet 7: the procedure CAMEL_MT_GMSC_DISC2 is specific to CAMEL. Sheet 4. sheet 7: the processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL. to indicate “Misrouted call to a ported number”. processing continues from the "Normal handling" exit of the test "Result?".

066 [10]. it is specified in 3GPP TS 23.078 [12]. 7. it is specified in 3GPP TS 23.3 Procedure Send_ACM_If_Required If no useful information would be carried in the Call Progress message.079 [13]. It is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 3: The test "MSRN contains a Routeing Number" is executed only if the SRF solution for call related MNP is used. processing continues from the "No" exit of the test "MSRN contains a Routeing Number". Sheet 3: the procedure CAMEL_MT_GMSC_Notify_CF is specific to CAMEL phase 2 or later.0 Release 1999 79 ETSI TS 123 018 V3. Sheet 1: the procedure CLI_MT_GMSC is specific to Enhanced CLI Handling. processing continues from the "No" exit of the test "Result=Pass?". it is specified in 3GPP TS 23. Sheet 4: the task "BOR:=OR" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. Sheet 2: the procedure OR_Handle_SRI_Negative_Response is specific to Support of Optimal Routeing. it is specified in 3GPP TS 23.11.081 [14].078 [12]. Sheet 1: the procedure CCBS_MT_GMSC_Check_CCBS_Call is specific to CCBS.2.11. processing continues from the "True" exit of the test "Route permitted". If the SRF solution for call related MNP is not used.078 [12]. it is not sent. Sheet 3: the procedure CCBS_MT_GMSC_Check_CCBS_Indicators is specific to CCBS.1.093 [22].1. If the GMSC does not support CAMEL phase 2 or later.018 version 3.078 [12]. Sheet 4: the task "OR:= True" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. Sheet 2: the test "Error=Unknown subscriber" refers to the negative response value received from the HLR. Sheet 3: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal Routeing. It is specified in 3GPP TS 23. it is specified in 3GPP TS 23.2.093 [22]. It is specified in 3GPP TS 23. If the GMSC does not support Optimal Routeing. If the GMSC does not support Optimal Routeing. Sheet 4: the procedure CAMEL_MT_GMSC_DISC4 is specific to CAMEL Phase 2 or later. Sheet 4: the procedure CAMEL_MT_MSC_DISC3 is specific to CAMEL phase 1. Sheet 4: the procedure Route_Permitted is specific to Support of Optimal Routeing.079 [13].1. Sheet 3: the procedure MNP_MT_GMSC_Check_MNP_Indicators is specific to Mobile Number Portability.3GPP TS 23. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.066 [10].0 (2002-03) 7.4 Procedure Send_Answer_If_Required If no useful information would be carried in the Call Progress message. 7. it is not sent. Sheet 2: the procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR is specific to Mobile Number Portability. processing continues from the "Continue" exit of the test "Result". Sheet 3: the procedure CAMEL_MT_GMSC_INIT is specific to CAMEL.066 [10]. ETSI . it is specified in 3GPP TS 23.093 [22].2 Procedure Obtain_Routeing_Address Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD is specific to Mobile Number Portability. it is specified in 3GPP TS 23. Sheet 4: the procedures CCBS_MT_GMSC_Remove_Indicators_Store_FWT is specific to CCBS.2.

Sheet 1.078 [12].5 Procedure Send_Network_Connect_If_Required If no useful information would be carried in the Call Progress message. it is specified in 3GPP TS 23. and will occur only if the GMSC supports CAMEL phase 2 or later.2. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 2 or later.078 [12]. it is specified in 3GPP TS 23. If the MSC does not support CAMEL. Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later.8 Process MT_CF_MSC Sheet 1: the procedure CAMEL_CF_MSC_INIT is specific to CAMEL.11.0 (2002-03) 7. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.078 [12].078 [12].2. Sheet 2: the procedure UUS_MSC_Clear_UUS is specific to UUS.2. Sheet 5: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL. processing continues from the "No" exit of the test "Result=Reconnect?" .7 Procedure Activate_CF_Process The processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL. sheet 4: the procedure CAMEL_CF_Dialled_Services is specific to CAMEL phase 3 or later. processing continues from the "No" exit of the test "Result=CAMEL handling?". processing continues from the "Yes" exit of the test "Result=Reconnect?". If the MSC does not support CAMEL phase 3 or later. 7. it is specified in 3GPP TS 23.078 [12].3GPP TS 23. it is specified in 3GPP TS 23. Sheet 1. sheet 3: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later. it is specified in 3GPP TS 23. Sheet 3: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later. Sheet 4: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. processing continues from the "Pass" exit of the test "Result?". ETSI .1. If the MSC does not support CAMEL.018 version 3. it is specified in 3GPP TS 23.078 [12]. it is specified in 3GPP TS 23.1.078 [12]. they are specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 5: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL.2.066 [10].6 Procedure Handle_COLP_Forwarding_Interaction_MSC The originating exchange or the destination exchange may release the call while a response is awaited from the process COLP_MAF039.078 [12]. Sheet 1. sheet 3: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1. it is specified in 3GPP TS 23.1.1.087 [20].0 Release 1999 80 ETSI TS 123 018 V3. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?".078 [12]. 7. Sheet 2: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL. 7. Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability. Sheet 1. Sheet 3: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL.078 [12]. If the MSC does not support CAMEL. it is specified in 3GPP TS 23.11. If the MSC does not support CAMEL.078 [12]. Sheet 5: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL. Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later. sheet 4: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2 or later. it is not sent. The message is saved for processing after return from the procedure. sheet 3.

2.018 version 3. Answer or Release causes no change of state in the process MT_GMSC 7.0 (2002-03) Sheet 5: after the process MT_CF_MSC has sent an IAM to the forwarded-to exchange.0 Release 1999 81 ETSI TS 123 018 V3.3GPP TS 23. Connect.11.1. Any message other than Address Complete. it acts as a relay for messages received from the parent process and the forwarded-to exchange.9 Macro CUG_Support_Check_GMSC ETSI .11.

11. OR.018 version 3.066 OR_Set_ORA_ Parameters See TS 23. Routeing address.078 Initial Address (Routeing Address) Initial Address (Routeing Address) To process MT_CF_MSC To originating exchange Idle Wait_For_ ACM Wait_For_ Forward_ACM Figure 35a: Process MT_GMSC (sheet 1) ETSI . False) Wait_For_ ACM CAMEL_Store_ Destination_ Address (OR. Own PLMN.078 Obtain_Routeing_Address (Called party address.0 Release 1999 82 ETSI TS 123 018 V3. Destination address. False) See TS 23. Reference address.0 (2002-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Idle MT_GMSC1(7) Signals to/from the left are to/from the originating exchange.11.079 CAMEL_Set_ ORA_Parameters See TS 23. Result) Result= Forward? No Yes Result= Fail? No Result= Routeing number? No Yes Yes Set cause Release Yes Result= Aborted? No Initial Address (Routeing Address) Release call resources CAMEL_Store_ Destination_ Address (OR. signals to/from the right are to/from the destination MSC unless marked otherwise Initial Address 1 Fail CUG_Support_ Check_GMSC Pass ACM sent:=False Answer sent:=False Network connect sent:=False Reconnect:=False Resume call:=False UU S CF Interaction:=False Reconnect:= True MNP_MT_GMSC_ Set_MNP_ Parameters See TS 23.3GPP TS 23.078 Send_ACM_ If_R equired Send_ACM_ If_Required See TS 23.

11.11.078 C AMEL_ S top_T N Ry See TS 23.018 version 3.078 C AMEL_M T_ GM SC _AN SW ER C AMEL_MT _ GM SC _ANSW ER See TS 23.0 (2002-03) Process M T _GM S C Proces s in the GMS C to handle a mobile-terminated call reques t W ait_ For_ AC M M T _GM S C2(7) Signal s from the right are from the destinati on exc hange A ddress C omplete C onn ec t S end_AC M_ If_R equired See TS 23.078 Fail R esult? R econnect Rec onn ec t R esult? F ail Pass Idle 1 Pa ss Idle S et dest ination a ddress p aram et er Set destin ation addres s parameter Send_Ne twork _ C onn ect_If_ R equ ired S end_Ans wer_ If_R equired W ait_For_ C lear Figure 35b: Process MT_GMSC (sheet 2) ETSI .0 Release 1999 83 ETSI TS 123 018 V3.3GPP TS 23.078 C AMEL_ S tart_TN R y W ait_ For_ A ns wer A ns wer See TS 23.

11.0 (2002-03) Process MT_GMSC Proces s in the GMS C to handle a mobile-terminated call reques t MT_GMSC3(7) W ait_ For_ Forward_ACM Signals f rom the right are from the proc ess MT_CF_MSC A ddress Complete Connect S end _ACM_ If_Required W ait_ For_ Forward_ A ns wer A ns wer See TS 23.0 Release 1999 84 ETSI TS 123 018 V3.078 Fail Result? Pass Idle Reconnect Rec onnect Result? Pas s 1 Fail Handle_COLP_ Forwardin g_ Interac tion_MSC Handle_COLP_ Forwarding_ Interaction_MSC Id le Set COLP presentation indicator Set CO LP pres entation indicator S et des tination a ddress p arameter Set destination addres s parameter S end _Ans wer_ If_Required Send_Network_ Conne ct_ If_ Required W ait_For_ Clear Figure 35c: Process MT_GMSC (sheet 3) ETSI .11.3GPP TS 23.078 CAMEL_MT_ GMSC_ANSWER CAMEL_MT_ GMSC_ANSW ER See TS 23.018 version 3.

079 for m ess age co ntents C C BS_MT _GMSC_ C heck_C C BS_ P os sible See TS 23.0 Release 1999 85 ETSI TS 123 018 V3.11.3GPP TS 23.0 (2002-03) Process M T _GM S C Proces s in the GMS C to handle a mobile-terminated call reques t W ait_For_ACM .079 R esul t= F ail? No Yes Yes R esul t= R efuse? No R esul t= R econnect? No Yes - W ait_Fo r_ F orw ard_AC M 1 Idle Figure 35d: Process MT_GMSC (sheet 4) ETSI .018 version 3.093 R esum e call :True OR _H andl e_ RCH See TS 23. W a it_For_ Ans wer M T _GM S C4(7) Signal s to/from the right are to/from the destinatio n M SC unless m arked otherwi se R esume C all H andli ng R efer to TS 23.11.

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

signal s to/from the right are to/from the destination exc hange or process MT_ CF _MS C unless marked otherwi se Releas e Release From gsmSSF In t_Releas e_ Call CCBS_MT _GMSC_ Check_CCBS_ P os sible See TS 23.3GPP TS 23.078 No Result= Reconnect? Yes Releas e CCBS_Set_ Diagn ostic_ For_Release Releas e Release 1 Releas e Releas e c all resourc es Idle Figure 35f: Process MT_GMSC (sheet 6) ETSI .0 (2002-03) Process MT_GMS C Proces s in the GMS C to handl e a mobile-terminated call reques t W ait_For_ACM.11. W ait_For_Forward_A CM.0 Release 1999 87 ETSI TS 123 018 V3. W ait_For_Forward_A ns wer MT_G MSC 6(7) Signals to/from the left are to/from the originat ing exchange.093 CAMEL phase 2 or higher supported? No Yes No CAMEL phase 2 or higher s upport ed? Yes Yes Release c aus e= No an swer from user? No 2 CAME L_MT _ GMSC_DISC3 CAMEL_MT_ GMSC_DISC6 CAMEL_MT_ G MSC_DISC3 CAMEL_MT _ G MS C_DIS C4 See TS 23. W ait_For_Answer.11.018 version 3.

W ait_For_Forward_Ans wer.0 (2002-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated c all r equest Wait_For_ Clear MT_GMSC7(7) Signals to/from the left are to/from the originating exchange. W ait_For_Clear Set negativ e response: OR not allowed * * Resume Call Handling negative response - - Wait_F or_ Clear - Figure 35g: Process MT_GMSC (sheet 7) ETSI . signals to/from the right are to/from the destination exchange or the process MT_CF_MSC unless marked otherwise Release Release Int_Releas e_ Call From gsmSSF CAMEL_MT_ GM SC_DISC1 See TS 23.078 CAMEL_MT_ GM SC_DISC2 See TS 23.018 version 3.11.11. W ait_For_Answer.3GPP TS 23.078 Result= CAMEL handling? No Yes Reconnect Result? CAMEL handling Release Normal handli ng Release 1 Release Release Release call resources Wait_F or_ Clear Idle Resume Call Handling W ait_For_ACM. W ait_For_Forward_AC M.0 Release 1999 88 ETSI TS 123 018 V3.

0 (2002-03) Procedure O btain_Routeing_Address Procedure in a G MSC to determine the address to whic h a call should be routed O RA1(4) Procedure Obtain _Routeing_Addres s FPA R IN I nput addres s.11.066 Result= Number ported? No Yes See TS 23.081 CLI_MT_ G MS C Pre-paging s uppo rted in GMSC? No Yes S et Pre-paging s uppo rted To HLR S end Routeing Info W ait_for_ Routeing_ Info 1 Figure 36a: Procedure Obtain_Routeing_Address (sheet 1) ETSI . Destination address . Own P LMN IN/OUT Rou teing address.0 Release 1999 89 ETSI TS 123 018 V3. OR.3GPP TS 23. Result MOB ILE_NUMB ER_ P ORTABILITY_ IN_TQo D See TS 23. Referen ce address .093 CCBS_MT_ GMSC_Ch ec k_ CCBS_Call Ro uteing addres s:= routein g number True Reconnect Fals e Result:= Ro uteing numbe r See TS 23.018 version 3.11.

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

0 (2002-03) Procedure Obtain_Routeing_Address Proc edure in a G MSC t o determine the address t o whic h a call s hould be routed Wait _for_ Routeing_ Inf o ORA3(4) Send Routeing Inf o ac k From HLR CAMEL supported? 1 No Yes No MSR N recei ved? CAMEL_MT_ GM SC_INIT See TS 23.018 version 3. 078 Result= Fail? No Continue Result Fail Routeing address: = MSR N Destination address := VMSC address Reconnect Recpnnect := True Result:= Fail Result:= Routeing number Result: = Pass 2 1 Figure 36c: Procedure Obtain_Routeing_Address (sheet 3) ETSI . 066 MNP_MT _GMSC _ Check_MNP_ Indicators Routeing address := MSRN Yes GSM_FTN CAMEL_ MT_G MSC_ Notify_C F Yes See TS 23.3GPP TS 23.0 Release 1999 91 ETSI TS 123 018 V3.11.11. 093 Yes Result= Aborted Store Forwarding Int errogat ion Required indicat or Result:= Aborted No No MSRN contains a Rout ei ng number? No Result= Fail CAMEL_FTN Result Yes See TS 23. 078 3 Yes Yes 3 Result= MSR N No CCBS_MT _ GM SC_Check_ CCBS_ Indicators See TS 23.

0 (2002-03) Pro c e d u re O bta in _ R o u te in g_ A dd r e ss Pr ocedure in a G MS C to de term i ne the add ress to w h ic h a cal l should be r outed O R A 4( 4) 2 BO R:=O R A ctiv ate_ C F_ Proces s R esu lt= F ail? No Y es C C B S_MT _ GM S C _R emov e_ Indic ators_ S tor e_FW T R oute_Perm itted ( OR .F TN .078 C A M E L_MT _ GM SC _D ISC 3 T o p rocess M T_ CF _MS C CF cancel led R outeing addr ess:= F TN R outei ng addres s:= R efere nce addres s D estin ation addres s:= R efere nce addres s OR :=Fals e D esti nation addr ess:= F TN OR :=T rue R esu lt:= F orw ard R esult:= P ass Figure 36d: Procedure Obtain_Routeing_Address (sheet 4) ETSI . R eference A ddr ess) R oute pe rm itted Tr ue See TS 23.093 R esult:= A borted See TS 23.0 78 Se e T S 23.3GPP TS 23.079 Fal se C A ME L phase 2 or hi gh er su ppor ted? No Y es C AME L_M T _ G M S C _DIS C 4 S ee T S 23.11.0 Release 1999 92 ETSI TS 123 018 V3.018 version 3.11.

11.0 Release 1999 93 ETSI TS 123 018 V3.3GPP TS 23.018 version 3.11.0 (2002-03) Procedure S end_A CM_If_Required Procedure to send an Address C om plete M es sage to the precedi ng exc han ge i f one i s requi red for this call S AC M IR 1(1) Sig nal s to the left are to the originating ex change True AC M s ent Fals e True N etwork c onn ec t s ent Fals e C all Progres s A ddr ess C om plete A CM sent:= True Figure 37: Procedure Send_ACM_If_Required ETSI .

11.0 Release 1999 94 ETSI TS 123 018 V3.3GPP TS 23.018 version 3.11.0 (2002-03) Procedure S end_A nsw er_If_Required Procedure to send an Ans wer M es sage to the precedi ng exc han ge i f one i s requi red for this call S AN M IR 1(1) Sig nal s to the left are to the originating ex change True A ns wer s ent False True N etwor k c onnect s ent False C al l Progres s Answ er Ans wer s ent:= True Figure 38: Procedure Send_Answer_If_Required ETSI .

11.0 Release 1999 95 ETSI TS 123 018 V3.3GPP TS 23.0 (2002-03) Procedure S end_N etwork_Connect_If_Required Proc edure to s end a C onnect M essage to the precedi ng exc han ge i f one i s requi red for this call S NCO NIR1(1) Sig nal s to the left are to the originating ex change True N etwork c onne ct s ent Fals e True A ns wer s ent Fals e AC M s ent True Fals e C al l Progress Ans wer C onnec t An swer sent:= True C onnect sent:= True Figure 39: Procedure Send_Network_Connect_If_Required ETSI .11.018 version 3.

3GPP TS 23.0 (2002-03) Pro cedure H andle_C OLP_F orwarding_Interaction_MS C Procedure in t he GM SC or VMSC to handle the intera ction betw een COLP and Ca ll F orw arding CO IN T_M 1(1) Signal s to/from the right are to/fro m the proces s C OLP_M AF 039 Initi ate handli ng of C OLP W ait_F or_ C OLP_Info Re lease From origi nating exc han ge or desti nati on ex change c onti nue c all handli ng Figure 40: Procedure Handle_COLP_Forwarding_Interaction_MSC ETSI .018 version 3.0 Release 1999 96 ETSI TS 123 018 V3.11.11.

0 (2002-03) Pro cedure A ctivate_CF _P rocess Procedure in t he MSC to i nitiate the p rocess whic h handles call forw ardi ng AC F P1(1) Signal s to/from the l eft are to/from the origi nating exchange.018 version 3. si gnals to/from the ri ght are to/from the pr oc ess M T_C F_M SC unless m arked othe rw ise P erform c all forwarding (BOR .3GPP TS 23.11.11.0 Release 1999 97 ETSI TS 123 018 V3. FTN ) W ait_F or_ C F_R esponse Releas e Perform c all forw arding ack Perform call forwardi ng negative respons e Int_R el eas e_ C all From gsmSSF CF cancelled Re lease CF cancelled R es ult:= Fai l Resu lt:= Pas s R esul t:= F ail R esult:= Fail Figure 41: Procedure Activate_Call_Forwarding_Process ETSI .

066 M OBILE_NU M BER_ POR TABILITY_ IN_O QoD C AMEL phas e 2 or hi gher supported? Initial Address No See TS 23.3GPP TS 23. True) C AMEL_OC H_ M SC _D ISC 3 See TS 23.11.078 A bort R esul t? Pass F ai l P erform c al l forwarding ack (F TN ) See T S 2 3.078 W ai t_For_ ACM Idle Idle Figure 42a: Process MT_CF_MSC (sheet 1) ETSI .078 Yes C AM EL_OCH _ MSC _DISC 4 See TS 23. si gnals to/from the ri ght are to/from the destination exc hange Idle P erform c al l forwarding C AM EL_CF _ M SC _INIT See TS 23.078 CAM EL_Store_ Des tination_ Address (BO R.078 C AMEL_ OC H _M SC 1 Res ult= Fail? Yes No Idl e W ait_F or_ IAM R esult= R econnect? Yes No 1 Ini tial Address CF cance lled 2 Perform C all Forwardi ng neg ati ve response See TS 23.0 Release 1999 98 ETSI TS 123 018 V3.0 (2002-03) Process M T _CF _M SC Proc es s in the MS C to handle c all forwar di ng M T CF M S C1(5) Si gnals to/from the l eft are to/from the parent proc ess.078 R esul t= P as s? Yes No C AM EL_CF _ D ialled_Serv ices See TS 23.11.018 version 3.

3GPP TS 23.018 version 3.078 CAM EL_C F_ MSC _AN SW E R See T S 23 .078 C AME L_C F_ MSC_AN SW ER See T S 23.11.0 (2002-03) Process M T _CF _M SC Proc es s in the MS C to handle c all forwar di ng W ait_For_ AC M M T CF M S C2(5) Si gnals to/from the l eft are to/from the parent proc ess. si gnals to/from the ri ght are to/from the destination exc hange Address Com plete Co nnect CAM EL_ Start_TN R y See T S 23 .087 A ddr ess C om plete W ait _For_ Ans wer Ans wer CAM EL_ Stop _T N Ry See T S 23 .0 Release 1999 99 ETSI TS 123 018 V3.087 UU S_M SC_ Clea r_U US No No Re sult= Pass? Yes R esult= R econnect? No Yes A ns wer Co nnect W ait _For_ Clea r Idle 2 W ait_For_ Cl ear Figure 42b: Process MT_CF_MSC (sheet 2) ETSI .078 UU S_M SC_ Clea r_U US See T S 23 .11.087 U US _M SC _ Cl ear_U U S See T S 23.078 Resu lt= Pas s? Ye s See TS 23.

11.018 version 3.0 Release 1999 100 ETSI TS 123 018 V3. W ait_For_A ns wer M T CF M S C3(5) Sig nal s to/from the l eft are to/from the parent proc ess.078 Releas e Releas e R elease 2 Rel eas e R elease c all resourc es Idle Figure 42c: Process MT_CF_MSC (sheet 3) ETSI .078 No R esult = R econnect? Yes C AM EL_ Stop_TN R y See TS 23.3GPP TS 23. si gnals to/from the ri ght are to/from the destinatio n exc hange unless m arked othe rw ise Rel eas e R elease F rom gsm SSF Int_O_ Rel eas e No C AM EL phase 2 or hi gher supported? Yes No C AMEL phas e 2 or hi gher s upporte d? Yes Yes R elease caus e= N o an swer from user? No 3 C AME L_O CH _ M SC_D ISC3 C AMEL_OC H _ MS C_D ISC4 C AM EL_OC H_ MSC _D ISC 3 C AM EL_OC H_ M SC 1 See TS 23.0 (2002-03) Process M T _CF _M SC Proc es s in the MS C to handle c all forwar di ng W ait_For_A CM .11.

0 (2002-03) Process M T _CF _M SC Proc es s in the MS C to handle c all forwar di ng W ait_F or _ A ns wer M T CF M S C4(5) Sig nal s to/from the l eft are to/from the parent proc ess.11.018 version 3.078 2 R elease R esul t? Fail R econnect Releas e See T S 2 3.078 C AMEL_C F_ D ial led_ Serv ices Abort R esult? F ail Pass R elease c al l r esourc es See T S 2 3.3GPP TS 23.0 Release 1999 101 ETSI TS 123 018 V3.11.078 C AMEL_ OC H _M SC 1 1 Idle R esult= R econnect? No Yes Perform Cal l Forwarding negative res ponse 2 Idle Figure 42d: Process MT_CF_MSC (sheet 4) ETSI . si gnals to/from the ri ght are to/from the destinatio n exc hange unless m arked othe rw ise T N Ry expired Internal 3 R elease C AM EL_OC H_ M SC 2 See TS 23.

11.11.0 Release 1999 102 ETSI TS 123 018 V3.018 version 3.0 (2002-03) Process M T _CF _M SC Proc es s in the MS C to handle c all forwar di ng M T CF M S C5(5) Si gnals to/from the l eft are to/from the parent proc ess.3GPP TS 23. si gnals to/from the ri ght are to/from the destination exc hange unless marked othe rw ise W ait_Fo r_ C lear Rel eas e R elease Int_O_ Re lease From gsmSSF C AMEL _O CH _ MS C_D ISC1 Se e T S 23.078 C AM EL_OC H_ M SC _D ISC 2 See TS 23.078 Re lease Res ult= CA MEL H andl ing? No Yes Yes R esul t= C AM EL H andling? No R esul t= R econnect? No Yes Rel eas e R elease 2 Re lease R elease c all resourc es Idle * * * - - - Figure 42e: Process MT_CF_MSC (sheet 5) ETSI .

if needed.0 (2002-03) Macrodefinition CUG_Support_Check_GMSC Macro to check support of CUG in GMSC. CUG_SC1(1) No CUG info present? Yes GMSC supports CUG? Yes No Outgoing Access present? No Yes Pass Fail Figure 43: Macro CUG_Support_Check_GMSC ETSI .018 version 3.3GPP TS 23.11.0 Release 1999 103 ETSI TS 123 018 V3. and check if call can continue.11.

If the HLR does not support Optimal Routeing.078 [12]. If the HLR does not support CUG. If the HLR does not support CAMEL. Sheet 4: the procedure PRN_Error_HLR can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. Sheet 2: the procedure CCBS_Handling_HLR is specific to CCBS.1 Functional requirements of HLR Process SRI_HLR Sheet 1: the procedures Check_Parameters.093 [22]. it is specified in 3GPP TS 23. If the HLR does not support Optimal Routeing. Sheet 1: the procedure CAMEL_HLR_INIT is specific to CAMEL.078 [12]. processing continues from the "No" exit of the test"Result=Fail?". If the HLR does not support CCBS. they are specified in 3GPP TS 23. accessible by the process SRI_HLR.2. it is specified in 3GPP TS 23. If the HLR does not support Optimal Routeing. Sheet 4: the test "Forwarding enquiry" is specific to Support of Optimal Routeing. If the HLR does not support CAMEL. the procedure sets the negative response to "Unexpected data value". It is specified in 3GPP TS 23.081 [14].2. This negative response parameter is global data.2. Handle_OR_HLR_CF and CAMEL_HLR_INIT can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. the test "Alerting pattern required" and the task "Set Alerting Pattern" are omitted. Sheet 4: the procedure Forward_CUG_Check is specific to CUG. processing continues from the "Yes" exit of the test "Result=Call allowed?". It is specified in 3GPP TS 23. processing continues from the "No" exit of the test.078 [12]. Sheet 3: the procedure CLI_HLR_Set_CLI is specific to Enhanced CLI Handling. accessible by the process SRI_HLR.2 7.018 version 3. Sheet 2: the procedure First_Forwarding_HLR can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message. the procedure sets the negative response to "Data missing". Sheet 3: the procedure OR_HLR_Interrogate_VLR is specific to Optimal Routeing. processing continues from the "No" exit of the test "Result=Forward?". Sheet 4: the procedure CAMEL_CSI_Check_HLR is specific to CAMEL.0 (2002-03) 7.2. Sheet 4: the procedure CAMEL_D_CSI_CHECK_HLR is specific to CAMEL phase 3 or later.11.079 [13]. Sheet 2: the procedure CAMEL_CSI_Check_HLR is specific to CAMEL. it is specified in 3GPP TS 23. Subscription_Check_HLR.078 [12]. ETSI .2. processing continues from the "Yes" exit of the test "Result = OK?". 7. If any parameter has a value which is not in the set of values expected for the parameter.0 Release 1999 104 ETSI TS 123 018 V3. If the HLR does not support CAMEL.078 [12]. it is specified in 3GPP TS 23. This negative response parameter is global data.11. accessible by the process SRI_HLR. Sheet 3: if the HLR does not support Network Indication of Alerting. This negative response parameter is global data. processing continues from the "No" exit of the test"Result=CSI active?".079 [13]. it is specified in 3GPP TS 23. processing continues from the "No" exit of the test "Result=Forward". Sheet 4: the procedures CAMEL_T_CSI_CHECK_HLR and CAMEL_O_CSI_CHECK_HLR are specific to CAMEL. Sheet 1: the procedure Handle_OR_HLR_CF is specific to Support of Optimal Routeing.2 Procedure Check_Parameters If any parameters required by the rules in clause 8 are missing from the message.3GPP TS 23. processing continues from the "No" exit of the test "Result=CSI active?". it is specified in 3GPP TS 23.

2.2. The procedure Super_Charged_SRI_Error_HLR is specific to Super-Charger.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.2.2. 7.9 7.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 following tests are on the value of the Provide Roaming Number negative response.4 Procedure First_Forwarding_HLR The MS is not reachable if any of the following conditions is satisfied: The HLR has no location information for the subscriber. The negative response "CUG reject" indicates whether the reason is: Incoming calls barred within CUG.018 version 3. processing continues from the "No" exit of the test "Result=Purged?". If a GSM bearer capability cannot be derived from the ISDN compatibility information or the MSISDN of the B subscriber.2.6 7.11. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.007 [29].0 Release 1999 105 ETSI TS 123 018 V3.2.2.2. 7. ETSI . If the HLR does not support Super-Charger. The procedure does not return a value.2.5 Procedure PRN_Error_HLR The procedure CCBS_Report_PRN_Failure is specific to CCBS. 7. The subscriber record is marked as MS purged.093 [22]. according to the result returned by the procedure Check_IC_Barring. The subscriber record is marked as Roaming Restricted due to Unsupported Feature. The subscriber is marked as deregistered because of subscription restrictions on roaming.2. 7. If the HLR does not support Optimal Routeing.7 Procedure Forward_CUG_Check Procedure Derive_Requested_Basic_Service_HLR The rules for deriving a Circuit-switched bearer capability from ISDN compatibility information or the MSISDN of the B subscriber are specified in 3GPP TS 29. The negative response "Call barred" indicates whether the reason is operator determined barring or supplementary service barring.2.2.2. Subscriber not member of CUG. Requested basic service violates CUG constraints. according to the cause returned by the procedure IC_CUG_Check.2.11. The subscriber record is marked as MSC area restricted.8 7.116 [23]. processing starts with the test "Negative response=Facility not supported?".3GPP TS 23.0 (2002-03) 7. the HLR applies a default basic service according to the requirements of the operator.2.

The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later. processing continues from the "Yes" exit of the test "Result = Pass?". 7.078 [12].078 [12].11.3GPP TS 23.11.2.2. processing continues from the "Yes" exit of the test "Result = Pass?".0 Release 1999 106 ETSI TS 123 018 V3. it is specified in 3GPP TS 23.018 version 3. ETSI . it is specified in 3GPP TS 23.0 (2002-03) The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later.11 Procedure Handle_CFNRc The test "Mobile subscriber not reachable" refers to the value of the indicator returned by the process MAF010. If the GMSC does not support CAMEL Phase 3 or later. If the GMSC does not support CAMEL Phase 3 or later.

3GPP TS 23. si gnals to/from the rig ht are to/from the VLR Idle Send R outei ng Info C heck_ Parame ters R esul t= P as s? Yes No S ubs cri ption_ C heck_H LR R esul t= F ail? No Yes See TS 23.078 C AM EL_ H LR _IN IT R esul t= F ail? No Yes 3 1 2 1 Figure 44a: Process SRI_HLR (sheet 1) ETSI .018 version 3.079 OR _H LR_C F R esul t= F ail? No Yes R esul t= F orw ard? No Yes See TS 23.11.0 Release 1999 107 ETSI TS 123 018 V3.11.0 (2002-03) Proc ess SR I_HLR Proces s in the H LR to handl e a request for routeing inform ation S RI_H LR1(4) Signals to /from t he left are to/from the GM SC.

11.0 Release 1999 108 ETSI TS 123 018 V3.078 CA MEL_ CS I_C heck_ HLR Yes 2 See TS 23.11.018 version 3.093 R esult = F orw ard No No Yes R esult = OK Yes 1 5 2 1 Figure 44b: Process SRI_HLR (sheet 2) ETSI .078 Res ult= CSI activ e? No Yes R esult= C SI ac tive? No 4 4 C C BS_H andl ing_ H LR See TS 23. si gnals to/from the rig ht are to/from the VLR F i rst_ Fo rw arding_ H LR R esult= F ail? No Yes R esult= F orw ard? No C AM EL_ C SI_C hec k_ H LR Yes See TS 23.0 (2002-03) Proc ess SR I_HLR Proces s in the H LR to handl e a request for routeing inform ation 3 S RI_H LR2(4) Signals to /from the l eft are to/from the GMSC.3GPP TS 23.

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

078 See TS 23.078 C AM EL_D_ C SI_C HE CK_ H LR C all ed party SS i nteraction v iolation Set negativ e res pons e: CU G reject Send Routeing Info ac k Send R outei ng Info ack Send R outeing Info ack Send Routeing Info negativ e res ponse Idl e Idle Idle Id le Figure 44d: Process SRI_HLR (sheet 4) ETSI .0 (2002-03) Proc ess SR I_HLR Proces s in the H LR to handl e a request for routeing inform ation W ait_F or_ M SR N S RI_H LR4(4) Signals to /from t he left are to/from the GM SC.078 C AM EL_O_ C SI_C HE CK_ H LR See TS 23.078 C AM EL_T _ C SI_C HE CK_ H LR R esult = C SI ac ti ve? Yes See TS 23.018 version 3.3GPP TS 23.11.0 Release 1999 110 ETSI TS 123 018 V3.11. si gnals to/from the rig ht are to/from the VLR Provide Roaming Number ac k P rovi de R oami ng N um ber negati ve response P RN _Error_ H LR 1 2 R esul t= F ail? No Yes F orw ard_ C U G_C hec k R esul t= C all allow ed? Yes Routeing address := MSR N 4 R outeing address:= F TN Yes No F orw ardi ng enquiry? No Yes F orw arding enquiry? No C AM EL_ C SI_Check _ H LR No See TS 23.

018 version 3.0 Release 1999 111 ETSI TS 123 018 V3.11.11.0 (2002-03) Procedure C heck_P aram eters Proc edure to c hec k the param eters o f a recei ved m ess age Chk_Pa r1(1) All required parameters present? Yes No All parameter values ac ceptable? Yes No Set negativ e res pons e: Data mi ssing Set negativ e re sponse: U nex pec ted data value R esul t:= Pas s R es ult:= Fai l Figure 45: Procedure Check_Parameters ETSI .3GPP TS 23.

018 version 3.11.0 (2002-03) Procedure S ubsc ription_Check _H LR Procedure in t he H LR to m ake subsc rip tion check s for a mobileterm inated call S C_HLR 1(1) MS k now n? Yes No Set neg ati ve response: U nknown subsc rib er Yes N umber c hanged? No D eri ve_R equested_ Bas ic_Servi ce_ HLR Set neg ati ve response: N umber changed R equested N o s ervice provi sioned? Yes C heck _IC _ Barring Set neg ati ve response: ser vic e not provis ioned Bearer serv ice or Teleserv ice R esul t= C all ba rred? No Yes Set neg ati ve response: C all barred IC _C UG_ C heck R esul t= C all allow ed? Yes No Set neg ati ve response: C UG reject R esul t:= Pas s R es ult:= Fail Figure 46: Procedure Subscription_Check_HLR ETSI .0 Release 1999 112 ETSI TS 123 018 V3.3GPP TS 23.11.

3GPP TS 23.0 Release 1999 113 ETSI TS 123 018 V3.018 version 3.11.0 (2002-03) Procedure F irst_F orwarding_HLR Procedure in t he H LR to handle c all forwar di ng before interrogation of t he VLR F F_H LR1(1) H andle_C FU R esul t= F ail? No Yes Yes R esul t= F orw ard? No Set negativ e re sponse: Fo rw arding violation No M S not reachable? Yes H andle_C FN Rc R esul t= F ail? No Yes Set negativ e re sponse: Fo rw arding violation No R esul t= F orw ard? Yes Set negativ e re sponse: Absent subsc ribe r R esult:= Forward R es ult:= Continue R esul t:= F orwa rd R es ult:= Fail Figure 47: Procedure First_Forwarding_HLR ETSI .11.

3GPP TS 23.018 version 3.11.0 Release 1999

114

ETSI TS 123 018 V3.11.0 (2002-03)

Procedure PR N_E rror_H LR
Procedure in t he H LR to handle a negati ve respons e for a roaming num ber request

P RN_ E_H1(1)

C CB S_R eport_ PR N _Failure

See TS 23.093

Negativ e response =OR not al lowed?? No

Yes

Set negativ e res pons e: OR not allo wed Yes

N egativ e respons e= Faci lity not s up ported? No

Yes

N egative response=Absent su bs cri ber? No

Set negativ e res pons e: Fac ili ty n ot supported

Negativ e response=N o roami ng number?

No

Yes

Handle_C FN R c

H an dle_C FN Rc

Set negativ e res pons e: System failu re

Fail Res ult?

Forw ard

Forward R esul t?

F ai l

N ot reachable Set n egativ e res pon se: Forwarding violation Super_C harged_ SRI_Error_ HLR Yes

Not re ac hable Set negativ e res pons e: Forwarding violati on

Res ult= Purged? No Se t negative respons e: Absent subscriber Set negative response: Sys tem fai lure R esult:= F orw ard R es ult:= Fail

R esult:= Fail

Figure 48: Procedure PRN_Error_HLR

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

115

ETSI TS 123 018 V3.11.0 (2002-03)

Pro cedure F orw ard_C UG_Check
Procedure to carry out CU G authori sation check for a forw arded cal l

F W D _CUG 1(1)

No

C U G provi si oned for forw ard ing subscriber against reque sted basic servic e Yes

C U G info prov ided i n ro utei ng i nform ation re quest No

Yes

P erform F orw arding CU G au thorisation

As de fined in TS 23.085

Pas s CUG au thorisation r es ult Fail

R es ult:= Cal l allo wed

R esul t:= C all barr ed

R esult: = C all allow ed

U pda te C UG i nf o

As defi ned in T S 23.085

Figure 49: Procedure Forward _CUG_Check

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

116

ETSI TS 123 018 V3.11.0 (2002-03)

Procedure D erive_Reque sted_B asic_S ervice_HLR
Proc edure in the H LR to deriv e the requeste d basi c serv ice for an incom ing (M T ) call accordi ng to the rules of GSM 09.07 No Exhaustiv e ISD N co mpatibi lity informati on av ailable? Yes

DR BS _H1(1)

No

M ulti num beri ng? Yes

GSM BC: =NU LL

A pply GSM BC fo r this M SISD N

D eriv e GSM B C from ISD N compati bili ty inf ormation

Basic serv ice:= de fault

D eriv e basic se rvi ce from GSM BC

Figure 50: Procedure Derive_Requested_Basic_Service_HLR

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

117

ETSI TS 123 018 V3.11.0 (2002-03)

Proc edure C heck_IC_Barring
Proc edure to c hec k call request against SS barring and OD B c ategori es

CIB 1(2)

Yes

Operato r determ ined BAIC im posed? No

Yes

Operato r determ ined BIC -R oam im posed? No

No

MS registered in H PLM N country? Yes

1 Yes Operato r determ ined BIC -R oam HZ im pos ed? No No MS registered in H PLM N zone? Yes

R esult:= Ca ll barred (O DB)

1

Figure 51a: Procedure Check_IC_Barring (sheet 1)

ETSI

3GPP TS 23.018 version 3.0 (2002-03) Proc edure C heck_IC_Barring Proc edure to c hec k call request against SS barring and OD B c ategori es 1 CIB 2(2) Initi ate handl ing of BAIC T o process MAF 022 W ait_F or_ B AIC _ R esponse C ontinue c all handli ng F rom proce ss M AF022 Yes C all ba rred? No Initi ate handl ing of BIC -R oam T o process MAF 023 W ait_F or_ BIC -Roam_ R esponse C ontinue c all handli ng F rom proce ss M AF023 Yes C all ba rred? No R esult:= C all barred (S S ba rri ng) R esul t:= C all allow ed Figure 51b: Procedure Check_IC_Barring (sheet 2) ETSI .11.11.0 Release 1999 118 ETSI TS 123 018 V3.

11.0 Release 1999 119 ETSI TS 123 018 V3.018 version 3.3GPP TS 23.11.0 (2002-03) Procedure IC_CUG_Check Procedure to carry out CU G authorisation check for an incoming (MT) call IC_CUG1(1) Signals to/from the right are to/from the process CUG_MAF015 No SRI contains CUG info? Yes HLR supports CUG? Yes No Yes Outgoing Access present? No Wait_For_ CUG_Response incoming call reject call (cause) response to call request complete call (conditional CUG info) Result:= Call allowed Result:= Call barred (cause) Result:= Call allowed Figure 52: Procedure IC_CUG_Check ETSI .

3GPP TS 23.11.0 (2002-03) Procedure Handle_CFU Proc edure in the HLR t o handle Call Forwarding Uncondit ional H_CFU1(1) Signals to/f rom t he right are to/f rom t he process MAF007 CAMEL_CHECK _SI I2_C DTI See TS 23.0 Release 1999 120 ETSI TS 123 018 V3.018 version 3.11. 078 No Result = Pass ? Yes initiate handling of CFU Wait_F or_ CFU _Result continue call handling Yes Error? No Normal call? No Yes Result:= Fail Result:= Forward Result:= Continue Figure 53: Procedure Handle_CFU ETSI .

3GPP TS 23. 078 No Result = Pass ? Yes initiate handling of CFNRc Wait_F or_ CFN Rc_Res ult continue call handling Yes Error? No Yes Mobile subs criber not reachable? No Result:= Fail Result:= Forward Result:= Not reachable Figure 54: Procedure Handle_CFNRc ETSI .11.11.0 Release 1999 121 ETSI TS 123 018 V3.018 version 3.0 (2002-03) Procedure Handle_CFNRc Proc edure in the HLR or VLR to handle Call Forwarding on Mobile Subsc riber Not Reachable H_CFNRc1(1) Signals to/f rom t he right are to/f rom t he process MAF010 CAMEL_CHECK _SI I2_C DTI See TS 23.

sheet 4: the number of unused authentication sets which triggers the VLR to request further authentication sets from the HLR is an operator option.2. Sheet 8: the test " Fatal PAR error?" takes the "Yes" exit if: the MS failed authentication. Sheet 2. sheet 3.2.3. or the HLR returned an "Unknown subscriber" error during the handling of the Process Access Request.2.0 Release 1999 122 ETSI TS 123 018 V3.2. Sheet 1: the test "Pre-paging allowed" takes the "yes" exit if: the information element "Pre-paging supported" was present in the Provide Roaming Number message. Sheet 7. sheet 6. Sheet 2. Sheet 2.3 7. Sheet 2. If the VLR does not support Super-Charger.2. If the HLR requests neither location information nor subscriber state. or as an operator option. Sheet 8: this process communicates with the matching instance of the process ICH_VLR.1.11. processing continues from the "No" exit of the test "Result=Purged?".2.018 version 3. the paging procedure can be completed before the minimum timer value for the Provide Roaming Number operation timer in the HLR has elapsed. the VLR treats this as a missing parameter.093 [22]. Sheet 1: the procedure Check_Reason_In_Serving_Network_Entity is specific to Super-Charger.2.078 [12].2. which is linked by the MSRN.3GPP TS 23. sheet 3.0 (2002-03) 7. sheet 7: the procedure CAMEL_SET_SOA is specific to CAMEL. sheet 7: the procedure CLI_PRN_VLR is specific to Enhanced CLI Handling. Sheet 3.2. ETSI . PAR successful and Fatal PAR error are global data.081 [14]. 7. Sheet 4: the procedure Search_For_MS_VLR is specified in subclause 7.116 [23]. sheet 4: the process Fetch_Authentication_Sets_VLR is specified in subclause 7. and there is an association established for the MS between the MSC/VLR and the SGSN.11.2 7.2. which is linked by the MSRN. Sheet 3. sheet 6. sheet 6.3. sheet 8: the state variables PAR pending. sheet 3. sheet 7: the task "Store alerting pattern (if received)" is executed only if the VLR supports the feature Network Indication of Alerting. It is specified in 3GPP TS 23. sheet 7: the procedure CCBS_Handle_PRN is specific to CCBS.2.3.11. or the MS failed IMEI checking.3 Process Restore_Subscriber_Data_VLR Process PSI_VLR Sheet 1: the procedure Check_Parameters is specified in subclause 7.3.2. sheet 6. Sheet 4: the test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented.1 Functional requirements of VLR Process PRN_VLR Sheet 1: the procedure Check_Parameters is specified in subclause 7. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. sheet 3.3. accessible to the matching instance of the process ICH_VLR. it is specified in 3GPP TS 23.

geodetic information and geographical information derived from the service area ID or cell ID if the VLR is capable of doing so (the mapping from service area ID or cell ID to location number is networkspecific and outside the scope of the UMTS and GSM standards). 7.3.0 (2002-03) 7. and the VLR configuration requires paging via the SGSN during VLR restoration. The test "Retrieve location info from SGSN" takes the "Yes" exit if: the Gs interface is implemented. geodetic information and geographical information derived from the service area ID or cell ID if the VLR is capable of doing so (the mapping from cell ID to location number is network-specific and outside the scope of the UMTS and GSM standards).2. The derivation of the location number. The output signal Page MS towards the SGSN includes or omits the Location area identity parameter depending on the availability of this information.0 Release 1999 123 ETSI TS 123 018 V3.11. the signal Page MS is sent to every SGSN to which the VLR is connected. ETSI .3.5 Procedure Retrieve_Current_Location_VLR The test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented. geodetic information and geographical information from the received service area ID or cell ID is a VLR operator option (the mapping from service area ID or cell ID to location number is networkspecific and outside the scope of the UMTS and GSM standards). If it is omitted.018 version 3. and there is an association established between the MSC/VLR and the SGSN.2.3GPP TS 23.11. the age of the location information. the location number. the location number.4 Procedure Retrieve_Location_Info_VLR The variable Current location retrieved is used to indicate that the location information was obtained by paging the MS. the age of the location information. - The output signal Send MS information towards the SGSN indicates that the required information is mobile location information. - The received location information consists of: the service area ID (for UMTS) or cell ID (for GSM) received in the paging response message or in the Send MS Information ack. The stored location information consists of: the service area ID (for UMTS) or cell ID (for GSM) of the cell in which the MS last established radio contact.

Idle Provide R oaming N um ber C heck_ Parameters 1 R esult= P as s? Yes No OR i ndicator present? Yes OR s upported? Yes No No If C S B C w as in cluded in the Provid e R oam ing N um ber No Set n egativ e res pon se: OR n ot allowed C onvert C S BC to basic service Service s upported by VLR? Yes Pre-paging s upported i n VLR? No No Yes Set n egativ e res pon se: Faci li ty not s uppo rted Pre-paging al low ed? Yes Yes IMSI known in VLR ? No Check _Reason_ In_S ervi ng_ N etw ork _E ntity No 4 Yes IMSI k now n i n VLR? No C heck_R eason_ In_Serving_ N etw or k_Entity No See TS 23.0 Release 1999 124 ETSI TS 123 018 V3.116 Provide Roaming N um ber nega ti ve response 2 Res ult= Purged? Yes R esult= P urged? Yes 3 1 5 1 Idle Figure 55a: Process PRN_VLR (sheet 1) ETSI .0 (2002-03) Process PR N_VLR Proces s in the VLR to handl e a request for a roam ing num ber P RN_ VLR1(8) Signal s to/from the l eft are to/fro m the HLR .11.018 version 3.3GPP TS 23.11.

093 Provide R oamin g N um be r ack 6 Figure 55b: Process PRN_VLR (sheet 2) ETSI .0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber 2 P RN_ VLR2(8 ) Signal s to the lef t are to the H LR .11.3GPP TS 23. IM SI detached Fa ls e R oaming i n LA al low ed? Ye s M SR N av ailable? Ye s M SC per VLR 1 Ye s True No No Se t negativ e res pon se: N o roam ing numbe r >1 R e ceived M SC nu m ber= Stored M SC num b er? No Set negative res pons e: Absent subscrib er 1 Fal se C o nfirmed by radi o contac t True U se re ceiv ed M SC numb er fo r M SR N U se stored M SC nu mber for MSR N A lloca te M SR N C AM EL_ SET _SOA See TS 23. ISD N L LC & ISDN H LC (as avail able) Store A lerting P attern (if re cei ved) C LI_PR N_ VLR See TS 23.078 S tore c om p ati bi lity i nfo C S BC.11.0 Release 1999 125 ETSI TS 123 018 V3.081 C C BS_H and le_ PR N See TS 23. ISD N BC .018 version 3.

ISD N BC .11.3GPP TS 23. D ata confirm e d by H L R:=F alse.093 Provide R oamin g N um be r ack F et ch_ A uth entic ati on_ S ets _VL R R estore_ S ubs cri ber_ D ata_VLR Idle Figure 55c: Process PRN_VLR (sheet 3) ETSI . IM SI detac hed:= False Allocate LM SI If used by VLR S tore c om p ati bi lity i nfo C S BC.0 Release 1999 126 ETSI TS 123 018 V3.081 Fals e D a ta confirm ed by HLR ? True M ore au thenti cation sets needed? No Yes C C BS_H and le_ PR N See TS 23. ISD N L LC & ISDN H LC (as avail able) Store A lerting P attern (if re cei ved) 6 C LI_PR N_ VLR See TS 23.018 version 3.0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber 3 P RN_ VLR3(8 ) Signal s to the lef t are to the H LR .11. M SR N available Ye s A lloca te M SR N No Set n egativ e res pons e: No roami ng nu mber See TS 23.078 1 C AM EL_ SET _SOA C reate IM SI record Location i nfo c onfi rmed i n HLR := Fal se O nl y if >1 M SC per VL R C onfirm ed by radio co ntact:=Fal se.

Yes IM SI detached? No No R oaming i n LA al low ed? Ye s Locat ion are a ID know n? Yes No True Data confirme d by H LR? Fals e More authe ntic ati on sets needed ? Yes No Yes Set Paging vi a S GSN possib le Paging vi a S GS N po ssible? No Fe tch_ Authentication_ Sets_VLR R es tore_ Subscribe r_ Data_VLR Page type= ci rc uit-sw i tc hed cal l Search_Fo r_ MS _VLR Page MS Res ult= Pass? No Yes Absent subscribe r? No Set n egativ e res pon s e: Absen t subsc riber 1 7 Yes W ait_For_ Ac cess_ R eque st Figure 55d: Process PRN_VLR (sheet 4) ETSI .11.0 Release 1999 127 ETSI TS 123 018 V3.018 version 3.3GPP TS 23.0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber 4 P RN_ VLR4(8 ) Signal s to the right are to the M SC .11.

0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber 5 P RN_ VLR5(8 ) C rea te IM SI r ecord L oca tion info c onfirme d i n HLR := Fa lse O nl y if >1 M SC per VLR C on firm ed by radio contact:=F al se . IM SI detac hed:= Fa lse Al locate LM SI If used by VLR S tore c om pati bility i nfo C S BC .3GPP TS 23.0 Release 1999 128 ETSI TS 123 018 V3. ISD N BC .018 version 3. D ata confirm ed by H LR:=F als e.11.11. ISD N LLC & ISDN H LC (as avail able) F etch_ A uthentic ation_ S ets _VL R R estore_ S ubs cri ber_ D ata_VLR S earch_For_ M S_VLR R esul t= P as s? No Ye s A bs ent s ubs cri ber? No Yes Se t negative respons e: Absent subscribe r 1 7 W a it_For_ Ac cess_ R equ es t Figure 55e: Process PRN_VLR (sheet 5) ETSI .

11.093 P rovi de R oam ing N um ber ack 8 Figure 55f: Process PRN_VLR (sheet 6) ETSI .0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber W ait_F o r_ A ccess _ R eques t P RN_ VLR6(8 ) Sign als to the l eft are to the H LR .018 version 3.0 Release 1999 129 ETSI TS 123 018 V3.3GPP TS 23. Page MS negative res po nse No Yes Pa ge MS vi a SGSN Process Access Request Page MS To SGSN MSR N available ? Ye s Busy subsc riber? No W ait_For_ Acc es s_ R e quest 1 MSC per VLR >1 Ye s R eceiv e d M SC num ber= S tored M SC n u mber? No False C onfirme d by radio contact True U se stored M SC numb e r fo r M SRN Absent Subscriber? No Yes 7 Us e r eceiv ed MS C num ber for M SR N Se t neg ati ve response: Sys tem fail ure Proc ess Ac cess R e quest ne gative re spons e Alloc ate MSR N CAM EL_ SE T_SOA See T S 23 .078 Set n egativ e res pon se: No roami ng numbe r 1 Set n egative resp ons e: Abse nt subscriber Store compati bili ty info C S BC . sig nals to/from th e right are to/from the MS C unless shown otherw ise. ISD N B ISD N LLC & ISD (as avai lable) Store Alerti ng Pattern (if recei ved) CLI_PR N_ VLR See T S 23 .11.081 CC BS_H an dle_ PR N See T S 23 .

018 version 3.3GPP TS 23.081 C C BS_H andle_ PR N See TS 23.093 P rovi de R oami ng N um ber ack PAR pendin g:=Fal se.0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber 7 P RN_ VLR7(8 ) Signal s to the lef t are to the H LR .0 Release 1999 130 ETSI TS 123 018 V3. ISD N LLC & ISDN H LC (as avail able) Store A lerti ng P attern ( if recei ved) C LI_PR N_ VLR See TS 23.11.11. PAR succ e ssful := False. ISD N BC . M SR N a v ai lable? Yes M SC p e r VLR 1 Yes No Set ne gativ e res pons e: No ro aming numb er >1 R eceived M SC num be r= S tored M SC num ber? No 1 Fa lse C onfirmed by radi o contact True U se stored M SC number for M SR N U se receiv ed M SC num ber f or M SR N A lloc ate M SR N C AM EL_ SET _SOA See TS 23. Fatal P AR e rror: =Fals e Idle Figure 55g: Process PRN_VLR (sheet 7) ETSI .078 S tore c om pati bility i nfo C S BC .

11. sig nals to/from the ri ght are to/fro m the MS C PAR pen ding:= True P rocess _ A ccess _ R eques t_VLR No R esul t= P as s? Yes PAR succ essful := True PAR succes sful:= Fals e PAR pen ding:= Fa lse PAR pending := Fals e PAR C om pleted Fatal PA R error? Yes No W ait_F o r_ C all_Arr iv al Fatal PA R error:= True Fatal PAR er ror:= Fa lse Cal l a rrived R adio co nnec tion released Call arrived PAR succe ssful := Fal se PAR C o m pleted F atal PAR error:= False Idle Idle Figure 55h: Process PRN_VLR (sheet 8) ETSI .3GPP TS 23.0 Release 1999 131 ETSI TS 123 018 V3.11.0 (2002-03) Process PR N_ VLR Proces s in the VLR to handl e a request for a roam ing num ber 8 P RN_ VLR8(8 ) Signal s to/from the l eft are to/from the proc ess IC H_VLR .018 version 3.

11.0 Release 1999 132 ETSI TS 123 018 V3.3GPP TS 23.11.0 (2002-03) Process R estore_Subscriber_D ata_VLR Proces s in the VLR to restore s ubs criber data RS D_ VLR1(1) Signal s to/from the l eft are to/from the HLR R estore D ata W ait_Fo r_ D ata Restore Data ack R estore D ata n egativ e re spons e Update Sub scriber Data Update HLR number Update MS Not Re ac habl e indic ator If receiv ed from HLR D ata confir med by H LR :=True Figure 56: Process Restore_Subscriber_Data_VLR ETSI .018 version 3.

018 version 3.11.3GPP TS 23.0 Release 1999 133 ETSI TS 123 018 V3.0 (2002-03) Process P S I_VLR Proces s in the VLR to handl e a request from th e H LR for subscriber information Idle P SI_ VLR1(2) Signals to /from the l eft are to/from the H LR.11. si gnals to/from the rig ht are to/from the MSC Provide Sub scriber Info Check _ Pa ram ete rs Res ult= Pass? Yes IMSI known in VLR ? Yes Subscriber state requested? Yes IMSI deta ch ed? No Roam ing in LA allow ed? Yes Set subscriber state requested No No No No Subsc riber state reques ted? Yes Yes No S ubs criber state:= N etw ork determined not reac hab le Subsc riber state := Assumed idl e Location i nfo reques te d? Yes No R etrieve_ Loc ation_ Info_VLR Obtai n Subscriber Info Prov ide Subsc ribe r Info ack Provide Subscriber Info negativ e response W ait_For_ MS C_R esponse Idle Idle Figure 57a: Process PSI_VLR (sheet 1) ETSI .

11.0 (2002-03) Process P S I_VLR Proces s in the VLR to handl e a request from th e H LR for subscriber information W ait_Fo r_ M SC _R espons e P SI_ VLR2(2) Signals to /from t he left are to/from the H LR.0 Release 1999 134 ETSI TS 123 018 V3.11. si gnals to/from the rig ht are to/from the MS C Obtain S ubs criber Info ack S ubs cri ber s tate receiv ed? Yes No S et s ubs cri ber s tate Location i nfo requested? Yes No R etri eve_ Loc at ion_ Info_VLR Provide Subs cri ber Info ack Idle Figure 57b: Process PSI_VLR (sheet 2) ETSI .018 version 3.3GPP TS 23.

0 (2002-03) Procedure Retrieve_Location_Info_VLR Procedure in the VLR to retrieve location information for a subscriber RLI_VLR1(1) Signals to/from the right are to/from the SGSN Current location retrieved:= False Yes Retrieve l ocation info from SGSN? No Current location requested? No Retrieve_ Current_ Location_VLR Yes Send MS information Wait_For_ SGSN_R esponse Send MS Information negativ e response Send MS Information ack False Current location retrieved True Current location requested? No No Current location requested? Yes Cell ID or SAI recei ved? Yes No MS state= Ready? No Location info:= Retrieved location info Location info:= Stored location info Derive location number.11. geodetic information and geographical information Figure 58: Procedure Retrieve_Location_Info_VLR ETSI .018 version 3. geodetic information and geographical information Yes Retrieve_ Current_ Location_VLR False Current location retrieved True Location info:= Stored location info Location info:= Received location info Derive location number.0 Release 1999 135 ETSI TS 123 018 V3.3GPP TS 23.11.

11.3GPP TS 23.11.0 Release 1999 136 ETSI TS 123 018 V3. signals to/from the right are to/from the MSC Paging via SGSN possible? Yes No Set paging via SGSN possible No Location area ID known? Yes Page type= Active location retrieval Search for MS Page t ype= Active location retrieval Page MS Wait_For_ Search_ Result Wait_For_ Page_ Result Search f or MS ack Search for MS negative response Search for MS via SGSN Page MS ack Page MS negative response Page MS via SGSN Roaming in LA allowed? Yes No Current location retrieved:= True Subscriber state:=Not reachable Page MS Current location retrieved:= True Page MS Wait_For_ Search_ Result Wait_For_ Page_ Result Figure 59: Procedure Retrieve_Current_Location_VLR ETSI .018 version 3.0 (2002-03) Procedure Retrieve_Current_Location_VLR Procedure in the VLR to retrieve the current location information for a subscriber RCL_VLR1(1) Signals to/from the left are to/from the SGSN.

ETSI .2.2. the state is busy.413 [26]) with the Request Type IE set to "Change of service area".4. or sent a CM service request for anything other than a circuit-switched call.0 Release 1999 137 ETSI TS 123 018 V3. or completed the location registration procedure. The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting Control procedure (see 3GPP TS 25. If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct". The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.2.2 Functional requirements of MSC Process Prepage_MSC Procedure Prepaging_Page_MS_MSC The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network.2.4 7.5 7. The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.4.3 Prepaging_Search_For_MS_MSC The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network.6 Process RCL_MSC Procedure Current_Location_Page_MSC The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. otherwise assumed idle.7 Procedure Current_Location_Search_MSC The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network.413 [26]) with the Request Type IE set to "Change of service area".018 version 3. 7. The test “GSM Access” takes the “Yes” exit if the MS is using a GSM radio access to communicate with the network.4.2. 7. The signal input "MS connection established" indicates that the MS has responded to paging.11.11.1 7.2.3GPP TS 23. or completed the location registration procedure. The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting Control procedure (see 3GPP TS 25.2. 7. 7.4 Process OSI_MSC If the MS is engaged on a circuit-switched call. The test “GSM Access” takes the “Yes” exit if the MS is using a GSM radio access to communicate with the network. The signal input "MS connection established" indicates that the MS has responded to paging. If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct".0 (2002-03) 7.4.4.2.4.4. or sent a CM service request for anything other than a circuit-switched call.

s ignals t o the right are to t he BSS Idle Page MS Search for MS Prepaging_ Page_M S_MSC Prepaging_ Search_for_ MS_MSC Yes Result= Pass ? No Yes Result= Pass ? No Idle Proc ess _ Acces_ Request _MSC Idle No Result= Pass ? Yes Start radio guard timer Idle Wait_F or_ Call_Arrival Call arriv ed Radio guard timer expired I nternal Release transaction BSS released t he radio resource Release transaction Stop radio guard timer Radio connec tion released Radio connec tion released Idle Figure 60: Process Prepage_MSC ETSI .0 (2002-03) Process Prepage_MSC Proc es s in t he MSC t o handle a pre-paging request PP_MSC1(1) Signals to/f rom the lef t are to/f rom t he VLR.0 Release 1999 138 ETSI TS 123 018 V3.11.11.3GPP TS 23.018 version 3.

11.11. signals to/from the ri ght are to/from the VLR unless m arked othe rw ise Loc ati on area ID known? Yes MS connection exis ts ? No No M S busy? Yes In specified l oc ation area Pa ge No Set negative response: Busy S ubs criber No P PP MS_M 1(1) Yes Set negativ e res ponse: U nknown LAI Yes Pagi ng vi a SGSN possi ble? Page MS vi a SGS N Set acces s c onnection s tatus Page MS negat ive res po ns e Sta rt Page response tim er R esul t:= Pas s R esult:= Fai l W ait_For_ Pa ge_ Res ponse MS connection establis hed Page response ti mer e xp ired CM Serv ice R equest For circui tswi tched cal l CM Serv ice R equest To process OC H_MSC Se t ac ce ss connection status Set negat ive r esponse: A bs ent S ubs cri ber P age M S negative response Set negativ e res ponse: Busy Subsc ribe r (N D U B) Page MS negat ive res po ns e R es ult:= Pa ss R esul t:= F ail R esult:= Fai l Figure 61: Procedure Prepaging_Page_MS_MSC ETSI .018 version 3.0 Release 1999 139 ETSI TS 123 018 V3.0 (2002-03) Procedure P repaging_P age_M S _MS C Procedure in t he MSC to page a n M S in a specified l ocation area Signal s to/from the l eft are to/fro m the BSS.3GPP TS 23.

0 Release 1999 140 ETSI TS 123 018 V3.0 (2002-03) Procedure P repaging_S earch_For_MS _M S C Procedure in t he MSC to page a n M S in a specified l ocation area Signal s to/from the l eft are to/fro m the BSS.018 version 3. signals to/from the ri ght are to/from the VLR unless m arked othe rw ise Paging vi a SGSN possi bl e? MS connection exis ts ? No No M S busy? Yes Page MS vi a SGS N No Set negativ e res ponse: Busy Subsc ribe r Yes P PS MS_M 1(1) Yes In speci fied loc ation area Page Set acces s c onnection s tatus Page MS negat ive res po ns e Sta rt Page response tim er R esul t:= Pas s R esult:= Fai l W ait_For_ Pa ge_ Res ponse MS connection establis hed Page response ti mer e xp ired CM Serv ice R equest For circui tswi tched cal l CM Serv ice R equest To process OC H_MSC Se t ac ce ss connection status Set negat ive r esponse: A bs ent S ubs cri ber P age M S negative response Set negativ e res ponse: Busy Subsc ribe r (N D U B) Page MS negat ive res po ns e R es ult:= Pa ss R esul t:= F ail R esult:= Fai l Figure 62: Procedure Prepaging_Search_For_MS_MSC ETSI .11.3GPP TS 23.11.

11.0 Release 1999 141 ETSI TS 123 018 V3.0 (2002-03) Process O SI_MSC Proc es s in the MS C to hand le a request from the VLR for inform ation on the subscriber's location and state O SI_M S C1(1) Signals to /from t he left are to/from the VLR Idle Obtain Subs cri ber Info S ubs cri ber s tate requested? Yes No S et s ubs criber s tate Obtain Subs cri ber Info ack Idle Figure 63: Process OSI_MSC ETSI .11.3GPP TS 23.018 version 3.

0 Release 1999 142 ETSI TS 123 018 V3.018 version 3.11.0 (2002-03) P ro c e s s R C L _ M S C P ro c es s in th e MS C to r etr i ev e th e cu r re n t lo ca tio n o f a su b sc rib e r R C L _ M S C 1( 1) S ig n a ls to /fr o m t he l eft a re to /fr om th e V L R Id le S e ar ch fo r MS P a g e MS Cu r re n t_ L o ca tio n _ Se a r ch _ M S C C u rr e n t_ L o c ati o n_ Page_M SC Id le Figure 64: Process RCL_MSC ETSI .3GPP TS 23.11.

3GPP TS 23.11. signals to/from the right are to/from the VLR unless marked otherwise MS connection exists? No No Yes Paging via SGSN possible? Yes Yes In all location area Page Search MS via SGSN GSM Access? No Start Page response timer Yes Report on change of service area? No Wait_For_ Page_ Response For circuitswitched call CM Service Request Page response timer expired MS connection established Location Reporting Control To process OCH_MSC CM Service Request Release transaction Wait_For_ Location_ Report Location Report Yes SAI received? No Set negative response: Busy subscriber Set negative response: Absent subscriber Set negative response: Busy Subscriber Search MS negative response Search MS negative response Search MS ack Search MS negative response Figure 65: Procedure Current_Location_Page_MSC ETSI .11.018 version 3.0 Release 1999 143 ETSI TS 123 018 V3.0 (2002-03) Procedure Current_Location_Search_MSC Procedure in the MSC to page an MS in a specified location area for Active Location Retrieval CLS_MSC1(1) Signals to/from the left are to/from the BSS/RAN.

s ignals t o/from the right are to/f rom t he VLR unless marked otherwis e MS connec tion exist s? No No Paging via SGSN possible? Yes Search for MS via SGSN Yes I n all location areas Page Start Page response timer Wait _F or_ Page_ Respons e For c ircuit s wit ched c all CM Serv ice Request Page response timer expired MS connec tion established Yes GSM Access? No To process O CH_MSC CM Serv ice Request Release transaction Set negativ e response: Busy subscriber Set negativ e response: Absent subscriber Set negativ e response: Busy subscriber Search for MS negativ e response Search for MS negativ e response Search for MS ack Search for MS negativ e response Figure 66: Procedure Current_Location_Search_MSC ETSI .018 version 3.11.3GPP TS 23.0 Release 1999 144 ETSI TS 123 018 V3.11.0 (2002-03) Procedure Current_Location_Search_MSC Proc edure in the MSC t o page an MS in all location areas for Act ive Location Retrieval CLS_MSC1(1) Signals to/f rom the lef t are to/f rom t he BSS.

If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 3 or later. sheet 3. sheet 10: the procedure CAMEL_MT_GMSC_DISC6 is called if the VMSC supports CAMEL phase 3 or later.0 Release 1999 145 ETSI TS 123 018 V3. it is specified in 3GPP TS 23. UUS1 implicit active. UUS1 explicit active. Sheet 2.078 [12].1. Sheet 1: the variables UUS result sent. accessible to the procedures Establish_Terminating_TCH_If_Required. Sheet 1: the procedure CAMEL_ICH_MSC_INIT is specific to CAMEL phase 3 or later. ETSI . The mapping used is a matter for the network operator. unspecified Sheet 2.850 [36]) is shown in table 2. sheet 7. Sheet 2: the signal input Complete Call will be received in the state Wait_For_Page_Request only if the MSC/VLR supports pre-paging. Sheet 2: the procedure Process_Access_Request_MSC is specified in subclause 7. sheet 8. it is specified in 3GPP TS 23. depending on the telephony signalling system used.11. this signal will not be received from the VLR. sheet 5.2. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 3 or later. sheet 7.11. UUS3 active and UUS CF interaction are specific to UUS. Sheet 3: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports CAMEL phase 3 or later. sheet 3: the suggested mapping from values of the Send Info For Incoming Call negative response information element to values of the ISUP release cause (see ITU-T Recommendation Q.007 [29]. They are accessible to all UUS specific procedures.078 [12]. ACM sent.3.1. unspecified Protocol error. sheet 10: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC supports CAMEL phase 3 or later. 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 ISUP release cause name Subscriber absent User busy Call rejected 21 111 19 111 111 Call rejected Protocol error. sheet 4.1 7. Sheet 1: the handling starting with the input signal "Continue CAMEL handling" is specific to CAMEL phase 3 or later. Send_ACM_If_Required.1 MT call Functional requirements of serving MSC Process ICH_MSC Sheet 1: the rules for converting the ISDN BC/LLC/HLC to a bearer service or teleservice are specified in 3GPP TS 29.3 7.018 version 3. Send_Answer_If_Required and Send_Network_Connect_If_Required. processing continues from the "No" exit of the test "Result=Reconnect?". Sheet 3: the procedure CAMEL_MT_GMSC_DISC5 is called if the VMSC supports CAMEL phase 3 or later. Sheet 2.1. Sheet 1: the task "Store UUS information (if received)" is executed only if the VMSC supports UUS.078 [12]. Sheet 1: the variables TCH allocated. sheet 8.078 [12].3. Answer sent and Network connect sent are global data.3GPP TS 23. unspecified No answer from user (user alerted) Protocol error. processing continues from the "No" exit of the test "Result=Reconnect?". UUS2 active.0 (2002-03) 7.

sheet 9: the procedures CD_Failure and CD_Success are specific to Call Deflection.1. Sheet 5: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. Sheet 5: the procedure UUS_ICH_Set_Info_In_IAM is specific to UUS. it is specified in 3GPP TS 23. sheet 8. it is specified in 3GPP TS 23. sheet 4. Sheet 3. Sheet 5. sheet 8: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS. Sheet 4: the procedure CAMEL_Check_ORLCF_VMSC is specific to CAMEL phase 2 or later. Sheet 3.078 [12].0 Release 1999 146 ETSI TS 123 018 V3. they are specified in 3GPP TS 23.093 [22]. Sheet 5: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in the Perform Call Forwarding ack. - Sheet 4: the procedure Handle_ORLCF_VMSC is specific to Support of Optimal Routeing. it is specified in 3GPP TS 23.11. Sheet 3: the processing in the branch starting with the input signal"Process Call Waiting" is specific to Call Wait. then ORLCF shall not take place (‘VMSCCF’ result from CAMEL_Check_ORLCF_VMSC). If CAMEL information is available for the subscriber and the GMSC supports the required CAMEL phase. it is specified in 3GPP TS 23.0 (2002-03) Sheet 3: If the VMSC does not support CAMEL phase 3 or later. Sheet 4: the procedure UUS_ICH_Check_Support is specific to UUS. The Resume Call Handling request shall include the relevant CAMEL information (‘ORLCF’ result from CAMEL_Check_ORLCF_VMSC). Sheet 5: it is an operator option whether to send an Address Complete message if the VLR returns forwarding information.3GPP TS 23.0 72 [11].087 [20]. sheet 11: the procedure CCBS_Check_Last_Call is specific to CCBS. If the VMSC does not support CW this signal will not be received from the VLR. Sheet 5: The task "set redirection information" includes the mapping of the MSISDN parameter received in the Send Info For Incoming Call ack message to the redirecting number of the IAM message and the setting of the presentation indicator of the redirecting number of the IAM message according to the value of the Redirecting presentation parameter received in the Send Info For Incoming Call ack message. processing starts with the possible call of the procedure CCBS_Check_Last_Call. it is specified in 3GPP TS 23. If CAMEL information is available for the subscriber but the GMSC does not support the required CAMEL phase. then ORLCF may take place. ETSI . If the VLR does not support CAMEL or no CAMEL information is available for the subscriber. If the VMSC sends an Address Complete message.072 [11].079 [13].2. Sheet 5: the procedure CAMEL_MT_VMSC_Notify_CF is specific to CAMEL phase 3 or later.2.11.078 [12]. the procedure CD_Reject is specific to Call Deflection. processing continues from the "Continue" exit of the test "ResultForwarding Failed?". Sheet 5.093 [22]. Sheet 5: the procedure Activate_CF_Process is specified in subclause 7. the procedure Complete_Call_In_MSC and the procedure Process_Call_Waiting_MSC will not return a "Reconnect" result. If the VMSC does not support Optimal Routeing. then ORLCF may take place (‘ORLCF’ result from CAMEL_Check_ORLCF_VMSC).018 version 3. sheet 7: the procedure Send_ACM_If_Required is specified in subclause 7. sheet 10.7.3. Sheet 5: If the VMSC does not support CAMEL phase 3 or later.078 [12].087 [20]. it shall include the called party’s status field of the Backward call indicator set to "no indication".1. Sheet4. it is specified in 3GPP TS 23.072 [11]. It is specified in 3GPP TS 23. it is specified in 3GPP TS 23. the procedure CD_Success is specific to Call Deflection. it is specified in 3GPP TS 23. Sheet 3. it is specified in 3GPP TS 23.

Sheet 1: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the established phase (called party answer). Sheet 11: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS. it acts as a transparent relay for messages received from the GMSC and the process MT_CF_MSC.11. Sheet 11.2. Sheet 11. the input signal Send Info For MT Reconnected Call ack will not be received. If the VMSC does not support CAMEL phase 3 or later.2 Procedure Page_MS_MSC Sheet 1: the test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. Sheet 1: the procedure Check_MT_Multicall_MSC is specific to Multicall.1. the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call. ETSI . If the VMSC does not support Multicall. sheet 12: the procedure CAMEL_MT_GMSC_ DISC2 is called if the VMSC supports CAMEL phase 3 or later. Sheet 9: the procedure Handle_ORLCF_MSC is specific to OR.2.1. If the VMSC does not support CAMEL phase 3 or later. If the VMSC does not support OR. it is specified in 3GPP TS 23.2. Sheet 8: the procedure CCBS_MT_MSC_Check_Forwarding is specific to CCBS.0 Release 1999 147 ETSI TS 123 018 V3. If the VMSC does not support CAMEL phase 3 or later. processing continues from the "No" exit of the test "Result=Reconnect?". processing continues from the "Yes" exit of the test "Result=Not provisioned?".135 [24]). Sheet 1: the test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.093 [22]. Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls. If the VMSC does not support CAMEL phase 3 or later.018 version 3.3.6.1. If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23. the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23.135 [24]. processing continues from the "No" exit of the test "Result=Reconnect?".5. Any message other than Address Complete. it is specified in 3GPP TS 23. Sheet 9: the processing on this sheet is specific to CAMEL phase 3 or later. it is specified in 3GPP TS 23. Connect. sheet 12: the procedure CAMEL_MT_GMSC_DISC1 is called if the VMSC supports CAMEL phase 3 or later.078 [12]. Sheet 12: after the VMSC has sent an IAM to the process MT_CF_MSC.079 [13]. it is specified in 3GPP TS 23. Sheet 13: The processing on this sheet is specific to CAMEL phase 3 or later. Sheet 7: the procedure Send_Answer_If_Required is specified in subclause 7. it is specified in 3GPP TS 23. the input signal Int_Release Call will not be received.078 [12]. because the VLR will always use a page type of "circuit-switched call".0 (2002-03) Sheet 6: The processing on this sheet is specific to CAMEL phase 3 or later.4. 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. but the more generalised procedure Page_MS_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures.3GPP TS 23. Sheet 1: if there is one established call. Sheet 7: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later.1. Sheet 7: the procedure Handle_COLP_Forwarding_Interaction is specified in subclause 7. it is specified in 3GPP TS 23. the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists. the input signal Int_Release Call will not be received. processing continues from the "No" exit of the test "Result = Forwarding Failed?". Sheet 7: the procedure Send_Network_Connect_If_Required is specified in subclause 7. Answer or Release causes no change of state in the process ICH_MSC. 7. Sheet 1: for an SMS or SS page.11.078 [12]. If there are two or more established calls (the Multicall case).087 [20].

093 [22].078 [12].087 [20]. Sheet 1. If the VMSC does not support CAMEL phase 3 or later. processing continues from the "No" exit of the test "Result=Reconnect?". sheet 7: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC supports CAMEL phase 3 or later. sheet 10: the procedure CAMEL_MT_GMSC_DISC6 is called if the VMSC supports CAMEL phase 3 or later.3. it is specified in 3GPP TS 23. Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS. sheet 5.018 version 3. the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists. sheet 2: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of information in the Set-up and Call Confirmed messages.3. it is specified in 3GPP TS 23.3 Procedure Search_For_MS_MSC Sheet 1: the test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. sheet 3. sheet 5: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS. because the VLR will always use a page type of "circuit-switched call".4 Procedure Complete_Call_In_MSC Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP.135 [24]. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.1. Sheet 1: for an SMS or SS page. If the VMSC does not support Multicall.135 [24].1. ETSI . 7. sheet 9: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS. Sheet 3. or sent a CM service request for anything other than a circuit-switched call. sheet 6. Sheet 2. sheet 6. the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call. 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 test "SMS or SS page" is not required for the handling of circuit-switched calls. or completed the location registration procedure. processing continues from the “Yes” exit of the test “Result=Not provisioned?”. Sheet 2. it is specified in 3GPP TS 23. Sheet 2: the procedure Establish_Terminating_TCH_Multicall1 is specific to Multicall. sheet 9.11. 7. If there are two or more established calls (the Multicall case). Sheet 2: the test "Result=Rejected?" can take the "Yes" exit only if the procedure Establish_Terminating_TCH_Multicall1 was called. Sheet 1: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the established phase (called party answer). Sheet 2: the signal input "MS connection established" indicates that the MS has responded to paging. the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23. or sent a CM service request for anything other than a circuit-switched call.0 (2002-03) Sheet 2: the signal input "MS connection established" indicates that the MS has responded to paging. it is specified in 3GPP TS 23. Sheet 1: if there is one established call. Sheet 1: the procedure Check_MT_Multicall_MSC is specific to Multicall. or completed the location registration procedure. Sheet 1: the test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call. Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS. it is specified in 3GPP TS 23.093 [22].135 [24]).093 [22]. sheet 5. sheet 3.0 Release 1999 148 ETSI TS 123 018 V3. Sheet 2. but the more generalised procedure Search_For_MS_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures.3GPP TS 23.078 [12]. sheet 4. it is specified in 3GPP TS 23.11.

2. If the VMSC does not support UUS. processing continues from the “Yes” exit of the test “Result=Pass?”. ETSI . Sheet 11: the procedures UUS_MSC_Check_UUS2_UUI_to MS and UUS_MSC_Check_UUS2_UUI_to NW are specific to UUS.0 (2002-03) Sheet 3: the procedure CAMEL_Start_TNRy is called if the VMSC supports CAMEL phase 3 or later.078 [12]. it is specified in 3GPP TS 23.2. Sheet 3.4.087 [20].1. processing continues from the "Yes" exit of the test "Result=Pass?". sheet 11: the procedure Handling_CD_MSC is specific to Call Deflection. it is specified in 3GPP TS 23. sheet 6: the procedure Establish_Terminating_TCH_Multicall2 is specific to Multicall. Sheet 5. sheet 7: the procedure Handle_AoC_MT_MSC is specific to AoC. sheet 7: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP. they are specified in 3GPP TS 23. it is specified in 3GPP TS 23.3GPP TS 23.018 version 3. processing continues from the “Yes” exit of the test “Result=Pass?”. Sheet 4. it is specified in 3GPP TS 23. Sheet 3: the procedure Send_ACM_If_Required is specified in subclause 7.1. Sheet 1: the procedure Establish_Terminating_TCH_Multicall1 is specific to Multicall.087 [20]. sheet 11: the processing in the branch starting with the input "CD Request" is specific to Call Deflection. 7. Sheet 5.087 [20]. If the VMSC does not support Multicall. Sheet 1: the Call Confirmed message indicates "busy" for the successful case. Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS. Sheet 4. If the VMSC does not support UUS.078 [12].11. processing continues from the "Yes" exit of the test "Result=Pass?". sheet 10: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS.072 [11]. it is specified in 3GPP TS 23. Sheet 1: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of information in the Set-up and Call Confirmed messages.3.078 [12]. Sheet 11: the procedure CD_UUS_Interaction is specific to Call Deflection. Sheet 8.087 [20]. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 6: the procedure CAMEL_Stop_TNRy is called if the VMSC supports CAMEL phase 3 or later. processing continues from the "Yes" exit of the test "Result=Pass?". processing continues from the "Yes" exit of the test "Result=Pass?".11. it is specified in 3GPP TS 23.3. If the VMSC does not support Multicall.135 [24]. If the VMSC does not support AoC. Sheet 4. sheet 7: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later.0 Release 1999 149 ETSI TS 123 018 V3. Sheet 7: the procedure Send_Answer_If_Required is specified in subclause 7.5 Procedure Process_Call_Waiting_MSC Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP.5.087 [20].1. Sheet 3. If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.1. it is specified in 3GPP TS 23. sheet 11: the procedure UUS_ICH_Check_Forwarding is specific to UUS. Sheet 8: the input signal "CAMEL TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or later. if the VMSC does not support Call Deflection the input is discarded. sheet 6: the procedure UUS_ICH_Check_Support is specific to UUS.072 [11]. Sheet 4: the procedure Send_Network_Connect_If_Required is specified in subclause 7. Sheet 3: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS.135 [24].2. Sheet 9.

If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23.11. processing continues from the "No" exit of the test "Result=Reconnect?". sheet 5: the procedure UUS_ICH_Check_Support is specific to UUS.093 [22].078 [12]. processing continues from the "Yes" exit of the test "Result=Pass?" where the test follows the procedure call. Sheet 2.135 [34]. Sheet 5: the procedure CAMEL_Stop_TNRy is called if the VMSC supports CAMEL phase 3 or later. Sheet 6: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later.072 [11]. it is specified in 3GPP TS 23. Sheet 5: the procedure Establish_Terminating_TCH_Multicall2 is specific to Multicall. Sheet 2: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS. Sheet 2. Sheet 7: the procedure CAMEL_MT_GMSC_DISC5 is called if the VMSC supports CAMEL phase 3 or later.11. Sheet 2. sheet 8: the procedure CAMEL_MT_GMSC_DISC6 is called if the VMSC supports CAMEL phase 3 or later. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?" on sheet 6. Sheet 4.0 Release 1999 150 ETSI TS 123 018 V3. it is specified in 3GPP TS 23. Sheet 6: the procedure Send_Answer_If_Required is specified in subclause 7.1. it is specified in 3GPP TS 23.2.078 [12]. sheet 3.087 [20]. If the VMSC does not support UUS. it is specified in 3GPP TS 23. sheet 8: the processing in the branch starting with the input "CD Request" is specific to Call Deflection. they are specified in 3GPP TS 23.078 [12]. sheet 7: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC supports CAMEL phase 3 or later. sheet 7: the Release transaction (reject) message covers all unsuccessful cases not otherwise indicated.078 [12].087 [20]. Sheet 2. Sheet 8: the procedures UUS_MSC_Check_UUS2_UUI_to_MS and UUS_MSC_Check_UUS2_UUI_to_NW are specific to UUS.2. sheet 8: the procedure UUS_ICH_Check_Forwarding is specific to UUS.0 (2002-03) Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS. Sheet 6: the procedure Handle_AoC_MT_MSC is specific to AoC. it is specified in 3GPP TS 23. sheet 3.3.087 [20].078 [12]. Sheet 2: the procedure CAMEL_Start_TNRy is called if the VMSC supports CAMEL phase 3 or later. sheet 7: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS.4. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.3GPP TS 23. sheet 8: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS. it is specified in 3GPP TS 23.1. sheet 4. If the VMSC does not support CAMEL phase 3 or later. Sheet 7: the input signal "CAMEL TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or later.093 [22]. sheet 8: the procedure Handling_CD_MSC is specific to Call Deflection.093 [22].087 [20]. sheet 6. if the VMSC does not support Call Deflection the input is discarded. Sheet 6: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP. processing continues from the "Yes" exit of the test "Result=Pass?". it is specified in 3GPP TS 23. Sheet 7. If the VMSC does not support UUS. it is specified in 3GPP TS 23. If the VMSC does not support AoC.078 [12].018 version 3. it is specified in 3GPP TS 23. Sheet 2. sheet 3. processing continues from the "No" exit of the test "Result=Reconnect?". it is specified in 3GPP TS 23. Sheet 3. If the VMSC does not support CAMEL phase 3 or later. Sheet 2: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS. processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 4. Sheet 2: the procedure Send_ACM_If_Required is specified in subclause 7. ETSI .

8 7.3GPP TS 23.1.10 Procedure Derive_GSM_BC_MSC Procedure Establish_Terminating_TCH_If_Required 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.3.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.7 7.0 (2002-03) Sheet 8: the procedure CD_UUS_Interaction is specific to Call Deflection.0 Release 1999 151 ETSI TS 123 018 V3.1. 7.1. 7. The message is saved for processing after return from the procedure.11.3. The message is saved for processing after return from the procedure.0 72 [11].018 version 3. ETSI .1.9 7.3. it is specified in GSM 23.3.1.3.11.

0 Release 1999 152 ETSI TS 123 018 V3. UUS1 implicit active:=F alse. Call answered := False Continue CAMEL Handling CAMEL_ ICH_MSC_ INIT See TS 23.11.11. UUS1 result sent:=False. Store UUS information (i f received) Send Info For Incoming Call Wait_F or_ Page_R equest ACM sent:=False. BOR :=False.0 (2002-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) c all ICH_MSC1(13) Signals to/from the left are to/from the BSS. UUS3 active:=False. signals to/from the right are to/from the VLR unless marked otherwise Idle Initial Address From GMSC Convert ISDN BC/LLC/HLC (if present) to bearer service/teleservi ce & CS BC.018 version 3. UUS2 active:=False.3GPP TS 23. TCH alloc ated:=False.078 Result? Reconnect MSR N Aborted Fail Set Suppress VT-CSI Set cause Send Info For MT R econnected Call Send Info For Incoming Call Release Release call resources Wait_For_ Reconnected_ Call_Result Wait_F or_ Page_R equest Idle Figure 67a: Process ICH_MSC (sheet 1) ETSI . UUS1 explicit active:=F alse. Network c onnect sent:=False. UUS C F interaction:=False. Answer sent:=False.

0 (2002-03) Pro c ess IC H _ M SC Proc es s in the MS C to ha ndle an incom i ng ( M T) call W ait_Fo r_ P age_R equest I C H_ M S C 2 (1 3 ) S ignal s t o/fr om the left are to/fr om th e GM SC. signa ls to/fr om the rig ht are to/fr om th e V LR Send Info For In coming Ca ll ne gative res ponse S et cause P age M S Send In fo F or Inco m ing C all Ack C all is to b e for war ded S earc h For M S Com plete C all P age_ M S_ M S C 1 Searc h_For_ M S _M SC 2 R esu lt= P as s? No No R esu lt= F ail? Ye s Yes Ye s Re su lt= Pass? No Re su lt= Fail No CAM EL_ MT _GM S C_ DIS C 6 P rocess _ A ccess_ R equest_M S C Y es CA ME L_ MT _GM S C_ DISC 6 Release call re so ur ces R esult= P as s? No Yes Rel ease call res our ce s CA ME L_ M T_GM SC _ DIS C 4 Y es Idl e W ait_ For_ M T _ Cal l_ R esult W ait_For _ M T_ Call _ R esult C A M E L_ M T_GM S C _ D IS C4 Y es W ait_For _ M T_C all_ Resu lt Id le Re sult= R econnect? No Rel eas e R esult= R econnect? No Send Info For M T Rec onnected C all R elease Re lease cal l res our ces R elease c al l r esources Idle W ait_ For_ R eco nnec te d_ C al l_R es ult Idle Figure 67b: Process ICH_MSC (sheet 2) ETSI .018 version 3.3GPP TS 23.11.11.0 Release 1999 153 ETSI TS 123 018 V3.

3GPP TS 23.0 (2002-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) c all Wait_For_ MT_Call_ Result ICH_MSC3(13) Signals to/from the left are to/from the GM SC.093 Release call resources Idle Figure 67c: Process ICH_MSC (sheet 3) ETSI .018 version 3.093 Result= Pass? No Store CW Treatment indicator for this call if rec eived in SII2 Yes Result= Pass? No UUS_ICH_ Check_ Suppor t See TS 23.0 Release 1999 154 ETSI TS 123 018 V3.11.11.087 Call answered := True Set cause Cause= No Subscriber Reply? No CAMEL_ MT_GMSC_ DISC4 Yes Yes Result= Fail CAMEL_ MT_GMSC_ DISC5 Wait_F or_ Clear Yes Result= Fail Wait_F or_ MT_Call_ Result Yes Yes Result= Reconnect? No Send Info For MT Rec onnected Call Release No No No Result= Reconnect? Yes Send Info For MT R ec onnected Call Result= Reconnect? No Wait_F or_ Reconnected_ Call_Result Wait_F or_ Reconnected_ Call_Res ult Release transaction CCBS_Check_ Last_Call See TS 23.072 Complete_ Call_In_MSC Proc ess_ Call_ Waiting_MSC CCBS_Set_ Diagnostic_ For_Release Yes See TS 23. signals to/from the right are to/from the VLR unless marked otherwise Send Info For Incoming Call negati ve response Complete Call 2 Process Call Waiting CD_Reject See TS 23.

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

11.0 Release 1999 156 ETSI TS 123 018 V3.3GPP TS 23.018 version 3. 093 CD_Suc ces s See TS 23. 078 Send Inf o For MT R ec onnec ted Call CCBS_Check_ Last_Call See TS 23. 078 See TS 23. 078 Yes Result= Reconnect ? No 4 CCBS_Check_ Last_Call See TS 23.0 (2002-03) Process ICH_MSC 3 Proc es s in t he MSC t o handle an inc oming (MT) c all Yes Ty pe of forwarding= Reconnec t? No CAMEL_ MT_VM SC_ Notify_C F ICH_MSC5(13) Signals to t he r ight are to t he VLR unless marked otherwis e See TS 23. 072 Wait _F or_ Reconnect ed_ Call_Res ult Idle Wait_F or_ Forward_ACM Figure 67e: Process ICH_MSC (sheet 5) ETSI .11. 093 Set redirecti on informat ion Send_ACM_ If _Required Activate_ CF_Proc ess No Result= Fail? Yes CAMEL_ MT_G MSC_ DISC4 UUS_I CH_ Set _Inf o_ In_IAM See TS 23. T rue) See TS 23. 072 CAMEL_St ore_ Destination_ Address (False. 087 Yes Result= Reconnect ? No Init ial Address Message To process MT_CF_MSC CD_Failure See TS 23.

3GPP TS 23.018 version 3. si gnals to/fr om th e rig ht are to/fr om the VL R unless m a r ked other wise Int_R elease_ C all F r om gsm S S F A bor t R ele ase R ele ase T ran sac ti on T o B SS R el ea se c all r esourc e s Idle Figure 67f: Process ICH_MSC (sheet 6) ETSI .0 Release 1999 157 ETSI TS 123 018 V3.0 (2002-03) Pro c ess IC H _ M SC Proc es s in the MS C to ha ndle an incom i ng ( M T) call W a it_F or_M T_C all_ Res ul t.11.11. W a it_F or_R ec onne cte d_C all_R es ult I C H_ M S C 6 (1 3 ) S ignals to /fr om t he left are to/from the GM SC.

078 CAMEL_ MT_GMSC_ DISC4 CAMEL_ MT_GMSC_ ANSW ER See TS 23.3GPP TS 23.11.0 Release 1999 158 ETSI TS 123 018 V3.018 version 3. signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Address Complete Connect Send_ACM_ If_Required Wait_For_ Forward_Answer Release Release Answer Release See TS 23.0 (2002-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) c all Wait_For_ Forward_ACM ICH_MSC7(13) Signals to/from the left are to/from the GMSC.078 CAMEL_ MT_GMSC_ ANSW ER CAMEL_ MT_GMSC_ DISC6 Yes See TS 23.078 Result= Fail? No No Result= Reconnect? Idle Yes Result= Fail? No Yes Yes Release Result= Reconnect? No Send Info For MT R econnected Call Handle_COLP_ Forwarding_ Interaction_MSC Send Info For MT R econnected Call Yes Result= Reconnec t? No Handle_COLP_ Forwarding_ Interaction_MSC To VLR To VLR Wait_F or_ Reconnected_ Call_Result Set COLP presentation indicator Wait_For_ Reconnected_ Call_Result Set COLP presentation indicator Release call resources Send_Answer_ If_Required Send_Network_ Connect_ If_Required Idle Call answered := True Wait_For_ Forward_Clear Figure 67g: Process ICH_MSC (sheet 7) ETSI .078 See TS 23.11.

093 C C B S _MT _ M SC _C hec k_ F orw ardi ng Send In fo F or M T R econnected C all T o VL R W ait_For _ R econnected_ C all _Re sul t Send In fo F or M T R econnected C all neg ative r espons e S ee T S 23.0 Release 1999 159 ETSI TS 123 018 V3.3GPP TS 23. si gnals to/fr om the ri ght ar e to /fr om the pr oc e ss M T_C F_M SC unless m ar ked othe rw ise Rel eas e R elease Rel eas e C A M EL_ M T _ GM SC _ D ISC4 Yes S ee TS 23.11.093 C C B S _Set_ D i agnostic_ F or_ R elease S et cau se R elease R e lease Int_Exception T o gs mS SF R ele as e c al l r esourc es Idle Figure 67h: Process ICH_MSC (sheet 8) ETSI .078 Se e TS 23 .018 version 3.0 (2002-03) Pro c ess IC H _ M SC Proc es s in the MS C to ha ndle an incom i ng ( M T) call W ait_Fo r_ F orw ard_A C M I C H_ M S C 8 (1 3 ) Si gna ls to/fr o m the l eft ar e to /fr om the GM S C .078 CA ME L_ MT _GM SC_ DIS C 6 R esul t= R econnect? No S ee T S 23.11.

072 CD_Failure CD_Suc cess See TS 23.0 (2002-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) c all Wait_For_ Reconnected_ Call_Result ICH_MSC9(13) Signals from the left are from the GMSC.072 Wait_For_ Release_From_ GM SC Release CAMEL_ MT_GMSC_ DISC6 See TS 23.079 No Result= Accepted? Yes No Result= Forwarding Failed?? Yes 4 See TS 23.11.0 Release 1999 160 ETSI TS 123 018 V3.018 version 3.3GPP TS 23. signals from the right are from the VLR Send Info For MT Reconnected Call ack True Call answered False Handle_ OR LCF_VMSC See TS 23.11.078 CCBS_Check_ Last_Call See TS 23.093 Release call resources Idle Figure 67i: Process ICH_MSC (sheet 9) ETSI .

11.078 R esult= R econnect? No Yes Release transacti on R elease C C BS_Check _ Last_C all See TS 23.3GPP TS 23.093 A bor t T o VLR Send Info F or M T R econnected C all To VLR R elease c all resourc es Idle W ait_For_ R econnected_ C all _Resul t Figure 67j: Process ICH_MSC (sheet 10) ETSI . si gnals to/from the rig ht are to/from the BSS unless marked otherwise R elease trans action R elease CAM EL_ MT _GMSC_ DISC 6 See T S 23 .0 (2002-03) Proc ess IC H_MSC Proc es s in the MS C to handle an incomi ng (M T) call W ait_Fo r_ M T _Cal l_ R esult ICH_M S C10(13) Signals to /from t he left are to/from the GM SC.0 Release 1999 161 ETSI TS 123 018 V3.078 C AMEL_ M T_GM SC _ D ISC4 See TS 23.11.018 version 3.

087 C A M E L_ M T_GM SC _ D ISC2 S ee TS 2 3.11. signa ls to/fr om the rig ht are to/from th e B SS unless m ar ke d other wi se R elease tr ans action R elease UU S_M S C_ Check_ UU S1_U UI S ee T S 23 .0 (2002-03) Pro c ess IC H _ M SC Proc es s in the MS C to ha ndle an incom i ng ( M T) call W ait_Fo r_ C lea r I C H_ M S C 1 1 (1 3 ) S ignal s t o/fr om the left are to/fr om th e GM SC.3GPP TS 23.078 Release transacti on R esult= R econnect? No Yes See TS 23.0 Release 1999 162 ETSI TS 123 018 V3.093 R ele ase c all r esourc es Idle W a it_For _ R econnected_ C all _Resul t Figure 67k: Process ICH_MSC (sheet 11) ETSI .018 version 3.11.087 U U S _M SC_ C hec k_ U U S 1_UU I R e lease S end Info F or M T R econ nected C a ll To V LR C C B S _Check _ Last_ C all S ee TS 23.078 CAM EL_ MT _GM S C_ DIS C 1 S ee T S 23.

078 CAM EL_ MT _GMSC_ DISC 1 R esult= R econnect? No Yes R elease Send Info F or M T R econnected C all To VLR R elease c all resourc es Idle W ait_For_ R econnected_ C all _Resul t W ait_For_Forw ard_A CM .018 version 3.0 Release 1999 163 ETSI TS 123 018 V3. si gnals to/from the ri ght are to/from the pr oc ess M T_C F_M SC unless m arked othe rw ise R elease R elease Release C AMEL_ M T_GM SC _ D ISC2 See TS 23. W ait_For_Forw ard_A nswer.11.078 See TS 23. W ait_For_Forward_Clear * * - - - Figure 67l: Process ICH_MSC (sheet 12) ETSI .3GPP TS 23.11.0 (2002-03) Proc ess IC H_MSC Proc es s in the MS C to handle an incomi ng (M T) call W ait_Fo r_ F orw ard_C lear ICH_M S C12(13) Signal s to/from the l eft are to/from the GMSC .

018 version 3.3GPP TS 23.0 (2002-03) Pro c ess IC H _ M SC Proc es s in the MS C to ha ndle an incom i ng ( M T) call W ait_For _For war d_A CM .11. si gnals to /fr om the ri ght are to/from the B S S un less m ar ked othe rw ise Int_R el ease _ C al l F r om gsm S SF R ele ase tr ansaction R elease R elease c al l r eso urc es Idle Figure 67m: Process ICH_MSC (sheet 13) ETSI .0 Release 1999 164 ETSI TS 123 018 V3. W ait_Fo r_For w ar d_Cle ar I C H_ M S C 1 3 (1 3 ) Si gna ls to/fr o m the l eft ar e to /fr om the GM S C .11. si gnals to/fr om the ri ght ar e to /fr om the pr oc e ss M T_C F_M SC unless m ar ked othe rw ise Int_R el ease _ C al l F r om gsm S SF R ele ase R elease R elease c al l r eso urc es Idle W ait_F or_ C lear S ignal s to /fr om the l eft are to/fr om the G M S C .

11.0 (2002-03) Procedure P age_M S _MS C Procedure in t he MSC to page a n M S in a specified l ocation area Signal s to/from the l eft are to/fro m the BSS.3GPP TS 23. signals to/from the ri ght are to/from the VLR unless m arked othe rw ise Loc ati on area ID known? Yes C al l still exis ts ? Yes MS connection exis ts ? No No P AGE _M1(2) No Set negative resp ons e: Unk now n LAI Yes Set negativ e res pons e: System Fai lure Cl ear re ceived:= False Ye s S MS or SS page? No Pagi ng vi a SGSN possi ble? No MS busy? Yes No Yes C heck _MT_ M ulticall_ MSC See TS 23.135 In specified l oc ation area Yes Pa ge R esult = Offered? No Page MS vi a SGS N R esult = M ore c alls poss ibl e? Yes No No R esult= not provi si one d? Yes C all in setup? No No C all w aiting? Yes Yes Set negati ve response: Busy S ubs criber Set acces s c onnection s tatus Sta rt Page response tim er W ait_For_ Pa ge_ Res ponse M ore c alls possi ble Set negativ e res pons e: Busy Subsc riber (N D UB ) Page MS negativ e response R esult:= Pas s R es ult:= Fail Figure 68a: Procedure Page_MS_MSC (sheet 1) ETSI .018 version 3.0 Release 1999 165 ETSI TS 123 018 V3.11.

0 (2002-03) Procedure P age_M S _MS C Procedure in t he MSC to page a n M S in a specified l ocation area W ait_For_ Page_ R esponse P AGE _M2(2) Signals to /from the l eft are to/from the BSS. si gnals to/from the rig ht are to/from the VLR unless marked otherwise Page re spons e timer expi red CM Service Re quest For circuitswitched call MS connecti on established R elease F rom GMSC Clear rec ei ved False True A bor t True C lear receiv ed False CM Serv ice Re quest To pro cess OC H_M SC Cl ear rec eived Fa lse True Set neg ati ve response: Absent Subsc ribe r Set n egativ e res pon se: Busy Subsc riber (N D UB ) Set a ccess connecti on status Releas e transac ti on Page MS negative re spons e Page MS negative res ponse R esult:= Pass R es ult:= Aborted C l ear rec ei ved:= T rue R esult:= A borted R esult:= F ai l R esult:= Fail R es ult:= Aborted W ait_ For_ Page_ R esponse Figure 68b: Procedure Page_MS_MSC (sheet 2) ETSI .3GPP TS 23.0 Release 1999 166 ETSI TS 123 018 V3.018 version 3.11.11.

0 Release 1999 167 ETSI TS 123 018 V3.11. si gnals to/from the rig ht are to/from the VLR unless marked otherwise Yes Set negative resp ons e: System Fail ure Yes S MS or SS page? No Cl ear re ceived:= False Paging via SGSN possi bl e? No M S busy? Yes Search for MS vi a SGS N No Yes C heck _MT_ M ulticall_ MSC See TS 23.135 Yes R esult = Offered? No R esult = M ore c alls poss ibl e? Yes No No R esult= not provi si one d? Yes C all in setup? No No C all w aiting? Yes Yes Set negati ve response: Busy S ubs criber Set acces s c onnection s tatus M ore c alls possi ble Set negativ e res pons e: Busy Subsc riber (N D UB ) Search For M S negativ e response R es ult:= Fail In al l location areas Page Sta rt Page response tim er W ait_For_ Se arch_ Res ponse R esul t:= Pas s Figure 69a: Procedure Search_For_MS_MSC (sheet 1) ETSI .0 (2002-03) Procedure S earch_F or_M S _M S C Procedure in t he MSC to search for an MS (page in all locati on areas) C al l still exis ts ? Yes MS connection exis ts ? No No S RCH _M 1(2) Signals to /from t he left are to/from the BSS.3GPP TS 23.11.018 version 3.

3GPP TS 23. si gnals to/from the rig ht are to/from the VLR unless marked otherwise Page re spons e timer expi red CM Service Re quest For circuitswitched call MS connecti on established R elease F rom GMSC Clear rec ei ved False True A bor t True C lear receiv ed False CM Serv ice Re quest To pro cess OC H_M SC Searc h For MS ack Releas e transac ti on Cl ear rec eived Fa lse True Set neg ati ve response: Absent Subsc ribe r Set n egativ e res pon se: Busy Subsc riber (N D UB ) Set a ccess connecti on status Searc h F or M S negative re spons e Searc h For M S negative res ponse R esult:= Pass R es ult:= Aborted C l ear rec ei ved:= T rue R esult:= A borted R esult:= F ai l R esult:= Fail R es ult:= Aborted W ait_ For_ Search_ R esponse Figure 69b: Procedure Search_For_MS_MSC (sheet 2) ETSI .11.0 (2002-03) Procedure S earch_F or_M S _M S C Procedure in t he MSC to search for an MS (page in all locati on areas) W ait_For_ Search_ R esponse S RCH _M 2(2) Signals to /from the l eft are to/from the BSS.018 version 3.0 Release 1999 168 ETSI TS 123 018 V3.11.

11.0 (2002-03) Procedure C om plete_C all_In _M S C Procedure in t he MSC to c omplete an MT ca ll on request from the VLR CC I_M S C1(11) Signal s t o/from the left are to/from the BSS.018 version 3.0 Release 1999 169 ETSI TS 123 018 V3.3GPP TS 23.087 C C BS_R eport_ N ot_Idl e See TS 23.093 W ait_F or_ S etup_ R esponse S etup fai lure Int_R elease_ C all From gsmSSF Set negat ive r esponse: A bs ent S ubs cri ber C om plete C al l negative response R esul t:= F ail Figure 70a: Procedure Complete_Call_In_MSC (sheet 1) ETSI . signals to/from the right are to/from the VLR unless marked otherwi se Set_C LIP_ Inf o_MSC D eri ve_ C S_BC _MS C S etup U U S_IC H _U US1_ Im plicit_ A ctive See TS 23.11.

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

135 Yes Yes Start No Reply Call Timer Result= Pass ? No CAMEL_ Start_TNRy See TS 23.11. s ignals t o/from the right are to/f rom the VLR unless marked otherwis e Alerting Connect UUS_I CH_ Check_Support See TS 23. 078 CAMEL_ MT_G MSC_ DI SC6 Result:= Reconnect Result:= Aborted Result:= Abort ed Figure 70c: Procedure Complete_Call_In_MSC (sheet 3) ETSI .11.0 (2002-03) Procedure Complete_Call_In_MSC Proc edure in the MSC t o complete an MT call on request from the VLR Wait _F or_ Alert ing CCI_MSC3(11) Signals to/f rom t he lef t are to/f rom the BSS.078 Yes Wait _f or_ Answer Result= Reconnect ? Release Abort Abort See TS 23.093 1 CCBS_ICH _MSC_ Report _Success See TS 23.093 No NRCT provi ded? Establish_ Terminat ing_TCH_ Multicall2 See TS 23.087 No Result= Pass ? Yes No Result= Pass ? Yes CCBS_ICH _MSC_ Report _Success See TS 23.3GPP TS 23.078 3 Yes Send_ACM_ If _Required 4 Result= Aborted? No CAMEL_ MT_GMSC_ DISC4 UTU 2Cnt: =0 See TS 23.0 Release 1999 171 ETSI TS 123 018 V3.018 version 3.087 UUS_I CH_ Check_Support See TS 23.

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

018 version 3. 078 Handling_C D_MSC See TS 23. s ignals to/from the right are to/f rom the VLR unless marked otherwis e Alert ing failure 1 CD_Request Release transaction CCBS_ICH _MSC_ Report _Success See TS 23. 093 Set cause CAMEL_ MT_G MSC_ DISC4 See TS 23.0 Release 1999 173 ETSI TS 123 018 V3.11. 093 Abort Complet e Call negativ e response Release To GMSC Result:= Reconnect Result:= Aborted Result:= Fail Figure 70e: Procedure Complete_Call_In_MSC (sheet 5) ETSI .0 (2002-03) Procedure Complete_Call_In_MSC Proc edure in the MSC t o complete an MT call on request from the VLR Wait _F or_ Alert ing CCI_MSC5(11) Signals to/f rom the lef t are to/f rom the BSS. 072 Yes Result= Reconnect? No CCBS_ICH _MSC_ Report _F ailure See TS 23.11.3GPP TS 23.

078 C AME L_ MT_GMSC _ D ISC 6 Resu lt:= Reco nnect R esul t:= A borted R esult:= Aborted Figure 70f: Procedure Complete_Call_In_MSC (sheet 6) ETSI .11.135 1 R esul t= P as s? No 5 R esul t= A borted? No See T S 23.078 C AM EL_ M T _GMSC _ D ISC4 Yes Yes R esul t= R econnect? R elease Abort A bor t See T S 23 .078 U U S_ICH _ C heck_ S upport No See TS 23.3GPP TS 23.0 (2002-03) Procedure C om plete_C all_In _M S C Procedure in t he MSC to c omplete an MT ca ll on request from the VLR W ait_for_ A ns wer CC I_M S C6(11) Signals to /from the l eft are to/from the BSS. si gnals to/from the rig ht are to/from the VLR unless marked otherwise C onnec t C AM EL_ S top_TN R y See TS 23.11.087 R esul t= P as s? Yes Est abl is h_ T erm i nating_ TC H_ M ulti call2 Yes See TS 23.018 version 3.0 Release 1999 174 ETSI TS 123 018 V3.

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

signals to/from the right are to/from the VLR unless ma rked otherwise CAM EL TNRy expired No Reply Call Time r expired UUS_ICH_ Check_ Forwarding See TS 23.3GPP TS 23.0 (2002-03) Procedure C om plete_C all_In _MSC Procedure in t he MSC to c omplete an MT ca ll on request from the VLR W ait_for_ A ns wer CC I_MSC8(11) Signals to/from the left are to/from the BSS.0 Release 1999 176 ETSI TS 123 018 V3.087 Result= P as s? Yes No Set negative response: No subsc riber reply Re lease transac tion Complete Call negative response 2 Release trans action Result:= Fail Figure 70h: Procedure Complete_Call_In_MSC (sheet 8) ETSI .11.11.018 version 3.

0 Release 1999 177 ETSI TS 123 018 V3. W ait_For_Ale rting CC I_M S C9(11) Signals to /from the l eft are to/from the BSS.087 U US _MSC _ Ch ec k_ U US 1_U U I See T S 23.11.093 Se t negative resp ons e: Bu sy subscriber (U D UB) U U S_MSC_ C heck_ U U S1_UU I See TS 23.078 Us er bus y? Yes No CC BS_IC H _M SC _ Report_F ailu re See T S 23.11.3GPP TS 23.087 Complete C all negativ e response R elease T o G MS C Rel eas e transac tion Abort R es ult:= Fail R esult:= Aborted Figure 70i: Procedure Complete_Call_In_MSC (sheet 9) ETSI .0 (2002-03) Procedure C om plete_C all_In _M S C Procedure in t he MSC to c omplete an MT ca ll on request from the VLR W ait_For_Setup_R esponse. si gnals to/from the rig ht are to/from the VLR unless marked otherwise Releas e transaction Rel eas e From GM SC CC BS_IC H_M SC _ Report _F ailur e See T S 2 3.018 version 3.093 CA ME L_ M T_GM SC _ DISC 6 See T S 23.

0 Release 1999 178 ETSI TS 123 018 V3.11.0 (2002-03) Procedure C om plete_C all_In _MSC Procedure in t he MSC to c omplete an MT ca ll on request from the VLR W ait_Fo r_ A ns wer CC I_MSC10(11) Signals to /from t he left are to/from the BSS.087 UUS _MSC_ Ch ec k_ UUS 1_UUI Re lease transac tion User bus y? Ye s See TS 23.087 UUS_MSC_ Check _ UUS1_UUI Set negative response: Bus y subscriber (UDUB) Complete Call negativ e response Resu lt:= Fail Abort 1 Result:= A borted Figure 70j: Procedure Complete_Call_In_MSC (sheet 10) ETSI . signals to/from the rig ht are to/from the VLR unless marked otherwise Release transaction From GMSC Re lease See TS 23 .11.018 version 3.078 CA ME L_ MT_GMSC_ DI SC6 UUS_MSC_ Check_ UUS1_UUI See TS 23.087 UUS_ICH_ Check_ Forwarding No No See TS 23 .087 Resu lt= Pas s? Ye s Release To G MS C See TS 23.3GPP TS 23.

072 Release To GMSC 2 Complet e Call negativ e response Result:= Aborted Result:= Fail Wait _F or_ Answer User t o User User t o User See TS 23.018 version 3. 072 CD_UUS_ Interaction Handling_ CD_MSC See TS 23. W ait_For_Answer Signals to/f rom t he lef t are to/f rom t he BSS.087 Abort No Result= Pass ? Release transaction Yes See TS 23.11.0 Release 1999 179 ETSI TS 123 018 V3.0 (2002-03) Procedure Complete_Call_In_MSC Proc edure in the MSC t o complete an MT call on request from the VLR Wait _F or_ Answer CCI_MSC11(11) W ait_For_Alert ing. s ignals t o/from the right are to/f rom t he VLR unless marked otherwise CD R equest Int _Releas e_ Call From gsmSSF UUS_I CH_ Check_ Forwarding See TS 23.11.3GPP TS 23. 087 UUS_M SC_ Check_UUS2_ UUI_t o_NW UUS_M SC_ Check_UUS2_ UUI_t o_MS See TS 23. 087 Wait _F or_ Answer Figure 70k: Procedure Complete_Call_In_MSC (sheet 11) ETSI .

087 U U S_ICH _U US 1_ Im pl ici t_ A ctive See TS 23.093 C C BS_R eport_ N ot_Id le W ait_F or_ S etup_ R esponse C al l C onfirmed See TS 23. si gnals to/from the ri ght are to/from the VLR unless ma rked otherw is e D eri ve_ C S_BC _MS C S etup Set negative response: Busy s ubs cri ber(N DU B) Process C all W aiti ng negative respons e R esul t:= F ail See TS 23.11.0 Release 1999 180 ETSI TS 123 018 V3.135 Es tablis h_ T erm inat ing_TC H_ Mult icall 1 No R esult= P as s? Yes R esul t= Aborted? No W ait_F or_ A lerti ng 4 Yes 5 Figure 71a: Procedure Process_Call_Waiting_MSC (sheet 1) ETSI .11.018 version 3.3GPP TS 23.0 (2002-03) Procedure P rocess_Call_W aiting_M S C Procedure in t he MSC to handle a Process C all W aiti ng request from the VLR C W T reatme nt i ndicator for existing call set to CW Allowed? Yes C all being s et up No Set_C LIP_ In fo_M SC Yes No PC W _M SC 1(8) Si gnals to/from the l eft are to/from the BSS.

078 Send_ACM _ If_Required To GM SC o f waiting call W a it_For_ Acceptance Figure 71b: Procedure Process_Call_Waiting_MSC (sheet 2) ETSI .11.093 Re sult= Pass? Yes H andli ng_ C D_ MSC Se e TS 23 . si gnals to /from the ri ght are to/from the VLR un less ma rked otherw ise W ait_For_ A lerti ng 2 4 Alerti ng C D Request Alertin g failure Set c ause U US _IC H _ Ch ec k_ Support No See T S 2 3.093 CA ME L_ M T_GM SC _ DI SC 4 Yes See T S 23.0 (2002-03) Proced ure P ro cess_Call_ W aiting _M S C Procedure in t he M SC to ha ndle a Process C all W a iti ng requ est from the VL R PC W _M SC 2( 8) Signal s to /from the l eft are to/from the BSS.093 UT U2 Cnt:=0 Re lea se To GM SC of wai ting call N RC T provi ded? Yes Start No R e ply C all T im er No Abort Start Acceptan ce tim er R esu lt:= Aborted CA ME L_ Start_TN R y See T S 2 3.3GPP TS 23.11.093 CC BS_IC H _M SC _ Repo rt_F ail ure See T S 23.087 C C BS_ ICH _M SC_ R eport_ Succes s Se e TS 23 .018 version 3.0 Release 1999 181 ETSI TS 123 018 V3.072 Re su lt= R eco nnect? No Releas e transac ti on For w aiting c al l Process C all W aiting negative response R esult:= F ai l R es ult:= Rec onn ec t 2 CC BS_IC H _M SC _ Re port_S ucce ss See T S 2 3.

087 UU S_IC H_ Check_ Support C lear pending c al l U U S_ICH _ C hec k_ Support See TS 2 3.0 (2002-03) Proced ure P ro cess_Call_ W aiting _M S C Procedure in t he M SC to ha ndle a Process C all W a iti ng requ est from the VL R W ait_Fo r_ S etu p_ R esponse PC W _M SC 3( 8) Signals to /from t he left are to/from the BSS.11. si gnals to/from th e rig ht are to/from the VL R unless ma rked otherwise R e lease trans action (U D U B) Int_R eleas e_ C all R elease transacti on (rej ect) Se tup fail ure From gsm SSF See TS 23.3GPP TS 23.11.093 R es ult:= Rec onn ec t Resu lt:= Aborted R esult: = F ai l Figure 71c: Procedure Process_Call_Waiting_MSC(sheet 3) ETSI .0 Release 1999 182 ETSI TS 123 018 V3.093 Set neg ati ve response: Busy subs cri ber(U D U B) Process C all W aiting negative respons e C C BS_IC H _M SC_ R epo rt_ Failure R elease T o GM SC of w aiti ng c al l Abort See T S 23.018 version 3.087 CAM EL_ MT _GM SC_ DISC 4 Yes See T S 23 .078 Resu lt= Reco nne c t? No CC BS_ICH _M SC _ Report_F ailure See T S 23 .

018 version 3.0 Release 1999 183 ETSI TS 123 018 V3.093 U U S_M SC_ C heck_ U U S1_UU I See TS 23. W ait_For_Ale rting PC W _M SC 4( 8) Signals to /from t he left are to/from the BSS.11.11.087 R elease transacti on F or wa iting cal l C AM EL_ M T _GM SC_ D ISC6 See TS 23.3GPP TS 23. si gnals to/from th e rig ht are to/from the VL R unless ma rked otherwise R elease F rom GM SC o f w aiti ng c al l C C BS_ICH _M SC_ R eport_Fai lure See TS 23.078 A bort R eleas e c all r esourc es F or wa iting cal l R esul t:= A borted Figure 71d: Procedure Process_Call_Waiting_MSC(sheet 4) ETSI .0 (2002-03) Proced ure P ro cess_Call_ W aiting _M S C Procedure in t he M SC to ha ndle a Process C all W a iti ng requ est from the VL R W ait_For_Setup_R esponse.

0 Release 1999 184 ETSI TS 123 018 V3.078 Rel eas e transac ti on U U S_ICH _ C heck_ S upport See TS 23.087 To G MSC of w aiting cal l Rel eas e R esul t= P as s? Yes No R es ult:= Aborted M ulticall s upported i n M SC ? No Es tabl is h_ Te rminating_ T CH _If_ R equired Yes Establi sh_ T erminating_T CH _ M ulticall2 T o G MSC of w aiting cal l Releas e See TS 23.0 (2002-03) Procedure P rocess_Call_W aiting_M S C Procedure in t he MSC to handle a Process C all W aiti ng request from the VLR W ait_for _ Ac ceptanc e PC W _M SC 5(8) Signal s t o/from the left are to/from the BSS.11.11.3GPP TS 23.018 version 3.135 3 2 Figure 71e: Procedure Process_Call_Waiting_MSC(sheet 5) ETSI . signals to/from the right are to/from the VLR unless marked otherwi se From gsm SSF Int_R eleas e_ C al l C onnec t Abort C AM EL_ S top_T NR y See TS 23.

0 (2002-03) Procedure Process_Call_Waiting_MSC 3 Procedure in the MSC to handle a Process Call Waiting request from the VLR Yes Result= Pass? No PCW_MSC6(8) Signals to the r ight are to the VLR 5 Yes Handle_AoC_ MT_MSC Result= Aborted? No No Result= Pass? Yes CAMEL_ MT_GMSC_ DISC4 Connect ack See TS 23.078 CAMEL_ MT_GMSC_ DISC6 Result= Reconnect? No Release To GMSC of waiting call Abort Abort For waiting call Release call resources Result:= Reconnect Result:= Aborted Result:= Aborted No Result= Pass? Yes Set_COL_ Presentation_ Indicator_MSC To GMSC of waiting call Send_ Answer_If_ Required To GMSC of waiting call Release Process Call Waiting ack Abort Result:= Pass Result:= Aborted Figure 71f: Procedure Process_Call_Waiting_MSC(sheet 6) ETSI .11.0 Release 1999 185 ETSI TS 123 018 V3.11.3GPP TS 23.078 See TS 23.018 version 3.078 CAMEL_ MT_GMSC_ ANSW ER Yes Result= Reconnect? No Yes See TS 23.

11.018 version 3. signals to/from the right are to/from the VLR unless marked otherwise W ait_for_ Ac ceptanc e Re lease transac tion (bus y) Release transaction (reject) 1 Ac ceptanc e timer expired CAMEL TNRy expired No Reply Call Timer expired See TS 23.0 (2002-03) Procedure Process_Call_W aiting_MSC Procedure in t he MSC to handle a Process Call W aiting request from the VLR PC W _MSC 7(8) Signals t o/from the left are to/from the BSS.087 UUS_ICH_ Check _ Forwarding No Res ult= Pass? Yes Release tra ns action For wait ing call Set negative resp ons e: No s ubs criber reply Proces s Call W aiting negativ e response Releas e transac tion CAMEL_ MT_GMSC_ DISC4 Yes See TS 23.078 UUS _ICH_ Chec k_ Forwarding No See TS 23.11.3GPP TS 23.0 Release 1999 186 ETSI TS 123 018 V3.087 Result:= Reconnect Res ult:= Fail Set n egativ e res pon se: Busy subsc riber(UDUB ) Process Ca ll W aiting negative res ponse Result:= Fail UUS_MSC_ Check _ UUS1_UUI Release To GMSC of waiting c all 2 A bort Result:= A borted Figure 71g: Procedure Process_Call_Waiting_MSC(sheet 7) ETSI .078 CAMEL_ MT_GMSC_ DISC5 See TS 23.087 Result= Recon nec t? No For waiting call Result= Pass? Yes UUS_ICH_ Check_ Forwarding See TS 23.

087 UU S_IC H_ Check_ Forw ardi ng No See T S 23 .0 (2002-03) Procedure P rocess_Call_W aiting_M S C Procedure in t he MSC to handle a Process C all W aiti ng request from the VLR PC W _M SC 8(8) Signal s t o/from the left are to/from the BSS.093 CC BS_IC H _MSC _ Report_F ailure R elease call res ources See TS 23.018 version 3. signals to/from the right are to/from the VLR unless marked otherwi se W ait_For_ Acceptance Re lease From GMSC of waiting cal l C D R equest U ser T o U ser From G MSC of activ e c al l Us er To Us er U US _MSC _ C hec k_ U US 1_U U I See T S 23.3GPP TS 23.078 From G MSC of waiti ng call Rel eas e Abort Process Call W ai ti ng negativ e response For w aiti ng c all See TS 23.078 CA MEL_ MT _GM SC_ DISC 6 Abort F or wa iting cal l Rel ease call res ources R es ult:= Aborted Figure 71h: Procedure Process_Call_Waiting_MSC(sheet 8) ETSI .0 Release 1999 187 ETSI TS 123 018 V3.11.072 Handling_ CD _MS C C D _U US_ Inter action W ai t_For_Se tup_R esponse.72 W ait_For_Alerti ng C AME L_ M T_GM SC _ D ISC 6 See T S 23.087 U U S_M SC_ C hec k_U US 2_ U U I_to_N W See TS 23.087 U US _M SC _ Check _UU S2_ UU I_to_M S Re lease transac tion For w aiti ng c all Resu lt= Pas s? Ye s W ait_For_ Acceptance See TS 23. Se e GSM 03.087 U US_MSC _ Check _ U US1_U UI R esult:= Aborted Resu lt:= Fail F or wa iting cal l Rel eas e transac tion 1 See TS 23.11.

018 version 3.11.0 Release 1999 188 ETSI TS 123 018 V3.0 (2002-03) Procedure S et_CLIP_Info_MS C Procedure in t he MSC to determi ne the C LIP inform ati on to be s ent to the MS Signal s to/from the right are to/fro m the proces s C LIP _M AF 002 CA INF_M 1( 1) Initi ate handli ng of C LIP W ait_F or_ C LIP_Info Re lease transac ti on From BSS C ontinue c all handli ng Re lease From GM SC Figure 72: Procedure Set_CLIP_Info_MSC ETSI .3GPP TS 23.11.

0 (2002-03) Procedure D erive_CS _BC _M S C Proc edure in the MSC to deriv e th e reque ste d G SM BC for an inc om ing (M T) c all according to the ru les of GSM 0 9.018 version 3.3GPP TS 23.11.0 Release 1999 189 ETSI TS 123 018 V3.07 No C S BC derived from ISD N co mpatibi lity info rmation? Yes Yes DR BC _M 1(1) C S BC recei ved in PR N ? No Omit C S B C from Setup U se C S BC r ecei ved i n PR N U se C S BC derived from ISD N compati bili ty inf ormation Figure 73: Derive_CS_BC_MSC ETSI .11.

3GPP TS 23.11.0 Release 1999 190 ETSI TS 123 018 V3.018 version 3. sig nals to/from the right are to/from the GM SC TC H al located Fals e True Al locate c hannel R esult:= Pass W ait_Fo r_ Allocatio n_ C om plete Releas e transac tion A lloc ation fa ilure Al locati on com plete Re lease R elease transacti on T C H al located:= True Rel eas e transac tion R esu lt:= F ail R esult := Pass R esult:= Aborted Figure 74: Procedure Establish_Terminating_TCH_If_Required ETSI .0 (2002-03) Procedure E stablish_T erm inating_T C H_If_Required Procedure in t he term inati ng VM SC to es tablish a Traffic C hannel if one ha s n ot been established for this c all E T TC IR 1(1) Signals to /from t he left are to/from the BSS.11.

018 version 3.3GPP TS 23.0 (2002-03) Procedure H andle_A oC _MT _MS C Procedure in t he MSC to handle AoC signalling towards the M S for an M T c al l A OCMT _M 1(1) Signal s t o/from the left are to/from the BSS. signal s from the right are from the AoC ti mer function.0 Release 1999 191 ETSI TS 123 018 V3. Yes A oC(I) provi sioned? No Set charging param eters No AoC (C ) provi sioned? Yes Send Charging Param eters S et c harging pa ramete rs Send C harging Parameters S tart AoC ac knowl edg ment ti mer W ait_F or_ C harging_ Parame ters_ Ac k C harging Param eters ack R elease c onne ction AoC ack no wledgm ent tim er expired R elease trans action R es ult:= Pass R esul t:= F ail Figure 75: Procedure Handle_AoC_MT_MSC ETSI .11.11.

3GPP TS 23.018 version 3.11.0 Release 1999

192

ETSI TS 123 018 V3.11.0 (2002-03)

Procedure S et_CO L_P resentation_Indicator_M S C
Procedure in t he MSC to determi ne the C OL presentation i ndi cator v alue Signal s to/from the right are to/fro m the proces s C OLR _M AF 041

CO IN D_M 1(1)

Initi ate handli ng of C OLR

W ait_F or_ C OLR _Info

Release transac tion

From BSS

C ontinue c all handli ng

Re lease

From GM SC

Figure 76: Procedure Set_COL_Presentation_Indicator MSC

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

193

ETSI TS 123 018 V3.11.0 (2002-03)

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 1: the procedure CAMEL_ICH_VLR is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VLR does not support CAMEL phase 3 or later, processing continues from the possible call of the procedure CCBS_ICH_Set_CCBS_Call_Indicator. Sheet 1: the procedure CCBS_ICH_Set_CCBS_Call_Indicator is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. Sheet 1, sheet 2, sheet 5: the procedure CCBS_ICH_VLR_Report_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. Sheet 1, sheet 3: the procedure CCBS_ICH_Report_Not_Reachable is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. Sheet 2: this process communicates with the matching instance of the process PRN_VLR, which is linked by the MSRN. Sheet 2: the test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented; and there is an association established for the MS between the MSC/VLR and the SGSN.

Sheet 3: the test "NDUB?" takes the "Yes" exit if the Page MS negative response or the Search for MS negative response had the value Busy Subscriber (NDUB). Sheet 3: the procedure Get_CW_Subscription_Info_VLR is specific to Call Waiting. If the VLR does not support Call Waiting, processing continues from the "No" exit of the test "CW available?". Sheet 3: the procedure Get_CW_Subscription_Info_Multicall_VLR is specific to Multicall; it is specified in 3GPP TS 23.135 [34]. If the VLR does not support both Multicall and Call Waiting, processing continues from the "No" exit of the test "CW available?". Sheet 3: the VLR uses the basic service returned in the Page MS negative response or the Search for MS negative response Busy Subscriber (More calls possible) to determine whether call waiting is available. Sheet 3: the procedure Get_LI_Subscription_Info_MT_VLR is specific to CLIP and COLR. If the VLR supports neither CLIP nor COLR, the procedure call is omitted. Sheet3: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC; it is specified in subclause 7.1.2.15. Sheet 3 sheet 6: the procedure CLI_ICH_VLR_Add_CLI is specific to Enhanced CLI Handling. It is specified in 3GPP TS 23.081 [14]. Sheet 3: the procedure CCBS_ICH_Handle_NDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. If the VLR does not support CCBS, processing continues from the "Forward" exit of the test "Result". Sheet 3: the procedure Process_Access_Request_VLR is specified in subclause 7.1.2.2. Sheet 3: the output signal Page MS towards the SGSN includes the Location area identity parameter. Sheet 3: if the VLR does not support CUG, handling continues from the "No" exit of the test "CUG info present?". Sheet 4, sheet 6: the procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?". Sheet 5, sheet 6: the procedure CD_Authorization is specific to Call Deflection, it is specified in 3GPP TS 23.072 [11]. If the VLR does not support Call Deflection, processing continues from the "Yes" exit of the test "Result=Aborted?".

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

194

ETSI TS 123 018 V3.11.0 (2002-03)

Sheet 5, sheet 6: the procedure CCBS_ICH_Handle_UDUB is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. Sheet 6: the test "NDUB?" is executed only if the VLR supports CCBS. If the VLR does not support CCBS, processing continues from connector 5. Sheet 7: the procedure CCBS_ICH_Set_CCBS_Target is specific to CCBS; it is specified in 3GPP TS 23.093 [22]. Sheet 7: the procedure Handle_CFNRc is specified in subclause 7.2.2.11. Sheet 8: the procedure Forward_CUG_Check is specific to CUG; it is specified in subclause 7.2.2.6. If the VLR does not support CUG, processing continues from the "Yes" exit of the test "Result=Call allowed?". Sheet 8: the procedures CAMEL_O_CSI_Check_VLR, and CAMEL_D_CSI_Check_VLR are specific to CAMEL phase 3 or later; they are specified in 3GPP TS 23.078 [12].

7.3.2.2

Procedure Derive_Requested_Basic_Service_VLR

If the VLR did not receive a basic service for the call in the Send Info For Incoming Call, and did not receive a GSM bearer capability in the Provide Roaming Number, it applies a default basic service according to the requirements of the operator.

7.3.2.3

Procedure Search_For_MS_VLR

The test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented; and the VLR configuration requires paging via the SGSN during VLR restoration.

The output signal Page MS towards the SGSN omits the Location area identity parameter. It is sent to every SGSN to which the VLR is connected.

7.3.2.4

Procedure Get_CW_Subscription_Info_VLR

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

7.3.2.5

Procedure Get_LI_Subscription_Info_MT_VLR

The VMSC may abort the transaction with the VLR while a response is awaited from the process CLIP_MAF001 or the process COLR_MAF040. The message is saved for processing after return from the procedure.

7.3.2.6

Procedure Handle_CFB

The test "Normal call busy" refers to the value of the indicator returned by the process MAF008. The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL Phase 3 or later, processing continues from the "Yes" exit of the test "Result = Pass?".

7.3.2.7

Procedure Handle_CFNRy

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

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

195

ETSI TS 123 018 V3.11.0 (2002-03)

Process ICH_VLR
Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call

ICH_VLR1(8)
Signals to/f rom the lef t are to/f rom t he MSC

Idle

Send Info For I ncoming Call

No MSR N known? Yes

CAMEL_ ICH_VLR

See TS 23. 078

Yes

Result= Fail? No

CCBS_ICH _ Set _CCBS_ Call_Indicator

See TS 23. 093

Set negat ive respons e: Unallocat ed Roaming Number

Idle

Data confirmed by H LR True

False

Derive_Reques ted_ Basic _Service_VLR

Set negativ e response: System Failure

Yes IMSI detac hed? No No Roaming in LA allowed? Yes CCBS_ICH _ Report _Not_ Reachable Send Inf o For I ncoming Call negative respons e CCBS_ICH _VLR_ Report_F ailure See TS 23. 093

1

10

I dle

Figure 77a: Process ICH_VLR (sheet 1)

ETSI

093 Yes Send Info For I ncoming Call negati ve response Set Paging via SG SN possible Paging v ia SGSN possible? Idle Search_For_ MS_VLR Page MS Page type= c ircuit -switched call Yes Result= Pass ? No Yes Result= Fail? No See TS 23. 093 CCBS_ICH _VLR_ Report_F ailure Idle 2 Wait _F or_ Access_ Request Figure 77b: Process ICH_VLR (sheet 2) ETSI .11.11.0 Release 1999 196 ETSI TS 123 018 V3.3GPP TS 23. Signals to/f rom the right are to/f rom t he proces s PRN_VLR.018 version 3. Prepaging supported? Yes True PAR pending False Wait_F or_ PAR_Complet ed No PAR complet ed True PAR succ ess ful False Call arriv ed True 11 Fatal PAR error False Set negativ e response: Impossible call complet ion No Locat ion area ID known? Yes No CCBS_ICH _VLR_ Report_F ailure See TS 23.0 (2002-03) Process ICH_VLR 10 Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call ICH_VLR2(8) Signals to t he lef t are to t he VMSC.

11.3GPP TS 23.0 Release 1999 197 ETSI TS 123 018 V3.093 CCBS_ICH _ Handle_NDUB Get _AoC_ Subsc ript ion_ Inf o_VLR Release Result Forward 4 8 5 Figure 77c: Process ICH_VLR (sheet 3) ETSI . Wait _F or_ Access_ Request Page MS negativ e response 2 Page MS via SG SN Abort Absent subscriber ? Yes No Page MS To SG SN No Busy subscriber ? Yes 3 Yes NDUB? No See TS 23. 093 CCBS_ICH _ Report _Not _ Reachable Wait _F or_ Access_ Request See TS 23.018 version 3. 093 CCBS_I CH_VLR_ Report _Failure 1 Idle Multic all s upport ed in VLR? No Get _CW _ Subsc ript ion_ Inf o_VLR Yes Get_CW _ Subsc ript ion_Info_ Multicall_VLR No CW available? Yes 9 Get _LI _ Subsc ript ion_ Inf o_MT_VLR See TS 23.11.0 (2002-03) Process ICH_VLR Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call ICH_VLR3(8) Signals to/f rom the left are t o/f rom the VMSC.

11.3GPP TS 23.0 Release 1999 198 ETSI TS 123 018 V3.0 (2002-03) Process ICH_VLR Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call Wait _F or_ Access_ Request ICH_VLR4(8) Signals to/from t he lef t are to/from t he VMSC. 093 Complet e Call Send Inf o For I ncoming Call negati ve response Wait _F or_ Complet e_Call_ Result Idle Figure 77d: Process ICH_VLR (sheet 4) ETSI . 093 Yes Succ ess? Idle CAMEL_CHECK _SI I2_C DTI No Yes Result = Pass ? No CFN Ry A&O? Yes Prov ide NRCT value No 3 Get _LI _ Subsc ript ion_ Inf o_MT_VLR Get _AoC_ Subsc ript ion_ Inf o_VLR Set negativ e response: System f ai lure See TS 23.081 CLI_ICH_VLR_ Add_CLI CCBS_ICH _VLR_ Report _F ailure See TS 23.11.085 CCBS_IC H_VLR_ Report _F ailure See TS 23. Proc ess Access Request Proc ess _ Access_ Request _VLR No 11 Result= Pass ? Yes CUG info present? No Yes Translat e CUG interlock to index As defined in TS 23.018 version 3.

018 version 3. 093 Yes Absent subscriber ? No CCBS_I CH_ Handle_UDUB Yes Radio conges tion? No No subscriber reply ? No Yes See TS 23.11.0 (2002-03) Process ICH_VLR Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call Wait_f or_ Complet e_Call Result ICH_VLR5(8) Signals to/f rom the left are t o/f rom the VMSC. 093 CCBS_IC H_VLR_ Report _F ailure No Result= Aborted? Yes No Result= Fail? Yes Set negativ e response: Impossible call completion 6 1 5 Send Inf o For I ncoming Call negati ve response 7 Idle Figure 77e: Process ICH_VLR (sheet 5) ETSI .0 Release 1999 199 ETSI TS 123 018 V3. Complet e Call ack Abort Complet e Call negati ve response Yes Idle Busy subscriber ? No See TS 23.3GPP TS 23.11. 072 CD_ Aut horization See TS 23.

0 (2002-03) Process ICH_VLR 4 Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call ICH_VLR6(8) Signals to/f rom the left are t o/f rom the VMSC.3GPP TS 23. 093 Yes Send Info For I ncoming Call negati ve response 7 Idle 6 5 Figure 77f: Process ICH_VLR (sheet 6) ETSI . 072 CD_ Aut horization 9 No Result= Aborted? Yes No Result= Fail? Set negativ e response: Impossible call completion CCBS_ICH _ Handle_UDUB See TS 23. CAMEL_CHECK _SI I2_C DTI See TS 23. 078 Yez Result = Pass ? No No CFN Ry A&O ? Yea Set NRCT CLI_ICH_VLR_ Add_CLI See TS 23. 081 Proc ess Call Wait ing Wait_F or_ PCW_Result Proc ess Call Waiting ack Abort Proc ess Call W ait ing negativ e response Yes Idle Busy subscriber ? No No subscriber reply ? No Yes NDUB? Yes No See TS 23.11.11.018 version 3.0 Release 1999 200 ETSI TS 123 018 V3.

0 Release 1999 201 ETSI TS 123 018 V3.3GPP TS 23.0 (2002-03) Process ICH_VLR Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call Signals to t he left are to t he VMSC 1 ICH_VLR7(8) Handle_CFNRc 5 Yes Result= Fail? Handle_CFB Set negativ e response: Forwarding Violat ion No Yes Result= Fail? No Set negativ e response: Forwarding Violat ion No Result= Forward? Yes Set negativ e response: Absent Subsc riber 7 6 8 Handle_CFNRy No Result= Forward? Yes CCBS_ICH _ Set_CCBS_ Target Set negativ e response: Forwarding Violat ion Yes Result= Fail? No See TS 23.018 version 3.11. 093 No Result= Forward? Set negativ e response: No Subsc riber Reply Yes Set negativ e response: Busy Subsc riber CCBS_ICH _ Set _CCBS_ Target See TS 23. 093 Send Inf o For I ncoming Call negati ve response 7 Idle 7 Figure 77g: Process ICH_VLR (sheet 7) ETSI .11.

078 Send Info For I ncoming Call ack Send Inf o For I ncoming Call negati ve response Idle Idle Figure 77h: Process ICH_VLR (sheet 8) ETSI .3GPP TS 23.11.0 (2002-03) Process ICH_VLR Proc es s in VLRB to handle a request f or inf ormation f or an i ncoming (MT) call 7 Signals to t he left are to t he VMSC.11.018 version 3. ICH_VLR8(8) Forward_ CUG _Check Result= Call allowed? Yes No Set result: Forward Set negat ive response: CUG rejec t Set forwarding informat ion CAMEL_ O_C SI_ CHECK_VLR See TS 23.0 Release 1999 202 ETSI TS 123 018 V3. 078 CAMEL_ D_CSI _ CHECK_VLR See TS 23.

018 version 3.0 (2002-03) Procedure D erive_Reque sted_B asic_S ervice_VLR Proc edure in the V LR to deriv e the requeste d basi c serv ice for an incom ing (M T) call DR BS _V1(1) Yes Ba si c servic e inc luded in Send Info F or Incomin g C all? No Basic serv ice:= BS received in SIFIC Yes C S BC received in Provide R oaming N um ber No Bas ic s ervice:= BS deriv ed from CS BC B as ic se rvi ce:= default Figure 78: Procedure Derive_Requested_Basic_Service_VLR ETSI .0 Release 1999 203 ETSI TS 123 018 V3.3GPP TS 23.11.11.

3GPP TS 23.018 version 3.e.11.11.0 Release 1999 204 ETSI TS 123 018 V3. page in all l ocation areas ) Signal s to/from the l eft are to/fro m the MS C S RCH _V1(1) No Pagin g v ia SGSN possi ble? Yes S et paging v ia SGSN poss ible Search F or M S Pa ge type= C ircuit-sw itched call W ait_Fo r_ S earch_R es ult Search For MS ack S ear ch F or M S n egativ e response Abort Search f or MS via S GSN Up date Location Are a ID T o SGS N Page M S R esult:= Pass Resu lt:= Fail R esult: = Aborted W ait_For_ Search _Result Figure 79: Procedure Search_For_MS_VLR ETSI .0 (2002-03) Procedure S earch_F or_M S _V LR Procedure in t he VLR to search for an MS (i.

0 Release 1999 205 ETSI TS 123 018 V3.11.11.0 (2002-03) Proc edure G et_CW _Subscription_Info_VLR Procedure in t he VLR to retrieve subscription inform ati on for th e C al l W aiting servic e Signal s to/from the right are to/fro m the proces s M AF013 CW I_VLR1(1) initiate handling of C W W ait_For_ C W _Info From MS C Abort process c al l w aiti ng Figure 80: Procedure Get_CW_Subscription_Info_VLR ETSI .3GPP TS 23.018 version 3.

3GPP TS 23.018 version 3.11.0 Release 1999

206

ETSI TS 123 018 V3.11.0 (2002-03)

Procedure Get_LI_Subscription_Info_M T_V LR
Procedure in t he VLR to retrieve subscription inform ation for the C LIP & C OLR li ne i dentificati on serv ices for an MT call Initi ate handl ing of C LIP

GLI_MT V 1(1)

T o process CLIP_MAF001

W ait_F or_ C LIP_Info

From MS C

Abort

C ontinue c all handli ng

F rom proc es s C LIP _M AF 001

Initi ate handl ing of C OLR

T o process CO LR _MAF040

W ait_F or_ C OLR _Info

From MS C

Abort

C ontinue c all handli ng

F rom process CO LR _M AF040

Figure 81: Procedure Get_LI_Subscription_Info_MT_VLR

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

207

ETSI TS 123 018 V3.11.0 (2002-03)

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

H_CFB1(1)

Signals to/f rom t he right are to/f rom t he process MAF008 CAMEL_CHECL _SI I2_C DTI See TS 23. 078

No Result = Pass ? Yes

initiate handling of CFB

Wait_F or_ CFB_Res ult

continue call handling

Yes Error? No

Normal call busy? No

Yes

Result:= Fail

Result:= Forward

Result:= Busy

Figure 82: Procedure Handle_CFB

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

208

ETSI TS 123 018 V3.11.0 (2002-03)

Pro cedure H andle_C FN Ry
Procedure in t he VLR to handle C all F orw ardi ng on N o subscriber Repl y Signal s to/from the right are to/fro m the proces s M AF009

H_C FN Ry1( 1)

i nitiate handli ng of C FN R y

W ait_F or_ C FN R y_R es ult

c onti nue c all handli ng

Yes E rror? No

N orm al c all? Yes

No

R es ult:= Fail

R esul t:= N o re ply

R esult:= Forward

Figure 83: Procedure Handle_CFNRy

ETSI

3GPP TS 23.018 version 3.11.0 Release 1999

209

ETSI TS 123 018 V3.11.0 (2002-03)

8

Contents of messages
On the D interface (VLR-HLR): Abort; Activate Trace Mode; Authentication Failure Report; Insert Subscriber Data; Send Authentication Info; Send Authentication Info ack; Send Authentication Info negative response;

This clause specifies the content of each message shown in clauses 5 and 7, except for the following messages, which are not specific to call handling:

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

Required M

Description Indicates the reason for the procedure being aborted.

8.1.2

Authenticate
The following information elements are required for authentication of a UMTS MS:

Information element name RAND(I)

Required M

AUTN(I)

M

Description Random number challenge to be sent to the MS (3GPP TS 33.102 [31]) Authentication token to be sent to the MS (3GPP TS 33.102 [31])

The following information elements are required for authentication of a GSM MS:
Information element name RAND CKSN Required M M Description Random number challenge to be sent to the MS (GSM 03.20 [1]) Cipher key sequence number to be sent to the MS (GSM 03.20 [1])

ETSI

Shall be present for an emergency call when the mobile is identified only by its IMEI.7 Check IMEI ack The following information element is required: Information element name Equipment status Required M Description Indicates whether the ME is black-listed. otherwise shall be absent.20 [1]) 8. Category of the MS for which the Complete Call is sent.102 [31]) The following information element is required for authentication of a GSM MS: Information element name SRES Required M Description Signature result returned by the MS (GSM 03. 8.1. for an MT call and for an emergency call when the MS is registered in the VLR.1. Unknown equipment. Shall be Information element name MSISDN IMEI C Category C ETSI .4 - Authenticate negative response wrong network signature.3GPP TS 23. The negative response information element can take the following value: 8.1.018 version 3.11.9 Complete Call The following information elements are required: Required C Description MSISDN of the MS for which the Complete Call is sent.1. IMEI of the mobile for which the Complete Call is sent.1. Shall be present for an ordinary MO call.5 Call arrived This message contains no information elements.0 Release 1999 210 ETSI TS 123 018 V3. 8. otherwise shall be absent.3 Authenticate ack The following information element is required for authentication of a UMTS MS: Information element name RES(I) Required M Description Result returned by the MS (3GPP TS 33.1.6 Check IMEI This message contains no information elements.1.8 - Check IMEI negative response The negative response information element can take the following values: System failure.0 (2002-03) 8. grey-listed or white-listed 8.11. 8.

11. Indicates that the CLIR override subscription option of CLIP is provisioned. Shall be present for an MO call if COLP is provisioned. Indicates that COLP is provisioned.0 (2002-03) 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 present for an ordinary MO call and for an emergency call when the MS is registered in the VLR. temporary (default presentation allowed) or temporary (default presentation restricted). Indicates that COLR is provisioned. 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. Indicates that the COLR override subscription option of COLP is provisioned. (continued) ETSI . otherwise shall be absent. otherwise shall be absent.018 version 3. otherwise shall be absent. Shall be present for an MT call if it was received in the Provide Roaming Number. Indicates that CLIR is provisioned. otherwise shall be absent. otherwise shall be absent. Shall be present for an MO call if CLIR is provisioned. Shall be present for an MT call if CLIP is provisioned. Indicates that CLIP is provisioned. Shall be present for an MO call if CLIR is provisioned. Indicates the mode in which CLIR is provisioned: permanent. Shall be present for an MT call if the Call Forwarding on No Reply service is active and operative. Shall be present for an MT call if it was received in the Provide Roaming Number. otherwise shall be absent. otherwise shall be absent.3GPP TS 23. otherwise shall be absent.11. otherwise shall be absent. 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. Value of timer to be used to determine the No subscriber reply condition. 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.0 Release 1999 211 ETSI TS 123 018 V3. Shall be present for an MT call if COLR is provisioned.

11.0 (2002-03) The following information elements are required (concluded): Information element name CUG index Required C Description For the definition of this IE. This parameter may be included at the discretion of the VLR operator. 8. The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier.14 - Forward New TMSI negative response The negative response information element can take the following value: TMSI reallocation failure. No subscriber reply.1.1.085 [18].085 [18]. 8.3GPP TS 23. CUG interlock C CUG outgoing access C Advice of Charge provision C Alerting Pattern C Shall be present for an MT call if it was received in the Provide Roaming Number and if the feature is supported by the MSC/VLR. otherwise shall be absent. Shall be present for an ordinary MO call or an MT call if Advice of Charge is provisioned. Busy subscriber. see 3GPP TS 23.018 version 3. see 3GPP TS 23.11. otherwise shall be absent.1. otherwise shall be absent. otherwise shall be absent.13 Forward New TMSI ack This message contains no information elements.1. For the definition of this IE.0 Release 1999 212 ETSI TS 123 018 V3. For the definition of this IE.085 [18]. ETSI . Radio congestion. Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. Shall be present for an ordinary MO call if the call is a CUG call. Shall be present for an ordinary MO call if the call is a CUG call with outgoing access. see 3GPP TS 23. NAEA preferred Carrier Id O 8.10 Complete Call ack This message contains no information elements. otherwise shall be absent.1.12 Forward New TMSI The following information element is required: Information element name TMSI Required M Description TMSI to be sent to the MS. May be present (as a network operator option) for an ordinary MO call if the call is a CUG call.11 - Complete Call negative response The negative response information element can take the following values: Absent subscriber. 8. 8. shall be present for an MT call if the call is a CUG call.

19 - Page MS negative response The negative response information element can take the following values: Absent subscriber. Location area in which the MS is to be paged.3GPP TS 23.1.18 Page MS ack The following information elements are required : Information element name Location area ID Serving cell ID Required M M Service area ID C Description Location area in which the MS responded to the page. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent.1.0 (2002-03) 8. Shall be present if the VLR determines that the MS can be paged via the SGSN.e. Shall be present if state information is required. 8. Subscriber state requested C Indicates that the VLR requires state information for the MS. Shall be present if the MS uses GSM radio access. Indicates whether the paging is for a circuit-switched call. Shall be present if the MS uses UMTS radio access. 8. 8. MT SMS delivery. Indicates that paging via the SGSN is possible.1. otherwise shall be absent. ETSI .16 Obtain Subscriber Info ack The following information elements are required: Information element name Required Description Subscriber state C Indicates whether the MS is busy (i.15 Obtain Subscriber Info The following information elements are required: Information element name IMSI Required M Description IMSI of the MS for which information is required. Busy subscriber (More calls possible). TMSI to be broadcast to identify the MS. Identity of the cell in which the served subscriber is located.11. SS activity or Active Location Retrieval. Service area identity of the cell in which the served subscriber is located.11. engaged on a circuitswitched call) or assumed idle. 8.1.17 Page MS The following information elements are required: Information element name IMSI Location area ID Page type Required M M M Paging via SGSN possible C TMSI O Description IMSI of the MS to be paged. otherwise shall be absent. Shall be present if the VLR requested state information.018 version 3.1.0 Release 1999 213 ETSI TS 123 018 V3.

0 Release 1999 214 ETSI TS 123 018 V3. The Page MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call.0 (2002-03) - Busy subscriber (NDUB). System failure.11.11. ETSI .018 version 3. Unknown location area ID.3GPP TS 23.

Circuit-switched paging priority.22 Process Access Request ack The following information elements are required: Information element name IMSI Required C IMEI C MSISDN O Description IMSI of the MS requesting the access. Identity of the service area (for UMTS access) in use by the served subscriber. one of IMSI. IMEI of the MS requesting the access. 8. one of IMSI. one of IMSI or IMEI shall be present. one of IMSI or TMSI shall be present. For normal MO call or page response. IMSI of the MS requesting the access. shall be absent. emergency call or page response. Shall be present for UMTS access.0 (2002-03) 8.018 version 3.0 Release 1999 215 ETSI TS 123 018 V3. TMSI or IMEI shall be present. one of IMSI or TMSI shall be present. Shall be present if TMSI is present. one of IMSI or TMSI shall be present.20 Page MS via SGSN The following information elements are required: Information element name IMSI eMLPP priority TMSI Channel type Required M O O O Description IMSI of the MS to be paged.11. Identity of the location area from which the access request was received. otherwise shall be absent. otherwise shall be absent. Cipher key sequence number of the MS requesting the access. For emergency call. TMSI or IMEI shall be present. For normal MO call or page response.3GPP TS 23. Type of channel required for the call. Identity of the cell (for GSM access) in use by the served subscriber. For normal MO call or page response. ETSI . Indicates whether or not the connection to the MS is ciphered and whether or not it is authenticated. For emergency call. otherwise shall be absent. one of IMSI. For emergency call.1. For emergency call. 8. IMEI of the MS requesting the access.1. one of IMSI or IMEI shall be present. TMSI or IMEI shall be present. Shall be present for GSM access.21 Process Access Request The following information elements are required: Information element name CM service type Required M Access connection status Current location area ID Service area ID M M C Serving cell ID C IMSI C TMSI C IMEI C CKSN C Description Indicates the type of access required: normal MO call. Other values (short message service and SS request) defined for this IE are not considered in the present document. For emergency call.11. shall be present.1. MSISDN of the MS requesting the access. TMSI to be broadcast to identify the MS. For normal MO call or page response. For normal MO call or page response. TMSI of the MS requesting the access.

8.11. 8. Shall be present if it was received in the Provide Roaming Number for the waiting call.26 - Process Call Waiting negative response The negative response information element can take the following values: Busy subscriber (UDUB). Shall be present if it was received in the Provide Roaming Number for the waiting call. ETSI .3GPP TS 23. Shall be present if CLIP is provisioned with the CLIR override subscription option and the MS is registered in the HPLMN country. see 3GPP TS 23. Shall be present if CLIP is provisioned.1. otherwise shall be absent. otherwise shall be absent. Shall be present if it was received in the Provide Roaming Number for the waiting call. For the definition of this IE.1.11.23 - Process Access Request negative response The negative response information element can take the following values: Roaming not allowed. No subscriber reply. Illegal equipment.27 Provide IMEI This message contains no information elements.1. Shall be present if it was received in the Provide Roaming Number for the waiting call. Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. Indicates that the CLIR override subscription option of CLIP is provisioned. otherwise shall be absent. 8. Indicates that COLR is provisioned. otherwise shall be absent. Shall be present if the Call Forwarding on No Reply service is active and operative. Illegal subscriber. otherwise shall be absent. Value of timer to be used to determine the No subscriber reply condition. otherwise shall be absent. Shall be present if the waiting call is a CUG call.1. Indicates that CLIP is provisioned. Unidentified subscriber.25 Process Call Waiting ack This message contains no information elements. System failure. otherwise shall be absent. otherwise shall be absent.24 Process Call Waiting The following information elements are required: Information element name MSISDN GSM bearer capability Required M C ISDN bearer capability ISDN low layer compatibility ISDN high layer compatibility CLIP provision CLIR override provision C C C C C COLR provision No Reply Condition Timer C C CUG index Advice of Charge provision C C Description MSISDN of the MS for which the Process Call Waiting is sent. Shall be present if Advice of Charge is provisioned. Busy subscriber (NDUB).0 Release 1999 216 ETSI TS 123 018 V3.1.018 version 3. otherwise shall be absent.0 (2002-03) 8. otherwise shall be absent.085 [18]. Shall be present if COLR is provisioned. 8.

8.3GPP TS 23.0 Release 1999 217 ETSI TS 123 018 V3.29 Provide IMSI This message contains no information elements.28 Provide IMEI ack The following information element is required: Information element name IMEI Required M Description IMEI of the ME involved in the access request.1. ETSI .1.018 version 3.11.0 (2002-03) 8.11.

Indicates whether the paging is for a circuit-switched call. TMSI to be broadcast to identify the MS.1.11. otherwise shall be absent. ETSI .018 version 3. Service area identity of the cell in which the served subscriber is located. SS activity or Active Location Retrieval.31 Radio connection released This message contains no information elements. 8.1. Shall be present if the MS uses UMTS radio access.0 Release 1999 218 ETSI TS 123 018 V3. Indicates that paging via the SGSN is possible. The Search For MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call. Shall be present if the VLR determines that the MS can be paged via the SGSN. Busy subscriber (More calls possible). MT SMS delivery.32 Search For MS The following information elements are required: Information element name IMSI Page type Required M M Paging via SGSN possible C TMSI O Description IMSI of the MS to be paged in all location areas. Busy subscriber (NDUB). 8. otherwise shall be absent.1.0 (2002-03) 8.1. Identity of the cell in which the served subscriber is located.1. otherwise shall be absent.11.30 Provide IMSI ack The following information element is required: Information element name IMSI Required M Description IMSI of the MS involved in the access request.3GPP TS 23.33 Search For MS ack The following information element is required: Information element name Location area ID Serving cell ID Required M C Service area ID C Description Location area in which the MS responded to the page.34 - Search For MS negative response The negative response information element can take the following values: Absent subscriber. 8. Shall be present if the MS uses GSM radio access. 8. System failure.

3GPP TS 23. Circuit-switched paging priority.35 Search for MS via SGSN The following information elements are required: Information element name IMSI eMLPP priority TMSI Channel type Required M O O O Description IMSI of the MS to be paged. Shall be present if it was received in the IAM. Shall be present if it was received in the IAM. Number of times the incoming call has already been forwarded. Number dialled by the calling subscriber. For the definition of this IE. Shall be present if it was received in the IAM. GSM bearer service required for the MT call.085 [18].1.0 Release 1999 219 ETSI TS 123 018 V3.1.11.36 Send Info For Incoming Call The following information elements are required: Information element name MSRN Bearer service Required M C Teleservice C Dialled number Number of forwarding C C CUG interlock CUG outgoing access C C Description Mobile Station Roaming Number received in the IAM.11.085 [18]. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. 8. Shall be present if it was received in the IAM. Type of channel required for the call. otherwise shall be absent. otherwise shall be absent. For the definition of this IE.0 (2002-03) 8. Shall be present if the MSC was able to derive a GSM teleservice from ISDN BC/LLC/HLC information received in the IAM. see 3GPP TS 23. TMSI to be broadcast to identify the MS. GSM teleservice 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. see 3GPP TS 23. ETSI .018 version 3.

018 version 3.1. Shall be present if the call is to be forwarded. otherwise shall be absent. see 3GPP TS 23. Indication of whether the forwarding party is to be notified that the call has been forwarded.11.164 number of the C subscriber. 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 3GPP TS 23. Indication of whether the calling party is to be notified that the call has been forwarded.085 [18]. Shall be present if a forwarded-to subaddress is stored in the VLR in association with the forwarded-to number. E.3GPP TS 23. ETSI . Shall be present if the call is to be forwarded.003 [5]). otherwise shall be absent. otherwise shall be absent. It will be used to create the redirecting number presented to the C subscriber. 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 3GPP TS 23.164 number which identifies the B subscriber. see 3GPP TS 23. on mobile subscriber busy.085 [18]. Indication of why the call has been forwarded (on call deflection. The preferred carrier identity identifying the carrier to be used to route the interexchange call if the forwarded call requires routing via an interexchange carrier. For the definition of this IE. For the definition of this IE.0 Release 1999 220 ETSI TS 123 018 V3. Shall be present if the call is to be forwarded on mobile subscriber busy or on no subscriber reply. E. otherwise shall be absent.11.085 [18]. Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber.0 (2002-03) 8. Subaddress of the C subscriber (see 3GPP TS 23. otherwise shall be absent. otherwise shall be absent. on mobile subscriber not reachable or on no subscriber reply).085 [18]. This parameter may be included at the discretion of the VLR operator.37 Send Info For Incoming Call ack The following information elements are required: Information element name IMSI Forwarded-to number Forwarding reason Required M M M Notification to calling party Notification to forwarding party M C Forwarded-to subaddress C Redirecting presentation C MSISDN C CUG interlock C CUG outgoing access C NAEA preferred Carrier Id O Description IMSI of the B subscriber.

8. For the definition of this IE. Busy subscriber. Call barred (Supplementary service barring). CUG reject (Inconsistent access information .0 Release 1999 221 ETSI TS 123 018 V3.1. ETSI .1.085 [18].3GPP TS 23. see 3GPP TS 23.0 (2002-03) 8.39 Send Info For Outgoing Call The following information elements are required: Information element name Called number Bearer service Required M C Teleservice C CUG index Suppress preferential CUG Suppress CUG outgoing access C C C Description E. For the definition of this IE. derived from the GSM bearer capability information received in the set-up request from the MS. Teleservice not provisioned. Unallocated roaming number. One of bearer service or teleservice shall be present. derived from the GSM bearer capability information received in the set-up request from the MS or from the emergency set-up request from the MS.38 - Send Info For Incoming Call negative response The negative response information element can take the following values: Absent subscriber. Shall be present if it was received in the set-up request from the MS.40 - Send Info For Outgoing Call negative response The negative response information element can take the following values: Bearer service not provisioned.164 number of the call destination. Forwarding violation. CUG reject (Inconsistent access information . No subscriber reply. see 3GPP TS 23. One of bearer service or teleservice shall be present.index incompatible with basic service). CUG reject (Outgoing calls barred within the CUG).085 [18].018 version 3. Bearer service required for the MO call.11. Shall be present if it was received in the set-up request from the MS. For the definition of this IE. Shall be present if it was received in the set-up request from the MS. CUG reject (Unknown CUG index).1.no CUG selected).085 [18].11. System failure. CUG reject (Called party SS interaction violation). 8. Teleservice required for the MO call. Impossible call completion. see 3GPP TS 23. Call barred (Operator determined barring).

3GPP TS 23.102 [31]). Shall be present if the ciphering mode indicates that ciphering of the radio connection is required.0 Release 1999 222 ETSI TS 123 018 V3.1.018 version 3. and if so which ciphering algorithm is to be used. The following information elements are required for a GSM connection: Information element name Ciphering mode Required M Description Indicates whether ciphering of the radio connection is required.102 [31]).1.0 (2002-03) 8.43 Use existing TMSI This message contains no information elements.08 [3] 8.41 Start security procedures The following information elements are required for a UMTS connection: Information element name CK IK Required M M Description Ciphering key to be used to cipher communication over the radio link (see 3GPP TS 33. see GSM 12. Ciphering key to be used if ciphering of the radio connection is required. Integrity key to be used to verify the integrity of messages transferred over the radio link (see 3GPP TS 33.1.11. ETSI . otherwise shall be absent. Kc C 8.42 Trace subscriber activity The following information elements are required: Information element name Trace reference Required M Trace type M Description Reference number to be included with tracing reports which the VMSC sends to the OMC For the definition of this IE.11.

otherwise shall be absent. Shall be present if the GMSC received it in the IAM.085 [18]. ISDN higher layer compatibility. For the definition of this IE. Shall be present if the GMSC received it in the IAM. otherwise shall be absent.11.018 version 3.3GPP TS 23.0 (2002-03) 8. otherwise shall be absent.11. Shall be present if the GMSC received it in the IAM and the HPLMN supports CUG. Shall be present if the GMSC supports pre-paging. ISDN bearer capability.1 Messages on the C interface (MSC-HLR) Send Routeing Info The following information elements are required: Information element name MSISDN Alerting Pattern Required M C CUG interlock C CUG outgoing access C Number of forwarding C ISDN BC ISDN LLC ISDN HLC Pre-paging supported C C C C Description MSISDN of the B subscriber (see 3GPP TS 23. Shall be present if the GMSC received it in the IAM and the HPLMN supports CUG. Shall be present if it was received in the IAM. ISDN lower layer compatibility. Shall be present if the GMSC received it in the IAM. ETSI . see 3GPP TS 23. For the definition of this IE. Shall be present if received in a Connect operation from the gsmSCF.085 [18].0 Release 1999 223 ETSI TS 123 018 V3.003 [5]). otherwise shall be absent. see 3GPP TS 23. otherwise shall be absent. Number of times the incoming call has already been forwarded.2 8. otherwise shall be absent. otherwise shall be absent.2. otherwise shall be absent.

Indication of whether the calling party is to be notified that the call has been forwarded. otherwise shall be absent.2. otherwise shall be absent.085 [18]. 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 3GPP TS 23. E. Indication of why the call has been forwarded (unconditionally or on mobile subscriber not reachable). E. otherwise shall be absent. ETSI . see 3GPP TS 23. otherwise shall be absent.018 version 3. otherwise shall be absent. Shall be present if the HLR has determined that the call is to be forwarded.003 [5]).085 [18]. see 3GPP TS 23. 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 3GPP TS 23.11. otherwise shall be absent.085 [18].11. This parameter may be included at the discretion of the HLR operator.085 [18]. For the definition of this IE. otherwise shall be absent. Subaddress of the C subscriber (see 3GPP TS 23.164 number which identifies the B subscriber (basic MSISDN).164 number of the C subscriber.2 Send Routeing Info ack The following information elements are required: Information element name IMSI Roaming number Required M C Forwarded-to number C Forwarded-to subaddress C Notification to calling party C Forwarding reason C Redirecting presentation C MSISDN C CUG interlock C CUG outgoing access C NAEA preferred Carrier Id O Description IMSI of the B subscriber (see 3GPP TS 23. E. 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. Shall be present if the HLR has determined that the call is to be forwarded. Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber.0 Release 1999 224 ETSI TS 123 018 V3. For the definition of this IE.3GPP TS 23. Shall be present if the HLR received it in the Provide Roaming Number ack and the call is not subject to early CF.164 number required to route the call to VMSCB (see 3GPP TS 23. Shall be present if the HLR has determined that the call is to be forwarded.003 [5]). Shall be present if the HLR has determined that the call is to be forwarded. The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier. It will be used to create the redirecting number presented to the C subscriber. otherwise shall be absent.0 (2002-03) 8. otherwise shall be absent.003 [5]). Shall be present if the HLR has determined that the call is to be forwarded.

Call barred (Operator determined barring).018 version 3. ETSI .11. CUG reject (Incoming calls barred within CUG).11.2. Forwarding violation Number changed. Unknown subscriber.3GPP TS 23.0 Release 1999 225 ETSI TS 123 018 V3. Unexpected data value. Teleservice not provisioned.3 - Send Routeing Info negative response The negative response information element can take the following values: Absent subscriber. Bearer service not provisioned. CUG reject (Called party SS interaction violation).0 (2002-03) 8. System Failure. CUG reject (Subscriber not member of CUG). CUG reject (Requested basic service violates CUG constraints). Data missing. Facility not supported. Call barred (Supplementary service barring).

ISDN bearer capability. otherwise shall be absent. Shall be present if the LMSI was sent to HLRB at location updating.3 - Provide Roaming Number negative response The negative response information element can take the following values: Absent subscriber. the VLR has indicated support for CAMEL Phase 3 or later. 8. it may be present if the HLR requires it to be included in the call data record. ISDN lower layer compatibility.3.164 number required to route the call to VMSCB (see 3GPP TS 23. If the GSM bearer capability IE is present. otherwise shall be absent.003 [5]).0 Release 1999 226 ETSI TS 123 018 V3.3 8. If the ISDN BC and ISDN LLC IEs are present. the ISDN LLC IE shall be absent. otherwise shall be absent.008.11. the GSM bearer capability IE shall be absent. otherwise shall be absent. It shall be present if the following 3 conditions are all satisfied: 1. Shall be present if the HLR received it in the Send Routeing Info message.164 number which identifies the B subscriber. 8. the subscriber has VT-CSI stored in HLR 3. ETSI .003 [5]).0 (2002-03) 8. otherwise shall be absent. Shall be present if the HLR has determined that pre-paging is supported in the GMSC and the HLR. May be present if the HLR can determine the required GSM bearer capability from ISDN compatibility information received in the Send Routeing Info message.1 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 LMSI GSM bearer capability C C ISDN BC C ISDN LLC C ISDN HLC C Alerting Pattern C Pre-paging supported C Description IMSI of the B subscriber (see 3GPP TS 23.2 Provide Roaming Number ack The following information element is required: Information element name Roaming number Required M Description E. May be present if the HLR received it in the Send Routeing Info message.164 number which identifies VMSCB (see 3GPP TS 23.11. Data missing. otherwise shall be absent. May be present if the HLR received it in the Send Routeing Info message. Shall be present if the HLR has determined an alerting category or an alerting level for the MT call configuration.003 [5]). If the GSM bearer capability IE is present. the MSISDN is different from the basic MSISDN 2. Information to define the GSM bearer capability required for the call. the ISDN BC IE shall be absent. or from the MSISDN if a multi-numbering scheme is used. E.018 version 3. alternate speech/data or speech followed by data calls this information element shall contain two GSM bearer capabilities. For alternate speech/fax.3. Local Mobile Subscriber Identity. ISDN higher layer compatibility.3GPP TS 23. E.3. as specified in 3GPP TS 24.

Indicates whether the HLR requires location information.11. otherwise shall be absent.0 Release 1999 227 ETSI TS 123 018 V3. 8. Shall be present if the LMSI was sent to the HLR at location updating. 8.3. Shall be present if subscriber state was requested. Shall be present if location information was requested and is available. Local Mobile Subscriber Identity. subscriber state or both location information and subscriber state. Unexpected data value.5.3. Indicates whether the MS is busy (i. No roaming number available.e.1. Indicates that the HLR requires active location retrieval.5 Provide Subscriber Info ack The following information elements are required: Information element name Location information Required C Subscriber state C Description Information to define the location of the MS: see definition in clause 8. ETSI .4 Provide Subscriber Info The following information elements are required: Information element name IMSI Required M LMSI Requested information Active location retrieval requested C M C Description IMSI of the subscriber for whom information is requested (see 3GPP TS 23. network determined not reachable (IMSI detached or roaming in a prohibited location area) or assumed idle.3GPP TS 23.11. OR not allowed. otherwise shall be absent. Shall be absent if the requested information does not indicate that the HLR requires location information.3.018 version 3.0 (2002-03) - Facility not supported.003 [5]). engaged on a circuitswitched call).

otherwise shall be absent. otherwise shall be absent. Shall be present if available in the MSC/VLR. Shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval. 8.1 Location information The compound information element Location information consists of the following subordinate information elements: Information element name Location number Required C Service area ID C Cell ID C Geographical information C Geodetic information C VLR number Age of location information Current Location Retrieved O C C Description For a definition of this information element. otherwise shall be absent.3. see 3GPP TS 23.003 [5]). The mapping from service area identity or cell ID and location area to location number is network-specific and outside the scope of the UMTS and GSM standards.032 [7] . ETSI .3GPP TS 23. otherwise shall be absent. cell global identity or location area identity. Shall be present if the VLR can derive it from the stored service area identity (for UMTS) or cell global identity (for GSM) or location area identity. Measured in minutes.0 (2002-03) 8.5. otherwise shall be absent. Unexpected data value.11. This information element corresponds to the Calling Geodetic Location defined in ITU-T Recommendation Q. LMSI of the subscriber for whom data are to be restored (see 3GPP TS 23.0 Release 1999 228 ETSI TS 123 018 V3. If the HLR receives it from the VLR it shall ignore it.763 [34]. Shall be present if the VLR can derive it from the stored service area identity.7 Restore Data The following information elements are required: Information element name IMSI Required M LMSI O Description IMSI of the subscriber for whom data are to be restored (see 3GPP TS 23. For a definition of this information element. 8.3. otherwise shall be absent.11.164 number which identifies the VLR (see 3GPP TS 23.763 [34]. Shall be present if the MS uses GSM radio access and the subscriber record is marked as confirmed by radio contact.003 [5]).3. System failure. Cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. May be included if required by the requesting VLR.003 [5]). Shall be present if the VLR can derive it from the stored service area identity. Service area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact.6 - Provide Subscriber Info negative response The negative response information element can take the following values: Data missing.018 version 3. Shall be present if the MS uses UMTS radio access and the subscriber record is marked as confirmed by radio contact. see ITU-T Recommendation Q. E. cell global identity or location area identity.

1 Messages on the F interface (MSC-EIR) Check IMEI The following information element is required: Information element name IMEI Required M Description IMEI of the ME whose status is to be checked (see 3GPP TS 23.11.4 8.4.003 [5]). otherwise shall be absent.9 - Restore Data negative response The negative response information element can take the following values: System failure.4.3 - Check IMEI negative response The negative response information element can take the following value: Unknown equipment.164 number which identifies the HLR (see 3GPP TS 23. 8. ETSI .8 Restore Data ack The following information elements are required: Information element name HLR number MS not reachable flag Required M C Description E. Shall be present if the corresponding indicator is set in the HLR record for the subscriber.2 Check IMEI ack The following information element is required: Information element name Equipment status Required M Description Indicates whether the ME is black-listed.018 version 3. 8.0 Release 1999 229 ETSI TS 123 018 V3.003 [5]).11. grey-listed or white-listed 8.4.3.0 (2002-03) 8. 8. Unknown subscriber.3GPP TS 23.3. Indicates whether the VLR should notify the HLR when the MS next establishes radio contact.

164 number of the C subscriber. 8.079 [13] 8. 8. 8. 8.2 PAR completed This message contains no information elements. ETSI .5.6.3 Perform Call Forwarding ack Information element name Forwarded-to number Required M Description E.2 Perform Call Forwarding Information element name Forwarded-to number OR call Required M M Description E. and ISUP messages received from the destination exchange and to be forwarded to the process MT_GMSC or the process ICH_MSC.164 number of the C subscriber. 8. In addition. Indicates whether the call which is to be forwarded was subject to basic OR as specified in 3GPP TS 23.1 Call arrived This message contains no information elements.018 version 3.11.0 (2002-03) 8.5. 8.5 Messages on the MSC internal interface This interface can carry ISUP messages received from the process MT_GMSC or the process ICH_MSC and to be forwarded to a destination exchange.0 Release 1999 230 ETSI TS 123 018 V3.6.6 Messages on the VLR internal interface This interface carries messages between corresponding instances of the processes PRN_VLR and ICH_VLR.4 - Perform Call Forwarding negative response The negative response information element can take the following value: Call forwarding failed.11. Note: this number may be different from the Forwarded-to number received in the Perform Call Forwarding.1 CF cancelled This message contains no information elements. The correlation between the process instances is done by the MSRN. it carries the following inter-process messages.5.5. as a result of CAMEL handling.3GPP TS 23.

0 Release 1999 231 ETSI TS 123 018 V3.7. TMSI to be broadcast to identify the MS. Information required for the specified MS.11. otherwise shall be absent.7.3GPP TS 23. Shall be present if it was received in the Page MS via SGSN request or Search for MS via SGSN request. Shall be present if the MS uses UMTS access. Location area identity of the location area where the mobile is registered. 8.7 8. otherwise shall be absent.11. according to the subscriber data in the VLR. these IEs are mandatory in this context.3 Send MS information ack The following information elements are required: Information element name IMSI Service area ID Required M C Cell ID C Location information age M (note) Description IMSI of the MS for which information is required.2 Send MS information The following information elements are required: Information element name IMSI Information requested Required M M Description IMSI of the MS for which information is required. Shall be present if it was received in the Page MS via SGSN request or Search for MS via SGSN request. Shall be present if the VLR can supply it. Type of channel required for the call. Shall be present if the MS uses GSM access. Shall be present if it was received in the Page MS via SGSN request or Search for MS via SGSN request.4 - Send MS information negative response The negative response information element can take the following value: No response from SGSN ETSI .7.1 Messages on the Gs interface Page MS The following information elements are required: Information element name IMSI eMLPP priority Required M C TMSI C Location area identity C Channel type C Description IMSI of the MS to be paged. otherwise shall be absent. otherwise shall be absent. Time in minutes since the MS last established a radio transaction NOTE: Although they are optional in the protocol. otherwise shall be absent. otherwise shall be absent.7.0 (2002-03) 8. Circuit-switched paging priority. 8. Cell ID (for GSM access) of the cell in which the MS last established radio contact.018 version 3. 8. Service area ID (for UMTS access) of the cell in which the MS last established radio contact.

After the MSC co-ordinating process has relayed a Release message. i. it acts as a transparent relay for messages received from the originating exchange and the process instance (denoted by "offspring").11.e. Sheet 2: after the MSC co-ordinating process has sent an IAM to a destination exchange. a GMSC or a transit exchange.e. It acts as a terminating exchange. it returns to the idle state. it interrogates an HLR for information to route the call. If the HLR returns routeing information. 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. i.3GPP TS 23. After the MSC co-ordinating process has relayed a Release message.e. i. It acts as a GMSC. it attempts to connect the call to an MS currently registered in the service area of the MSC. This behaviour is not specific to UMTS or GSM. it acts as a transparent relay for messages received from the originating exchange and the destination exchange.11.018 version 3. - Sheet 1: when the MSC co-ordinating process has decided whether the MSC is to act as a terminating VMSC. it returns to the idle state. Sheet 2: after the MSC co-ordinating process has sent an IAM to an instance of the process MT_GMSC or ICH_MSC.0 (2002-03) Annex A (informative): Handling of an IAM at an MSC An MSC which receives an IAM from an originating exchange may react in three different ways: It acts as a transit exchange.0 Release 1999 232 ETSI TS 123 018 V3. the MSC uses the routeing information from the HLR to construct an IAM. it forwards the IAM to an idle instance of the appropriate process. which it sends to a destination exchange determined by analysis of the routeing information from the HLR. ETSI .

3GPP TS 23.11.0 Release 1999 233 ETSI TS 123 018 V3.11.018 version 3.0 (2002-03) Process MSC _Coord Proc ess in the MSC to ha ndle an incoming IAM and trigger the correc t application process C oord_M1(2) ID LE Initial Addres s From originating exchange Called party address in MSRN range for t hi s MSC? Yes No No Inc oming IAM was routed with ro utei ng n umber for MN P? Yes Recov er ported number from IAM HLR address d eriv able? Yes No T o process IC H_ MSC Initial Addres s Initi al A ddress T o process MT _G MS C Initial Addres s To des tination determined by rou teing tables Relay_ I nformation_ I nternally Relay_ Information_ External ly Figure 84a: Process MSC_Coord (sheet 1) ETSI .

018 version 3.11.11.0 (2002-03) Process M S C_Coord Proc ess in the MS C to handle an inco mi ng IA M and tri gger the correct appl ic ati on process R el ay_ Infor mati on_ Inter nal ly Coord_M 2(2) Re lease From originating exchange R elease F rom of fspring Re lease To offspring R elease To origi nati ng exchange ID LE * From originating ex change ID LE * From of fspri ng - To of fspri ng - To originating ex change R el ay_ Inform ation_ Internall y R elay_ Inform ation_ Internal ly R el ay_ Infor mati on_ E xt ernall y Re lease From originating exchange R elease F rom des ti nati on exchange Re lease To desti nati on exchange R elease To origi nati ng exchange ID LE * From originating ex change ID LE * From desti nati on ex change - To destination ex change R el ay_ Inform ation_ Externally - To originating ex change R elay_ Inform ation_ Externally Figure 82b: Process MSC_Coord (sheet 2) ETSI .0 Release 1999 234 ETSI TS 123 018 V3.3GPP TS 23.

0 3.018 23.018 23.3.4.0 3.4.018 CN#04 23.018 23.0 3.3.4.0 3.4.5.018 Introduction of CAMEL Phase 3 Addition of the description for Multicall Alternative solution for ALR Correction of the SDL diagrams for Prepaging Inclusion of D-CSI check in HLR/VLR Initialisation of Backward Call indicator Correction of the result of the procedure CAMEL_ICH_MSC_INIT Clarification of N-CSI in Core NW Replacement of references to GSM with references to UMTS Clarification of NPDB error detection and MNP specific call handling Setting the Destination Address for MO calls O-CSI and D-CSI checks for ORLCF calls Correction of CF Notification Introduction of Authentication Failure Report ISUP release cause value Correction of CAMEL Incoming Call Handling Improvement of Active Retrieval of Location Information procedure North American Service Provider Number Portability impacts for MNP Correction of connector numbering in process ICH_MSC Correction of the SDL diagram for Prepaging Correction to process ICH_VLR Handling of the Call Diversion Treatment Indicator Modifications to procedure obtain routeing address.5.0 CN#05 CN#05 CN#05 CN#05 CN#05 23.0 3.6.018 23.4.0 3.6.0 3.0 3.0 3.0 3.018 23.018 23.018 23.018 23.0 3.0 3.018 3.018 23.3.11.0 001 <Phase> New Version Subject/Comment Transferred to 3GPP CN1 Approved at CN#03 Notification of Call Forwarding to the gsmSCF Addition of the description for Pre-Paging Removal of TDP criteria from Resume Call Handling GMSC CAMEL phases in Provide Roaming Number Separation of success & failure cases for OR of late call forwarding Notification of Call Forwarding to the gsmSCF before activating call forwarding process Introduction of the Super-Charger Concept in TS 23.4.3.0 3.0 3.1.018 CN#11 23.0 004r2 027r3 025r7 026r2 030 032r1 033 034 037 039r2 043r1 044 047 048 049 050r3 045r1 051r4 052r2 053 054 056 057r3 059r1 060 061r2 063r1 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 R99 3.0 3.0 3.0 3.6.018 23.0 3.0 3.0 3.5.0 (2002-03) Annex B: Change history Change history TSG CN# Spec Version CR Apr 1999 GSM 03.0 3.4.018 3.018 23.0 3.3.0.0 3.0 3.2.6.4.2.0 3.5.018 23.0 3.5.0 CN#07 CN#08 CN#09 23.0 CN#03 23.018 23.018 23.0 3.3.018 23.3.0 3.0 3.018 23.0 3.6.2.0 Release 1999 235 ETSI TS 123 018 V3.5.0 3.3.0 3.4.0 3.7.0 3.6.018 3.0 3.4.018 23.0 3.4.18 7.4.3.0 3.0 3.0 3.3.3.0 3.0 3.4.6.0 002r4 006 007r1 023 024 CN#06 23.0 068 R99 3.5.0.4.5.018 23.0 3.018 version 3.1.0 3.1.3.0 3.0 3.0 3.0 3.4.3.018 23.11.6.1.0 3.0 ETSI .3.018 23.3.5.3.0 3.018 23.1.018 23.018 23.0 3.4.0 3.3GPP TS 23.1.0 3.018 23.0 3.5.2.2.0 3.0 3.0 3.2.0 3.0 3.0 3.018 23. Corrections to process ICH_VLR Update of CAMEL references Correction of procedure Obtain_Routeing_Address for the reconnect case Paging not via the SGSN correction R99 R99 R99 R99 R99 R99 R99 3.018 23.0 3.018 3.0.2.018 23.0 3.6.5.0 3.4.018 23.018 23.

11.11.10.0 3.0 (2002-03) Change history TSG CN# Spec CN#12 23.0 Corrections in the ATI mechanism description R99 3.0 073 <Phase> New Version Subject/Comment R99 3.018 Version CR 3.018 23.0 3.10.9.0 3.018 23.9.0 Handling of Reconnect on Leg2 Disconnect R99 3.0 3.018 23.018 23.0 Handling of CUG calls in non-supporting networks R99 3.018 23.0 Release 1999 236 ETSI TS 123 018 V3.018 23.9.8.018 23.8.10.8.11.10.11.7.10.0 Correction on the Active Location Retrieval description R99 3.0 Initialisation of variable to monitor activation of CSI’s R99 3.0 3.0 MSISDN in Provide Roaming Number in case of MSP CN#13 CN#13 CN#14 CN#14 CN#14 CN#15 CN#15 CN#15 23.0 075 078 079 089r2 086r2 096 101r1 ETSI .10.0 Missing connector in procedure Process_Call_Waiting_MSC R99 3.11.018 version 3.9.018 3.3GPP TS 23.0 Addition of missing process Update_Location_VLR R99 3.0 Editorial clean up R99 3.0 3.9.0 3.

6.0 V3.0 V3.11.10.0 January 2000 March 2000 June 2000 September 2000 March 2001 June 2001 September 2001 January 2002 March 2002 Publication Publication Publication Publication Publication Publication Publication Publication Publication ETSI .3.0 V3.018 version 3.0 Release 1999 237 ETSI TS 123 018 V3.0 V3.3GPP TS 23.11.5.11.4.8.0 V3.0 (2002-03) History Document history V3.0 V3.0 V3.9.0 V3.7.

Sign up to vote on this title
UsefulNot useful