You are on page 1of 290

3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; V10.1.

0 (2011-03) Basic call handling; Technical Specification Technical realization (Release 10)

3GPP TS 23.018

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.

Release 10

2

3GPP TS 23.018 V10.1.0 (2011-03)

Keywords
UMTS, GSM, basic, call

3GPP Postal address 3GPP support office address
650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
© 2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS™ is a Trade Mark of ETSI registered for the benefit of its members 3GPP™ is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE™ is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners GSM® and the GSM logo are registered and owned by the GSM Association

3GPP

Release 10

3

3GPP TS 23.018 V10.1.0 (2011-03)

Contents
Contents....................................................................................................................................................3 Foreword...................................................................................................................................................7 1 Scope......................................................................................................................................................8 2 References..............................................................................................................................................8 3 Definitions and abbreviations...............................................................................................................10
3.1 Definitions............................................................................................................................................................10 3.2 Abbreviations.......................................................................................................................................................10

4 Architecture..........................................................................................................................................11
4.1 Architecture for an MO call.................................................................................................................................11 4.2 Architecture for an MT call..................................................................................................................................12 4.3 Architecture for a TO call....................................................................................................................................12

5 Information flows.................................................................................................................................13
5.1 Information flow for an MO call..........................................................................................................................13 5.2 Information flow for retrieval of routeing information for an MT call................................................................16 5.2.1 Mobile Terminating Roaming Retry Call after successful Retrieval of Routeing Information........................17 5.2.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing Information......................................19 5.2.3 Mobile Terminating Roaming Forwarding Call after successful Retrieval of Routeing Information..............22 5.3 Information flow for an MT call..........................................................................................................................26

6 Principles for interactions with supplementary services.......................................................................28
6.1 Call Deflection service (3GPP TS 23.072)..........................................................................................................29 6.2 Line identification services (3GPP TS 23.081)....................................................................................................29 6.2.1 Calling Line Identification Presentation (CLIP)...............................................................................................29 6.2.2 Calling Line Identification Restriction (CLIR).................................................................................................29 6.2.3 Connected Line Identification Presentation (COLP)........................................................................................29 6.2.4 Connected Line Identification Restriction (COLR)..........................................................................................29 6.3 Call forwarding services (3GPP TS 23.082)........................................................................................................29 6.3.1 Call Forwarding Unconditional (CFU).............................................................................................................29 6.3.2 Call Forwarding on mobile subscriber Busy (CFB).........................................................................................29 6.3.3 Call Forwarding on No Reply (CFNRy)...........................................................................................................29 6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc).....................................................................29 6.4 Call wait (3GPP TS 23.083).................................................................................................................................30 6.5 Call hold (3GPP TS 23.083)................................................................................................................................30 6.6 Multiparty (3GPP TS 23.084)..............................................................................................................................30 6.7 Closed user group (3GPP TS 23.085)..................................................................................................................30 6.8 Advice of charge (3GPP TS 23.086)....................................................................................................................30 6.9 User-to-user signalling (3GPP TS 23.087)..........................................................................................................30 6.10 Call barring (3GPP TS 23.088)..........................................................................................................................30 6.10.1 Barring of outgoing calls.................................................................................................................................30 6.10.2 Barring of incoming calls................................................................................................................................30 6.11 Explicit Call Transfer (3GPP TS 23.091)..........................................................................................................31 6.12 Completion of Calls to Busy Subscriber (3GPP TS 23.093).............................................................................31 6.13 Multicall (3GPP TS 23.135)..............................................................................................................................31

7 Functional requirements of network entities........................................................................................31
7.1 MO call.................................................................................................................................................................32 7.1.1 Functional requirements of serving MSC.........................................................................................................32 7.1.1.1 Process OCH_MSC........................................................................................................................................32 7.1.1.2 Procedure Process_Access_Request_MSC....................................................................................................32 7.1.1.3 Procedure OG_Call_Setup_MSC...................................................................................................................32 7.1.1.4 Procedure Obtain_IMSI_MSC.......................................................................................................................34 7.1.1.5 Procedure Authenticate_MSC........................................................................................................................34 7.1.1.6 Procedure Obtain_IMEI_MSC.......................................................................................................................34 7.1.1.7 Procedure Check_IMEI_MSC.......................................................................................................................34

3GPP

Release 10

4

3GPP TS 23.018 V10.1.0 (2011-03)

7.1.1.8 Procedure Establish_Originating_TCH_If_Required....................................................................................35 7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC........................................................................................35 7.1.1.10 Procedure Send_Alerting_If_Required........................................................................................................35 7.1.1.11 Procedure Set_COLP_Info_MSC................................................................................................................35 7.1.1.12 Procedure Send_Access_Connect_If_Required...........................................................................................35 7.1.1.13 Procedure Handle_AoC_MO_MSC.............................................................................................................35 7.1.1.14 Procedure TCH_Check................................................................................................................................36 7.1.2 Functional requirements of VLR......................................................................................................................62 7.1.2.1 Process OCH_VLR........................................................................................................................................62 7.1.2.2 Procedure Process_Access_Request_VLR....................................................................................................62 7.1.2.3 Procedure OG_Call_Subscription_Check_VLR............................................................................................62 7.1.2.4 Procedure Obtain_Identity_VLR...................................................................................................................62 7.1.2.5 Procedure Obtain_IMSI_VLR.......................................................................................................................62 7.1.2.6 Procedure Authenticate_VLR........................................................................................................................62 7.1.2.7 Procedure Obtain_Authentication_Sets_VLR...............................................................................................63 7.1.2.8 Procedure Start_Tracing_VLR.......................................................................................................................63 7.1.2.9 Procedure Check_IMEI _VLR.......................................................................................................................63 7.1.2.10 Procedure Obtain_IMEI_VLR.....................................................................................................................63 7.1.2.11 Process Fetch_Authentication_Sets_VLR...................................................................................................63 7.1.2.12 Procedure Check_BAOC.............................................................................................................................63 7.1.2.13 Procedure OG_CUG_Check........................................................................................................................63 7.1.2.14 Procedure Get_LI_Subscription_Info_MO_VLR........................................................................................63 7.1.2.15 Procedure Get_AoC_Subscription_Info_VLR............................................................................................63 7.1.2.16 Procedure Check_OG_Barring....................................................................................................................63 7.1.2.17 Process Update_Location_VLR...................................................................................................................63 7.2 Retrieval of routeing information for MT call.....................................................................................................90 7.2.1 Functional requirements of GMSC...................................................................................................................90 7.2.1.1 Process MT_GMSC.......................................................................................................................................90 7.2.1.2 Procedure Obtain_Routeing_Address............................................................................................................92 7.2.1.3 Procedure Send_ACM_If_Required..............................................................................................................93 7.2.1.4 Procedure Send_Answer_If_Required...........................................................................................................93 7.2.1.5 Procedure Send_Network_Connect_If_Required..........................................................................................94 7.2.1.6 Procedure Handle_COLP_Forwarding_Interaction_MSC............................................................................94 7.2.1.7 Procedure Activate_CF_Process....................................................................................................................94 7.2.1.8 Process MT_CF_MSC...................................................................................................................................94 7.2.1.9 Macro CUG_Support_Check_GMSC............................................................................................................96 7.2.2 Functional requirements of HLR....................................................................................................................122 7.2.2.1 Process SRI_HLR........................................................................................................................................122 7.2.2.2 Procedure Check_Parameters.......................................................................................................................124 7.2.2.3 Procedure Subscription_Check_HLR..........................................................................................................124 7.2.2.4 Procedure First_Forwarding_HLR...............................................................................................................125 7.2.2.5 Procedure PRN_Error_HLR........................................................................................................................125 7.2.2.6 Procedure Forward_CUG_Check................................................................................................................125 7.2.2.7 Void 125 7.2.2.8 Procedure Check_IC_Barring......................................................................................................................125 7.2.2.9 Procedure IC_CUG_Check..........................................................................................................................125 7.2.2.10 Procedure Handle_CFU.............................................................................................................................125 7.2.2.11 Procedure Handle_CFNRc.........................................................................................................................125 7.2.3 Functional requirements of VLR....................................................................................................................143 7.2.3.1 Process PRN_VLR.......................................................................................................................................143 7.2.3.2 Process Restore_Subscriber_Data_VLR......................................................................................................144 7.2.3.3 Process PSI_VLR.........................................................................................................................................144 7.2.3.4 Procedure Retrieve_Location_Info_VLR....................................................................................................144 7.2.3.5 Procedure Active_Info_Retrieval_VLR.......................................................................................................144 7.2.4 Functional requirements of MSC....................................................................................................................159 7.2.4.1 Process Prepage_MSC.................................................................................................................................159 7.2.4.2 Procedure Prepaging_Page_MS_MSC........................................................................................................159 7.2.4.3 Prepaging_Search_For_MS_MSC...............................................................................................................159 7.2.4.4 Process OSI_MSC........................................................................................................................................159 7.2.4.5 Process RCL_MSC......................................................................................................................................159 7.2.4.6 Procedure Active_Info_Retrieval_Page_MSC............................................................................................159

3GPP

Release 10

5

3GPP TS 23.018 V10.1.0 (2011-03)

7.2.4.7 Procedure Active_Info_Retrieval_Search_MSC.........................................................................................159 7.2.4.8 Procedure Retrieve_IMEI_If_Required.......................................................................................................160 7.3 MT call...............................................................................................................................................................168 7.3.1 Functional requirements of serving MSC.......................................................................................................168 7.3.1.1 Process ICH_MSC.......................................................................................................................................168 7.3.1.2 Procedure Page_MS_MSC...........................................................................................................................170 7.3.1.3 Procedure Search_For_MS_MSC................................................................................................................171 7.3.1.4 Procedure Complete_Call_In_MSC.............................................................................................................172 7.3.1.5 Void 173 7.3.1.6 Procedure Set_CLIP_Info_MSC..................................................................................................................173 7.3.1.7 Void 174 7.3.1.8 Procedure Establish_Terminating_TCH_If_Required.................................................................................174 7.3.1.9 Procedure Handle_AoC_MT_MSC.............................................................................................................174 7.3.1.10 Procedure Set_COL_Presentation_Indicator_MSC...................................................................................174 7.3.2 Functional requirements of VLR....................................................................................................................215 7.3.2.1 Process ICH_VLR........................................................................................................................................215 7.3.2.2 Void 216 7.3.2.3 Procedure Search_For_MS_VLR................................................................................................................216 7.3.2.4 Procedure Get_CW_Subscription_Info_VLR.............................................................................................216 7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR........................................................................................216 7.3.2.6 Procedure Handle_CFB...............................................................................................................................216 7.3.2.7 Procedure Handle_CFNRy...........................................................................................................................217 7.4 Subs_FSM..........................................................................................................................................................230 7.4.1 Functional requirements of serving MSC.......................................................................................................230 7.4.1.1 Process Subs_FSM.......................................................................................................................................230 7.4.1.1.1 Macro Check_Ongoing_Calls...................................................................................................................231 7.4.1.1.2 Macro Update_Non_Speech_Calls_Status...............................................................................................231 7.4.1.1.3 Macro Increment_Call_Counter................................................................................................................231 7.4.1.1.4 Macro Decrement_Call_Counter..............................................................................................................231 7.5 TO call................................................................................................................................................................253 7.5.1 Functional requirements of inter-connecting MSC.........................................................................................253 7.5.1.1 Process TO_MSC.........................................................................................................................................253

8 Contents of messages.........................................................................................................................261
8.1 Messages on the B interface (MSC-VLR).........................................................................................................262 8.1.1 Abort 262 8.1.2 Authenticate....................................................................................................................................................262 8.1.3 Authenticate ack..............................................................................................................................................263 8.1.4 Authenticate negative response.......................................................................................................................263 8.1.5 Call arrived......................................................................................................................................................263 8.1.6 Check IMEI.....................................................................................................................................................263 8.1.7 Check IMEI ack..............................................................................................................................................263 8.1.8 Check IMEI negative response.......................................................................................................................263 8.1.9 Complete Call..................................................................................................................................................264 8.1.10 Complete Call ack.........................................................................................................................................265 8.1.11 Complete Call negative response..................................................................................................................265 8.1.12 Forward New TMSI......................................................................................................................................265 8.1.13 Forward New TMSI ack................................................................................................................................265 8.1.14 Forward New TMSI negative response.........................................................................................................265 8.1.15 Obtain Subscriber Info..................................................................................................................................265 8.1.16 Obtain Subscriber Info ack............................................................................................................................265 8.1.17 Page MS........................................................................................................................................................266 8.1.18 Page MS ack..................................................................................................................................................266 8.1.19 Page MS negative response...........................................................................................................................266 8.1.20 Page MS via SGSN.......................................................................................................................................267 8.1.21 Process Access Request................................................................................................................................267 8.1.22 Process Access Request ack..........................................................................................................................267 8.1.23 Process Access Request negative response...................................................................................................268 8.1.24 Process Call Waiting.....................................................................................................................................268 8.1.25 Process Call Waiting ack..............................................................................................................................268 8.1.26 Process Call Waiting negative response.......................................................................................................269 8.1.27 Provide IMEI.................................................................................................................................................269

3GPP

...........................5..................................8 Messages on the E interface (GMSC-VMSC)..............................................................................................................................................................................5............1...............................................................3 Perform Call Forwarding ack..........282 8...281 8.......................................................................5..3..5.............4....................................................................................................................................279 8...........................269 8.......................33 Search For MS ack..278 8......281 8.......................................................................................................................................................2...........................................273 8...282 8..........281 8.......3 Send MS information ack...............................................................................274 8...........................................................................................................274 8.....................................4.............................280 8.....................................1....7................................1.1...................................................................................................................................................................2 Provide Roaming Number ack................................................................................................................................................................................283 8........................................269 8....................................................................41 Start security procedures...42 Trace subscriber activity..............................................................................2 Check IMEI ack............1........................................................................1...................5 Provide Subscriber Info ack........................................................3................................................................281 8..280 8...............283 8..3 Check IMEI negative response..................................6 Messages on the VLR internal interface.....................................................................................................................285 Annex B (informative): Change history.............................................................................274 8.............................................271 8.......1.........1...40 Send Info For Outgoing Call negative response....................1 Check IMEI................................................5 Messages on the MSC internal interface........................273 8....................................................29 Provide IMSI........................................................................................32 Search For MS...............281 8...............................................................................2 Send Routeing Info ack....................................................1 Send Routeing Info.....................................................3..................................4 Provide Subscriber Info..........................................1..................276 8.................39 Send Info For Outgoing Call...............................272 8........................................3................................................................................................3 Messages on the D interface (VLR-HLR)......................273 8.................................1 Provide Roaming Number..................................................................................................2 Perform Call Forwarding........................................1 Call arrived.............................................................................................................270 8.......................................271 8...283 8..4 Send MS information negative response......269 8...............1 Page MS....................................................................................................................................282 8......................................8 Restore Data ack........................................................Release 10 6 3GPP TS 23..................................................................................................................3 Provide Roaming Number negative response......................................................35 Search for MS via SGSN......7 Restore Data...............................................................................................................................................................7....................5........................................281 8............................3.............................................0 (2011-03) 8............................................3......................................7...............1 Location information.......6 Provide Subscriber Info negative response......................274 8............................3.................................................277 8..................................................................................................1..................................................38 Send Info For Incoming Call negative response..........7 Messages on the Gs interface.........................6....................2 PAR completed....................2.........................................................282 8.....3...........2....................................................................................................................1................................1.....283 8....................................................................................................................287 3GPP ...............................................1.........................................................1 Release Resources.....................................................................................................282 8.....................................276 8..........................................................................................................018 V10..........................278 8.........................................................................................................................272 8...............................................3..44 Release MSRN...........................................................36 Send Info For Incoming Call........................................................................279 8...................................269 8............................2 Send MS information...................................................................8..............3 Send Routeing Info negative response......................................................................................................1............................................4..37 Send Info For Incoming Call ack...30 Provide IMSI ack........................................................................4 Perform Call Forwarding negative response......................................................2 Messages on the C interface (MSC-HLR)...282 8......................1..43 Use existing TMSI....................283 8.........................................................................................284 8................................1..........284 Annex A (informative): Handling of an IAM at an MSC......7.........6..........................270 8................1 CF cancelled.............................274 8..........................1..40A Send UESBI-Iu to Access Network.............................................280 8.............................282 8.282 8...................9 Restore Data negative response.............1....................................273 8...........................................................................................................277 8.......34 Search For MS negative response.........4 Messages on the F interface (MSC-EIR).............................................................................................................3...................................28 Provide IMEI ack......1................31 Radio connection released...........................................................................................................................................................269 8..

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

If there is any conflict between the present document and the corresponding stage 3 specifications (3GPP TS 24.018 V10. The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling.072: "Call deflection Supplementary Service. • For a specific reference. The logical separation of the MSC and VLR (shown in clauses 4. 3GPP TR 21. 2 References • References are either specific (identified by date of publication. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] 3GPP TS 43. the latest version applies.09x series of specifications.Release 10 8 3GPP TS 23. edition number.07x.032: "Universal Geographical Area Description (GAD)". 3GPP .003: "Numbering. a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.008: "Telecommunication management. etc. up to the point where the call is established. constitute provisions of the present document. as appropriate. Trunk Originated call is also modelled. but is required for both CAMEL (3GPP TS 23. The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the relevant 3GPP TS 23.1. the term MS is used to denote a UMTS UE or GSM MS.020: "Security related Network Functions". 3GPP TS 48. Void 3GPP TS 23.Base Station System (MSC .413 [27].008 [2] and 3GPP TS 29. The following documents contain provisions which.079 [13]. the stage 3 specification shall prevail. The use of the Provide Subscriber Information message flow is shown in 3GPP TS 23. 3GPP TS 23. They do not impose any requirement except the definition of the externally visible behaviour.079 [13]).08x and 3GPP TS 23.008 [26].012: "Location management procedures". addressing and identification". 3GPP TS 52. 3GPP TS 25. In the case of a reference to a 3GPP document (including a GSM document). subsequent revisions do not apply. In the present document. GSM subscriber and equipment trace". 3GPP TS 23. Stage2".078 [12] and 3GPP TS 23. 3GPP TS 23. • For a non-specific reference.066: "Support of GSM Mobile Number Portability (MNP). Service description.0 (2011-03) 1 Scope The present document specifies the technical realization of the handling of calls originated by a UMTS or GSM mobile subscriber and calls directed to a UMTS or GSM mobile subscriber. through reference in this text. Stage 2".BSS) interface Layer 3 specification".060: "General Packet Radio Service (GPRS). 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.905: "Vocabulary for 3GPP Specifications". 3GPP TS 23.078 [12]) and optimal routeing (3GPP TS 23. 5 and 7). 3GPP TS 48. 3GPP TS 23. 3GPP TS 23. version number. The handling of DTMF signalling and Off-Air Call set-up (OACSU) are not described in the present document. which is a single physical entity.008: "Mobile Switching Centre . Normal release of the call after establishment is also specified.002 [29]).) or non-specific. Stage 2".

