You are on page 1of 281

3GPP TS 23.018 V7.5.

0 (2007-06)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Basic call handling; Technical realization (Release 7)

R

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

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

Release 7

2

3GPP TS 23.018 V7.5.0 (2007-06)

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.
© 2007, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.

3GPP

Release 7

3

3GPP TS 23.018 V7.5.0 (2007-06)

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.........................................................................................................17 5.3 Information flow for an MT call..........................................................................................................................19

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

7 Functional requirements of network entities........................................................................................24
7.1 MO call.................................................................................................................................................................25 7.1.1 Functional requirements of serving MSC.........................................................................................................25 7.1.1.1 Process OCH_MSC........................................................................................................................................25 7.1.1.2 Procedure Process_Access_Request_MSC....................................................................................................25 7.1.1.3 Procedure OG_Call_Setup_MSC...................................................................................................................25 7.1.1.4 Procedure Obtain_IMSI_MSC.......................................................................................................................27 7.1.1.5 Procedure Authenticate_MSC........................................................................................................................27 7.1.1.6 Procedure Obtain_IMEI_MSC.......................................................................................................................27 7.1.1.7 Procedure Check_IMEI_MSC.......................................................................................................................27 7.1.1.8 Procedure Establish_Originating_TCH_If_Required....................................................................................28 7.1.1.9 Procedure Set_CLI_Presentation_Indicator_MSC........................................................................................28

3GPP

Release 7

4

3GPP TS 23.018 V7.5.0 (2007-06)

7.1.1.10 Procedure Send_Alerting_If_Required........................................................................................................28 7.1.1.11 Procedure Set_COLP_Info_MSC................................................................................................................28 7.1.1.12 Procedure Send_Access_Connect_If_Required...........................................................................................28 7.1.1.13 Procedure Handle_AoC_MO_MSC.............................................................................................................28 7.1.1.14 Procedure TCH_Check................................................................................................................................29 7.1.2 Functional requirements of VLR......................................................................................................................55 7.1.2.1 Process OCH_VLR........................................................................................................................................55 7.1.2.2 Procedure Process_Access_Request_VLR....................................................................................................55 7.1.2.3 Procedure OG_Call_Subscription_Check_VLR............................................................................................55 7.1.2.4 Procedure Obtain_Identity_VLR...................................................................................................................55 7.1.2.5 Procedure Obtain_IMSI_VLR.......................................................................................................................55 7.1.2.6 Procedure Authenticate_VLR........................................................................................................................55 7.1.2.7 Procedure Obtain_Authentication_Sets_VLR...............................................................................................56 7.1.2.8 Procedure Start_Tracing_VLR.......................................................................................................................56 7.1.2.9 Procedure Check_IMEI _VLR.......................................................................................................................56 7.1.2.10 Procedure Obtain_IMEI_VLR.....................................................................................................................56 7.1.2.11 Process Fetch_Authentication_Sets_VLR...................................................................................................56 7.1.2.12 Procedure Check_BAOC.............................................................................................................................56 7.1.2.13 Procedure OG_CUG_Check........................................................................................................................56 7.1.2.14 Procedure Get_LI_Subscription_Info_MO_VLR........................................................................................56 7.1.2.15 Procedure Get_AoC_Subscription_Info_VLR............................................................................................56 7.1.2.16 Procedure Check_OG_Barring....................................................................................................................56 7.1.2.17 Process Update_Location_VLR...................................................................................................................56 7.2 Retrieval of routeing information for MT call.....................................................................................................83 7.2.1 Functional requirements of GMSC...................................................................................................................83 7.2.1.1 Process MT_GMSC.......................................................................................................................................83 7.2.1.2 Procedure Obtain_Routeing_Address............................................................................................................85 7.2.1.3 Procedure Send_ACM_If_Required..............................................................................................................86 7.2.1.4 Procedure Send_Answer_If_Required...........................................................................................................86 7.2.1.5 Procedure Send_Network_Connect_If_Required..........................................................................................87 7.2.1.6 Procedure Handle_COLP_Forwarding_Interaction_MSC............................................................................87 7.2.1.7 Procedure Activate_CF_Process....................................................................................................................87 7.2.1.8 Process MT_CF_MSC...................................................................................................................................87 7.2.1.9 Macro CUG_Support_Check_GMSC............................................................................................................89 7.2.2 Functional requirements of HLR....................................................................................................................115 7.2.2.1 Process SRI_HLR........................................................................................................................................115 7.2.2.2 Procedure Check_Parameters.......................................................................................................................117 7.2.2.3 Procedure Subscription_Check_HLR..........................................................................................................117 7.2.2.4 Procedure First_Forwarding_HLR...............................................................................................................118 7.2.2.5 Procedure PRN_Error_HLR........................................................................................................................118 7.2.2.6 Procedure Forward_CUG_Check................................................................................................................118 7.2.2.7 Void 118 7.2.2.8 Procedure Check_IC_Barring......................................................................................................................118 7.2.2.9 Procedure IC_CUG_Check..........................................................................................................................118 7.2.2.10 Procedure Handle_CFU.............................................................................................................................118 7.2.2.11 Procedure Handle_CFNRc.........................................................................................................................118 7.2.3 Functional requirements of VLR....................................................................................................................136 7.2.3.1 Process PRN_VLR.......................................................................................................................................136 7.2.3.2 Process Restore_Subscriber_Data_VLR......................................................................................................137 7.2.3.3 Process PSI_VLR.........................................................................................................................................137 7.2.3.4 Procedure Retrieve_Location_Info_VLR....................................................................................................137 7.2.3.5 Procedure Active_Info_Retrieval_VLR.......................................................................................................137 7.2.4 Functional requirements of MSC....................................................................................................................152 7.2.4.1 Process Prepage_MSC.................................................................................................................................152 7.2.4.2 Procedure Prepaging_Page_MS_MSC........................................................................................................152 7.2.4.3 Prepaging_Search_For_MS_MSC...............................................................................................................152 7.2.4.4 Process OSI_MSC........................................................................................................................................152 7.2.4.5 Process RCL_MSC......................................................................................................................................152 7.2.4.6 Procedure Active_Info_Retrieval_Page_MSC............................................................................................152 7.2.4.7 Procedure Active_Info_Retrieval_Search_MSC.........................................................................................152 7.2.4.8 Procedure Retrieve_IMEI_If_Required.......................................................................................................153

3GPP

Release 7

5

3GPP TS 23.018 V7.5.0 (2007-06)

7.3 MT call...............................................................................................................................................................161 7.3.1 Functional requirements of serving MSC.......................................................................................................161 7.3.1.1 Process ICH_MSC.......................................................................................................................................161 7.3.1.2 Procedure Page_MS_MSC...........................................................................................................................163 7.3.1.3 Procedure Search_For_MS_MSC................................................................................................................164 7.3.1.4 Procedure Complete_Call_In_MSC.............................................................................................................165 7.3.1.5 Void 166 7.3.1.6 Procedure Set_CLIP_Info_MSC..................................................................................................................166 7.3.1.7 Void 167 7.3.1.8 Procedure Establish_Terminating_TCH_If_Required.................................................................................167 7.3.1.9 Procedure Handle_AoC_MT_MSC.............................................................................................................167 7.3.1.10 Procedure Set_COL_Presentation_Indicator_MSC...................................................................................167 7.3.2 Functional requirements of VLR....................................................................................................................208 7.3.2.1 Process ICH_VLR........................................................................................................................................208 7.3.2.2 Void 209 7.3.2.3 Procedure Search_For_MS_VLR................................................................................................................209 7.3.2.4 Procedure Get_CW_Subscription_Info_VLR.............................................................................................209 7.3.2.5 Procedure Get_LI_Subscription_Info_MT_VLR........................................................................................209 7.3.2.6 Procedure Handle_CFB...............................................................................................................................209 7.3.2.7 Procedure Handle_CFNRy...........................................................................................................................209 7.4 Subs_FSM..........................................................................................................................................................223 7.4.1 Functional requirements of serving MSC.......................................................................................................223 7.4.1.1 Process Subs_FSM.......................................................................................................................................223 7.4.1.1.1 Macro Check_Ongoing_Calls...................................................................................................................224 7.4.1.1.2 Macro Update_Non_Speech_Calls_Status...............................................................................................224 7.4.1.1.3 Macro Increment_Call_Counter................................................................................................................224 7.4.1.1.4 Macro Decrement_Call_Counter..............................................................................................................224 7.5 TO call................................................................................................................................................................246 7.5.1 Functional requirements of inter-connecting MSC.........................................................................................246 7.5.1.1 Process TO_MSC.........................................................................................................................................246

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

3GPP

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

Should the TSG modify the contents of the present document. y the second digit is incremented for all changes of substance.0 (2007-06) Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). z the third digit is incremented when editorial only changes have been incorporated in the specification.y. 3 Indicates a TSG approved Release 1999 document under change control. up to the point where the call is established within the 3GPP system.018 V7.z where: x the first digit: 1 presented to TSG for information. 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. corrections. 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. updates. 4 Indicate a TSG approved Release 4 document under change control. 3GPP . 2 presented to TSG for approval. i.e.5. etc.Release 7 7 3GPP TS 23. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. technical enhancements.

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

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

Location Information: information to define the whereabouts of the MS.Release 7 10 3GPP TS 23.5. 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 PLMN BC 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 . 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. 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.the PLMN containing GMSCB Inter Working Unit Lower Layer Compatibility Mobile Originated MultiParTY Mobile Terminated Network Determined User Busy No Reply Call Timer (GSM or UMTS) PLMN Bearer Capability 3GPP .018 V7.1 Definitions For the purposes of the present document.0 (2007-06) 3 Definitions and abbreviations 3.2 Abbreviations For the purposes of the present document.

2 show the architecture for handling a basic MO call and a basic MT call.018 V7. any telephony signalling system may be used. 3GPP .0 (2007-06) PRN PUESBINE SCUDIF SGSN SIFIC SIFOC SRI TO UDUB UESBI-Iu VLRA VLRB VMSCA VMSCB VPLMNA VPLMNB 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.Release 7 11 3GPP TS 23. In a given network. In figure 1 and throughout the present document. as indicated in figure 1.1 Architecture for an MO call A basic mobile originated call involves signalling between the MS and its VMSC via the BSS. 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. between the VMSC and the VLR and between the VMSC and the destination exchange. the term BSS is used to denote a GSM BSS or a UTRAN. A basic mobile-to-mobile call is treated as the concatenation of an MO call and an MT call. 4. as appropriate.5.1 and 4. the term ISUP is used to denote the telephony signalling system used between exchanges.

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

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

Release 7 14 3GPP TS 23. NOTE 2: Security procedures may be initiated at any stage after authentication. the MSC may send a CM service accept towards the MS. This option is not available for a UMTS connection [ffs]. its position in this message flow diagram is an example.0 (2007-06) 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.018 V7. this is not shown in this message flow diagram. at any stage during the establishment of an MO call. and may check the IMEI. Figure 3: Information flow for a basic mobile originated call 3GPP . optionally it may instead send a "start ciphering" request indicating that no ciphering is required. the position in this message flow diagram is an example.5. NOTE 3: If ciphering is not required for a GSM connection. NOTE 4: The network may request the IMEI from the MS. either as part of the procedure to start security procedures or explicitly after security procedures have started.

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

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

Release 7 17 3GPP TS 23. It applies to a mobile terminating call while the called mobile is simultaneously moving from an old to a new MSC. if the GMSC. it indicates this by an information element in the PRN message. In that case. if pre-paging is supported. upon receipt of : an ISUP IAM message which was preceeded by a MAP Cancel Location procedure or by a Send Identification procedure for a super-charger subscriber. it is prepared to wait long enough for the PRN ack to allow pre-paging to be completed).0 (2007-06) HLRB decides whether pre-paging is supported according to the following criteria: GMSCB has indicated that it supports pre-paging. the HLR and the old terminating VMSC support the MT Roaming Retry procedure. 3GPP . GMSCB constructs an IAM using the roaming number.e. and HLRB supports pre-paging (i. 5.1 Mobile Terminating Roaming Retry Call The information flow for mobile terminating roaming retry call is shown in figure 4a. and retry the terminating call setup towards the new MSC by sending an additional SRI to the HLR. the old VMSC shall instruct the GMSC to resume terminating call procedure by sending a MAP Resume Call Handling message.018 V7. and sends it to VMSCB. HLRB sends a request for a roaming number (PRN) to VLRB.5. terminate any open CAP dialogue.2. The GMSC shall then release the ISUP connection to the old VMSC. and HLRB relays the roaming number to GMSCB in the SRI ack. VLRB returns the roaming number in the PRN ack. 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). or a MAP Cancel Location procedure or Send Identification procedure for a super-charger subscriber while ongoing paging.