ITU-T Recommendation Q. 3GPP TS 23.BSS) and Base Station System . Stage 2". 3GPP TS 23. 3GPP TS 23. ITU-T Recommendation Q.850 (1996): "Usage of cause and location in the Digital Subscriber Signalling System No. 7 – ISDN user part signalling procedures".1.091: "Explicit Call Transfer (ECT) supplementary service. 3GPP TS 23. Stage 2".762 (1999): "Signalling System No.763 (1999): "Signalling System No.010: "Information Element Mapping between Mobile Station . Stage 2".086: "Advice of Charge (AoC) Supplementary Service.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)". 3GPP TS 25. 3GPP TS 23. Stage 2". 3GPP TS 29.002: "Mobile Application Part (MAP) specification". Stage 2".018 V10.Mobile-services Switching Centre (BSS . 3GPP TS 23. 7 . ITU-T Recommendation Q.082: "Call Forwarding (CF) Supplementary Services.135: "Multicall supplementary service. 3GPP TS 23. 3GPP TS 29.MSC) Signalling Procedures and the Mobile Application Part (MAP)". Stage 3".ISDN User Part general functions of messages and signals".078: "Customized Applications for Mobile network Enhanced Logic (CAMEL). 7 .085: "Closed User Group (CUG) Supplementary Service.Base Station System (MS .088: "Call Barring (CB) Supplementary Service. 3GPP TS 27.116: "Super-charger technical realization. Stage 2". 3GPP TS 23. 7 ISDN User Part".084: "Multi Party (MPTY) Supplementary Service.ISDN User Part formats and codes". UDI/RDI fallback and service modification.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". 3GPP TS 23. Security architecture ".ISDN User Part functional description ".761 (1999): " Signalling System No.087: "User-to-User Signalling (UUS) Supplementary Service. 3GPP TS 23.079: "Support of Optimal Routeing (SOR). ITU-T Recommendation Q. Stage 2 ". 3GPP TS 24. 3GPP TS 33.764 (1999): " Signalling System No. Stage 2".172: "Technical realization of Circuit Switched (CS) multimedia service . Stage 2". 3GPP TS 23.195: "Provision of UE Specific Behaviour Information to Network Entities". 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) . 3GPP TS 29. Stage 2". Stage 2".413: "UTRAN Iu interface RANAP signalling". 7 . 3GPP TS 23.008: "Mobile radio interface Layer 3 specification.Release 10 9 3GPP TS 23. 3GPP TS 23.Stage 2" [31] [32] [33] [34] [35] [36] [37] [38] [39] 3GPP . 3GPP TS 23. 1 and the Signalling System No. Stage 2".081: "Line identification Supplementary Services. Core network protocols. Stage 2" 3GPP TS 23.0 (2011-03) [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [25a] [26] [27] [28] [29] [30] 3GPP TS 23. Stage 2". Stage 2".083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Service.102: "3G Security. Technical realization. ITU-T Recommendation Q.093: "Technical realization of Completion of Calls to Busy Subscriber (CCBS).

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

A basic mobile-to-mobile call is treated as the concatenation of an MO call and an MT call.1 and 4. between the VMSC and the VLR and between the VMSC and the destination exchange. 4.1 Architecture for an MO call A basic mobile originated call involves signalling between the MS and its VMSC via the BSS.Release 10 11 3GPP TS 23.2 show the architecture for handling a basic MO call and a basic MT call. In a given network. the term ISUP is used to denote the telephony signalling system used between exchanges. Radio I/F signalling BSSA Iu or A I/F signalling VMSCA IAM (ISUP) MS SIFOC Complete call VPLMNA VLRA Figure 1: Architecture for a basic mobile originated call In figure 1 and throughout the present document. the term BSS is used to denote a GSM BSS or a UTRAN.018 V10.0 (2011-03) PLMN BC PRN PUESBINE SCUDIF SGSN SIFIC SIFOC SRI TO UDUB UESBI-Iu VLRA VLRB VMSCA VMSCB VPLMNA VPLMNB (GSM or UMTS) PLMN Bearer Capability Provide Roaming Number Provision of User Equipment Specific Behaviour Information to Network Entities Service Change and UDI/RDI Fallback Serving GPRS support node Send Information For Incoming Call Send Information For Outgoing Call Send Routeing Information Trunk Originated User Determined User Busy User Equipment Specific Behaviour Information over the Iu interface 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. In figure 1 and throughout the present document. 3GPP . any telephony signalling system may be used. as appropriate. as indicated in figure 1.1.

as for the mobile originated case. the MS establishes communication with the network using radio interface signalling. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see 3GPP TS 23. HLRB requests a roaming number from VLRB. it requests VMSCB to page the MS. as indicated in figure x.0 (2011-03) When the user of an MS wishes to originate a call. If VLRA determines that the outgoing call is allowed. If VLRB determines that the incoming call is allowed. also using the MAP protocol. it requests routeing information from HLRB using the MAP protocol. 4.060 [9]) and there is an association between VLRB and the SGSN for the MS. When the MS responds.018 V10. and sends a message containing the address of the called party. 3GPP . and VLRB returns a roaming number in the Provide Roaming Number Ack. it responds with a Complete Call. HLRB returns the roaming number to GMSCB in the Send Routeing Info ack. 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.1. containing HLRB. over an internal interface of the MSC/VLR. over an internal interface of the MSC/VLR. it requests information to handle the incoming call (SIFIC) from VLRB. The IPLMN. Communication between VMSCB and the MS is via the BSS. The originating exchange may also be another MSC of the same or different PLMN. 4. When VMSCB receives the IAM. VMSCA: establishes a traffic channel to the MS.3 Architecture for a TO call A basic trunk originated call involves signalling between the PSTN and the PLMN’s MSC. and VMSCB establishes a traffic channel to the MS. is in principle distinct from HPLMNB. VMSCB informs VLRB in the Page ack message. and constructs an ISUP IAM using the called party address and sends it to the destination exchange.2 Architecture for an MT call A basic mobile terminated call involves signalling as indicated in figure 2.Release 10 12 3GPP TS 23. VMSCB pages the MS using radio interface signalling. GMSCB uses the roaming number to construct an ISUP IAM. VLRB instructs VMSCB to connect the call in the Complete call. which it sends to VMSCB. the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS. containing GMSCB. VMSCA requests information to handle the outgoing call (SIFOC) from VLRA. 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.

In a given network.0 (2011-03) The MSC may also be connected to PBX but that is outside the scope of this document. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between BSSA and VMSCA is shown by dashed lines. The MSC analyses the called party number and routes the call to an appropriate destination.102 [32] or the GSM ciphering mechanism defined in 3GPP TS 43. and ISUP signalling between VMSCA and the destination exchange is shown by solid lines. If the called number is a PSTN number then the call is routed to (appropriate) PSTN operator. 3GPP .3. any telephony signalling system may be used.020 [1].018 V10. the terms "security procedures" and "security control" denote the UMTS ciphering and integrity protection mechanism defined in 3GPP TS 33. the term ISUP is used to denote the telephony signalling system used between exchanges. If the MSISDN belongs to another PLMN (or is ported out). the call is routed to another PLMN. The MSC receives a setup (IAM) message from the originating exchange. There may be other destinations also. If the called party number is an MSISDN the gateway MSC functionality is activated. 5. 5 Information flows In this clause and clause 7. Signalling over the radio interface between MSA and BSSA or VMSCA is shown by dotted lines.1. IAM (ISUP/internal) Originating exchange IAM (ISUP) MSC IAM (ISUP) GMSC B/ VMSC B PSTN switch IAM (ISUP) Other PLMN Figure 4.Release 10 13 3GPP TS 23. In the PBX case same modelling applies but the PBX signalling is different to ISUP. many variations are possible. signalling over the B interface between VMSCA and VLRA is shown by chain lines. as appropriate.1 Information flow for an MO call An example information flow for an MO call is shown in figure 3.1: Architecture for a basic trunk originated call In figure x and throughout the present document.

either as part of the procedure to start security procedures or explicitly after security procedures have started.018 V10. the position in this message flow diagram is an example. This option is not available for a UMTS connection [ffs]. NOTE 2: Security procedures may be initiated at any stage after authentication.1. this is not shown in this message flow diagram. and may check the IMEI.0 (2011-03) 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 Complete call Call proceeding Allocate channel Assignment cmd Assignment comp Allocation complete IAM ACM ANM Alert Connect Connect ack NOTE 1: Authentication may occur at any stage during the establishment of an MO call. optionally it may instead send a "start ciphering" request indicating that no ciphering is required. NOTE 4: The network may request the IMEI from the MS. Figure 3: Information flow for a basic mobile originated call 3GPP . the MSC may send a CM service accept towards the MS. its position in this message flow diagram is an example. NOTE 3: If ciphering is not required for a GSM connection.Release 10 14 3GPP TS 23. at any stage during the establishment of an MO call.

to indicate to the calling user that the B subscriber is being alerted.0 (2011-03) When the user wishes to originate a call.Release 10 15 3GPP TS 23. using a Send Info For Outgoing Call (SIFOC) message containing the B subscriber address. If the user originates one or more new MO calls in a multicall configuration. to trigger BSSA and MSA to set up a traffic channel over the radio interface. which relays it to VMSCA. VMSCA sends to VLRA a request for information to handle the outgoing call. MSA sends a CM service request through the existing signalling connection for each new call. VMSCA sends a Call Proceeding message via BSSA to MSA. MSA also uses the Set-up message to indicate the bearer capability required for the call.020 [1] for GSM.102 [32] for UMTS 3GPP TS 43. VMSCA sends a Connect message via BSSA to MSA. it sends a Process Access Request ack to VMSCA. VLRA may also initiate security procedures at this stage.102 [32] for UMTS and 3GPP TS 43. VMSCA constructs an ISUP IAM using the B subscriber address. When the destination exchange returns an ISUP ANswer Message (ANM). It is a network operator option whether to allow an emergency call when the mobile identifies itself by an IMEI. as described in 3GPP TS 33. or security procedures have been successfully initiated. BSSA relays the CM Service Accept to MSA. VLRA may then initiate authentication. The network then waits for the call to be cleared. For an emergency call. it sends a Complete Call message to VMSCA. and sends it to the destination exchange. 3GPP . MSA establishes a signalling connection with BSSA. as described in 3GPP TS 33. to indicate that the call request has been accepted. MSA sends a Set-up message containing the B subscriber address via BSSA to VMSCA. If VMSCA has received a Start security procedures message from VLRA. VMSCA translates this bearer capability into a basic service. If security procedures are not required at this stage.020 [1] for GSM. When MSA has received the CM Service Accept. Details of the handling are shown in clause 7. MSA interprets this in the same way as a CM Service Accept. VMSCA sends a Process Access Request to VLRA.020 [1] for GSM. The Call Proceeding message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be changed. and determines whether an interworking function is required. the Process Access Request ack message triggers a Start security procedures message towards BSSA. otherwise VMSCA sends a CM Service Accept message towards BSSA. If VLRA determines that the call should be connected. it initiates security procedures as described in 3GPP TS 33. VMSCA sends an Alerting message via BSSA to MSA. When the destination exchange returns an ISUP Address Complete Message (ACM). a different CM service type (emergency call) is used. and the mobile may identify itself by an IMEI. If VLRA determines that MSA is allowed service. and sends an Allocate channel message to BSSA.018 V10. when security procedures have been successfully initiated. If BSSA receives a Start security procedures message from VMSCA. When the traffic channel assignment process is complete (indicated by the Allocation complete message from BSSA to VMSCA).102 [32] for UMTS and 3GPP TS 43. to instruct MSA to connect the speech path.1. and sends a Connection Management (CM) service request to BSSA.

and signalling over the radio interface between BSSB and MSB is shown by dotted lines. and over the B interface between VLRB and VMSCB is shown by chain lines. NOTE 3: If an ISUP REL message is received at the GMSC between sending of SRI and receiving of SRI ack. If GMSCB can derive an HLR address from the B party address. it is prepared to wait long enough for the SRI ack to allow pre-paging to be completed). Figure 4: Information flow for retrieval of routeing information for a basic mobile terminated call When GMSCB receives an IAM. paging is initiated after VLRB has accepted the PRN message. VMSCB releases the radio resource allocated for the MT call if the timer expires before the IAM is received.0 (2011-03) 5.e. and when the MAP RELEASE_RESOURCES message is received from the GMSC. NOTE 2: VMSCB starts the timer for the release of radio resources after it sends the Process Access Request message to VLRB. Instead a MAP Release_Resources message may be sent to the VMSC. it sends a request for routeing information (SRI) to HLRB. the GMSC does not send IAM to the VMSC. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines.1. The paging procedure is described in subclause 5. it indicates this by an information element in the SRI message.Release 10 16 3GPP TS 23. it analyses the called party address. and between GMSCB and VMSCB is shown by solid lines.018 V10. ISUP signalling between the originating exchange and GMSCB.3. signalling over the MAP interfaces between GMSCB and HLRB and between HLRB and VLRB. If GMSCB supports pre-paging (i.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. NOTE 1: If pre-paging is used. 3GPP .

This second SRI request leads to obtaining a roaming number from the new MSC towards which the call can then be delivered (possibly after new CAMEL interactions). upon receipt of: an ISUP IAM message which was preceeded by a MAP Cancel Location procedure. the HLR and the old terminating VMSC support the MT Roaming Retry procedure. HLRB sends a request for a roaming number (PRN) to VLRB. In that case.Release 10 17 3GPP TS 23. To support mobile terminating roaming retry with such HLR implemenations. The GMSC shall then release the ISUP connection to the old VMSC. it is prepared to wait long enough for the PRN ack to allow pre-paging to be completed). and HLRB supports pre-paging (i. If Paging Area function is supported in HLRB then HLRB sends the paging area if stored in HLR.116 [24]). VLRB returns the roaming number in the PRN ack. if the GMSC.1.e. and HLRB relays the roaming number to GMSCB in the SRI ack. 5. and retry the terminating call setup towards the new MSC by sending an additional SRI to the HLR. An HLR supporting the "mobile terminating roaming retry" feature shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR. This shall also apply if the HLR and the old VLR support Super-Charger (see 3GPP TS 23. terminate any open CAP dialogue. or a MAP Cancel Location procedure while on-going paging.018 V10.2. the old VMSC shall instruct the GMSC to resume terminating call procedure by sending a MAP Resume Call Handling message.NOTE: HLRs compliant with an earlier release of the specification and supporting mobile terminating roaming retry and Super-Charger may not always send a Cancel Location message in a supercharged network. 3GPP . regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified.0 (2011-03) HLRB decides whether pre-paging is supported according to the following criteria: GMSCB has indicated that it supports pre-paging. the old VLR can start a timer upon receipt of the MAP Send Identification message while on-going paging to trigger the sending of an internal Cancel Location to the old MSC and thus the sending of a MAP Resume Call Handling message by the old MSC to the GMSC after the sending of the MAP Update Location by the new VLR to the HLR. if pre-paging is supported. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC. GMSCB constructs an IAM using the roaming number. it indicates this by an information element in the PRN message. and sends it to VMSCB.1 Mobile Terminating Roaming Retry Call after successful Retrieval of Routeing Information The information flow for mobile terminating roaming retry call after successful retrieval of routeing information is shown in figure 4a.

. New VMSC/VLR may delay setup until location update procedure finishes.8 LocUpdate Accept TMSI Realloc Cmplt Setup Call Confirmed Normal MT call procedure follows.0 (2011-03) GMSC HLR Old VMSC/VLR New VMSC/VLR MS SRI (B. basic call interrogation)5 HLR delays the sending of PRN until location update procedure finishes. roaming retry) 4 REL RLC 2nd SRI (B.018 V10. E.Roaming retry)1 PRN (call ref.g. TMSI reallocation.GMSC@. GMSC@.Release 10 18 3GPP TS 23.call Ref.. ciphering. Roaming retry)2 PRN ACK (MSRN) SRI ACK IAM (MSRN) Paging Update Location Cancel Location3 Cancel Location Ack LocUpdate Authentication Procedure Old MSC stops paging timer and inform GMSC Insert Subscriber Data (multiple) ACK RCH (call reference. 6 Insert Subscriber Data (continued) Update Location Ack PRN PRN ACK (MSRN’)7 2nd SRI ACK (MSRN’)7 IAM (MSRN’) Further procedures related to location update.1. 3GPP .

upon receipt of: a MAP Cancel Location procedure while on-going pre-paging. 2. the GMSC address and the MT Roaming Retry Supported IE in the first SRI sent to the HLR. the incoming IAM may either be handled as a waiting call or forwarded as Busy (CFB). the new SRI shall be sent without the Roaming Retry Supported IE. the new MSC may delay the setup of the call until the completion of the Location Update procedure or start at once the normal terminating call procedure. If "Suppress T-CSI" was included in the SRI request. MAP-SEND-ROUTING-INFOFOR-SM. Receipt of the MT Roaming Retry Supported IE in the PRN indicates that the GMSC supports the Resume Call Handling procedure and the mobile terminating roaming retry feature. sends an RCH message to the GMSC with the MT Roaming Retry IE. if the GMSC and the HLR support the MT Roaming Retry procedure. In the former case. depending on the state of the "follow-on" call and the subscriber's subscription data. 5. the HLR delays the sending of the PRN to the new VLR till completion of the Update Location procedure. 6. The procedure may e. the GMSC address and the MT Roaming Retry Supported IE in the PRN sent to the MSC/VLR if received in the SRI. if any exists. and re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call reference number. or upon receipt of the MAP Cancel Location message while paging. MAP-ANY-TIME-INTERROGATION. If "Suppress T-CSI" was not included in the SRI request. and if it supports the "mobile terminating roaming retry" feature and did receive the MT Roaming Retry Supported IE in the PRN. Similarly. if the Location Update is received with the "follow-on" indication and if the VMSC supports the "follow-on" indication. MAP-SEND-ROUTING-INFO-FOR-LCS. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC. 8.g. the old MSC/VLR stops paging. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number. 4. Receipt of the MSRN' from the new MSC/VLR enables the GMSC to relay the call towards the new MSC/VLR. using TAbandon EDP. the old VMSC/VLR shall return a PRN negative response to the HLR. 5. Upon receipt of the ISUP IAM message which was preceeded by a MAP Cancel Location message. different charging rates or regional service subscription). terminates T-CSI dialog with the SCP. More generally.g.1.0 (2011-03) Figure 4a: Information flow for a mobile terminating roaming retry call after successful Retrieval of Routeing Information 1.2. PSI). If the IAM message is received before the Location Update procedure is completed with the MS. 3. the GMSC shall use an appropriate high value for the timer supervising receipt of SRI ACK. Furthermore. this also applies to all TCAP transactions that the HLR may have to open toward a VLR (e. releases the call towards the old MSC/VLR. apply during prepaging if the GMSC. if paging was on-going. e. Note that the Suppress T-CSI field is not set since the Mobile Terminating procedure is restarted from the beginning including the handling of CAMEL interaction on T-CSI (this is because T-CSI treatments may end differently if old and new MSCs are not in the same PLMN or in the same geographical area. the GMSC acknowledges the RCH message.018 V10. Upon receipt of the RCH message with the MT roaming retry IE. To avoid looping.g.g. USSD. Upon receipt of a SRI request or PRN ack (regardless of the PRN response from the old VLR) during an ongoing Update Location procedure. the HLR shall relay a SRI negative response with the error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC. and the called party is roaming to a different MSC/VLR during the PRN procedure.2 Mobile Terminating Roaming Retry Call during Retrieval of Routeing Information The information flow for mobile terminating roaming retry call during retrieval of routing information is shown in figure 4b. a HLR supporting the "mobile terminating roaming retry" feature should wait for the completion of any ongoing Location Update procedure when processing other terminating requests e.Release 10 19 3GPP TS 23. 7. A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number. HLR and old MSC/VLR support pre-paging. the HLR may either return a SRI negative response with 3GPP . In that case.

e. different charging rates or regional service subscription. the old VLR can start a timer upon receipt of the MAP Send Identification message while on-going paging to trigger the sending of an internal Cancel Location to the old MSC and thus the sending of a PRN negative response to the HLR after the sending of the MAP Update Location by the new VLR to the HLR.018 V10. To support mobile terminating roaming retry with such HLR implementations. or instead delay the sending of a PRN request to the new VLR until completion of the Update Location procedure. 3GPP . This second SRI request leads to obtaining a roaming number from the new MSC towards which the call can then be delivered (possibly after new CAMEL interactions).1. the mobile terminating procedure is restarted from the beginning including the handling of CAMEL interaction on T-CSI. NOTE 2: Legacy HLR implementations supporting mobile terminating roaming retry and Super-Charger may not always send a Cancel Location message in a supercharged network.0 (2011-03) the error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC. This shall also apply if the HLR and the old VLR support Super-Charger (see 3GPP TS 23. An HLR supporting the "mobile terminating roaming retry" feature shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR.Release 10 20 3GPP TS 23. NOTE 1: If "Suppress T-CSI" was included in the SRI request.116 [24]). regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. because T-CSI treatments can end differently if old and new MSCs are not in the same PLMN or in the same geographical area. The GMSC shall release the T-CSI dialogue (if existing) and retry the terminating call setup towards the new MSC by sending an additional SRI to the HLR when receiving a SRI negative response with the error "absent subscriber" including the reason "mtRoamingRetry".g.

A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number.Release 10 21 3GPP TS 23.018 V10. the GMSC address.1.0 (2011-03) Figure 4b: Information flow for a mobile terminating roaming retry call during Retrieval of Routeing Information 1. The Pre-paging Supported IE is included in the SRI message if the GSMC supports the "Pre-paging" feature. and the MT Roaming Retry Supported IE in the first SRI sent to the HLR. 3GPP .

the old MSC/VLR stops pre-paging and sends a PRN negative response message to the HLR.0 (2011-03) 2. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC. The new terminating VLR shall include an MTRF Supported flag in the MAP Update Location message sent to the HLR. MAP-SEND-ROUTING-INFOFOR-SM.g. Similarly. USSD. the HLR returns a SRI negative response with error "absent subscriber" including the reason "mtRoamingRetry" to the GMSC. If the HLR authorises the MTRF call between the old and the new terminating MSCs. Upon receipt of the SRI negative response with error "absent subscriber" including the reason "mtRoamingRetry".2. An HLR supporting the "mobile terminating roaming forwarding" feature shall always send a MAP Cancel Location message message to the old VLR upon receipt of the MAP Update Location from the new VLR. the HLR shall include the MTRF Supported And Authorized flag and the new MSC/VLR numbers in the MAP Cancel Location message sent to the old VLR. the Pre-paging Supported IE is included in the PRN message. the MAP Cancel Location message does not include the MTRF Supported And Not Authorized flag and the old VLR has received the MTRF Supported flag earlier in the MAP Send Indentification message.3 Mobile Terminating Roaming Forwarding Call after successful Retrieval of Routeing Information The information flow for mobile terminating roaming forwarding (MTRF) call after successful retrieval of routeing information is shown in figure 4c. The HLR should also support the Mobile Terminating Roaming Forwarding procedure in order to ensure that roaming forwarding can be offered in all scenarios (e. As deployment scenarios may exist where the home network (HLR) has not been updated to support MTRF the visited network can perform a limited roaming forwarding solution autonomously if the MTRF Supported flag is signalled in the MAP Send Identification message under the conditions defined in this clause. The new terminating 3GPP . if either of the following is true: the MAP Cancel Location message includes the MTRF Supported And Authorized flag or. Otherwise if the HLR disallows the MTRF call between the old and the new terminating MSCs. If GMSC and HLR support the "Prepaging" feature. the HLR shall include the MTRF Supported And Not Authorized flag in the MAP Cancel Location message sent to the old VLR. MAP-SEND-ROUTING-INFO-FOR-LCS. More generally. MAP-ANY-TIME-INTERROGATION.1.116 [24]). a HLR supporting the "mobile terminating roaming retry" feature should wait for the completion of any ongoing Location Update procedure when processing other terminating requests e. 5. 4. If the old VLR receives a MAP Send Identification message containing the MTRF Supported flag it shall not trigger any MAP Provide Roaming Number request to the new terminating VLR until is has received the MAP Cancel Location message. This shall also apply if the HLR and the old VLR support Super-Charger (see 3GPP TS 23. Upon receipt of the MAP Cancel Location message while pre-paging. the old VLR shall send a MAP Provide Roaming Number request (including the MTRF Indicator and the parameters received from the HLR in the MAP Provide Roaming Number) to the new terminating VLR. NOTE: The full support of MTRF for roaming scenarios requires both home network (HLR) and visited network (VLRs) to support the MTRF procedures and protocol extensions. If meanwhile the HLR has received a new Update Location procedure from a new MSC/VLR. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number and the GMSC address in the PRN sent to the MSC/VLR if received in the SRI. Upon receipt of a MAP Cancel Location message while ongoing paging.018 V10. if the old and the new terminating MSC/VLRs support the MT Roaming Forwarding procedure. regardless of whether the new VLR indicates or not during the location update procedure that the previous network entity must be notified. the GMSC re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call reference number. See the same procedures from step 5 to step 8 in the figure 4a.g. 3.-8. The new VLR may also signal the MTRF Supported flag and the new MSC/VLR numbers in the MAP Send Identification message to indicate to the old VLR that it supports MTRF. 5.Release 10 22 3GPP TS 23. in case of IMSI in the LAU Request from UE). this also applies to all TCAP transactions that the HLR may have to open toward a VLR (e.g. PSI).

3GPP .018 V10.1.Release 10 23 3GPP TS 23.0 (2011-03) MSC/VLR shall then allocate an MSRN to allow the call to be routed from the old MSC to the new MSC and send it to the old VLR within the MAP Provide Roaming Number response.

Location Update IAM (MSRN) 10. If HLR authorises MTRF then use new MSC/VLR numbers to trigger sending of PRN Req 6. TMSI reallocation. PRN (MTRF Indicator.Release 10 24 3GPP TS 23. Old MSC number) Insert Subscriber Data (continued) Update Location Ack 7. IMEI checking. Update Location (MTRF Supported) 3.g. 3GPP .0 (2011-03) GMSC SRI (B) HLR Old MSC/VLR New MSC/VLR MS PRN SRI ACK PRN ACK (MSRN) Paging 1.018 V10. Location Update Accept TMSI Realloc Cmplt Setup Call Confirmed Normal MT call procedure follows. PRN ACK (MSRN’) 9. Send Identification (MTRF Supported. IAM (MSRN’) Further procedures related to location update. new MSC/VLR numbers ) Authentication Procedure 2. New VMSC/VLR delays setup until location update procedure finishes. the new VLR returns MSRN’ to the old VLR.1. New MSC/VLR numbers) Cancel Location Ack 4. Cancel Location (MTRF Supported And Authorized. ciphering. E. Old MSC stops paging timer Insert Subscriber Data (multiple) 5. After Update Location Ack is received. 8.

1. the HLR includes the MTRF Supported And Not Authorized flag in the MAP Cancel Location message sent to the old VLR. 3. it sends a MAP Provide Roaming Number request (including the MTRF Indicator and the parameters received from the HLR in the MAP Provide Roaming Number) to the new terminating VLR. the old MSC/VLR stops any on-going Camel transaction.1. Upon receipt of a MAP Cancel Location message while on-going paging and if it includes the MTRF Supported And Authorized flag or if the MAP Cancel Location message does include neither the MTRF Supported And Authorized flag nor the MTRF Supported And Not Authorized flag but the old MSC/VLR had received earlier the MTRF Supported flag at step 1.Release 10 25 3GPP TS 23. If the the MAP Cancel Location message does not include the MTRF Supported And Authorized flag and it did not receive the MTRF Supported flag at step 1 or if the MAP Cancel Location message includes the MTRF Supported And Not Authorized flag. not after the old VLR restart). 4. The new VLR may not include the MTRF Supported flag in the MAP Send Identification message sent to the old VMSC if the Location Update message received from the MS indicates a CS fallback mobile originating call. If it supports MTRF and decides to apply MTRF based on local operator policy and optionally roaming agreements with the HLR and new MSC for MTRF.0 (2011-03) Figure 4c: Information flow for a mobile terminating roaming forwarding call after successful Retrieval of Routeing Information The sequence follows the normal MT terminating call with the following differences: 1. 7. 3GPP . the new MSC/VLR may check roaming agreements with the HLR and the old MSC for MTRF. Receipt of the MSRN from the new MSC/VLR enables the old MSC to relay the call towards the new MSC. the new MSC/VLR allocates an MSRN to allow the call to be routed from the old MSC to the new MSC. Upon receipt of the MAP Provide Roaming Number Request. The new MSC/VLR may reject the MAP Provide Roaming Number Request with a cause indicating that the subscriber is busy if it has received from the MS a CM Service Request indicating a CS mobile originated call. Upon receipt of a MAP Update Location including the MTRF Supported flag. the new MSC/VLR may allocate an MSRN before completion of the MAP Update Location procedure with the HLR. the new VLR returns a negative response to the old VLR. and if the conditions for using these procedures are met. the MSC can decide based on operator policy which procedure to follow. The new MSC/VLR sends MSRN to the old VLR within the MAP Provide Roaming Number response. the HLR includes the MTRF Supported And Authorized flag and the new MSC/VLR numbers in the MAP Cancel Location message sent to the old VLR. If the Location Update Request contains the "CSMT" flag set and a valid TMSI/old LAI (e. 8.2. If the old MSC supports both the MT Roaming Retry and the MT Roaming Forwarding procedures. 5. The new VLR may not include the MTRF Supported flag in the MAP Update Location message sent to the HLR if the Location Update message received from the MS indicates a CS fallback mobile originating call. Upon receipt of the MSRN from the new MSC/VLR. a new MSC/VLR supporting the MTRF feature may include the MTRF Supported flag and the new MSC/VLR numbers in the MAP Send Identification to the old VMSC. As an implementation option. If MTRF is authorised.018 V10. If the new VLR accepts the MAP Provide Roaming Number request. A new MSC/VLR supporting the MTRF feature includes the MTRF Supported flag in the MAP Update Location message sent to the HLR. 2. the old MSC/VLR may initiate the MT Roaming Retry procedure as per subclause 5. If MTRF is not authorised. upon successful completion of the MAP Update Location procedure with the HLR. an HLR supporting the MTRF feature decides whether to authorise MTRF call between the old and the new MSCs based on roaming agreements with the old and the new MSCs.g. If the new VLR rejects the MTRF request. the old MSC/VLR stops paging. 6. 9.

1. The MAP Update Location message and Send Identification message. The Location Update Accept message may be sent to the MS at any time after receipt of the MAP Update Location Ack from the HLR. is present in those messages. the incoming IAM may either be handled as a waiting call or forwarded as Busy (CFB).0 (2011-03) 10. depending on the state of the "follow-on" call and the subscriber's subscription data. signalling over the B interface between VMSCB and VLRB is shown by chain lines. the new MSC may delay the setup of the call until the completion of the Location Update procedure or start at once the normal terminating call procedure. 5. and the MAP Cancel Location message may include the new LMSI allocated by the new terminating MSC/VLR if respectively the MTRF Supported flag. i. ISUP signalling between GMSCB and VMSCB is shown by solid lines. the old VLR shall include the new LMSI in the MAP Provide Roaming Number message it sends to the new VLR. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines. the location update procedure with the MS is not affected by the MT Roaming Forwarding procedure. In the former case. If the IAM message is received before the Location Update procedure is completed with the MS.e. if the Location Update is received with the "follow-on" indication and if the MSC supports the "follow-on" indication. or the MTRF Supported And Authorized flag. If available.018 V10. and signalling over the radio interface between VMSCB or BSSB and MSB is shown by dotted lines.3 Information flow for an MT call An example information flow for an MT call is shown in figure 5. many variations are possible. 3GPP .Release 10 26 3GPP TS 23.

NOTE 4: The network may request the IMEI from the MS.1. NOTE 3: This message flow diagram assumes that the MS has already been authenticated on location registration. either as part of the procedure to start security procedures or explicitly after security procedures have been started. NOTE 6: If a connection between MSCB and MSB has been established as a result of pre-paging. at any stage after the MS responds to paging. this is not shown in this message flow diagram. If this is not so (for the first MT call after VLR restoration).018 V10. the network may initiate authentication after the MS responds to paging. VLRB sends the Call arrived message to MSCB to stop the guard timer for the release of the radio connection. the MSC may send a Start security procedures message indicating that no ciphering is required. and may check the IMEI. Figure 5: Information flow for a basic mobile terminated call 3GPP . NOTE 5: If a connection between MSCB and MSB has been established as a result of pre-paging. NOTE 2: If Security procedures are not required. the paging procedure is not performed.Release 10 27 3GPP TS 23. the position in this message flow diagram is an example.0 (2011-03) GMSCB IAM VLRB VMSCB BSSB MSB SIFIC Page MS Page Page Chan req Imm ass Page resp Process access req Start security proc (note 1) Process access req ack MS conn estab 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 ACM ANM Complete call ack Connect ack NOTE 1: Security procedures may be initiated at any stage after the network has accepted the page response.

When the called user answers. VMSCB: responds with a Connect ack message towards MSB. VMSCB sends a Process access request message to VLRB to indicate that MSB has responded to paging. MSB then sends a page response on the signalling channel. When VMSCB receives the Call confirmed message via BSSB. BSSB instructs MSB to tune to a traffic channel by sending an Assignment command. each supplementary service which a network entity supports is managed by a supplementary service handler. The call handling processes defined in the present document use the data to define the contents of messages to other entities. If a network entity does not support a supplementary service.1. If VPLMNB supports GPRS and the Gs interface between VLRB and the SGSN is implemented (see 3GPP TS 23. 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. The Process access request ack message triggers a Start security procedures message towards BSSB. 3GPP . which responds with an immediate assignment command. If MSB detects the page. If VLRB recognizes the roaming number. When MSB receives the Set-up message from BSSB. as described in 3GPP TS 33. VMSCB sends a page request to BSSB. Descriptions may be found in the stage 2 specifications for each supplementary service. as described in 3GPP TS 33. it responds with a Call confirmed message. it sends a request to VMSCB to page MSB. and BSSB broadcasts the page on the paging channel. 6 Principles for interactions with supplementary services This clause specifies the principles used to describe the invocation of the GSM or UMTS supplementary services which were standardized when the present document was drafted.018 V10. to instruct MSB to use the specified signalling channel. VLRB then sends a Complete call message to VMSCB. it sends an Allocate channel message to BSSB. sends a Complete call ack to VLRB. which handles data in the entity in which it runs.102 [32] for UMTS and 3GPP TS 43. which relays it to the originating exchange.102 [32] for UMTS and 3GPP TS 43. BSSB relays this to VMSCB. which BSSB relays to VMSCB. sends an ANM to GMSCB. VLRB may then initiate authentication. VMSCB sends a Set-up message towards MSB. they are therefore outside the scope of the present document. The network then waits for the call to be cleared. which relays it to the originating exchange. it bypasses the interaction with the handler for that supplementary service. The Set-up message may include bearer capability information for the call.060 [9]) and there is a valid association between VLRB and the SGSN for the MS. which BSSB relays to VMSCB as an Allocation complete.020 [1] for GSM. VMSCB sends an ACM to GMSCB. Registration. deactivation and interrogation are call-independent operations. if VMSCB has not received a Start security procedures message from VLRB. In the modelling used in the present document. If VLRB determines that MSB is allowed service. and sends an Alerting message to indicate that the called user is being alerted. and MSB is allowed service. erasure.Release 10 28 3GPP TS 23. the paging signal towards the MS goes from VMSCB via VLRB and the SGSN to the BSS. If a radio connection between the network and MSB is already established. message. VLRB may also initiate security procedures at this stage. using a Send Info For Incoming Call (SIFIC) message containing the roaming number received in the IAM. it sends a Process access request ack to VMSCB. If no radio connection exists. VMSCB responds immediately to the page request. the Start security procedures message indicates no ciphering.0 (2011-03) When VMSCB receives an IAM from GMSCB it sends to VLRB a request for information to handle the incoming call. activation. it sends a channel request to BSSB. The Call Confirmed message includes bearer capability information if any of the negotiable parameters of the bearer capability has to be changed.020 [1] for GSM. Exceptions to this general principle are described later in this clause. MSB sends a Connect message. When MSB has tuned to the specified traffic channel it responds with an Assignment complete.

3GPP .082) 6.1.2. The basic call handling processes MT_GMSC and ICH_MSC interact with the process COLP_MAF039 (3GPP TS 23.2 Call Forwarding on mobile subscriber Busy (CFB) The basic call handling process ICH_VLR interacts with the process MAF008 (3GPP TS 23.081 [14]) as described in subclauses 7.1.3.082 [15]) as described in subclause 7.1 and 7.2.3.081 [14]) as described in subclauses 7.081 [14]) as described in subclauses 7.1 and 7. 6.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.1.2.082 [15]) as described in subclause 7. 6.3.3.3 Call forwarding services (3GPP TS 23.072 [11]) as described in subclauses 7.1.2. 6.081 [14]) as described in subclauses 7.072) The basic call handling processes ICH_MSC and ICH_VLR interact with the CD supplementary service (3GPP TS 23.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.2. 6.1.2.2.3. 6. 6.2.3.1.2 and 7.2. 6.3.3.1.082 [15]) as described in subclauses 7.3.2 respectively.081) 6.3.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) The basic call handling processes SRI_HLR and ICH_VLR interact with the process MAF010 (3GPP TS 23.1 Call Deflection service (3GPP TS 23.1 Call Forwarding Unconditional (CFU) The basic call handling process SRI_HLR interacts with the process MAF007(3GPP TS 23.2.2 Line identification services (3GPP TS 23.018 V10.081 [14]) as described in subclauses 7.3.2.1 and 7.1 and 7.2.3.2.3 Call Forwarding on No Reply (CFNRy) The basic call handling process ICH_VLR interacts with the process MAF009 (3GPP TS 23.3.082 [15]) as described in subclause 7.1 and 7.0 (2011-03) 6.1 Calling Line Identification Presentation (CLIP) The basic call handling processes ICH_VLR and ICH_MSC interact with the processes CLIP_MAF001 and CLIP_MAF002 (3GPP TS 23. 6.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.2 and 7.Release 10 29 3GPP TS 23.3.2.

085 [18]) as described in subclause 7.1 and 7.3. The basic call handling process SRI_HLR interacts with the process CUG_MAF015 (3GPP TS 23.7 Closed user group (3GPP TS 23.6.2.1.10 Call barring (3GPP TS 23.2.4 Call wait (3GPP TS 23.085 [18]) as described in subclause 7.085) The basic call handling process OCH_VLR interacts with the process CUG_MAF014 (3GPP TS 23.083) The basic call handling process ICH_VLR interacts with the process MAF013 (3GPP TS 23. 7.10.1. 6.Release 10 30 3GPP TS 23. The basic call handling processes OCH_MSC and ICH_MSC interact with the procedures Process_Hold_Request and Process_Retrieve_Request as described in subclauses 7.2.3.086) The interactions between Advice of Charge (3GPP TS 23.1.088) 6.018 V10.1.1. The interactions between call forwarding and CUG (3GPP TS 23.2.2 Barring of incoming calls The basic call handling process SRI_HLR interacts with the processes MAF022 and MAF023 (3GPP TS 23.1.9 User-to-user signalling (3GPP TS 23.3.6 Multiparty (3GPP TS 23.3.2.5 Call hold (3GPP TS 23.2.2. The interactions between Advice of Charge (3GPP TS 23.2.1 and 7. OCH_VLR.2.1.3.2.087) The basic call handling processes OCH_MSC.0 (2011-03) 6.1 and 7. 3GPP . 6.083) Invocation of call hold before a basic call has been established will be rejected.1.084) Invocation of multiparty before a basic call has been established will be rejected.083 [16]) as described in subclause 7.088 [21]) as described in subclause 7.2.1. 6. 6. MT_GMSC and ICH_MSC interact with the UUS supplementary service as described in subclauses 7.2.3.086 [19]) and MO calls are handled as described in subclauses 7.1 and 7.3.8 Advice of charge (3GPP TS 23.1.085 [18]) are handled as described in subclause 7. 6.1 respectively. 6. Further details of the handling of call waiting are given in subclauses 7.1 and 7.2.088 [21]) as described in subclause 7. 6. 7.2.086 [19]) and MT calls are handled as described in subclauses 7. MAF018 and MAF020 (3GPP TS 23.1 Barring of outgoing calls The basic call handling process OCH_VLR interacts with the processes MAF017.10.

If a supervision timer expires before a distant entity responds to a signal. SRI_HLR. Telephony signalling interfaces. Q.1. which is specified in 3GPP TS 48.2.2respectively. 7. D & F interfaces is MAP. other telephony signalling systems may be used instead.1 and 7. used to interwork between an MSC and another exchange. OCH_VLR. which is specified in ITU-T Recommendations Q. which is specified in 3GPP TS 29.0 (2011-03) 6.e.135) The basic call handling processes OCH_MSC. VLR & HLR (D) and MSC & EIR (F). for interworking with the BSS and DTAP. The protocols used over the A interface are BSSMAP. 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. In general.13 Multicall (3GPP TS 23. 7.008 [2]. 7.3. for interworking with the MS.413 [27]. An MSC which receives an IAM from an originating exchange may react in three different ways: It acts as a transit exchange. 6. Where a timer is shown in the present document.1. The protocol used over the C. The entities described in this clause interwork with other entities over four different types of interface: The Iu interface. 7 Functional requirements of network entities The text in this clause is a supplement to the definition in the SDL diagrams. 7.2.3. 6. The protocols used over the Iu interface are RANAP.11 Explicit Call Transfer (3GPP TS 23.1. for interworking with the MS. i. it attempts to connect the call to an MS currently registered in the service area of the MSC.1. The present document shows the call handling application processes interworking with a protocol handler for each of the protocols listed above.008 [26]. The C.002 [29].2.1.008 [26].763 [35] and Q. 7. used to interwork between the MSC & HLR (C).018 V10.1. i.093) The basic call handling processes OCH_MSC.2.2. D & F interfaces. it relays the IAM to a destination exchange determined by analysis of the called party address.091) There is no interaction between Explicit Call Transfer and the basic call handling described in the present document.1. OCH_VLR.2respectively.1 and 7. ICH_MSC & ICH_VLR interact with the Multicall supplementary service as described in subclauses subclauses 7. 7.3. It acts as a terminating exchange. This behaviour is not specific to UMTS or GSM. which is specified in 3GPP TS 24. the protocol used over telephony signalling interfaces is ISUP. the protocol handler reports timer expiry to the application as an error condition or negative response. used to interwork between the MSC and the UTRAN or the UMTS UE. for interworking with the UTRAN and DTAP. which is specified in 3GPP TS 25. which is specified in 3GPP TS 24.762 [34].2.764 [36]. therefore. and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. - 3GPP . Each protocol defines supervision timers.e. 7. Q. it is an application timer rather than a protocol timer.1.761[33].3.12 Completion of Calls to Busy Subscriber (3GPP TS 23. ICH_MSC and ICH_VLR interact with the CCBS supplementary service as described in subclauses 7. For the purposes of the present document.3. it does not duplicate the information in the SDL diagrams. The A interface. MT_GMSC.Release 10 31 3GPP TS 23. the handling is as defined in the appropriate protocol specification. PRN_VLR. used to interwork between the MSC and the GSM BSS or the GSM MS.

CCBS_OCH_Report_Failure. MS connected and Reconnect are global data.e. Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC. Sheet 1: the variable UUS1 result sent is specific to UUS. sheet 3: At any stage.010 [31]. If the MSC does not support PUESBINE. the MS may terminate the transaction with the network by sending a CM service abort message. the text associated with each SDL diagram specifies the handling which applies if the entity does not support an optional feature or service. accessible to the procedure Establish_Originating_TCH_If_Required. sheet 3: if the VMSC receives a Set-up message from the MS while the access request is being handled.1.001 [28]. For simplicity of description. it is specified in 3GPP TS 23. it is assumed that support for Operator Determined Barring and the Call Forwarding and Call Barring supplementary services is mandatory. or (for GSM only) no ciphering.1. the VMSC may encapsulate the request for the IMEI in the Start security procedures message. it is specified in 3GPP TS 23.1 Functional requirements of serving MSC 7. Send_Alerting_If_Required and Send_Access_Connect_If_Required. the procedure call is omitted if the entity does not support an optional feature or service.1. this signal will not be received.1 MO call 7.078 [12].1. which it sends to a destination exchange determined by analysis of the routeing information from the HLR. 7. CCBS_OCH_Report_Success. Sheet 1: the procedure CAMEL_N_CSI_CHECK_MSC is specific to CAMEL Phase 3 or later. Sheet 1: the VMSC converts the PLMN bearer capability negotiated between the VMSC and the MS to a basic service according to the rules defined in 3GPP TS 27. 7.1. 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. Sheet 2. the message is saved for processing after the access request has been handled.018 V10. the BSS relays the response in the Security procedures complete message to the MSC. 3GPP .093 [23]. If the handling consists only of a call to a procedure specific to the feature or service. Sheet 2: The Start security procedures message may indicate one of several ciphering algorithms.1.1 Process OCH_MSC The variable TCH allocated is global data.Release 10 32 3GPP TS 23.3 Procedure OG_Call_Setup_MSC Sheet 1: the variables Alerting sent. Sheet 1: the procedure UUS_OCH_Check_Setup is specific to UUS. it interrogates an HLR for information to route the call.195 [25a].2 Procedure Process_Access_Request_MSC Sheet 1: the processing starting with the input signal "Send UESBI-Iu to Access Network" is specific to PUESBINE. 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. Annex A describes the method which the MSC uses to decide how to process the IAM. If the handling consists of more than a call to a procedure specific to the feature or service. i. The procedures CCBS_Report_Not_Idle and CCBS_Check_Last_Call are specific to CCBS.0 (2011-03) - It acts as a GMSC. accessible to the procedures CCBS_Check_OG_Call. 7. they are specified in 3GPP TS 23. Sheet 2.1. If the HLR returns routeing information.1. Sheet 1: the task "Convert IMEISV to UESBI" is defined in 3GPP TS 23. CCBS_Check_If_CCBS_Possible.087 [20]. This variable is accessible to all UUS specific procedures.

Sheet 1: the variable "On_Hold" is used only if the VMSC supports Call Hold. Sheet 3: the procedure CCBS_Check_OG_Call is specific to CCBS. Sheet 5: the procedure Set_COLP_Info_MSC is specific to COLP. sheet 6. sheet 3. Sheet 4: the task "UTU2Cnt := 0" is executed only if the VMSC supports UUS Sheet 4: the procedure CAMEL_OCH_MSC_ALERTING is specific to CAMEL phase 4 or later. sheet 8. If the VMSC does not support CAMEL phase 4 or later. The task "Store CCBS Result" is executed only if the VMSC supports CCBS. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?". it is specified in 3GPP TS 23. 3GPP .0 (2011-03) Sheet 1: the procedure Check_OG_Multicall_MSC is specific to Multicall. sheet 6: the procedure CCBS_OCH_Report_Failure is specific to CCBS. If the VMSC does not support Multicall.4. sheet 7.093 [23]. the MS may terminate the transaction with the network by sending a Release transaction request. 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. processing continues from the "Yes" exit of the test "Result=Pass?". processing continues from the "CCBS Not Possible" exit of the test "CCBS Result". Sheet 3: the procedure CAMEL_MO_Dialled_Services is specific to CAMEL phase 3 or later. sheet 6.093 [23].1.078 [12]. If the VMSC does not support CCBS. Sheet 1. processing continues from the "Pass" exit of the test "Result?". Sheet 3: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability.078 [12]. it is specified in 3GPP TS 23. Sheet 4. they are specified in 3GPP TS 23.078 [12]. it is specified in 3GPP TS 23.093 [23]. Sheet 5: the procedure CAMEL_OCH_MSC_ANSWER is specific to CAMEL.078 [12]. it is specified in 3GPP TS 23.066 [10]. sheet 2.093 [23]. Sheet 3: the procedure CAMEL_OCH_MSC_INIT is specific to CAMEL. sheet 7. If the VMSC does not support CLIR. Sheet 3: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later. If the VMSC does not support CAMEL.078 [12]. Sheet 3: the procedure CCBS_OCH_Report_Success is specific to CCBS. Sheet 1.018 V10. it is specified in 3GPP TS 23. If the VMSC does not support CCBS. sheet 5. sheet 4. it is specified in 3GPP TS 23. sheet 9: at any stage after the Set-up has been received. Sheet 3.078 [12]. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Call allowed?". Sheet 3: the procedure Set_CLI_Presentation_Indicator_MSC is specific to CLIR. Sheet 3: the procedure UUS_OCH_Set_Info_In_IAM is specific to UUS. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.078 [12].087 [20]. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL. sheet 5: the procedure CAMEL_OCH_LEG1_MSC is specific to CAMEL phase 4 or later. Sheet 5: The process CAMEL_OCH_LEG2_MSC is specific to CAMEL phase 4 or later. processing continues from the "Pass" exit of the test "Result?".135 [25]. processing continues from the "Yes" exit of the test "Result=Pass?". sheet 7: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later. sheet 3. processing continues from the "Yes" exit of the test "Result=Pass?".Release 10 33 3GPP TS 23. Sheet 2. sheet 2. Sheet 6: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS.078 [12]. Sheet 5: the procedure Handle_AoC_MO_MSC is specific to AoC. they are specified in 3GPP TS 23. sheet 9: signals are sent to and received from the process Subs_FSM as described in subclause 7.

and will occur only if the VMSC supports CAMEL phase 2 or later. Sheet 10: the procedure Process_Hold_Request is specific to Call Hold.1. Sheet 6.018 V10. processing continues from the "No" exit of the test "Result=CAMEL handling?".087 [20].078 [12].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. it is specified in 3GPP TS 23.078 [12]. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.078 [12].087 [20].Release 10 34 3GPP TS 23.078 [12].078 [12].1. If a CC connection has not been established. If the VMSC does not support CAMEL. it is specified in 3GPP TS 23. 3GPP . sheet 7: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL Phase 1. otherwise it uses a Release. The MS may terminate the transaction with the network while the VMSC is waiting for the MS to return its IMEI. it is specified in 3GPP TS 23. sheet 6: the procedure CAMEL_OCH_MSC1 is 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. Sheet 8: the input signal User To User is specific to UUS. Sheet 9: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL. 7. it is discarded if the VMSC does not support UUS. Release Complete or Disconnect.1. Sheet 7.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 9: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS. otherwise it uses a Release. 7. Sheet 6. Release Complete or Disconnect. processing continues from the "No" exit of the test "Result=Reconnect?". The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.078 [12].6 Procedure Obtain_IMEI_MSC The Send IMEI request to the MS specifies the IMEISV as the requested identity. Sheet 6. processing continues from the "No" exit of the test "Result=CAMEL handling?". the MS uses CM Service Abort. it is specified in 3GPP TS 23. If a CC connection has not been established.0 (2011-03) Sheet 6. Sheet 9: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL. Release Complete or Disconnect.1. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.1. it is specified in 3GPP TS 23.083[16].1.1.1. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 2 or later. it is specified in 3GPP TS 23. the MS uses CM Service Abort. Release Complete or Disconnect. they are specified in 3GPP TS 23. Sheet 10: the procedure Process_Retrieve_request is specific to Call Hold. If a CC connection has not been established. If a CC connection has not been established. otherwise it uses a Release.083[16]. it is specified in 3GPP TS 23. otherwise it uses a Release. sheet 9: the processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL. Sheet 8: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. the MS uses CM Service Abort. 7. the MS uses CM Service Abort. sheet 7: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later. sheet 7. If the VMSC does not support CAMEL.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. it is specified in 3GPP TS 23.1. 7. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process.

7.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.1. The procedures UUS_MSC_Check_UUS1_UUI and UUS_OCH_Set_Alert_And_Connect_Param are specific to UUS. otherwise it uses a Release.087 [20]. If no useful information would be carried in the Facility message.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. If no useful information would be carried in the Progress message.087 [20].Release 10 35 3GPP TS 23. 7.1. If a CC connection has not been established. processing continues from the "No" exit of the test "Acknowledgement required".1.12 Procedure Send_Access_Connect_If_Required The test "Acknowledgement required" refers to the result returned by the procedure Handle_AoC_MSC.1.1. The message is saved for processing after return from the procedure.1. it is specified in 3GPP TS 23.1.1.1. If the VMSC does not support AoC.10 Procedure Send_Alerting_If_Required The test "Backward call indicator=no indication" refers to the called party's status field in the backward call indicators parameter of the ISUP Address Complete message which triggered the call of the procedure Send_Alerting_If_Required. The message is saved for processing after return from the procedure. it is not sent. processing continues from the "Yes" exit of the test "Result=Pass?".018 V10.8 7. If the VMSC does not support UUS. they are specified in 3GPP TS 23.11 Procedure Set_COLP_Info_MSC The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process COLP_MAF006. The VMSC aborts the transaction with the VLR and returns an aborted result to the parent process. If the VMSC does not support UUS.1. The procedure UUS_OCH_Set_Alert_And_Connect_Param is specific to UUS.1. 7. the MS uses CM Service Abort.1. 7. Release Complete or Disconnect. 7. 3GPP .0 (2011-03) The MS may terminate the transaction with the network while the VMSC is waiting for the result of the IMEI check from the EIR.1. it is not sent. processing continues from the "Yes" exit of the test "Result=Pass?".

14 Procedure TCH_Check OCH_MSC1(1) Process OCH_MSC Process in the MSC to handle an outgoing call request Signals from the left are from the BSS Idle CM service request Process_ Access_ Request_MSC No Result= Pass? Yes Wait_For_ Setup Setup CM Service Abort See TS 23.1.0 (2011-03) 7.Release 10 36 3GPP TS 23.1.018 V10.093 CCBS_Report_ Not_Idle TCH allocated:= False OG_Call_ Setup_MSC See TS 23.093 CCBS_Check_ Last_Call Release call resources Idle Figure 6: Process OCH_MSC 3GPP .1.

195 No Abort Result= Pass? Yes Result:= Fail Result:= Fail UESBI-Iu Wait_For_ PAR_Result Wait_For_ PAR_Result Wait_For_ PAR_Result Figure 7a: Procedure Process_Access_Request_MSC (sheet 1) 3GPP . Process Access Request Wait_For_ PAR_Result Provide IMSI Authenticate Trace Subscriber Activity Obtain_IMSI_ MSC Authenticate_ MSC Tracing Active:= TRUE No Result= Pass? Yes No Result= Pass? Yes Result:= Fail Result:= Fail Wait_For_ PAR_Result Wait_For_ PAR_Result Wait_For_ PAR_Result Wait_For_ PAR_Result CM service abort Start security procedures Provide IMEI Send UESBI-Iu to Access Network Ciphering Required:= True Obtain_IMSI_ MSC Convert IMEISV to UESBI-Iu See 3GPP TS 23.0 (2011-03) Procedure Process_Access_Request_MSC Procedure in the MSC to handle a request from the MS for system access PAR_MSC1(3) Signals to/from the left are to/from the BSS.1.018 V10.Release 10 37 3GPP TS 23. signals to/from the right are to/from the VLR.

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

Release 10 39 3GPP TS 23. signals to/from the right are to/from the VLR. CM service abort Setup Abort TMSI Reallocation Failure TMSI Reallocation Complete Abort Forward New TMSI negative response Forward New TMSI ack Result:= Fail Result:= Fail Result:= Pass Figure 7c: Procedure Process_Access_Request_MSC (sheet 3) 3GPP .018 V10.0 (2011-03) Procedure Process_Access_Request_MSC Procedure in the MSC to handle a request from the MS for system access Wait_For_ TMSI_Ack PAR_MSC3(3) Signals to/from the left are to/from the BSS.1.

018 V10.093 Wait_For_ MO_Call_ Result Figure 8a: Procedure OG_Call_Setup_MSC (sheet 1) 3GPP .135 No Result= Pass? Yes Release transaction Send Info For Outgoing Call CCBS_OCH_ Report_Failure See TS 23.1.Release 10 40 3GPP TS 23.087 Convert PLMN BC to basic service CAMEL_N_CSI_ CHECK_MSC See TS 23.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS OCS_MSC1(11) Alerting sent:=False Backward call indicator:=No indication MS connected:=False Reconnect:=False UUS1 result sent:=False On_Hold=False CAMEL_invocation:=False UUS_OCH_ Check_ Setup See TS 23.078 Check_OG_ Multicall_MSC See TS 23.

1.093 1 Figure 8b: Procedure OG_Call_Setup _MSC (sheet 2) 3GPP .018 V10.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_ MO_Call_ Result OCS_MSC2(11) Release transaction Complete Call Send Info For Outgoing Call negative response Convert PLMN BC to channel requirement Abort Call Proceeding Release transaction Establish_ Originating_ TCH_If_ Required No Result= Pass? Yes See TS 23.Release 10 41 3GPP TS 23.093 CCBS_OCH_ Report_Failure CCBS_OCH_ Report_Failure See TS 23.

Release 10 42 3GPP TS 23.093 CCBS_OCH_ Report_Failure See TS 23. False) Wait_For_ ACM See TS 23.087 To Subs_FSM Call setup failed Initial Address Destination address:= IAM.078 A Leg1_only Abort Fail CCBS_Check_ OG_Call No A See TS 23.078 3 Result= Leg1_only? No No Result= Pass? Yes CAMEL_MO_ Dialled_ Services Result? Pass A Reconnect:= True See TS 23.018 V10.1.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS 1 OCS_MSC3(11) Signals to/from the left are to/from the BSS.078 Figure 8c: Procedure OG_Call_Setup _MSC (sheet 3) 3GPP . Set_CLI_ Presentation_ Indicator_ MSC Result= Call allowed? Yes No Release transaction CAMEL_OCH_ MSC_INIT Yes See TS 23.093 See TS 23. signals to/from the right are to/from the destination exchange unless otherwise marked.066 PORTABILITY_ IN_OQoD UUS_OCH_ Set_Info_ In_IAM See TS 23.Called Party Address CAMEL_Store_ Destination_ Address (False.078 Leg1_Status :=Set-up CAMEL_OCH_ LEG1_MSC (Leg1_Status) Idle Result= Pass? Yes Release transaction MOBILE_NUMBER_ See TS 23.

Address Complete Connect See TS 23.078 CAMEL_ Start_TNRy Send_ Alerting_If_ Required No Result= Pass? Yes Release CAMEL_OCH_ MSC_ALERTING Release Fail See TS 23. signals to/from the right are to/from the destination exchange unless otherwise marked.1.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_ ACM OCS_MSC4(11) Signals to/from the left are to/from the BSS.093 See TS 23.093 CCBS_OCH_ Report_Success CCBS_OCH_ Report_Success See TS 23.018 V10.Release 10 43 3GPP TS 23.078 Result? Pass UTU2Cnt:=0 Reconnect 3 Answer Release transaction To Subs_FSM Call setup failed Alerting in progress To Subs_FSM Wait_For_ Answer ECT request Answer To Subs_FSM ECT request CAMEL_ Stop_TNRy See TS 23.078 Wait_For_ Answer 2 Figure 8d: Procedure OG_Call_Setup _MSC (sheet 4) 3GPP .

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

093 Release Call setup failed To Subs_FSM Figure 8f: Procedure OG_Call_Setup _MSC (sheet 6) 3GPP .Release 10 45 3GPP TS 23.1.093 See TS 23.093 CCBS_OCH_ Report_Failure CAMEL Phase 2 or higher supported? No Yes No CAMEL Phase 2 or higher supported? Yes Yes No Release cause= No answer from user? CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC_DISC4 CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC1 4 No Result= Reconnect? Yes See TS 23. signals to/from the right are to/from the destination exchange unless otherwise marked.018 V10.078 Release transaction 3 CCBS Result CCBS Possible CCBS Not Possible Release transaction CCBS_ Activation_ MSC Release See TS 23. Release transaction Release From destination exchange From gsmSSF Int_Release_ Call CCBS_OCH_ Report_Failure See TS 23.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_ ACM OCS_MSC6(11) Signals to/from the left are to/from the BSS.093 CCBS_Check_ If_CCBS_ Possible Store CCBS Result See TS 23.

018 V10.078 Release transaction UUS_MSC_ Check_ UUS1_UUI No See TS 23. signals to/from the right are to/from the destination exchange unless otherwise marked.087 Result= Reconnect? Yes See TS 23.087 UUS_MSC_ Check_ UUS1_UUI 3 Release Release transaction Release Call setup failed To Subs_FSM Signals to/from the left are to/from the BSS.Release 10 46 3GPP TS 23. Figure 8g: Procedure OG_Call_Setup _MSC (sheet 7) 3GPP .1.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_Connect_Ack Wait_For_Answer OCS_MSC7(11) Release transaction Release From gsmSSF Int_Release_ Call CAMEL Phase 2 or higher supported? No Yes No CAMEL Phase 2 or higher supported? Yes Yes No Release cause= No answer from user? 4 CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC_DISC4 CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC1 See TS 23.

Fail To Subs_FSM Wait_For_ Answer Call setup failed 3 Figure 8h: Procedure OG_Call_Setup _MSC (sheet 8) 3GPP .Release 10 47 3GPP TS 23.1.078 Release Result? Reconnect Release transaction Continue. signals to/from the right are to/from the destination exchange unless otherwise marked.087 4 Release See TS 23.018 V10.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_ Answer OCS_MSC8(11) Signals to/from the left are to/from the BSS. User to User User to User TNRy expired Internal UUS_MSC_ Check_UUS2_ UUI_to_NW See TS 23.087 UUS_MSC_ Check_UUS2_ UUI_to_MS CAMEL_OCH_ MSC2 See TS 23.

1.Release 10 48 3GPP TS 23.078 CAMEL_OCH_ MSC_DISC2 See TS 23.087 Release transaction CAMEL_OCH_ MSC_DISC1 See TS 23.018 V10.087 UUS_MSC_ Check_ UUS1_UUI See TS 23.078 Result= Reconnect? No Yes Yes Yes Result= CAMEL handling? No Result= CAMEL handling? No Release transaction 3 Release Release Call cleared To Subs_FSM Figure 8i: Procedure OG_Call_Setup _MSC (sheet 9) 3GPP . Wait_For_Clear Release transaction Release from gsmSSF Int_Release_ Call UUS_MSC_ Check_ UUS1_UUI See TS 23. signals to/from the right are to/from the destination exchange unless otherwise marked.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS OCS_MSC9(11) Signals to/from the left are to/from the BSS.

Release 10 49 3GPP TS 23.083 Wait_For_ Clear Figure 8j: Procedure OG_Call_Setup _MSC (sheet 10) 3GPP .018 V10.083 Process_ Hold_ Request Hold reject Retrieve reject Process_ Retrieve_ Request See 3G TS 23.1.0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_ Clear OCS_MSC10(11) Signals to/from the left are to/from the BSS Hold request Retrieve request Hold supported? Yes No No Hold supported? Yes See 3G TS 23.

0 (2011-03) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message has been received from the MS Wait_For_ Clear OCS_MSC11(11) Signals from the left are from the BSS. signals to the right are to the Subs_FSM process. ECT request MPTY request ECT request MPTY request Wait_For_ Clear Figure 8k: Procedure OG_Call_Setup _MSC (sheet 11) 3GPP .Release 10 50 3GPP TS 23.1.018 V10.

Signals to/from the right are to/from the VLR OIMSI_M1(1) Send IMSI Wait_For_ IMSI Send IMSI ack Release transaction Send IMSI negative response Release transaction Provide IMSI ack Abort Result:= Pass Result:= Aborted Figure 9: Procedure Obtain_IMSI_MSC 3GPP .018 V10.Release 10 51 3GPP TS 23.0 (2011-03) Procedure Obtain_IMSI_MSC Procedure in the MSC to obtain the IMSI from the MS and relay it to the VLR Signals to/from the left are to/from the BSS.1.

Signals to/from the right are to/from the VLR AUT_MSC1(1) Authenticate Wait_For_ Auth_Response Authenticate ack Release transaction Authenticate negative response Authenticate ack Abort Authenticate negative response Release transaction Wait_For_ Auth_Result Result:= Aborted Authentication accepted Authentication rejected Authentication rejected Result:= Pass Figure 10: Procedure Authenticate_MSC 3GPP .1.0 (2011-03) Procedure Authenticate_MSC Procedure in the MSC to obtain an authentication response from the MS and relay it to the VLR Signals to/from the left are to/from the BSS.Release 10 52 3GPP TS 23.018 V10.

018 V10.0 (2011-03) Procedure Obtain_IMEI_MSC Procedure in the MSC to obtain the IMEI from the MS and relay it to the VLR Signals to/from the left are to/from the BSS.Release 10 53 3GPP TS 23. Signals to/from the right are to/from the VLR OIMEI_M1(1) Send IMEI Wait_For_ IMEI Send IMEI ack Release transaction Send IMEI negative response Release transaction Provide IMEI ack Abort Result:= Pass Result:= Aborted Figure 11: Procedure Obtain_IMEI_MSC 3GPP .1.

IMEI available? No Yes Send IMEI Wait_For_ IMEI CM service abort Send IMEI negative response Send IMEI ack Release transaction Check IMEI To EIR Abort Wait_for_ Check_IMEI_ Result Result:= Aborted Release transaction Check IMEI negative response From EIR Check IMEI ack From EIR Abort Check IMEI negative response Check IMEI ack Result:= Aborted Result:= Pass Figure 12: Procedure Check_IMEI_MSC 3GPP .0 (2011-03) Procedure Check_IMEI_MSC Procedure in the MSC to check the IMEI and relay the result to the VLR CIMEI_M1(1) Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless marked otherwise.1.018 V10.Release 10 54 3GPP TS 23.

0 (2011-03) Procedure Establish_Originating_TCH_If_Required Procedure in the originating VMSC to establish a Traffic Channel if one has not been established for this call EOTCIR1(1) Signals to/from the left are to/from the BSS. signals to the right are to the process Subs_FSM TCH_Check Result Use existing Allocate Aborted.Release 10 55 3GPP TS 23. Fail Reject Allocate channel Wait_For_ Allocation_ Complete Release transaction Allocation failure Allocation complete Release transaction Result:= Pass Result:= Fail Result:= Pass Result:= Fail Result:= Rejected Call setup failed Call setup failed Figure 13: Procedure Establish_Originating_TCH_If_Required 3GPP .018 V10.1.

0 (2011-03) Procedure Set_CLI_Presentation_Indicator_MSC Procedure in the MSC to determine the CLI presentation indicator value Signals to/from the right are to/from the process CLIR_MAF004 CAIND_M1(1) Initiate handling of CLIR Wait_For_ CLIR_Info Release transaction From BSS Clear call Continue call handling Result:= Call not allowed Result:= Call allowed Figure 14: Procedure Set_CLI_Presentation_Indicator_MSC 3GPP .1.Release 10 56 3GPP TS 23.018 V10.

Release 10 57 3GPP TS 23.087 UUS_MSC_ Check_ UUS1_UUI UUS_OCH_Set_ Alert_And_ Connect_Param See TS 23.018 V10.087 Result= Pass? Yes No Progress Alerting Alerting sent:= True Result:= Pass Result:= Fail Figure 15: Procedure Send_Alerting_If_Required 3GPP .1.0 (2011-03) Procedure Send_Alerting_If_Required Procedure to send an Alerting message to the MS if one is required for this call SALTIR1(1) Signals to the left are to the BSS True Alerting sent False True Access Connect sent False Yes No Backward call indicator= no indication? See TS 23.

0 (2011-03) Procedure Set_COLP_Info_MSC Procedure in the MSC to determine the COLP information to be sent to the MS Signals to/from the right are to/from the process COLP_MAF006 COINF_M1(1) Initiate handling of COLP Wait_For_ COLP_Info Release transaction From BSS Continue call handling Release From destination exchange Figure 16: Procedure Set_COLP_Info_MSC 3GPP .1.018 V10.Release 10 58 3GPP TS 23.

018 V10.Release 10 59 3GPP TS 23.0 (2011-03) Procedure Handle_AoC_MO_MSC Procedure in the MSC to handle AoC signalling towards the MS for an MO call AoCMO_M1(1) Yes AoC(I) provisioned? No Set charging parameters No AoC(C) provisioned? Yes Set charging parameters Acknowledgment required:= False Acknowledgment required:= True Figure 17: Procedure Handle_AoC_MO_MSC 3GPP .1.

087 Facility Connect No Acknowledgment required? Yes No Acknowledgment required? Yes Start AoC acknowledgment timer Start AoC acknowledgment timer Wait_For_ AoC_Ack_F Wait_For_ AoC_Ack_C Charging Parameters ack Release transaction AoC acknowledgment timer expired Charging Parameters ack Release transaction Connect Ack AoC acknowledgment timer expired Release transaction Release transaction Release Release Result:= Facility sent Result:= Fail Result:= Connect sent Result:= Fail Figure 18: Procedure Send_Access_Connect_If_Required 3GPP . signals to/from the right are to/from the destination exchange MS connected UUS_OCH_ Set_Alert_And_ Connect_Param See TS 23.1.018 V10.0 (2011-03) Procedure Send_Access_Connect_If_Required Procedure to send a Connect message to the MS if one is required for this call True False SACONIR1(1) Signals to/from the left are to/from the BSS.Release 10 60 3GPP TS 23.

0 (2011-03) Procedure TCH_Check Procedure in originating or terminating VMSC to check if a trafic channel has been established for this call.Release 10 61 3GPP TS 23.1. signals to/from the right are to/from the process Subs_FSM Wait_For_ TCH_Result From GMSC Release Release transaction Allocate TCH TCH available TCH already allocated Result:= Aborted Result := Fail Result := Allocate Result := Use existing Result := Reject Figure 19: Procedure OCH_VLRTCH_Check 3GPP .018 V10. No Is call speech? Yes Non speech TCH required Speech TCH required TCH_Ch1(1) Signals to/from the left are to/from the BSS.

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.1. processing continues from connector 1 to the call to the procedure Check_OG_Barring. Sheet 2: the process Subscriber_Present_VLR is described in 3GPP TS 29. sheet 4. it is specified in 3GPP TS 23.1.135 [25].018 V10.1.1.087 [20].093 [23]. Sheet 1: the procedure OG_CUG_Check is specific to CUG.Release 10 62 3GPP TS 23. If the VLR supports neither CLIR nor COLP. it is specified in 3GPP TS 23.2.002 [29]. it is specified in 3GPP TS 23.5 7. If the VMSC does not support UUS.2.1. 3GPP .2. sheet 5: the procedure CCBS_Report_MS_Activity is specific to CCBS.1.1 7. the procedure call is omitted. Sheet 1: the procedure Get_LI_Subscription_Info_MO_VLR is specific to CLIR and COLP.078 [12]. 7. Sheet 3. processing continues from the "Yes" exit of the test "Result=Call allowed?". 7. Sheet 2: the negative response "call barred" indicates whether the reason is operator determined barring or supplementary service barring.2. Sheet 2: the procedure CAMEL_OCH_VLR is specific to CAMEL. Sheet 5: it is a network operator decision whether emergency calls are allowed from an ME with no SIM.2. Sheet 1: the procedure UUS_OCH_Check_Provision is specific to UUS. Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated.0 (2011-03) 7.2 Functional requirements of VLR 7. If the VMSC does not support Multicall. processing continues from the "Yes" exit of the test "Result=Pass?". processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 1: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC. If the VLR does not support CAMEL. Sheet 3: it is a network operator decision (subject to MoU requirements) how often an IMEI should be checked.4 Procedure Obtain_Identity_VLR It is a network operator decision whether open (non ciphered) identification of the MS by its IMSI is allowed. Sheet 1: the procedure Check_OG_Multicall_VLR is specific to Multicall.1. according to the result returned by the procedure Check_OG_Barring. it is specified in 3GPP TS 23.2 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. 7. A UMTS connection shall always be ciphered.2. If the VLR does not support CUG. Sheet 2: it is a network operator decision (subject to MoU requirements) whether a GSM connection should be ciphered.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.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.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.14 Procedure Get_LI_Subscription_Info_MO_VLR If the VLR does not support CLIR.2. greylisted.2. 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.Release 10 63 3GPP TS 23.1. then service is not granted.1.11 7.012 [6].2.1.088 [21]). 7. but the network operator may decide to initiate tracing.2.1. 7.2. the message is saved for handling after return from the procedure.2.2.16 Procedure Check_OG_Barring Sheet 3: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF018 or MAF020 (see 3GPP TS 23.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. 7. 7.2.7 7. whitelisted.1. 3GPP . If the VLR does not support COLP.1. it omits the signal interchange with the process CLIR_MAF003. the message is saved for handling after return from the procedure.018 V10. then service is granted.1. the message is saved for handling after return from the procedure. 7.10 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.2.2.1. 7.1.1.8 7.1. it omits the signal interchange with the process COLP_MAF005.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.1.2. then service is granted.0 (2011-03) 7.

1.1.018 V10. Idle OCH_VLR1(1) Process Access Request Process_ Access_ Request_VLR Result= Pass Yes No Wait_For_ SIFOC Idle Send Info For Outgoing Call Abort Yes Emergency call? No Idle Complete Call OG_Call_ Subscription_ Check_VLR Idle Idle Figure 7.2.1: Process OCH_VLR 3GPP .Release 10 64 3GPP TS 23.0 (2011-03) Process OCH_VLR Process in the VLR to handle an outgoing (MO) call setup request Signals to/from the left are to/from the MSC.

1.018 V10.2a: Procedure Process_Access_Request_VLR (sheet 1) 3GPP .0 (2011-03) Procedure Process_Access_Request_VLR Procedure in the VLR to handle a request from the MS for system access IMEISV stored? No Obtain_ IMEI_VLR PAR_VLR1(5) Signals to/from the left are to/from the MSC Yes PUESBINE supported? No No Result:= Aborted Yes Result= Pass? Yes Send UESBI-Iu to Access Network No PUESBINE supported? Yes No Identity known? Yes Obtain_ Identity_VLR Yes Result= Pass? Identity= IMEI? No Authentication required? Yes Authenticate_ VLR No Yes No No No Result= Fail? Yes Result= Pass? Yes IMSI detached:= False Confirmed by Radio Contact:= True Set negative response: System Failure 3 Set negative response: Unidentified Subscriber 3 Result:= Aborted 2 1 Figure 7.2.1.Release 10 65 3GPP TS 23.

1.1.2b: Procedure Process_Access_Request_VLR (sheet 2) 3GPP .2.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.018 V10.0 (2011-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 False Location info confirmed in HLR Update_ Location_VLR No Yes Mobile Not Reachable Flag set? Subscriber_ Present_VLR See TS 29.Release 10 66 3GPP TS 23.

1.018 V10.2c: Procedure Process_Access_Request_VLR (sheet 3) 3GPP . 4 5 PAR_VLR3(5) Start security procedures Identity:= IMSI Process Access Request ack No IMEI check required? Yes Check_ IMEI_VLR Result= Pass? Yes No TMSI reallocation required? Yes No Result= Fail? Yes CCBS_Report_ MS_Activity See TS 23.093 No Forward New TMSI Use Existing TMSI IMSI detached:= True Freeze existing TMSI Result:= Pass Set negative response: Illegal Equipment Result:= Aborted Wait_For_ TMSI_Ack 3 Figure 7.1.2.0 (2011-03) Procedure Process_Access_Request_VLR Procedure in the VLR to handle a request from the MS for system access Signals to the left are to the MSC.Release 10 67 3GPP TS 23.

093 Yes Result= Unidentified Subscriber? No Set negative response: Unidentified Subscriber Result:= Pass Set negative response: Illegal Subscriber 3 Figure 7.1.2d: Procedure Process_Access_Request_VLR (sheet 4) 3GPP .0 (2011-03) Procedure Process_Access_Request_VLR Procedure in the VLR to handle a request from the MS for system access Signals from the left are from the MSC.1.2.018 V10.Release 10 68 3GPP TS 23. Wait_For_ TMSI_Ack PAR_VLR4(5) 2 Result= Aborted? No Yes Forward New TMSI ack Forward New TMSI negative response Result:= Aborted Yes Result= Procedure Error? No Result= Unknown Subscriber? No Set negative response: System Failure Yes Unfreeze existing TMSI CCBS_Report_ MS_Activity See TS 23.

0 (2011-03) Procedure Process_Access_Request_VLR Procedure in the VLR to handle a request from the MS for system access Signals to the left are to the MSC.2e: Procedure Process_Access_Request_VLR (sheet 5) 3GPP .093 CCBS_Report_ MS_Activity Result:= Pass Result:= Aborted Result:= Fail Figure 7.1. 3 PAR_VLR5(5) CM service type =Emergency call? Yes No Emergency call setup allowed without SIM? No No Yes IMEI required? Yes Obtain_ IMEI_VLR Result= Pass? Yes No Identity:= IMEI Result= Fail? No Yes Process Access Request ack Process Access Request negative response See TS 23.Release 10 69 3GPP TS 23.1.2.018 V10.

135 Check_OG_ Multicall_VLR Set negative response: Basic service not provisioned No Bearer service or teleservice Result= Pass? Yes Check_ BAOC Result= Call barred? No OG_CUG_ Check Yes Set negative response: Call barred No Result= Call allowed? Yes Get_LI_ Subscription_ Info_MO_VLR Get_AoC_ Subscription_ Info_VLR UUS_OCH_ Check_ Provision Set negative response: CUG reject Result= Pass? Yes No Send Info For Outgoing Call negative response 1 Figure 7.Release 10 70 3GPP TS 23.0 (2011-03) Procedure OG_Call_Subscription_Check_VLR Procedure in the VLR to perform subscription checks for an outgoing call Signals to the left are to the MSC OCSCVLR1(2) No Basic service provisioned? Yes See TS 23.2.1.018 V10.1.3a: Procedure OG_Call_Subscription_Check_VLR (sheet 1) 3GPP .

1.2.1.018 V10.Release 10 71 3GPP TS 23.078 Result= Fail? No Yes Check_OG_ Barring Call barred? No Yes Set negative response: Call barred Complete Call Send Info For Outgoing Call negative response Figure 7.0 (2011-03) Procedure OG_Call_Subscription_Check_VLR Procedure in the VLR to perform subscription checks for an outgoing call OCSCVLR2(2) Signals to the left are to the MSC 1 CAMEL_ OCH_VLR See TS 23.3b: Procedure OG_Call_Subscription_Check _VLR (sheet 2) 3GPP .

2.1.0 (2011-03) Procedure Obtain_Identity_VLR Procedure in the VLR to obtain the identity of an MS OID_VLR1(1) Yes Identity= IMSI? No Identification allowed? No Yes Obtain_ IMSI_VLR Result= Pass? Yes No No IMSI known? Yes Result:= Fail Result:= Pass Result:= Aborted Figure 7.Release 10 72 3GPP TS 23.4: Procedure Obtain_Identity_VLR 3GPP .1.018 V10.

5: Procedure Obtain_IMSI_VLR 3GPP .1.Release 10 73 3GPP TS 23.2.1. OIMSI_V1(1) Provide IMSI Wait_For_ IMSI Provide IMSI ack Abort Result:= Pass Result:= Aborted Figure 7.0 (2011-03) Procedure Obtain_IMSI_VLR Process in the VLR to obtain the IMSI from the MS via the MSC Signals to/from the left are to/from the MSC.018 V10.

6a: Procedure Authenticate_VLR (sheet 1) 3GPP . AUT_VLR1(2) Authentication sets available? No Yes Obtain_ Authentication_ Sets_VLR No Result= Pass? Yes 2 Yes Result= Aborted? No Authenticate Result:= Aborted Yes Result= Procedure Error? No Wait_For_ Authenticate_ Result Result:= Procedure Error Result:= Unknown Subscriber Authenticate ack Authenticate negative response Authentication failure report More authentication sets needed? Abort Received SRES= expected SRES? Yes More authentication sets needed? No No Yes Fetch_ Authentication_ Sets_VLR No Yes Fetch_ Authentication_ Sets_VLR Authentication accepted Result:= Pass Result:= Aborted 1 Figure 7.2.Release 10 74 3GPP TS 23.1.0 (2011-03) Procedure Authenticate_VLR Procedure in the VLR to authenticate an MS via the MSC Signals to/from the left are to/from the MSC.1.018 V10.

2.Release 10 75 3GPP TS 23.0 (2011-03) Procedure Authenticate_VLR Procedure in the VLR to authenticate an MS via the MSC Signals to the left are to the MSC.1.018 V10.6b: Procedure Authenticate_VLR (sheet 2) 3GPP . Identity=IMSI? No No 1 AUT_VLR2(2) Yes Retry with IMSI? Yes Obtain_ IMSI_VLR No Result= Pass? Yes No IMSI known? Yes Yes IMSI matches TMSI? No Authentication accepted Authentication rejected Authentication failure report Result:= Aborted Result:= Unidentified Subscriber Identity:= IMSI Result:= Illegal Subscriber 2 Figure 7.1.

0 (2011-03) Procedure Obtain_Authentication_Sets_VLR Procedure in the VLR to obtain authentication sets from the HLR Signals to/from the right are to/from the HLR OAS_VLR1(2) Send Authentication Info Wait_For_ Authentication_ Sets Send Authentication Info ack Send Authentication Info negative response Empty result? No Yes No Unknown Subscriber? Yes Authentication sets available in VLR? No Yes Yes No Re-use old sets? Result:= Pass Result:= Procedure Error Result:= Unknown Subscriber Figure 7.1.2.7a: Procedure Obtain_Authentication_Sets_VLR (sheet 1) 3GPP .Release 10 76 3GPP TS 23.018 V10.1.

2. Signals to/from the right are to/from the HLR Wait_For_ Authentication_ Sets Abort Abort Abort Authentication sets available? Yes Yes Re-use old sets? No No Result:= Aborted Result:= Pass Result:= Procedure Error Figure 7.7b: Procedure Obtain_Authentication_Sets_VLR (sheet 2) 3GPP .1.018 V10.Release 10 77 3GPP TS 23.0 (2011-03) Procedure Obtain_Authentication_Sets_VLR Procedure in the VLR to obtain authentication sets from the HLR OAS_VLR2(2) Signals to/from the left are to/from the MSC.1.

ST_TR_V1(1) Tracing active? Yes No Trace Subscriber Activity Figure 7.018 V10.1.2.8: Procedure Start_Tracing_VLR 3GPP .Release 10 78 3GPP TS 23.0 (2011-03) Procedure Start_Tracing_VLR Procedure in the VLR to request the MSC to start activity tracing Signals to the left are to the MSC.1.

1.9: Procedure Check_IMEI_VLR 3GPP .Release 10 79 3GPP TS 23.1.2.0 (2011-03) Procedure Check_IMEI_VLR Procedure in the VLR to request the MSC to check an IMEI Signals to/from the left are to/from the MSC CIMEI_V1(1) Check IMEI Wait_For_ Check_IMEI_ Result Abort Check IMEI negative response Check IMEI ack No Service granted? Yes Result:= Aborted Result:= Fail Result:= Pass Figure 7.018 V10.

018 V10.0 (2011-03) Procedure Obtain_IMEI_VLR Process in the VLR to obtain the IMSI from the MS via the MSC OIMEI_V1(1) Signals to/from the left are to/from the MSC Provide IMEI Wait_For_ IMEI Provide IMEI ack Abort Store IMEISV Result:= Pass Result:= Aborted Figure 7.2.1.Release 10 80 3GPP TS 23.1.10: Procedure Obtain_IMEI _VLR 3GPP .

11: Process Fetch_Authentication_Sets_VLR 3GPP .018 V10.2.1.1.Release 10 81 3GPP TS 23.0 (2011-03) Process Fetch_Authentication_Sets_VLR Process in the VLR to retrieve authentication sets from the HLR FAS_VLR1(1) Obiain_ Authentication_ Sets_VLR Figure 7.

0 (2011-03) Procedure Check_BAOC Procedure to check call request against ODBAOC and SS BAOC Signals to/from the right are to/from the process MAF017 CBAOC1(1) Yes No Operator determined BAOC imposed? Result:= Call barred (ODB) Initiate handling of BAOC Wait_For_ BAOC_ Response From MSC Abort Continue call handling Yes Call barred? No Result:= Call barred (SS barring) Result:= Call allowed Figure 7.1.12: Procedure Check_BAOC 3GPP .018 V10.Release 10 82 3GPP TS 23.2.1.

Release 10 83 3GPP TS 23.13: Procedure OG_CUG_Check 3GPP .018 V10.1.1.0 (2011-03) Procedure OG_CUG_Check Procedure to carry out CUG authorisation check for an outgoing (MO) call Signals to/from the right are to/from the process CUG_MAF014 OG_CUG1(1) outgoing call request Wait_For_ CUG_Response From MSC Abort response to call request complete call (conditional CUG info) reject call (cause) Result:= Call allowed Result:= Call barred Figure 7.2.

0 (2011-03) Procedure Get_LI_Subscription_Info_MO_VLR Procedure in the VLR to retrieve subscription information for the CLIR & COLP line identification services for an MO call Initiate handling of CLIR GLI_MOV1(1) To process CLIR_MAF003 Wait_For_ CLIR_Info From MSC Abort Continue call handling From process CLIR_MAF003 Initiate handling of COLP To process COLP_MAF005 Wait_For_ COLP_Info From MSC Abort Continue call handling From process COLP_MAF005 Figure 7.1.1.14: Procedure Get_LI_Subscription_Info_MO_VLR 3GPP .2.018 V10.Release 10 84 3GPP TS 23.

1.0 (2011-03) Procedure Get_AoC_Subscription_Info_VLR Procedure in the VLR to determine the subscription to Advice of Charge services GAOCI_V1(1) AoC(I) provisioned? No No Yes AoC(C) provisioned? Yes Set indicator: AoC not provisioned Set indicator: AoC(C) provisioned Set indicator: AoC(I) provisioned Figure 7.15: Procedure Get_AoC_Subscription_Info_VLR 3GPP .1.Release 10 85 3GPP TS 23.018 V10.2.

2.018 V10.Release 10 86 3GPP TS 23.16a: Procedure Check_OG_Barring (sheet 1) 3GPP .1.0 (2011-03) Procedure Check_OG_Barring Procedure to check call request against SS barring and ODB categories COB1(3) Yes No Yes 1 Yes Yes No 1 No Yes 1 Yes No Yes 1 Yes Yes No 1 No Yes Result:= Call barred (ODB) Destination address CC= HPLMN CC? No No Destination address CC= HPLMN CC? No No Operator determined BOIC imposed? Destination address CC= Local CC? Operator determined BOIC-exHC imposed? Destination address CC= Local CC? Operator determined BOIZC imposed? Destination address ZC= Local ZC? Operator determined BOIZC-exHC imposed? Destination address ZC= Local ZC? 1 Figure 7.1.

018 V10.1.16b: Procedure Check_OG_Barring (sheet 2) 3GPP .1.Release 10 87 3GPP TS 23.2.0 (2011-03) Procedure Check_OG_Barring Procedure to check call request against SS barring and ODB categories 1 COB2(3) No Yes 2 Yes No Yes No 2 No Yes Result:= Call barred (ODB) Operator determined BOIC-exHC&BOIZC imposed? Destination address ZC= Local ZC? Destination address CC= Local CC? Destination address CC= HPLMN CC? 2 Figure 7.

Release 10 88 3GPP TS 23.1.1.0 (2011-03) Procedure Check_OG_Barring Procedure to check call request against SS barring and ODB categories 2 COB3(3) Yes Call barred? No Initiate handling of BOIC To process MAF018 Wait_For_ BOIC_ Response From MSC Abort Continue call handling From process MAF018 Yes Call barred? No Initiate handling of BOIC-exHC To process MAF020 Wait_For_ BOIC-exHC_ Response From MSC Abort Continue call handling From process MAF020 Yes Call barred? No Result:= Call barred (SS barring) Result:= Call allowed Figure 7.018 V10.2.16c: Procedure Check_OG_Barring (sheet 3) 3GPP .

2.1.0 (2011-03) Process Update_Location_VLR Process in the VLR to update the location information in the HLR. UL_VLR1(1) Update_HLR_ VLR See TS 23.018 V10.1.17: Process Update_Location_VLR 3GPP .012 Figure 7.Release 10 89 3GPP TS 23.

Sheet 1: the parameters "Reference address".078 [12].Release 10 90 3GPP TS 23. "OR" and "Own PLMN" are passed to the procedure Obtain_Routeing_Address only if the GMSC supports Optimal Routeing. The mapping used is a matter for the network operator. Sheet 1: the variable UUS CF interaction is specific to UUS.1 Functional requirements of GMSC 7.1. The parameter "Destination address" is returned by the procedure Obtain_Routeing_Address only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. available to the parent process. CCBS_Set_Diagnostic_For_Release.079 [13]. Send_ACM_If_Required.0 (2011-03) 7. Sheet 1: the procedure OR_Set_ORA_Parameters is specific to Support of Optimal Routeing. Answer sent.2 Retrieval of routeing information for MT call 7.066 [10]. 3GPP . depending on the telephony signalling system used.1. it is specified in 3GPP TS 23.850 [37]) is shown in table 1.018 V10.2. it is accessible to all UUS specific procedures in the GMSC. Reconnect and Resume call are global data. Network connect sent. The Send Routeing Info negative response information element received in the execution of the procedure Obtain_Routeing_Address is global data. Obtain_Routeing_Address. it is specified in 3GPP TS 23. 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. accessible to the procedures CCBS_MT_GMSC_Check_CCBS Possible. it is specified in 3GPP TS 23.1 Process MT_GMSC Sheet 1: the variables ACM sent. Sheet 1: the procedure CAMEL_Set_ORA_Parameters is specific to CAMEL. Sheet 1: the procedure MNP_MT_GMSC_Set_MNP_Parameters is specific to Mobile Number Portability. Send_Answer_If_Required and Send_Network_Connect_If_Required.2.

unspecified 69 Requested facility not implemented 21 Call rejected 22 Number changed 111 Protocol error. 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.Release 10 91 3GPP TS 23. Sheet 1: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in the Perform Call Forwarding ack. Sheet 2. 3GPP . depending on national regulations. Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. it shall include the called party's status field of the Backward call indicator set to "no indication". Sheet 1.0 (2011-03) Table 1: Suggested mapping of Send Routeing Info (SRI) negative responses to ISUP release causes SRI negative response Absent subscriber Bearer service not provisioned Busy subscriber 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 NOTE: ISUP release cause number 20 57 17 21 21 21 55 87 87 ISUP release cause name Subscriber absent Bearer capability not authorized User busy Call rejected Call rejected Call rejected Incoming calls barred within CUG User not member of CUG User not member of CUG 111 Protocol error. MNP can require a specific ISUP release cause value. sheet 8: the process CAMEL_MT_LEG1_GMSC is specific to CAMEL phase 4 or later. If the GMSC sends an Address Complete message. Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later. processing continues from the "Pass" exit of the test "Result?". Sheet 1: it is an operator option whether to send an Address Complete message if the HLR returns forwarding information.078 [12]. under all other conditions the SRI negative response "unknown subscriber" shall be mapped to ISUP release cause number 1 "Unallocated (unassigned) number".078 [12]. 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". If the GMSC sends an Address Complete message. sheet 3: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later.078 [12].1. it is specified in 3GPP TS 23. unspecified 57 Bearer capability not authorized 111 Protocol error. it is specified in 3GPP TS 23.078 [12]. sheet 3: the task "Set destination address parameter" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. sheet 3: the procedure CAMEL_MT_GMSC_ANSWER is specific to CAMEL.078 [12]. it is specified in 3GPP TS 23. according to National Coding Standard. processing continues from the "Pass" exit of the test "Result". unspecified 1 Unallocated (unassigned) number 26 Misrouted call to a ported number (note) If the Diagnostic parameter indicates "NPDB mismatch".018 V10. If the GMSC does not support CAMEL phase 4 or later. Sheet 1: it is an operator option whether to send an Address Complete message if the Number Portability Database returns a routeing number. Sheet 2. Sheet 2. North American GSM Number Portability (NAGNP) requires the SRI negative response "unknown subscriber" to be treated differently under certain conditions. to indicate "Misrouted call to a ported number". it is specified in 3GPP TS 23. If the GMSC does not support CAMEL.

If the GMSC does not support CAMEL. Sheet 7: the procedure CAMEL_MT_GMSC_DISC2 is specific to CAMEL.0 (2011-03) Sheet 3: the procedure Handle_COLP_Forwarding_Interaction is specific to COLP. Any message other than Address Complete. It is specified in 3GPP TS 23. sheet 6: the procedure CCBS_MT_GMSC_Check_CCBS_Possible is specific to CCBS. sheet 7: the processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL.172 [38]. it is specified in 3GPP TS 23. Sheet 6: the procedures CAMEL_MT_GMSC_DISC4 and CAMEL_MT_GMSC_DISC6 are specific to CAMEL phase 2 or later.1. Sheet 1: the procedure CLI_MT_GMSC is specific to Enhanced CLI Handling.078 [12]. The procedure CAMEL_MT_GMSC_DISC5 is specified in 3GPP TS 23.081 [14]. Sheet 8: the procedure CAMEL_MT_LEG2_GMSC is specific to CAMEL phase 4 or later. Sheet 1: if Mobile Terminating Roaming Retry is supported. it acts as a relay for messages received from the originating exchange and the destination VMSC or the process MT_CF_MSC.2. processing continues from the "Normal handling" exit of the test "Result?". Sheet 6. Sheet 7: after the GMSC has sent an IAM to the destination VMSC or the forwarded-to exchange (via the process MT_CF_MSC). If the GMSC does not support Optimal Routeing. as specified in 3GPP TS 23.078 [12]. If the GMSC does not support SCUDIF.066 [10]. If the GMSC does not support CAMEL. and will occur only if the GMSC supports Optimal Routeing. Sheet 7: the procedure CAMEL_MT_GMSC_DISC1 is specific to CAMEL. Answer or Release causes no change of state in the process MT_GMSC. the call reference number and the MT Roaming Retry Supported IE in the SRI message. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Connect. Sheet 2: the test "Error=Unknown subscriber" refers to the negative response value received from the HLR. 3GPP .079 [13].078 [12]. Sheet 4: the input signal Resume Call Handling and all the subsequent processing on this sheet are specific to Support of Optimal Routeing.Release 10 92 3GPP TS 23. processing continues from the "Fail" exit of the test "Result". they are specified in 3GPP TS 23. 7.078 [12].1. Sheet 4.093 [23]. it is specified in 3GPP TS 23.078 [12].018 V10. 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=Pass?". it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 1: global flag "Clear MT Roaming Retry IE" is initialized to No at the start of MT_GMSC procedure. Sheet 1: the procedure CCBS_MT_GMSC_Check_CCBS_Call is specific to CCBS. Sheet 1: for SCUDIF calls. processing continues from the "No" exit of the test "Result=CAMEL handling?".079 [13]. the GMSC shall include the GMSC address. it is specified in 3GPP TS 23. the message Send Routeing Info shall include the ISDN BC of both the preferred and the less preferred service. Sheet 6: the procedure CAMEL_MT_GMSC_DISC3 is specific to CAMELphase 1. It is specified in 3GPP TS 23. The procedure OR_Handle_RCH is specified in 3GPP TS 23. it is specified in 3GPP TS 23.093 [23].172 [38].078 [12]. and if no Resume Call Handling message for roaming retry has been received. it is specified in 3GPP TS 23. Sheet 6: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS.093 [23].2 Procedure Obtain_Routeing_Address Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_TQoD is specific to Mobile Number Portability. Sheet 2: the procedure SCUDIF_Negative_SRI_Response_Handling is specific to SCUDIF. Sheet 2: the procedure OR_Handle_SRI_Negative_Response is specific to Support of Optimal Routeing. and will occur only if the GMSC supports CAMEL phase 2 or later.

7.079 [13]. Sheet 6: the procedure CAMEL_MT_MSC_DISC3 is specific to CAMEL phase 1.172 [38]. Sheet 4: The test "MSRN contains a Routeing Number" is executed only if the SRF solution for call related MNP is used. it is specified in 3GPP TS 23. Sheet 4: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal Routeing.093 [23].078 [12].1.172 [38]. it is specified in 3GPP TS 23.093 [23]. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.1. Sheet 6: the procedure CAMEL_MT_GMSC_DISC4 is specific to CAMEL Phase 2 or later. Sheet 5: the procedure CAMEL_MT_GMSC_Notify_CF is specific to CAMEL phase 2 or later.078 [12]. 7. "Release Resources" shall not be sent.172 [38].2. it is specified in 3GPP TS 23. Sheet 6: the procedure Route_Permitted is specific to Support of Optimal Routeing. processing continues from the "continue" exit of the test "Result ?". Sheet 6: the procedures CCBS_MT_GMSC_Remove_Indicators_Store_FWT is specific to CCBS.3 Procedure Send_ACM_If_Required If no useful information would be carried in the Call Progress message. it is specified in 3GPP TS 23. Sheet 3: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF. If the GMSC does not support CAMEL phase 2 or later. Sheet 5: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF.066 [10]. it is specified in 3GPP TS 23. processing continues from the "True" exit of the test "Route permitted". If support of "Release Resources" by the VMSC is not indicated in Send Routing Info ack. Sheet 3: the procedure SCUDIF_Check_Service_Availability is specific to SCUDIF. it is specified in 3GPP TS 23. it is not sent.018 V10. Sheet 6: the task "OR:= True" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. It is specified in 3GPP TS 23. 3GPP . it is specified in 3GPP TS 23. Sheet 4: the procedure MNP_MT_GMSC_Check_MNP_Indicators is specific to Mobile Number Portability. Sheet 3: the procedure CAMEL_MT_GMSC_INIT is specific to CAMEL.078 [12].078 [12]. If the GMSC does not support Optimal Routeing.2. Sheet 3: sending of "Release Resources" is an implementation option. it is specified in 3GPP TS 23.Release 10 93 3GPP TS 23.1. Sheet 4: the procedure CCBS_MT_GMSC_Check_CCBS_Indicators is specific to CCBS. Sheet 4: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF. processing continues from the "No" exit of the test "MSRN contains a Routeing Number". processing continues from the "Continue" exit of the test "Result". If the GMSC does not support SCUDIF.4 Procedure Send_Answer_If_Required If no useful information would be carried in the Call Progress message.172 [38]. it is not sent.066 [10]. If the SRF solution for call related MNP is not used. it is specified in 3GPP TS 23. Sheet 6: the task "BOR:=OR" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. it is specified in 3GPP TS 23.0 (2011-03) Sheet 2: the procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR is specific to Mobile Number Portability.

Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. 7. it is specified in 3GPP TS 23.078 [12]. it is specified in 3GPP TS 23. Sheet 1.078 [12].078 [12]. it is specified in 3GPP TS 23.078 [12]. it is specified in 3GPP TS 23.078 [12]. sheet 3: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later.8 Process MT_CF_MSC Sheet 1: the procedure CAMEL_CF_MSC_INIT is specific to CAMEL. Sheet 1. sheet 4: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2 or later. If the MSC does not support CAMEL phase 3 or later.066 [10]. sheet 6: the procedure CAMEL_MT_CF_LEG1_MSC is specific to CAMEL phase 4 or later. Sheet 4: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. If the MSC does not support CAMEL. Sheet 3: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later.078 [12].078 [12]. Sheet 2: the procedure CAMEL_CF_MSC_ALERTING is specific to CAMEL phase 4 or later.1. If the MSC does not support CAMEL. it is specified in 3GPP TS 23. Sheet 2: the procedure UUS_MSC_Clear_UUS is specific to UUS. Sheet 1.078 [12].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. they are specified in 3GPP TS 23.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.018 V10. Sheet 1. 7.1. it is specified in 3GPP TS 23.0 (2011-03) 7. processing continues from the "Yes" exit of the test "Result=Reconnect?".078 [12]. it is specifed in 3GPP TS 23. sheet 4: the procedure CAMEL_CF_Dialled_Services is specific to CAMEL phase 3 or later. If the MSC does not support CAMEL phase 2 or later.078 [12].078 [12]. Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later. it is specified in 3GPP TS 23.2.2.1. Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability. If the GMSC does not support CAMEL phase 4 or later. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 3: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL. Sheet 1. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?".1. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23.2. processing continues from the "Pass" exit of the test "Result?".1. processing continues from the "Pass" exit of the test "Result?". processing continues from the "Pass" exit of the test "Result?".087 [20]. 7.Release 10 94 3GPP TS 23. and will occur only if the GMSC supports CAMEL phase 2 or later. sheet 3: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1. sheet 3.5 Procedure Send_Network_Connect_If_Required If no useful information would be carried in the Call Progress message. The message is saved for processing after return from the procedure. it is specified in 3GPP TS 23. it is not sent.2. Sheet 2: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL. 3GPP .078 [12].

Sheet 6: the process CAMEL_MT_CF_LEG2_MSC is specific to CAMEL phase 4 or later.018 V10. 3GPP . Any message other than Address Complete.1. processing continues from the "No" exit of the test "Result=CAMEL handling?".078 [12]. If the MSC does not support CAMEL. it is specified in 3GPP TS 23. it acts as a relay for messages received from the parent process and the forwarded-to exchange. If the MSC does not support CAMEL. processing continues from the "No" exit of the test "Result=Reconnect?" . it is specified in 3GPP TS 23.078 [12].078 [12]. Connect. Sheet 5: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL. Sheet 5: after the process MT_CF_MSC has sent an IAM to the forwarded-to exchange.Release 10 95 3GPP TS 23. Sheet 5: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL.0 (2011-03) Sheet 5: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL. Answer or Release causes no change of state in the process MT_GMSC. it is specified in 3GPP TS 23.

2.1.066 MNP_MT_GMSC_ Set_MNP_ Parameters OR_Set_ORA_ Parameters See TS 23.9 Macro CUG_Support_Check_GMSC MT_GMSC1(9) Signals to/from the left are to/from the originating exchange.079 CAMEL_Set_ ORA_Parameters See TS 23.078 4 Figure 36a: Process MT_GMSC (sheet 1) 3GPP .018 V10.Release 10 96 3GPP TS 23.1. signals to/from the right are to/from the destination MSC unless marked otherwise Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Idle Initial Address 1 CUG_Support_ Check_GMSC Reconnect:= True ACM sent:=False Answer sent:=False Network connect sent:=False Reconnect:=False Resume call:=False UUS CF Interaction:=False See TS 23.0 (2011-03) 7.

018 V10. Result) Result? Fail Aborted Pass Routeing Number Forward Leg1_only Leg1_status := Set-up Set cause See TS 23. False) See TS 23.Release 10 97 3GPP TS 23. Destination address.078 Send_ACM_ If_Required Send_ACM_ If_Required To originating exchange Wait_For_ ACM Wait_For_ Forward_ACM Figure 36b: Process MT_GMSC (sheet 2) 3GPP . signals to/from the right are to/from the destination MSC unless marked otherwise Obtain_Routeing_Address (Called party address.0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request 4 MT_GMSC2(9) Signals to/from the left are to/from the originating exchange. Own PLMN.078 CAMEL_Store_ Destination_ Address (OR. OR. False) CAMEL_Store_ Destination_ Address (OR.1.078 CAMEL_MT_ LEG1_GMSC (Leg1_status) Release Idle Release call resources Initial Address (Routeing Address) Initial Address (Routeing Address) Initial Address (Routeing Address) To process MT_CF_MSC Idle See TS 23. Routeing address. Reference address.

1.078 CAMEL_MT_ MSC_ALERTING Answer Result? Pass Else Wait_For_ Answer Answer See TS 23.Release 10 98 3GPP TS 23.078 CAMEL_MT_ GMSC_ANSWER CAMEL_MT_ GMSC_ANSWER See TS 23.018 V10.078 Result? Pass Set destination address parameter Else Else Result? Pass Release Result? Fail Reconnect Set destination address parameter Send_Answer_ If_Required Release 1 Send_Network_ Connect_If_ Required 3 Idle 3 Figure 36c: Process MT_GMSC (sheet 3) 3GPP .0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Wait_For_ ACM MT_GMSC3(9) Signals from the right are from the destination exchange Address Complete Connect Send_ACM_ If_Required See TS 23.078 CAMEL_ Stop_TNRy See TS 23.078 CAMEL_ Start_TNRy See TS 23.

0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Wait_For_ Forward_ACM MT_GMSC4(9) Signals from the right are from the process MT_CF_MSC Address Complete Connect Send_ACM_ If_Required See TS 23.078 Result? Pass Handle_COLP_ Forwarding_ Interaction_MSC Else Else Result? Pass Release Result? Fail Reconnect Handle_COLP_ Forwarding_ Interaction_MSC Set COLP presentation indicator Release 1 Set COLP presentation indicator Set destination address parameter Idle Set destination address parameter Send_Answer_ If_Required Send_Network_ Connect_If_ Required 3 3 Figure 36d: Process MT_GMSC (sheet 4) 3GPP .018 V10.078 CAMEL_MT_ MSC_ALERTING Answer Result? Pass Wait_For_ Forward_ Answer Else Answer See TS 23.1.Release 10 99 3GPP TS 23.078 CAMEL_MT_ GMSC_ANSWER CAMEL_MT_ GMSC_ANSWER See TS 23.

Release 10 100 3GPP TS 23.018 V10.1.078 OR_Handle_ RCH Yes See TS 23.079 for message contents Release CAMEL_ MT_GMSC_ DISC6 Clear MT Roaming Retry IE := true CAMEL_ Stop_TNRy see TS 23.079 Resume call := true Result= Fail? No Result= Release? No Yes 4 Yes Result= Refuse? No Yes Release Result= Reconnect? No - Wait_For_ Forward_ACM 1 Idle Figure 36e: Process MT_GMSC (sheet 5) 3GPP . Wait_For_Answer MT_GMSC5(9) Signals to/from the right are to/from the destination MSC unless marked otherwise Refer to TS 23.093 Check_CCBS_ Possible Resume call:True Wait_For_ACM.0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Resume Call Handling MT Roaming Retry supported Yes No MT Roaming Retry IE received Yes Resume Call Handling Ack No CCBS_MT_GMSC_ See TS 23.

signals to/from the right are to/from the destination MSC unless marked otherwise TNRy expired Internal 2 Release CAMEL_MT_ GMSC_DISC5 See TS 23.1.0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Wait_For_ Answer MT_GMSC6(9) Signals to/from the left are to/from the originating MSC. Fail Release Release call resources Idle 1 Figure 36f: Process MT_GMSC (sheet 6) 3GPP .Release 10 101 3GPP TS 23.018 V10.078 Release Result? Reconnect Continue.

Release 10 102 3GPP TS 23.1.078 No Result= Reconnect? Yes CCBS_Set_ Diagnostic_ For_Release Release Release Release 1 Release Release call resources Idle Figure 36g: Process MT_GMSC (sheet 7) 3GPP .018 V10. Wait_For_Forward_Answer MT_GMSC7(9) Signals to/from the left are to/from the originating exchange. Wait_For_Forward_ACM. Wait_For_Answer.0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Wait_For_ACM. signals to/from the right are to/from the destination exchange or process MT_CF_MSC unless marked otherwise Release Release From gsmSSF Int_Release_ Call CCBS_MT_GMSC_ Check_CCBS_ Possible See TS 23.093 CAMEL phase 2 or higher supported? No Yes No CAMEL phase 2 or higher supported? Yes Yes Release cause= No answer from user? No 2 CAMEL_MT_ GMSC_DISC3 CAMEL_MT_ GMSC_DISC6 CAMEL_MT_ GMSC_DISC3 CAMEL_MT_ GMSC_DISC4 See TS 23.

signals to/from the right are to/from the destination exchange or the process MT_CF_MSC unless marked otherwise Release Release Int_Release_ Call From gsmSSF CAMEL_MT_ GMSC_DISC1 See TS 23. Wait_For_Answer.018 V10.078 Result= CAMEL handling? No Yes Reconnect Result? CAMEL handling Release Normal handling Release 1 Release Release Release call resources Wait_For_ Clear Idle Resume Call Handling Wait_For_ACM. Wait_For_Forward_Answer. Wait_For_Clear Set negative response: OR not allowed * * Resume Call Handling negative response - - Wait_For_ Clear - Figure 36h: Process MT_GMSC (sheet 8) 3GPP .Release 10 103 3GPP TS 23. Wait_For_Forward_ACM.0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request Wait_For_ Clear MT_GMSC8(9) Signals to/from the left are to/from the originating exchange.078 CAMEL_MT_ GMSC_DISC2 See TS 23.1.

1.0 (2011-03) Process MT_GMSC Process in the GMSC to handle a mobile-terminated call request 3 MT_GMSC9(9) CAMEL phase 4 or later control relationship exists? Yes Leg1_status := Active No See TS 23.Release 10 104 3GPP TS 23.018 V10.078 CAMEL_MT_ LEG1_GMSC (Leg1_status) Wait_For_ Clear See TS 23.078 CAMEL_MT_ GMSC_LEG2 Idle Figure 36i: Process MT_GMSC (sheet 9) 3GPP .

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

172 Wait_for_Routeing_Info Result Fail OR_Handle_SRI_ Negative_Response (Own PLMN) Result= Pass? No No Error= Unknown subscriber? Yes Pass 4 Retry Send Routeing Info See TS 23.1.066 MOBILE_NUMBER_ PORTABILITY_ IN_QoHR No Result= Number ported? Yes Routeing address:= routeing number Result:=Fail Result:= Routeing number Figure 37b: Procedure Obtain_Routeing_Address (sheet 2) 3GPP .079 Yes Result:=Pass Wait_for_ Routeing_ Info See TS 23.0 (2011-03) Procedure Obtain_Routeing_Address Procedure in a GMSC to determine the address to which a call should be routed Wait_for_ Routeing_ Info Send Routeing Info negative response If MT Roaming Retry is supported Yes and MT Roaming Retry Indicator received? No Call Released? Yes Result:= Aborted No SCUDIF_negative_ SRI_response_ handling ORA2(6) Signals to/from the left are to/from the originating exchange.Release 10 106 3GPP TS 23.018 V10. signals to/from the right are to/from the HLR Release Set: Call Released Wait_for_ Routeing_ Info Clear RoamingRetry Supported IE Send Routeing Info See TS 23.

172 Result? second_SRI Continue Result:= Aborted Network Signal Info:= less preferred service CAMEL supported? 1 Send Routeing Info No MSRN received? No Yes 3 SCUDIF_Check_ Service_Compatibility Yes CAMEL_MT_ GMSC_INIT See TS 23.078 Wait_for_ Routeing_ Info Result= MSRN Yes No See TS 23.172 Yes Result= Aborted No Yes Result = Leg1_only? Result:= Aborted Result := Leg1_only 3 2 5 Figure 37c: Procedure Obtain_Routeing_Address (sheet 3) 3GPP .1.0 (2011-03) Procedure Obtain_Routeing_Address Procedure in a GMSC to determine the address to which a call should be routed Wait_for_ Routeing_ Info ORA3(6) Send Routeing Info ack From HLR Yes Call Relaesed? MSRN received? No Yes Release Resources 4 No SCUDIF_Check_ Service_Availability See TS 23.018 V10.Release 10 107 3GPP TS 23.

066 Result= Fail? Yes No Routeing address:= MSRN Destination address:= VMSC address Result:= Fail Result:= Routeing number Result:= Pass Figure 37d: Procedure Obtain_Routeing_Address (sheet 4) 3GPP .Release 10 108 3GPP TS 23.1.018 V10.093 Store Forwarding Interrogation Required indicator No MSRN contains a Routeing number? Yes MNP_MT_GMSC_ Check_MNP_ Indicators Routeing address:= MSRN See TS 23.172 CCBS_MT_ GMSC_Check_ CCBS_ Indicators See TS 23.0 (2011-03) Procedure Obtain_Routeing_Address Procedure in a GMSC to determine the address to which a call should be routed ORA4(6) 3 SCUDIF_Check_ Service_Compatibility See TS 23.

172 Reconnect := True Result:= Fail 2 1 Figure 37e: Procedure Obtain_Routeing_Address (sheet 5) 3GPP .0 (2011-03) Procedure Obtain_Routeing_Address Procedure in a GMSC to determine the address to which a call should be routed ORA5(6) 5 Result= Fail No Result CAMEL_FTN GSM_FTN CAMEL_ MT_GMSC_ Notify_CF Yes See TS 23.018 V10.Release 10 109 3GPP TS 23.1.078 Fail Result Continue Reconnect SCUDIF_Check_ Service_Compatibility See TS 23.

Release 10 110 3GPP TS 23.FTN.078 See TS 23.018 V10.0 (2011-03) Procedure Obtain_Routeing_Address Procedure in a GMSC to determine the address to which a call should be routed 2 ORA6(6) BOR:=OR Activate_ CF_Process Result? Fail Release Pass CCBS_MT_ GMSC_Remove_ Indicators_ Store_FWT Release See TS 23. Reference Address) False Route permitted True See TS 23.1.093 Result:= Aborted Route_Permitted (OR.079 CAMEL phase 2 or higher supported? No Yes CAMEL_MT_ GMSC_DISC4 See TS 23.078 CAMEL_MT_ GMSC_DISC3 To process MT_CF_MSC CF cancelled Routeing address:= FTN Routeing address:= Reference address Destination address:= FTN Destination address:= Reference address OR:=True OR:=False Result:= Forward Result:= Pass Figure 37f: Procedure Obtain_Routeing_Address (sheet 6) 3GPP .

0 (2011-03) Procedure Send_ACM_If_Required Procedure to send an Address Complete Message to the preceding exchange if one is required for this call True SACMIR1(1) Signals to the left are to the originating exchange ACM sent False True Network connect sent False Call Progress Address Complete ACM sent:= True Figure 38: Procedure Send_ACM_If_Required 3GPP .1.018 V10.Release 10 111 3GPP TS 23.

0 (2011-03) Procedure Send_Answer_If_Required Procedure to send an Answer Message to the preceding exchange if one is required for this call True SANMIR1(1) Signals to the left are to the originating exchange Answer sent False True Network connect sent False Call Progress Answer Answer sent:= True Figure 39: Procedure Send_Answer_If_Required 3GPP .018 V10.1.Release 10 112 3GPP TS 23.

018 V10.Release 10 113 3GPP TS 23.0 (2011-03) Procedure Send_Network_Connect_If_Required Procedure to send a Connect Message to the preceding exchange if one is required for this call True Network connect sent False True SNCONIR1(1) Signals to the left are to the originating exchange Answer sent False True ACM sent False Call Progress Answer Connect Answer sent:= True Connect sent:= True Figure 40: Procedure Send_Network_Connect_If_Required 3GPP .1.

0 (2011-03) Procedure Handle_COLP_Forwarding_Interaction_MSC Procedure in the GMSC or VMSC to handle the interaction between COLP and Call Forwarding COINT_M1(1) Signals to/from the right are to/from the process COLP_MAF039 Initiate handling of COLP Wait_For_ COLP_Info Release From originating exchange or destination exchange continue call handling Figure 41: Procedure Handle_COLP_Forwarding_Interaction_MSC 3GPP .1.018 V10.Release 10 114 3GPP TS 23.

1. signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Perform call forwarding (BOR.018 V10.Release 10 115 3GPP TS 23. FTN) Wait_For_ CF_Response Release Perform call forwarding ack Perform call forwarding negative response Int_Release_ Call From gsmSSF CF cancelled CF cancelled Result:= Fail Result:= Pass Result:= Fail Result:= Release Figure 42: Procedure Activate_CF_Process 3GPP .0 (2011-03) Procedure Activate_CF_Process Procedure in the MSC to initiate the process which handles call forwarding ACFP1(1) Signals to/from the left are to/from the originating exchange.

True) Wait_For_ ACM CAMEL phase 2 or higher supported? No CAMEL_OCH_ MSC_DISC3 See TS 23.078 Yes CAMEL_OCH_ MSC_DISC4 See TS 23.018 V10.078 No Leg1_status := Set-up CAMEL_MT_CF _LEG1_MSC (Leg1_status) Idle 4 See TS 23.078 Result? Leg1_only Abort Pass Perform call forwarding See TS 23.0 (2011-03) Process MT_CF_MSC Process in the MSC to handle call forwarding Idle MTCFMSC1(6) Signals to/from the left are to/from the parent process.078 4 Yes Result = Leg1_only? No Result= Pass? Yes CAMEL_CF_ Dialled_Services Fail See TS 23.078 See TS 23.078 ack(FTN) Idle Wait_For_ IAM CAMEL_ OCH_MSC1 No Result= Fail? Yes No Result= Reconnect? Yes 1 Initial Address CF cancelled 2 Perform Call Forwarding negative response See TS 23.1. signals to/from the right are to/from the destination exchange Perform call forwarding CAMEL_CF_ MSC_INIT See TS 23.078 Idle Idle Figure 43a: Process MT_CF_MSC (sheet 1) 3GPP .Release 10 116 3GPP TS 23.066 MOBILE_NUMBER_ PORTABILITY_ IN_OQoD Initial Address CAMEL_Store_ Destination_ Address (BOR.

078 Result? Pass Else Else Result? Pass See TS 23.078 CAMEL_ Stop_TNRy See TS 23.087 UUS_MSC_ Clear_UUS UUS_MSC_ Clear_UUS See TS 23. signals to/from the right are to/from the destination exchange Address Complete Connect See TS 23.0 (2011-03) Process MT_CF_MSC Process in the MSC to handle call forwarding Wait_For_ ACM MTCFMSC2(6) Signals to/from the left are to/from the parent process.087 See TS 23.078 CAMEL_ Start_TNRy See TS 23.Release 10 117 3GPP TS 23.018 V10.087 UUS_MSC_ Clear_UUS Reconnect Result? Fail Release Answer 2 Release Connect A Idle A Figure 43b: Process MT_CF_MSC (sheet 2) 3GPP .078 CAMEL_CF_ MSC_ANSWER CAMEL_CF_ MSC_ANSWER See TS 23.1.078 CAMEL_CF_ MSC_ALERTING Answer Result? Pass Else Address Complete Address Complete Wait_For_ Answer Answer See TS 23.

0 (2011-03) Process MT_CF_MSC Process in the MSC to handle call forwarding Wait_For_ACM.Release 10 118 3GPP TS 23. signals to/from the right are to/from the destination exchange unless marked otherwise Release Release From gsmSSF Int_O_ Release CAMEL phase 2 or higher supported? No Yes No CAMEL phase 2 or higher supported? Yes Yes Release cause= No answer from user? No 3 CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC_DISC4 CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC1 See TS 23. Wait_For_Answer MTCFMSC3(6) Signals to/from the left are to/from the parent process.078 No Result= Reconnect? Yes CAMEL_ Stop_TNRy See TS 23.078 Release Release Release 2 Release Release call resources Idle Figure 43c: Process MT_CF_MSC (sheet 3) 3GPP .1.018 V10.

078 CAMEL_CF_ Dialled_ Services Abort Result? Fail Pass Release call resources See TS 23.Release 10 119 3GPP TS 23.1.018 V10. signals to/from the right are to/from the destination exchange unless marked otherwise TNRy expired Internal 3 Release CAMEL_OCH_ MSC2 See TS 23.0 (2011-03) Process MT_CF_MSC Process in the MSC to handle call forwarding Wait_For _ Answer MTCFMSC4(6) Signals to/from the left are to/from the parent process.078 CAMEL_ OCH_MSC1 1 Yes Idle Result= Reconnect? No Perform Call Forwarding negative response 2 Idle Figure 43d: Process MT_CF_MSC (sheet 4) 3GPP .078 2 Release Result? Fail Reconnect Release See TS 23.

Release 10 120 3GPP TS 23. signals to/from the right are to/from the destination exchange unless marked otherwise Release Release Int_O_ Release From gsmSSF CAMEL_OCH_ MSC_DISC1 See TS 23.018 V10.078 Release Result= CAMEL Handling? No Yes Yes Result= CAMEL Handling? No Yes Result= Reconnect? No Release Release 2 Release Release call resources Idle * * * - - - Figure 43e: Process MT_CF_MSC (sheet 5) 3GPP .0 (2011-03) Process MT_CF_MSC Process in the MSC to handle call forwarding Wait_For_ Clear MTCFMSC5(6) Signals to/from the left are to/from the parent process.1.078 CAMEL_OCH_ MSC_DISC2 See TS 23.

0 (2011-03) Process MT_CF_MSC Process in the MSC to handle call forwarding A MTCFMSC6(6) CAMEL phase 4 or later control relationship exists? Yes See TS 23.1.Release 10 121 3GPP TS 23.018 V10.078 CAMEL_MT_ CF_LEG1_MSC (Leg1_status) Idle Figure 43f: Process MT_CF_MSC (sheet 6) 3GPP .078 No CAMEL_MT_ CF_LEG2_MSC Leg1_status := Active Wait_For_ Clear See TS 23.

Subscription_Check_HLR. Handle_OR_HLR_CF and CAMEL_HLR_INIT can set the negative response parameter which is used by the process 3GPP . and check if call can continue.2 Functional requirements of HLR 7.1 Process SRI_HLR Sheet 1: the procedures Check_Parameters.018 V10. CUG_SC1(1) No CUG info present? Yes GMSC supports CUG? Yes Yes No Outgoing Access present? No Pass Fail Figure 43bis: Macro CUG_Support_Check_GMSC 7.2. SCUDIF_Subscription_Check_HLR.2.0 (2011-03) Macrodefinition CUG_Support_Check_GMSC Macro to check support of CUG in GMSC.Release 10 122 3GPP TS 23.2. if needed.1.

it is specified in 3GPP TS 23. processing continues from the "No" exit of the test "Result=Forward". It is specified in 3GPP TS 23. If the HLR does not support CCBS.018 V10. processing continues from the "yes" exit of the test "Result = Continue ?". and modifies it if needed. Sheet 3: the procedure CLI_HLR_Set_CLI is specific to Enhanced CLI Handling. If the HLR does not support Optimal Routeing. This procedure gets the result from the Subscription_Check_HLR procedure. If the HLR does not support Optimal Routeing. If the HLR does not support CAMEL.079 [13]. It is specified in 3GPP TS 23.079 [13]. Sheet 2: the procedure CCBS_Handling_HLR is specific to CCBS. If the HLR does not support SCUDIF. processing continues from the "No" exit of the test"Result=CSI active?". and modifies it if needed. Sheet 5: the procedure SCUDIF_Check_Second_Service_after_PRN is specific to SCUDIF. processing continues from the "No" exit of the test"Result=Fail?". processing continues from the "Yes" exit of the test "Result = OK?". it is specified in 3GPP TS 23.Release 10 123 3GPP TS 23. 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. 3GPP . Sheet 3: the procedure SCUDIF_Set_Correct_PLMN_BC is specific to SCUDIF. processing continues from the "No" exit of the test "Result=CSI active?". processing continues from the "Yes" exit of the test "Result=Call allowed?". the test "Result = CSI Active ?" applies to the result of the CAMEL_CSI_Check_HLR procedure. This negative response parameter is global data. If the HLR does not support CAMEL.172 [38].081 [14]. it is specified in 3GPP TS 23.078 [12]. it is specified in 3GPP TS 23. Sheet 6: the test "Forwarding enquiry" is specific to Support of Optimal Routeing. accessible by the process SRI_HLR. Sheet 1: the procedure CAMEL_HLR_INIT is specific to CAMEL.172 [38].172 [38]. This negative response parameter is global data. the test "Alerting pattern required" and the task "Set Alerting Pattern" are omitted. If the HLR does not support CAMEL phase 4 or later. If the HLR does not support Optimal Routeing. If the HLR does not support SCUDIF. Sheet 6: the procedure CAMEL_CSI_Check_HLR is specific to CAMEL. This negative response parameter is global data. it is specified in 3GPP TS 23. Sheet 2: the procedure SCUDIF_CAMEL_CSI_Check_HLR is specific to SCUDIF. If the HLR does not support SCUDIF. Sheet 2: the test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. Sheet 2: the procedure CAMEL_CSI_Check_HLR is specific to CAMEL. processing continues from the "No" exit of the test "Result=CSI active?". Sheet 5: 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.078 [12]. If the HLR does not support CUG. Sheet 5: the procedure Forward_CUG_Check is specific to CUG. processing continues from the "No" exit. If the HLR does not support CAMEL. processing continues from the "No" exit of the test.093 [23]. accessible by the process SRI_HLR. If the HLR does not support CAMEL phase 4 or later. the test "Result = Fail ?" applies to the result of the Subscription_Check_HLR procedure.078 [12].0 (2011-03) SRI_HLR to construct the Send Routeing Info negative response message. it is specified in 3GPP TS 23. This procedure gets the result from the CAMEL_CSI_Check_HLR procedure.1. processing continues from the "Set_PLMN_BC" exit of the test "Result ?". it is specified in 3GPP TS 23. Sheet 3: the procedure OR_HLR_Interrogate_VLR is specific to Optimal Routeing. Sheet 1: the procedure SCUDIF_Subscription_Check_HLR is specific to SCUDIF. it is specified in 3GPP TS 23.172 [38]. Sheet 2: the test "Suppress CCBS Handling?" is specific to CAMEL phase 4 or later. it is specified in 3GPP TS 23. accessible by the process SRI_HLR. Sheet 1: the procedure Handle_OR_HLR_CF is specific to Support of Optimal Routeing. Sheet 3: if the HLR does not support Network Indication of Alerting. If the HLR does not support CAMEL. If the HLR does not support SCUDIF. processing continues from the "No" exit. processing continues from the "No" exit of the test "Result=Forward?".

Sheet 6: the procedure SCUDIF_Check_Second_Service_before_Negative_Response can set the negative response parameter which is used by the process SRI_HLR to construct the Send Routeing Info negative response message.172 [38]. processing continues from the "No" exit. Sheet 6: the procedure SCUDIF_Check_Second_Service_before_Negative_Response is specific to SCUDIF.2. If the HLR does not support SCUDIF.078 [12].078 [12]. it applies a default basic service according to the requirements of the operator. This negative response parameter is global data. the procedure sets the negative response to "Data missing". The test "Suppress CUG Handling?" is specific to CAMEL phase 4 or later. Sheet 7: the procedure SCUDIF_Check_Second_Service_when_Forwarded is specific to SCUDIF. processing continues from the "Yes" exit of the test "Result = Continue ?".1) shall delay the sending of the PRN message till completion of any on-going Location Update procedure.007 [30]. 7.3 Procedure Subscription_Check_HLR The HLR derives the possible PLMN bearer capability to populate the parameter in the Provide Roaming Number request according to the rules defined in 3GPP TS 29. they are specified in 3GPP TS 23. accessible by the process SRI_HLR. Sheet 7: the procedures CAMEL_T_CSI_CHECK_HLR and CAMEL_O_CSI_CHECK_HLR are specific to CAMEL.Release 10 124 3GPP TS 23. If the HLR does not support SCUDIF. If the HLR does not support CAMEL. If the HLR receives Send Routeing Information from the gsmSCF and the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request.018 V10.2. If the HLR does not support SCUDIF. 7. processing continues from the "No" exit of the test "Result=CSI active?". it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. the test "Result = CSI Active ?" applies to the result of the CAMEL_CSI_Check_HLR procedure. Sheet 7: the procedure SCUDIF_Set_Second_Service_when_Forwarded is specific to SCUDIF. NOTE The information element “gsmSCF Initiated Call” in Send Routeing Information serves as an indication to the HLR that this Send Routeing Information is sent by the gsmSCF. and modifies it if needed. it is specified in 3GPP TS 23. 3GPP . 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.172 [38]. processing continues from the "No" exit. it applies the corresponding PLMN bearer service or teleservice for handling the call. If the HLR does not support SCUDIF.172 [38].2.2 Procedure Check_Parameters If any parameters required by the rules in clause 8 are missing from the message. Sheet 7: A HLR implementing the Mobile Terminating Roaming Retry feature (see sub-clause 5. processing continues from the "Fail" exit of the test "Result ?". it is specified in 3GPP TS 23. then the HLR shall apply basic service TS11. This procedure gets the result from the CAMEL_CSI_Check_HLR procedure. Sheet 7: the procedure CAMEL_D_CSI_CHECK_HLR is specific to CAMEL phase 3 or later.2. The test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. If the HLR does not support CAMEL phase 4 or later. If the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request. the procedure sets the negative response to "Unexpected data value". processing continues from the "Yes" exit of the test "Result = Continue ?".2. it is specified in 3GPP TS 23. If the HLR is able to determine the PLMN bearer capability or equivalent ISDN compatibility information to be sent to the VLR in the Provide Roaming Number request. If the HLR does not support CAMEL phase 4 or later.078 [12]. Refer to 3GPP TS 23.1. If any parameter has a value which is not in the set of values expected for the parameter.172 [38].0 (2011-03) Sheet 6: the procedure SCUDIF_CAMEL_CSI_Check_HLR is specific to SCUDIF.

The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later. The negative response "CUG reject" indicates whether the reason is: Incoming calls barred within CUG. processing continues from the "Yes" exit of the test "Result = Pass?". The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later.2.8 7.2.5 Procedure PRN_Error_HLR The procedure CCBS_Report_PRN_Failure is specific to CCBS.2.2.018 V10.11 Procedure Handle_CFNRc The test "Mobile subscriber not reachable" refers to the value of the indicator returned by the process MAF010. The subscriber record is marked as MS purged. according to the cause returned by the procedure IC_CUG_Check. The subscriber record is marked as MSC area restricted.093 [23].Release 10 125 3GPP TS 23.116 [24]. it is specified in 3GPP TS 23. The subscriber is marked as deregistered because of subscription restrictions on roaming.2.7 7. The subscriber record is marked as Roaming Restricted due to Unsupported Feature.2. according to the result returned by the procedure Check_IC_Barring. processing continues from the "Yes" exit of the test "Result = Pass?".9 7. 7.2. Requested basic service violates CUG constraints.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.6 7. The procedure Super_Charged_SRI_Error_HLR is specific to Super-Charger.078 [12]. it is specified in 3GPP TS 23.2. 3GPP .2.2. the following tests are on the value of the Provide Roaming Number negative response.078 [12]. If the GMSC does not support CAMEL Phase 3 or later. 7. 7. If the GMSC does not support CAMEL Phase 3 or later. it is specified in 3GPP TS 23.1. If the HLR does not support Super-Charger.10 Procedure Forward_CUG_Check Void 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. it is specified in 3GPP TS 23. processing continues from the "No" exit of the test "Result=Purged?". The procedure does not return a value. If the HLR does not support Optimal Routeing. Subscriber not member of CUG. 7.2.2.0 (2011-03) The negative response "Call barred" indicates whether the reason is operator determined barring or supplementary service barring.2.2.2.2. processing starts with the test "Negative response=Facility not supported?".

172 Result= Fail? No Yes See TS 23.079 OR_HLR_CF 6 Yes Result= Fail? No Yes Result= Forward? No See TS 23.Release 10 126 3GPP TS 23. signals to/from the right are to/from the VLR Idle Send Routeing Info Check_ Parameters Result= Pass? No Yes Subscription_ Check_HLR SCUDIF_Subscription _Check_HLR 7 See TS 23.018 V10.078 CAMEL_ HLR_I NIT Yes Result= Fail? No 3 1 2 1 Figure 44a: Process SRI_HLR (sheet 1) 3GPP .0 (2011-03) Process SRI_HLR Process in the HLR to handle a request for routeing inf ormation SRI_HLR1(7) Signals to/f rom the left are to/from the GMSC or the gsmSCF.1.

078 CAMEL_ CSI_Check_ HLR 2 See TS 23.018 V10.093 Yes Result = Forward No No Result = OK Yes 5 1 2 1 Figure 44b: Process SRI_HLR (sheet 2) 3GPP .1.172 Yes Result= CSI active? No Yes Result= CSI active? No gsmSCF Initiated No Call? 4 4 Yes Yes Suppress CCBS Handling? No CCBS_Handling_ HLR See TS 23.0 (2011-03) Process SRI_HLR Process in the HLR to handle a request for routeing information 3 SRI_HLR2(7) Signals to/from the left are to/from the GMSC or the gsmSCF.078 CAMEL_ CSI_Check_ HLR See TS 23.172 SCUDIF_CAMEL_ CSI_Check_ HLR SCUDIF_CAMEL_ CSI_Check_HLR See TS 23.Release 10 127 3GPP TS 23. signals to/from the right are to/from the VLR First_ Forwarding_ HLR Yes Result= Fail? No Yes Result= Forward? No See TS 23.

018 V10.Release 10 128 3GPP TS 23.1.0 (2011-03) Process SRI_HLR Process in the HLR to handle a request for routeing inf ormation SRI_HLR3(7) Signals to/from the left are to/from the GMSC or the gsmSCF.079 Yes Result= Fail? No Result= Forward? Yes No 2 1 SCUDIF_Set_ Correct_PLMN_BC Result Set_PLMN_BC SRI_Ack Continue Yes 4 PLMN BC= NULL? No Set PLMN BC parameter Alerting Pattern required? Yes Set Alerting Pattern No See TS 23. signals to/from the right are to/from the VLR 5 OR_HLR_ Interrogate_VLR See TS 23.081 CLI_HLR_ Set_CLI 8 Figure 44c: Process SRI_HLR (sheet 3) 3GPP .

Release 10 129 3GPP TS 23.0 (2011-03) Process SRI_HLR Process in the HLR to handle a request for routeing inf ormation SRI_HLR4(7) 8 Pre-paging supported in HLR? Yes Pre-paging supported in GMSC? Yes No No Set Pre-paging supported Provide Roaming Number Wait_For_ MSRN Figure 44d: Process SRI_HLR (sheet 4) 3GPP .1.018 V10.

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

Release 10

131

3GPP TS 23.018 V10.1.0 (2011-03)

Process SRI_HLR
Process in the HLR to handle a request for routeing inf ormation

SRI_HLR6(7)

11

Yes Forwarding enquiry? No CAMEL_ CSI_Check_ HLR 1

See TS 23.078

SCUDIF_CAMEL_ CSI_Check_HLR

See TS 23.172

Result= CSI active? Yes

No

Called party SS interaction violation

Set negative response: CUG reject

SCUDIF_Check_ Second_Service_ before_negative_ response

See TS 23.172

Result?

Pass

fail

Second_Interrogation

6

7

Send Routeing Info ack

Send Routeing Info negative response

Idle

Idle

Figure 44f: Process SRI_HLR (sheet 6)

3GPP

Release 10

132

3GPP TS 23.018 V10.1.0 (2011-03)

Process SRI_HLR
Process in the HLR to handle a request for routeing inf ormation 9

SRI_HLR7(7)

Routeing address:= FTN

SCUDIF_Set_Second_ Service_when_ Forwarded

See TS 23.172

Result= Continue? No 10 Yes Forwarding enquiry? No CAMEL_T_ CSI_CHECK_ HLR Yes

See TS 23.078

See TS 23.078

CAMEL_O_ CSI_CHECK_ HLR

See TS 23.078

CAMEL_D_ CSI_CHECK_ HLR

SCUDIF_Check_ Second_Service_ when_Forwarded

See TS 23.172

Result= Continue? No Yes Send Routeing Info ack 7

Idle

Figure 44g: Process SRI_HLR (sheet 7)

3GPP

Release 10

133

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Check_Parameters
Procedure to check the parameters of a received message

Chk_Par1(1)

All required parameters present? Yes

No

All parameter values acceptable? Yes

No

Set negative response: Data missing

Set negative response: Unexpected data value

Result:= Pass

Result:= Fail

Figure 45: Procedure Check_Parameters

3GPP

Release 10

134

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Subscription_Check_HLR
Procedure in the HLR to make subscription checks for a mobileterminated call

SC_HLR1(1)

MS known? Yes

No

Set negative response: Unknown subscriber

Number changed? No

Yes

See TS 29.007

Derive requested basic service

Set negative response: Number changed

Requested service provisioned? Yes

No

gsmSCF Initiated Call? Yes Yes

No Set negative response: service not provisioned Bearer service or Teleservice

Suppress ICB? No Check_IC_ Barring

Result= Call barred? No

Yes

gsmSCF Initiated Call? Yes Yes

No

Set negative response: Call barred

Suppress CUG? No

IC_CUG_ Check

Result= Call allowed? Yes

No

Set negative response: CUG reject

Result:= Pass

Result:= Fail

Figure 46: Procedure Subscription_Check_HLR

3GPP

Release 10

135

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure First_Forwarding_HLR
Procedure in the HLR to handle call forwarding before interrogation of the VLR

FF_HLR1(1)

Handle_CFU

Result= Fail? No Yes

Yes

Result= Forward? No

Set negative response: Forwarding violation

No

MS not reachable? Yes

Handle_CFNRc

Result= Fail? No

Yes

Set negative response: Forwarding violation No

Result= Forward? Yes

Set negative response: Absent subscriber

Result:= Forward

Result:= Continue

Result:= Forward

Result:= Fail

Figure 47: Procedure First_Forwarding_HLR

3GPP

018 V10.093 Negative response=OR not allowed?? Yes No Set negative response: OR not allowed Yes Negative response=Facility not supported? No Yes No Negative response=Absent subscriber? Set negative response: Facility not supported Negative response=No roaming number? No Yes Handle_CFNRc Handle_CFNRc Set negative response: System failure Fail Result? Forward Not reachable Forward Result? Fail Not reachable Set negative response: Forwarding violation Set negative response: Forwarding violation Super_Charged_ SRI_Error_ HLR Yes Result= Purged? No Set negative response: Absent subscriber Set negative response: System failure Result:= Forward Result:= Fail Result:= Fail Figure 48: Procedure PRN_Error_HLR 3GPP .1.Release 10 136 3GPP TS 23.0 (2011-03) Procedure PRN_Error_HLR Procedure in the HLR to handle a negative response for a roaming number request CCBS_Report_ PRN_Failure PRN_E_H1(1) See TS 23.

Release 10 137 3GPP TS 23.1.085 Figure 49: Procedure Forward _CUG_Check Figure 50: Void 3GPP .0 (2011-03) Procedure Forward_CUG_Check Procedure to carry out CUG authorisation check for a forwarded call FWD_CUG1(1) No Yes CUG info provided in routeing information request Yes No Perform Forwarding CUG authorisation CUG provisioned for forwarding subscriber against requested basic service As defined in TS 23.085 Pass CUG authorisation result Fail Result:= Call allowed Result:= Call barred Result:= Call allowed Update CUG info As defined in TS 23.018 V10.

018 V10.Release 10 138 3GPP TS 23.1.0 (2011-03) Procedure Check_IC_Barring Procedure to check call request against SS barring and ODB categories CIB1(2) Yes No Yes No No Yes MS registered in HPLMN country? Operator determined BAIC imposed? Operator determined BIC-Roam imposed? 1 Yes No No Yes MS registered in HPLMN zone? Operator determined BIC-RoamHZ imposed? Result:= Call barred (ODB) 1 Figure 51a: Procedure Check_IC_Barring (sheet 1) 3GPP .

1.0 (2011-03) Procedure Check_IC_Barring Procedure to check call request against SS barring and ODB categories 1 CIB2(2) Initiate handling of BAIC To process MAF022 Wait_For_ BAIC_ Response Continue call handling From process MAF022 Yes Call barred? No Initiate handling of BIC-Roam To process MAF023 Wait_For_ BIC-Roam_ Response Continue call handling From process MAF023 Yes Call barred? No Result:= Call barred (SS barring) Result:= Call allowed Figure 51b: Procedure Check_IC_Barring (sheet 2) 3GPP .Release 10 139 3GPP TS 23.018 V10.

Release 10 140 3GPP TS 23.018 V10.1.0 (2011-03) Procedure IC_CUG_Check Procedure to carry out CUG authorisation check for an incoming (MT) call IC_CUG1(1) Signals to/from the right are to/from the process CUG_MAF015 HLR supports CUG? Yes No No SRI contains CUG info? Yes Yes Outgoing Access present? No incoming call Wait_For_ CUG_Response 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 3GPP .

078 No Result = Pass? Yes initiate handling of CFU Wait_For_ CFU_Result continue call handling Yes Error? No Normal call? No Yes Result:= Fail Result:= Forward Result:= Continue Figure 53: Procedure Handle_CFU 3GPP .0 (2011-03) Procedure Handle_CFU Procedure in the HLR to handle Call Forwarding Unconditional H_CFU1(1) Signals to/from the right are to/from the process MAF007 CAMEL_CHECK _SII2_CDTI See TS 23.Release 10 141 3GPP TS 23.018 V10.1.

1.0 (2011-03) Procedure Handle_CFNRc Procedure in the HLR or VLR to handle Call Forwarding on Mobile Subscriber Not Reachable H_CFNRc1(1) Signals to/from the right are to/from the process MAF010 CAMEL_CHECK _SII2_CDTI See TS 23.Release 10 142 3GPP TS 23.078 No Result = Pass? Yes initiate handling of CFNRc Wait_For_ CFNRc_Result continue call handling Yes Error? No Yes Mobile subscriber not reachable? No Result:= Fail Result:= Forward Result:= Not reachable Figure 54: Procedure Handle_CFNRc 3GPP .018 V10.

2.3. sheet 7: the procedure CAMEL_SET_SOA is specific to CAMEL. Sheet 4: "Location cancelled" cause is set when VMSC receives Cancel Location while paging. Sheet 3. sheet 3. Sheet 2. sheet 6. Sheet 8: this process communicates with the matching instance of the process ICH_VLR. If the VLR does not support Super-Charger.0 (2011-03) 7. sheet 3.2.1 Process PRN_VLR Sheet 1: the procedure Check_Parameters is specified in subclause 7. the paging procedure can be completed before the minimum timer value for the Provide Roaming Number operation timer in the HLR has elapsed. Sheet 2. sheet 6.3. it is specified in 3GPP TS 23. Sheet 2. or the MS failed IMEI checking. sheet 4: A VLR not supporting the flag "Subscriber data dormant" shall behave as if this flag is set to false. sheet 8: the state variables PAR pending.3. during the handling of the Process Access Request. Sheet 2.11.1. 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. PAR successful and Fatal PAR error are global data. Sheet 8: the test " Fatal PAR error?" takes the "Yes" exit if: the MS failed authentication.2. 3GPP . processing continues from the "No" exit of the test "Result=Purged?". Sheet 1: the procedure Check_Reason_In_Serving_Network_Entity is specific to Super-Charger. sheet 3. Sheet 7. Sheet 2. which is linked by the MSRN.Release 10 143 3GPP TS 23. and there is an association established for the MS between the MSC/VLR and the SGSN.2. sheet 7: the procedure CCBS_Handle_PRN is specific to CCBS. which is linked by the MSRN. sheet 3.081 [14]. it is specified in 3GPP TS 23. It is specified in 3GPP TS 23. Sheet 4: the procedure Search_For_MS_VLR is specified in subclause 7. sheet 6. sheet 7: the procedure CLI_PRN_VLR is specific to Enhanced CLI Handling. sheet 4: the process Fetch_Authentication_Sets_VLR is specified in subclause 7.1. sheet 4: the number of unused authentication sets which triggers the VLR to request further authentication sets from the HLR is an operator option. it is specified in 3GPP TS 23. or as an operator option.3 Functional requirements of VLR 7. or the HLR returned an "Unknown subscriber" error.2. sheet 7: the task "Store alerting pattern (if received)" is executed only if the VLR supports the feature Network Indication of Alerting.2.093 [23]. accessible to the matching instance of the process ICH_VLR. Sheet 3.2. sheet 6.078 [12]. Sheet 4: the test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented.116 [24].018 V10.

Release 10 144 3GPP TS 23. If the test "Report upon change of service area" takes the no exit.2.3 Process Restore_Subscriber_Data_VLR Process PSI_VLR Sheet 1: the procedure Check_Parameters is specified in subclause 7. The test "Report upon change of service area" takes the yes exit if the MSC has performed the Location Reporting Control procedure with the Request Type IE set to "change of service area" [26]. 7. the VLR treats this as a missing parameter. 7.3.2.0 (2011-03) 7.5 Procedure Active_Info_Retrieval_VLR Sheet 1: the test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented. - The output signal Send MS information towards the SGSN indicates that the required information is mobile location information.3. the age of the location information. MS classmark and IMEI.1.2.2. 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).2. 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). If the HLR requests none of location information subscriber state.2. and there is an association established between the MSC/VLR and the SGSN. 3GPP . and the VLR configuration requires paging via the SGSN during VLR restoration. the age of the location information. Sheet 2: the test "Active retrieval required" takes the "Yes" exit if any one or more of current location. MS classmark or IMEI is indicated in the Provide Subscriber Info request.4 - Procedure Retrieve_Location_Info_VLR The test "Retrieve location info from SGSN" takes the "Yes" exit if: the Gs interface is implemented. Sheet 2: the output signal Page MS towards the SGSN includes or omits the Location area identity parameter depending on the availability of this information. 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.018 V10. If it is omitted. the location number. the location number.2. 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.3. then the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct".3. - The derivation of the location number. geodetic information and geographical information derived from the service area ID or cell ID if the VLR is capable of doing so (the mapping from service area ID or cell ID to location number is networkspecific and outside the scope of the UMTS and GSM standards). the signal Page MS is sent to every SGSN to which the VLR is connected.2 7.

018 V10. Idle Provide Roaming Number Check_ Parameters 1 No Result= Pass? Yes No OR indicator present? Yes OR supported? Yes No Convert PLMN BC to basic service If PLMN BC was included in the Provide Roaming Number No Set negative response: OR not allowed Service supported by VLR? Yes Pre-paging supported in VLR? No No Pre-paging allowed? Yes Yes IMSI known in VLR? No Check_Reason_ In_Serving_ Network_Entity Yes IMSI known in VLR? No Check_Reason_ In_Serving_ Network_Entity Yes Set negative response: Facility not supported Provide Roaming Number negative response 2 4 See TS 23.Release 10 145 3GPP TS 23.1.116 No Result= Purged? Yes No Result= Purged? Yes 3 1 5 1 Idle Figure 55a: Process PRN_VLR (sheet 1) 3GPP .0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number PRN_VLR1(8) Signals to/from the left are to/from the HLR.

0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number True Signals to the left are to the HLR.081 CCBS_Handle_ PRN Provide Roaming Number ack MT Roaming Retry Supported No Idle 6 See TS 23.018 V10.078 PLMN BC.1. ISDN BC. Set negative response: Purged MS 1 2 PRN_VLR2(8) Subscriber data dormant False IMSI detached True False Yes Roaming in LA allowed? MSRN available? Yes MSC per VLR 1 Yes >1 Set negative response: No roaming number Received MSC number= Stored MSC number? Confirmed by radio contact True Use received MSC number for MSRN Allocate MSRN Use stored MSC number for MSRN Set negative response: Absent subscriber 1 No MT Roaming Retry Supported Yes Data confirmed by HLR? False True No Yes Fetch_ Authentication_ Sets_VLR Restore_ Subscriber_ Data_VLR 9 9 No No 9 More authentication sets needed? No False CAMEL_ SET_SOA Store compatibility info Store Alerting Pattern (if received) CLI_PRN_ VLR See TS 23. ISDN LLC & ISDN HLC (as available) See TS 23.093 Yes 3GPP .Release 10 146 3GPP TS 23.

IMSI detached:=False Allocate LMSI If used by VLR PLMN BC.018 V10. Data confirmed by HLR:=False.1.078 1 CAMEL_ SET_SOA Create IMSI record Location info confirmed in HLR:= False Only if >1 MSC per VLR Confirmed by radio contact:=False. MSRN available Yes Allocate MSRN No Set negative response: No roaming number See TS 23.0 (2011-03) Figure 55b: Process PRN_VLR (sheet 2) Process PRN_VLR Process in the VLR to handle a request for a roaming number 3 PRN_VLR3(8) Signals to the left are to the HLR. ISDN LLC & ISDN HLC (as available) Store PgA (if received and supported) CLI_PRN_ VLR See TS 23.081 Store compatibility info Store Alerting Pattern (if received) 6 False Data confirmed by HLR? True More authentication sets needed? Yes No CCBS_Handle_ PRN Provide Roaming Number ack Fetch_ Authentication_ Sets_VLR Restore_ Subscriber_ Data_VLR Idle See TS 23.093 Figure 55c: Process PRN_VLR (sheet 3) 3GPP . ISDN BC.Release 10 147 3GPP TS 23.

018 V10.Release 10 148 3GPP TS 23.0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number 4 PRN_VLR4(8) Signals to the right are to the MSC. True Subscriber data dormant False Yes IMSI detached? No No Roaming in LA allowed? Yes No Yes Location area ID known? True Data confirmed by HLR? False No Yes Fetch_ Authentication_ Sets_VLR Restore_ Subscriber_ Data_VLR Search_For_ MS_VLR Yes Page MS Page type= circuit-switched call More authentication sets needed? Paging via SGSN possible? Set negative response: Purged MS 1 No Yes Set Paging via SGSN possible Result= Pass? No Yes Absent subscriber? No Set negative response: Absent subscriber Location cancelled? No Yes Set negative response: Purged MS 1 Wait_For_ Access_ Request 1 7 Figure 54d: Process PRN_VLR (sheet 4) 3GPP .1.

ISDN BC.0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number 5 PRN_VLR5(8) Create IMSI record Location info confirmed in HLR:= False Only if >1 MSC per VLR Confirmed by radio contact:=False. ISDN LLC & ISDN HLC (as available) Fetch_ Authentication_ Sets_VLR Restore_ Subscriber_ Data_VLR Search_For_ MS_VLR Yes Result= Pass? No Yes Absent subscriber? Set negative response: Absent subscriber No 1 7 Wait_For_ Access_ Request Figure 54e: Process PRN_VLR (sheet 5) 3GPP . IMSI detached:=False Allocate LMSI If used by VLR Store compatibility info PLMN BC. Data confirmed by HLR:=False.018 V10.Release 10 149 3GPP TS 23.1.

ISDN BC.Release 10 150 3GPP TS 23.018 V10. Page MS via SGSN Process Access Request Page MS negative response No Page MS To SGSN MSRN available? Yes Wait_For_ Access_ Request 1 Yes Busy subscriber? No Yes MSC per VLR >1 Received MSC number= Stored MSC number? No False Confirmed by radio contact True Use received MSC number for MSRN Use stored MSC number for MSRN Set negative response: System failure Yes Absent Subscriber? No 7 Allocate MSRN Process Access Request negative response CAMEL_ SET_SOA See TS 23. ISDN LLC & ISDN HLC (as available) 1 Store Alerting Pattern (if received) CLI_PRN_ VLR See TS 23.0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number Wait_For_ Access_ Request PRN_VLR6(8) Signals to the left are to the HLR.078 Set negative response: No roaming number Set negative response: Absent subscriber Store compatibility info PLMN BC.081 CCBS_Handle_ PRN See TS 23. signals to/from the right are to/from the MSC unless shown otherwise.093 Provide Roaming Number ack 8 Figure 54f: Process PRN_VLR (sheet 6) 3GPP .1.

PAR successful:=False. No MSRN available? Yes Set negative response: No roaming number >1 Yes Received MSC number= Stored MSC number? No False Confirmed by radio contact True Use received MSC number for MSRN Use stored MSC number for MSRN 1 MSC per VLR 1 Allocate MSRN CAMEL_ SET_SOA See TS 23.1.Release 10 151 3GPP TS 23. ISDN BC.093 Provide Roaming Number ack PAR pending:=False. ISDN LLC & ISDN HLC (as available) Store Alerting Pattern (if received) CLI_PRN_ VLR See TS 23.0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number 7 PRN_VLR7(8) Signals to the left are to the HLR.081 CCBS_Handle_ PRN See TS 23.078 Store compatibility info PLMN BC.018 V10. Fatal PAR error:=False Idle Figure 54g: Process PRN_VLR (sheet 7) 3GPP .

Release 10 152 3GPP TS 23.0 (2011-03) Process PRN_VLR Process in the VLR to handle a request for a roaming number 8 PRN_VLR8(8) Signals to/from the left are to/from the process ICH_VLR.018 V10.1. signals to/from the right are to/from the MSC PAR pending:= True Process_ Access_ Request_VLR Result= Pass? Yes PAR successful:= True PAR successful:= False No PAR pending:= False PAR pending:= False No PAR Completed Fatal PAR error? Yes Wait_For_ Call_Arrival Fatal PAR error:= True Fatal PAR error:= False Call arrived Radio connection released PAR successful:= False PAR Completed Call arrived Fatal PAR error:= False Idle Idle Figure 54h: Process PRN_VLR (sheet 8) 3GPP .

018 V10.0 (2011-03) Process Restore_Subscriber_Data_VLR Process in the VLR to restore subscriber data RSD_VLR1(1) Signals to/from the left are to/from the HLR Restore Data Wait_For_ Data Restore Data ack Restore Data negative response Update Subscriber Data Update HLR number Update MS Not Reachable indicator If received from HLR Data confirmed by HLR:=True Figure 56: Process Restore_Subscriber_Data_VLR 3GPP .1.Release 10 153 3GPP TS 23.

1.018 V10. signals to/from the right are to/from the MSC Idle Provide Subscriber Info Check_ Parameters No Result= Pass? Yes No IMSI known in VLR? Yes Subscriber state requested? Yes Yes IMSI detached? No Roaming in LA allowed? Yes Set subscriber state requested Subscriber state:= Network determined not reachable Subscriber state:= Assumed idle No No No Subscriber state requested? Yes Location info requested? Yes Location info:= Stored location info No Obtain Subscriber Info Provide Subscriber Info ack Provide Subscriber Info negative response Wait_For_ MSC_Response Idle Idle Figure 57a: Process PSI_VLR (sheet 1) 3GPP .Release 10 154 3GPP TS 23.0 (2011-03) Process PSI_VLR Process in the VLR to handle a request from the HLR for subscriber information PSI_VLR1(2) Signals to/from the left are to/from the HLR.

018 V10.Release 10 155 3GPP TS 23.1. signals to/from the right are to/from the MSC Obtain Subscriber Info ack Subscriber state received? Yes No Set subscriber state Active retrieval required? Yes No Location info requested? Yes No Active_Info_ Retrieval_ VLR Retrive_ Location_ Info_VLR Provide Subscriber Info ack Idle Figure 57b: Process PSI_VLR (sheet 2) 3GPP .0 (2011-03) Process PSI_VLR Process in the VLR to handle a request from the HLR for subscriber information Wait_For_ MSC_Response PSI_VLR2(2) Signals to/from the left are to/from the HLR.

geodetic information and geographical information Figure 58: Procedure Retrieve_Location_Info_VLR 3GPP .1.Release 10 156 3GPP TS 23.0 (2011-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 Yes Retrieve location info from SGSN? No Send MS information Location info:= Stored location info Wait_For_ SGSN_Response Send MS Information negative response Send MS Information ack Location info:= Stored location info Location info:= Received location info Derive location number.018 V10.

018 V10.0 (2011-03) Procedure Active_Info_Retrieval_VLR Procedure in the VLR to retrieve the current location information for a subscriber AIR_VLR1(2) Signals to/from the right are to/from the MSC Set information required Paging via SGSN possible? Yes No Set paging via SGSN possible No Location area ID known? Yes Page type= Active information retrieval Search for MS Page type= Active information retrieval Page MS Wait_For_ Search_ Result Wait_For_ Page_ Result Figure 59a: Procedure Active_Info_Retrieval_VLR 3GPP .1.Release 10 157 3GPP TS 23.

0 (2011-03) Procedure Active_Info_Retrieval_VLR Procedure in the VLR to retrieve the current location information for a subscriber Wait_For_ Search_ Result AIR_VLR2(2) Search for MS ack Search for MS negative response No Search for MS via SGSN Roaming in LA allowed? Yes Page MS Subscriber state:=Not reachable Wait_For_ Search_ Result No Yes Location info received? No Yes Location info received? Location info:= Received location info Location info:= Stored location info Location info:= Received location info Location info:= Stored location info Wait_For_ Page_ Result Page MS ack Page MS negative response Page MS via SGSN Yes Location info received? No Page MS Location info:= Received location info Location info:= Stored location info Wait_For_ Page_ Result Figure 59b: Procedure Active_Info_Retrieval_VLR (sheet 2) 3GPP .Release 10 158 3GPP TS 23.1.018 V10.

The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call.5 Process RCL_MSC This process runs when the MSC receives a Page MS message or a Search for MS message with a Page type indicating Active Info Retrieval.4.2.2 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. 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. or completed the location registration procedure.2.1.4.4 Process OSI_MSC If the MS is engaged on a circuit-switched call.413 [27]) with the Request Type IE set to "Change of service area". 7.Release 10 159 3GPP TS 23. or completed the location registration procedure.2.4.4. or sent a CM service request for anything other than a circuit-switched call.2.1 7. 7. If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct".7 Procedure Active_Info_Retrieval_Search_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.4.6 Procedure Active_Info_Retrieval_Page_MSC The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network.2.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.413 [26]) with the Request Type IE set to "Change of service area". The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network. 3GPP .018 V10. the state is busy.4. 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".4 Functional requirements of MSC 7. or sent a CM service request for anything other than a circuit-switched call. 7.2.4. The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network.2. 7. The signal input "MS connection established" indicates that the MS has responded to paging.2. 7. The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call. The signal input "MS connection established" indicates that the MS has responded to paging. 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.0 (2011-03) 7.

Process Prepage_MSC Process in the MSC to handle a pre-paging request Idle PP_MSC1(1) Signals to/from the left are to/from the VLR.018 V10. signals to the right are to the BSS Page MS Search for MS Prepaging_ Search_for_ MS_MSC Yes Result= Pass? No Idle Prepaging_ Page_MS_MSC Yes Result= Pass? No Idle Process_ Acces_ Request_MSC Result= Pass? Yes Start radio guard timer No Idle Wait_For_ Call_Arrival Call arrived Radio guard timer expired Release transaction Radio connection released Internal Release transaction BSS released the radio resource Stop radio guard timer Radio connection released Idle Figure 60: Process Prepage_MSC 3GPP .0 (2011-03) 7.Release 10 160 3GPP TS 23.8 Procedure Retrieve_IMEI_If_Required If the IMEI is retrieved using an existing connection between the MS and the network (as opposed to a connection which has been set up for active information retrieval). the Release transaction signal is relayed to the MSC process which is supervising the existing connection.1.2.4.

signals to/from the right are to/from the VLR unless marked otherwise Location No area ID known? Yes Yes MS connection exists? No No Yes In specified location area Page MS busy? No Set negative response: Busy Subscriber Page MS via SGSN Start Page response timer Wait_For_ Page_ Response Set access connection status Result:= Pass Page MS negative response Result:= Fail Yes Set negative response: Unknown LAI PPPMS_M1(1) Paging via SGSN possible? Cancel Location MS connection established Page response timer expired CM Service Request CM Service Request For circuitswitched call To process OCH_MSC Set negative response: Location Cancelled Page MS negative response Result:= Fail Set access connection status Set negative response: Absent Subscriber Page MS negative response Set negative response: Busy Subscriber (NDUB) Page MS negative response Result:= Fail Result:= Pass Result:= Fail Figure 61: Procedure Prepaging_Page_MS_MSC 3GPP .Release 10 161 3GPP TS 23.0 (2011-03) Procedure Prepaging_Page_MS_MSC Procedure in the MSC to page an MS in a specified location area Signals to/from the left are to/from the BSS.1.018 V10.

signals to/from the right are to/from the VLR unless marked otherwise Paging via SGSN possible? Yes MS connection exists? No No Yes Page MS via SGSN In all location areas or in PgA if PgA received and supported Set access connection status Result:= Pass MS busy? No Set negative response: Busy Subscriber Page MS negative response Result:= Fail Yes PPSMS_M1(1) Page Start Page response timer Wait_For_ Page_ Response MS connection established Page response timer expired CM Service Request CM Service Request For circuitswitched call To process OCH_MSC Set access connection status Set negative response: Absent Subscriber Page MS negative response Set negative response: Busy Subscriber (NDUB) Page MS negative response Result:= Fail Result:= Pass Result:= Fail Figure 62: Procedure Prepaging_Search_For_MS_MSC 3GPP .018 V10.1.Release 10 162 3GPP TS 23.0 (2011-03) Procedure Prepaging_Search_For_MS_MSC Procedure in the MSC to page an MS in all location areas Signals to/from the left are to/from the BSS.

0 (2011-03) Process OSI_MSC Process in the MSC to handle a request from the VLR for information on the subscriber's location and state OSI_MSC1(1) Signals to/from the left are to/from the VLR Idle Obtain Subscriber Info Subscriber state requested? Yes No Set subscriber state Obtain Subscriber Info ack Idle Figure 63: Process OSI_MSC 3GPP .Release 10 163 3GPP TS 23.1.018 V10.

018 V10.0 (2011-03) Process AIR_MSC Process in the MSC to retrieve any one or more of the current location.1. MS classmark and IMEI of a subscriber AIR_MSC1(1) Signals to/from the left are to/from the VLR Idle Search for MS Page MS Active_Info_ Retrieval_ Search_MSC Active_Info_ Retrieval_ Page_MSC Idle Figure 64: Process AIR_MSC 3GPP .Release 10 164 3GPP TS 23.

0 (2011-03) Procedure Active_Info_Retrieval_Page_MSC Procedure in the MSC to page an MS in a specified location area for Active Location Retrieval No AIRP_MSC1(2) Signals to/from the left are to/from the BSS.1.Release 10 165 3GPP TS 23.018 V10. signals to/from the right are to/from the VLR unless marked otherwise Location area ID known? Yes MS connection exists? No No Yes Paging via SGSN possible? Yes Retrieve_ IMEI_If_ Required Yes In specified location area Page Page MS via SGSN GSM Access? No Start Page response timer Location info requested? Yes Wait_For_ Page_ Response Report on change of service area? No Yes No Page response timer expired MS connection established CM Service Request For circuitswitched call Location Reporting Control CM Service Request To process OCH_MSC Wait_For_ Location_ Report Retrieve_ IMEI_If_ Required Retrieve_ IMEI_If_ Required Location Report Release transaction Location info:= Received location info Set negative response: Absent subscriber Set negative response: Unknown LAI Page MS negative response Page MS ack Page MS ack Page MS ack Page MS negative response Figure 65: Procedure Active_Info_Retrieval_Page_MSC 3GPP .

1.018 V10. signals to/from the right are to/from the VLR unless marked otherwise MS connection exists? No No Yes Paging via SGSN possible? Yes In all location areas Search for MS via SGSN Retrieve_ IMEI_If_ Required Yes GSM Access? No Page Start Page response timer Location info requested? Yes No Wait_For_ Page_ Response Report on change of service area? No Yes Page response timer expired MS connection established CM Service Request For circuitswitched call Location Reporting Control CM Service Request To process OCH_MSC Wait_For_ Location_ Report Retrieve_ IMEI_If_ Required Retrieve_ IMEI_If_ Required Location Report Release transaction Location info:= Received location info Set negative response: Absent subscriber Search for MS negative response Search for MS ack Search for MS ack Search for MS ack Figure 66: Procedure Active_Info_Retrieval_Search_MSC 3GPP .0 (2011-03) Procedure Active_Info_Retrieval_Search_MSC Procedure in the MSC to page an MS in all location areas for Active Location Retrieval AIRS_MSC1(1) Signals to/from the left are to/from the BSS.Release 10 166 3GPP TS 23.

Release 10 167 3GPP TS 23.018 V10.1.0 (2011-03) Procedure Retrive_IMEI_If_Required Procedure in the MSC to retrieve the IMEI of the MS if requested by the VLR Signals to/from the left are to/from the BSS RIIR1(1) No IMEI requested? Yes Send IMEI Wait_For_ IMEI IMEI Release transaction IMEI:= Received IMEI Release transaction To supervising process. if required Figure 66bis: Procedure Retrieve_IMEI_If_Required 3GPP .

Send_ACM_If_Required.1. Sheet 1: the procedure CAMEL_ICH_MSC_INIT is specific to CAMEL phase 3 or later. sheet 5.3.018 V10.007 [30].1. accessible to the procedures Establish_Terminating_TCH_If_Required. this signal will not be received from the VLR. sheet 6.3 MT call 7. depending on the telephony signalling system used. Sheet 2. Sheet 1: The variable "On_Hold" is used only if the VMSC supports Call Hold. If the VMSC does not support CAMEL phase 3 or later. sheet 10. sheet 12: the procedure CAMEL_MT_GMSC_DISC6 is called if the VMSC supports CAMEL phase 3 or later.Release 10 168 3GPP TS 23.078 [12]. unspecified No answer from user (user alerted) Protocol error. Table 2: Suggested mapping of Send Info For Incoming Call (SIFIC) negative responses to ISUP release causes SIFIC negative response Absent subscriber Busy subscriber CUG reject (Called party SS interaction violation) Forwarding violation Impossible call completion No subscriber reply System failure Unallocated roaming number ISUP release cause number 20 17 21 21 111 19 111 111 ISUP release cause name Subscriber absent User busy Call rejected Call rejected Protocol error. sheet 10. sheet 9: the process CAMEL_ICH_LEG1_MSC is specific to CAMEL phase 4 or later.1 Process ICH_MSC Sheet 1: the task "Release Resources" refers to any resources that may have been allocated for the call due to PrePaging. processing continues from the "No" exit of the test "Result=Reconnect?". sheet 8.850 [37]) is shown in table 2. it is specified in 3GPP TS 23.1. Sheet 1: the task "Store UUS information (if received)" is executed only if the VMSC supports UUS. sheet 12: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC supports CAMEL phase 3 or later.1 Functional requirements of serving MSC 7. UUS2 active. They are accessible to all UUS specific procedures.0 (2011-03) 7. it is specified in 3GPP TS 23. 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. The mapping used is a matter for the network operator. UUS3 active and UUS CF interaction are specific to UUS.3. Sheet 2: the procedure Process_Access_Request_MSC is specified in subclause 7. UUS1 explicit active.2. Send_Answer_If_Required and Send_Network_Connect_If_Required. Sheet 2. Sheet 1: the handling starting with the input signal "Continue CAMEL handling" is specific to CAMEL phase 3 or later. UUS1 implicit active.078 [12]. Answer sent and Network connect sent are global data. Sheet 1. unspecified Sheet 2. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 3 or later. Sheet 1: the rules for converting the ISDN BC/LLC/HLC to a bearer service or teleservice are specified in 3GPP TS 29.078 [12]. sheet 11. sheet 3. sheet 8. Sheet 1: the variables UUS result sent. ACM sent.1. 3GPP . it is specified in 3GPP TS 23. sheet 4. 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 1: the variables TCH allocated.078 [12]. unspecified Protocol error.

078 [12]. 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 10: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS. If CAMEL information is available for the subscriber and the GMSC supports the required CAMEL phase. - Sheet 5: the procedure Handle_ORLCF_VMSC is specific to Support of Optimal Routeing. sheet 5. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 3 or later. Sheet 3.0 (2011-03) Sheet 3: the procedure CAMEL_MT_GMSC_DISC5 is called if the VMSC supports CAMEL phase 3 or later. Sheet 6: The task "set redirection information" includes the mapping of the MSISDN parameter received in the Send Info For Incoming Call ack message to the redirecting number of the IAM message and the setting of the presentation indicator of the redirecting number of the IAM message according to the value of the Redirecting presentation parameter received in the Send Info For Incoming Call ack message.083 [16].072 [11]. it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support Optimal Routeing. Sheet 6: the procedure CAMEL_MT_VMSC_Notify_CF is specific to CAMEL phase 3 or later.078 [12]. 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". then ORLCF may take place ('ORLCF' result from CAMEL_Check_ORLCF_VMSC).093 [23]. Sheet 4: the procedure CAMEL_ICH_LEG2_MSC isspecific to CAMEL phase 4 or later. it is specified in 3GPP TS 23.078 [12].1. they are specified in 3GPP TS 23.Release 10 169 3GPP TS 23. If the VMSC sends an Address Complete message. 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. The Resume Call Handling request shall include the relevant CAMEL information ('ORLCF' result from CAMEL_Check_ORLCF_VMSC). sheet 11: the procedures CD_Failure and CD_Success are specific to Call Deflection. sheet 11. it is specified in 3GPP TS 23. Sheet 5.078 [12]. the procedure Complete_Call_In_MSC and the procedure Process_Call_Waiting will not return a "Reconnect" result. sheet 13: the procedure CCBS_Check_Last_Call is specific to CCBS. Sheet 3: the procedure CD_Reject is specific to Call Deflection. Sheet 3: the processing in the branch starting with the input signal"Process Call Waiting" is specific to Call Wait. it is specified in 3GPP TS 23.072 [11]. sheet 6. processing continues from the "Continue" exit of the test "Result?". Sheet 3: the procedure UUS_ICH_Check_Support is specific to UUS.093 [23].018 V10. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 5: the procedure CAMEL_Check_ORLCF_VMSC is specific to CAMEL phase 2 or later. 3GPP . then ORLCF shall not take place ('VMSCCF' result from CAMEL_Check_ORLCF_VMSC). it is specified in 3GPP TS 23. Sheet 3: if the VMSC does not support CAMEL phase 3 or later. this signal will not be received from the VLR. Sheet 3: the procedure Process_Call_Waiting is specific to Call Waiting. processing continues from the "No" exit of the test "Result=Reconnect?".087 [20]. it is specified in 3GPP TS 23. Sheet 6: it is an operator option whether to send an Address Complete message if the VLR returns forwarding information. processing starts with the possible call of the procedure CCBS_Check_Last_Call. Sheet 9: the procedure CAMEL_ICH_LEG2_CF_MSC is specific to CAMEL phase 4 or later. If the VMSC does not support Call Waiting.079 [13]. then ORLCF may take place. Sheet 6: If the VMSC does not support CAMEL phase 3 or later. sheet 12. If the VLR does not support CAMEL or no CAMEL information is available for the subscriber. sheet 6. Sheet 3.

083[16]. it is specified in 3GPP TS 23. processing continues from the "No" exit of the test "Result = Forwarding Failed?". Sheet 13: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS. Sheet 6: the procedure UUS_ICH_Set_Info_In_IAM is specific to UUS.018 V10.078 [12]. Sheet 16: the procedure Process_Hold_Request is specific to Call Hold.1. Sheet 8: the procedure Send_Network_Connect_If_Required is specified in subclause 7.2.6. If the VMSC does not support CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later. 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 processing on this sheet is specific to CAMEL phase 3 or later.7. If the VMSC does not support OR. Sheet 8: the procedure Handle_COLP_Forwarding_Interaction_MSC is specified in subclause 7.2. 7.1.083[16]. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 4 or later. Sheet 6: the called party address sent in the IAM to the process MT_CF_MSC is the Forwarded-to number received in the Perform Call Forwarding ack.2.3. it is specified in 3GPP TS 23.078 [12]. Connect. Sheet 14: after the VMSC has sent an IAM to the process MT_CF_MSC.4.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.1. the input signal Send Info For MT Reconnected Call ack will not be received.5.078 [12]. the input signal Int_Release Call will not be received. Sheet 6: the procedure Activate_CF_Process is specified in subclause 7. the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists.087 [20]. Answer or Release causes no change of state in the process ICH_MSC. the input signal Int_Release Call will not be received. Sheet 13. Sheet 8: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later. Sheet 15: The processing on this sheet is specific to CAMEL phase 3 or later.2.0 (2011-03) Sheet 6.3. sheet 14: the procedure CAMEL_MT_GMSC_DISC2 is called if the VMSC supports CAMEL phase 3 or later. Sheet 8: the procedure Send_Answer_If_Required is specified in subclause 7.1. Sheet 11: the processing on this sheet is specific to CAMEL phase 3 or later. Sheet 10: the procedure CCBS_MT_MSC_Check_Forwarding is specific to CCBS. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 1: for an SMS or SS page.1. it acts as a transparent relay for messages received from the GMSC and the process MT_CF_MSC. processing continues from the "Pass" exit of the test "Result?".1.079 [13]. processing continues from the "Pass" exit of the test "Result?". Sheet 6: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. it is specified in 3GPP TS 23.2. Sheet 13. If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23. Any message other than Address Complete. Sheet 11: the procedure Handle_ORLCF_VMSC is specific to OR.1. 3GPP .078 [12]. it is specified in 3GPP TS 23. sheet 8: the procedure Send_ACM_If_Required is specified in subclause 7.093 [23].087 [20]. Sheet 16: the procedure Process_Retrieve_request is specific to Call_Hold. it is specified in 3GPP TS 23. sheet 14: the procedure CAMEL_MT_GMSC_DISC1 is called if the VMSC supports CAMEL phase 3 or later. it is specified in 3GPP TS 23.Release 10 170 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 8: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later.078 [12].

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

Release 10

172

3GPP TS 23.018 V10.1.0 (2011-03)

-

If the result of location update is successful and location update is not through Gs interface, then the Search_MS_MSC procedure returns with PASS. If the result of location update is successful and location update is through Gs interface, then the procedure continues from the beginning of the Page_MS_MSC procedure. If the result of the location update is not successful, then the procedure should return FAIL after sending the Search MS negative response (cause Absent Subscriber) to VLR.

Sheet 2: the procedure Check_MT_Multicall_MSC is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. If the VMSC does not support Multicall, processing continues from the "Yes" exit of the test "Result=Not provisioned?". Sheet 2: the test "Call in set-up" takes the "Yes" exit if the call on which the MS is engaged has not reached the established phase (called party answer). Sheet 2: the test "Call waiting" takes the "Yes" exit if a waiting call has been offered to the subscriber but the outcome of offering the call has not been determined. Sheet 2: if there is one established call, the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call. If there are two or more established calls (the Multicall case), the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23.135 [25]). Sheet 3: the signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure. Sheet 4 : A MSC not implementing the MT Roaming Retry feature may not immediately stop paging upon receipt of a Cancel Location message.