5.Release 7 18 3GPP TS 23.0 (2007-06) GMSC SRI (B.018 V7. GMSC@ Figure 4a: Information flow for a mobile terminating roaming retry call S 3GPP .

e. Furthermore.5. A GMSC supporting the "mobile terminating roaming retry" feature includes the Call Reference Number. the new SRI shall be sent without the Roaming Retry Supported IE. ISUP signalling between GMSCB and VMSCB is shown by solid lines. depending on the state of the "follow-on" call and the subscriber's subscription data. different charging rates or regional service subscription). or upon receipt of the MAP Cancel Location message or MAP Send Identification message for super-charger subscriber while paging. Receipt of the MSRN' from the new MSC/VLR enables the GMSC to relay the call towards the new MSC/VLR. the GMSC shall use an appropriate high value for the timer supervising receipt of SRI ACK. A HLR supporting the "mobile terminating roaming retry" feature includes the Call Reference Number. terminates T-CSI dialog with the SCP. and signalling over the radio interface between VMSCB or BSSB and MSB is shown by dotted lines. and if it supports the "mobile terminating roaming retry" feature and did receive the MT Roaming Retry Supported IE in the PRN. 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. More generally. the GMSC address and the MT Roaming Retry Supported IE in the PRN sent to the MSC/VLR if received in the SRI. if the Location Update is received with the "follow-on" indication and if the VMSC supports the "follow-on" indication. Upon receipt of the RCH message with the MT roaming retry IE. USSD. this also applies to all TCAP transactions that the HLR may have to open toward a VLR (e. Similarly. Upon receipt of the ISUP IAM message which was preceeded by a MAP Cancel Location message or by a MAP Send Identification message for a supercharger subscriber. if any exists. signalling over the Iu interface (for UMTS) or the A interface (for GSM) between VMSCB and BSSB is shown by dashed lines. many variations are possible. MAP-ANY-TIME-INTERROGATION. 3. sends an RCH message to the GMSC with the MT Roaming Retry IE. If the IAM message is received before the Location Update procedure is completed with the MS. 8. the GMSC address and the MT Roaming Retry Supported IE in the first SRI sent to the HLR. PSI).g. 3GPP . 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 GMSC acknowledges the RCH message. using TAbandon EDP. the HLR delays the sending of the PRN to the new VLR till completion of the Update Location procedure. 2. releases the call towards the old MSC/VLR. 5. the incoming IAM may either be handled as a waiting call or forwarded as Busy (CFB). 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. In the former case.018 V7. 6. 4. 5. 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. 7.0 (2007-06) 1. To avoid looping.Release 7 19 3GPP TS 23.3 Information flow for an MT call An example information flow for an MT call is shown in figure 5. MAP-SEND-ROUTING-INFOFOR-SM.g. the old MSC/VLR stops paging. signalling over the B interface between VMSCB and VLRB is shown by chain lines. and re-sends a new SRI to the HLR (still a 'basic call' interrogation type) using a new call reference number. 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.g. MAP-SEND-ROUTING-INFO-FOR-LCS. if paging was on-going.

5. the paging procedure is not performed.Release 7 20 3GPP TS 23.0 (2007-06) 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. NOTE 5: If a connection between MSCB and MSB has been established as a result of pre-paging. the network may initiate authentication after the MS responds to paging. either as part of the procedure to start security procedures or explicitly after security procedures have been started. the MSC may send a Start security procedures message indicating that no ciphering is required. and may check the IMEI. the position in this message flow diagram is an example. at any stage after the MS responds to paging. NOTE 4: The network may request the IMEI from the MS. Figure 5: Information flow for a basic mobile terminated call 3GPP .018 V7. this is not shown in this message flow diagram. If this is not so (for the first MT call after VLR restoration). VLRB sends the Call arrived message to MSCB to stop the guard timer for the release of the radio connection. NOTE 3: This message flow diagram assumes that the MS has already been authenticated on location registration. NOTE 2: If Security procedures are not required. NOTE 6: If a connection between MSCB and MSB has been established as a result of pre-paging.

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

1 and 7.2.3.083 [16]) as described in subclause 7.2.4 Call wait (3GPP TS 23.1.2 Calling Line Identification Restriction (CLIR) The basic call handling processes OCH_MSC and OCH_VLR interact with the processes CLIR_MAF004 and CLIR_MAF003 (3GPP TS 23.3 Call forwarding services (3GPP TS 23.2. 6.0 (2007-06) 6.3.3 Call Forwarding on No Reply (CFNRy) The basic call handling process ICH_VLR interacts with the process MAF009 (3GPP TS 23.081) 6.1 and 7.1.081 [14]) as described in subclauses 7.082 [15]) as described in subclause 7. 6.3.3.018 V7.1 and 7. 6.1 and 7.1 and 7.2 Call Forwarding on mobile subscriber Busy (CFB) The basic call handling process ICH_VLR interacts with the process MAF008 (3GPP TS 23.3. 3GPP .2.3. 6.3.1.2.081 [14]) as described in subclauses 7.2.1 Calling Line Identification Presentation (CLIP) The basic call handling processes ICH_VLR and ICH_MSC interact with the processes CLIP_MAF001 and CLIP_MAF002 (3GPP TS 23.2 Line identification services (3GPP TS 23.4 Connected Line Identification Restriction (COLR) The basic call handling processes ICH_VLR and ICH_MSC interact with the processes COLR_MAF040 and COLR_MAF041 (3GPP TS 23.1.2 and 7.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. The basic call handling processes MT_GMSC and ICH_MSC interact with the process COLP_MAF039 (3GPP TS 23.2.083) The basic call handling process ICH_VLR interacts with the process MAF013 (3GPP TS 23. 6. 6. 6.081 [14]) as described in subclauses 7.Release 7 22 3GPP TS 23.1.3.2.2.3.2.3.2.081 [14]) as described in subclauses 7.5.082) 6.2.082 [15]) as described in subclause 7.2.2 and 7.082 [15]) as described in subclauses 7.3.082 [15]) as described in subclause 7.2.3.1 Call Forwarding Unconditional (CFU) The basic call handling process SRI_HLR interacts with the process MAF007(3GPP TS 23.081 [14]) as described in subclauses 7.2. 6.1. Further details of the handling of call waiting are given in subclauses 7.3.3.2.4 Call Forwarding on mobile subscriber Not Reachable (CFNRc) The basic call handling processes SRI_HLR and ICH_VLR interact with the process MAF010 (3GPP TS 23.3.

8 Advice of charge (3GPP TS 23. 6.7 Closed user group (3GPP TS 23. 6. 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.1 and 7.1.091) There is no interaction between Explicit Call Transfer and the basic call handling described in the present document.018 V7.6 Multiparty (3GPP TS 23.086 [19]) and MO calls are handled as described in subclauses 7.2.3.9 User-to-user signalling (3GPP TS 23.086 [19]) and MT calls are handled as described in subclauses 7.1 and 7. The interactions between Advice of Charge (3GPP TS 23. MT_GMSC and ICH_MSC interact with the UUS supplementary service as described in subclauses 7.3.088 [21]) as described in subclause 7. MAF018 and MAF020 (3GPP TS 23.5 Call hold (3GPP TS 23.1.085 [18]) are handled as described in subclause 7. 7.10.088 [21]) as described in subclause 7.2.1.11 Explicit Call Transfer (3GPP TS 23.1 Barring of outgoing calls The basic call handling process OCH_VLR interacts with the processes MAF017. 6.1 and 7.1.085 [18]) as described in subclause 7.085 [18]) as described in subclause 7.2.1.10.2.2 Barring of incoming calls The basic call handling process SRI_HLR interacts with the processes MAF022 and MAF023 (3GPP TS 23.1 and 7.5.084) Invocation of multiparty before a basic call has been established will be rejected.2. 3GPP .1.2.3. 6. 6.087) The basic call handling processes OCH_MSC.2. The interactions between call forwarding and CUG (3GPP TS 23. 6.0 (2007-06) 6.088) 6. The basic call handling process SRI_HLR interacts with the process CUG_MAF015 (3GPP TS 23. OCH_VLR.2.10 Call barring (3GPP TS 23.083) Invocation of call hold before a basic call has been established will be rejected.2.1.1 respectively.Release 7 23 3GPP TS 23.086) The interactions between Advice of Charge (3GPP TS 23.085) The basic call handling process OCH_VLR interacts with the process CUG_MAF014 (3GPP TS 23.2.6. 6. 7.2.1.1.3.

the handling is as defined in the appropriate protocol specification. MT_GMSC. The protocols used over the Iu interface are RANAP. - 3GPP . the MSC uses the routeing information from the HLR to construct an IAM.093) The basic call handling processes OCH_MSC.3.2. Q. It acts as a GMSC.008 [26]. it attempts to connect the call to an MS currently registered in the service area of the MSC.2. i. VLR & HLR (D) and MSC & EIR (F). The C. used to interwork between an MSC and another exchange.3. The protocols used over the A interface are BSSMAP.e. other telephony signalling systems may be used instead.e. ICH_MSC and ICH_VLR interact with the CCBS supplementary service as described in subclauses 7.2. used to interwork between the MSC and the GSM BSS or the GSM MS. 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. For the purposes of the present document.3. which it sends to a destination exchange determined by analysis of the routeing information from the HLR.008 [26]. OCH_VLR. and thereafter relays other telephony signalling between the originating and destination exchange until the connection is released. 7.008 [2]. SRI_HLR.1 and 7. used to interwork between the MSC and the UTRAN or the UMTS UE. i. which is specified in 3GPP TS 29. Each protocol defines supervision timers.e. OCH_VLR.1. This behaviour is not specific to UMTS or GSM. the protocol used over telephony signalling interfaces is ISUP. used to interwork between the MSC & HLR (C).2respectively.1 and 7.2.12 Completion of Calls to Busy Subscriber (3GPP TS 23. D & F interfaces. which is specified in ITU-T Recommendations Q. 7. which is specified in 3GPP TS 24.1. In general. i.413 [27]. the protocol handler reports timer expiry to the application as an error condition or negative response. which is specified in 3GPP TS 48.1. for interworking with the BSS and DTAP. Q.3.763 [35] and Q.1. for interworking with the MS. If a supervision timer expires before a distant entity responds to a signal.1.135) The basic call handling processes OCH_MSC. 7. 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. for interworking with the UTRAN and DTAP.3. 7 Functional requirements of network entities The text in this clause is a supplement to the definition in the SDL diagrams. for interworking with the MS. 7. The present document shows the call handling application processes interworking with a protocol handler for each of the protocols listed above.764 [36]. which is specified in 3GPP TS 25.761[33].762 [34]. Where a timer is shown in the present document. ICH_MSC & ICH_VLR interact with the Multicall supplementary service as described in subclauses subclauses 7.0 (2007-06) 6.2respectively. It acts as a terminating exchange. D & F interfaces is MAP. it does not duplicate the information in the SDL diagrams.1. If the HLR returns routeing information.1. The A interface.5.002 [29]. Telephony signalling interfaces. 7.Release 7 24 3GPP TS 23. 7. it is an application timer rather than a protocol timer.2. An MSC which receives an IAM from an originating exchange may react in three different ways: It acts as a transit exchange. The protocol used over the C. 7.018 V7. The entities described in this clause interwork with other entities over four different types of interface: The Iu interface. 6.2. therefore.13 Multicall (3GPP TS 23. which is specified in 3GPP TS 24. PRN_VLR.

Sheet 1: the procedure Check_OG_Multicall_MSC is specific to Multicall. The SDL diagrams in this clause show the handling for a number of optional features and services.1. Sheet 2. it is specified in 3GPP TS 23. If the handling consists of more than a call to a procedure specific to the feature or service. Send_Alerting_If_Required and Send_Access_Connect_If_Required. the VMSC may encapsulate the request for the IMEI in the Start security procedures message. Sheet 1: the variable UUS1 result sent is specific to UUS. the BSS relays the response in the Security procedures complete message to the MSC.1. Sheet 1: the task "Convert IMEISV to UESBI" is defined in 3GPP TS 23. it is assumed that support for Operator Determined Barring and the Call Forwarding and Call Barring supplementary services is mandatory.1.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.1.5. sheet 3: if the VMSC receives a Set-up message from the MS while the access request is being handled. MS connected and Reconnect are global data. it is specified in 3GPP TS 23.1 Functional requirements of serving MSC 7.Release 7 25 3GPP TS 23. they are specified in 3GPP TS 23. CCBS_OCH_Report_Success. the text associated with each SDL diagram specifies the handling which applies if the entity does not support an optional feature or service. Sheet 2: instead of using the explicit procedure Obtain_IMEI_MSC. The procedures CCBS_Report_Not_Idle and CCBS_Check_Last_Call are specific to CCBS.093 [23].001 [28]. Sheet 2: The Start security procedures message may indicate one of several ciphering algorithms.1 MO call 7. accessible to the procedure Establish_Originating_TCH_If_Required.3 Procedure OG_Call_Setup_MSC Sheet 1: the variables Alerting sent. If the handling consists only of a call to a procedure specific to the feature or service. Sheet 1: the procedure UUS_OCH_Check_Setup is specific to UUS.087 [20]. This variable is accessible to all UUS specific procedures. 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. it is specified in 3GPP TS 23. For simplicity of description. CCBS_OCH_Report_Failure. 3GPP .1 Process OCH_MSC The variable TCH allocated is global data. If the VMSC does not support Multicall. or (for GSM only) no ciphering. 7.1. sheet 3: At any stage. the procedure call is omitted if the entity does not support an optional feature or service. this signal will not be received. If the MSC does not support PUESBINE. the message is saved for processing after the access request has been handled.1. Sheet 2. 7.1. accessible to the procedures CCBS_Check_OG_Call. 7.0 (2007-06) Annex A describes the method which the MSC uses to decide how to process the IAM. 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.018 V7.135 [25]. processing continues from the "Yes" exit of the test "Result=Pass?". CCBS_Check_If_CCBS_Possible. the MS may terminate the transaction with the network by sending a CM service abort message.078 [12]. Sheet 1: the procedure CAMEL_N_CSI_CHECK_MSC is specific to CAMEL Phase 3 or later.195 [25a].010 [31].

The task "Store CCBS Result" is executed only if the VMSC supports CCBS. Sheet 6. sheet 3. Sheet 2.078 [12]. sheet 6: the procedure CCBS_OCH_Report_Failure is specific to CCBS.078 [12]. Sheet 3: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later.078 [12]. If the VMSC does not support CCBS. it is specified in 3GPP TS 23.066 [10].087 [20]. they are specified in 3GPP TS 23. sheet 7.093 [23]. Sheet 3: the procedure UUS_OCH_Set_Info_In_IAM is specific to UUS. sheet 7: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later.018 V7.078 [12]. Sheet 4. If the VMSC does not support CCBS. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 5: the procedure CAMEL_OCH_MSC_ANSWER is specific to CAMEL. it is specified in 3GPP TS 23. sheet 3. Sheet 3: the procedure Set_CLI_Presentation_Indicator_MSC is specific to CLIR. sheet 5. processing continues from the "Yes" exit of the test "Result=Pass?".5.078 [12]. Sheet 3: the procedure CAMEL_OCH_MSC_INIT is specific to CAMEL.Release 7 26 3GPP TS 23. sheet 4. it is specified in 3GPP TS 23. Sheet 5: the task "Store CW treatment indicator for this call if received in SII2" is executed only if the VMSC supports CAMEL phase 3 or later. sheet 7. it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?". If the VMSC does not support CAMEL phase 4 or later. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 5: The process CAMEL_OCH_LEG2_MSC is specific to CAMEL phase 4 or later.078 [12]. Sheet 3.078 [12]. processing continues from the "Yes" exit of the test "Result=Pass?". If the VMSC does not support CLIR. Sheet 5: the procedure Set_COLP_Info_MSC is specific to COLP. Sheet 1. Sheet 5: the procedure Handle_AoC_MO_MSC is specific to AoC. processing continues from the "CCBS Not Possible" exit of the test "CCBS Result". 3GPP . it is specified in 3GPP TS 23. sheet 2. the MS may terminate the transaction with the network by sending a Release transaction request. sheet 9: signals are sent to and received from the process Subs_FSM as described in subclause 7. sheet 7: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL Phase 1. Sheet 3: the procedure CCBS_Check_OG_Call is specific to CCBS. sheet 2.0 (2007-06) Sheet 1: the variable "On_Hold" is used only if the VMSC supports Call Hold. If the VMSC does not support CAMEL.078 [12].4. sheet 6. Sheet 3: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 1. If the VMSC does not support CAMEL phase 3 or later. processing continues from the "Pass" exit of the test "Result?". processing continues from the "Pass" exit of the test "Result?".093 [23]. processing continues from the "Yes" exit of the test "Result=Call allowed?". Sheet 3: the procedure CCBS_OCH_Report_Success is specific to CCBS.093 [23]. 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 9: at any stage after the Set-up has been received.078 [12]. they are specified in 3GPP TS 23. sheet 8. Sheet 3: the procedure CAMEL_MO_Dialled_Services is specific to CAMEL phase 3 or later. sheet 5: the procedure CAMEL_OCH_LEG1_MSC is specific to CAMEL phase 4 or later. If the VMSC does not support CAMEL.093 [23]. sheet 6. Sheet 6: the procedures CCBS_Check_If_CCBS_Possible and CCBS_Activation_MSC are specific to CCBS. it is specified in 3GPP TS 23.

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

The procedure UUS_OCH_Set_Alert_And_Connect_Param is specific to UUS.9 Procedure Establish_Originating_TCH_If_Required Procedure Set_CLI_Presentation_Indicator_MSC The MS may terminate the transaction with the network by sending a Release transaction message while a response is awaited from the process CLIR_MAF004. If no useful information would be carried in the Progress message.1.10 Procedure Send_Alerting_If_Required The test "Backward call indicator=no indication" refers to the called party's status field in the backward call indicators parameter of the ISUP Address Complete message which triggered the call of the procedure Send_Alerting_If_Required.087 [20].1. If the VMSC does not support UUS. 3GPP .087 [20]. The procedures UUS_MSC_Check_UUS1_UUI and UUS_OCH_Set_Alert_And_Connect_Param are specific to UUS. 7. 7.1.12 Procedure Send_Access_Connect_If_Required The test "Acknowledgement required" refers to the result returned by the procedure Handle_AoC_MSC.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.1.5.1.1. it is not sent. The message is saved for processing after return from the procedure. If the VMSC does not support AoC. 7. processing continues from the "Yes" exit of the test "Result=Pass?".018 V7.1. 7.1.0 (2007-06) 7.1. they are specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?". processing continues from the "No" exit of the test "Acknowledgement required".1. it is not sent. it is specified in 3GPP TS 23. If the VMSC does not support UUS.1.1. The message is saved for processing after return from the procedure.Release 7 28 3GPP TS 23. If no useful information would be carried in the Facility message.8 7.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.

14 Procedure TCH_Check OCH_MSC1(1) Process OCH_MSC Process in the MS C to handle an outgoing call request Signals from the left are from the BSS Idle CM service request Process_ Access_ Request_MSC No Resu lt= Pass? Ye s Wait _For_ Setup S etup CM Service Abort See TS 23.1.Release 7 29 3GPP TS 23.018 V7.0 (2007-06) 7.093 CCBS_Check_ Last_Call Rele ase call resources Idle Figure 6: Process OCH_MSC 3GPP .5.093 CCBS_Rep ort_ Not_Idle TCH allocated:= False OG_Ca ll_ Setu p_MSC See TS 23.1.

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 Result:= Fail Result:= Fail No Result= Pass? Yes 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 (2007-06) Procedure Process_Access_Request_MSC Procedure in the MSC to handle a request from the M for system access S PAR_MSC1(3) Signals to/from the left are to/fromthe BSS.Release 7 30 3GPP TS 23. signals to/from the right are to/fromthe VLR.5.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 .018 V7.

signals to/from the right are to/from the VL R.Release 7 31 3GPP TS 23.018 V7. Abort Proce ss Access Request negative response Process Access Requ est ack Yes CM Service type= P age Response? No Ciphering required True False Map negative response to reject cause Yes CM Service type = Page Resp onse? No Release transaction CM Service Reject Resu lt:= Fail Start security procedures CM Service Accept W ait_For_ TMS I_ Reallocation CM service abort Provide IMEI S etup Check IMEI Abort Forward New TMSI Use Existing TMSI Obtain_IMEI_ MS C Check_IMEI_ MSC Map negative re sponse to re ject cause Abort Result= Pass? Yes No No Result= Pass? Yes CM Service Reject Rea lloca te TMSI Result:= Fail Result:= Fail Result:= Fail Result:= Pass Wait_For_ TMSI_ Reallocation W ait_For_ TMS I_ Reallocation Wa it_For_ TMSI_Ack Figure 7b: Procedure Process_Access_Request_MSC (sheet 2) 3GPP .0 (2007-06) Procedure Process_Access_Request_MSC Procedure in t he MSC to handle a request from the MS for system access W ait_For_ P AR_Result PAR_MSC2(3) Signals to/from the left are to/from the BSS.5.

sig nals to/from the right are to/from the VLR. CM service abort Setup A bort TMSI Reallocation Fa ilure TMSI Reallocation Comple te Abort Forward New TMSI negative re sponse Forward New TMSI ack Result:= Fail Result:= Fail Result:= Pass Figure 7c: Procedure Process_Access_Request_MSC (sheet 3) 3GPP .018 V7.0 (2007-06) Procedure Process_Access_Request_MSC Procedure in t he MSC to handle a request from the MS for system access W ait_For_ TM SI_Ack PAR_MSC3(3) Signals to /from the left are to/from the BSS.5.Release 7 32 3GPP TS 23.

093 Wait_For_ MO_Call_ Result Figure 8a: Procedure OG_Call_Setup_MSC (sheet 1) 3GPP .Release 7 33 3GPP TS 23.0 (2007-06) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoi ng 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.087 Convert PLMN BC to basic service CAMEL_N_CSI_ CHECK_MSC See TS 23.5.018 V7.135 No Result= Pass? Yes Release transaction Send Info For Outgoing Call CCBS_OCH_ Report_Failure See TS 23.078 Check_OG_ Multicall_MSC See TS 23.

093 CCBS_OCH_ Report_Failure CCBS_OCH_ Report_Failure See TS 23.5.0 (2007-06) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoi ng 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 7 34 3GPP TS 23.018 V7.093 1 Figure 8b: Procedure OG_Call_Setup _MSC (sheet 2) 3GPP .

078 A Leg1_only Abort Fail CCBS_Check_ OG_Call No A See TS 23.093 See TS 23. signals to/from the right are to/from the destination exchange unless otherwise marked.Release 7 35 3GPP TS 23.Called Party Address CAMEL_Store_ Destination_ Address (False.018 V7.0 (2007-06) 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. Set_CLI_ Presentation_ Indicator_ MSC Result= Call allowed? Yes No Release transaction CAMEL_OCH_ MSC_INIT Yes See TS 23.093 CCBS_OCH_ Report_Failure See TS 23.078 Figure 8c: Procedure OG_Call_Setup _MSC (sheet 3) 3GPP .5. False) Wait_For_ ACM 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.078 Leg1_Status :=Set-up CAMEL_OCH_ LEG1_MSC (Leg1_Status) Idle Result= Pass? Yes Release transaction MOBILE_NUMBER_ See TS 23.087 To Subs_FSM Call setup failed Initial Address Destinatio n address:= IAM.066 PORTABILITY_ IN_OQoD UUS_OCH_ Set_Info_ In_IAM See TS 23.

Address Complete Connect See TS 23.018 V7.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.Release 7 36 3GPP TS 23.093 See TS 23.5.078 Wait_For_ Answer 2 Figure 8d: Procedure OG_Call_Setup _MSC (sheet 4) 3GPP .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.093 CCBS_OCH_ Report_Success CCBS_OCH_ Report_Success See TS 23.0 (2007-06) 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.

078 CAMEL_OCH_ LEG2_MSC No CAMEL phase 4 or later contr ol relationship exists? Yes B See TS 23.Release 7 37 3GPP TS 23.078 CAMEL_OCH_ MSC_ANSWER No Result= Pass? Yes Yes Result= Reconnect? No 3 Handle_AoC_ MO_MSC Set_COLP_ Info_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.0 (2007-06) 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 ar e fr om the BSS.018 V7. signals to the right ar e to the process Subs_FSM See TS 23.5.078 CAMEL_OCH_ LEG1_MSC (Leg1_Status) Leg1_Status := Active Wait_For_ Clear Idle Figure 8e: Procedure OG_Call_Setup _MSC (sheet 5) 3GPP .

0 (2007-06) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message ha s been received from the MS Wait_For_ ACM OCS_MSC6(11) Signals to/from the left are to/from the BSS.Release 7 38 3GPP TS 23.093 CCBS_Check_ If_CCBS_ Possible See TS 23.093 CCBS_OCH_ Re port_Fai lu re Store CCBS Re sult CAME L Phase 2 or higher supported ? No Yes No CAME L Phase 2 or higher supported ? Yes Yes No Release cau se= No answer from use r? CAMEL_OCH_ MSC_DISC3 CA MEL_OCH_ MSC_DISC4 CA MEL_OCH_ MSC_DISC3 CA MEL_OCH_ MSC1 4 No Re sult= Re connect? Yes See TS 23. Release transa cti on Release From destin ation exchang e From gsmSSF Int_Release_ Call CCBS_OCH_ Re por t_Fai lu re See TS 23.078 Release transacti on 3 CCBS Re sult CCBS Possible CCBS Not Possible Release transa cti on CCBS_ Activation_ MSC Release See TS 23.5.093 Release Call setu p failed To Subs_FSM Figure 8f: Procedure OG_Call_Setup _MSC (sheet 6) 3GPP . signals to/fro m the right are to/from the destination exchange unless oth er wise marked.093 See TS 23.018 V7.

Figure 8g: Procedure OG_Call_Setup _MSC (sheet 7) 3GPP .087 Re sult= Re connect? Yes See TS 23.018 V7. signals to/fro m the right are to/from the destination exchange unless oth er wise marked.5.087 UUS_MSC_ Ch eck_ UUS1_UUI 3 Release Release transa cti on Release Call setu p failed To Subs_FSM Signals to/from the left are to/from th e BSS.078 Release transacti on UUS_MSC_ Ch eck_ UUS1_UUI No See TS 23.0 (2007-06) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message ha s been received from the MS Wait_Fo r_ Connect_Ack Wait_Fo r_ Answer OCS_MSC7(11) Release transa cti on Release From gsmSSF Int_Release_ Call CAME L Phase 2 or higher supported ? No Yes No CAME L Phase 2 or higher supported ? Yes Yes No Release cau se= No answer fr om user? 4 CAMEL_OCH_ MSC_DISC3 CA MEL_OCH_ MSC_DISC4 CA MEL_OCH_ MSC_DISC3 CA MEL_OCH_ MSC1 See TS 23.Release 7 39 3GPP TS 23.

078 Re lease Re sult? Re connect Release transa cti on Co ntinue. signals to/fro m the right are to/from the destination exchange unless oth er wise marked.018 V7. Fail To Subs_FSM Wait_For_ Answer Call setu p failed 3 Figure 8h: Procedure OG_Call_Setup _MSC (sheet 8) 3GPP .087 4 Release See TS 23.5.0 (2007-06) Procedure OG_Call_Setup_MSC Procedure in the originating VMSC to set up an outgoing call after a Setup message ha s been received from the MS Wait_For_ Answer OCS_MSC8(11) Signals to/from the left are to/from the BSS. Use r to Use r User to User TNRy expired Internal UUS_MSC_ Ch eck_UUS2_ UUI_to_NW See TS 23.Release 7 40 3GPP TS 23.087 UUS_MSC_ Ch eck_UUS2_ UUI_ to_MS CA MEL_OCH_ MS C2 See TS 23.

signals to/from the right are to/from the destination exchange unless otherwise marked.018 V7.Release 7 41 3GPP TS 23.078 CAMEL_OCH_ MSC_DISC2 See TS 23.087 Release transaction CAMEL_OCH_ MSC_DISC1 See TS 23. Wait_For_Clear Release transaction Release from gsmSSF Int_Release_ Call UUS_MSC_ Check_ UUS1_UUI See TS 23.087 UUS_MSC_ Check_ UUS1_UUI See TS 23.078 Result= Reconnect? No Yes Result= CAMEL handling? No Yes Yes Result= CAMEL handling? No Release transaction 3 Release Release Call cleared To Subs_FSM Figure 8i: Procedure OG_Call_Setup _MSC (sheet 9) 3GPP .0 (2007-06) 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.5.

018 V7.083 Wait_For_ Clear Figure 8j: Procedure OG_Call_Setup _MSC (sheet 10) 3GPP .Release 7 42 3GPP TS 23.5.083 Process_ Hold_ Request Hold reject Retrieve reject Process_ Retrieve_ Request See 3G TS 23.0 (2007-06) 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 (2007-06) 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. ECT request MPTY request ECT request MPTY request Wait_For_ Clear Figure 8k: Procedure OG_Call_Setup _MSC (sheet 11) 3GPP .5.Release 7 43 3GPP TS 23.018 V7. signals to the right are to the Subs_FSM process.

018 V7.5.Release 7 44 3GPP TS 23.0 (2007-06) Procedure Obtain_IMSI_MSC Procedure in t he MSC to obtain the IMS I from the MS and re lay it to the VLR Signals to/from the left are to/from the BSS. Signals to/from the right are to/from the VLR OIMSI_M1(1) Send IMSI W ait_For_ IMSI Send IMSI ack Release transaction Send IMSI negative response Re lease transaction Provide IM SI ack A bort Result:= Pass Result:= A borted Figure 9: Procedure Obtain_IMSI_MSC 3GPP .

5. Signals to/from the right are to/from the VLR AUT_MSC1(1) Authenticate W ait_For_ Auth_Response Au thenticate ack Release transaction Auth enticate negative response Authenticate ack A bort Authenticate negat ive respo nse Release transa ction Wait_For_ Auth_Result Result:= Aborted Authentication accepted Authentication reject ed Authentication rejected Result:= Pass Figure 10: Procedure Authenticate_MSC 3GPP .Release 7 45 3GPP TS 23.0 (2007-06) Procedure Au thenticate_MSC Procedure in t he MSC to obtain an authentication response from the MS and re lay it to the VLR Signals to/from the left are to/from the BSS.018 V7.

0 (2007-06) Procedure Obtain_IMEI_MSC Procedure in t he MSC to obtain the IME I from the MS and re lay it to the VLR Signals to/from the left are to/from the BSS.Release 7 46 3GPP TS 23. Signals to/from the right are to/from the VLR OIMEI_M1(1) Send IMEI W ait_For_ IMEI Se nd IMEI ack Release transaction Send IMEI negative response Release transa ction Provide IMEI ack A bort Result:= Pass Result:= A borted Figure 11: Procedure Obtain_IMEI_MSC 3GPP .5.018 V7.

Release 7 47 3GPP TS 23. IMEI available? No Yes Send IMEI W ait_For_ IMEI CM service abort Send IMEI negative response Send I MEI ack Release transaction Ch eck IMEI To EIR Abort Wa it_for_ Check_IMEI_ Resu lt Result:= Aborted Release transaction Check IMEI negative response From EIR Ch eck IMEI ack From EIR Abort Check IMEI negative response Ch eck IMEI ack Result:= Aborted Result:= Pass Figure 12: Procedure Check_IMEI_MSC 3GPP .0 (2007-06) Procedure Check_IMEI_MSC Procedure in t he MSC to check the IMEI and relay the result to t he VLR CIMEI_M1(1) Signals to/from the left are to/from the BSS.5.018 V7. signals to/from the right are to/from the VL R unless ma rked otherwise.

0 (2007-06) Procedure Establish_Originating_TCH_If_Required Procedure in the originating VMSC to e stablish a Traffic Channel if one has not been established for this cal l EOTCIR1(1) Signals to/from the left are to/from the BSS. signals to the right are to the process Subs_FSM TCH_Check Re sult Use existing Allocate Aborted.Release 7 48 3GPP TS 23.5. Fail Re ject Allocate channel Wait_For_ Allocation_ Co mplete Release transa cti on Allocation failure Allocation complete Release transa cti on Re sult:= Pass Re sult:= Fa il Re sult:= Pass Re sult:= Fail Re sult:= Re jected Call setu p failed Call setu p failed Figure 13: Procedure Establish_Originating_TCH_If_Required 3GPP .018 V7.

0 (2007-06) Procedure Set_CLI_Presentation_Indicator_MSC Procedure in t he MSC to determine the CLI presentation indicator value Signals to/from the right are to/fro m the process CLIR_MAF004 CAIND_M1(1) Initiate handling of CLIR W ait_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 .5.Release 7 49 3GPP TS 23.018 V7.

018 V7.087 Result= P ass? Yes No Progress A lerting A lerting sent:= True Result:= Pass Result:= Fail Figure 15: Procedure Send_Alerting_If_Required 3GPP .5.0 (2007-06) Procedure Send_Alerting_If_Required Procedure to send an Alerting message to the MS if one is req uired for this call SALTIR1(1) Sign als to the left are to the B SS True Alerting sent False True A ccess Connect sent False Ye s Backward call indicator= no indication? No See TS 23.087 UUS_MSC_ Check_ UUS1_UUI UUS_OCH_Set_ A lert_And_ Connect_Param See TS 23.Release 7 50 3GPP TS 23.

5.0 (2007-06) Procedure Set_COLP_Info_MSC Procedure in t he MSC to determine the COLP information to be sent to the MS Signals to/from the right are to/fro m the process COLP_MAF006 COINF_M1(1) Initiate handling of COLP W ait_For_ COLP_Info Re lease transaction From BSS Continue call handling Release From destination exchange Figure 16: Procedure Set_COLP_Info_MSC 3GPP .018 V7.Release 7 51 3GPP TS 23.

5.018 V7.Release 7 52 3GPP TS 23.0 (2007-06) Procedure Handle_AoC_MO_MSC Procedure in t he MSC to handle AoC signalling towards the MS for an MO call AoCMO_M1(1) Ye s A oC(I) provisioned? No Set charging parameters No AoC(C) provisioned? Yes S et charging pa ramete rs Acknowledgment required:= False A cknowledgment required: = True Figure 17: Procedure Handle_AoC_MO_MSC 3GPP .

018 V7.Release 7 53 3GPP TS 23. signals to/from the right are to/from the destination exchange True MS conn ected False UUS_O CH_ Set_Alert_An d_ Connect_Param See TS 23.087 Facility Connect No Acknowledgment required? Yes No Acknowledgment req uired? Yes Sta rt AoC acknowledgme nt timer Start AoC acknowledgment timer Wait_For_ Ao C_Ack_F W ait_For_ AoC_Ack_C Charging Parameters ack Release transaction AoC a cknowledgment timer expired Charging Parameters ack Release tra nsaction Connect Ack Ao C acknowledgment timer expired Release transaction Release transaction Release Re lease Result:= Facility sent Resu lt:= Fail Result:= Connect sent Result:= Fail Figure 18: Procedure Send_Access_Connect_If_Required 3GPP .5.0 (2007-06) Procedure Se nd_Access_Connect_If_Required Procedure to send a Connect message to the MS if one is req uired for this call SACONIR1(1) Signals to/from the left are to/from the BSS.

5.Release 7 54 3GPP TS 23. 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 . 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.018 V7.0 (2007-06) Procedure TCH_Check Procedure in originating or terminating VMSC to check if a trafic channel has been established for this call.

it is specified in 3GPP TS 23.1. Sheet 2: the negative response "call barred" indicates whether the reason is operator determined barring or supplementary service barring.2. Sheet 2: it is a network operator decision (subject to MoU requirements) whether a GSM connection should be ciphered. Sheet 1: the procedure Check_OG_Multicall_VLR is specific to Multicall.2.2.Release 7 55 3GPP TS 23. sheet 4. If the VLR does not support CAMEL.2. If the VLR does not support CUG. processing continues from connector 1 to the call to the procedure Check_OG_Barring. the procedure call is omitted.2.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.093 [23]. Sheet 1: it is a network operator decision (subject to MoU requirements) how often an MS should be authenticated.1.5 7. Sheet 3.4 Procedure Obtain_Identity_VLR It is a network operator decision whether open (non ciphered) identification of the MS by its IMSI is allowed.2 Functional requirements of VLR 7.087 [20]. Sheet 1: the procedure OG_CUG_Check is specific to CUG.1 7.5. Sheet 5: it is a network operator decision whether emergency calls are allowed from an ME with no SIM.1. A UMTS connection shall always be ciphered.1. sheet 5: the procedure CCBS_Report_MS_Activity is specific to CCBS.2.0 (2007-06) 7.078 [12]. it is specified in 3GPP TS 23. Sheet 1: the procedure UUS_OCH_Check_Provision is specific to UUS.1. If the VLR supports neither CLIR nor COLP.018 V7. Sheet 2: the procedure CAMEL_OCH_VLR is specific to CAMEL.135 [25]. If the VMSC does not support Multicall. Sheet 1: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC. it is specified in 3GPP TS 23. according to the result returned by the procedure Check_OG_Barring. processing continues from the "Yes" exit of the test "Result=Pass?". 7. processing continues from the "Yes" exit of the test "Result=Call allowed?". 7. Sheet 2: the process Subscriber_Present_VLR is described in 3GPP TS 29.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.002 [29]. it is specified in 3GPP TS 23. Sheet 3: it is a network operator decision (subject to MoU requirements) how often an IMEI should be checked. 3GPP .1. processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 1: the procedure Get_LI_Subscription_Info_MO_VLR is specific to CLIR and COLP. 7.1. If the VMSC does not support UUS.3 Procedure OG_Call_Subscription_Check_VLR Sheet 1: it is an implementation option to carry out the check for operator determined barring of all outgoing calls before the check on provisioning of the requested basic service.

1.1.1. the message is saved for handling after return from the procedure. 7.2.2. it omits the signal interchange with the process CLIR_MAF003. 7.2.2. 7.012 [6].2.1.1. the message is saved for handling after return from the procedure. then service is granted. but the network operator may decide to initiate tracing.1.5.2.8 7.15 Procedure Get_AoC_Subscription_Info_VLR The indicator of whether or not AoC is provisioned is global data which can be read by the parent process. 7.2.2. whitelisted.17 Process Update_Location_VLR The procedure Update_HLR_VLR is described in 3GPP TS 23.0 (2007-06) 7.10 7. 7. the message is saved for handling after return from the procedure.018 V7.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. then service is granted. it omits the signal interchange with the process COLP_MAF005.1. If the VLR does not support COLP.7 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. then service is not granted.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.1.1. greylisted. 3GPP . the message is saved for handling after return from the procedure.2.1.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.1.16 Procedure Check_OG_Barring Sheet 3: if the VLR receives an Abort message from the MSC while it is awaiting a response from the process MAF018 or MAF019.14 Procedure Get_LI_Subscription_Info_MO_VLR If the VLR does not support CLIR.Release 7 56 3GPP TS 23. 7.2.11 7.

1: Process OCH_VLR 3GPP . Idle OCH_VLR1(1) P rocess A ccess Request P rocess_ A ccess_ Request_VLR Result= Pass Yes No W ait_For_ S IFOC Idle S end Info For Outgoing Call Abort Yes E mergency call? No Idle Complete Call OG_Call_ S ubscription_ Check_VLR Idle Idle Figure 7.018 V7.1.2.5.Release 7 57 3GPP TS 23.0 (2007-06) Process OCH_VLR Process in the VLR to handle an outgo ing (MO) call setup request Signals to/from the left are to/fro m the MSC.

5.2a: Procedure Process_Access_Request_VLR (sheet 1) 3GPP .Release 7 58 3GPP TS 23.018 V7.2.0 (2007-06) 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.1.

0 (2007-06) 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.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.5.2.1.2b: Procedure Process_Access_Request_VLR (sheet 2) 3GPP .018 V7.Release 7 59 3GPP TS 23.

4 5 PAR_VLR3(5) Sta rt security procedures Identity:= IMSI Process Access Request ack No IME I 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.0 (2007-06) Procedure Process_Access_Request_VLR Procedure in t he VLR to handle a request from the MS for system access Signals to the lef t are to the M SC.093 No Forward New TMSI Use E xisting TMSI IMSI detached := True Freeze existing TMSI Result:= Pass Set negative respon se: Illegal Equipment Result:= Aborted Wait_For_ TMSI_Ack 3 Figure 7.2c: Procedure Process_Access_Request_VLR (sheet 3) 3GPP .018 V7.2.5.1.Release 7 60 3GPP TS 23.

018 V7.1.0 (2007-06) Procedure Process_Access_Request_VLR Procedure in t he VLR to handle a request from the MS for system access Signals from the left are from the MSC.2d: Procedure Process_Access_Request_VLR (sheet 4) 3GPP .Release 7 61 3GPP TS 23.2.5.093 Result= Unidentified Subscriber? No Yes Result:= Pass Set negative response: Unide ntified S ubscriber Set negative response: I llegal S ubscriber 3 Figure 7. PAR_VLR4(5) 2 W ait_For_ TMSI_Ack Result= Aborted? No Yes Forward New TMSI ack Forward New TMSI negative response Resu lt:= A borted Yes Result= Procedure Error? No Result= Unknown Subscriber? No Yes Set negative response: System Failure Unfreeze existing TMSI CCBS _Report_ MS_Activity See TS 23.

5.0 (2007-06) Procedure Process_Access_Request_VLR Procedure in t he VLR to handle a request from the MS for system access Signals to the lef t are to the M SC.018 V7.Release 7 62 3GPP TS 23.2. 3 PAR_VLR5(5) CM service type =Emerge ncy call? Yes No Emerg ency call setup allowed without S IM? No No Yes IMEI required? Yes O btain_ IMEI_VLR Result= P ass? Yes No Identity:= IMEI Result= Fail? No Yes P rocess A ccess Request ack Pro cess Access Re quest negative response See TS 23.2e: Procedure Process_Access_Request_VLR (sheet 5) 3GPP .1.093 CCBS_Report_ MS_Activity Result:= Pass Result: = Aborted Result:= Fail Figure 7.

Release 7 63 3GPP TS 23.3a: Procedure OG_Call_Subscription_Check_VLR (sheet 1) 3GPP .018 V7.5.0 (2007-06) Procedure OG_Call_Subscription_Check_VLR Procedure in t he VLR to perf orm subscriptio n checks for an outgoing call Signals to the lef t are to the MSC OCSCVLR1(2) No Basic service provisioned? Yes See TS 23.2.1.135 Check_OG_ Multicall_VLR Set negative re sponse: Basic service not provisioned No Bearer service or telese rvice Result= P ass? Yes Check_ B AO C Result= Call barred? No OG_CUG_ Check Yes Set negative re sponse: Call barred No Result= Call allowed? Yes Get_LI_ S ubscription_ Info_MO_VLR G et_AoC_ S ubscription_ Info_VLR UUS_OCH_ Check_ Provision Set negative re sponse: CUG reject Result= P ass? Yes No Send In fo For Outgo ing Call negative response 1 Figure 7.

3b: Procedure OG_Call_Subscription_Check _VLR (sheet 2) 3GPP .0 (2007-06) Procedure OG_Call_Subscription_Check_VLR Procedure in t he VLR to perf orm subscriptio n checks for an outgoing call OCSCVLR2(2) Signals to the left are to the MS C 1 CAMEL_ OCH_VLR See TS 23.018 V7.Release 7 64 3GPP TS 23.2.1.5.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 (2007-06) Procedure Obtain_Identity_VLR Procedure in t he VLR to obtain the identity of an MS OID_VLR1(1) Yes Identity= IMSI? No Identification allowed? No Yes O btain_ IMSI_VLR Result= P ass? Yes No No IMSI known? Yes Result:= Fail Result:= Pass Result:= Abort ed Figure 7.4: Procedure Obtain_Identity_VLR 3GPP .018 V7.5.1.2.Release 7 65 3GPP TS 23.

0 (2007-06) Procedure Obtain_IMSI_VLR Process in the VLR to obtain the IMS I from the MS via the MSC Signals to/from the left are to/fro m the MSC. OIMSI_V1(1) P rovide IMSI W ait_For_ IMSI Provide IMSI ack Abort Result:= Pass Result:= Aborted Figure 7.5.1.5: Procedure Obtain_IMSI_VLR 3GPP .Release 7 66 3GPP TS 23.018 V7.2.

AUT_VLR1(2) Auth entication sets available? No Yes O btain_ A uthentication_ S ets_VLR No Result= P ass? Yes 2 Yes Result= Aborted? No Authenticate Result:= Aborted Yes Result= Procedure Error? No W ait_For_ Authenticate_ Result Result:= Procedure Error Result:= Unknown Subscriber Authenticate ack Authenticate negative re sponse Authentication failure re port More auth entication sets needed? Abort Received SRES= expected SRES? Yes Mo re authentication sets needed? Yes Fetch_ A uthenticat ion_ S ets_VLR No No No Yes Fetch_ Authentication_ Sets_VLR Authentication accepted Result:= Pass Result:= Aborted 1 Figure 7.6a: Procedure Authenticate_VLR (sheet 1) 3GPP .1.5.2.Release 7 67 3GPP TS 23.0 (2007-06) Procedure Authenticate_VLR Procedure in t he VLR to authenticate an MS via the MS C Signals to/from the left are to/fro m the MSC.018 V7.

5.Release 7 68 3GPP TS 23.2. Identity=IMSI? No 1 AUT_VLR2(2) Yes Retry with IMSI? Yes No O btain_ IMSI_VLR No Result= P ass? Yes No IMSI known? Yes IMSI matches TMS I? No Authentica tion accepted Yes Authentication rejected Authentication failure report Result:= Aborted Result:= Unidentified Sub scriber Identity:= IMSI Result:= Illega l Subscriber 2 Figure 7.018 V7.6b: Procedure Authenticate_VLR (sheet 2) 3GPP .1.0 (2007-06) Procedure Authenticate_VLR Procedure in t he VLR to authenticate an MS via the MS C Signals to the lef t are to the M SC.

2.7a: Procedure Obtain_Authentication_Sets_VLR (sheet 1) 3GPP .1.0 (2007-06) Procedure Obtain_Authentication_Sets_VLR Procedure in t he VLR to obtain authentication sets from the HLR Signals to/from the right are to/from the HLR OAS_ VLR1(2) Send Authentication Info W ait_For_ A uthenticat ion_ S ets Send Authentication Info ack Send Authentication Info negative respo nse Empty result? No Yes No Unknown Subscriber? Yes Authentication sets available in VLR? Yes No Yes Re-use o ld sets? No Result:= Pass Result:= Procedure Error Result:= Unknown Subscriber Figure 7.5.Release 7 69 3GPP TS 23.018 V7.

Release 7 70 3GPP TS 23.018 V7.7b: Procedure Obtain_Authentication_Sets_VLR (sheet 2) 3GPP .2.0 (2007-06) Procedure Obtain_Authentication_Sets_VLR Procedure in t he VLR to obtain authentication sets from the HLR OAS_ VLR2(2) Signals to/from the left are to/fro m the MSC.1. Signals to/from the right are to/from the HLR W ait_For_ A uthentication_ S ets Abort Abort Abort Authentication sets available? Yes No Yes Re-use old se ts? No Result:= Aborted Result:= Pass Result:= Procedure Error Figure 7.5.

0 (2007-06) Procedure Start_Tracing_VLR Procedure in t he VLR to requ est the MSC to start activity tracing Signals to the lef t are to the M SC.8: Procedure Start_Tracing_VLR 3GPP .1.2.018 V7.5. ST_TR_V1(1) Tracing active? Yes No Trace S ubscriber Act ivity Figure 7.Release 7 71 3GPP TS 23.

9: Procedure Check_IMEI_VLR 3GPP .5.1.0 (2007-06) Procedure Check_IMEI_VLR Procedure in t he VLR to requ est the MSC to check an IMEI Signals to/from the left are to/fro m the MS C CIMEI_V1(1) Check IMEI W ait_For_ Check_IMEI_ Result Abort Check IMEI negat ive response Check IMEI ack No Service gran ted? Yes Result:= Aborted Result:= Fail Result:= Pass Figure 7.Release 7 72 3GPP TS 23.018 V7.2.

Release 7 73 3GPP TS 23.5.1.0 (2007-06) 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 l eft are to/fromthe MSC Provide IMEI Wait_For_ IMEI Provide IMEI ack Abort Store IMEISV Result:= Pass Result:= Aborted Figure 7.10: Procedure Obtain_IMEI _VLR 3GPP .2.018 V7.

2.1.5.Release 7 74 3GPP TS 23.0 (2007-06) Process Fetch_Au thentication_Sets_VLR Process in the VLR to retrieve authentica tion sets from the HLR FAS_VLR1(1) Obiain_ A uthentication_ S ets_VLR Figure 7.018 V7.11: Process Fetch_Authentication_Sets_VLR 3GPP .

Release 7 75 3GPP TS 23.0 (2007-06) Procedure Check_BAOC Procedure to check call request against ODBAOC and SS BAOC Signals to/from the right are to/fro m the process MAF017 CBAOC1(1) Ye s O perator determined BAOC imposed? No Result:= Call barred (ODB) Initiate handling of BAO C W ait_For_ B AOC_ Response From MS C Abort Continue call handling Ye s Call ba rred? No Result:= Call barred (SS barring ) Result:= Call allowed Figure 7.5.018 V7.12: Procedure Check_BAOC 3GPP .1.2.

5.13: Procedure OG_CUG_Check 3GPP .Release 7 76 3GPP TS 23.018 V7.2.0 (2007-06) Procedure OG_CUG_Check Procedure to carry out CUG authorisation check for an outgoing (MO) call Signals to/from the right are to/fro m the process CUG_MAF014 OG_CUG1(1) outgoing call requ est W ait_For_ CUG_Re sponse From MS C Abort response to call request complete call (conditional CUG info) reject call (cause) Result := Call allowed Result:= Ca ll barred Figure 7.1.

14: Procedure Get_LI_Subscription_Info_MO_VLR 3GPP .2.1.Release 7 77 3GPP TS 23.018 V7.0 (2007-06) Procedure Get_LI_Subscription_Info_MO_VLR Procedure in t he 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 W ait_For_ CLIR_Info From MS C Abort Continue call handling From process CLIR_MAF003 Initiate handling of COLP To process COLP_MAF005 W ait_For_ COLP_Info From MS C Abort Continue call handling From process COLP_MAF005 Figure 7.5.

0 (2007-06) Procedure Get_AoC_Subscription_Info_VLR Procedure in t he VLR to determine the subscription to Advice of Charge services GAOCI_V1(1) A oC(I) provisioned? No Yes No AoC(C) provisioned? Yes Set indicator: AoC not provisioned S et indicator: A oC(C) provisioned Set indicator: AoC(I) provisioned Figure 7.15: Procedure Get_AoC_Subscription_Info_VLR 3GPP .018 V7.1.2.5.Release 7 78 3GPP TS 23.

0 (2007-06) Procedure Check_OG_Barring Procedure to check call request against SS barring and ODB categories COB1(3) Yes Operator determined BOIC imposed? No No Destina tion address CC= Local CC? Yes 1 Yes Operator determined BOIC-exHC imposed? No Yes Destina tion address CC= Local CC? No 1 No Destina tion address CC= HPLMN CC? Yes 1 Yes Operator determined BOIZC imposed? No No Dest ination address ZC= Local ZC? Yes 1 Yes Operator determined BOIZC-exHC imposed? No Yes Dest ination address ZC= Local ZC? No 1 No Destina tion address CC= HPLMN CC? Yes Result:= Call barred (ODB) 1 Figure 7.1.16a: Procedure Check_OG_Barring (sheet 1) 3GPP .5.Release 7 79 3GPP TS 23.2.018 V7.

Release 7 80 3GPP TS 23.018 V7.2.0 (2007-06) Procedure Check_OG_Barring Procedure to check call request against SS barring and ODB categories 1 COB2(3) No Yes 2 Yes Operato r determined BO IC-exHC&BOIZC imposed? Destination address ZC= Local ZC? No Yes Destination address CC= Local CC? No 2 No Destination address CC= HPLMN CC? Yes Result:= Call barred (O DB) 2 Figure 7.5.1.16b: Procedure Check_OG_Barring (sheet 2) 3GPP .

5.018 V7.1.16c: Procedure Check_OG_Barring (sheet 3) 3GPP .0 (2007-06) 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 W ait_Fo r_ B OIC_ Response From MSC Abo rt Continue call handling From process MAF018 Yes Call barred? No Initiate handling of BOIC-exHC To process MAF020 W ait_Fo r_ B OIC-exHC_ Response From MSC Abo rt Continue call handling From process MAF020 Yes Call barred? No Result:= Ca ll barred (SS barring) Result:= Call allowed Figure 7.2.Release 7 81 3GPP TS 23.

012 Figure 7.5.1.0 (2007-06) 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 V7.2.17: Process Update_Location_VLR 3GPP .Release 7 82 3GPP TS 23.

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

Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. processing continues from the "Pass" exit of the test "Result". sheet 3: the procedure CAMEL_MT_GMSC_ANSWER is specific to CAMEL. depending on national regulations. If the GMSC does not support CAMEL. Sheet 3: the procedure Handle_COLP_Forwarding_Interaction is specific to COLP. sheet 3: the task "Set destination address parameter" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. it shall include the called party's status field of the Backward call indicator set to "no indication". If the GMSC does not support CAMEL phase 4 or later. it is specified in 3GPP TS 23.Release 7 84 3GPP TS 23.078 [12]. 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. 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". it is specified in 3GPP TS 23. Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop_TNRy are specific to CAMEL phase 2 or later. Sheet 2. Sheet 2. North American GSM Number Portability (NAGNP) requires the SRI negative response "unknown subscriber" to be treated differently under certain conditions. unspecified 57 Bearer capability not authorized 111 Protocol error. according to National Coding Standard. Sheet 2.5. sheet 3: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later. to indicate "Misrouted call to a ported number".078 [12]. If the GMSC sends an Address Complete message. unspecified 69 Requested facility not implemented 21 Call rejected 22 Number changed 111 Protocol error. processing continues from the "Pass" exit of the test "Result?". it shall include the called party's status field of the Backward call indicator set to "no indication". under all other conditions the SRI negative response "unknown subscriber" shall be mapped to ISUP release cause number 1 "Unallocated (unassigned) number". they are specified in 3GPP TS 23. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.078 [12]. sheet 8: the process CAMEL_MT_LEG1_GMSC is specific to CAMEL phase 4 or later. Sheet 1: it is an operator option whether to send an Address Complete message if the HLR returns forwarding information. unspecified 1 Unallocated (unassigned) number 26 Misrouted call to a ported number (note) If the Diagnostic parameter indicates "NPDB mismatch".078 [12]. If the GMSC sends an Address Complete message. 3GPP .0 (2007-06) Table 1: Suggested mapping of Send Routeing Info (SRI) negative responses to ISUP release causes SRI negative response Absent subscriber Bearer service not provisioned Call barred (ODB) Call barred (SS barring) CUG reject (Called party SS interaction violation) CUG reject (Incoming calls barred within CUG) CUG reject (Subscriber not member of CUG) CUG reject (Requested basic service violates CUG constraints) Data missing Facility not supported Forwarding violation Number changed System failure Teleservice not provisioned Unexpected data value Unknown subscriber NOTE: ISUP release cause number 20 57 21 21 21 55 87 87 ISUP release cause name Subscriber absent Bearer capability not authorized 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 1: it is an operator option whether to send an Address Complete message if the Number Portability Database returns a routeing number. Sheet 1.078 [12].018 V7.

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

Release 7

86

3GPP TS 23.018 V7.5.0 (2007-06)

Sheet 2: the procedure MOBILE_NUMBER_PORTABILITY_IN_QoHR is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. Sheet 3: the procedure SCUDIF_Check_Service_Availability is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. If the GMSC does not support SCUDIF, processing continues from the "continue" exit of the test "Result ?". Sheet 3: the procedure CAMEL_MT_GMSC_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. Sheet 3: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. Sheet 3: sending of "Release Resources" is an implementation option. If support of "Release Resources" by the VMSC is not indicated in Send Routing Info ack, "Release Resources" shall not be sent. Sheet 4: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. Sheet 4: the procedure CCBS_MT_GMSC_Check_CCBS_Indicators is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. Sheet 4: the task "Store Forwarding Interrogation Required indicator" is executed only if the GMSC supports Optimal Routeing. Sheet 4: The test "MSRN contains a Routeing Number" is executed only if the SRF solution for call related MNP is used. If the SRF solution for call related MNP is not used, processing continues from the "No" exit of the test "MSRN contains a Routeing Number". Sheet 4: the procedure MNP_MT_GMSC_Check_MNP_Indicators is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. Sheet 5: the procedure CAMEL_MT_GMSC_Notify_CF is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 2 or later, processing continues from the "Continue" exit of the test "Result". Sheet 5: the procedure SCUDIF_Check_Service_Compatibility is specific to SCUDIF; it is specified in 3GPP TS 23.172 [38]. Sheet 6: the task "BOR:=OR" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls. Sheet 6: the procedures CCBS_MT_GMSC_Remove_Indicators_Store_FWT is specific to CCBS; it is specified in 3GPP TS 23.093 [23]. Sheet 6: the procedure Route_Permitted is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23.079 [13]. If the GMSC does not support Optimal Routeing, processing continues from the "True" exit of the test "Route permitted". Sheet 6: the procedure CAMEL_MT_MSC_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12]. Sheet 6: the procedure CAMEL_MT_GMSC_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12]. Sheet 6: the task "OR:= True" is executed only if the GMSC supports Optimal Routeing of mobile-to-mobile calls.