7.3.1.4

Procedure Complete_Call_In_MSC

Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP. Sheet 1: the VMSC derives the PLMN bearer capability required for the call according to the rules defined in 3GPP TS 29.007 [30]. Sheet 1, sheet 2: the VMSC and the MS may negotiate the bearer capability to be used for the call by the exchange of information in the Set-up and Call Confirmed messages. Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS, it is specified in 3GPP TS 23.087 [20]. Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. Sheet 2: the procedure Establish_Terminating_TCH_Multicall is specific to Multicall; it is specified in 3GPP TS 23.135 [25]. Sheet 2: the test "Result=Rejected?" can take the "Yes" exit only if the procedure Establish_Terminating_TCH_Multicall was called. Sheet 2, sheet 3, sheet 4, sheet 5, sheet 6, sheet 7: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the VMSC does not support CAMEL phase 3 or later, processing continues from the "No" exit of the test "Result=Reconnect?". Sheet 2, sheet 3, sheet 6, sheet 9, sheet 10: the procedure CAMEL_MT_GMSC_DISC6 is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. Sheet 2, sheet 5, sheet 9: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. Sheet 3, sheet 5: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. Sheet 3: the procedure CAMEL_Start_TNRy is called if the VMSC supports CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12].

3GPP

Release 10

173

3GPP TS 23.018 V10.1.0 (2011-03)

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

7.3.1.5 7.3.1.6

Void Procedure Set_CLIP_Info_MSC

The originating exchange may release the call or the MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIP_MAF002. The message is saved for processing after return from the procedure.

3GPP

Release 10

174

3GPP TS 23.018 V10.1.0 (2011-03)

7.3.1.7 7.3.1.8

Void Procedure Establish_Terminating_TCH_If_Required

The procedure TCH_Check is specified in subclause 7.1.1.14.

7.3.1.9 7.3.1.10

Procedure Handle_AoC_MT_MSC Procedure Set_COL_Presentation_Indicator_MSC

The originating exchange may release the call or the MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process COLP_MAF041. The message is saved for processing after return from the procedure.

3GPP

Release 10

175

3GPP TS 23.018 V10.1.0 (2011-03)

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

ICH_MSC1(17)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise Idle

Release Resources

From GMSC

Initial Address

From GMSC

Release Resources

Convert ISDN BC/LLC/HLC (if present) to bearer service/teleservice & CS BC; Store UUS information (if received)

Release MSRN

Send Info For Incoming Call

Idle

Wait_For_ Page_Request

Continue CAMEL Handling

ACM sent:=False; Answer sent:=False; BOR:=False; Network connect sent:=False; TCH allocated:=False; UUS1 result sent:=False; UUS1 implicit active:=False; UUS1 explicit active:=False; UUS2 active:=False; UUS3 active:=False; UUS CF interaction:=False; Call answered := False; On_Hold:=False