7.2.1.3

Procedure Send_ACM_If_Required

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

7.2.1.4

Procedure Send_Answer_If_Required

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

3GPP

Release 7

87

3GPP TS 23.018 V7.5.0 (2007-06)

7.2.1.5

Procedure Send_Network_Connect_If_Required

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

7.2.1.6

Procedure Handle_COLP_Forwarding_Interaction_MSC

The originating exchange or the destination exchange may release the call while a response is awaited from the process COLP_MAF039. The message is saved for processing after return from the procedure.

7.2.1.7

Procedure Activate_CF_Process

The processing in the branch beginning with the Int_Release_Call input will occur only if the MSC supports CAMEL.

7.2.1.8

Process MT_CF_MSC

Sheet 1: the procedure CAMEL_CF_MSC_INIT is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 1, sheet 4: the procedure CAMEL_CF_Dialled_Services is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 3 or later, processing continues from the "Pass" exit of the test "Result?". Sheet 1, sheet 3, sheet 4: the procedure CAMEL_OCH_MSC1 is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL phase 2 or later, processing continues from the "Yes" exit of the test "Result=Reconnect?". Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability; it is specified in 3GPP TS 23.066 [10]. Sheet 1: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later; it is specified in 3GPP TS 23.078 [12]. Sheet 1, sheet 3: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1; it is specified in 3GPP TS 23.078 [12]. Sheet 1, sheet 3: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later; it is specified in 3GPP TS 23.078 [12]. Sheet 1, sheet 6: the procedure CAMEL_MT_CF_LEG1_MSC is specific to CAMEL phase 4 or later; it is specified in 3GPP TS 23.078 [12]. Sheet 2: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later; they are specified in 3GPP TS 23.078 [12]. Sheet 2: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL; it is specified in 3GPP TS 23.078 [12]. If the MSC does not support CAMEL, processing continues from the "Pass" exit of the test "Result?". Sheet 2: the procedure UUS_MSC_Clear_UUS is specific to UUS; it is specified in 3GPP TS 23.087 [20]. Sheet 2: the procedure CAMEL_CF_MSC_ALERTING is specific to CAMEL phase 4 or later; it is specifed in 3GPP TS 23.078 [12]. If the GMSC does not support CAMEL phase 4 or later, processing continues from the "Pass" exit of the test "Result?". Sheet 3: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later; it is specified in 3GPP TS 23.078 [12]. Sheet 3: the processing in the branch beginning with the Int_O_Release input will occur only if the MSC supports CAMEL. Sheet 4: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later, and will occur only if the GMSC supports CAMEL phase 2 or later. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23.078 [12].

3GPP

Release 7

88

3GPP TS 23.018 V7.5.0 (2007-06)

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

3GPP

Release 7

89

3GPP TS 23.018 V7.5.0 (2007-06)

7.2.1.9

Macro CUG_Support_Check_GMSC
MT_GMSC1(9)
Signals to/from the left are to/from the originating exchange; 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.066

MNP_MT_GMSC_ Set_M NP_ Parameters

OR_Set_ORA_ Parameters

See TS 23.079

CAMEL_Set_ ORA_Parameters

See TS 23.078

4

Figure 36a: Process MT_GMSC (sheet 1)

3GPP

Release 7

90

3GPP TS 23.018 V7.5.0 (2007-06)

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; signals to/from the right are to/from the destination MSC unless marked otherwise

Obtain_Routeing_Address (Called party address, Reference address, OR, Own PLMN, Routeing address, Destination address, Result)

Result? Fail Aborted Pass Routeing Number Forward

Leg1_only Leg1_status := Set-up

Set cause

See TS 23.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.078

CAMEL_Store_ Destination_ Address (OR, False)

CAMEL_Store_ Destination_ Address (OR, False)

See TS 23.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

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 .5.018 V7.0 (2007-06) 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.Release 7 91 3GPP TS 23.078 CAMEL_MT_ MSC_ALERTING Answer Result? Pass Wait_For_ Answer Else Answer See TS 23.078 CAMEL_MT_ GMSC_ANSWER CAMEL_MT_ GMSC_ANSWER See TS 23.078 CAMEL_ Start_TNRy See TS 23.

Release 7

92

3GPP TS 23.018 V7.5.0 (2007-06)

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

CAMEL_MT_ MSC_ALERTING

Answer

Result? Pass Wait_For_ Forward_ Answer

Else

Answer

See TS 23.078

CAMEL_MT_ GMSC_ANSWER

CAMEL_MT_ GMSC_ANSWER

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

Release 7

93

3GPP TS 23.018 V7.5.0 (2007-06)

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.093 Check_CCBS_ Possible Resume call:True Wait_For_ACM, Wait_For_Answer

MT_GMSC5(9)
Signals to/from the right are to/from the destination MSC unless marked otherwise

Refer to TS 23.079 for message contents

Release

CAMEL_ MT_GMSC_ DISC6 Clear MT Roaming Retry IE := true

CAMEL_ Stop_TNRy

see TS 23.078

OR_Handle_ RCH Yes

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

Release 7

94

3GPP TS 23.018 V7.5.0 (2007-06)

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; 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.078

Release Result?

Reconnect

Continue, Fail

Release

Release call resources

Idle

1

Figure 36f: Process MT_GMSC (sheet 6)

3GPP

Release 7

95

3GPP TS 23.018 V7.5.0 (2007-06)

Process MT_GMSC
Process in the GMSC to handle a mobile-terminated call request Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer, Wait_For_Forward_Answer

MT_GMSC7(9)
Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the destination exchange or process MT_CF_M SC unless marked otherwise

Release

Release

From gsmSSF

Int_Release_ Call

CCBS_MT_GM SC_ 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.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

Release 7

96

3GPP TS 23.018 V7.5.0 (2007-06)

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; 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.078

CAMEL_MT_ GMSC_DISC2

See TS 23.078

Result= CAMEL handling? No

Yes

Reconnect Result?

CAMEL handling Release

Norm handling al

Release

1

Release

Release

Release call resources

Wait_For_ Clear

Idle

Resum e Call Handling

Wait_For_ACM, Wait_For_Forward_ACM, Wait_For_Answer, Wait_For_Forward_Answer, Wait_For_Clear

Set negative response: OR not allowed

*

*

Resum Call e Handling negative response

-

-

Wait_For_ Clear

-

Figure 36h: Process MT_GMSC (sheet 8)

3GPP

5.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 .Release 7 97 3GPP TS 23.0 (2007-06) 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.018 V7.

Result See TS 23. OR.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 . Own PLMN IN/OUT Routeing address.093 CCBS_MT_ GMSC_Check_ CCBS_Call Reconnect False True Routeing address:= routeing number Result:= Routeing number See TS 23. Destination address.Release 7 98 3GPP TS 23.066 MOBILE_NUMBER_ PORTABILITY_ IN_TQoD Result= Number ported? No Yes See TS 23. Reference address.0 (2007-06) 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.5.018 V7.

signals to/from the right are to/from the HLR ORA2(6) Release Send Routeing Info negative response Set: Call Released Yes Call Released? No Wait_for_ Routeing_ Info Result:= Aborted SCUDIF_negative_ SRI_response_ handling See TS 23.066 No Result= Number ported? Yes Routeing address:= routeing number Result:=Fail Result:= Routeing number Figure 37b: Procedure Obtain_Routeing_Address (sheet 2) 3GPP .018 V7.079 Result= Pass? Yes No No Result:=Pass Error= Unknown subscriber? Yes MOBILE_NUMBER_ PORTABILITY_ IN_QoHR Wait_for_ Routeing_ Info See TS 23.Release 7 99 3GPP TS 23.172 Result Fail Pass Retry Send Routeing Info 4 OR_Handle_SRI_ Negative_Response (Own PLMN) See TS 23.5.0 (2007-06) Procedure Obtain_Routeing_Address Procedure in a GMSC to determine the address to which a call should be routed Wait_for_ Routeing_ Info Signals to/from the left are to/from the originating exchange.