CAMEL_ ICH_MSC_ INIT

See TS 23.078

Result?

Leg1_only

Reconnect

MSRN

Aborted

Fail

Leg1_status := Set-up

Set Suppress VT-CSI

Set cause

CAMEL_ICH_ LEG1_MSC (Leg1_Status)

Send Info For MT Reconnected Call

Send Info For Incoming Call

Release

Release call resources Idle

Wait_For_ Reconnected_ Call_Result See TS 23.078

Wait_For_ Page_Request

Idle

Figure 67a: Process ICH_MSC (sheet 1)

3GPP

Release 10

176

3GPP TS 23.018 V10.1.0 (2011-03)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_ Page_Request

ICH_MSC2(17)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR

Send Info For Incoming Call negative response Set cause

Page MS

Send Info For Incoming Call Ack

Call is to be forwarded

Search For MS

Complete Call

Page_ MS_MSC

1

Search_For_ MS_MSC

2

See TS 23.078

Result= Pass? No No Result= Fail? Yes

Yes

Yes

Result= Pass? No Result= Fail No

CAMEL_ MT_GMSC_ DISC6

Process_ Access_ Request_MSC

Yes

CAMEL_ MT_GMSC_ DISC6

Release call resources

Result= Pass? Yes

No CAMEL_ MT_GMSC_ DISC4 Yes Wait_For_ MT_Call_ Result

Release call resources

CAMEL_ MT_GMSC_ DISC4 Yes

Idle

Wait_For_ MT_Call_ Result

Wait_For_ MT_Call_ Result

Idle

Result= Reconnect? No Release

Result= Reconnect? No

See TS 23.078

Send Info For MT Reconnected Call

Release

Release call resources

Release call resources

Idle

Wait_For_ Reconnected_ Call_Result

Idle

See TS 23.078

See TS 23.078

Figure 67b: Process ICH_MSC (sheet 2)

3GPP

078 See TS 23.093 Signals to/from the left are to/from the GMSC.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call Wait_For_ MT_Call_ Result ICH_MSC3(17) Send Info For Incoming Call negative response Complete Call 2 Process Call Waiting CD_Reject See TS 23. signals to/from the right are to/from the VLR unless marked otherwise Release call resources Idle Figure 67c: Process ICH_MSC (sheet 3) 3GPP .087 Call answered := True Set cause To Subs_FSM Yes Cause= No Subscriber Reply? No CAMEL_ MT_GMSC_ DISC4 No CAMEL_ MT_GMSC_ DISC5 Call setup failed To Subs_FSM Call established To Subs_FSM Call setup failed 5 Result= Fail No Yes Yes Result= Fail No Yes Result= Reconnect? Yes Send Info For MT Reconnected Call Wait_For_ MT_Call_ Result Yes Result= Reconnect? No Release Result= Reconnect? No Send Info For MT Reconnected Call Wait_For_ Reconnected_ Call_Result Wait_For_ Reconnected_ Call_Result See TS 23.078 Release transaction CCBS_Check_ Last_Call See TS 23.083 Process_ Call_ Waiting Yes CCBS_Set_ Diagnostic_ For_Release See TS 23.072 Complete_ Call_In_MSC See TS 23.Release 10 177 3GPP TS 23.018 V10.1.093 Result= Pass? No Yes Result= Pass? No Store CW Treatment indicator for this call if received in SII2 UUS_ICH_ Check_ Support See TS 23.

018 V10.1.078 CAMEL_ICH_ LEG1_MSC (Leg1_Status) Wait_For_ Clear See TS 23.078 CAMEL_ICH_ LEG2_MSC Idle Figure 67d: Process ICH_MSC (sheet 4) 3GPP .0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call 5 ICH_MSC4(17) CAMEL phase 4 or later control relationship exists? Yes Leg1_status := Active No See TS 23.Release 10 178 3GPP TS 23.

Release 10

179

3GPP TS 23.018 V10.1.0 (2011-03)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_ MT_Call_ Result 1 Send Info For Incoming Call ack MT Roaming Retry supported Yes MT Roaming Retry Indicator received Yes Handle_ ORLCF_VMSC VMSCCF Wait_For_ Release_ From_GMSC Release No CAMEL_Check_ ORLCF_VMSC See TS 23.079 No Call is to be forwarded

ICH_MSC5(17)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR

Result? ORLCF Handle_ ORLCF_VMSC Continue Result? See TS 23.079

Accepted

CAMEL_ MT_GMSC_ DISC6 Release call resources

Forwarding Failed CD_Failure See TS 23.072 CD_Success See TS 23.072

Idle

Wait_For_ Release_ From_GMSC 3 Release

CAMEL_ MT_GMSC_ DISC6 CCBS_Check_ Last_Call

See TS 23.078

See TS 23.093

Release call resources

Idle

Figure 67e: Process ICH_MSC (sheet 5)

3GPP

Release 10

180

3GPP TS 23.018 V10.1.0 (2011-03)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Yes Type of forwarding= Reconnect? No CAMEL_ MT_VMSC_ Notify_CF 3

ICH_MSC6(17)
Signals to the right are to the VLR unless marked otherwise

See TS 23.078

Yes Result= Reconnect? No 4

CCBS_Check_ Last_Call

See TS 23.093

Set redirection information

Send_ACM_ If_Required

Activate_ CF_Process

Fail Result?

Pass

Release UUS_ICH_ Set_Info_ In_IAM

Release

See TS 23.087

CAMEL_ MT_GMSC_ DISC4

See TS 23.078

Initial Address Message

To process MT_CF_MSC

Yes Result= Reconnect? No Send Info For MT Reconnected Call

CAMEL_Store_ Destination_ Address (False, True)

See TS 23.078

CD_Failure

See TS 23.072

CD_Success

See TS 23.072

Wait_For_ Reconnected_ Call_Result

CCBS_Check_ Last_Call

See TS 23.093

Wait_For_ Forward_ACM

Idle

Figure 67f: Process ICH_MSC (sheet 6)

3GPP

Release 10

181

3GPP TS 23.018 V10.1.0 (2011-03)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_MT_Call_Result, Wait_For_Reconnected_Call_Result

ICH_MSC7(17)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the VLR unless marked otherwise

Int_Release_ Call

From gsmSSF

Abort

Release

Release Transaction

To BSS

Release call resources

Idle

Figure 67g: Process ICH_MSC (sheet 7)

3GPP

Release 10

182

3GPP TS 23.018 V10.1.0 (2011-03)

Process ICH_MSC
Process in the MSC to handle an incoming (MT) call Wait_For_ Forward_ACM

ICH_MSC8(17)
Signals to/from the left are to/from the GMSC; signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise

Address Complete

Connect

Send_ACM_ If_Required

See TS 23.078

CAMEL_MT_ MSC_ALERTING

Result? Answer Pass Else

Wait_For_ Forward_Answer

Release

Release

Answer

Release

See TS 23.078

CAMEL_ MT_GMSC_ DISC4

CAMEL_ MT_GMSC_ ANSWER

See TS 23.078

See TS 23.078

CAMEL_ MT_GMSC_ ANSWER

CAMEL_ MT_GMSC_ DISC6

See TS 23.078

Result? Pass No Handle_COLP_ Forwarding_ Interaction_MSC

Else

Else

Result? Pass

Result= Reconnect? Yes

Release

Result? Fail

Reconnect

Handle_COLP_ Forwarding_ Interaction_MSC

Release

Set COLP presentation indicator

Release

6

Set COLP presentation indicator

Send_Answer_ If_Required

Idle

Send_Network_ Connect_ If_Required

6 Call answered := True

Release call resources

To VLR

Send Info For MT Reconnected Call

7

Idle

Wait_For_ Reconnected_ Call_Result

Figure 67h: Process ICH_MSC (sheet 8)

3GPP

Release 10

183

3GPP TS 23.018 V10.1.0 (2011-03)

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

ICH_MSC9(17)

CAMEL phase 4 or later control relationship exists? Yes Leg1_status := Active

No

See TS 23.078

CAMEL_ICH_ LEG1_MSC (Leg1_Status)

Wait_For_ Clear

See TS 23.078

CAMEL_ICH_ LEG2_CF_MSC

Idle

Figure 67i: Process ICH_MSC (sheet 9)

3GPP

018 V10.093 To VLR Wait_For_ Reconnected_ Call_Result Send Info For MT Reconnected Call negative response See TS 23. signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Release Release Release CAMEL_ MT_GMSC_ DISC4 See TS 23.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call Wait_For_ Forward_ACM ICH_MSC10(17) Signals to/from the left are to/from the GMSC.Release 10 184 3GPP TS 23.078 CAMEL_ MT_GMSC_ DISC6 Yes Result= Reconnect? No CCBS_MT_ MSC_Check_ Forwarding Send Info For MT Reconnected Call See TS 23.078 See TS 23.1.093 CCBS_Set_ Diagnostic_ For_Release Set cause Release Release Int_Exception To gsmSSF Release call resources Idle Figure 67j: Process ICH_MSC (sheet 10) 3GPP .

072 CD_Failure CD_Success See TS 23. signals from the right are from the VLR Send Info For MT Reconnected Call ack True Call answered False Handle_ ORLCF_VMSC See TS 23.1.072 Wait_For_ Release_From_ GMSC Release CAMEL_ MT_GMSC_ DISC6 See TS 23.079 No Result= Accepted? Yes No Result= Forwarding Failed? Yes 4 See TS 23.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call Wait_For_ Reconnected_ Call_Result ICH_MSC11(17) Signals from the left are from the GMSC.018 V10.078 CCBS_Check_ Last_Call See TS 23.Release 10 185 3GPP TS 23.093 Release call resources Idle Figure 67k: Process ICH_MSC (sheet 11) 3GPP .

078 CAMEL_ MT_GMSC_ DISC4 See TS 23.1. signals to/from the right are to/from the BSS unless marked otherwise Release Release transaction CAMEL_ MT_GMSC_ DISC6 See TS 23.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call Wait_For_ MT_Call_ Result ICH_MSC12(17) Signals to/from the left are to/from the GMSC.078 Yes Result= Reconnect? No Release transaction Release CCBS_Check_ Last_Call See TS 23.093 Abort To VLR Send Info For MT Reconnected Call To VLR Release call resources Idle Wait_For_ Reconnected_ Call_Result Figure 67l: Process ICH_MSC (sheet 12) 3GPP .Release 10 186 3GPP TS 23.018 V10.

078 Yes Release transaction Result= Reconnect? No See TS 23.1. signals to/from the right are to/from the BSS unless marked otherwise Release Release transaction UUS_MSC_ Check_ UUS1_UUI See TS 23.087 CAMEL_ MT_GMSC_ DISC2 See TS 23.078 CAMEL_ MT_GMSC_ DISC1 See TS 23.Release 10 187 3GPP TS 23.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call Wait_For_Clear ICH_MSC13(17) Signals to/from the left are to/from the GMSC.093 Release call resources To Subs_FSM Call cleared Idle Wait_For_ Reconnected_ Call_Result Figure 67m: Process ICH_MSC (sheet 13) 3GPP .087 UUS_MSC_ Check_ UUS1_UUI Release Send Info For MT Reconnected Call To VLR CCBS_Check_ Last_Call See TS 23.018 V10.

078 See TS 23.1.Release 10 188 3GPP TS 23.078 CAMEL_ MT_GMSC_ DISC1 Yes Result= Reconnect? No Release Send Info For MT Reconnected Call To VLR Release call resources Idle Wait_For_ Reconnected_ Call_Result Wait_For_Forward_ACM.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call Wait_For_ Forward_Clear ICH_MSC14(17) Signals to/from the left are to/from the GMSC. signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Release Release Release CAMEL_ MT_GMSC_ DISC2 See TS 23.018 V10. Wait_For_Forward_Answer. Wait_For_Forward_Clear * * - - - Figure 67n: Process ICH_MSC (sheet 14) 3GPP .

signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Wait_For_Forward_ACM.018 V10.1.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call ICH_MSC15(17) Signals to/from the left are to/from the GMSC.Release 10 189 3GPP TS 23. Wait_For_Forward_Clear Wait_For_ Clear Int_Release_ Call From gsmSSF Int_Release_ Call From gsmSSF Release Release transaction To the BSS Release Release Release call resources Release call resources Idle Call cleared To Subs_FSM Idle Figure 67o: Process ICH_MSC (sheet 15) 3GPP .

083 Wait_For_ Clear Figure 67p: Process ICH_MSC (sheet 16) 3GPP .018 V10.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call ICH_MSC16(17) Signals to/from the left are to/from the BSS Wait_For_ Clear Hold request Retrieve request Hold supported? Yes No No Hold supported? Yes See 3G TS 23.1.Release 10 190 3GPP TS 23.083 Process_ Hold_ Request Hold reject Retrieve reject Process_ Retrieve_ Request See 3G TS 23.

018 V10.0 (2011-03) Process ICH_MSC Process in the MSC to handle an incoming (MT) call ICH_MSC17(17) Signals from the left are from the BSS. Wait_For_ Clear ECT request MPTY request ECT request MPTY request Wait_For_ Clear Figure 67q: Process ICH_MSC (sheet 17) 3GPP .1. signals to the right are to the Subs_FSM process.Release 10 191 3GPP TS 23.

signals to/from the right are to/from the VLR unless marked otherwise PAGE_M1(3) Set negative response: Unknown LAI Set negative response: System Failure Clear received:= False No Yes SMS or SS page? No Yes Paging via SGSN possible? In specified location area Page Page MS via SGSN Request call status To Subs_FSM Set access connection status Start Page response timer Wait_For_ Page_ Response Wait_For_ Call_Status Result:= Pass Page MS negative response Result:= Fail Figure 68a: Procedure Page_MS_MSC (sheet 1) 3GPP .1.Release 10 192 3GPP TS 23.018 V10.0 (2011-03) Procedure Page_MS_MSC Procedure in the MSC to page an MS in a specified location area No Location area ID known? Yes No Call still exists? Yes MS connection exists? No Yes Signals to/from the left are to/from the BSS.

0 (2011-03) Procedure Page_MS_MSC Procedure in the MSC to page an MS in a specified location area Wait_For_ Call_Status PAGE_M2(3) Signals to/from the left are to/from the BSS.018 V10.Release 10 193 3GPP TS 23.135 Result= Offered? No Yes Result= More calls possible? No Yes Result= not provisioned? Yes Call in setup? No No Call waiting? No Yes Yes Set negative response: Busy subscriber More calls possible Set negative response: Busy subscriber (NDUB) Page MS negative response Set access connection status Result:= Fail Result:= Pass Figure 68b: Procedure Page_MS_MSC (sheet 2) 3GPP . signals to/from the right are to/from the VLR unless marked otherwise Call status From process Subs_FSM Check_MT_ Multicall_MSC See TS 23.1.

0 (2011-03) Procedure Page_MS_MSC Procedure in the MSC to page an MS in a specified location area Wait_For_ Page_ Response PAGE_M3(3) Signals to/from the left are to/from the BSS.Release 10 194 3GPP TS 23. signals to/from the right are to/from the VLR unless marked otherwise Page response timer expired CM Service Request For circuitswitched call MS connection established Release From GMSC Clear received False True Abort True Clear received False CM Service Request To process OCH_MSC Clear received False True Set negative response: Absent Subscriber Set negative response: Busy Subscriber (NDUB) Set access connection status Release transaction Page MS negative response Page MS negative response Result:= Pass Result:= Aborted Clear received:= True Result:= Aborted Result:= Fail Result:= Fail Result:= Aborted Wait_For_ Page_ Response Figure 68c: Procedure Page_MS_MSC (sheet 3) 3GPP .018 V10.1.

1.0 (2011-03) Procedure Page_MS_MSC Procedure in the MSC to page an MS in a specified location area PAGE_M4(4) Signals to/from the left are to/from the BSS.018 V10.Release 10 195 3GPP TS 23. signals to/from the right are to/from the VLR unless marked otherwise Wait_For_ Page_ Response Cancel Location True Clear received False Set negative response: Location Cancelled Page MS negative response Result:= Fail Result:= Aborted Release transaction Figure 68c: Procedure Page_MS_MSC (sheet 4) 3GPP .

1. signals to/from the right are to/from the VLR unless marked otherwise No Call still exists? Yes Yes MS connection exists? No Clear received:= False No Yes Set negative response: System Failure Set access connection status Search For MS negative response SMS or SS page? No Yes Paging via SGSN possible? Search for MS via SGSN Request call status To Subs_FSM In all location areas or in PgA if PgA received and supported Page Start Page response timer Result:= Pass Result:= Fail Wait_For_ Search_ Response Wait_For_ Call_Status Figure 69a: Procedure Search_For_MS_MSC (sheet 1) 3GPP .Release 10 196 3GPP TS 23.018 V10.0 (2011-03) Procedure Search_For_MS_MSC Procedure in the MSC to search for an MS (page in all location areas) SRCH_M1(4) Signals to/from the left are to/from the BSS.

135 Result= Offered? No Yes Result= More calls possible? No Yes Result= not provisioned Yes Call in setup? No No Call waiting? No Yes Yes Set negative response: Busy Subscriber More calls possible Set negative response: Busy Subscriber (NDUB) Search For MS negative response Set access connection status Result:= Fail Result:= Pass Figure 69b: Procedure Search_For_MS_MSC (sheet 2) 3GPP .1. signals to/from the right are to/from the VLR unless marked otherwise Call status From process Subs_FSM Check_MT_ Multicall_MSC See TS 23.018 V10.0 (2011-03) Procedure Search_For_MS_MSC Procedure in the MSC to search for an MS (page in all location areas) Wait_For_ Call_Status SRCH_M2(3) Signals to/from the left are to/from the BSS.Release 10 197 3GPP TS 23.

018 V10.0 (2011-03) Procedure Search_For_MS_MSC Procedure in the MSC to search for an MS (page in all location areas) Wait_For_ Search_ Response SRCH_M3(3) Signals to/from the left are to/from the BSS.1. signals to/from the right are to/from the VLR unless marked otherwise Page response timer expired CM Service Request For circuitswitched call MS connection established Release From GMSC Clear received False True Abort True Clear received False CM Service Request To process OCH_MSC Search For MS ack Release transaction Clear received False True Set negative response: Absent Subscriber Set negative response: Busy Subscriber (NDUB) Set access connection status Search For MS negative response Search For MS negative response Result:= Pass Result:= Aborted Clear received:= True Result:= Aborted Result:= Fail Result:= Fail Result:= Aborted Wait_For_ Search_ Response Figure 69c: Procedure Search_For_MS_MSC (sheet 3) 3GPP .Release 10 198 3GPP TS 23.

018 V10.0 (2011-03) Procedure Search_For_MS_MSC Procedure in the MSC to search for an MS (page in all location areas) SRCH_M4(4) Signals to/from the left are to/from the BSS.Release 10 199 3GPP TS 23.1. signals to/from the right are to/from the VLR unless marked otherwise Wait_For_ Search_ Response Cancel Location True Clear received False Set negative response: Location Cancelled Search for MS negative response Result:= Fail Result:= Aborted Release transaction Figure 69d: Procedure Search_For_MS_MSC (sheet 4) 3GPP .

018 V10.Release 10 200 3GPP TS 23.093 Wait_For_ Setup_ Response Setup failure Int_Release_ Call From gsmSSF Set negative response: Absent Subscriber Complete Call negative response Result:= Fail Figure 70a: Procedure Complete_Call_In_MSC (sheet 1) 3GPP .1.087 CCBS_Report_ Not_Idle See TS 23. signals to/from the right are to/from the VLR unless marked otherwise Set_CLIP_ Info_MSC Derive required PLMN BC See TS 29.007 Setup UUS_ICH_UUS1_ Implicit_ Active See TS 23.0 (2011-03) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR CCI_MSC1(11) Signals to/from the left are to/from the BSS.

078 Set negative response: Radio congestion CCBS_ICH_MSC_ Report_Failure See TS 23.Release 10 201 3GPP TS 23.1.0 (2011-03) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Setup_ Response CCI_MSC2(11) Signals to/from the left are to/from the BSS.018 V10.093 Complete Call negative response Result:= Aborted Result:= Reconnect Result:= Fail 4 Wait_For_ Alerting Figure 70b: Procedure Complete_Call_In_MSC (sheet 2) 3GPP .135 Result= Fail? No Yes Result= Aborted No Yes Yes CAMEL_ MT_GMSC_ DISC4 See TS 23.078 Result= Rejected? No Yes Abort Result= Reconnect? No CAMEL_ MT_GMSC_ DISC6 See TS 23. signals to/from the right are to/from the VLR Call Confirmed Multicall supported in MSC? No Establish_ Terminating_ TCH_If_ Required Yes Establish_ Terminating_TCH_ Multicall See TS 23.

078 CAMEL_ MT_GMSC_ DISC6 Result:= Aborted Result:= Reconnect Result:= Aborted Result:= Aborted Wait_for_ Answer Figure 70c: Procedure Complete_Call_In_MSC (sheet 3) 3GPP .093 No NRCT provided? Establish_ Terminating_ TCH_Multicall See TS 23.0 (2011-03) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Alerting CCI_MSC3(11) Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless marked otherwise Alerting Connect UUS_ICH_ Check_Support See TS 23.018 V10.135 Yes Yes Start No Reply Call Timer Result= Pass? No CAMEL_ Start_TNRy See TS 23.078 Yes Result= Reconnect? No Result? Answer Pass Fail Release Reconnect Release Abort A Release To GMSC Abort See TS 23.093 1 See TS 23.078 CAMEL_ MT_GMSC_ DISC4 CAMEL_MT_ MSC_ALERTING See TS 23.Release 10 202 3GPP TS 23.087 UUS_ICH_ Check_Support See TS 23.078 3 Yes Send_ACM_ If_Required 4 Result= Aborted? No UTU2Cnt:=0 See TS 23.1.087 No Result= Pass? Yes CCBS_ICH_MSC_ Report_Success No Result= Pass? Yes CCBS_ICH_MSC_ Report_Success See TS 23.

0 (2011-03) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR 3 CCI_MSC4(11) Signals to/from the left are to/from the BSS.1. signals to/from the right are to/from the VLR unless marked otherwise Handle_AoC_ MT_MSC No Result= Pass? Yes 2 Connect ack CAMEL_ MT_GMSC_ DISC4 See TS 23.078 CAMEL_ MT_GMSC_ ANSWER No Result= Reconnect? Yes Result? Fail Release Pass Reconnect Release To GMSC Set_COL_ Presentation_ Indicator_MSC To GMSC Send_Network_ Connect_If_ Required To GMSC Release Complete Call ack Abort Result:= Aborted Result:= Pass Result:= Reconnect Result:= Aborted Figure 70d: Procedure Complete_Call_In_MSC (sheet 4) 3GPP .078 Set cause See TS 23.Release 10 203 3GPP TS 23.018 V10.

Release 10

204

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Complete_Call_In_MSC
Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Alerting

CCI_MSC5(11)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise

Alerting failure

1

CD_Request

Release transaction

CCBS_ICH_MSC_ Report_Success

See TS 23.093

Set cause

CAMEL_ MT_GMSC_ DISC4

See TS 23.078

Handling_CD_MSC

See TS 23.072

Yes Result= Reconnect? No

CCBS_ICH_MSC_ Report_Failure

See TS 23.093

Abort

Complete Call negative response

Release

To GMSC

Result:= Reconnect

Result:= Aborted

Result:= Fail

Figure 70e: Procedure Complete_Call_In_MSC (sheet 5)

3GPP

Release 10

205

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Complete_Call_In_MSC
Procedure in the MSC to complete an MT call on request from the VLR Wait_for_ Answer

CCI_MSC6(11)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise

A

Connect

CAMEL_ Stop_TNRy

See TS 23.078

UUS_ICH_ Check_ Support

See TS 23.087

No Result= Pass? Yes Establish_ Terminating_ TCH_Multicall

See TS 23.135

1

Yes Result= Pass? No

5

Yes Result= Aborted? No CAMEL_ MT_GMSC_ DISC4

See TS 23.078

Yes Result= Reconnect?

Release

Abort

Abort

See TS 23.078

CAMEL_ MT_GMSC_ DISC6

Result:= Reconnect

Result:= Aborted

Result:= Aborted

Figure 70f: Procedure Complete_Call_In_MSC (sheet 6)

3GPP

Release 10

206

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Complete_Call_In_MSC
Procedure in the MSC to complete an MT call on request from the VLR 5

CCI_MSC7(11)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise

Handle_AoC_ MT_MSC

No Result= Pass? Yes 2

Connect ack

CAMEL_ MT_GMSC_ DISC4

See TS 23.078

Set cause

See TS 23.078

CAMEL_ MT_GMSC_ ANSWER

Yes Result= Reconnect? Yes

Result? Fail Release Pass

Reconnect

Release

To GMSC

Set_COL_ Presentation_ Indicator_MSC

To GMSC

Send_Answer_ If_Required

To GMSC

Release

Complete Call ack

Abort

Result:= Aborted

Result:= Pass

Result:= Reconnect

Result:= Aborted

Figure 70g: Procedure Complete_Call_In_MSC (sheet 7)

3GPP

Release 10

207

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Complete_Call_In_MSC
Procedure in the MSC to complete an MT call on request from the VLR Wait_for_ Answer

CCI_MSC8(11)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise CAMEL TNRy expired

No Reply Call Timer expired

UUS_ICH_ Check_ Forwarding

See TS 23.087

Result= Pass? Yes

No

Set negative response: No subscriber reply

Release transaction

Complete Call negative response

2

Release transaction

Result:= Fail

Figure 70h: Procedure Complete_Call_In_MSC (sheet 8)

3GPP

Release 10

208

3GPP TS 23.018 V10.1.0 (2011-03)

Procedure Complete_Call_In_MSC
Procedure in the MSC to complete an MT call on request from the VLR Wait_For_Setup_Response, Wait_For_Alerting

CCI_MSC9(11)
Signals to/from the left are to/from the BSS; signals to/from the right are to/from the VLR unless marked otherwise

Release transaction

Release

From GMSC

CCBS_ICH_MSC_ Report_Failure

See TS 23.093

CAMEL_ MT_GMSC_ DISC6

See TS 23.078

User busy? Yes

No

CCBS_ICH_MSC_ Report_Failure

See TS 23.093

Set negative response: Busy subscriber (UDUB)

UUS_MSC_ Check_ UUS1_UUI

See TS 23.087

UUS_MSC_ Check_ UUS1_UUI

See TS 23.087

Complete Call negative response

Release

To GMSC

Release transaction

Abort

Result:= Fail

Result:= Aborted

Figure 70i: Procedure Complete_Call_In_MSC (sheet 9)

3GPP

018 V10.087 UUS_ICH_ Check_ Forwarding No Result= Pass? Yes No See TS 23.087 UUS_MSC_ Check_ UUS1_UUI Release transaction User busy? Yes See TS 23.0 (2011-03) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Answer CCI_MSC10(11) Signals to/from the left are to/from the BSS.078 CAMEL_ MT_GMSC_ DISC6 UUS_MSC_ Check_ UUS1_UUI See TS 23.087 UUS_MSC_ Check_ UUS1_UUI Set negative response: Busy subscriber (UDUB) Complete Call negative response Result:= Fail Abort 1 Result:= Aborted Figure 70j: Procedure Complete_Call_In_MSC (sheet 10) 3GPP . signals to/from the right are to/from the VLR unless marked otherwise Release transaction From GMSC Release See TS 23.1.087 Release To GMSC See TS 23.Release 10 209 3GPP TS 23.

018 V10. Wait_For_Answer Signals to/from the left are to/from the BSS.1.072 Release To GMSC 2 Complete Call negative response Result:= Aborted Result:= Fail Wait_For_ Answer User to User User to User See TS 23.087 UUS_MSC_ Check_UUS2_ UUI_to_NW UUS_MSC_ Check_UUS2_ UUI_to_MS See TS 23.087 Abort No Result= Pass? Release transaction Yes See TS 23.087 Wait_For_ Answer Figure 70k: Procedure Complete_Call_In_MSC (sheet 11) 3GPP . signals to/from the right are to/from the VLR unless marked otherwise CD Request Int_Release_ Call From gsmSSF UUS_ICH_ Check_ Forwarding See TS 23.0 (2011-03) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Answer CCI_MSC11(11) Wait_For_Alerting.072 CD_UUS_ Interaction Handling_ CD_MSC See TS 23.Release 10 210 3GPP TS 23.

0 (2011-03) Procedure Set_CLIP_Info_MSC Procedure in the MSC to determine the CLIP information to be sent to the MS Signals to/from the right are to/from the process CLIP_MAF002 CAINF_M1(1) Initiate handling of CLIP Wait_For_ CLIP_Info Release transaction From BSS Continue call handling Release From GMSC Figure 71: Procedure Set_CLIP_Info_MSC Figure 72: Void 3GPP .Release 10 211 3GPP TS 23.018 V10.1.

Release 10 212 3GPP TS 23.018 V10.0 (2011-03) Procedure Establish_Terminating_TCH_If_Required Procedure in the terminating VMSC to establish a Traffic Channel if one has not been established for this call ETTCIR1(1) Signals to/from the left are to/from the BSS.1. signals to/from the right are to/from the GMSC TCH_Check Result Fail Use existing Allocate Reject Aborted Result:= Fail Result:= Pass Allocate channel Result:= Rejected Result:= Aborted Wait_For_ Allocation_ Complete Release transaction Allocation failure Allocation complete Release Release transaction Release transaction Result:= Fail Result:= Pass Result:= Aborted Figure 73: Procedure Establish_Terminating_TCH_If_Required 3GPP .

Release 10 213 3GPP TS 23.0 (2011-03) Procedure Handle_AoC_MT_MSC Procedure in the MSC to handle AoC signalling towards the MS for an MT call AOCMT_M1(1) Signals to/from the left are to/from the BSS. signals from the right are from the AoC timer function.1.018 V10. Yes AoC(I) provisioned? No Set charging parameters No AoC(C) provisioned? Yes Send Charging Parameters Set charging parameters Send Charging Parameters Start AoC acknowledgment timer Wait_For_ Charging_ Parameters_ Ack Charging Parameters ack Release connection AoC acknowledgment timer expired Release transaction Result:= Pass Result:= Fail Figure 74: Procedure Handle_AoC_MT_MSC 3GPP .

1.0 (2011-03) Procedure Set_COL_Presentation_Indicator_MSC Procedure in the MSC to determine the COL presentation indicator value Signals to/from the right are to/from the process COLR_MAF041 COIND_M1(1) Initiate handling of COLR Wait_For_ COLR_Info Release transaction From BSS Continue call handling Release From GMSC Figure 75: Procedure Set_COL_Presentation_Indicator MSC 3GPP .018 V10.Release 10 214 3GPP TS 23.