5.Release 7 100 3GPP TS 23.018 V7.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.0 (2007-06) 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.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 .

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.5.Release 7 101 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 .172 CCBS_MT_ GMSC_Check_ CCBS_ Indicators See TS 23.018 V7.0 (2007-06) 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.

018 V7.0 (2007-06) 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.172 Reconnect := True Result:= Fail 2 1 Figure 37e: Procedure Obtain_Routeing_Address (sheet 5) 3GPP .Release 7 102 3GPP TS 23.5.078 Fail Result Continue Reconnect SCUDIF_Check_ Service_Compatibility See TS 23.

079 CAMEL phase 2 or higher supported? No Yes CAMEL_MT_ GMSC_DISC4 See TS 23.093 Result:= Aborted Route_Permitted (OR.0 (2007-06) 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.5.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 .078 See TS 23. Reference Address) False Route permitted True See TS 23.Release 7 103 3GPP TS 23.FTN.018 V7.

018 V7.5.Release 7 104 3GPP TS 23.0 (2007-06) Procedure Send_ACM_If_Required Procedure to send an Address Complete M essage to the preceding exchan ge if one is required for this call SACMIR1(1) Sig nals to the left are to the originating exchange True ACM sent False True Network conn ect sent False Call Progress A ddress Complete A CM sent:= True Figure 38: Procedure Send_ACM_If_Required 3GPP .

0 (2007-06) Procedure Send_Answer_If_Required Procedure to send an Answer M essage to the preceding exchan ge if one is required for this call SANMIR1(1) Sig nals to the left are to the originating exchange True A nswer sent False True Network connect sent False Call Progress Answer Answer sent:= True Figure 39: Procedure Send_Answer_If_Required 3GPP .5.Release 7 105 3GPP TS 23.018 V7.

0 (2007-06) Procedure Send_Network_Connect_If_Required Procedure to send a Connect Message to the preceding exchan ge if one is required for this call SNCONIR1(1) Sig nals to the left are to the originating exchange True Network conne ct sent False True A nswer sent False True ACM sent False Call Progress Answer Connect An swer sent:= True Connect sent:= True Figure 40: Procedure Send_Network_Connect_If_Required 3GPP .5.Release 7 106 3GPP TS 23.018 V7.

0 (2007-06) Procedure Handle_COLP_Forwarding_Interaction_MSC Procedure in t he GMSC or VMSC to handle the intera ction between COLP and Ca ll Forwarding COINT_M1(1) Signals to/from the right are to/fro m the process COLP_MAF039 Initiate handling of COLP W ait_For_ COLP_Info Re lease From originating exchan ge or destination exchange continue call handling Figure 41: Procedure Handle_COLP_Forwarding_Interaction_MSC 3GPP .018 V7.5.Release 7 107 3GPP TS 23.

0 (2007-06) 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.018 V7. 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 .Release 7 108 3GPP TS 23.5. signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Perform call forwarding (BOR.

078 No Leg1_status := Set-up CAMEL_MT_CF _LEG1_MSC (Leg1_status ) Idle 4 See TS 23.078 See TS 23.0 (2007-06) 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. True) Wait_For_ ACM CAMEL phase 2 or higher supported? No CAMEL_OCH_ MSC_DISC3 See TS 23. signals to/from the right are to/from the destination exchange Perform c all forwarding CAMEL_CF_ MSC_INIT 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.018 V7.078 Idle Idle Figure 43a: Process MT_CF_MSC (sheet 1) 3GPP .078 Result? Leg1_only Abort Pass Perform c all forwarding See TS 23.078 Yes CAMEL_OCH_ MSC_DISC4 See TS 23.066 MOBILE_NUMBER_ PORTABILITY_ IN_OQoD Initial Address CAMEL_Store_ Destination_ Address (BOR.5.078 4 Yes Result = Leg1_only? No Result= Pass? Yes CAMEL_CF_ Dialled_Services Fail See TS 23.Release 7 109 3GPP TS 23.

087 See TS 23.Release 7 110 3GPP TS 23.018 V7.078 CAMEL_CF_ MSC_ANSWER CAMEL_CF_ MSC_ANSWER See TS 23.078 CAMEL_ Stop_TNRy See TS 23.078 CAMEL_ Start_TNRy See TS 23.087 UUS_MSC_ Clear_UUS UUS_MSC_ Clear_UUS See TS 23.0 (2007-06) Process MT_CF_MSC Process in the M SC to handle call forwarding Wait_For_ ACM MTCFMSC2(6) Signals to/from the left are to/from the parent process.078 Result? Pass Else Else Result? Pass See TS 23. signals to/from the right are to/from the destination exchange Address Complete Connect See TS 23.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 .5.078 CAMEL_CF_ MSC_ALERTING Answer Result? Pass Else Address Complete Address Complete Wait_For_ Answer Answer See TS 23.

Release 7 111 3GPP TS 23.018 V7.5. 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.0 (2007-06) Process MT_CF_MSC Process in the M SC to handle call forwarding Wait_For_ACM.078 No Result= Reconnect? Yes CAMEL_ Stop_TNRy See TS 23. Wait_For_Answer MTCFMSC3(6) Signals to/from the left are to/from the parent process.078 Release Release Release 2 Release Release call resources Idle Figure 43c: Process MT_CF_MSC (sheet 3) 3GPP .

078 2 Release Result? Fail Reconnect Release See TS 23.078 CAMEL_CF_ Dialled_ Services Abort Result? Fail Pass Release call resources See TS 23. 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.Release 7 112 3GPP TS 23.5.0 (2007-06) Process MT_CF_MSC Process in the M SC to handle call forwarding Wait_For _ Answer MTCFMSC4(6) Signals to/from the left are to/from the parent process.078 CAMEL_ OCH_M SC1 1 Yes Idle Result= Reconnect? No Perform Call Forwarding negative response 2 Idle Figure 43d: Process MT_CF_MSC (sheet 4) 3GPP .018 V7.

Release 7 113 3GPP TS 23.018 V7.5. 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.0 (2007-06) Process MT_CF_MSC Process in the M SC to handle call forwarding Wait_For_ Clear MTCFMSC5(6) Signals to/from the left are to/from the parent process.078 CAMEL_OCH_ MSC_DISC2 See TS 23.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 .

078 No CAMEL_MT_ CF_LEG2_MSC Leg1_status := Active Wait_For_ Clear See TS 23.078 CAMEL_MT_ CF_LEG1_MSC (Leg1_status) Idle Figure 43f: Process MT_CF_MSC (sheet 6) 3GPP .018 V7.0 (2007-06) 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.Release 7 114 3GPP TS 23.5.

5. CUG_SC1(1) No CUG info present? Yes GMSC supports CUG? Yes No Outgoing Access present? No Yes Pass Fail Figure 43bis: Macro CUG_Support_Check_GMSC 7. if needed.Release 7 115 3GPP 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 .1 Process SRI_HLR Sheet 1: the procedures Check_Parameters.018 V7.2 Functional requirements of HLR 7.2. and check if call can continue. SCUDIF_Subscription_Check_HLR.2.2.0 (2007-06) Macrodefinition CUG_Support_Check_GMSC Macro to check support of CUG in GMSC.

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

018 V7. It is an implementation option to carry out the check for operator determined barring of incoming calls before the check on provisioning of the requested basic service. the procedure sets the negative response to "Unexpected data value". then the HLR shall apply basic service TS11. 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. If the HLR does not support SCUDIF. 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. The test "gsmSCF Initiated Call?" is specific to CAMEL phase 4 or later. This negative response parameter is global data. processing continues from the "Yes" exit of the test "Result = Continue ?".172 [38].1) shall delay the sending of the PRN message till completion of any on-going Location Update procedure. it applies the corresponding PLMN bearer service or teleservice for handling the call. If the HLR does not support CAMEL phase 4 or later. the procedure sets the negative response to "Data missing". Sheet 7: the procedure SCUDIF_Check_Second_Service_when_Forwarded is specific to SCUDIF. Sheet 7: the procedures CAMEL_T_CSI_CHECK_HLR and CAMEL_O_CSI_CHECK_HLR are specific to CAMEL.5. it is specified in 3GPP TS 23. accessible by the process SRI_HLR. If the HLR does not support CAMEL phase 4 or later.078 [12]. 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. If the HLR is not able to determine any compatibility information to be sent to the VLR in the Provide Roaming Number request.2 Procedure Check_Parameters If any parameters required by the rules in clause 8 are missing from the message.2. 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. it is specified in 3GPP TS 23.078 [12]. 7. the test "Result = CSI Active ?" applies to the result of the CAMEL_CSI_Check_HLR procedure.172 [38]. processing continues from the "Fail" exit of the test "Result ?". 7.2.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.078 [12]. Sheet 7: the procedure CAMEL_D_CSI_CHECK_HLR is specific to CAMEL phase 3 or later. The test "Suppress CUG Handling?" is specific to CAMEL phase 4 or later. Sheet 7: A HLR implementing the Mobile Terminating Roaming Retry feature (see sub-clause 5. it is specified in 3GPP TS 23. If the HLR does not support SCUDIF. This procedure gets the result from the CAMEL_CSI_Check_HLR procedure. and modifies it if needed.Release 7 117 3GPP TS 23. Refer to 3GPP TS 23. processing continues from the "No" exit. If the HLR does not support SCUDIF. it is specified in 3GPP TS 23. If the HLR does not support CAMEL.2. processing continues from the "No" exit of the test "Result=CSI active?". it applies a default basic service according to the requirements of the operator. 3GPP .0 (2007-06) Sheet 6: the procedure SCUDIF_CAMEL_CSI_Check_HLR is specific to SCUDIF.2. processing continues from the "No" exit.172 [38]. processing continues from the "Yes" exit of the test "Result = Continue ?". it is specified in 3GPP TS 23. they are specified in 3GPP TS 23. If any parameter has a value which is not in the set of values expected for the parameter. Sheet 7: the procedure SCUDIF_Set_Second_Service_when_Forwarded is specific to SCUDIF.2. Sheet 6: the procedure SCUDIF_Check_Second_Service_before_Negative_Response is specific to SCUDIF.172 [38]. If the HLR does not support SCUDIF.007 [30].

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

0 (2007-06) Process SRI_HLR Process in the HLR to handle a request for routeing information SRI_HLR1(7) Signals to/from the left are to/from the GMSC or the gsmSCF.5.018 V7. 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.079 OR_HLR_CF 6 Yes Result= Fail? No Yes Result= Forward? No See TS 23.172 Result= Fail? No Yes See TS 23.078 CAMEL_ HLR_INIT Yes Result= Fail? No 3 1 2 1 Figure 44a: Process SRI_HLR (sheet 1) 3GPP .Release 7 119 3GPP TS 23.

signals to/from the right are to/from the VLR Firs t_ Forwarding_ HLR Yes Result= Fail? No Yes Result= Forward? See TS 23.5.018 V7.Release 7 120 3GPP TS 23.078 CAMEL_ CSI_Check _ HLR No See TS 23.0 (2007-06) 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 gs mSCF.078 CAMEL_ CSI_Check _ HLR 2 See TS 23.172 Yes Result= CSI active? No Yes Result= CSI active? No gsmSCF Initiated No Call? 4 4 Yes Yes Suppress C CBS Handling? No CCBS_Handling_ HLR See TS 23.093 Yes Result = Forward No No Result = OK Yes 5 1 2 1 Figure 44b: Process SRI_HLR (sheet 2) 3GPP .172 SCUDIF_CAMEL_ CSI_Check _ HLR SCUDIF_CAMEL_ CSI_Check _HLR See TS 23.

Release 7 121 3GPP TS 23.0 (2007-06) Process SRI_HLR Process in the HLR to handle a request for routeing information SRI_HLR3(7) Signals to/from the left are to/from the GMSC or the gsmSCF.018 V7.081 CLI_HLR_ Set_CLI 8 Figure 44c: Process SRI_HLR (sheet 3) 3GPP . signals to/from the right are to/from the VLR 5 OR_HLR_ Interrogate_VLR See TS 23.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.5.

Release 7

122

3GPP TS 23.018 V7.5.0 (2007-06)

Process SRI_HLR
Process in the HLR to handle a request for routeing information

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

Release 7

123

3GPP TS 23.018 V7.5.0 (2007-06)

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; signals to/from the right are to/from the VLR

Provide Roaming Number ack

Provide Roaming Number negative response

Routeing address:= MSRN

PRN_Error_ HLR

2

Result= Fail? No Yes

1 Forward_ CUG_Check

SCUDIF_Check_ Second_Service_ after_PRN

Result= Call allowed? See TS 23.172 Yes

No

11 9

Result= Continue? No Yes 7

4

10

Send Routeing Info ack

Idle

Figure 44e: Process SRI_HLR (sheet 5)

3GPP

Release 7

124

3GPP TS 23.018 V7.5.0 (2007-06)

Process SRI_HLR
Process in the HLR to handle a request for routeing information

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 7

125

3GPP TS 23.018 V7.5.0 (2007-06)

Process SRI_HLR
Process in the HLR to handle a request for routeing information 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 7

126

3GPP TS 23.018 V7.5.0 (2007-06)

Procedure Check_Parameters
Procedure to check the parameters o f a received m essage

Chk_Par1(1)

All required parameters present? Yes

No

All parameter values acceptable? Yes

No

Set negative response: Data missing

Set negative re sponse: Unexpected data value

Result:= Pass

Result:= Fail

Figure 45: Procedure Check_Parameters

3GPP

018 V7.007 Set negative response: Number changed Requested service provisioned? Yes No gsmSCF Initiated Call? Yes No Set negative response: service not provisioned Bearer service or Teleservice Yes 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 rejec t Result:= Pass Result:= Fail Figure 46: Procedure Subscription_Check_HLR 3GPP .0 (2007-06) Procedure Subscription_Check_HLR Procedure in the HLR to make subs cription checks for a mobileterminated call SC_HLR1(1) MS known? Yes No Set negative response: Unknown subsc riber Number changed? No Derive requested basic servic e Yes See TS 29.Release 7 127 3GPP TS 23.5.

5.Release 7 128 3GPP TS 23.0 (2007-06) Procedure First_Forwarding_HLR Procedure in t he HLR to handle call forwarding before interrogation of t he VLR FF_HLR1(1) Handle_CFU Result= Fail? No Yes Yes Result= Forward? No Set negative re sponse: Fo rwarding violation No MS not reachable? Yes Handle_CFNRc Result= Fail? No Yes Set negative re sponse: Fo rwarding violation No Result= Forward? Yes Set negative re sponse: Absent subscribe r Result:= Forward Result:= Continue Result:= Forwa rd Result:= Fail Figure 47: Procedure First_Forwarding_HLR 3GPP .018 V7.

0 (2007-06) Procedure PRN_Error_HLR Procedure in t he HLR to handle a negative response for a roaming number request PRN_ E_H1(1) CCB S_Report_ PRN_Failure See TS 23.093 Negative response =OR not allowed?? Yes No Set negative response: OR not allo wed Yes Negative response=Facility not sup ported? No Yes Negative response=Absent su bscriber? No Set negative response: Facility n ot supported Negative response=No roaming number? No Yes Handle_CFNRc Han dle_CFNRc Set negative response: System failu re Fail Result? Forward Forward Result? Fail Not reachable Set n egative respon se: Forwarding violation Super_Charged_ SRI_Error_ HLR Yes Not re achable Set negative response: Forwarding violation Result= Purged? No Se t negative response: Absent subscriber Set negative response: System failure Result:= Forward Result:= Fail Result:= Fail Figure 48: Procedure PRN_Error_HLR 3GPP .Release 7 129 3GPP TS 23.5.018 V7.

0 (2007-06) Procedure Forward_CUG_Check Procedure to carry out CUG authorisation check for a forwarded call FWD_CUG1(1) No Yes CUG info provided in ro uteing information re quest Yes CUG provisioned for forward ing subscriber against reque sted basic service No P erform Forwarding CUG au thorisation As de fined in TS 23.085 Figure 49: Procedure Forward _CUG_Check Figure 50: Void 3GPP .018 V7.Release 7 130 3GPP TS 23.085 CUG au thorisation result Fail Pass Result:= Call allo wed Result:= Call barred Result: = Call allowed Upda te CUG inf o As defined in TS 23.5.

018 V7.Release 7 131 3GPP TS 23.0 (2007-06) Procedure Check_IC_Barring Procedure to check call request against SS barring and ODB categories CIB1(2) Yes Operato r determined BAIC imposed? No Yes Operato r determined BIC-Roam imposed? No No MS registered in HPLM N country? Yes 1 Yes Operato r determined BIC-RoamHZ imposed? No No MS registered in HPLM N zone? Yes Result:= Ca ll barred (ODB) 1 Figure 51a: Procedure Check_IC_Barring (sheet 1) 3GPP .5.

5.Release 7 132 3GPP TS 23.018 V7.0 (2007-06) 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 W ait_For_ B AIC_ Response Continue call handling From proce ss MAF022 Yes Call ba rred? No Initiate handling of BIC-Roam To process MAF023 W ait_For_ BIC-Roam_ Response Continue call handling From proce ss MAF023 Yes Call ba rred? No Result:= Call barred (S S ba rring) Result:= Call allowed Figure 51b: Procedure Check_IC_Barring (sheet 2) 3GPP .

0 (2007-06) Procedure IC_CUG_Check Procedure to carry out CUG authoris ation check for an incoming (MT) call IC_CUG1(1) Signals to/from the right are to/from the proc ess CUG _MAF015 HLR supports CUG? Yes No No SRI contains CUG info? Yes Yes Outgoing Acc ess pres ent? No inc oming call Wait_For_ CUG_Response reject call (caus e) response to call reques t complete call (conditional CUG info) Result:= Call allowed Result:= Call barred (cause) Result:= Call allowed Figure 52: Procedure IC_CUG_Check 3GPP .018 V7.5.Release 7 133 3GPP TS 23.

0 (2007-06) Procedure Handle_CFU P roc edure in the HLR t o handle Call Forwarding Unconditional H_CFU1(1) Signals to/from the right are to/from the process MAF007 CAMEL_CHE CK _SII2_C DTI See TS 23.5.078 No Result = Pass ? Y es initiate handling of CFU Wait_F or_ CFU _Result continue call handling Y es Error? No Normal call? No Yes Result:= Fail Result:= Forward Result:= Continue Figure 53: Procedure Handle_CFU 3GPP .Release 7 134 3GPP TS 23.018 V7.

078 No Result = Pass ? Y es initiate handling of CFNRc Wait_F or_ CFN Rc_Res ult continue call handling Y es Error? No Yes Mobile subs criber not reachable? No Result:= Fail Result:= Forward Result:= Not reachable Figure 54: Procedure Handle_CFNRc 3GPP .0 (2007-06) Procedure Handle_CFNRc P roc edure in the HLR or VLR to handle Call Forwarding on Mobile S ubsc riber Not Reachable H_CFNRc1(1) Signals to/from the right are to/from the process MAF010 CAMEL_CHE CK _SII2_C DTI See TS 23.018 V7.5.Release 7 135 3GPP TS 23.

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

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

0 (2007-06) 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.Release 7 138 3GPP TS 23. Idle Provide Roam ing 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.116 No Result= Purged? Yes No Result= Purged? Yes 3 1 5 1 Idle Figure 55a: Process PRN_VLR (sheet 1) 3GPP .5.018 V7.

Release 7 139 3GPP TS 23.093 Yes 3GPP . 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.5.0 (2007-06) Process PRN_VLR Process in the VLR to handle a request for a roaming number True Signals to the left are to the HLR.078 PLMN BC.081 CCBS_Handle_ PRN Provide Roaming Number ack MT Roaming Retry Supported No Idle 6 See TS 23. ISDN BC.018 V7.

Release 7 140 3GPP TS 23.0 (2007-06) 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) No Signals to the left are to the HLR.018 V7. ISDN BC.5.078 1 Create IMSI record Location info confirmed in HLR:= False Only if >1 MSC per VLR Confirmed by radio contact:=False.081 Data confirmed by HLR? True False CCBS_Handle_ PRN See TS 23. N ISDN LLC & ISDN HLC (as available) Store Alerting Pattern (if received) 6 CLI_PRN_ VLR See TS 23. IM detached:=False SI Allocate LM SI If used by VLR Store compatibility info PLM BC. Data confirmed by HLR:=False.093 More authentication sets needed? No Yes Provide Roam ing Number ack Fetch_ Authentication_ Sets_VLR Restore_ Subscriber_ Data_VLR Idle Figure 55c: Process PRN_VLR (sheet 3) 3GPP . MSRN available Yes Allocate MSRN Set negative response: No roaming num ber CAMEL_ SET_SOA See TS 23.

018 V7.0 (2007-06) 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.Release 7 141 3GPP TS 23.5. 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 .

Release 7 142 3GPP TS 23.0 (2007-06) 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 BC. N 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 . Data confirmed by HLR:=False.018 V7.5. IM detached:=False SI Allocate LM SI If used by VLR Store compatibility info PLM BC.

093 Provide Roam ing Number ack 8 Figure 54f: Process PRN_VLR (sheet 6) 3GPP .Release 7 143 3GPP TS 23. N ISDN LLC & ISDN HLC (as available) 1 Store Alerting Pattern (if received) CLI_PRN_ VLR See TS 23.5.018 V7. signals to/from the right are to/from the MSC unless shown otherwise.0 (2007-06) 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.081 CCBS_Handle_ PRN See TS 23. ISDN BC.078 Set negative response: No roam ing num ber Set negative response: Absent subscriber Store compatibility info PLM BC. 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 MSC per VLR >1 Received MSC number= Stored MSC num ber? No False Confirmed by radio contact True Use received MSC number for MSRN Use stored MSC number for MSRN Set negative response: System failure Busy subscriber? No Yes 7 Yes Absent Subscriber? No Allocate MSRN Process Access Request negative response CAMEL_ SET_SOA See TS 23.

N ISDN LLC & ISDN HLC (as available) Store Alerting Pattern (if received) CLI_PRN_ VLR See TS 23. ISDN BC.081 CCBS_Handle_ PRN See TS 23.0 (2007-06) 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. PAR successful:=False.018 V7. Fatal PAR error:=False Idle Figure 54g: Process PRN_VLR (sheet 7) 3GPP .093 Provide Roam ing Number ack PAR pending:=False.Release 7 144 3GPP TS 23.078 Store compatibility info PLM BC.5. No MSRN available? Yes Set negative response: No roaming number >1 Yes Received MSC number= Stored MSC num ber? 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.

5.0 (2007-06) 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. signals to/from the right are to/fro m the MSC PAR pending:= True Process_ A ccess_ Request_VLR No Result= Pass? Yes PAR successful:= True PAR successful:= False PAR pending:= Fa lse PAR pending := False PAR Completed Fatal PAR error? Yes No Wait_For_ Call_Arrival Fatal PAR error:= True Fatal PAR error:= False Call arrived Radio co nnection released Call arrived PAR succe ssful:= False PAR Completed Fatal PAR error:= False Idle Idle Figure 54h: Process PRN_VLR (sheet 8) 3GPP .Release 7 145 3GPP TS 23.018 V7.

018 V7.0 (2007-06) 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 W ait_Fo r_ Data Restore Data ack Restore Data n egative re sponse Update Sub scriber Data Update HLR number Update MS Not Re achable indicator If received from HLR Data confirmed by HLR:=True Figure 56: Process Restore_Subscriber_Data_VLR 3GPP .5.Release 7 146 3GPP TS 23.

018 V7.0 (2007-06) Process PSI_VLR Process in the VLR to handle a request from the HLR for subscriber inform ation PSI_VLR1(2) Signals to/from the left are to/from the HLR.5. 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 Roam ing in LA allowed? Yes Set subscriber state requested Subscriber state:= Network determ ined not reachable Subscriber state:= Assumed i dle 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 7 147 3GPP TS 23.

018 V7.5. signals to/from the right are to/from the MSC Obtain Subscriber Info ack Subscriber state recei ved? 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 .Release 7 148 3GPP TS 23.0 (2007-06) Process PSI_VLR Process in the VLR to handle a request from the HLR for subscriber inform ation Wait_For_ MSC_Response PSI_VLR2(2) Signals to/from the left are to/from the HLR.

Release 7

149

3GPP TS 23.018 V7.5.0 (2007-06)

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 l ocation info fromSGSN? 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 num ber, geodetic information and geographical information

Figure 58: Procedure Retrieve_Location_Info_VLR

3GPP

Release 7

150

3GPP TS 23.018 V7.5.0 (2007-06)

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 inform ation required

Paging via SGSN possible? Yes

No

Set paging via SGSN possible

No

Location area ID known?

Yes

Page type= Acti ve inform on ati retrieval

Search for MS

Page type= Active inform on ati retrieval

Page MS

Wait_For_ Search_ Result

Wait_For_ Page_ Result

Figure 59a: Procedure Active_Info_Retrieval_VLR

3GPP

Release 7

151

3GPP TS 23.018 V7.5.0 (2007-06)

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 M S via SGSN

Roam ing in LA allowed? Yes

Page MS Subscriber state:=Not reachable

Wait_For_ Search_ Result No

Yes

Location info recei ved?

No

Yes

Location info recei ved?

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 7

152

3GPP TS 23.018 V7.5.0 (2007-06)

7.2.4 Functional requirements of MSC
7.2.4.1 7.2.4.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 "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call. The signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure.

7.2.4.3

Prepaging_Search_For_MS_MSC

The test "MS connection exists" takes the "Yes" exit if there is a radio connection established between the MS and the network. The test "MS busy" takes the "Yes" exit if the MS is engaged on a circuit-switched call. The signal input "MS connection established" indicates that the MS has responded to paging, or sent a CM service request for anything other than a circuit-switched call, or completed the location registration procedure.

7.2.4.4

Process OSI_MSC

If the MS is engaged on a circuit-switched call, the state is busy, otherwise assumed idle.

7.2.4.5

Process RCL_MSC

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.

7.2.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. The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network. The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting Control procedure (see 3GPP TS 25.413 [27]) with the Request Type IE set to "Change of service area". If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct".

7.2.4.7