093 [23]. due to super-charger).081 [14]. sheet 3: the procedure CCBS_ICH_Report_Not_Reachable is specific to CCBS. Sheet 3: the procedure Get_CW_Subscription_Info_Multicall_VLR is specific to Multicall.1. If the VLR does not support both Multicall and Call Waiting. it is specified in 3GPP TS 23.093 [23].2. it is specified in subclause 7. Sheet 1: A VLR not supporting the flag "Subscriber data dormant" shall behave as if the flag is set to false. Sheet 1: If no IMSI record is found. Sheet 2: this process communicates with the matching instance of the process PRN_VLR. processing continues from the "No" exit of the test "CW available?". sheet 5: the procedure CCBS_ICH_VLR_Report_Failure is specific to CCBS.0 (2011-03) 7.1 Process ICH_VLR Sheet 1: if the MSRN received in the Send Info For Incoming Call is not allocated or there is no IMSI record for the IMSI identified by the MSRN or the MS is marked as "Subscriber data dormant" (e.Release 10 215 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 2: the test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented. 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).3. "GMSC supports MT Roaming Retry" takes "No" exit. . Sheet 1. which is linked by the MSRN.2 Functional requirements of VLR 7.018 V10.15. Sheet 3 sheet 6: the procedure CLI_ICH_VLR_Add_CLI is specific to Enhanced CLI Handling.007 [30]. If the VLR does not support CAMEL phase 3 or later. the procedure call is omitted.2. It is specified in 3GPP TS 23. The "Cancel Location received" flag enables to differentiate for a subscriber whose subscriber data is dormant whether a Cancel Location has been received or not from the HLR. Sheet 1: MT roaming retry is not triggered for an incoming call that arrives at the old VLR after the receipt of the MAP Send Identification request from the new VLR but before the receipt of the MAP Cancel Location from the HLR. Sheet 3: the procedure Get_LI_Subscription_Info_MT_VLR is specific to CLIP and COLR. Sheet 1: the procedure CCBS_ICH_Set_CCBS_Call_Indicator is specific to CCBS.1. 3GPP .078 [12]. Sheet 1: the procedure CAMEL_ICH_VLR is specific to CAMEL phase 3 or later. Sheet 1: If the MSRN is not allocated. the " Subscriber data dormant" check takes the "False" exit. processing continues from the possible call of the procedure CCBS_ICH_Set_CCBS_Call_Indicator.135 [34]. processing continues from the "No" exit of the test "CW available?". Sheet 1: the VLR derives the basic service required for the call according to the rules defined in 3GPP TS 29. Sheet 1.g. Sheet3: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC.093 [23]. it is specified in 3GPP TS 23. If the VLR does not support Call Waiting. it is specified in 3GPP TS 23. Sheet 3: the procedure Get_CW_Subscription_Info_VLR is specific to Call Waiting.3. sheet 2. this is treated as an unknown MSRN. 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. it is specified in 3GPP TS 23. and there is an association established for the MS between the MSC/VLR and the SGSN. If the VLR supports neither CLIP nor COLR.

and CAMEL_D_CSI_Check_VLR are specific to CAMEL phase 3 or later. If the VLR does not support Call Deflection. Sheet 7: the procedure CCBS_ICH_Set_CCBS_Target is specific to CCBS. processing continues from the "Yes" exit of the test "Result=Call allowed?".2.3. If the VLR does not support CCBS.Release 10 216 3GPP TS 23.078 [12]. The message is saved for processing after return from the procedure.3. they are specified in 3GPP TS 23.2. 3GPP .2. sheet 6: the procedure CCBS_ICH_Handle_UDUB is specific to CCBS.6. Sheet 8: the procedure Forward_CUG_Check is specific to CUG. Sheet 5. it is specified in 3GPP TS 23.6 Procedure Handle_CFB The test "Normal call busy" refers to the value of the indicator returned by the process MAF008. Sheet 3: the procedure Process_Access_Request_VLR is specified in subclause 7. it is specified in 3GPP TS 23.093 [23]. It is sent to every SGSN to which the VLR is connected. processing continues from the "Yes" exit of the test "Result = Pass?".3 - Void Procedure Search_For_MS_VLR The test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented.1. 7.2. The message is saved for processing after return from the procedure. If the VLR does not support CCBS. The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later. and the VLR configuration requires paging via the SGSN during VLR restoration. If the GMSC does not support CAMEL Phase 3 or later. processing continues from connector 5.3.078 [12].2 7. 7.3. 7. handling continues from the "No" exit of the test "CUG info present?".2. it is specified in subclause 7. If the VLR does not support CUG.2.0 (2011-03) Sheet 3: the procedure CCBS_ICH_Handle_NDUB is specific to CCBS.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. it is specified in 3GPP TS 23.093 [23]. Sheet 3: the output signal Page MS towards the SGSN includes the Location area identity parameter.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. Sheet 3: if the VLR does not support CUG.2. 7. If the GMSC does not support CAMEL Phase 3 or later. Sheet 5. Sheet 4.018 V10. processing continues from the "Yes" exit of the test "Result = Pass?". Sheet 6: the test "NDUB?" is executed only if the VLR supports CCBS.3.2.072 [11]. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.2.1. The output signal Page MS towards the SGSN omits the Location area identity parameter.078 [12].093 [23]. Sheet 7: the procedure Handle_CFNRc is specified in subclause 7.2. Sheet 8: the procedures CAMEL_O_CSI_Check_VLR. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Aborted?". sheet 6: the procedure CD_Authorization is specific to Call Deflection.2. sheet 6: the procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later. processing continues from the "Forward" exit of the test "Result".11.

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

093 Idle 2 Wait_For_ Access_ Request Figure 76b: Process ICH_VLR (sheet 2) 3GPP .018 V10. Signals to/from the right are to/from the process PRN_VLR. Prepaging supported? Yes True PAR pending False Wait_For_ PAR_Completed No PAR completed True PAR successful False Call arrived True 11 Fatal PAR error False Set negative response: Impossible call completion No Location area ID known? Yes No CCBS_ICH_VLR_ Report_Failure See TS 23.1.Release 10 218 3GPP TS 23.093 Yes Send Info For Incoming Call negative response Set Paging via SGSN possible Paging via SGSN possible? Idle Search_For_ MS_VLR Page MS Page type= circuit-switched call Yes Result= Pass? No Yes Result= Fail? No CCBS_ICH_VLR_ Report_Failure See TS 23.0 (2011-03) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call 10 ICH_VLR2(8) Signals to the left are to the VMSC.

0 (2011-03) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call Wait_For_ Access_ Request ICH_VLR3(8) Signals to/from the left are to/from the VMSC.Release 10 219 3GPP TS 23.1.093 CCBS_ICH_VLR_ Report_Failure Busy subscriber? Yes Idle 3 1 12 NDUB? No Yes Multicall supported in VLR? No Yes Location Cancelled ? Yes No Get_CW_ Get_CW_ Subscription_ Subscription_Info_ Info_VLR Multicall_VLR No CW available? Yes 9 GMSC supports MT Roaming No Retry Yes set MT Roaming Retry Indicator Send Info For Incoming Call Ack CCBS_ICH_ Handle_NDUB Idle 13 Get_LI_ Subscription_ Info_MT_VLR Get_AoC_ Subscription_ Info_VLR 4 See TS 23.018 V10.093 No Yes CCBS_ICH_ Report_Not_ Reachable Wait_For_ Access_ Request See TS 23.093 Release Result Forward 8 5 Figure 76c: Process ICH_VLR (sheet 3) 3GPP . Page MS negative response MT Roaming Retry supported No Absent subscriber? No Yes 2 Page MS via SGSN Abort 12 13 Page MS To SGSN See TS 23.

081 CLI_ICH_VLR_ Add_CLI CCBS_ICH_VLR_ Report_Failure See TS 23.085 CCBS_ICH_VLR_ Report_Failure See TS 23.018 V10.093 Yes Success? Idle CAMEL_CHECK _SII2_CDTI No Yes Result = Pass? No CFNRy A&O? Yes Provide NRCT value No 3 Get_LI_ Subscription_ Info_MT_VLR Get_AoC_ Subscription_ Info_VLR Set negative response: System failure See TS 23.093 Complete Call Send Info For Incoming Call negative response Wait_For_ Complete_Call_ Result Idle Figure 76d: Process ICH_VLR (sheet 4) 3GPP .0 (2011-03) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call Wait_For_ Access_ Request ICH_VLR4(8) Signals to/from the left are to/from the VMSC.1.Release 10 220 3GPP TS 23. Process Access Request Process_ Access_ Request_VLR No 11 Result= Pass? Yes CUG info present? No Yes Translate CUG interlock to index As defined in TS 23.

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

078 Yez Result = Pass? No No CFNRy A&O? Yea Set NRCT CLI_ICH_VLR_ Add_CLI See TS 23. CAMEL_CHECK _SII2_CDTI See TS 23.018 V10.0 (2011-03) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call 4 ICH_VLR6(8) Signals to/from the left are to/from the VMSC.072 9 No Result= Aborted? Yes No Result= Fail? Set negative response: Impossible call completion Yes CCBS_ICH_ Handle_UDUB See TS 23.Release 10 222 3GPP TS 23.081 Process Call Waiting Wait_For_ PCW_Result Process Call Waiting ack Abort Process Call Waiting negative response Yes Idle Busy subscriber? No No subscriber reply? No CD_ Authorization Yes NDUB? Yes No See TS 23.093 Send Info For Incoming Call negative response 7 Idle 6 5 Figure 76f: Process ICH_VLR (sheet 6) 3GPP .1.

093 Send Info For Incoming Call negative response 7 Idle 7 Figure 76g: Process ICH_VLR (sheet 7) 3GPP .0 (2011-03) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call Signals to the left are to the VMSC 1 ICH_VLR7(8) Handle_CFNRc 5 Yes Result= Fail? Handle_CFB Set negative response: Forwarding Violation Yes Result= Fail? No Set negative response: Forwarding Violation No Yes Set negative response: Absent Subscriber No Result= Forward? 7 6 8 Handle_CFNRy No Result= Forward? Yes CCBS_ICH_ Set_CCBS_ Target Set negative response: Forwarding Violation Yes Result= Fail? No See TS 23.093 No Result= Forward? Set negative response: No Subscriber Reply Yes Set negative response: Busy Subscriber CCBS_ICH_ Set_CCBS_ Target See TS 23.Release 10 223 3GPP TS 23.1.018 V10.

Release 10 224 3GPP TS 23.0 (2011-03) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call 7 Signals to the left are to the VMSC.078 Send Info For Incoming Call ack Send Info For Incoming Call negative response Idle Idle Figure 76h: Process ICH_VLR (sheet 8) Figure 77: Void 3GPP .078 CAMEL_ D_CSI_ CHECK_VLR See TS 23. ICH_VLR8(8) Forward_ CUG_Check Result= Call allowed? Yes No Set result: Forward Set negative response: CUG reject Set forwarding information CAMEL_ O_CSI_ CHECK_VLR See TS 23.018 V10.1.

e. page in all location areas) Signals to/from the left are to/from the MSC SRCH_V1(1) No Paging via SGSN possible? Yes Set paging via SGSN possible Search For MS Page type= Circuit-switched call Wait_For_ Search_Result PgA is sent if PgA supported and received Search For MS ack Search For MS negative response Abort Search for MS via SGSN Update Location Area ID To SGSN Page MS Result:= Pass Result:= Fail Result:= Aborted Wait_For_ Search_Result Figure 78: Procedure Search_For_MS_VLR 3GPP .018 V10.1.0 (2011-03) Procedure Search_For_MS_VLR Procedure in the VLR to search for an MS (i.Release 10 225 3GPP TS 23.

1.0 (2011-03) Procedure Get_CW_Subscription_Info_VLR Procedure in the VLR to retrieve subscription information for the Call Waiting service Signals to/from the right are to/from the process MAF013 CWI_VLR1(1) initiate handling of CW Wait_For_ CW_Info From MSC Abort process call waiting Figure 79: Procedure Get_CW_Subscription_Info_VLR 3GPP .018 V10.Release 10 226 3GPP TS 23.

1.0 (2011-03) Procedure Get_LI_Subscription_Info_MT_VLR Procedure in the VLR to retrieve subscription information for the CLIP & COLR line identification services for an MT call Initiate handling of CLIP GLI_MTV1(1) To process CLIP_MAF001 Wait_For_ CLIP_Info From MSC Abort Continue call handling From process CLIP_MAF001 Initiate handling of COLR To process COLR_MAF040 Wait_For_ COLR_Info From MSC Abort Continue call handling From process COLR_MAF040 Figure 80: Procedure Get_LI_Subscription_Info_MT_VLR 3GPP .Release 10 227 3GPP TS 23.018 V10.

0 (2011-03) Procedure Handle_CFB Procedure in the VLR to handle Call Forwarding on Busy H_CFB1(1) Signals to/from the right are to/from the process MAF008 CAMEL_CHECL _SII2_CDTI See TS 23.Release 10 228 3GPP TS 23.018 V10.078 No Result = Pass? Yes initiate handling of CFB Wait_For_ CFB_Result continue call handling Yes Error? No Normal call busy? No Yes Result:= Fail Result:= Forward Result:= Busy Figure 81: Procedure Handle_CFB 3GPP .1.

018 V10.0 (2011-03) Procedure Handle_CFNRy Procedure in the VLR to handle Call Forwarding on No subscriber Reply Signals to/from the right are to/from the process MAF009 H_CFNRy1(1) initiate handling of CFNRy Wait_For_ CFNRy_Result continue call handling Yes Error? No No Normal call? Yes Result:= Fail Result:= No reply Result:= Forward Figure 82: Procedure Handle_CFNRy 3GPP .Release 10 229 3GPP TS 23.1.

1. sheet 7.1 Functional requirements of serving MSC 7. Sheet 8: the procedure Handle_ECT_Active is specific to ECT. The process Subs_FSM interacts with the processes OCH_MSC and ICH_MSC as specified in subclauses 7. sheet 15: processing on this page will occur only if the VMSC supports HOLD. which then responds appropriately.Release 10 230 3GPP TS 23. sheet 9. sheet 11. It monitors the state of any ongoing calls for that subscriber. Sheet 8: the procdure Handle_MPTY is specific to MPTY. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. sheet 14: processing on this page will occur only if the VMSC supports both HOLD and Multicall.091 [22].1.1.1 and 7. The individual call control processes OCH_MSC and ICH_MSC submit supplementary service requests received from the MS to the process Subs_FSM.1. Sheet 5. 3GPP .091 [22]. it is specified in 3GPP TS 23. sheet 6. sheet 8.3.018 V10. Sheet 13.4.084 [17].1 Process Subs_FSM One instance of the process Subs_FSM runs for each subscriber who is involved in at least one call.4 Subs_FSM 7. Sheet 12: the procedure Handle_ECT_Alerting is specific to ECT.0 (2011-03) 7. Sheet 10: processing on this page will occur only if the VMSC supports Multicall. sheet 12.4.

1.2 7.1. Speech_Call_Cnt:=0 Non_Speech_Call_Cnt:=0 Speech_CallA:=Null Speech_CallB:=Null Non_Speech_Calls:=Null OG_Call_Alerting:=False Idle Non speech TCH required Speech TCH required Non_Speech_ Calls:=Setup Speech_CallA:= Setup Allocate TCH Setup_ Pending Figure 83a: Process Subs_FSM (sheet 1) 3GPP .0 (2011-03) 7.4.1.4.1.1.4.4 Macro Check_Ongoing_Calls Macro Update_Non_Speech_Calls_Status Macro Increment_Call_Counter Macro Decrement_Call_Counter SFSM1(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.3 7.Release 10 231 3GPP TS 23.018 V10.1 7.1.1.1.4.1.

0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.Release 10 232 3GPP TS 23.1.018 V10. SFSM2(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Setup_ Pending Call established Call setup failed Increment_ Call_Counter Non_Speech Speech Speech_CallA:=Null Speech_CallB:=Null Non_Speech_Calls:=Null Non_Speech_ Calls:=Active Speech_CallA:= Active Idle_ Data_Call_ Active Call_Active Idle Figure 83b: Process Subs_FSM (sheet 2) 3GPP .

Idle_ Data_Call_ Active SFSM3(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Non speech TCH required Speech TCH required Call cleared Non-Speech_ Calls:=Setup Speech_CallA:= Setup Allocate TCH Data_Call_ Active_ Setup_Pending Call cleared Call established Call setup failed Decrement_ Call_Counter Speech. Non_Speech Increment_ Call_Counter Speech Non_Speech Decrement_ Call_Counter Speech.Release 10 233 3GPP TS 23.018 V10. Non_Speech Check_ Ongoing_Calls Calls_Ongoing Speech_CallA:= Active Non_Speech_ Calls:=Active Check_ Ongoing_Calls Calls_Ongoing No_Calls_Ongoing No_Calls_Ongoing Data_Call_ Active_ Setup_Pending Setup_ Pending Call_Active Idle_ Data_Call_ Active Idle Figure 83c: Process Subs_FSM (sheet 3) 3GPP .1.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

Release 10 234 3GPP TS 23. Call_Active SFSM4(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Hold request Non speech TCH required Speech TCH required Call cleared Hold ack Allocate TCH TCH already allocated Decrement_ Call_Counter Speech.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1.018 V10. Non_Speech Check_ Ongoing_Calls Calls_Ongoing No_Calls_Ongoing Yes Ongoing speech call? No Speech_CallA:= Held Non_Speech_ Calls:=Setup Speech_CallA:= Null Speech_CallA:=Null Speech_CallB:=Null Call_Held Call_Active_ Data_Call_ Setup_Pending Call_Active Idle_ Data_Call_ Active Idle Figure 83d: Process Subs_FSM (sheet 4) 3GPP .

Release 10 235 3GPP TS 23.018 V10.1.1 Nonspeech call using TCH? Yes No Speech_CallA:= Null Update_Non_ Speech_ Calls_Status Retrieve reject Retrieve ack Yes Non_Speech_ Call_Count = 0? No Idle_ Data_Call_ Active Speech_CallA:= Active Idle Call_Held Call_Active Figure 83e: Process Subs_FSM (sheet 5) 3GPP .0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1 Non_Speech_Call_Cnt . SFSM5(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC unless marked otherwise Call_Held From held call Call cleared Call cleared Retrieve request Speech_Call_Cnt:= Non_Speech_Call_Cnt:= Speech_Call_Cnt .

018 V10.Release 10 236 3GPP TS 23. SFSM6(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC unless marked otherwise Call_Held Speech TCH required Non speech TCH required Nonspeech call using TCH? Yes TCH available Allocate TCH No TCH available Speech_CallB:= Setup Non_Speech_ Calls:=Setup Call_Held_ Setup_Pending Call_Held_ Data_Call_ Setup_Pending Figure 83f: Process Subs_FSM (sheet 6) 3GPP .0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1.

signals from the right are internal MSC signals unless marked otherwise Retrieve request Non speech TCH required Hold request Speech TCH required Retrieve reject Allocate TCH TCH already allocated Non_Speech_ Calls:=Setup Handle_ Timed_Call_ Swap Se 3G TS 23.018 V10. T_Expr Result? Active_Clr Call_Held_ Call_Active Hold_Clr Call_Held_ Call_Active Call_Held Call_Active Figure 83g: Process Subs_FSM (sheet 7) 3GPP .1.Release 10 237 3GPP TS 23. Call_Held_ Call_Active SFSM7(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.083 Call_Held_ Call_Active Call_Held_Call_ Active_Data_Call Setup_Pending Retr_req.

Call_Held_ Call_Active SFSM8(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC MPTY request ECT request MPTY supported? Yes No No ECT supported? Yes See TS 23.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.091 Result Call_Held_ Call_Active Fail Result Pass End End_Active End_Held Fail No Non-speech call ongoing? Yes Idle Idle_ Data_Call_ Active Call_Active Call_Held Call_Held_ Call_Active Idle Call_Held_ Call_Active Figure 83h: Process Subs_FSM (sheet 8) 3GPP .1.018 V10.084 Handle_ MPTY MPTY reject ECT reject Handle_ECT_ Active See TS 23.Release 10 238 3GPP TS 23.

Call_Held_ Call_Active SFSM9(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC unless marked otherwise Call cleared From held call Call cleared Speech_Call_Cnt:= Speech_Call_Cnt .1 Non_Speech Decrement_ Call_Counter Speech Speech_CallA:=Active Speech_CallB:=Null Update_Non_ Speech_ Calls_Status Speech_CallB:= Null Call_Active Call_Held_ Call_Active Call_Held Figure 83i: Process Subs_FSM (sheet 9) 3GPP .018 V10.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1.Release 10 239 3GPP TS 23.

1. Call_Active_ Data_Call_ Setup_Pending SFSM10(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Call established Call setup failed Call cleared Retrieve request Hold request Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt + 1 Retrieve reject Hold ack Non_Speech_ Calls:=Active Update_Non_ Speech_ Calls_Status Decrement_ Call_Count Speech Non_Speech Yes Non-speech call ongoing? No Speech_CallA:= Null Update_Non_ Speech_ Calls_Status Call_Active Data_Call_ Active_ Setup_Pending Setup_Pending Call_Active_ Data_Call_ Setup_Pending Call_Held_ Setup_Pending Figure 83j: Process Subs_FSM (sheet 10) 3GPP .Release 10 240 3GPP TS 23.018 V10.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

Non_Speech Nonspeech call ongoin? Yes No Non_Speech_ Calls:=Active Speech_CallB:= Active Check_ Ongoing_Calls Calls_Ongoing No_Calls_Ongoing Speech_CallB:= Null Non_Speech_ Calls:=Active Non_Speech_ Calls:=Null Yes Speech call ongoing? No Speech_CallA:=Setup Speech_CallB:=Null Call_Held Call_Held_ Call_Active Call_Held_ Setup_Pending Data_Call_ Active_ Setup_Pending Setup_Pending Figure 83k: Process Subs_FSM (sheet 11) 3GPP . Call_Held_ Setup_Pending SFSM11(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Call setup failed Call established Call cleared OG_Call_ Alerting:=False OG_Call_ Alerting:=False OG_Call_ Alerting:=False Yes Speech call? No Increment_ Call_Count Non_Speech Speech Decrement_ Call_Count Speech.018 V10.Release 10 241 3GPP TS 23.1.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

Release 10 242 3GPP TS 23.1.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.091 Handle_ECT_ Alerting ECT reject Pass Result Fail OG_Call_ Alerting:=True OG_Call_ Alerting:=False Call_Held_ Setup_Pending Call_Held_ Setup_Pending Idle Call_Held_ Setup_Pending Figure 84l: Process Subs_FSM (sheet 12) 3GPP .018 V10. Call_Held_ Setup_Pending SFSM12(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Alerting in progress Hold request Retrieve request ECT request Hold reject Retrieve reject Yes ECT supported? No See TS 23.

0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.083 Handle_ Timed_Call_ Swap Retrieve reject Non_Speech_ Calls:=Active Update_Non_ Speech_ Calls_Status Call_Held_Call_ Active_Data_Call_ Setup_Pending Retr_req.1. T_Expr Result Active_Clr Hold_Clr Call_Held_ Call_Active Call_Held_Call_ Active_Data_Call_ Setup_Pending Call_Held_ Setup_Pending Call_Active_ Data_Call_ Setup_Pending Figure 84m: Process Subs_FSM (sheet 13) 3GPP . Call_Held_Call_ Active_Data_Call_ Setup_Pending SFSM13(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Call established Call setup failed Hold request Retrieve request Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt + 1 See 3G TS 23.018 V10.Release 10 243 3GPP TS 23.

1 Speech_Call_Cnt:= Speech_Call_Cnt .Release 10 244 3GPP TS 23. Call_Held_Call_ Active_Data_Call_ Setup_Pending SFSM14(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC From held call Call cleared Call cleared Call cleared From active call Speech_Call_Cnt:= Speech_Call_Cnt .018 V10.1 Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt .1 Speech_CallA:=Active Speech_CallB:=Null Yes Speech call ongoing? No Speech_CallA:=Held Speech_CallB:=Null Speech_CallB:= Null Call_Active_ Data_Call_ Setup_Pending Call_Held_Call_ Active_Data_Call Setup_Pending Setup_Pending Call_Held_ Data_Call_ Setup_Pending Figure 84n: Process Subs_FSM (sheet 14) 3GPP .0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1.

1.Release 10 245 3GPP TS 23. Call_Held_ Data_Call_Setup_ Pending SFSM15(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Call setup failed Call established Call cleared Hold request Retrieve request Update_Non_ Speech_ Calls_Status Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt + 1 Non_Speech_Call_Cnt .1 Hold reject Nonspeech call using TCH? Yes No Update_Non_ Speech_ Calls_Status Retrieve reject Retrieve ack Speech call ongoing? No Speech_CallA:= Null Yes Speech_CallA:= Active Call_Held Data_Call_Setup_ Pending Call_Held_ Data_Call_Setup_ Pending Call_Active_ Data_Call_ Setup_Pending Figure 84o: Process Subs_FSM (sheet 14) 3GPP .018 V10.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

1.Release 10 246 3GPP TS 23. SFSM16(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC * Request call status Call status - Figure 84p: Process Subs_FSM (sheet 14) 3GPP .0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.018 V10.

SFSM17(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Except for the following states: "Call Held Call Active" "Call Held Setup Pending" * ECT request ECT reject - Figure 84q: Process Subs_FSM (sheet 14) 3GPP .1.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.018 V10.Release 10 247 3GPP TS 23.

018 V10.Release 10 248 3GPP TS 23.0 (2011-03) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1. SFSM18(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC Except for the following state: "Call Held Call Active" * MPTY request MPTY reject - Figure 84r: Process Subs_FSM (sheet 14) 3GPP .

COC1(1) Non_ Speech_Call_ Cnt 0 Non_Speech_ Calls:=Null >=1 Speech_ Call_Cnt 0 >=1 No_Calls_ Ongoing Calls_ Ongoing Figure 85: Macro Check_Ongoing_Calls 3GPP .0 (2011-03) Macrodefinition Check_Ongoing_Calls Macro to check if there are any speech or non-speech calls remaining (and also update the Non_Speech_Calls status variable.Release 10 249 3GPP TS 23.1.018 V10.

018 V10.0 (2011-03) Macrodefinition Update_Non_Speech_Calls_Status Macro to update the Non_Speeh_Calls variable depending on whether there are any non-speech calls ongoing or not.Release 10 250 3GPP TS 23. Upd_NSC_Stat1(1) Yes Non-speech call ongoing? No Non_Speech_ Calls:=Active Non_Speech_ Calls:=Null Figure 86: Macro Update_Non_Speech_Calls_Status 3GPP .1.

0 (2011-03) Macrodefinition Increment_Call_Counter Macro to increment the correct counter depedning on the type of the current call.Release 10 251 3GPP TS 23.1.018 V10. Inc_Call_Cnt1(1) No Speech call? Yes Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt + 1 Speech_Call_Cnt:= Speech_Call_Cnt + 1 Non_ Speech Speech Figure 87: Macro Increment_Call_Counter 3GPP .

Release 10 252 3GPP TS 23. Inc_Call_Cnt1(1) No Speech call? Yes Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt .0 (2011-03) Macrodefinition Decrement_Call_Counter Macro to decrement the correct counter depedning on the type of the current call.018 V10.1 Non_ Speech Speech Figure 88: Macro Decrement_Call_Counter 3GPP .1.1 Speech_Call_Cnt:= Speech_Call_Cnt .

078 [12]. it is specified in 3GPP TS 23. sheet 2: The variable “Return_Place” indicates at which detection point the additional digit collection is. If the MSC does not support CAMEL.078 [12]. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23. Sheet 3: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL.1. Sheet 1. sheet 2. sheet 4: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1. processing continues from the "Pass" exit of the test "Result?". Sheet 2: “Number_of_Digits” is the Collected_Info specific reporting criterion.1. processing continues from the "Pass" exit of the test "Result?".1 Process TO_MSC Sheet 1: the procedure CAMEL_TOC_INIT is specific to CAMEL.078 [12]. Sheet 3: the procedure UUS_MSC_Clear_UUS is specific to UUS. At the expiry of the timer.018 V10.1 Functional requirements of inter-connecting MSC 7. sheet 4: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later.5. the MSC/gsmSSF may report digits to the gsmSCF (if the event detection point is armed).078 [12]. If the MSC does not support CAMEL trunk triggering. Sheet 1. it is specified in 3GPP TS 23.078 [12].078 [12]. processing continues from the "Pass" exit of the test "Result=?". 3GPP . If the GMSC does not support CAMEL phase 4 or later. The gsmSCF specifies the criterion. Sheet 1. The procedure call formal parameter “First” or “NotFirst” indicates whether the procedure was called earlier in the same call. it is specified in 3GPP TS 23. Sheet 5: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. If the MSC does not support CAMEL.078 [12]. sheet2. and will occur only if the GMSC supports CAMEL phase 2 or later. it is specified in 3GPP TS 23.087 [20]. it is specified in 3GPP TS 23. Sheet 2: “ST digit” is the ISUP value for a digit indicating that the Called Party Number is complete. Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability. Sheet 1. This timer is used for the SDL modelling purposes only and it may not present the actual implementations. it is specified in 3GPP TS 23.5. sheet 2: The “inter-digit timer” is a MSC internal timer to wait for additional dialling from the incoming side.078 [12]. they are specified in 3GPP TS 23. it is specified in 3GPP TS 23. The process CS_gsmSSF sends the parameter to the TO_MSC process.078 [12].078 [12]. Sheet 3: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later.066 [10]. Sheet 1. it is specified in 3GPP TS 23. Sheet 1. sheet 3: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. it is specified in 3GPP TS 23. processing continues from the "Pass" exit of the test "Result?".078 [12].0 (2011-03) 7. it is specifed in 3GPP TS 23. Sheet 4: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL.5 TO call 7. sheet 7: the procedure CAMEL_MT_CF_LEG1_MSC is specific to CAMEL phase 4 or later. Sheet 3: the procedure CAMEL_CF_MSC_ALERTING is specific to CAMEL phase 4 or later. it is specified in 3GPP TS 23. The procedure call formal parameter “First” or “NotFirst” indicates whether the procedure was called earlier in the same call. sheet 4: the procedure CAMEL_TOC_Dialled_Services is specific to CAMEL phase 3 or later. Sheet 4: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later.Release 10 253 3GPP TS 23. Sheet 1.

If the MSC does not support CAMEL. Sheet 6: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL. Sheet 6: after the process TO_MSC has sent an IAM to the forwarded-to exchange. it is specified in 3GPP TS 23. Sheet 6: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL. processing continues from the "No" exit of the test "Result=Reconnect?" . it is specified in 3GPP TS 23.078 [12]. it is specified in 3GPP TS 23. 3GPP . it acts as a relay for messages received from the parent process and the forwarded-to exchange. processing continues from the "No" exit of the test "Result=CAMEL handling?". Sheet 7: the process CAMEL_MT_CF_LEG2_MSC is specific to CAMEL phase 4 or later.1.0 (2011-03) Sheet 6: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL.Release 10 254 3GPP TS 23.078 [12].018 V10. If the MSC does not support CAMEL.078 [12].

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

Release 10 256 3GPP TS 23. Inter_Digit_timer from SELF SAM Stop Inter_Digit_timer (Dialled number length >= Number_of_Digits) OR (ST digit received) No Start Inter_Digit_timer See TS 23. False) Wait_For_SAM Digits are waited based on timer for modelling purposes. Once timer expires.078 B C Figure 7.078 Yes CAMEL_Store_ Destination_ Address (False.0 (2011-03) Process TO_MSC Process in the MSC to handle trunk originated call.1.5. Return_Place? Dialled_Services Init See TS 23.018 V10. new digits are reported to gsmSCF. signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number.078 CAMEL_TOC_ MSC_INIT (NotFirst) CAMEL_TOC_ Dialled_Services (NotFirst) See TS 23.1b: Process TO_MSC (sheet 2) 3GPP . Wait_For_SAM TOMSC2(7) Signals to/from the left are to/from the originating switch. There may be vendor specic differences in this issue.

1. False) See TS 23.078 CAMEL_ Start_TNRy See TS 23.087 UUS_MSC_ Clear_UUS CAMEL_Store_ Destination_ Address (False.078 Result? Pass See TS 23. Address Complete Wait_For_ ACM TOMSC3(7) Signals to/from the left are to/from the originating switch.5. signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number.1c: Process TO_MSC (sheet 3) 3GPP .078 CAMEL_CF_ MSC_ANSWER CAMEL_CF_ MSC_ANSWER See TS 23.078 See TS 23.087 UUS_MSC_ Clear_UUS Else Else Result? Pass Reconnect Release Result? Fail Answer 2 Release Connect A Idle A Figure 7.Release 10 257 3GPP TS 23.078 CAMEL_CF_ MSC_ALERTING Answer Result? Pass Else SAM Address Complete Address Complete - Wait_For_ Answer Answer See TS 23.0 (2011-03) Process TO_MSC Process in the MSC to handle trunk originated call. Connect SAM See TS 23.018 V10.078 CAMEL_ Stop_TNRy UUS_MSC_ Clear_UUS See TS 23.087 See TS 23.

018 V10.0 (2011-03) Process TO_MSC Process in the MSC to handle trunk originated call.Release 10 258 3GPP TS 23. Int_ReleaseCall Release Release From gsmSSF CAMEL trunk triggering supported? No Yes No CAMEL trunk triggering supported? Yes Yes No 3 Release cause= No answer from user? CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC_DISC4 CAMEL_OCH_ MSC_DISC3 CAMEL_OCH_ MSC1 No See TS 23. Wait_For_ACM. Wait_For_Answer TOMSC4(7) Signals to/from the left are to/from the originating switch. signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number.1d: Process TO_MSC (sheet 4) 3GPP .1.078 Result= Reconnect? Yes CAMEL_ Stop_TNRy See TS 23.5.078 Release Release Release 2 Release Release call resources Idle Figure 7.

0 (2011-03) Process TO_MSC Process in the MSC to handle trunk originated call.1e: Process TO_MSC (sheet 5) 3GPP .078 2 Release Result? Fail Reconnect Release See TS 23.018 V10. TNRy expired Internal 3 Release CAMEL_OCH_ MSC2 See TS 23.5. signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number.078 CAMEL_TOC_ Dialled_Services (First) Abort Result? Fail Pass Release call resources See TS 23. Wait_For _ Answer TOMSC5(7) Signals to/from the left are to/from the originating switch.1.078 CAMEL_ OCH_MSC1 1 Idle Result= Reconnect? No Yes Release 2 Idle Figure 7.Release 10 259 3GPP TS 23.

5.1f: Process TO_MSC (sheet 6) 3GPP .0 (2011-03) Process TO_MSC Process in the MSC to handle trunk originated call.018 V10.Release 10 260 3GPP TS 23.1.078 CAMEL_OCH_ MSC_DISC2 Result= Yes CAMEL Handling? No Result= Reconnect? No Yes See TS 23. signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number. Wait_For_ Clear TOMSC6(7) Signals to/from the left are to/from the originating switch.078 Release Yes Release Release 2 Release Release call resources Idle * * * - - - Figure 7. Int_ReleaseCall From gsmSSF Release Release CAMEL_OCH_ MSC_DISC1 Result= CAMEL Handling? No See TS 23.

except for the following messages.0 (2011-03) Process TO_MSC Process in the MSC to handle trunk originated call.1g: Process TO_MSC (sheet 7) 8 Contents of messages On the D interface (VLR-HLR): Abort. which are not specific to call handling: 3GPP . A TOMSC7(7) CAMEL phase 4 or later control relationship exists? Yes See TS 23.018 V10.078 No CAMEL_MT_ CF_LEG2_MSC When this process calls CAMEL_MF_RECONNECT_MSC the formal call parameters "BOR" and "Forwarding" in CAMEL_Store_Destination_Address shall be "False". See TS 23.Release 10 261 3GPP TS 23. This clause specifies the content of each message shown in clauses 5 and 7. Activate Trace Mode.5.1.078 Leg1_status := Active Wait_For_ Clear CAMEL_TOC_ LEG1_MSC (Leg1_status) Idle Figure 7. Authentication Failure Report.

If the information element is shown as conditional or optional in this clause.1 Abort The following information element is required: Information element name Abort reason Required M Description Indicates the reason for the procedure being aborted.102 [32]) Authentication token to be sent to the MS (3GPP TS 33. and the conditions in the derived specification require the information element to be present. Send Authentication Info negative response. 8.Release 10 262 3GPP TS 23. it shall always be present. at the discretion of the application at the sending entity. If the specification for a service or feature requires information elements in a message additional to those specified in this clause. A conditional information element shall be present if certain conditions are fulfilled. then the following principles apply: If the information element is shown as mandatory in this clause. An optional element may be present or absent.1 Messages on the B interface (MSC-VLR) 8. If the specification for a service or feature has different requirements for the presence of an information element in a message which is specified in this clause.2 Authenticate The following information elements are required for authentication of a UMTS UE: Information element name RAND(I) AUTN(I) Required M M Description Random number challenge to be sent to the MS (3GPP TS 33. - 8. if those conditions are not fulfilled it shall be absent. information elements are shown as mandatory (M). conditional (C) or optional (O).1. Send Authentication Info ack.1. it shall always be present in the context of the service or feature defined in the derived specification. Some messages which are defined in this clause are used for other services or features. it shall be present even if the conditions in this clause do not require it to be present. but mandatory in the derived specification.018 V10. in this case the requirements for the presence of each information element are as defined in this clause. The specifications (referred to below as "derived specifications") for those services or features may simply refer to the present document for the definition of the message.1. If the information element is shown as conditional or optional in this clause.102 [32]) 3GPP . the requirements for the presence of the additional information elements are specified in the relevant specification. A mandatory information element shall always be present.0 (2011-03) - Insert Subscriber Data. Send Authentication Info. In the tables which follow.

020 [1]) 8.5 Call arrived This message contains no information elements.1. 8.1.020 [1]) 8. 8.018 V10.020 [1]) Cipher key sequence number to be sent to the MS (3GPP TS 43. grey-listed or white-listed 8.4 Authenticate negative response The negative response information element can take the following value: wrong network signature.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.1.1.8 Check IMEI negative response The negative response information element can take the following values: System failure.Release 10 263 3GPP TS 23.1. 3GPP .0 (2011-03) 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 (3GPP TS 43. 8.6 Check IMEI This message contains no information elements.102 [32]) 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 (3GPP TS 43.3 Authenticate ack The following information element is required for authentication of a UMTS UE: Information element name RES(I) Required M Description Result returned by the MS (3GPP TS 33.1. Unknown equipment.1.

otherwise shall be absent. Shall be present for an ordinary MO call if the call is a CUG call. otherwise shall be absent. otherwise shall be absent. Indicates that CLIP is provisioned. Shall be present for an MT call if CLIP is provisioned. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. Shall be present for an MO call if COLP is provisioned. For the definition of this IE. 3GPP .085 [18].Release 10 264 3GPP TS 23. otherwise shall be absent. Indicates that the CLIR override subscription option of CLIP is provisioned. otherwise shall be absent. 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. Shall be present for an ordinary MO call if the call is a CUG call with outgoing access. Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. otherwise shall be absent. Shall be present for an MT call if COLR is provisioned. otherwise shall be absent.0 (2011-03) 8. otherwise shall be absent. May be present (as a network operator option) for an ordinary MO call if the call is a CUG call. Shall be present for an MT call if CLIP is provisioned with the CLIR override subscription option and the MS is registered in the HPLMN country. otherwise shall be absent. Shall be present for an ordinary MO call or an MT call if Advice of Charge is provisioned. Shall be present for an MT call according to the rules defined in 3GPP TS 29. see 3GPP TS 23. Category of the MS for which the Complete Call is sent.085 [18]. Value of timer to be used to determine the No subscriber reply condition. Shall be present for an ordinary MO call. Shall be present for an MT call if the Call Forwarding on No Reply service is active and operative. Indicates the mode in which CLIR is provisioned: permanent.007 [30]. see 3GPP TS 23. Shall be present for an MT call if it was received in the Provide Roaming Number. otherwise shall be absent. for an MT call and for an emergency call when the MS is registered in the VLR. 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. Shall be present for an MT call if it was received in the Provide Roaming Number.1. Indicates that COLP is provisioned. otherwise shall be absent. Indicates that the COLR override subscription option of COLP is provisioned. see 3GPP TS 23. otherwise shall be absent. For the definition of this IE. otherwise shall be absent. Indicates that COLR is provisioned. otherwise shall be absent. Shall be present for an ordinary MO call and for an emergency call when the MS is registered in the VLR. Shall be present for an MT call if it was received in the Provide Roaming Number.085 [18]. Shall be present for an MO call if CLIR is provisioned. Shall be present for an MO call if CLIR is provisioned. otherwise shall be absent. shall be present for an MT call if the call is a CUG call.9 Complete Call The following information elements are required: Information element name MSISDN Required C IMEI Category PLMN bearer capability ISDN bearer capability ISDN low layer compatibility ISDN high layer compatibility CLIP provision CLIR override provision C C C C C C C C CLIR provision CLIR mode C C COLP provision COLR override provision C C COLR provision No Reply Condition Timer C C CUG index C CUG interlock CUG outgoing access Advice of Charge provision C C C Alerting Pattern C Description MSISDN of the MS for which the Complete Call is sent. Indicates that CLIR is provisioned. IMEI of the mobile for which the Complete Call is sent.1. For the definition of this IE. otherwise shall be absent. Shall be present for an emergency call when the mobile is identified only by its IMEI.018 V10. temporary (default presentation allowed) or temporary (default presentation restricted).

Indicates that the VLR requires state information for the MS.10 Complete Call ack This message contains no information elements.1. otherwise shall be absent. Busy subscriber. 8.15 Obtain Subscriber Info The following information elements are required: Information element name IMSI Subscriber state requested Required M C Description IMSI of the MS for which information is required.1.1. 8.018 V10. No subscriber reply. 8. 8.1.14 Forward New TMSI negative response The negative response information element can take the following value: TMSI reallocation failure.12 Forward New TMSI The following information element is required: Information element name TMSI Required M Description TMSI to be sent to the MS.1. Radio congestion. 8. This parameter may be included at the discretion of the VLR operator.1.0 (2011-03) Information element name NAEA preferred Carrier Id Required O Description The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier.13 Forward New TMSI ack This message contains no information elements.1. 8. Shall be present if state information is required.1.Release 10 265 3GPP TS 23.16 Obtain Subscriber Info ack The following information elements are required: 3GPP . 8.11 Complete Call negative response The negative response information element can take the following values: Absent subscriber.

IMEISV as defined in 3GPP TS 23.1.018 V10.MS classmark. . otherwise shall be absent.Location. Shall be present if the VLR requested state information. otherwise shall be absent. otherwise shall be absent. MS classmark 2 as defined in 3GPP TS 24. Shall be present if the Page type is Active Information Retrieval.008 [26]. 8.0 (2011-03) Information element name Subscriber state Required C Description Indicates whether the MS is busy (i. SS activity or Active Location Retrieval. Service area identity of the cell in which the served subscriber is located.e. Identity of the cell in which the served subscriber is located.067 [39]). Shall be present if the IMEI was requested in the Page MS message and the MSC retrieved it from the MS. 3GPP . Indicates whether the paging is for a circuit-switched call.1.19 Page MS negative response The negative response information element can take the following values: Absent subscriber. 8. Indicates the information requested by the VLR – one or more of: .1. otherwise shall be absent. 8. Busy subscriber (More calls possible). Location area in which the MS is to be paged.003 [5]. otherwise shall be absent. MT SMS delivery. Indicates that paging via the SGSN is possible.IMEI. otherwise shall be absent. This parameter should be present if the VLR supports the eMLPP feature and if the Call Priority was received in the MAP_PROVIDE_ROAMING_NUMBER request or in the MAP PROVIDE_SUBSCRIBER_INFO request. TMSI to be broadcast to identify the MS. Shall be present if the MS uses UMTS radio access. Shall be present if the VLR determines that the MS can be paged via the SGSN.1. This parameter indicates the eMLPP priority of the call (see 3GPP TS 23. Shall be present if the MS uses GSM radio access.18 Page MS ack The following information elements are required: Information element name Location area ID Serving cell ID Service area ID MS classmark IMEI (with software version) Required M M C M C Description Location area in which the MS responded to the page.Release 10 266 3GPP TS 23. . engaged on a circuitswitched call) or assumed idle.17 Page MS The following information elements are required: Information element name IMSI Location area ID Page type Requested information Required M M M C Paging via SGSN possible TMSI Call Priority C O O Description IMSI of the MS to be paged.

Type of channel required for the call. Identity of the service area (for UMTS access) in use by the served subscriber.22 Process Access Request ack The following information elements are required: 3GPP . 8.1. otherwise shall be absent. Circuit-switched paging priority.018 V10. TMSI or IMEI shall be present. Other values (short message service and SS request) defined for this IE are not considered in the present document. IMSI of the MS requesting the access. TMSI or IMEI shall be present. The Page MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call. 8. Cipher key sequence number of the MS requesting the access.1.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.1. otherwise shall be absent. IMEI of the MS requesting the access. System failure. one of IMSI. Shall be present if TMSI is present. Identity of the cell (for GSM access) in use by the served subscriber. TMSI to be broadcast to identify the MS.1. one of IMSI.0 (2011-03) - Busy subscriber (NDUB). For normal MO call or page response. For emergency call. For normal MO call or page response. TMSI or IMEI shall be present. emergency call or page response. otherwise shall be absent. one of IMSI or TMSI shall be present. Unknown location area ID. one of IMSI.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 Serving cell ID IMSI TMSI IMEI CKSN M M C C C C C C Description Indicates the type of access required: normal MO call. Shall be present for GSM access. Identity of the location area from which the access request was received. one of IMSI or TMSI shall be present. TMSI of the MS requesting the access. For emergency call. Indicates whether or not the connection to the MS is ciphered and whether or not it is authenticated. one of IMSI or TMSI shall be present. For normal MO call or page response. Shall be present for UMTS access. For emergency call.Release 10 267 3GPP TS 23. 8.

24 Process Call Waiting The following information elements are required: Information element name MSISDN PLMN bearer capability ISDN bearer capability ISDN low layer compatibility ISDN high layer compatibility CLIP provision CLIR override provision Required M C C C C C C COLR provision No Reply Condition Timer CUG index Advice of Charge provision C C C C Description MSISDN of the MS for which the Process Call Waiting is sent.018 V10. Shall be present according to the rules defined in 3GPP TS 29. Shall be present if it was received in the Provide Roaming Number for the waiting call.0 (2011-03) Information element name IMSI IMEI MSISDN Required C C O Description IMSI of the MS requesting the access. Value of timer to be used to determine the No subscriber reply condition. otherwise shall be absent.085 [18]. MSISDN of the MS requesting the access. shall be present. otherwise shall be absent. System failure. otherwise shall be absent. 3GPP . Shall be present if CLIP is provisioned. one of IMSI or IMEI shall be present.1. Shall be present if the Call Forwarding on No Reply service is active and operative. Shall be present if Advice of Charge is provisioned. otherwise shall be absent.1. For the definition of this IE.23 Process Access Request negative response The negative response information element can take the following values: Roaming not allowed. For emergency call. 8. Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. shall be absent. Shall be present if CLIP is provisioned with the CLIR override subscription option and the MS is registered in the HPLMN country. Indicates that CLIP is provisioned. Indicates that COLR is provisioned. otherwise shall be absent. IMEI of the MS requesting the access. For emergency call. Illegal equipment. Shall be present if the waiting call is a CUG call. Illegal subscriber.1.25 Process Call Waiting ack This message contains no information elements. Shall be present if it was received in the Provide Roaming Number for the waiting call.007 [30]. 8.Release 10 268 3GPP TS 23. Shall be present if COLR is provisioned. Shall be present if it was received in the Provide Roaming Number for the waiting call. Indicates that the CLIR override subscription option of CLIP is provisioned. For normal MO call or page response. For normal MO call or page response. Unidentified subscriber.1. see 3GPP TS 23. one of IMSI or IMEI shall be present. 8. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent.

1.27 Provide IMEI This message contains no information elements.Release 10 269 3GPP TS 23.32 Search For MS The following information elements are required: 3GPP .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.1.1. No subscriber reply.29 Provide IMSI This message contains no information elements. Busy subscriber (NDUB). 8.1.0 (2011-03) 8.1. 8. 8.26 Process Call Waiting negative response The negative response information element can take the following values: Busy subscriber (UDUB).31 Radio connection released This message contains no information elements.1.1. 8. 8. 8.003 [5]) of the ME involved in the access request.018 V10.1.28 Provide IMEI ack The following information element is required: Information element name IMEI Required M Description IMEISV (as defined in 3GPP TS 23.

System failure. Indicates whether the paging is for a circuit-switched call.Release 10 270 3GPP TS 23. otherwise shall be absent.1. Indicates the information requested by the VLR – one or more of: . Shall be present if the VLR determines that the MS can be paged via the SGSN. 3GPP . . The Search For MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call.067 [39]). MS classmark 2 as defined in 3GPP TS 24. otherwise it shall be absent. This parameter indicates the eMLPP priority of the call (see 3GPP TS 23. 8.33 Search For MS ack The following information element is required: Information element name Location area ID Serving cell ID Service area ID MS classmark IMEI (with software version) Required M C C M C Description Location area in which the MS responded to the page.0 (2011-03) Information element name IMSI Page type Requested information Required M M C Paging via SGSN possible TMSI Paging area C O O Call Priority O Description IMSI of the MS to be paged in all location areas.Location. Busy subscriber (NDUB).008 [26].003 [5]. . Identity of the cell in which the served subscriber is located.MS classmark. May be present if the Paging type is circuit switched call.018 V10. SS activity or Active Location Retrieval. Service area identity of the cell in which the served subscriber is located. otherwise shall be absent. otherwise shall be absent. This parameter should be present if the VLR supports the eMLPP feature and if the Call Priority was received in the MAP_PROVIDE_ROAMING_NUMBER request or in the MAP PROVIDE_SUBSCRIBER_INFO request. Indicates that paging via the SGSN is possible. Shall be present if the IMEI was requested in the Page MS message and the MSC retrieved it from the MS.34 Search For MS negative response The negative response information element can take the following values: Absent subscriber. It indicates the set of Location Areas in which the MS is to be paged on the A interface if Location area ID is not known in VLR. Shall be present if the Page type is Active Information Retrieval. TMSI to be broadcast to identify the MS. if the Paging Area function is supported and if the paging area is available. otherwise shall be absent. 8. Shall be present if the MS uses GSM radio access. MT SMS delivery. Busy subscriber (More calls possible). IMEISV as defined in 3GPP TS 23.1. Shall be present if the MS uses UMTS radio access.IMEI. otherwise shall be absent.1.

otherwise shall be absent. Shall be present if the MSC was able to derive a teleservice from ISDN BC/LLC/HLC information received in the IAM.1. Shall be present if the MSC was able to derive a bearer service from ISDN BC/LLC/HLC information received in the IAM. Bearer service required for the MT call. For the definition of this IE.1. Shall be present if it was received in the IAM. Type of channel required for the call. For the definition of this IE.Release 10 271 3GPP TS 23. Number of times the incoming call has already been forwarded. 3GPP . otherwise shall be absent.085 [18].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.1. see 3GPP TS 23.0 (2011-03) 8. Shall be present if it was received in the IAM. 8. TMSI to be broadcast to identify the MS. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. Number dialled by the calling subscriber. Shall be present if it was received in the IAM. Circuit-switched paging priority.085 [18].018 V10. see 3GPP TS 23.36 Send Info For Incoming Call The following information elements are required: Information element name MSRN Bearer service Teleservice Dialled number Number of forwarding CUG interlock CUG outgoing access Required M C C C C C C Description Mobile Station Roaming Number received in the IAM. Shall be present if it was received in the IAM. otherwise shall be absent. Teleservice required for the MT call.

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.085 [18]. see 3GPP TS 23. For the definition of this IE. Shall be present if the call is to be forwarded. E.085 [18]. No subscriber reply.1. Indication of whether the calling party is to be notified that the call has been forwarded.085 [18]. For the definition of this IE. Shall be present if the call is to be forwarded other than for MT roaming retry reason. otherwise shall be absent. Unallocated roaming number.164 number of the C subscriber. otherwise shall be absent. otherwise shall be absent. Forwarding violation. E. Shall be present if a forwarded-to subaddress is stored in the VLR in association with the forwarded-to number. CUG reject (Called party SS interaction violation). Shall be present if the call is to be forwarded. Shall be present if the call is to be forwarded other than for MT roaming retry reason. 8. Subaddress of the C subscriber (see 3GPP TS 23. 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. otherwise shall be absent. System failure.003 [5]).1. 3GPP . on mobile subscriber not reachable or on no subscriber reply). Impossible call completion. Shall be present if the call is to be forwarded on mobile subscriber busy or on no subscriber reply.38 Send Info For Incoming Call negative response The negative response information element can take the following values: Absent subscriber. on mobile subscriber busy. This parameter may be included at the discretion of the VLR operator. Indication that the call is forwarded for MT roaming retry.1.Release 10 272 3GPP TS 23. Indication of why the call has been forwarded (on call deflection.085 [18]. Indication of whether the forwarding party is to be notified that the call has been forwarded. Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber. otherwise shall be absent. It will be used to create the redirecting number presented to the C subscriber. see 3GPP TS 23.37 Send Info For Incoming Call ack The following information elements are required: Information element name IMSI Forwarded-to number Forwarding reason Required M C C Notification to calling party Notification to forwarding party C C Forwarded-to subaddress C Redirecting presentation MSISDN CUG interlock C C C CUG outgoing access C NAEA preferred Carrier Id O MT Roaming Retry Indicator C Description IMSI of the B subscriber.018 V10.0 (2011-03) 8.164 number which identifies the B 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. otherwise shall be absent. Busy subscriber. All other forwarding parameters are not relevant if this IE is present. Shall be present if the call is to be forwarded other than for MT roaming retry reason.

1. Call barred (Operator determined barring).1. For the definition of this IE.003 [5]. For the definition of this IE. CUG reject (Unknown CUG index).index incompatible with basic service).018 V10. Shall be present if it was received in the set-up request from the MS. see 3GPP TS 23. see 3GPP TS 23.1. One of bearer service or teleservice shall be present.1.no CUG selected). see 3GPP TS 23. CUG reject (Outgoing calls barred within the CUG). Teleservice not provisioned.1. Shall be present if it was received in the set-up request from the MS.41 Start security procedures The following information elements are required for a UMTS connection: 3GPP .39 Send Info For Outgoing Call The following information elements are required: Information element name Called number Bearer service Teleservice Required M C C CUG index Suppress preferential CUG Suppress CUG outgoing access C C C Description E. derived from the PLMN bearer capability information received in the set-up request from the MS or from the emergency set-up request from the MS. For the definition of this IE. CUG reject (Inconsistent access information .40 Send Info For Outgoing Call negative response The negative response information element can take the following values: Bearer service not provisioned.40A Send UESBI-Iu to Access Network The following information element is required: Information element name IMEI (with software version) Required C Description IMEISV as defined in 3GPP TS 23.Release 10 273 3GPP TS 23. 8.164 number of the call destination. derived from the PLMN bearer capability information received in the set-up request from the MS.085 [18]. CUG reject (Inconsistent access information . One of bearer service or teleservice shall be present.085 [18].0 (2011-03) 8. Teleservice required for the MO call. Shall be present if it was received in the set-up request from the MS. Call barred (Supplementary service barring).085 [18]. Bearer service required for the MO call. 8. 8.

008 [3] 8.1. otherwise shall be absent. 8. 8.1 Send Routeing Info The following information elements are required: 3GPP .43 Use existing TMSI This message contains no information elements. The following information elements are required for a GSM connection: Information element name Ciphering mode Kc Required M C Description Indicates whether ciphering of the radio connection is required.1.1.2. Shall be present if the ciphering mode indicates that ciphering of the radio connection is required.102 [32]). 8.44 Release MSRN The following information elements are required: Information element name MSRN Required M Description Mobile Station Roaming Number received with the message RELEASE RESOURCES. and if so which ciphering algorithm is to be used.42 Trace subscriber activity The following information elements are required: Information element name Trace reference Trace type Required M M Description Reference number to be included with tracing reports which the VMSC sends to the OMC For the definition of this IE.Release 10 274 3GPP TS 23.018 V10.2 Messages on the C interface (MSC-HLR) 8.1. Ciphering key to be used if ciphering of the radio connection is required.102 [32]).0 (2011-03) 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. Integrity key to be used to verify the integrity of messages transferred over the radio link (see 3GPP TS 33. see 3GPP TS 52.

otherwise shall be absent.Release 10 275 3GPP TS 23. otherwise shall be absent. For the definition of this IE. ISDN higher layer compatibility. otherwise shall be absent. This parameter should be present if the GMSC supports the eMLPP feature and if the call is an eMLPP call. otherwise shall be absent.1. otherwise shall be absent. Shall be present if the GMSC received it in the IAM. This parameter indicates the eMLPP priority of the call (see 3GPP TS 23. ISDN lower layer compatibility.0 (2011-03) Information element name MSISDN Alerting Pattern CUG interlock CUG outgoing access Number of forwarding ISDN BC ISDN LLC ISDN HLC Pre-paging supported Call Priority Required M C C C C C C C C O Description MSISDN of the B subscriber (see 3GPP TS 23. otherwise shall be absent.085 [18]. Shall be present if the GMSC received it in the IAM. see 3GPP TS 23. 3GPP .067 [39]). Number of times the incoming call has already been forwarded. Shall be present if received in a Connect operation from the gsmSCF. Shall be present if the GMSC supports pre-paging. otherwise shall be absent. The eMLPP priority levels A and B shall be mapped to the Call priority level 0.018 V10. Shall be present if it was received in the IAM.003 [5]). For the definition of this IE.085 [18]. Shall be present if the GMSC received it in the IAM. Shall be present if the GMSC received it in the IAM and the GMSC supports CUG. otherwise shall be absent. Shall be present if the GMSC received it in the IAM and the GMSC supports CUG. ISDN bearer capability. see 3GPP TS 23.

otherwise shall be absent.2 Send Routeing Info ack The following information elements are required: Information element name IMSI Roaming number Required M C Forwarded-to number Forwarded-to subaddress C C Notification to calling party Forwarding reason C 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. It will be used to create the redirecting number presented to the C subscriber. Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber.085 [18].1. 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 received it in the Provide Roaming Number ack and the call is not subject to early CF. 3GPP . Shall be present if the HLR has determined that the call is to be forwarded. Indication of whether the calling party is to be notified that the call has been forwarded. E.2. The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier. 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. This parameter may be included at the discretion of the HLR operator. Subaddress of the C subscriber (see 3GPP TS 23. For the definition of this IE. 8.085 [18].085 [18].018 V10. see 3GPP TS 23.003 [5]). Shall be present if the HLR has determined that the call is to be forwarded. Shall be present if the HLR has determined that the call is to be forwarded. Indication of why the call has been forwarded (unconditionally or on mobile subscriber not reachable).164 number required to route the call to VMSCB (see 3GPP TS 23. otherwise shall be absent. CUG reject (Called party SS interaction violation). E. Shall be present if the HLR has determined that the call is to be forwarded. otherwise shall be absent.Release 10 276 3GPP TS 23.164 number which identifies the B subscriber (basic MSISDN). 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. otherwise shall be absent. CUG reject (Incoming calls barred within CUG).3 - Send Routeing Info negative response The negative response information element can take the following values: Absent subscriber. Shall be present if the HLR has determined that the call is to be forwarded.003 [5]). CUG reject (Requested basic service violates CUG constraints). otherwise shall be absent. Call barred (Supplementary service barring).0 (2011-03) 8. otherwise shall be absent.164 number of the C subscriber. Bearer service not provisioned. For the definition of this IE. Call barred (Operator determined barring).2.085 [18]. otherwise shall be absent. otherwise shall be absent.003 [5]). otherwise shall be absent. E. see 3GPP TS 23.

1. Data missing.Release 10 277 3GPP TS 23. System Failure.3.0 (2011-03) - CUG reject (Subscriber not member of CUG).1 Provide Roaming Number The following information elements are required: 3GPP . Teleservice not provisioned. Unexpected data value. Unknown subscriber. Forwarding violation Number changed. 8.3 Messages on the D interface (VLR-HLR) 8. Facility not supported.018 V10.

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

. Indicates that the HLR requires active location retrieval.003 [5]. 8. MS classmark 2 as defined in 3GPP TS 24.003 [5]). Facility not supported. . Unexpected data value. Shall be present if subscriber state was requested.018 V10. . otherwise shall be absent.3. Data missing.MS classmark. Indicates which of the following information the HLR requires: . 8.5 Provide Subscriber Info ack The following information elements are required: Information element name Location information Subscriber state Required C C IMEI (with software version) MS classmark C C Description Information to define the location of the MS: see definition in subclause 8.e.1. Shall be absent if the requested information does not indicate that the HLR requires location information. Shall be present if location information was requested and is available.IMEI (with software version). otherwise shall be absent. Shall be present if the MS classmark was requested. Indicates the eMLPP priority of the call (see 3GPP TS 23.008 [26]. Should be present if the HLR supports this parameter and if the Call Priority was received in the MAP_SEND_ROUTING_INFORMATION request. otherwise shall be absent. network determined not reachable (IMSI detached or roaming in a prohibited location area) or assumed idle.4 Provide Subscriber Info The following information elements are required: Information element name IMSI LMSI Requested information Required M C M Active location retrieval requested Call Priority C O Description IMSI of the subscriber for whom information is requested (see 3GPP TS 23.5.3. Indicates whether the MS is busy (i.1.3. Local Mobile Subscriber Identity. Shall be present if the IMEI was requested. Shall be present if the LMSI was sent to the HLR at location updating.Release 10 279 3GPP TS 23. otherwise shall be absent. 3GPP . engaged on a circuitswitched call).0 (2011-03) - Absent subscriber. No roaming number available.067 [39]). IMEISV as defined in 3GPP TS 23.location information.subscriber state. OR not allowed.

cell global identity or location area identity. Shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval. Shall be present if the VLR can derive it from the stored service area identity. 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. otherwise shall be absent.1. Shall be present if the MS uses UMTS radio access and the subscriber record is marked as confirmed by radio contact. For a definition of this information element. If the HLR receives it from the VLR it shall ignore it. Measured in minutes.763 [35]. cell global identity or location area identity. Shall be present if available in the MSC/VLR. 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. otherwise shall be absent.0 (2011-03) 8. Shall be present if the MS uses E-UTRAN radio access and the subscriber record is marked as confirmed by radio contact.018 V10. otherwise shall be absent. E-UTRAN cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. see 3GPP TS 23. 8. otherwise shall be absent. Shall be present if the MS uses E-UTRAN radio access and the cell ID is not known.7 Restore Data The following information elements are required: 3GPP . 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. Shall be present if the MS uses GSM radio access and the subscriber record is marked as confirmed by radio contact.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 E-UTRAN Cell ID O C C C Tracking area ID C Description For a definition of this information element.Release 10 280 3GPP TS 23. otherwise shall be absent.3.003 [5]). otherwise shall be absent.164 number which identifies the VLR (see 3GPP TS 23. otherwise shall be absent. E.032 [7] .3. see ITU-T Recommendation Q. otherwise shall be absent 8.3.6 Provide Subscriber Info negative response The negative response information element can take the following values: Data missing.5. Unexpected data value. Tracking area identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. This information element corresponds to the Calling Geodetic Location defined in ITU-T Recommendation Q. 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.763 [35]. Shall be present if the VLR can derive it from the stored service area identity.

3.4.4.3 Check IMEI negative response The negative response information element can take the following value: Unknown equipment.8 Restore Data ack The following information elements are required: Information element name HLR number MS not reachable flag Required M C Description E. 8. LMSI of the subscriber for whom data are to be restored (see 3GPP TS 23.164 number which identifies the HLR (see 3GPP TS 23.003 [5]). otherwise shall be absent.4 Messages on the F interface (MSC-EIR) 8.3. grey-listed or white-listed 8.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. Shall be present if the corresponding indicator is set in the HLR record for the subscriber. Unknown subscriber.4.1.003 [5]).0 (2011-03) Information element name IMSI LMSI Required M O Description IMSI of the subscriber for whom data are to be restored (see 3GPP TS 23. May be included if required by the requesting VLR.003 [5]).9 Restore Data negative response The negative response information element can take the following values: System failure.003 [5]). Indicates whether the VLR should notify the HLR when the MS next establishes radio contact. 8.018 V10. 8. 8.1 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.Release 10 281 3GPP TS 23. 3GPP .

2 Perform Call Forwarding The following information element is required: Information element name Forwarded-to number OR call Required M M Description E. 8.6.164 number of the C subscriber.5. Note: this number may be different from the Forwarded-to number received in the Perform Call Forwarding.2 PAR completed This message contains no information elements.5.1 CF cancelled This message contains no information elements.5.079 [13] 8.6 Messages on the VLR internal interface This interface carries messages between corresponding instances of the processes PRN_VLR and ICH_VLR.Release 10 282 3GPP TS 23. 8.1 Call arrived This message contains no information elements. 3GPP .6. 8.1. it carries the following inter-process messages. Indicates whether the call which is to be forwarded was subject to basic OR as specified in 3GPP TS 23.164 number of the C subscriber.0 (2011-03) 8. 8.5. and ISUP messages received from the destination exchange and to be forwarded to the process MT_GMSC or the process ICH_MSC. The correlation between the process instances is done by the MSRN.3 Perform Call Forwarding ack The following information element is required: Information element name Forwarded-to number Required M Description E.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. 8. 8. as a result of CAMEL handling.018 V10.4 Perform Call Forwarding negative response The negative response information element can take the following value: Call forwarding failed. In addition.

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

Release 10 284 3GPP TS 23.1 Release Resources The following information elements are required: Information element name MSRN Required M Description Mobile Station Roaming Number. 3GPP .8 Messages on the E interface (GMSC-VMSC) 8.8.0 (2011-03) 8.1.018 V10.

It acts as a terminating exchange. It acts as a GMSC. i. it attempts to connect the call to an MS currently registered in the service area of the MSC. If the HLR returns routeing information. and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. i. which it sends to a destination exchange determined by analysis of the routeing information from the HLR. 3GPP . - Sheet 1: when the MSC co-ordinating setup procedure has decided whether the MSC is to act as a terminating VMSC.0 (2011-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. a GMSC or a transit exchange.018 V10.Release 10 285 3GPP TS 23. it forwards the IAM to an idle instance of the appropriate process.e.e.1. it relays the IAM to a destination exchange determined by analysis of the called party address. it interrogates an HLR for information to route the call. the MSC uses the routeing information from the HLR to construct an IAM.e. i. This behaviour is not specific to UMTS or GSM.

018 V10.0 (2011-03) procedure MSC_coord_setup Procedure in the MSC to handle an incoming IAM and trigger the correct application process 1(1) Called party address in MSRN range for this MSC? Yes No Incoming IAM was routed with routeing number for MNP? No Yes Recover ported number from IAM Yes To process ICH_MSC Initial Address Initial Address To process MT_GMSC Initial Address To destination determined by routeing tables HLR address derivable? No Figure 84a: Process MSC_Coord (sheet 1) 3GPP .Release 10 286 3GPP TS 23.1.

Release 10 287 3GPP TS 23.1.018 V10.0 (2011-03) Annex B (informative): Change history 3GPP .

0 Initialization of Backward Call indicator 3.0 4.5.1.2.018 23.4.0 Addition of the description for Pre-Paging 3.0 3.2.0 GMSC CAMEL phases in Provide Roaming Number 3.3.0 Clarification of N-CSI in Core NW 3.018 23.3.0 3.1.018 23.1.2.0 3.18 CN#03 23.018 23.0 Introduction of CAMEL Phase 3 3.0.0 3.018 23.4.0 3.3.3.0 Notification of Call Forwarding to the gsmSCF 3.0 Separation of success & failure cases for OR of late call forwarding 3.1.6.0 ISUP release cause value 3.0 3.018 23.018 002r4 006 007r1 023 024 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 055r4 064 065 067 069 Phase R4 Rel-4 Rel-4 Rel-4 Rel-4 Change history Version New Version Subject/Comment 7.4.4.4.0 3.018 23. 3.018 V10.018 23.0 4.5.4.5.0 3.0 Inclusion of call hold in basic call handling.5.0 Inclusion of D-CSI check in HLR/VLR 3.0 Correction of procedure Obtain_Routeing_Address for the reconnect case 3.018 23.1.018 23.018 23.0 3.018 23.3.4.018 23.6.0 Handling of the Call Diversion Treatment Indicator 3.4.0 Transferred to 3GPP CN1 3.018 23.0.5.0 Tidying up of Process Subs_FSM and interprocess signals 4.5.0 Correction to process ICH_VLR 3. 4.0 3.3.0 North American Service Provider Number Portability impacts for MNP 3.3.1.6.1.018 23.3.3.4.0 Clarification of NPDB error detection and MNP specific call handling 3.0 Modifications to procedure obtain routeing address.0 3.0 Approved at CN#03 3.0 3.0 Corrections to process ICH_VLR 3.0 4.018 23.0 3.0 3.0 3.018 23.0.018 23.018 23.0 Improvement of Active Retrieval of Location Information procedure 3.018 23.018 23.0 Removal of TDP criteria from Resume Call Handling 3.2.4.0 3.1.018 23.2.0 3.0 3.1.0 3.0 Correction of the SDL diagrams for Prepaging 3.4.018 23.6.018 23.0 3.0 Correction of connector numbering in process ICH_MSC 3.6.2.0 Addition of the description for Multicall 3.0 Update of CAMEL references 3.2.0.6.0 3.5.018 23.0 Removal of CW descriptions 4.018 001 CN#05 CN#05 CN#05 CN#05 CN#05 CN#06 CN#06 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#07 CN#08 CN#08 CN#08 CN#09 CN#09 CN#09 CN#09 CN#09 CN#09 CN#09 CN#09 CN#09 CN#10 CN#11 CN#11 CN#11 23.0 Setting the Destination Address for MO calls 3.018 23.0 4.018 3.018 23.0 (2011-03) TSG CN# Spec CR Apr 1999 GSM 03.0 Correction of the result of the procedure CAMEL_ICH_MSC_INIT 3.6.0 Correction of CF Notification 3.Release 10 288 3GPP TS 23.0 Replacement of references to GSM with references to UMTS 3.0 4.3.0 3.0 Correction of CAMEL Incoming Call Handling 3.0 3.3.0 3.018 23.4.018 23.0 3.5.2.2.0 Paging not via the SGSN correction 3GPP .3.6.018 23.4.1.5.0 3.0 O-CSI and D-CSI checks for ORLCF calls 3.2.0.0 Correction of the SDL diagram for Prepaging 3.0 Incorporation of MPTY and ECT into the Subs_FSM process 4.018 23.1.5.018 23.3.0 3.4.0 3.018 23.0 Notification of Call Forwarding to the gsmSCF before activating call forwarding process 3.4.3.3.3.0 3.6.0 3.018 23.0 3.4.018 23.0 Alternative solution for ALR 3.4.0 3.018 23.018 CN#04 23.5.0 Introduction of the Super-Charger Concept in TS 23.0 3.0 Introduction of Authentication Failure Report 3.

0 7.018 23.0.018 23.0 5.0 Paging optimization with A/Iu flex Rel-8 8.0 Collective CR for Rel-6 Enhanced Dialled Services Rel-6 6.0 Corrections in the ATI mechanism description Rel-5 5.018 23.2.0 Incorrect References Rel-7 7.018 23.0 Pre-Paging Resource Optimization Rel-6 6.8.3.4.0 5.018 23.018 23.018 23.0 5.0.0 5.3.2.0 5.3.1.6.3.0 Procedure Check_OG_Barring Missing SRIack negative response to ISUP release cause mapping in GMSC Rel-8 7.018 23.0 Setting of Leg1_Status variable Rel-5 5.0 Handling of Reconnect on Leg2 Disconnect Rel-5 5.0 Handling of CUG calls in non-supporting networks Rel-5 5.018 23.1.018 23.2.0 5.1.0 6.5.7.0 Stopping No_Answer timer in the case of forwarding notification Rel-5 5.0 Release Result from CAMEL_MT_GMSC_Notify_CF Rel-5 5.0 5.1.018 23.018 CR 074 072 077 081 091r2 082r2 088r2 093r1 098 100r1 109r1 110 111 112r1 118 115r2 122 124 128 133 132 126r1 135 137 141r1 143r1 144 145r1 146 0147 0150 0155 0157r4 0159 0160 0162 0163r2 0164r1 0166 - CT#40 CT#41 CT#42 CT#45 CT#46 23.018 23.1.0.018 23.0 Add “CAMEL_Stop_TNRy”in Procedure OG_Call_Setup _MSC (sheet 4) Rel-6 6.5.2.0 7.0 7.4.0.6.018 23.0.0 5.0 HLR Interrogation for SCUDIF calls Rel-6 5.1.2.2.0 5.0 Management Based Activation Impacts Rel-7 6.6.0 Correction in the ATI mechanism description Rel-5 5.0 Introduction of CAMEL Phase 4 Rel-5 5.018 23.0 5.3.0.018 23.0 5.0 eMLPP Priority in MAP SRI.0.SDLs Rel-7 7.4.0 5.7.6.0.0 Minor corrections to Process ICH_MSC Rel-5 5.0 8.0 Initialization of variable to monitor activation of CSI's Rel-5 4.4.3.0 Default Basic Service for gsmSCF-initiated calls Rel-6 6.2.0 Incorrect implementation of CR 133 Rel-6 6.018 23.3.0 Addition of procedure to retrieve UE-specific behaviour data Rel-5 5.3.0 PSI negative response 8.0 6.0 5.018 23.0 MSISDN in Provide Roaming Number in case of MSP Rel-5 5.2.007 Rel-7 7.0 5.2.7.2.3.0 7.018 V10.0 6.018 23.1.0 5.5.0 Mobile Termination whilst the MS is moving to another MSC Rel-7 7.018 23.2.1.018 23.2.3.1.7.0 5.0 Correction to the IC_CUG_Check Procedure Rel-7 7.2.018 23.018 CN#12 CN#13 CN#13 CN#14 CN#14 CN#15 CN#15 CN#15 CN#15 CN#15 CN#17 CN#17 CN#17 CN#18 CN#19 CN#20 CN#20 CN#20 CN#21 CN#21 CN#21 CN#22 CN#22 CN#22 CN#25 CN#25 CN#27 CT#28 CT#29 CT#30 CT#33 CT#34 CT#36 CT#36 CT#37 23.1.6.3.0 Handling of MultiCall in MPTY procedure Rel-5 5.0 6.0 Transferring the MS classmark & IMEI to the gsmSCF Rel-5 5.3.0 8.018 23.0 Correction on the Active Location Retrieval description Rel-5 5.0.0 Editorial clean up Rel-5 5.4.0 7.1.0 4.0 5.1.018 23.0 9.1.0 6.4.0 Addition of missing process Update_Location_VLR Rel-5 5.3.018 23.1 Copyright Notification updated Rel-8 8.0 Clarification of requirements for the presence of IEs in messages Rel-5 5.2.4.018 23.7.018 23.0 Trunk Originated CAMEL: Inter-digit timer stop/reset SDL correction Rel-7 7.1 8. PRN and PSI request Rel-8 8.018 23.018 23.0 5.018 23.0 7.0 5.2.018 23.0 Optional Suppress Terminating Services Bit String in SRI Rel-7 7.0 (2011-03) TSG CN# Spec CN#12 23.0 8.0 PLMN BC in PRN for alternate speech/fax alignment with TS 29.0 6.018 23.0 Trunk Originated CAMEL triggering .018 23.4.8.6.5.0 Corrections to "Early UE" handling Rel-5 5.3.0 7.0.018 23.018 23.0 Update to Rel-9 version (MCC) 3GPP .Release 10 289 3GPP TS 23.1.018 Change history Phase Version New Version Subject/Comment Rel-4 4.4.2.018 23.018 23.8.0 6.0 Removal of SIWF material Rel-6 6.0 5.5.3.0 Determining the basic service for MT calls Rel-5 5.0 7.

1.1.018 23.1.2.2.Release 10 290 3GPP TS 23.018 V10.0 9.0.0.0 9.0 MT Roaming Retry and Super Charger 3GPP .2.0 9.0 10.0 Correction for SMS via SGs charging Rel-9 9.1 10.1.018 CR 0167r4 0168r2 0170 0171 0174r2 0173 Change history Phase Version New Version Subject/Comment Rel-9 9.2.018 23.0 10.0 Mobile Terminating Roaming Forwarding Rel-10 10.018 23.018 23.0.018 CT#49 CT#49 CT#50 CT#51 CT#51 23.0 MT Roaming Retry Rel-10 10.0.0 (2011-03) TSG CN# Spec CT#47 23.0 SRI Negative Response Error Rel-9 9.0 Mobile Termination on Pre-paging whilst the MS is moving to another MSC Rel-9 9.1 History table version numbers corrected Rel-10 9.2.1.018 23.0 9.1.