Procedure 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. The test "GSM Access" takes the "Yes" exit if the MS is using a GSM radio access to communicate with the network. The test "Report on change of service area?" takes the "Yes" exit if the MSC has performed the Location Reporting Control procedure (see 3GPP TS 25.413 [26]) with the Request Type IE set to "Change of service area". If the test "Report on change of service area?" takes the "No" exit the MSC shall perform a Location Reporting Control procedure with the Request Type IE set to "Direct".

3GPP

Release 7

153

3GPP TS 23.018 V7.5.0 (2007-06)

7.2.4.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.
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; 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 60: Process Prepage_MSC

3GPP

0 (2007-06) Procedure Prepaging_Search_For_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. 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 Set access connection status Result:= Pass MS busy? No Set negative response: Busy Subscriber Page MS negative response Result:= Fail Yes PPSMS_M1(1) In specified location area Page Start Page response timer Wait_For_ Page_ Response 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 7 154 3GPP TS 23.018 V7.5.

0 (2007-06) Procedure Prepaging_Search_For_MS_MSC Procedure in t he MSC to page a n MS in a specified location area Signals to/from the left are to/fro m the BSS.5. signals to/from the right are to/from the VLR unless m arked othe rwise Paging via SGSN possible? MS connection exists? No No MS busy? Yes Page MS via SGS N No Set negative response: Busy Subscribe r Set access connection status Page MS negat ive respo nse Yes PPSMS_M1(1) Yes In specified location area Page Sta rt Page response timer Wait_For_ Pa ge_ Response Result:= Pass Result:= Fail MS connection established Page response timer e xp ired CM Service Request CM Service Request For circuitswitched call To process OCH_MSC Se t acce ss connection status Set negat ive response: A bsent S ubscriber P age MS negative response Set negative response: Busy Subscribe r (NDUB) Page MS negat ive respo nse Result:= Pa ss Result:= Fail Result:= Fail Figure 62: Procedure Prepaging_Search_For_MS_MSC 3GPP .018 V7.Release 7 155 3GPP TS 23.

0 (2007-06) Process OSI_MSC Process in the MS C to hand le a request from the VLR for information on the subscriber's location and state OSI_MSC1(1) Signals to /from t he left are to/from the VLR Idle Obtain Subscriber Info S ubscriber state requested? Yes No S et subscriber state Obtain Subscriber Info ack Idle Figure 63: Process OSI_MSC 3GPP .Release 7 156 3GPP TS 23.018 V7.5.

018 V7.Release 7 157 3GPP TS 23.0 (2007-06) Process AIR_MSC Process in the M to retrieve SC any one or more of the current location. MS classm and IM of a subscriber ark EI AIR_MSC1(1) Signals to/from the left are to/from the VLR Idle Search for MS Page MS Active_Info_ Retrieval_ Search_M SC Active_Info_ Retrieval_ Page_MSC Idle Figure 64: Process AIR_MSC 3GPP .5.

0 (2007-06) 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.Release 7 158 3GPP TS 23.5. 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 circuitsw itched 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 .018 V7.

5.018 V7.0 (2007-06) 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 ar e to/from the BSS. signals to/fr om the right ar e to/from the VLR unless mar ked 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 Star t Page response timer Location info requested? Yes No Wait_For_ Page_ Response Report on change of ser vice ar ea? No Yes Page r esponse timer expired MS connection established CM Service Request For circuitswitched call Location Reporting Control CM Service Request To pr ocess OCH_MSC Wait_For_ Location_ Repor t 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 .Release 7 159 3GPP TS 23.

Release 7 160 3GPP TS 23.5.018 V7.0 (2007-06) 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 .

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

sheet 6. sheet 11. If CAMEL information is available for the subscriber but the GMSC does not support the required CAMEL phase. Sheet 6: it is an operator option whether to send an Address Complete message if the VLR returns forwarding information. then ORLCF may take place ('ORLCF' result from CAMEL_Check_ORLCF_VMSC).078 [12]. it is specified in 3GPP TS 23. sheet 10: the procedure CCBS_Set_Diagnostic_For_Release is specific to CCBS.5. Sheet 3: the procedure Process_Call_Waiting is specific to Call Waiting. this signal will not be received from the VLR. it is specified in 3GPP TS 23. Sheet 3. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 3. then ORLCF may take place. processing continues from the "Continue" exit of the test "Result?". it is specified in 3GPP TS 23. If the VLR does not support CAMEL or no CAMEL information is available for the subscriber. If the VMSC does not support Call Waiting. If the VMSC does not support Optimal Routeing.078 [12]. the procedure Complete_Call_In_MSC and the procedure Process_Call_Waiting will not return a "Reconnect" result.079 [13].072 [11].0 (2007-06) Sheet 3: the procedure CAMEL_MT_GMSC_DISC5 is called if the VMSC supports CAMEL phase 3 or later.087 [20]. Sheet 6: the procedure CAMEL_MT_VMSC_Notify_CF is specific to CAMEL phase 3 or later.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 3: if the VMSC does not support CAMEL phase 3 or later. sheet 11: the procedures CD_Failure and CD_Success are specific to Call Deflection.072 [11]. Sheet 3: the processing in the branch starting with the input signal"Process Call Waiting" is specific to Call Wait. they are specified in 3GPP TS 23.093 [23]. Sheet 3: the procedure UUS_ICH_Check_Support is specific to UUS. sheet 5. Sheet 4: the procedure CAMEL_ICH_LEG2_MSC isspecific to CAMEL phase 4 or later. sheet 13: the procedure CCBS_Check_Last_Call is specific to CCBS. If the VMSC does not support CAMEL phase 3 or later. If the VMSC sends an Address Complete message. The Resume Call Handling request shall include the relevant CAMEL information ('ORLCF' result from CAMEL_Check_ORLCF_VMSC).Release 7 162 3GPP TS 23. it is specified in 3GPP TS 23. - Sheet 5: the procedure Handle_ORLCF_VMSC is specific to Support of Optimal Routeing. It is specified in 3GPP TS 23. Sheet 5: the procedure CAMEL_Check_ORLCF_VMSC is specific to CAMEL phase 2 or later. it is specified in 3GPP TS 23. Sheet 5.078 [12]. it shall include the called party's status field of the Backward call indicator set to "no indication". Sheet 3: the procedure CD_Reject is specific to Call Deflection.083 [16]. Sheet 6: If the VMSC does not support CAMEL phase 3 or later. 3GPP . If CAMEL information is available for the subscriber and the GMSC supports the required CAMEL phase.078 [12]. it is specified in 3GPP TS 23. processing starts with the possible call of the procedure CCBS_Check_Last_Call. then ORLCF shall not take place ('VMSCCF' result from CAMEL_Check_ORLCF_VMSC). sheet 12. it is specified in 3GPP TS 23.093 [23]. processing continues from the "No" exit of the test "Result=Reconnect?". 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. Sheet 9: the procedure CAMEL_ICH_LEG2_CF_MSC is specific to CAMEL phase 4 or later.018 V7. it is specified in 3GPP TS 23. sheet 6.

Sheet 6: the procedure Activate_CF_Process is specified in subclause 7.2.2. processing continues from the "Pass" exit of the test "Result?". 7. Sheet 11: the procedure Handle_ORLCF_VMSC is specific to OR. 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. If the VMSC does not support CAMEL phase 4 or later. If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23. Sheet 14: after the VMSC has sent an IAM to the process MT_CF_MSC. Sheet 13. it is specified in 3GPP TS 23. the input signal Int_Release Call will not be received. sheet 14: the procedure CAMEL_MT_GMSC_DISC1 is called if the VMSC supports CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later. it is specified in 3GPP TS 23.079 [13].078 [12].1. processing continues from the "No" exit of the test "Result = Forwarding Failed?". it is specified in 3GPP TS 23. Sheet 10: the procedure CCBS_MT_MSC_Check_Forwarding is specific to CCBS.7.6. Sheet 8: the procedure Send_Answer_If_Required is specified in subclause 7. it is specified in 3GPP TS 23.2.018 V7. Sheet 16: the procedure Process_Hold_Request is specific to Call Hold. it is specified in 3GPP TS 23. the input signal Send Info For MT Reconnected Call ack will not be received. it is specified in 3GPP TS 23.1.083[16].1. 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. Sheet 7: The processing on this sheet is specific to CAMEL phase 3 or later. Sheet 11: the processing on this sheet is specific to CAMEL phase 3 or later. processing continues from the "No" exit of the test "Result=Reconnect?". it is specified in 3GPP TS 23.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.078 [12]. Sheet 15: The processing on this sheet is specific to CAMEL phase 3 or later. If the VMSC does not support OR. Sheet 13. sheet 8: the procedure Send_ACM_If_Required is specified in subclause 7.078 [12]. it is specified in 3GPP TS 23. If the VMSC does not support CAMEL phase 3 or later. Sheet 8: the procedure Send_Network_Connect_If_Required is specified in subclause 7. it acts as a transparent relay for messages received from the GMSC and the process MT_CF_MSC. the input signal Int_Release Call will not be received. If the VMSC does not support CAMEL phase 3 or later. Sheet 16: the procedure Process_Retrieve_request is specific to Call_Hold. the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists. sheet 14: the procedure CAMEL_MT_GMSC_DISC2 is called if the VMSC supports CAMEL phase 3 or later. Sheet 1: for an SMS or SS page. Sheet 6: the procedure UUS_ICH_Set_Info_In_IAM is specific to UUS.1.2.087 [20]. Any message other than Address Complete.2.1. it is specified in 3GPP TS 23. Sheet 8: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later.087 [20].1.078 [12].3. Connect.3. Sheet 8: the procedure Handle_COLP_Forwarding_Interaction_MSC is specified in subclause 7. Answer or Release causes no change of state in the process ICH_MSC. Sheet 13: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS. it is specified in 3GPP TS 23. 3GPP . If the VMSC does not support CAMEL phase 3 or later. Sheet 8: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later.093 [23].083[16].0 (2007-06) Sheet 6.Release 7 163 3GPP TS 23.5.078 [12].4.5.

because the VLR will always use a page type of "circuit-switched call".1. the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23.5. then Page_MS_MSC continues from the beginning of the procedure.3. 3GPP . processing continues from the "Yes" exit of the test "Result=Not provisioned?". or completed the location registration procedure.0 (2007-06) Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls. If the result of location update is not successful. the Search_MS_MSC procedure should return FAIL after sending Search MS negative response (cause Busy Subscriber) to VLR.1 Mobile Terminating CM Activity): If location update procedure is ongoing for the MS. Sheet 1: for an SMS or SS page. because the VLR will always use a page type of "circuit-switched call". Sheet 4: A MSC not implementing the MT Roaming Retry feature may not immediately stop paging upon receipt of a Cancel Location message. then Page_MS_MSC procedure returns with PASS.135 [25]). 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). the MSC should delay the launching of Search_MS_MSC procedure until location update procedure ends. If the "follow-on" indicator is received and MSC supports "follow-on" feature.135 [25].008 [13] section 4. the Page_MS_MSC procedure should return FAIL after sending Page MS negative response (cause Busy Subscriber) to VLR. Otherwise. 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. Sheet 2: if there is one established call.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. 7.018 V7. the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call.3. but the more generalized procedure Search_For_MS_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures. and if the "follow-on" indicator is received and the MSC supports the "follow-on" feature.1 Mobile Terminating CM Activity): If location update procedure is ongoing for the MS.3. but the more generalized procedure Page_MS_MSC is equally applicable to paging for SMS delivery or network-initiated SS procedures.Release 7 164 3GPP TS 23. Otherwise. the test "Call still exists" takes the "Yes" exit if the SMS or SS transaction which led to the page still exists. the MSC should delay the launching of Page_MS_MSC procedure until the location update procedure ends. Sheet 2: the procedure Check_MT_Multicall_MSC is specific to Multicall. If the VMSC does not support Multicall.5. it is specified in 3GPP TS 23. then the procedure should return FAIL after sending Page MS negative response (cause Absent Subscriber) to VLR. 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 1: If the MSC supports the option to delay the Mobile Terminating CM request during a location update procedure (see 3GPP TS 24. If there are two or more established calls (the Multicall case).1. If the result of location update is successful and location update is not through Gs interface. Sheet 1: the test "SMS or SS page" is not required for the handling of circuit-switched calls. Sheet 1: If the MSC supports the option to delay Mobile Terminating CM request during a location update procedure (see 3GPP TS 24.008 [13] section 4.5.1. If the result of location update is successful and location update is through Gs interface.

it is specified in 3GPP TS 23.3. If there are two or more established calls (the Multicall case). or completed the location registration procedure. then the procedure should return FAIL after sending the Search MS negative response (cause Absent Subscriber) to VLR.0 (2007-06) - If the result of location update is successful and location update is not through Gs interface.135 [25].007 [30]. it is specified in 3GPP TS 23. the negative response Busy Subscriber (More calls possible) includes the basic service list which applies for the established calls (See 3GPP TS 23. it is specified in 3GPP TS 23. Sheet 3.1. Sheet 2. sheet 3. sheet 9: the procedure CCBS_ICH_MSC_Report_Failure is specific to CCBS. Sheet 2: if there is one established call. If the VMSC does not support Multicall. then the procedure continues from the beginning of the Page_MS_MSC procedure. Sheet 1: the procedure CCBS_Report_Not_Idle is specific to CCBS. Sheet 1: the VMSC derives the PLMN bearer capability required for the call according to the rules defined in 3GPP TS 29.078 [12]. 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. it is specified in 3GPP TS 23. sheet 5. processing continues from the "No" exit of the test "Result=Reconnect?". it is specified in 3GPP TS 23. then the Search_MS_MSC procedure returns with PASS. 3GPP .093 [23]. Sheet 3: the signal input "MS connection established" indicates that the MS has responded to paging. it is specified in 3GPP TS 23. Sheet 2: the procedure Establish_Terminating_TCH_Multicall is specific to Multicall.093 [23]. If the result of the location update is not successful. 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. sheet 4. it is specified in 3GPP TS 23.135 [25].5. sheet 5: the procedure CCBS_ICH_MSC_Report_Success is specific to CCBS.Release 7 165 3GPP TS 23. or sent a CM service request for anything other than a circuit-switched call. 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.018 V7.093 [23]. sheet 5. sheet 6. 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 4 : A MSC not implementing the MT Roaming Retry feature may not immediately stop paging upon receipt of a Cancel Location message. Sheet 2.087 [20]. sheet 7: the procedure CAMEL_MT_GMSC_DISC4 is called if the VMSC supports CAMEL phase 3 or later. If the VMSC does not support CAMEL phase 3 or later. 7. sheet 6. If the result of location update is successful and location update is through Gs interface.4 Procedure Complete_Call_In_MSC Sheet 1: the procedure Set_CLIP_Info_MSC is specific to CLIP. 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).078 [12]. sheet 3. sheet 9. Sheet 2: the test "Result=Rejected?" can take the "Yes" exit only if the procedure Establish_Terminating_TCH_Multicall was called. Sheet 2. Sheet 2: the procedure Check_MT_Multicall_MSC is specific to Multicall. processing continues from the "Yes" exit of the test "Result=Not provisioned?". the negative response Busy Subscriber (More calls possible) includes the basic service which applies for the established call. Sheet 1: the procedure UUS_ICH_UUS1_Implicit_Active is specific to UUS. Sheet 1.135 [25]).078 [12].

Sheet 8. Sheet 4. processing continues from the "Yes" exit of the test "Result=Pass?". it is specified in 3GPP TS 23. processing continues from the "Yes" exit of the test "Result=Pass?". processing continues from the "Yes" exit of the test "Result=Pass?". Sheet 11: the procedures UUS_MSC_Check_UUS2_UUI_to MS and UUS_MSC_Check_UUS2_UUI_to NW are specific to UUS.087 [20]. If the VMSC does not support CAMEL phase 3 or later.5.1. sheet 7: the procedure Handle_AoC_MT_MSC is specific to AoC. sheet 10: the procedure UUS_MSC_Check_UUS1_UUI is specific to UUS. sheet 7: the procedure CAMEL_MT_GMSC_ANSWER is called if the VMSC supports CAMEL phase 3 or later.087 [20]. If the VMSC does not support UUS.3. Sheet 7: the procedure Send_Answer_If_Required is specified in subclause 7.078 [12]. Sheet 3.0 (2007-06) Sheet 3: the procedure CAMEL_MT_MSC_ALERTING is specific to CAMEL phase 4 or later. sheet 11: the procedure Handling_CD_MSC is specific to Call Deflection. sheet 7: the procedure Set_COL_Presentation_Indicator_MSC is specific to COLP. sheet 6: the procedure UUS_ICH_Check_Support is specific to UUS. Sheet 3.1. Sheet 11: the procedure CD_UUS_Interaction is specific to Call Deflection. it is specified in 3GPP TS 23. they are specified in 3GPP TS 23. if the VMSC does not support Call Deflection the input is discarded. 7. If the VMSC does not support CAMEL phase 4 or later.1. it is specified in 3GPP TS 23.3. 3GPP .072 [11]. Sheet 6: the procedure CAMEL_Stop_TNRy is called if the VMSC supports CAMEL phase 3 or later. processing continues from the "Yes" exit of the test "Result=Pass?".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. Sheet 3: the procedure Send_ACM_If_Required is specified in subclause 7. sheet 11: the processing in the branch starting with the input "CD Request" is specific to Call Deflection. If the VMSC does not support Multicall.2. Sheet 5.018 V7. processing continues from the "Yes" exit of the test "Result=Pass?".072 [11]. Sheet 5.2. it is specified in 3GPP TS 23.5.1. it is specified in 3GPP TS 23.087 [20]. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.087 [20]. sheet 11: the procedure UUS_ICH_Check_Forwarding is specific to UUS. sheet 6: the procedure Establish_Terminating_TCH_Multicall is specific to Multicall.5 7.135 [25]. Sheet 9.1. The message is saved for processing after return from the procedure. processing continues from the "Pass" exit of the test "Result?". it is specified in 3GPP TS 23.3.4.2. Sheet 3: the task "UTU2Cnt:=0" is executed only if the VMSC supports UUS.Release 7 166 3GPP TS 23. If the VMSC does not support UUS. Sheet 4. it is specified in 3GPP TS 23.078 [12].078 [12]. Sheet 4. If the VMSC does not support AoC. Sheet 8: the input signal "CAMEL TNRy expired" will be received only if the VMSC supports CAMEL phase 3 or later. Sheet 4: the procedure Send_Network_Connect_If_Required is specified in subclause 7.

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.5. 3GPP .0 (2007-06) 7.3.1.3.7 7.9 7.14.018 V7.3.1.1.1. 7.8 Void Procedure Establish_Terminating_TCH_If_Required The procedure TCH_Check is specified in subclause 7.Release 7 167 3GPP TS 23.1.1.3. The message is saved for processing after return from the procedure.

0 (2007-06) 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. Call answered := False. UUS3 active:=False. TCH allocated:=False. UUS1 explicit active:=False.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.Release 7 168 3GPP TS 23. UUS CF interaction:=False.5. Store UUS information (if received) Release MSRN Send Info For Incoming Call Idle Wait_For_ Page_Request Continue CAMEL Handling ACM sent:=False. 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.018 V7. BOR:=False. UUS1 implicit active:=False. On_Hold:=False CAMEL_ ICH_MSC_ INIT See TS 23. Network connect sent:=False.078 Wait_For_ Page_Request Idle Figure 67a: Process ICH_MSC (sheet 1) 3GPP . UUS1 result sent:=False. Answer sent:=False. UUS2 active:=False.

0 (2007-06) 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 Page MS Send Info For Incoming Call Ack Call is to be forwarded Search For MS Complete Call Set cause Page_ MS_MSC 1 Search_For_ MS_MSC 2 See TS 23.018 V7.078 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 Figure 67b: Process ICH_MSC (sheet 2) 3GPP .Release 7 169 3GPP TS 23.5.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 Wait_For_ MT_Call_ Result Release call resources CAMEL_ MT_GMSC_ DISC4 Idle Wait_For_ MT_Call_ Result Wait_For_ MT_Call_ Result Idle Result= Reconnect? No Release Yes Yes Result= Reconnect? No See TS 23.

078 Release transaction CCBS_Check_ Last_Call See TS 23.093 Signals to/from the left are to/from the GMSC.018 V7.Release 7 170 3GPP TS 23.093 Result= Pass? No Yes Yes Result= Pass? No Store CW Treatment indicator for this call if received in SII2 UUS_ICH_ Check_ Support See TS 23.072 Complete_ Call_In_MSC See TS 23.0 (2007-06) 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.078 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 Cause= No Subscriber Reply? No CAMEL_ MT_GMSC_ DISC4 CAMEL_ MT_GMSC_ DISC5 Yes Call setup failed To Subs_FSM Call established To Subs_FSM Call setup failed 5 Yes Yes Result= Fail No Result= Fail No Result= Reconnect? Yes Send Info For MT Reconnected Call No Result= Reconnect? No Release Yes Wait_For_ MT_Call_ Result Yes Result= Reconnect? No Send Info For MT Reconnected Call Wait_For_ Reconnected_ Call_Result Wait_For_ Reconnected_ Call_Result See TS 23.5.083 Process_ Call_ Waiting CCBS_Set_ Diagnostic_ For_Release See TS 23.

0 (2007-06) 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.5.078 CAMEL_ICH_ LEG2_MSC Idle Figure 67d: Process ICH_MSC (sheet 4) 3GPP .Release 7 171 3GPP TS 23.078 CAMEL_ICH_ LEG1_MSC (Leg1_Status) Wait_For_ Clear See TS 23.018 V7.

093 Release call resources Idle Figure 67e: Process ICH_MSC (sheet 5) 3GPP .5.079 Accepted CAMEL_ MT_GMSC_ DISC6 Release call resources Forwarding Failed CD_Failure See TS 23.018 V7.Release 7 172 3GPP TS 23.072 CD_Success See TS 23.0 (2007-06) 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.072 Idle Wait_For_ Release_ From_GMSC 3 Release CAMEL_ MT_GMSC_ DISC6 CCBS_Check_ Last_Call See TS 23.078 See TS 23.

072 CD_Success See TS 23.087 CAMEL_ MT_GM SC_ DISC4 See TS 23.018 V7.078 CD_Failure See TS 23.5.078 Yes Result= Reconnect? No CCBS_Check_ Last_Call 4 See TS 23. True) See TS 23.Release 7 173 3GPP TS 23.0 (2007-06) Process ICH_MSC Process in the M SC 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.093 Wait_For_ Forward_ACM Idle Figure 67f: Process ICH_MSC (sheet 6) 3GPP .093 Set redirecti on information Send_ACM_ If_Required Activate_ CF_Process Fail Result? Release Pass Release UUS_ICH_ Set_Info_ In_IAM 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.072 Wait_For_ Reconnected_ Call_Result CCBS_Check_ Last_Call See TS 23.

Wait_For_Reconnected_Call_Result ICH_MSC7(17) Signals to/from the left are to/from the GMSC.Release 7 174 3GPP TS 23.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_MT_Call_Result.018 V7. 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 .5.

Release 7 175 3GPP TS 23.078 CAMEL_MT_ MSC_ALERTING Result? Answer Pass Wait_For_ Forward_Answer Else Release Release Answer Release See TS 23.078 See TS 23. 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.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_ Forward_ACM ICH_MSC8(17) Signals to/from the left are to/from the GMSC.078 CAMEL_ MT_GM SC_ DISC4 CAMEL_ MT_GM SC_ ANSWER See TS 23.018 V7.5.078 Result? Pass No Result= Reconnect? Yes Set COLP presentation indicator Handle_COLP_ Forwarding_ Interaction_MSC Else Else Result? Pass Release Result? Fail Reconnect Handle_COLP_ Forwarding_ Interaction_MSC Release 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 .078 CAMEL_ MT_GMSC_ ANSWER CAMEL_ MT_GM SC_ DISC6 See TS 23.

018 V7.0 (2007-06) 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.5.078 CAMEL_ICH_ LEG1_MSC (Leg1_Status) Wait_For_ Clear See TS 23.Release 7 176 3GPP TS 23.078 CAMEL_ICH_ LEG2_CF_MSC Idle Figure 67i: Process ICH_MSC (sheet 9) 3GPP .

Release 7 177 3GPP TS 23.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 . signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Release Release Release CAMEL_ MT_GM SC_ DISC4 See TS 23.5.078 CAMEL_ MT_GM SC_ DISC6 Yes Result= Reconnect? No CCBS_MT_ MSC_Check_ Forwarding Send Info For MT Reconnected Call See TS 23.078 See TS 23.018 V7.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_ Forward_ACM ICH_MSC10(17) Signals to/from the left are to/from the GMSC.093 To VLR Wait_For_ Reconnected_ Call_Result Send Info For MT Reconnected Call negati ve response See TS 23.

018 V7. 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.093 Release call resources Idle Figure 67k: Process ICH_MSC (sheet 11) 3GPP .072 CD_Failure CD_Success See TS 23.078 CCBS_Check_ Last_Call See TS 23.072 Wait_For_ Release_From_ GMSC Release CAMEL_ MT_GM SC_ DISC6 See TS 23.Release 7 178 3GPP TS 23.079 No Result= Accepted? Yes No Result= Forwarding Failed? Yes 4 See TS 23.5.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_ Reconnected_ Call_Result ICH_MSC11(17) Signals from the left are from the GMSC.

018 V7.078 Yes Result= Reconnect? No Release transaction Release CCBS_Check_ Last_Call See TS 23. signals to/from the right are to/from the BSS unless marked otherwise Release Release transaction CAMEL_ MT_GM SC_ DISC6 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 7 179 3GPP TS 23.5.078 CAMEL_ MT_GM SC_ DISC4 See TS 23.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_ MT_Call_ Result ICH_MSC12(17) Signals to/from the left are to/from the GMSC.

087 CAMEL_ MT_GM SC_ DISC2 See TS 23.093 Release call resources To Subs_FSM Call cleared Idle Wait_For_ Reconnected_ Call_Result Figure 67m: Process ICH_MSC (sheet 13) 3GPP .5.018 V7.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_Clear ICH_MSC13(17) Signals to/from the left are to/from the GMSC.078 Yes Release transaction Result= Reconnect? No See TS 23.087 UUS_MSC_ Check_ UUS1_UUI Release Send Info For MT Reconnected Call To VLR CCBS_Check_ Last_Call See TS 23. signals to/from the right are to/from the BSS unless marked otherwise Release Release transaction UUS_MSC_ Check_ UUS1_UUI See TS 23.Release 7 180 3GPP TS 23.078 CAMEL_ MT_GM SC_ DISC1 See TS 23.

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 Release Release Release CAMEL_ MT_GM SC_ DISC2 See TS 23.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Wait_For_ Forward_Clear ICH_MSC14(17) Signals to/from the left are to/from the GMSC.018 V7.5.Release 7 181 3GPP TS 23.078 See TS 23.078 CAMEL_ MT_GM SC_ 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. Wait_For_Forward_Answer.

018 V7. 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 . signals to/from the right are to/from the process MT_CF_MSC unless marked otherwise Wait_For_Forward_ACM.Release 7 182 3GPP TS 23.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call ICH_MSC15(17) Signals to/from the left are to/from the GMSC.5.

018 V7.083 Process_ Hold_ Request Hold reject Retrieve reject Process_ Retrieve_ Request See 3G TS 23.Release 7 183 3GPP TS 23.5.083 Wait_For_ Clear Figure 67p: Process ICH_MSC (sheet 16) 3GPP .0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call Signals to/from the left are to/from the BSS ICH_MSC16(17) Wait_For_ Clear Hold request Retrieve request Hold supported? Yes No No Hold supported? Yes See 3G TS 23.

Release 7 184 3GPP TS 23.5.0 (2007-06) Process ICH_MSC Process in the M SC to handle an incoming (MT) call ICH_MSC17(17) Signals from the left are from the BSS. signals to the right are to the Subs_FSM process. Wait_For_ Clear ECT request MPTY request ECT request MPTY request Wait_For_ Clear Figure 67q: Process ICH_MSC (sheet 17) 3GPP .018 V7.

5.Release 7 185 3GPP TS 23.0 (2007-06) Procedure Page_MS_MSC Procedure in the MSC to p ag e an MS in a speci fied locatio n area No Loca tion area ID known? Yes No Ca ll still exi sts? Yes MS conn ection exi sts? No Yes Signals to/from the left are to/from the BSS. signals to/fro m the right are to/from the VLR unless ma rked o therwise PAGE_M1(3) Set negative respon se: Un known LAI Set negative respon se: System Failu re Cl ea r recei ved:= Fa lse No Yes SMS or SS page? No Yes Pag in g via SGSN possible? In specified lo cati on area Pag e Page MS via SG SN Request call status To Subs_FSM Set access conn ection status Start Page respon se timer Wait_For_ Page_ Re sponse Wait_For_ Ca l _Status Re sult:= Pass Page MS negative response Re sult:= Fail Figure 68a: Procedure Page_MS_MSC (sheet 1) 3GPP .018 V7.

018 V7.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 .5.Release 7 186 3GPP TS 23. 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.0 (2007-06) 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.

signals to/fro m the right are to/from the VLR unless ma rked o therwise Page response timer expired CM Service Request For circu itswitched call MS connection esta blished Release From GMSC Cl ea r rece ived Fa ls e True Abort True Cl ear received False CM Service Request To p ro cess OCH_ MSC Cl ear received False Tru e Set negative respon se: Abse nt Subscriber Set negative respon se: Busy Subscriber (NDUB ) Set access co nn ection status Release transa cti on Page MS negative response Page MS negative response Re sult:= Pass Re sult:= Aborted Cl ea r recei ved:= True Re sult:= Aborted Re sult:= Fail Re sult:= Fail Re sult:= Aborted Wait_For_ Page_ Re sponse Figure 68c: Procedure Page_MS_MSC (sheet 3) 3GPP .5.Release 7 187 3GPP TS 23.018 V7.0 (2007-06) Procedure Page_MS_MSC Procedure in the MSC to p ag e an MS in a speci fied locatio n area Wait_For_ Page_ Re sponse PAGE_M3(3) Signals to/from the left are to/from the BSS.

0 (2007-06) 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. 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 .018 V7.5.Release 7 188 3GPP TS 23.

0 (2007-06) Procedure Search_For_MS_MSC Procedure in the MSC to search for an MS (p age in a ll loca tion ar eas) Signals to/from the left are to/from the BSS. signals to/fro m the right are to/from the VLR unless ma rked o therwise SRCH_M1(3) No Ca ll still exi sts? Yes MS conn ection exi sts? No Yes Cl ea r recei ved:= Fa lse No Yes SMS or SS page? No Yes Pag in g via SGSN possible? Search for MS via SG SN Request call status To Subs_FSM Set negative respon se: System Failu re In a ll lo cati on areas Page Set access conn ection status Search For MS ne ga tive response Start Page respon se timer Re sult:= Pass Re sult:= Fail Wait_For_ Search _ Re sponse Wait_For_ Ca l _Status Figure 69a: Procedure Search_For_MS_MSC (sheet 1) 3GPP .5.Release 7 189 3GPP TS 23.018 V7.

5.018 V7.0 (2007-06) 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.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 . 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.Release 7 190 3GPP TS 23.

018 V7.Release 7 191 3GPP TS 23.0 (2007-06) Procedure Search_For_MS_MSC Procedure in the MSC to search for an MS (p age in a ll loca tion ar eas) Wait_For_ Search _ Re sponse SRCH_M3(3) Signals to/from the left are to/from the BSS.5. signals to/fro m the right are to/from the VLR unless ma rked o therwise Page response timer expired CM Service Request For circu itswitched call MS connection esta blished Release From GMSC Cl ea r rece ived Fa ls e True Abort True Cl ear received False CM Service Request To p ro cess OCH_ MSC Sea rch For MS ack Release transa cti on Cl ear received False Tru e Set negative respon se: Abse nt Subscriber Set negative respon se: Busy Subscriber (NDUB ) Set access co nn ection status Search For MS negative response Search For MS negative response Re sult:= Pass Re sult:= Aborted Cl ea r recei ved:= True Re sult:= Aborted Re sult:= Fail Re sult:= Fail Re sult:= Aborted Wait_For_ Search _ Re sponse Figure 69c: Procedure Search_For_MS_MSC (sheet 3) 3GPP .

Release 7 192 3GPP TS 23. 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 .0 (2007-06) 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.018 V7.5.

Release 7 193 3GPP TS 23.5.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 .0 (2007-06) Procedure Complete_Call_In_MSC Procedure in the MSC to com plete an MT call on request from the VLR CCI_MSC1(11) Signals to/from the left are to/from the BSS. signals to/from the right are to/from the VLR unless marked otherwise Set_CLIP_ Info_MSC Derive required PLMN BC See TS 29.018 V7.087 CCBS_Report_ Not_Idle See TS 23.007 Setup UUS_ICH_UUS1_ Implicit_ Active See TS 23.

Release 7 194 3GPP TS 23.5.135 Re sult= Fa il? No Yes Re sult= Aborted No Yes Yes CA MEL_ MT_GMSC_ DISC4 See TS 23. signals to/fro m the right are to/from the VLR Call Confirmed Multicall supported in MSC? No Establish _ Te rminating_ TCH_If_ Re qui red Yes Establish _ Te rminating_ TCH_ Mu ltica ll See TS 23.093 Complete Call negative response Re sult:= Aborted Re sult:= Re connect Re sult:= Fail 4 Wait_For_ Alerting Figure 70b: Procedure Complete_Call_In_MSC (sheet 2) 3GPP .0 (2007-06) Procedure Complete_Call_In_MSC Procedure in the MSC to complete an MT call on request from the VLR Wait_For_ Setu p_ Re sponse CCI_MSC2(11) Signals to/from the left are to/from the BSS.078 Re sult= Re je cted ? No Yes Abort Re sult= Re connect? No CA MEL_ MT_GMSC_ DISC6 See TS 23.078 Set negative respon se: Ra dio cong estion CCBS_ICH_MSC_ Re por t_Fai lu re See TS 23.018 V7.

signals to/from the right are to/from the VLR unless marked otherwise Alerting Connect UUS_ICH_ Check_Support See TS 23.018 V7.Release 7 195 3GPP TS 23.093 1 See TS 23.5.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 .078 Yes Result= Reconnect? No Result? Answer Pass Fail Release Reconnect Release Abort A Release To GMSC Abort See TS 23.0 (2007-06) Procedure Complete_Call_In_MSC Procedure in the MSC to com plete an MT call on request from the VLR Wait_For_ Alerting CCI_MSC3(11) Signals to/from the left are to/from the BSS.087 UUS_ICH_ Check_Support See TS 23.078 3 Yes Send_ACM_ If_Required 4 Result= Aborted? No UTU2Cnt:=0 See TS 23.078 CAMEL_ MT_GM SC_ DISC4 CAMEL_MT_ MSC_ALERTING See TS 23.087 No Result= Pass? Yes CCBS_ICH_MSC_ Report_Success No Result= Pass? Yes CCBS_ICH_MSC_ Report_Success See TS 23.135 Yes Start No Reply Call Timer Result= Pass? No CAMEL_ Start_TNRy See TS 23.093 No NRCT provi ded? Yes Establish_ Terminating_ TCH_Multicall See TS 23.

Release 7 196 3GPP TS 23.5. 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_GM SC_ DISC4 See TS 23.078 CAMEL_ MT_GM SC_ ANSWER No Result= Reconnect? Yes Result? Fail Release Pass Reconnect Release To GMSC Set_COL_ Presentation_ Indicator_M SC 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.018 V7.0 (2007-06) Procedure Complete_Call_In_MSC Procedure in the MSC to com plete an MT call on request from the VLR 3 CCI_MSC4(11) Signals to/from the left are to/from the BSS.

078 Handling_C D_MSC See TS 23.072 Yes Result= Reconnect? No CCBS_ICH _MS C_ Report_F ailure S ee TS 23. s ignals to/from the right are to/f rom the VLR unless marked otherwis e Alerting failure 1 CD_Request Release transaction CCBS_ICH _MSC_ Report_S uccess See TS 23.Release 7 197 3GPP TS 23.0 (2007-06) Procedure Complete_Call_In_MSC P roc edure in the MSC t o complete an MT call on request from the VLR Wait_F or_ Alert ing CCI_MSC5(11) Signals to/f rom the left are to/f rom the BSS .018 V7.093 Abort Complete Call negativ e response Release To GMSC Result:= Reconnect Result:= Aborted Result:= Fail Figure 70e: Procedure Complete_Call_In_MSC (sheet 5) 3GPP .093 S et cause CAMEL_ MT_GMSC_ DISC4 S ee TS 23.5.

078 Yes Result= Reconnect? Release Abort Abort See TS 23.0 (2007-06) Procedure Complete_Call_In_MSC Procedure in the MSC to com plete an MT call on request from the VLR Wait_for_ Answer CCI_MSC6(11) Signals to/from the left are to/from the BSS.135 1 Result= Pass? No Yes 5 Yes Result= Aborted? No CAMEL_ MT_GM SC_ DISC4 See TS 23.5.078 CAMEL_ MT_GM SC_ DISC6 Result:= Reconnect Result:= Aborted Result:= Aborted Figure 70f: Procedure Complete_Call_In_MSC (sheet 6) 3GPP . signals to/from the right are to/from the VLR unless m arked 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.018 V7.Release 7 198 3GPP TS 23.

0 (2007-06) Procedure Complete_Call_In_MSC Procedure in the MSC to com plete an MT call on request from the VLR 5 CCI_MSC7(11) Signals to/from the left are to/from the BSS.078 CAMEL_ MT_GM SC_ ANSWER Yes Result= Reconnect? Yes Result? Fail Release Pass Reconnect Release To GMSC Set_COL_ Presentation_ Indicator_M SC 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 .078 Set cause See TS 23. signals to/from the right are to/from the VLR unless m arked otherwise Handle_AoC_ MT_MSC No Result= Pass? Yes 2 Connect ack CAMEL_ MT_GM SC_ DISC4 See TS 23.018 V7.Release 7 199 3GPP TS 23.5.

018 V7.0 (2007-06) Procedure Com plete_Call_In _MSC Procedure in t he MSC to c omplete an MT ca ll on request from the VLR W ait_for_ A nswer CCI_MSC8(11) Signals to/from the left are to/from the BSS.087 Result= P as s? Yes No Set negative response: No subsc riber reply Re lease transac tion Complete Call negative response 2 Release trans action Result:= Fail Figure 70h: Procedure Complete_Call_In_MSC (sheet 8) 3GPP . signals to/from the right are to/from the VLR unless ma rked otherwise CAM EL TNRy expired No Reply Call Time r expired UUS_ICH_ C heck_ Forwarding See TS 23.5.Release 7 200 3GPP TS 23.

018 V7.093 CA ME L_ MT_GMSC_ DISC6 See TS 23.087 UUS _MSC_ Ch eck_ UUS 1_UUI See TS 23. W ait_For_Ale rting CCI_MSC9(11) Signals to /from the left are to/from the BSS.5.093 Se t negative resp onse: Bu sy subscriber (UDUB) UUS_MSC_ Check_ UUS1_UUI See TS 23.087 Complete Call negative response Release To GMS C Release transaction Abort Result:= Fail Result:= Aborted Figure 70i: Procedure Complete_Call_In_MSC (sheet 9) 3GPP .0 (2007-06) Procedure Complete_Call_In_MSC Procedure in t he MSC to complete an MT ca ll on request from the VLR W ait_For_Setup_Response.078 User busy? Yes No CCBS_ICH_M SC_ Report_Failu re See TS 23.Release 7 201 3GPP TS 23. signals to/from the rig ht are to/from the VLR unless marked otherwise Release transaction Release From GMSC CCBS_ICH_MSC_ Report _Failure See TS 2 3.

5.018 V7.087 UUS_ICH_ Check_ Forwarding No No See TS 23 .087 Resu lt= Pas s? Ye s Release To G MS C See TS 23.087 UUS_MSC_ Check _ UUS1_UUI Set negative response: Bus y subscriber (UDUB) Complete Call negativ e response Resu lt:= Fail Abort 1 Result:= A borted Figure 70j: Procedure Complete_Call_In_MSC (sheet 10) 3GPP . signals to/from the rig ht are to/from the VLR unless marked otherwise Release transaction From GMSC Re lease See TS 23 .078 CA ME L_ MT_GMSC_ DI SC6 UUS_MSC_ C heck_ UUS1_UUI See TS 23.087 UUS _MSC_ Ch ec k_ UUS 1_UUI Re lease transac tion User bus y? Ye s See TS 23.0 (2007-06) Procedure Com plete_Call_In _MSC Procedure in t he MSC to c omplete an MT ca ll on request from the VLR W ait_Fo r_ A nswer CCI_MSC10(11) Signals to /from t he left are to/from the BSS.Release 7 202 3GPP TS 23.

W ait_For_A nswer Signals to/from the lef t are to/from the BS S.087 UUS _M SC_ Check_UUS2_ UUI_to_NW UUS_M SC_ Check_UUS2_ UUI_to_MS See TS 23.5.087 Wait_F or_ Answer Figure 70k: Procedure Complete_Call_In_MSC (sheet 11) 3GPP . s ignals t o/from the right are to/from the VLR unless marked otherwise CD R equest Int_Releas e_ Call From gsmSS F UUS_ICH_ Check_ Forwarding See TS 23.072 Release To GMS C 2 Complete Call negativ e response Result:= Aborted Result:= Fail Wait_F or_ Answer User to User User to User S ee TS 23.087 Abort No Result= P ass ? Release transaction Yes See TS 23.Release 7 203 3GPP TS 23.0 (2007-06) Procedure Complete_Call_In_MSC P roc edure in the MSC t o complete an MT call on request from the VLR Wait_F or_ Answer CCI_MSC11(11) W ait_For_A lerting.018 V7.072 CD_UUS_ Interaction Handling_ CD_MSC See TS 23.

018 V7.5.Release 7 204 3GPP TS 23.0 (2007-06) Procedure Set_CLIP_Info_MSC Procedure in t he MSC to determine the CLIP information to be sent to the MS Signals to/from the right are to/fro m the process CLIP _MAF002 CAINF_M1(1) Initiate handling of CLIP W ait_For_ CLIP_Info Re lease transaction From BSS Continue call handling Re lease From GMSC Figure 71: Procedure Set_CLIP_Info_MSC Figure 72: Void 3GPP .

signals to/fro m the right are to/from the GMSC TCH_Check Re sult Fa il Use existing Allocate Re ject Aborted Re sult:= Fa il Re sult:= Pass Allocate channel Re sult:= Re jected Re sult:= Aborted Wait_For_ Allocation_ Co mplete Release transa cti on Allocation failure Allocation complete Release Release transa cti on Release transacti on Re sult:= Fa il Re sult:= Pass Re sult:= Aborted Figure 73: Procedure Establish_Terminating_TCH_If_Required 3GPP .5.018 V7.0 (2007-06) Procedure Establish_Terminating_TCH_If_Required Procedure in the terminating VMSC to e stablish a Traffic Channel if one has not been established for this cal l ETTCIR1(1) Signals to/from the left are to/from the BSS.Release 7 205 3GPP TS 23.

signals from the right are from the AoC timer function.0 (2007-06) Procedure Handle_AoC_MT_MSC Procedure in t he MSC to handle AoC signalling towards the MS for an MT call AOCMT_M1(1) Signals t o/from the left are to/from the BSS. Yes A oC(I) provisioned? No Set charging parameters No AoC(C) provisioned? Yes Send Charging Parameters S et charging pa ramete rs Send Charging Parameters S tart AoC acknowledg ment timer W ait_For_ Charging_ Parame ters_ Ack Charging Parameters ack Release conne ction AoC ackno wledgment timer expired Release transaction Result:= Pass Result:= Fail Figure 74: Procedure Handle_AoC_MT_MSC 3GPP .Release 7 206 3GPP TS 23.018 V7.5.

018 V7.Release 7 207 3GPP TS 23.0 (2007-06) Procedure Set_COL_Presentation_Indicator_MSC Procedure in t he MSC to determine the COL presentation indicator value Signals to/from the right are to/fro m the process COLR_MAF041 COIND_M1(1) Initiate handling of COLR W ait_For_ COLR_Info Release transaction From BSS Continue call handling Re lease From GMSC Figure 75: Procedure Set_COL_Presentation_Indicator MSC 3GPP .5.

Release 7 208 3GPP TS 23. If the VLR does not support CCBS. due to super-charger).093 [23]. Sheet3: the procedure Get_AoC_Subscription_Info_VLR is specific to AoC. Sheet 3: the procedure Get_LI_Subscription_Info_MT_VLR is specific to CLIP and COLR. the procedure call is omitted.0 (2007-06) 7.135 [34].3.15. Sheet 1: A VLR not supporting the flag "Subscriber data dormant" shall behave as if the flag is set to false. Sheet 1: the procedure CAMEL_ICH_VLR is specific to CAMEL phase 3 or later. If the VLR does not support both Multicall and Call Waiting. it is specified in subclause 7. sheet 2. . 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.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. Sheet 3: the procedure Get_CW_Subscription_Info_Multicall_VLR is specific to Multicall. 3GPP . this is treated as an unknown MSRN.018 V7.2.2. Sheet 3: the procedure Process_Access_Request_VLR is specified in subclause 7. It is specified in 3GPP TS 23.093 [23]. If the VLR does not support Call Waiting. the " Subscriber data dormant" check takes the "False" exit. processing continues from the "No" exit of the test "CW available?". Sheet 1: If no IMSI record is found. Sheet 3: the test "NDUB?" takes the "Yes" exit if the Page MS negative response or the Search for MS negative response had the value Busy Subscriber (NDUB). Sheet 1: the VLR derives the basic service required for the call according to the rules defined in 3GPP TS 29.3.g. Sheet 3: the procedure Get_CW_Subscription_Info_VLR is specific to Call Waiting.093 [23]. Sheet 1: the procedure CCBS_ICH_Set_CCBS_Call_Indicator is specific to CCBS. "GMSC supports MT Roaming Retry" takes "No" exit. processing continues from the "Forward" exit of the test "Result". it is specified in 3GPP TS 23. processing continues from the possible call of the procedure CCBS_ICH_Set_CCBS_Call_Indicator. Sheet 1. If the VLR supports neither CLIP nor COLR.2 Functional requirements of VLR 7. Sheet 2: this process communicates with the matching instance of the process PRN_VLR.081 [14]. sheet 5: the procedure CCBS_ICH_VLR_Report_Failure is specific to CCBS.1. Sheet 1: If the MSRN is not allocated. Sheet 3: the procedure CCBS_ICH_Handle_NDUB is specific to CCBS. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23.5. it is specified in 3GPP TS 23. If the VLR does not support CAMEL phase 3 or later.1.2. it is specified in 3GPP TS 23.078 [12]. and there is an association established for the MS between the MSC/VLR and the SGSN. Sheet 2: the test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented. it is specified in 3GPP TS 23. Sheet 3 sheet 6: the procedure CLI_ICH_VLR_Add_CLI is specific to Enhanced CLI Handling. which is linked by the MSRN.093 [23].007 [30]. sheet 3: the procedure CCBS_ICH_Report_Not_Reachable is specific to CCBS. processing continues from the "No" exit of the test "CW available?".2. Sheet 1.

sheet 6: the procedure CCBS_ICH_Handle_UDUB is specific to CCBS. The message is saved for processing after return from the procedure.2.5 Procedure Get_LI_Subscription_Info_MT_VLR The VMSC may abort the transaction with the VLR while a response is awaited from the process CLIP_MAF001 or the process COLR_MAF040. If the GMSC does not support CAMEL Phase 3 or later.2. 7. and the VLR configuration requires paging via the SGSN during VLR restoration. 7. Sheet 8: the procedure Forward_CUG_Check is specific to CUG. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. it is specified in 3GPP TS 23. sheet 6: the procedure CD_Authorization is specific to Call Deflection. The procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later. If the VLR does not support CCBS.078 [12]. Sheet 6: the test "NDUB?" is executed only if the VLR supports CCBS. processing continues from the "Yes" exit of the test "Result=Aborted?".3. processing continues from connector 5. it is specified in 3GPP TS 23.6. it is specified in 3GPP TS 23.0 (2007-06) Sheet 3: the output signal Page MS towards the SGSN includes the Location area identity parameter.093 [23].3 Void Procedure Search_For_MS_VLR The test "Paging via SGSN possible" takes the "yes" exit if: the Gs interface is implemented. If the GMSC does not support CAMEL Phase 3 or later. 3GPP .2.5. The message is saved for processing after return from the procedure. If the VLR does not support Call Deflection.2 7.3. and CAMEL_D_CSI_Check_VLR are specific to CAMEL phase 3 or later.Release 7 209 3GPP TS 23. Sheet 8: the procedures CAMEL_O_CSI_Check_VLR. Sheet 5.2.2.2. processing continues from the "Yes" exit of the test "Result=Call allowed?".2.3.072 [11].6 Procedure Handle_CFB The test "Normal call busy" refers to the value of the indicator returned by the process MAF008.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.3. they are specified in 3GPP TS 23. 7. The output signal Page MS towards the SGSN omits the Location area identity parameter. processing continues from the "Yes" exit of the test "Result = Pass?".2.11. 7.093 [23]. Sheet 3: if the VLR does not support CUG.7 Procedure Handle_CFNRy The test "Normal call" refers to the value of the indicator returned by the process MAF009. It is sent to every SGSN to which the VLR is connected.078 [12]. Sheet 5.2. Sheet 7: the procedure CCBS_ICH_Set_CCBS_Target is specific to CCBS. sheet 6: the procedure CAMEL_CHECK_SII2_CDTI is specific to CAMEL Phase 3 or later.3.018 V7. Sheet 7: the procedure Handle_CFNRc is specified in subclause 7. If the VLR does not support CUG.078 [12]. it is specified in subclause 7. 7. processing continues from the "Yes" exit of the test "Result = Pass?". Sheet 4.3. handling continues from the "No" exit of the test "CUG info present?".2.

0 (2007-06) Process ICH_VLR Process in VLRB to handle a request for information for an incoming (MT) call Idle ICH_VLR1(8) Signals to/from the left are to/from the MSC Release MSRN Send Info For Incoming Call MSRN known? Yes Release MSRN No See TS 23.018 V7.5.Release 7 210 3GPP TS 23.078 MT Roaming Retry supported No Yes GMSC supports MT Roaming Retry Yes set MT Roaming Retry Indicator Send Info For Incoming Call Ack Idle Idle CAMEL_ ICH_VLR Yes Result= Fail? No True See TS 23.093 CCBS_ICH_ Report_Not_ Reachable 1 No Roaming in LA allowed? Send Info For Incoming Call negative response Idle 10 Figure 76a: Process ICH_VLR (sheet 1) 3GPP .007 Set negative response: System Failure CCBS_ICH_VLR_ Report_Failure Subscriber data dormant False IMSI detached? No Yes See TS 23.093 CCBS_ICH_ Set_CCBS_ Call_Indicator Idle No Subscriber data dormant False Set negative response: Unallocated Roaming Number False Data confirmed by HLR True Derive required basic service True See TS 29.

018 V7.Release 7 211 3GPP TS 23. Prepaging supported? Yes True PAR pending False Wait_F or_ P AR_Complet ed No PAR completed True PAR succ ess ful False Call arriv ed True 11 Fatal PAR error False Set negativ e response: Impossible call completion No Locat ion area ID known? Y es No CCB S_ICH _V LR_ Report_F ailure See TS 23.5.093 CCBS_ICH _VLR_ Report_F ailure Idle 2 Wait_F or_ Access_ Request Figure 76b: Process ICH_VLR (sheet 2) 3GPP . Signals to/from the right are to/from the proces s PRN_V LR.0 (2007-06) Process ICH_VLR P roc es s in VLRB to handle a request for information f or an i ncoming (MT) call 10 ICH_VLR2(8) Signals to the lef t are to the VMSC. 093 Yes Send Inf o For Incoming Call negati ve response Set Paging via S GSN possible Paging v ia SGSN possible? Idle Search_For_ MS_VLR Page MS Page type= c ircuit-switched call Yes Result= P ass ? No Yes Result= Fail? No See TS 23.

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.0 (2007-06) 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 7 212 3GPP TS 23.018 V7.093 Release Result Forward 8 5 Figure 76c: Process ICH_VLR (sheet 3) 3GPP .5.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.093 No Yes CCBS_ICH_ Report_Not_ Reachable Wait_For_ Access_ Request See TS 23.

Proc ess Access Request P roc ess _ Access_ Request_V LR No 11 Result= P ass ? Yes CUG info present? No Y es Translate CUG interlock to index A s defined in TS 23.093 Yes Succ ess? Idle CA MEL_CHECK _SII2_C DTI No Yes Result = P ass ? No CFN Ry A &O? Yes Prov ide NRCT value No 3 Get_LI_ Subsc ription_ Info_MT_V LR Get _AoC_ Subsc ription_ Info_VLR Set negativ e response: S ystem fai lure See TS 23.081 CLI_ICH_VLR_ A dd_CLI CCB S_ICH _VLR_ Report_F ailure S ee TS 23.5.093 Complete Call Send Inf o For Incoming Call negati ve response Wait_F or_ Complete_Call_ Result Idle Figure 76d: Process ICH_VLR (sheet 4) 3GPP .085 CCBS_IC H_V LR_ Report_F ailure See TS 23.0 (2007-06) Process ICH_VLR P roc es s in VLRB to handle a request for inf ormation f or an i ncoming (MT) call Wait_F or_ Access_ Request ICH_VLR4(8) S ignals to/from the left are to/from the VMSC.018 V7.Release 7 213 3GPP TS 23.

Complete Call ack Abort Complete Call negati ve response Yes Idle Busy subscriber ? No See TS 23.072 CD_ Authorization See TS 23.093 Yes Absent subscriber ? No CCB S_ICH_ Handle_UDUB Yes Radio conges tion? No No subscriber reply ? No Yes See TS 23.018 V7.093 CCBS_IC H_VLR_ Report_F ailure No Result= Aborted? Y es No Result= Fail? Y es Set negativ e response: Impossible call completion 6 1 5 Send Info For Incoming Call negati ve response 7 Idle Figure 76e: Process ICH_VLR (sheet 5) 3GPP .Release 7 214 3GPP TS 23.5.0 (2007-06) Process ICH_VLR P roc es s in VLRB to handle a request for information f or an i ncoming (MT) call Wait_for_ Complet e_Call Result ICH_VLR5(8) Signals to/f rom the left are to/from the VMS C.

072 CD_ A uthorization 9 No Result= Aborted? Yes No Result= Fail? Set negativ e response: Impossible call completion Yes CCB S_ICH _ Handle_UDUB See TS 23. 093 Send Info For Incoming Call negati ve response 7 Idle 6 5 Figure 76f: Process ICH_VLR (sheet 6) 3GPP .0 (2007-06) Process ICH_VLR P roc es s in VLRB to handle a request for information f or an i ncoming (MT) call 4 ICH_VLR6(8) Signals to/f rom the left are to/from the VMS C.5.078 Yez Result = Pass ? No No CFN Ry A &O ? Y ea Set NRCT CLI_ICH_V LR_ Add_CLI See TS 23.018 V7.081 Proc ess Call Waiting Wait_F or_ P CW_Result Proc ess Call Waiting ack Abort Proc ess Call W aiting negativ e response Yes Idle B usy subscriber ? No No subscriber reply ? No Y es NDUB? Yes No See TS 23. CAMEL_CHE CK _SII2_C DTI See TS 23.Release 7 215 3GPP TS 23.

5.Release 7 216 3GPP TS 23.093 S end Info For Incoming Call negati ve response 7 Idle 7 Figure 76g: Process ICH_VLR (sheet 7) 3GPP .093 No Result= Forward? S et negativ e response: No Subsc riber Reply Yes Set negativ e response: Busy S ubsc riber CCBS_ICH _ S et_CCBS _ Target See TS 23.018 V7.0 (2007-06) Process ICH_VLR P roc es s in VLRB to handle a request for information f or an i ncoming (MT) call Signals to the left are to the VMSC 1 ICH_VLR7(8) Handle_CFNRc 5 Y es Result= Fail? Handle_CFB S et negativ e response: Forwarding Violation Yes Result= Fail? No Set negativ e response: Forwarding Violation No Yes Set negativ e response: Absent S ubsc riber No Result= Forward? 7 6 8 Handle_CFNRy No Result= Forward? Yes CCBS_ICH _ Set _CCBS_ Target Set negativ e response: Forwarding Violation Y es Result= Fail? No S ee TS 23.

ICH_VLR8(8) Forward_ CUG_Check Result= Call allowed? Yes No Set result: Forward Set negative response: CUG rejec t Set forwarding information CAMEL_ O_C SI_ CHECK_V LR See TS 23.Release 7 217 3GPP TS 23.0 (2007-06) Process ICH_VLR P roc es s in VLRB to handle a request for information f or an i ncoming (MT) call 7 Signals to the left are to the VMSC.5.018 V7.078 Send Info For Incoming Call ack Send Info For Incoming Call negati ve response Idle Idle Figure 76h: Process ICH_VLR (sheet 8) Figure 77: Void 3GPP .078 CAMEL_ D_CSI_ CHECK_V LR See TS 23.

Release 7 218 3GPP TS 23. page in all location areas) Signals to/from the left are to/fro m the MS C SRCH_V1(1) No Pagin g via SGSN possible? Yes S et paging via SGSN possible Search For MS Pa ge type= Circuit-switched call W ait_Fo r_ S earch_Result Search For MS ack S earch For MS n egative response Abort Search f or MS via S GSN Up date Location Are a ID To SGS N Page MS Result:= Pass Resu lt:= Fail Result: = Aborted Wait_For_ Search _Result Figure 78: Procedure Search_For_MS_VLR 3GPP .5.0 (2007-06) Procedure Search_For_MS_VLR Procedure in t he VLR to search for an MS (i.e.018 V7.

Release 7 219 3GPP TS 23.018 V7.5.0 (2007-06) Procedure Get_CW_Subscription_Info_VLR Procedure in t he VLR to retrieve subscription inform ation for th e Call W aiting service Signals to/from the right are to/fro m the process MAF013 CWI_VLR1(1) initiate handling of CW W ait_For_ CW _Info From MS C Abort process call waiting Figure 79: Procedure Get_CW_Subscription_Info_VLR 3GPP .

Release 7 220 3GPP TS 23.018 V7.0 (2007-06) Procedure Get_LI_Subscription_Info_MT_VLR Procedure in t he 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 W ait_For_ CLIP_Info From MS C Abort Continue call handling From process CLIP _MAF001 Initiate handling of COLR To process COLR_MAF040 W ait_For_ COLR_Info From MS C Abort Continue call handling From process COLR_MAF040 Figure 80: Procedure Get_LI_Subscription_Info_MT_VLR 3GPP .5.

Release 7 221 3GPP TS 23.078 No Result = Pass ? Y es initiate handling of CFB Wait_F or_ CFB_Res ult continue call handling Y es Error? No Normal call busy? No Yes Result:= Fail Result:= Forward Result:= B usy Figure 81: Procedure Handle_CFB 3GPP .5.018 V7.0 (2007-06) Procedure Handle_CFB P roc edure in the V LR t o handle Call Forwarding on Bus y H_CFB1(1) Signals to/from the right are to/from the process MAF008 CAMEL_CHE CL _SII2_C DTI See TS 23.

Release 7 222 3GPP TS 23.0 (2007-06) Procedure Handle_CFNRy Procedure in t he VLR to handle Call Forwarding on No subscriber Reply Signals to/from the right are to/fro m the process MAF009 H_CFNRy1(1) initiate handling of CFNRy W ait_For_ CFNRy_Result continue call handling Yes E rror? No Normal call? Yes Result:= Fail Result:= No re ply No Result:= Forward Figure 82: Procedure Handle_CFNRy 3GPP .018 V7.5.

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

1.5.Release 7 224 3GPP TS 23. 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 .4.2 7.018 V7.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.1.1.1.1.0 (2007-06) 7.4.4.1.1.1.1 7.4.3 7.

5.Release 7 225 3GPP TS 23.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.018 V7. 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 .

018 V7. Non_Speech 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 . Non_Speech Increment_ Call_Counter Non_Speech Decrement_ Call_Counter Speech. 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.Release 7 226 3GPP TS 23.5.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

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 7 227 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 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.5.018 V7.

5.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.1 Non_Speech_Call_Cnt .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 .Release 7 228 3GPP TS 23. 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 V7.

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 .Release 7 229 3GPP TS 23.018 V7.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.5.

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 . 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.5. Call_Held_ Call_Active SFSM7(18) Signals to/from the left are to/from either process OCH_MSC or process ICH_MSC.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.Release 7 230 3GPP TS 23.083 Call_Held_ Call_Active Call_Held_Call_ Active_Data_Call Setup_Pending Retr_req.018 V7.

5.018 V7.084 Handle_ MPTY MPTY reject ECT reject Handle_ECT_ Active See TS 23.Release 7 231 3GPP TS 23.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis. 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.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 .

0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis. 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 .018 V7.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 .Release 7 232 3GPP TS 23.5.

5.018 V7.Release 7 233 3GPP TS 23.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis. 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 Non-speech call ongoing? Yes 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 .

Call_Held_ Setup_Pending SFSM11(18) Signals to/from the left are to/fro m either process OCH _MSC or process ICH_MSC Call setup faile d 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 V7. Non_Sp eech 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_Ca llA:=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 .Release 7 234 3GPP TS 23.5.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

Release 7 235 3GPP TS 23.5.018 V7. 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.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 .0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.5.Release 7 236 3GPP TS 23.018 V7.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. 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.

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 .Release 7 237 3GPP TS 23.1 Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt .018 V7.1 Speech_Call_Cnt:= 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 .5.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.018 V7.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 . 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 .Release 7 238 3GPP TS 23.5.

Release 7 239 3GPP TS 23.018 V7.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis. 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 .5.

018 V7.Release 7 240 3GPP TS 23. 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 .5.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.

Release 7 241 3GPP TS 23.018 V7.0 (2007-06) Process Subs_FSM Process in the serving MSC to control the call states on a per subscriber basis.5. 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 .018 V7.5.0 (2007-06) 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 7 242 3GPP TS 23.

Release 7 243 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 .018 V7.5.0 (2007-06) 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.

018 V7.Release 7 244 3GPP TS 23.5.0 (2007-06) Macrodefinition Increment_Call_Counter Macro to increment the correct counter depedning on the type of the current call. 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 .

5. Inc_Call_Cnt1(1) No Speech call? Yes Non_Speech_Call_Cnt:= Non_Speech_Call_Cnt .018 V7.0 (2007-06) Macrodefinition Decrement_Call_Counter Macro to decrement the correct counter depedning on the type of the current call.1 Speech_Call_Cnt:= Speech_Call_Cnt .1 Non_ Speech Speech Figure 88: Macro Decrement_Call_Counter 3GPP .Release 7 245 3GPP TS 23.

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 1. processing continues from the "Pass" exit of the test "Result?". processing continues from the "Pass" exit of the test "Result?". Sheet 1. it is specified in 3GPP TS 23. Sheet 2: “Number_of_Digits” is the Collected_Info specific reporting criterion.078 [12]. Sheet 1. Sheet 5: the input signal TNRy expired and all the subsequent processing are specific to CAMEL phase 2 or later. The process CS_gsmSSF sends the parameter to the TO_MSC process.078 [12]. If the GMSC does not support CAMEL phase 4 or later. it is specified in 3GPP TS 23. sheet 2: The variable “Return_Place” indicates at which detection point the additional digit collection is. sheet 4: the procedure CAMEL_TOC_Dialled_Services is specific to CAMEL phase 3 or later. sheet 3: the procedure CAMEL_Store_Destination_Address is specific to CAMEL phase 3 or later. Sheet 1: the procedure MOBILE_NUMBER_PORTABILITY_IN_OQoD is specific to Mobile Number Portability. sheet 4: the procedure CAMEL_OCH_MSC_DISC3 is specific to CAMEL phase 1.078 [12].Release 7 246 3GPP TS 23. processing continues from the "Pass" exit of the test "Result?". sheet 4: the procedure CAMEL_OCH_MSC_DISC4 is specific to CAMEL Phase 2 or later. Sheet 3: the procedure CAMEL_CF_MSC_ANSWER is specific to CAMEL.5.018 V7. sheet 2: The “inter-digit timer” is a MSC internal timer to wait for additional dialling from the incoming side.5.5.078 [12].087 [20]. it is specified 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. Sheet 1.078 [12].066 [10].5 TO call 7. Sheet 3: the procedure CAMEL_CF_MSC_ALERTING is specific to CAMEL phase 4 or later. The gsmSCF specifies the criterion.078 [12]. Sheet 2: “ST digit” is the ISUP value for a digit indicating that the Called Party Number is complete. If the MSC does not support CAMEL. 3GPP . it is specified in 3GPP TS 23. Sheet 3: the procedures CAMEL_Start_TNRy and CAMEL_Stop TNRy are specific to CAMEL phase 2 or later.1.1 Functional requirements of inter-connecting MSC 7. they are specified in 3GPP TS 23. processing continues from the "Pass" exit of the test "Result=?". it is specified in 3GPP TS 23. Sheet 3: the procedure UUS_MSC_Clear_UUS is specific to UUS. Sheet 1.0 (2007-06) 7. If the MSC does not support CAMEL trunk triggering. The procedure CAMEL_OCH_MSC2 is specified in 3GPP TS 23. the MSC/gsmSSF may report digits to the gsmSCF (if the event detection point is armed). and will occur only if the GMSC supports CAMEL phase 2 or later. sheet 2. it is specified in 3GPP TS 23. This timer is used for the SDL modelling purposes only and it may not present the actual implementations.078 [12].078 [12].078 [12]. Sheet 1. Sheet 1. sheet 7: the procedure CAMEL_MT_CF_LEG1_MSC is specific to CAMEL phase 4 or later. it is specified in 3GPP TS 23.078 [12]. The procedure call formal parameter “First” or “NotFirst” indicates whether the procedure was called earlier in the same call. sheet2. Sheet 4: the procedure CAMEL_Stop_TNRy is specific to CAMEL phase 2 or later. it is specified in 3GPP TS 23.1 Process TO_MSC Sheet 1: the procedure CAMEL_TOC_INIT is specific to CAMEL. it is specified in 3GPP TS 23. If the MSC does not support CAMEL. At the expiry of the timer.078 [12]. it is specifed 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. it is specified in 3GPP TS 23.018 V7. If the MSC does not support CAMEL. it is specified in 3GPP TS 23. processing continues from the "No" exit of the test "Result=Reconnect?" .Release 7 247 3GPP TS 23. Sheet 6: the procedure CAMEL_OCH_MSC_DISC2 is specific to CAMEL.078 [12].5. it is specified in 3GPP TS 23. If the MSC does not support CAMEL.0 (2007-06) Sheet 6: the procedure CAMEL_OCH_MSC_DISC1 is specific to CAMEL. Sheet 7: the process CAMEL_MT_CF_LEG2_MSC is specific to CAMEL phase 4 or later. processing continues from the "No" exit of the test "Result=CAMEL handling?". 3GPP . Sheet 6: after the process TO_MSC has sent an IAM to the forwarded-to exchange. it acts as a relay for messages received from the parent process and the forwarded-to exchange.078 [12].078 [12].

078 Wait_For_ ACM Wait_For_SAM Idle Figure 7. False) MSC_Coord_ setup Return_Place := DialledServices More_Digits Start Inter_Digit_timer 2 Release See TS 23. Initial Address CAMEL_TOC_ MSC_INIT (First) See 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.5.066 MOBILE_NUMBER_ PORTABILITY_ IN_OQoD CAMEL_Store_ Destination_ Address (False.078 Return_Place := Init Fail See TS 23.078 B 4 Leg1 Result? Pass The duration is a MSC specific and/or interface specific value See TS 23. Idle TOMSC1(7) Signals to/from the left are to/from the originating switch.5.078 CAMEL_ OCH_MSC1 No Result= Reconnect? Yes Wait_For_SAM Idle 1 Pass See TS 23.1a: Process TO_MSC (sheet 1) 3GPP .018 V7.0 (2007-06) Process TO_MSC Process in the MSC to handle trunk originated call.Release 7 248 3GPP TS 23.

5.0 (2007-06) Process TO_MSC Process in the MSC to handle trunk originated call.Release 7 249 3GPP TS 23.1b: Process TO_MSC (sheet 2) 3GPP . There may be ve ndor specic differences in this issue . sig nals to/fro m the right are to/from the destina tion exchange or MT_GMSC or ICH_MSC process depending on th e called nu mbe r.078 Yes CAMEL_Store_ Destination_ Address (False . Once timer expires. False) Wait_For_SAM Dig its are waited based on timer for modelling purposes.018 V7. new digits are reported to gsmSCF. Wait_For_SAM TOMSC2(7) Signals to/from the left are to/from the originating switch.078 CAMEL_TOC_ MSC_ INIT (NotFirst) CAMEL_TOC_ Dialled_Services (NotFirst) See TS 23.5.078 B C Figure 7. Retu rn_Place? Dialled_Services Init See TS 23. Inte r_Digit_timer from SELF SAM Stop Inter_Digit_timer (Dialled number length >= Number_of_Digits) OR (ST digit re ceived) No Start Inter_Digit_timer See TS 23.

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

078 Release Release Release 2 Release Release call resources Idle Figure 7. 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.Release 7 251 3GPP TS 23.0 (2007-06) Process TO_MSC Process in the MSC to handle trunk originated call.018 V7. Wait_For_Answer TOMSC4(7) Signals to/from the left are to/from the originating s witch. Wait_For_ACM.1d: Process TO_MSC (sheet 4) 3GPP . signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number.078 Result= Reconnect? Yes CAMEL_ Stop_TNRy See TS 23.5.5.

0 (2007-06) Process TO_MSC Process in the MSC to handle trunk originated call.078 2 Release Result? Fail Reconnect Release See TS 23.5. signals to/from the r ight are to/from the destination exch an ge or MT_GMSC or ICH_MSC process depending on the called number.5. TNRy expired Inte rnal 3 Release CAMEL_OCH_ MSC2 See TS 23.Release 7 252 3GPP TS 23.1e: Process TO_MSC (sheet 5) 3GPP .078 CAMEL_ TOC_ Dialled_Services (First) Abort Result? Fail Pass Release call resources See TS 23.078 CAMEL_ OCH_MSC1 1 Idle Result= Yes Reconnect? No Re lea se 2 Idle Figure 7. Wait_For _ Answe r TOMSC5(7) Signals to/from the left are to/from the originating switch .018 V7.

078 CAMEL_OCH_ MSC_DISC2 Result= Yes CAMEL Handling? No Result= Yes Reconnect? No See TS 23.018 V7.1f: Process TO_MSC (sheet 6) 3GPP . signals to/from the right are to/from the destination exchange or MT_GMSC or ICH_MSC process depending on the called number. Int_ReleaseCall From gsmSSF Release Release CAMEL_OCH_ MSC_DISC1 Result= CAMEL Handling? No See TS 23.5.Release 7 253 3GPP TS 23.0 (2007-06) Process TO_MSC Process in the MSC to handle trunk originated call.5.078 Release Yes Release Release 2 Release Release call resources Idle * * * - - - Figure 7. Wait_For_ Clear TOMSC6(7) Signals to/from the left are to/from the originating switch.

Authentication Failure Report.5.Release 7 254 3GPP TS 23. 3GPP . See TS 23.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".078 Leg1_status := Active Wait_For_ Clear CAMEL_TOC_ LEG1_MSC (Leg1_status) Idle Figure 7.5. except for the following messages. A TOMSC7(7) CAMEL phase 4 or la ter control relationship exists? Yes See TS 23. Activate Trace Mode.1g: Process TO_MSC (sheet 7) 8 Contents of messages This clause specifies the content of each message shown in clauses 5 and 7.0 (2007-06) Process TO_MSC Process in the MSC to handle trunk originated call.018 V7. which are not specific to call handling: On the D interface (VLR-HLR): Abort.

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. Send Authentication Info negative response. at the discretion of the application at the sending entity.1 Abort The following information element is required: Information element name Abort reason Required M Description Indicates the reason for the procedure being aborted. but mandatory in the derived specification. Send Authentication Info ack. If the information element is shown as conditional or optional in this clause. it shall be present even if the conditions in this clause do not require it to be present. Some messages which are defined in this clause are used for other services or features. 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.Release 7 255 3GPP TS 23. - 8.1. conditional (C) or optional (O).102 [32]) Authentication token to be sent to the MS (3GPP TS 33. An optional element may be present or absent.1.1 Messages on the B interface (MSC-VLR) 8. In the tables which follow. then the following principles apply: If the information element is shown as mandatory 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. it shall always be present in the context of the service or feature defined in the derived specification.018 V7. in this case the requirements for the presence of each information element are as defined in this clause. A mandatory information element shall always be present. the requirements for the presence of the additional information elements are specified in the relevant specification.5. 8. If the information element is shown as conditional or optional in this clause. and the conditions in the derived specification require the information element to be present. Send Authentication Info. if those conditions are not fulfilled it shall be absent. If the specification for a service or feature requires information elements in a message additional to those specified in this clause. it shall always be present. A conditional information element shall be present if certain conditions are fulfilled. information elements are shown as mandatory (M).102 [32]) 3GPP .0 (2007-06) - Insert Subscriber Data.

020 [1]) 8.5.1.020 [1]) 8.1. 8.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. 8.1.1. Unknown equipment.020 [1]) Cipher key sequence number to be sent to the MS (3GPP TS 43. 3GPP . 8.5 Call arrived This message contains no information elements.6 Check IMEI This message contains no information elements.1.Release 7 256 3GPP TS 23.018 V7.1. grey-listed or white-listed 8.4 Authenticate negative response The negative response information element can take the following value: -wrong network signature.0 (2007-06) 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.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.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.8 Check IMEI negative response The negative response information element can take the following values: System failure.

see 3GPP TS 23. temporary (default presentation allowed) or temporary (default presentation restricted). Indicates that the COLR override subscription option of COLP is provisioned. shall be present for an MT call if the call is a CUG call. Shall be present for an ordinary MO call.018 V7.085 [18]. Shall be present for an ordinary MO call and for an emergency call when the MS is registered in the VLR. For the definition of this IE. otherwise shall be absent. otherwise shall be absent. see 3GPP TS 23. Shall be present for an MT call according to the rules defined in 3GPP TS 29.085 [18]. Shall be present for an MT call if the Call Forwarding on No Reply service is active and operative. Category of the MS for which the Complete Call is sent. otherwise shall be absent. otherwise shall be absent. For the definition of this IE. Indicates that COLP is provisioned. for an MT call and for an emergency call when the MS is registered in the VLR. Shall be present for an ordinary MO call if the call is a CUG call with outgoing access. 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. 3GPP .Release 7 257 3GPP TS 23. otherwise shall be absent. Shall be present for an MO call if COLP is provisioned with the COLR override subscription option and the MS is registered in the HPLMN country. 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 emergency call when the mobile is identified only by its IMEI. otherwise shall be absent. IMEI of the mobile for which the Complete Call is sent. 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 it was received in the Provide Roaming Number.0 (2007-06) 8. Shall be present for an ordinary MO call if the call is a CUG call. Shall be present for an MO call if COLP is provisioned. Value of timer to be used to determine the No subscriber reply condition. Indicates that COLR is provisioned. Shall be present for an MT call if it was received in the Provide Roaming Number. Shall be present for an ordinary MO call or an MT call if Advice of Charge is provisioned. otherwise shall be absent. Shall be present for an MT call if COLR is provisioned. otherwise shall be absent. otherwise shall be absent. Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. For the definition of this IE. Shall be present for an MO call if CLIR is provisioned. otherwise shall be absent. otherwise shall be absent. Shall be present for an MT call if CLIP is provisioned.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 the CLIR override subscription option of CLIP is provisioned. Shall be present for an MO call if CLIR is provisioned.1. otherwise shall be absent. Indicates that CLIR is provisioned.085 [18]. Indicates that CLIP is provisioned.007 [30]. Shall be present for an MT call if it was received in the Provide Roaming Number. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. Indicates the mode in which CLIR is provisioned: permanent. see 3GPP TS 23.5.

8.1.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. Radio congestion.0 (2007-06) 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. 8.1.10 Complete Call ack This message contains no information elements. Indicates that the VLR requires state information for the MS.5.1. otherwise shall be absent. Busy subscriber.13 Forward New TMSI ack This message contains no information elements. This parameter may be included at the discretion of the VLR operator.1. 8.16 Obtain Subscriber Info ack The following information elements are required: 3GPP . Shall be present if state information is required. No subscriber reply.1.11 Complete Call negative response The negative response information element can take the following values: Absent subscriber.1.Release 7 258 3GPP TS 23.1.12 Forward New TMSI The following information element is required: Information element name TMSI Required M Description TMSI to be sent to the MS. 8. 8. 8.14 Forward New TMSI negative response The negative response information element can take the following value: TMSI reallocation failure.018 V7. 8.

3GPP . otherwise shall be absent. Busy subscriber (NDUB). Service area identity of the cell in which the served subscriber is located. otherwise shall be absent. otherwise shall be absent.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 C O Description IMSI of the MS to be paged.e.Location. SS activity or Active Location Retrieval. Shall be present if the VLR determines that the MS can be paged via the SGSN. otherwise shall be absent.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. Shall be present if the VLR requested state information. 8.Release 7 259 3GPP TS 23. IMEISV as defined in 3GPP TS 23.008 [26].1. System failure. . Indicates whether the paging is for a circuit-switched call. TMSI to be broadcast to identify the MS. Shall be present if the MS uses GSM radio access. . otherwise shall be absent. 8.1. Indicates that paging via the SGSN is possible. Shall be present if the MS uses UMTS radio access. Unknown location area ID. 8. otherwise shall be absent. MS classmark 2 as defined in 3GPP TS 24. Location area in which the MS is to be paged.MS classmark. Busy subscriber (More calls possible). Identity of the cell in which the served subscriber is located. Shall be present if the IMEI was requested in the Page MS message and the MSC retrieved it from the MS. Indicates the information requested by the VLR – one or more of: .018 V7.IMEI.5.1.0 (2007-06) Information element name Subscriber state Required C Description Indicates whether the MS is busy (i. engaged on a circuitswitched call) or assumed idle. MT SMS delivery.19 Page MS negative response The negative response information element can take the following values: Absent subscriber. Shall be present if the Page type is Active Information Retrieval.003 [5].

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

MSISDN of the MS requesting the access. For emergency call.1. 8. 8. one of IMSI or IMEI shall be present. Illegal subscriber.0 (2007-06) Information element name IMSI IMEI MSISDN Required C C O Description IMSI of the MS requesting the access. otherwise shall be absent. Shall be present according to the rules defined in 3GPP TS 29.1. otherwise shall be absent. see 3GPP TS 23. otherwise shall be absent. Shall be present if COLR is provisioned. Indicates whether Advice of Charge (Information) or Advice of Charge (Charging) is provisioned. Shall be present if CLIP is provisioned with the CLIR override subscription option and the MS is registered in the HPLMN country. 8. Shall be present if it was received in the Provide Roaming Number for the waiting call.5. one of IMSI or IMEI shall be present. otherwise shall be absent.23 Process Access Request negative response The negative response information element can take the following values: Roaming not allowed. otherwise shall be absent. shall be present. Shall be present if CLIP is provisioned.Release 7 261 3GPP TS 23. Shall be present if the Call Forwarding on No Reply service is active and operative.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. Shall be present if the waiting call is a CUG call. For emergency call. otherwise shall be absent.1. otherwise shall be absent. For normal MO call or page response. otherwise shall be absent. Unidentified subscriber. 3GPP . Indicates that CLIP is provisioned. System failure.085 [18]. For normal MO call or page response. Shall be present if Advice of Charge is provisioned. shall be absent. Indicates that the CLIR override subscription option of CLIP is provisioned. otherwise shall be absent.018 V7. Indicates that COLR is provisioned. For the definition of this IE. Shall be present if it was received in the Provide Roaming Number for the waiting call.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. IMEI of the MS requesting the access.007 [30]. Illegal equipment. Value of timer to be used to determine the No subscriber reply condition.

31 Radio connection released This message contains no information elements.1. Busy subscriber (NDUB). 8.018 V7.0 (2007-06) 8. 8.1.5.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.1.1. 8.32 Search For MS The following information elements are required: 3GPP . No subscriber reply.1.29 Provide IMSI This message contains no information elements.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. 8.1.26 Process Call Waiting negative response The negative response information element can take the following values: Busy subscriber (UDUB).Release 7 262 3GPP TS 23.003 [5]) of the ME involved in the access request.27 Provide IMEI This message contains no information elements. 8. 8.

34 Search For MS negative response The negative response information element can take the following values: Absent subscriber.0 (2007-06) Information element name IMSI Page type Requested information Required M M C Paging via SGSN possible TMSI C O Description IMSI of the MS to be paged in all location areas. 8. Indicates that paging via the SGSN is possible. otherwise shall be absent.003 [5]. 8. Shall be present if the VLR determines that the MS can be paged via the SGSN. The Search For MS negative response Busy subscriber (More calls possible) also indicates the basic service which applies for the established call. Shall be present if the IMEI was requested in the Page MS message and the MSC retrieved it from the MS. Shall be present if the MS uses UMTS radio access.1. Indicates the information requested by the VLR – one or more of: .Location.MS classmark. IMEISV as defined in 3GPP TS 23. Shall be present if the Page type is Active Information Retrieval. . . otherwise shall be absent. otherwise shall be absent.IMEI.35 Search for MS via SGSN The following information elements are required: 3GPP . otherwise shall be absent. MS classmark 2 as defined in 3GPP TS 24. otherwise shall be absent.018 V7. Busy subscriber (NDUB). Shall be present if the MS uses GSM radio access. Busy subscriber (More calls possible). TMSI to be broadcast to identify the MS. Identity of the cell in which the served subscriber is located.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.1.1. MT SMS delivery. Indicates whether the paging is for a circuit-switched call.008 [26].5. Service area identity of the cell in which the served subscriber is located. 8. System failure.Release 7 263 3GPP TS 23. SS activity or Active Location Retrieval.

For the definition of this IE. Number of times the incoming call has already been forwarded. otherwise shall be absent.0 (2007-06) Information element name IMSI eMLPP priority TMSI Channel type Required M O O O Description IMSI of the MS to be paged. Shall be present if it was received in the IAM. Bearer service required for the MT call.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.085 [18].085 [18]. Shall be present if it was received in the IAM. Shall be present if the MSC was able to derive a bearer service from ISDN BC/LLC/HLC information received in the IAM. see 3GPP TS 23. Teleservice required for the MT call. For the definition of this IE. otherwise shall be absent. Type of channel required for the call.1. otherwise shall be absent.5. Shall be present if it was received in the IAM. TMSI to be broadcast to identify the MS. Number dialled by the calling subscriber.018 V7. otherwise shall be absent. otherwise shall be absent. Shall be present if it was received in the IAM. Shall be present if the MSC was able to derive a teleservice from ISDN BC/LLC/HLC information received in the IAM.Release 7 264 3GPP TS 23. 8. Circuit-switched paging priority. see 3GPP TS 23. otherwise shall be absent. 3GPP .

It will be used to create the redirecting number presented to the C subscriber. Shall be present if the call is to be forwarded on mobile subscriber busy or on no subscriber reply. Indication of why the call has been forwarded (on call deflection. E. No subscriber reply.Release 7 265 3GPP TS 23. otherwise shall be absent. Forwarding violation.0 (2007-06) 8.164 number which identifies the B subscriber. otherwise shall be absent. Impossible call completion. otherwise shall be absent. otherwise shall be absent.085 [18]. 3GPP . Shall be present if a forwarded-to subaddress is stored in the VLR in association with the forwarded-to number. Shall be present if the call is to be forwarded. 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. Unallocated roaming number. Indication that the call is forwarded for MT roaming retry. Busy subscriber. Shall be present if the call is to be forwarded. 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. Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber.085 [18]. Shall be present if the call is to be forwarded other than for MT roaming retry reason. Indication of whether the forwarding party is to be notified that the call has been forwarded. see 3GPP TS 23. For the definition of this IE. otherwise shall be absent. on mobile subscriber busy.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. This parameter may be included at the discretion of the VLR operator. 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. otherwise shall be absent. 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. System failure.164 number of the C subscriber. For the definition of this IE. Subaddress of the C subscriber (see 3GPP TS 23.003 [5]).1.085 [18]. E. see 3GPP TS 23.38 Send Info For Incoming Call negative response The negative response information element can take the following values: Absent subscriber.018 V7.085 [18]. Indication of whether the calling party is to be notified that the call has been forwarded. on mobile subscriber not reachable or on no subscriber reply).5. Shall be present if the call is to be forwarded other than for MT roaming retry reason. 8. CUG reject (Called party SS interaction violation).1.

see 3GPP TS 23.1. Shall be present if it was received in the set-up request from the MS. Call barred (Supplementary service barring). For the definition of this IE.085 [18].003 [5].5.1. see 3GPP TS 23. For the definition of this IE. For the definition of this IE.Release 7 266 3GPP TS 23.085 [18]. Bearer service required for the MO call.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. Teleservice required for the MO call. CUG reject (Unknown CUG index). CUG reject (Inconsistent access information .164 number of the call destination.index incompatible with basic service). One of bearer service or teleservice shall be present.40 Send Info For Outgoing Call negative response The negative response information element can take the following values: Bearer service not provisioned. CUG reject (Inconsistent access information . One of bearer service or teleservice shall be present. 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. 8. CUG reject (Outgoing calls barred within the CUG). see 3GPP TS 23. Shall be present if it was received in the set-up request from the MS. 8. Call barred (Operator determined barring). Teleservice not provisioned. Shall be present if it was received in the set-up request from the MS.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.0 (2007-06) 8.no CUG selected).085 [18].1.1. 8. derived from the PLMN bearer capability information received in the set-up request from the MS.018 V7.

1.018 V7. 8.2 Messages on the C interface (MSC-HLR) 8. otherwise shall be absent. 8.102 [32]).1.102 [32]).008 [3] 8.1. and if so which ciphering algorithm is to be used. 8.Release 7 267 3GPP TS 23. Shall be present if the ciphering mode indicates that ciphering of the radio connection is required.0 (2007-06) 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. Ciphering key to be used if ciphering of the radio connection is required. Integrity key to be used to verify the integrity of messages transferred over the radio link (see 3GPP TS 33.43 Use existing TMSI This message contains no information elements.1 Send Routeing Info The following information elements are required: 3GPP .2. see 3GPP TS 52.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.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. 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.5.

For the definition of this IE. see 3GPP TS 23. Number of times the incoming call has already been forwarded. otherwise shall be absent. otherwise shall be absent. Shall be present if the GMSC received it in the IAM and the GMSC supports CUG. ISDN higher layer compatibility. Shall be present if the GMSC received it in the IAM. otherwise shall be absent.0 (2007-06) Information element name MSISDN Alerting Pattern CUG interlock CUG outgoing access Number of forwarding ISDN BC ISDN LLC ISDN HLC Pre-paging supported Required M C C C C C C C C Description MSISDN of the B subscriber (see 3GPP TS 23. 3GPP . For the definition of this IE. otherwise shall be absent. ISDN lower layer compatibility. otherwise shall be absent. Shall be present if the GMSC supports pre-paging. Shall be present if it was received in the IAM.003 [5]). Shall be present if received in a Connect operation from the gsmSCF. otherwise shall be absent. Shall be present if the GMSC received it in the IAM and the GMSC supports CUG. Shall be present if the GMSC received it in the IAM. otherwise shall be absent. ISDN bearer capability.5.085 [18]. Shall be present if the GMSC received it in the IAM.Release 7 268 3GPP TS 23. otherwise shall be absent. see 3GPP TS 23.085 [18].018 V7.

Shall be present if the HLR has determined that the call is to be forwarded.003 [5]). For the definition of this IE. It will be used to create the redirecting number presented to the C subscriber. This parameter may be included at the discretion of the HLR operator.085 [18].2. otherwise shall be absent. E. E. otherwise shall be absent. Bearer service not provisioned. see 3GPP TS 23.164 number required to route the call to VMSCB (see 3GPP TS 23.018 V7.164 number which identifies the B subscriber (basic MSISDN).003 [5]). CUG reject (Incoming calls barred within CUG). 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. Call barred (Supplementary service barring).Release 7 269 3GPP TS 23.085 [18].0 (2007-06) 8. Indication of why the call has been forwarded (unconditionally or on mobile subscriber not reachable). Shall be present if the HLR has determined that the call is to be forwarded 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. 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. 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.5.003 [5]). Shall be present if the HLR has determined that the call is to be forwarded. 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. otherwise shall be absent. otherwise shall be absent. otherwise shall be absent. For the definition of this IE. Shall be present if the HLR has determined that the call is to be forwarded.164 number of the C subscriber. The preferred carrier identity identifying the carrier to be used to route the interexchange call if the call requires routing via an interexchange carrier. Call barred (Operator determined barring).085 [18]. 8. Subaddress of the C subscriber (see 3GPP TS 23.2. 3GPP . otherwise shall be absent. CUG reject (Called party SS interaction violation).085 [18]. CUG reject (Requested basic service violates CUG constraints). Indication of whether the MSISDN of B subscriber shall be presented to the C subscriber. otherwise shall be absent.3 - Send Routeing Info negative response The negative response information element can take the following values: Absent subscriber. see 3GPP TS 23. E. Indication of whether the calling party is to be notified that the call has been forwarded. otherwise shall be absent.

Forwarding violation Number changed. May be present if the HLR can determine the required PLMN bearer capability from ISDN compatibility information received in the Send Routeing Info message. Shall be present if the HLR has determined that pre-paging is supported in the GMSC and the HLR.003 [5]). If the PLMN bearer capability IE is present.007 [30]. If the PLMN bearer capability IE is present. the ISDN LLC IE shall be absent. Teleservice not provisioned. Local Mobile Subscriber Identity. E. ISDN bearer capability. It may be present if the HLR requires it to be included in the call data record.018 V7.3. For alternate speech/facsimile group 3 calls this information element shall contain one PLMN bearer capability. the subscriber has VT-CSI stored in HLR. 8. otherwise shall be absent.3 Messages on the D interface (VLR-HLR) 8. otherwise shall be absent. Facility not supported. the PLMN bearer capability IE shall be absent.5. otherwise shall be absent. Data missing. or from the MSISDN if a multi-numbering scheme is used. May be present if the HLR received it in the Send Routeing Info message.003 [5]).164 number which identifies VMSCB (see 3GPP TS 23.164 number which identifies the B subscriber. the ISDN BC IE shall be absent. If the ISDN BC and ISDN LLC IEs are present. Unknown subscriber. the MSISDN is different from the basic MSISDN. otherwise shall be absent. System Failure. May be present if the HLR received it in the Send Routeing Info message. E. 3. Unexpected data value.0 (2007-06) - CUG reject (Subscriber not member of CUG). 2. Information to define the PLMN bearer capability required for the call. ISDN lower layer compatibility. Shall be present if the HLR received it in the Send Routeing Info message. It shall be present if the following 3 conditions are all satisfied: 1. ISDN higher layer compatibility.Release 7 270 3GPP TS 23. as specified in 3GPP TS 29. otherwise shall be absent.1 Provide Roaming Number The following information elements are required: 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 C C C Description IMSI of the B subscriber (see 3GPP TS 23. Shall be present if the HLR has determined an alerting category or an alerting level for the MT call configuration. the VLR has indicated support for CAMEL Phase 3 or later. 3GPP . otherwise shall be absent. Shall be present if the LMSI was sent to HLRB at location updating.

MS classmark.location information. No roaming number available.5 Provide Subscriber Info ack The following information elements are required: 3GPP . OR not allowed.IMEI (with software version). Indicates that the HLR requires active location retrieval. Indicates which of the following information the HLR requires: . 8. Shall be present if the LMSI was sent to the HLR at location updating.3.subscriber state.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 C Description IMSI of the subscriber for whom information is requested (see 3GPP TS 23.2 Provide Roaming Number ack The following information element is required: Information element name Roaming number Required M Description E.3 Provide Roaming Number negative response The negative response information element can take the following values: Absent subscriber.018 V7. Data missing. Local Mobile Subscriber Identity. .Release 7 271 3GPP TS 23. .3. .164 number required to route the call to VMSCB (see 3GPP TS 23. Shall be absent if the requested information does not indicate that the HLR requires location information.3. Facility not supported.5. 8. 8.3.003 [5]). Unexpected data value.003 [5]).0 (2007-06) 8.

8. Shall be present if the MS classmark was requested. otherwise shall be absent.3. cell global identity or location area identity. otherwise shall be absent.Release 7 272 3GPP TS 23. otherwise shall be absent. 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. Indicates whether the MS is busy (i. see ITU-T Recommendation Q.3. System failure.e. otherwise shall be absent. MS classmark 2 as defined in 3GPP TS 24.1. see 3GPP TS 23.018 V7.008 [26]. otherwise shall be absent. Shall be present if the IMEI was requested. otherwise shall be absent.5. Shall be present if location information was requested and is available.3.032 [7] .003 [5].1 Location information The compound information element Location information consists of the following subordinate information elements: Information element name Location number Required C Service area ID C Cell ID C Geographical information C Geodetic information C VLR number Age of location information Current Location Retrieved O C C Description For a definition of this information element.5. Shall be present if available in the MSC/VLR. cell global identity or location area identity.763 [35]. network determined not reachable (IMSI detached or roaming in a prohibited location area) or assumed idle. engaged on a circuitswitched call).5. otherwise shall be absent. The mapping from service area identity or cell ID and location area to location number is network-specific and outside the scope of the UMTS and GSM standards.763 [35]. 3GPP . Measured in minutes. Shall be present if the VLR can derive it from the stored service area identity. otherwise shall be absent. 8.003 [5]). If the HLR receives it from the VLR it shall ignore it. E. Cell global identity of the cell in which the MS is currently in radio contact or in which the MS was last in radio contact. Shall be present if the VLR can derive it from the stored service area identity.164 number which identifies the VLR (see 3GPP TS 23. otherwise shall be absent. This information element corresponds to the Calling Geodetic Location defined in ITU-T Recommendation Q.0 (2007-06) 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. Shall be present if the MS uses GSM radio access and the subscriber record is marked as confirmed by radio contact.6 Provide Subscriber Info negative response The negative response information element can take the following values: Data missing. Shall be present if subscriber state was requested. Shall be present when location information was obtained after a successful paging procedure for Active Location Retrieval. IMEISV as defined in 3GPP TS 23. Shall be present if the MS uses UMTS radio access and the subscriber record is marked as confirmed by radio contact. otherwise shall be absent. For a definition of this information element. 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.

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

1 CF cancelled This message contains no information elements.5.4 Perform Call Forwarding negative response The negative response information element can take the following value: Call forwarding failed. In addition. 8.5 Messages on the MSC internal interface This interface can carry ISUP messages received from the process MT_GMSC or the process ICH_MSC and to be forwarded to a destination exchange.5.079 [13] 8. 8. 8.6.6.4.3 Perform Call Forwarding ack The following information element is required: Information element name Forwarded-to number Required M Description E.3 Check IMEI negative response The negative response information element can take the following value: Unknown equipment. as a result of CAMEL handling.164 number of the C subscriber. The correlation between the process instances is done by the MSRN.5.6 Messages on the VLR internal interface This interface carries messages between corresponding instances of the processes PRN_VLR and ICH_VLR.2 Perform Call Forwarding The following information element is required: Information element name Forwarded-to number OR call Required M M Description E. and ISUP messages received from the destination exchange and to be forwarded to the process MT_GMSC or the process ICH_MSC.1 Call arrived This message contains no information elements. Indicates whether the call which is to be forwarded was subject to basic OR as specified in 3GPP TS 23. Note: this number may be different from the Forwarded-to number received in the Perform Call Forwarding.018 V7. 8.Release 7 274 3GPP TS 23.0 (2007-06) 8.5. 8. 8. 8.5. 3GPP .164 number of the C subscriber. it carries the following inter-process messages.2 PAR completed This message contains no information elements.

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

Release 7 276 3GPP TS 23.0 (2007-06) 8.018 V7.5.1 Release Resources The following information elements are required: Information element name MSRN Required M Description Mobile Station Roaming Number.8 Messages on the E interface (GMSC-VMSC) 8. 3GPP .8.

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

018 V7.5.Release 7 278 3GPP TS 23.0 (2007-06) procedure MSC_coord_setup Procedur e in the MSC to handle a n incoming IAM and trigger the correct application proce ss 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 In itial Address To destination dete rmin ed by routeing tables HLR address No derivable? Figure 84a: Process MSC_Coord (sheet 1) 3GPP .

018 V7.Release 7 279 3GPP TS 23.5.0 (2007-06) Annex B (informative): Change history 3GPP .

5.018 23.0 3.0 Correction of CAMEL Incoming Call Handling 3.018 23.018 23.6.0 Correction to process ICH_VLR 3.3.018 23.3.018 23.5.3.018 23.Release 7 280 3GPP TS 23.018 23.0 Correction of connector numbering in process ICH_MSC 3.6.0 4.4.0 (2007-06) TSG CN# Spec CR Apr 1999 GSM 03.0 4.018 23.4.0 O-CSI and D-CSI checks for ORLCF calls 3.2.018 23.0 Corrections to process ICH_VLR 3.3.0 Modifications to procedure obtain routeing address.0 4.0 Separation of success & failure cases for OR of late call forwarding 3.1.2.0 3.0 Initialization of Backward Call indicator 3.3.5.1.18 CN#03 23.0 Approved at CN#03 3.018 V7.0.0 3.0 3.5.0 Alternative solution for ALR 3.018 23.0 Update of CAMEL references 3.018 23.0 Initialization of variable to monitor activation of CSI's 3GPP .2.018 23.4.0 3.018 23.0 3.5.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 CN#12 23.0 Removal of TDP criteria from Resume Call Handling 3.0 4.0 Setting the Destination Address for MO calls 3.0 3.0 Paging not via the SGSN correction 4.0 Replacement of references to GSM with references to UMTS 3.0.5.3.018 23.3.018 23.2.3.0 Correction of procedure Obtain_Routeing_Address for the reconnect case 3.4.1.0 3.0 3.0 Tidying up of Process Subs_FSM and interprocess signals 4.0 Transferred to 3GPP CN1 3.4.0 3.018 23.0 GMSC CAMEL phases in Provide Roaming Number 3.6.018 23.018 23.2.018 23.3.4.0 North American Service Provider Number Portability impacts for MNP 3.018 23.0 3.0 Inclusion of call hold in basic call handling.0 Introduction of the Super-Charger Concept in TS 23.018 23.018 23.0.4.018 23.2.6.0 3.4.1.6.4.0 3.1.018 CN#04 23.0 4.0 3.018 23.6.0 Notification of Call Forwarding to the gsmSCF before activating call forwarding process 3.018 23.0 3.0 3.0 3.4.6.2.018 23.0 Inclusion of D-CSI check in HLR/VLR 3.0 3.018 23. 4.0 3.6.0 3.1.0 3.0 3.1.1.5.5.0 Incorporation of MPTY and ECT into the Subs_FSM process 4.3.4.4.4.5.0 3.4.0.3.0 3.018 3.0.0 Correction of the SDL diagram for Prepaging 3.018 23.5.3.018 23.0 Introduction of CAMEL Phase 3 3.5.2.6.018 23.3.2.018 23.4.018 23.0 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 074 Phase R4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Change history Version New Version Subject/Comment 7.3.0 Introduction of Authentication Failure Report 3.2.0 Notification of Call Forwarding to the gsmSCF 3.0 3.0 Clarification of N-CSI in Core NW 3.5.4.3.0 3.0 Addition of the description for Pre-Paging 3.4.0 3.3.018 23.3.0 3.1.018 23.018 23.0 3.0 Addition of the description for Multicall 3.0 Clarification of NPDB error detection and MNP specific call handling 3.1.0 Improvement of Active Retrieval of Location Information procedure 3.018 23.0 4.0 Correction of the result of the procedure CAMEL_ICH_MSC_INIT 3.2.0 Handling of the Call Diversion Treatment Indicator 3.0 3.0 Removal of CW descriptions 4.0 ISUP release cause value 3. 3.0 3.0 Correction of CF Notification 3.0 Correction of the SDL diagrams for Prepaging 3.

0.0 Removal of SIWF material Rel-6 6.1.2.5.1.SDLs Rel-7 7.018 23.0 5.4.0.0 Addition of procedure to retrieve UE-specific behaviour data Rel-5 5.018 23.0 Trunk Originated CAMEL triggering .0 5.1.018 23.0 Collective CR for Rel-6 Enhanced Dialled Services Rel-6 6.3.5.0 6.0 5.0 6.018 23.0.0 Correction on the Active Location Retrieval description Rel-5 5.0 5.018 23.0 Introduction of CAMEL Phase 4 Rel-5 5.018 23.0 Incorrect implementation of CR 133 Rel-6 6.0 Setting of Leg1_Status variable Rel-5 5.3.7.018 23.0 7.018 23.018 23.007 3GPP .0 5.0 Corrections to "Early UE" handling Rel-5 5.3.2.3.0.018 23.6.0 5.0 Add “CAMEL_Stop_TNRy”in Procedure OG_Call_Setup _MSC (sheet 4) Rel-6 6.018 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 23.018 CR 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 Change history Phase Version New Version Subject/Comment Rel-5 4.3.018 V7.4.018 23.4.018 23.0 6.0 Handling of MultiCall in MPTY procedure Rel-5 5.2.0 5.0 Mobile Termination whilst the MS is moving to another MSC Rel-7 7.0 Management Based Activation Impacts Rel-7 6.7.0 Handling of CUG calls in non-supporting networks Rel-5 5.0 (2007-06) TSG CN# Spec CN#12 23.0 Minor corrections to Process ICH_MSC Rel-5 5.1.2.0 Release Result from CAMEL_MT_GMSC_Notify_CF Rel-5 5.0 5.5.2.1.3.018 23.018 23.0 5.5.0 5.0 Addition of missing process Update_Location_VLR Rel-5 5.0 Trunk Originated CAMEL: Inter-digit timer stop/reset SDL correction Rel-7 7.3.018 23.018 23.6.3.0 5.0 Incorrect References Rel-7 7.3.Release 7 281 3GPP TS 23.8.1.8.018 23.0 5.018 23.1.0 5.0 Clarification of requirements for the presence of IEs in messages Rel-5 5.0 7.3.0 Correction to the IC_CUG_Check Procedure Rel-7 7.3.0 Correction in the ATI mechanism description Rel-5 5.0.0 Transferring the MS classmark & IMEI to the gsmSCF Rel-5 5.018 23.018 23.0 7.4.7.0 Default Basic Service for gsmSCF-initiated calls Rel-6 6.0 5.1.2.0 5.0 5.018 23.0 Optional Suppress Terminating Services Bit String in SRI Rel-7 7.018 23.2.018 23.0 Pre-Paging Resource Optimization Rel-6 6.0 Editorial clean up Rel-5 5.018 23.0 6.018 23.0 PLMN BC in PRN for alternate speech/fax alignment with TS 29.0 7.0 5.0 7.2.1.0 7.0.4.0 7.2.4.7.8.4.6.3.0 5.7.018 23.4.0 HLR Interrogation for SCUDIF calls Rel-6 5.0 6.018 23.0 Determining the basic service for MT calls Rel-5 5.3.0 5.4.0.5.018 23.018 23.0 Handling of Reconnect on Leg2 Disconnect Rel-5 5.0 5.3.018 23.0 6.2.0 Stopping No_Answer timer in the case of forwarding notification Rel-5 5.0 6.2.018 23.0 Corrections in the ATI mechanism description Rel-5 5.0 MSISDN in Provide Roaming Number in case of MSP Rel-5 5.6.018 CN#13 23.2.2.