P. 1
Camel Phase 2 Etsi

Camel Phase 2 Etsi

|Views: 14|Likes:
Published by Vladimir Tsagov
Camel Phase 2 Etsi
Camel Phase 2 Etsi

More info:

Published by: Vladimir Tsagov on Feb 13, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

09/27/2013

pdf

text

original

TS 101 044 V5.7.

0 (1999-03)
Technical Specification

Digital cellular telecommunications system (Phase 2+); Customized Applications for Mobile network Enhanced Logic (CAMEL); Stage 2 (GSM 03.78 version 5.7.0 Release 1996)

R

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

European Telecommunications Standards Institute

(GSM 03.78 version 5.7.0 Release 1996)

2

TS 101 044 V5.7.0 (1999-03)

Reference
RTS/SMG-030378QR6 (9o002kc3.PDF)

Keywords
Digital cellular telecommunications system, Global System for Mobile communications (GSM)

ETSI Secretariat
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE

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

Internet
secretariat@etsi.fr
Individual copies of this ETSI deliverable can be downloaded from

http://www.etsi.org
If you find errors in the present document, send your comment to: editor@etsi.fr

Copyright Notification
No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1999. All rights reserved.

ETSI

(GSM 03.78 version 5.7.0 Release 1996)

3

TS 101 044 V5.7.0 (1999-03)

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

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

4
4.1 4.2 4.2.1 4.2.2 4.2.3 4.2.4 4.2.5 4.2.6

Architecture............................................................................................................................................11
Functional Entities used for CAMEL............................................................................................................... 11 Interfaces defined for CAMEL ........................................................................................................................ 11 HLR - VLR interface.................................................................................................................................. 11 GMSC - HLR interface .............................................................................................................................. 12 GMSC - gsmSSF interface ......................................................................................................................... 12 gsmSSF - gsmSCF interface....................................................................................................................... 12 MSC - gsmSSF interface ............................................................................................................................ 12 gsmSCF - HLR interface ............................................................................................................................ 12

5
5.1 5.2

Detection Points (DPs)...........................................................................................................................12
Definition and description................................................................................................................................ 12 DP processing rules ......................................................................................................................................... 13

6
6.1 6.1.1 6.1.1.1 6.1.1.2 6.1.1.3 6.1.1.4 6.2

Description of CAMEL Subscriber Data...............................................................................................14
Description of Originating/Terminating CAMEL Subscription Information (O/T-CSI).................................. 14 Content of the O/T-CSI .............................................................................................................................. 14 gsmSCF address ................................................................................................................................... 14 Service Key .......................................................................................................................................... 14 Default Call Handling........................................................................................................................... 14 TDP List ............................................................................................................................................... 14 Description of Subscriber Information in S R I Ack indicator......................................................................... 14

7

Description of CAMEL BCSMs ............................................................................................................14
General Handling............................................................................................................................................. 14 Originating Basic Call State Model (O-BCSM) .............................................................................................. 15 Description of O-BCSM............................................................................................................................. 15 Description of the call model (PICs) .................................................................................................... 15 O_Null & Authorise_Origination_Attempt_Collect_Info............................................................... 16 Analyse, Routing & Alerting........................................................................................................... 16 O_Active......................................................................................................................................... 17 O_Exception ................................................................................................................................... 17 Terminating Basic Call State Model (T-BCSM).............................................................................................. 17 Description of T-BCSM ............................................................................................................................. 17 Description of the call model (PICs) .................................................................................................... 18 T_Null............................................................................................................................................. 18 Terminating Call Handling.............................................................................................................. 19 T_Active ......................................................................................................................................... 19 T_Exception.................................................................................................................................... 20 BCSM Modelling of Call Scenarios ................................................................................................................ 20 Mobile Originated Call............................................................................................................................... 20 Mobile Terminated Call ............................................................................................................................. 21 Call Forwarding at the GMSC.................................................................................................................... 21 Call Forwarding at the MSC....................................................................................................................... 22 Handling of mobile originated calls................................................................................................................. 23 Handling of mobile originated calls in the originating VMSC ................................................................... 23

7.1 7.2 7.2.1 7.2.1.1 7.2.1.1.1 7.2.1.1.2 7.2.1.1.3 7.2.1.1.4 7.3 7.3.1 7.3.1.1 7.3.1.1.1 7.3.1.1.2 7.3.1.1.3 7.3.1.1.4 7.4 7.4.1 7.4.2 7.4.3 7.4.4

8
8.1 8.1.1

Procedures for CAMEL .........................................................................................................................23

ETSI

(GSM 03.78 version 5.7.0 Release 1996)

4

TS 101 044 V5.7.0 (1999-03)

8.1.1.1 8.1.1.1.2 8.1.1.1.3 8.1.1.1.4 8.1.1.2 8.1.1.3 8.1.1.4 8.1.1.5 8.1.2 8.1.2.1 8.2 8.2.1 8.2.1.1 8.2.1.2 8.2.1.2.1 8.2.1.2.2 8.2.1.2.3 8.2.1.2.4 8.2.1.2.5 8.2.1.2.6 8.2.1.2.7 8.2.1.2.8 8.2.1.3 8.2.1.4 8.2.1.5 8.2.1.6 8.2.2 8.2.2.1 8.2.2.2 8.2.2.3 8.2.2.4 8.2.3 8.2.3.1 8.3 8.3.1 8.3.2 8.4 8.4.1 8.4.2 8.5 8.5.1 8.5.1.1 8.5.1.2 8.5.1.3 8.5.2 8.5.2.1 8.5.2.2 8.5.2.3 8.5.3 8.5.3.1 8.5.3.2 8.5.3.3 8.5.3.4 8.5.3.5 8.5.3.6 8.5.3.7 8.5.4 8.5.4.1 8.5.4.2 8.5.4.3

Procedure CAMEL_OCH_MSC_INIT ................................................................................................ 23 Actions on receipt of Int_Error ....................................................................................................... 23 Actions on receipt of Int_Continue ................................................................................................. 23 Actions on receipt of Int_Connect .................................................................................................. 23 Procedure CAMEL_OCH_MSC_ANSWER........................................................................................ 23 Procedure CAMEL_OCH_MSC_DISC1 ............................................................................................. 23 Procedure CAMEL_OCH_MSC_DISC2 ............................................................................................. 23 Procedure CAMEL_OCH_MSC_DISC3 ............................................................................................. 23 Handling of mobile originated calls in the originating VLR ...................................................................... 30 Procedure CAMEL_OCH_VLR........................................................................................................... 30 Retrieval of routeing information..................................................................................................................... 31 Retrieval of routeing informationin the GMSC .......................................................................................... 31 Procedure CAMEL_Set_ORA_Parameters .......................................................................................... 31 Procedure CAMEL_MT_GMSC_INIT................................................................................................ 31 Action on receipt of Int_Release_Call ............................................................................................ 31 Action on receipt of Int_Error......................................................................................................... 31 Action on receipt of Int_Continue................................................................................................... 31 Action on receipt of Int_Connect .................................................................................................... 31 Send Routeing Info negative response in state Wait_For_Routeing_Info_2................................... 32 Send Routeing Info ack with MSRN in state Wait_For_Routeing_Info_2 ..................................... 32 Send Routeing Info ack with FTN in state Wait_For_Routeing_Info_2......................................... 32 Send Routeing Info ack with O-CSI and FTN in state Wait_For_Routeing_Info_2....................... 32 Procedure CAMEL_MT_GMSC_ANSWER ....................................................................................... 32 Procedure CAMEL_MT_GMSC_DISC1............................................................................................. 32 Procedure CAMEL_MT_GMSC_DISC2............................................................................................. 32 Procedure CAMEL_MT_GMSC_DISC3............................................................................................. 32 Retrieval of routeing information in the HLR ............................................................................................ 42 Procedure CAMEL_HLR_INIT ........................................................................................................... 42 Procedure CAMEL_CSI_Check_HLR................................................................................................. 42 Procedure CAMEL_T_CSI_CHECK_HLR ......................................................................................... 42 Procedure CAMEL_O_CSI_CHECK_HLR......................................................................................... 42 Handling of provide roaming number request in the VLR ......................................................................... 46 Procedure CAMEL_SET_SOA ............................................................................................................ 47 Handling of mobile terminated calls ................................................................................................................ 48 Handling of mobile terminated calls handling in the terminating VMSC................................................... 48 Handling of mobile terminated calls in the terminating VLR..................................................................... 48 Handling of forwarded calls............................................................................................................................. 48 Procedure CAMEL_CF_INIT.................................................................................................................... 48 Procedure CAMEL_CF_ANSWER ........................................................................................................... 48 Handling of mobile calls in the gsmSSF .......................................................................................................... 53 State Idle .................................................................................................................................................... 53 Int_Invoke_gsmSSF ............................................................................................................................. 53 Int_DP_O/T_Answer or Int_DP_O/T_Disconnect............................................................................... 53 Int_O/T_Exception ............................................................................................................................... 53 State Wait_For_Request............................................................................................................................. 53 Int_DP_Collected_Info......................................................................................................................... 53 DP_Terminating_Attempt_Authorised................................................................................................. 53 Int_O/T_Exception ............................................................................................................................... 53 Waiting_For_Instructions........................................................................................................................... 53 CAP_Request_Report_BCSM_Event .................................................................................................. 53 CAP_Continue...................................................................................................................................... 53 CAP_Connect ....................................................................................................................................... 54 CAP_Release_Call ............................................................................................................................... 54 Timer expire ......................................................................................................................................... 54 Int_O/T_Exception ............................................................................................................................... 54 Int_DP_O/T_Disconnect ...................................................................................................................... 54 Monitoring ................................................................................................................................................. 54 Int_DP_O/T-Answer............................................................................................................................. 54 Int_DP_O/T_Disconnect ...................................................................................................................... 54 CAP_Release_Call ............................................................................................................................... 55

ETSI

. 71 Description ..................2 9.........2.........5..............................................3.......................1.........................................0 Release 1996) 5 TS 101 044 V5...2 9..1 9....................................................5 9.. 65 Description .... 65 Description .................... 65 Event Report BCSM ..............................................................................................................................................................................6 9...............................5 8.........................................................................................5....7 8...............................1..... 66 Description ........................................................4.......................................... 65 Information Elements ..................................................2 9...................................................4 9..........................................................................................................3................................................................................2...3 9.2................3 9.................................................................................................5................................................................................................................................................................ 73 Description ............................................................................... 74 Description ........4.........2 9......1...........................................................4 9.................................................................................................................................5.............. 65 Activity Test Response............. 72 Information Elements ..........................1 9......................................1 9............................1....2 9..................................... 66 Initial DP .........................1.............................................................................2 9................4........................................................................6 8.........................................3.................................................2..................................................... 72 Insert Subscriber Data ........................................3.....2..............78 version 5...................1 9.................................................................................1...............2 9................................................1....................................................................................... 62 Procedure Provide_Subscriber_Info_HLR .................1................1.........................1.............................................1 9...................................................1 9..................5.............................1.......................4 8.......4............5... 71 Information Elements ...........................................................................................1 9......................................................................... 69 Information Elements .............. 70 Information Elements ........................................................................ 69 Continue ...... 74 Description .........2................................................................ 72 Description ..................2 9..................................................................................2.................................................................................................1 9.....2.........................1..6.. 70 Release Call................................................5.............................. 70 gsmSCF to HLR information flows ..........3 9..................................3..2 9..2............................................................................. 55 Actions of the process gsmSSF in error cases .............1..............................................................2 9.............. 73 Information Elements ........................................................................4..............................................3..................................................2 9.............................. 70 Description .............................................................................................................................................................1 9.........................................................................................................2 9...............................................................................................4 9............... 69 Description .......................................................3......................65 gsmSSF to gsmSCF information flows ..............................................................1..............................................2............................ 74 ETSI ......................................................5 9................................................................................................2........................................................... 67 gsmSCF to gsmSSF information flows ..........................................................................2 9.............1 9................. 71 Information Elements ..2.................................................... 70 Description .............................1 9..................................... 71 Any Time Interrogation Response......................................................2.................................................1...........................6..1 9....................................................5........ 69 Connect ............................................................4 9....1.......................2....1.. 70 Information Elements .........6........... 55 Any Time Interrogation ...............................1 9...2.... 71 Any Time Interrogation Request ...............................................................................5......................................................2......................................................2 9............6.......................................... 73 Information Elements . 70 Description ..................................7................................................... 66 Information Elements ................... 73 Provide Roaming Number.....5............................................ 69 Activity Test...................... 74 Insert Subscriber Data ack.............................................................................................. 65 Information Elements ..............0 (1999-03) 8................................................................. 73 Provide Subscriber Info....................................1 9....................1.............7................. 63 CAMEL specific handling at subscriber data management in the HLR.................................................................................3.................................................... 70 Information Elements ....................................2 9............................................................... 72 Delete Subscriber Data.............. 72 Description .............. 71 HLR to gsmSCF information flows ..........4.....5.1 9................................2 9..................................................................... 65 9 9...............................................5..................... 72 Information Elements .....4............................................................2...............6.....1 9.....1 Description of information flows.................................................................................................................................................................2............5.........1 9.............................. 72 HLR to VLR information flows ....................................................................9 Int_O/T_Exception ............................... 65 Processing of Non-Call Related Events ....................................................................................................................................................................................2.....................................................2 9...................................2...(GSM 03...............................1 9..............8 8..2 9...................... 69 Information Elements .......5......................................................................................................................................................................................................1.1 9...........1 9.........................................5........................................................................................ 74 Information Elements .........2..3............................................................................................................................................ 69 Description ..............................1 9.......................1......................... 71 Description ...............................1 9..........................4.............1. 73 VLR to HLR information flows ..........................................5......................... 74 Provide Subscriber Info ack .....................................................2 9.....................................2................... 70 Request Report BCSM Event.......3 9................ 73 Description ............

............................ 76 9........................11.. 75 9....................................................................3 Send Info For Incoming Call negative response.10.7......................................................................................................................................................................11................................................................................2 Information Elements ....1........11......................................... 74 9.......................................9.......................................11 VLR to MSC information flows........2.............. 78 9.... 77 9...(GSM 03................................................................................. 77 9.......................................................................................................1 Send Routeing Info.........................................................................................2 Information Elements .......................................1 Send Routeing Info ack .....................2 Information Elements ............. 74 9...... 77 9..3........1 Resume Call Handling..................................................................................................................... 76 9......1............................................................................ 78 9............11............ 77 9...............................7................2 Information Elements .................................................................2 Send Info For Incoming Call ack ......................................................1 Complete Call....................................................... 76 9..2 Information Elements ........................................................................................................10.....................................................................................................................................9 VMSC to GMSC information flows .2 Information Elements ............ 76 9.................1 Description ..............................................................................................0 Release 1996) 6 TS 101 044 V5...................1 Send Info For Outgoing Call ......................... 77 9..............1..............................................................................7 HLR to GMSC information flows............................ 78 9....... 78 9.....................................1................... 74 9...................1 Description ..................................................................................................................................................... 74 9......................8..7...................................80 ETSI ............................ 77 9.....7.......................9...11...................................1........................................................................2 Information Elements .............8 GMSC to HLR information flows...........8...............79 History ......1 Description ..................................................3.1..1..1 Description ..1 Description ..................7......................................................11.........................11................................78 version 5................................................................................................8.............................................................. 78 9.......................................................................................... 78 9........................1.............................................11............................ 75 9................................ 74 9...................................... 75 9........................2 Information Elements .............................9.1 Description ................................................6...........................................................0 (1999-03) 9..................2.............2................................................................................11.....1...........................................................10 MSC to VLR information flows.................................10................................................................................................................. 78 Annex A (informative): Document Change History............................................................1 Description ...................................................................................... 76 9.................................. 77 9....................1..........................................

if any. is publicly available for ETSI members and non-members. No guarantee can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server) which are. i. technical enhancements. Latest updates are available on the ETSI Web server (http://www. corrections.0 Release 1996) 7 TS 101 044 V5. etc.78 version 5.(GSM 03. The contents of the present document are subject to continuing work within SMG and may change following formal SMG approval. updates. The present document defines the stage 2 description of Customized Applications for Mobile network Enhanced Logic (CAMEL) within the digital cellular telecommunications system.0 (1999-03) Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI.7.org/ipr). which is available free of charge from the ETSI Secretariat. or may be. Essential. or potentially Essential.e. Pursuant to the ETSI IPR Policy. essential to the present document. it will then be republished by ETSI with an identifying change of release date and an increase in version number as follows: Version 5.etsi. including IPR searches. and can be found in SR 000 314: "Intellectual Property Rights (IPRs). or may become. y the third digit is incremented when editorial only changes have been incorporated in the specification.7.x. ETSI . IPRs notified to ETSI in respect of ETSI standards". no investigation. Should SMG modify the contents of the present document. The information pertaining to these essential IPRs.y where: 5 indicates GSM Phase 2+ Release 1996 x the second digit is incremented for changes of substance. has been carried out by ETSI. Foreword This Technical Specification (TS) has been produced by the Special Mobile Group (SMG).

[1] [2] [3] [4] GSM 01. any time interrogation. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with a gsmSCF which is controlled by the HPLMN.0 Release 1996) 8 TS 101 044 V5. suppression of announcements. the appropriate procedures which provide the necessary information to the VPLMN or to the HPLMN are invoked. GSM 03. mobile terminating calls. subsequent revisions do not apply.mobile originated and forwarded calls. • For a specific reference. In the first phase the CAMEL feature supports: .7. Basic call handling.78 [2]) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services of operators which are not covered by standardized GSM services even when roaming outside the HPLMN. Abbreviations and acronyms". i.78 version 5.(GSM 03. The specification of operator specific services in HPLMN are outside the scope of the present document. Subscribers who have subscribed to operator specific services and therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. Technical realisation ". constitute provisions of the present document. version number. In case a subscriber is marked to need CAMEL support. edition number. Support of Optimal Routeing (SOR).. Any user procedures for the control of operator specific services are outside the scope of the present document. GSM 02. 2 References • References are either specific (identified by date of publication. and the gsmSCF and the HPLMN are therefore distinct entities. The mechanism described in the present document addresses especially the need for information exchange between the VPLMN or IPLMN and the HPLMN for support of operator specific services. through reference in this text.78: "Digital cellular telecommunications system (Phase 2+). ETSI .04 (ETR 350): "Digital cellular telecommunications system (Phase 2+). the GSM Service Control Function (gsmSCF) is treated as being part of the HPLMN. Customized Applications for Mobile network Enhanced Logic (CAMEL) . • A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number.0 (1999-03) 1 Scope The present document specifies the stage 2 description for the first phase (see GSM 02. The regulatory environment in some countries may require the possibility that the gsmSCF and the HPLMN are controlled by different operators.e. In the present document. the latest version applies. • For a non-specific reference. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN. in case an Emergency call has been requested the gsmSSF shall not be invoked. Note that CAMEL is not applicable to Emergency Setup (TS 12). Technical realisation" The following documents contain provisions which.stage 1 GSM 03.) or non-specific.18 (TS 101 043): "Digital cellular telecommunications system (Phase 2+).79 (TS 101 045): "Digital cellular telecommunications system (Phase 2+). The CAMEL feature is a network feature and not a supplementary service.7. etc.

7. Service Key: The Service Key can identify to the gsmSCF the service logic that it should apply. The Service Key is part of the T/O-CSI. Point In Call (PIC): PICs identify MSC/VLR (GMSC) activities associated with one or more basic call/connection states of interest to OSS service logic instances.02 (ETS 300 974): "Digital cellular telecommunications system (Phase 2+).78 (TS 101 046): "Digital cellular telecommunications system (Phase 2+). The T-BCSM corresponds to that portion of the BCSM associated with the terminating party.78 version 5. Terminating Basic Call State Model (T-BCSM): The terminating half of the BCSM. GSM Service Switching Function (gsmSSF): A functional entity that interfaces the MSC/GMSC to the gsmSCF. The provision of location information is independent of the MS status.7. The concept of the gsmSSF is derived from the IN SSF. As such. the following definitions apply: Basic Call State Model (BCSM): The BCSM provides a high-level model of GMSC. GSM 09.1 Definitions and abbreviations Definitions For the purposes of the present document. The Service Key is administered by the HPLMN.1214. Originating Basic Call State Model (O-BCSM): The originating half of the BCSM. Originating CAMEL Subscription Information (O-CSI): The O-CSI identifies the subscriber as having originating CAMEL services.0 (1999-03) [5] [6] GSM 09. May 1995: "Distributed Functional Plane for Intelligent Network CS-1" [7] 3 3. Subscriber State: See GSM 02. The O-BCSM corresponds to that portion of the BCSM associated with the originating party. It interfaces with the gsmSSF and the HLR. ITU-T Q.78 [2]. and is passed transparently by the VPLMN/IPLMN to the gsmSCF. but uses different triggering mechanisms because of the nature of the mobile network. Terminating CAMEL Subscription Information (T-CSI): The T-CSI identifies the subscriber as having terminating CAMEL services. Location Information: Indicates the location of the served subscriber. As part of the location information.0 Release 1996) 9 TS 101 044 V5. GSM Service Control Function (gsmSCF): A functional entity that contains the CAMEL service logic to implement OSS. ETSI . it identifies a set of basic call activities in a GMSC or MSC/VLR and shows how these activities are joined together to process a basic call. an indication of the age of this information shall be delivered.or MSC/VLR-activities required to establish and maintain communication paths for users.(GSM 03. Customized Applications for Mobile network Enhanced Logic (CAMEL): CAMEL Application Part (CAP) specification". Detection Points (DP): The points in processing at which notifications (to the service logic) can occur and transfer of control (to the gsmSCF) is possible are called Detection Points (DPs). Mobile Application Part (MAP) specification".

0 (1999-03) 3.04.78 version 5.7.(GSM 03.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.0 Release 1996) 10 TS 101 044 V5. the following abbreviations apply.7. BCSM CAMEL DP EDP GMSC gsmSCF gsmSSF HLR HPLMN IE IF IPLMN MSC O-BCSM O-CSI ODB OSS PIC PLMN SLPI SMF T-BCSM T-CSI TDP VLR VPLMN Basic Call State Model Customized Applications for Mobile network Enhanced Logic Detection Point Event Detection Point Gateway MSC GSM Service Control Function GSM Service Switching Function Home Location Register Home PLMN Information Element Information Flow Interrogating PLMN Mobile service Switching Centre Originating Basic Call State Model Originating CAMEL Subscription Information Operator Determined Barring Operator Specific Service Point In Call Public Land Mobile Network Service Logic Program Instance Service Management Function Terminating Basic Call State Model Terminating CAMEL Subscription Information Trigger Detection Point Visitor Location Register Visited PLMN ETSI . For the purposes of the present document.

VLR: The VLR stores the O-CSI as part of the subscriber data for subscribers roaming in the VLR area. The O-CSI is sent to the VLR in case of Location Update or if the O-CSI is updated.0 Release 1996) 11 TS 101 044 V5. GMSC: When processing the calls for subscribers requiring CAMEL support the GMSC receives a O/T-CSI from the HLR.7. Also the additions needed to the basic GSM functionality are described. The O/T-CSI is sent to the GMSC when the HLR responds to a request for routing information. gsmSCF: see subclause 3. 4.7.1 HLR . The HLR may provide an interface towards the gsmSCF for the Any Time Interrogation procedure.2 Interfaces defined for CAMEL This subclause describes the different interfaces applicable to CAMEL.VLR interface This interface is used to send the CAMEL related subscriber data to the visited PLMN and for provision of MSRN.78 version 5. The GMSC monitors on request the call states (events) and informs the gsmSSF of these states during processing enabling the gsmSSF to control the execution of the call in the GMSC.1. The interface is also used to retrieve subscriber status and location information of the mobile subscriber or to indicate suppression of announcement for a CAMEL service. The architecture is applicable to the first phase of CAMEL. indicating the GMSC to request instruction from the gsmSSF. The MSC monitors on request the call states (events) and informs the gsmSSF of these states during processing enabling the gsmSSF to control the execution of the call in the MSC.1.Outgoing leg (or Forwarding leg) Visiting Network Interrogating Network Figure 4/1: Functional architecture for support of CAMEL HLR: The HLR stores the O/T-CSI for subscribers requiring CAMEL support. ETSI . MSC: When processing the calls for subscribers requiring CAMEL support the MSC receives a O-CSI from the VLR indicating the MSC to request instruction from the gsmSSF.(GSM 03.0 (1999-03) 4 4.2.1 Architecture Functional Entities used for CAMEL This subclause describes the functional architecture needed to support CAMEL. It specifies on a high level the functions specific to CAMEL. Home Network HLR MAP gsmSCF MAP CAP MAP CAP gsmSSF Incoming line VLR Roaming leg gsmSSF MSC MS GMSC Forwarded leg MO call . gsmSSF: see subclause 3. 4. Figure 4/1 shows the functional entities involved in calls requiring CAMEL support.

4.2. A DP can be armed in order to notify the gsmSCF that the DP was encountered. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs. Event Detection Point .Request (TDP-R) This detection point is statically armed and initiates a CAMEL control relationship when encountered. Processing is suspended when the DP is encountered.HLR interface This interface is used at terminating calls to exchange routing information. The DPs for Mobile Originated Calls and Mobile Terminated Calls are described in subclauses 7.Request (EDP-R) This detection point is dynamically armed within the context of a CAMEL control relationship. The interface is described in the specification to make it easier to understand the handling of DPs (arming/disarming of DPs.2. location information. Event Detection Point . 4.1 Detection Points (DPs) Definition and description Certain basic call events may be visible to the GSM Service Control Function (gsmSCF).2. the processing entity continues the processing without gsmSCF involvement.gsmSCF interface This interface is used by the gsmSCF to control a call in a certain gsmSSF.3.7. The DPs are characterized by the following attributes: ETSI . The O/T-CSI that is passed to the IPLMN is sent over this interface.2 GMSC . 4.HLR interface This interface is used by the gsmSCF to request information from the HLR.2 and 7. subscriber status. DP processing etc.0 (1999-03) 4. The DPs are the points in call at which these events are detected. 4.gsmSSF interface This an Internal interface.2. subscription information and suppression of announcements. Processing is not suspended when encountering the DP.5 MSC . As a network operator option the HLR may refuse to provide the information requested by the gsmSCF.78 version 5. and potentially to allow the gsmSCF to influence subsequent handling of the call.HLR interface is a network operator option.(GSM 03.gsmSSF interface This is an internal interface. Support of the gsmSCF . Processing is suspended awaiting instructions from the gsmSCF when encountering the DP. If the DP is not armed.6 gsmSCF . Relationships on this interface are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF.7.3 GMSC .).2. 5 5.). Three different types of DPs are identified: Trigger Detection Point .Notification (EDP-N) This detection point is dynamically armed within the context of a CAMEL control relationship.4 gsmSSF . DP processing etc.0 Release 1996) 12 TS 101 044 V5.

If a call is released.The mechanism by which the DP is armed.given that an armed DP was encountered. During a control relationship.0 (1999-03) a) Arming/disarming mechanism . the gsmSSF provides an information flow via a relationship.2 DP processing rules Since a DP may be armed as an EDP-N or an EDP-R for the same call. or when the call clears.78 version 5. - When the armed TDP-R is encountered triggering is unconditional. A control relationship changes to a monitor relationship if there are no more EDP-Rs armed and ≥ 1 EDP-N armed.(GSM 03. Only TDP-Rs can be disarmed using this mechanism. The following arming rules apply: A DP is statically armed by provisioning the O/T-CSI in the HLR. EDP-Ns are disarmed by the gsmSSF as they are encountered and reported to the SCF. A DP may be statically armed or dynamically armed. During a monitor relationship. If an EDP is met that causes the release of the related leg. A CAMEL monitor relationship if the gsmSCF is not able to influence the call processing via the relationship. If an armed EDP is met. or when the call clears. the gsmSSF should apply the following set of rules during DP processing to ensure single point of control: A control relationship persists as long as there is ≥ 1 EDP-R armed for this portion of the call. A statically armed DP remains armed until the O/T-CSI is withdrawn. A relationship between the gsmSSF and the gsmSCF for the purpose of operator specific service processing is considered to be a CAMEL relationship. b) Relationship . A DP is dynamically armed by the gsmSCF within the context of a CAMEL control relationship (between the gsmSSF and the gsmSCF).0 Release 1996) 13 TS 101 044 V5.7.7. then it is disarmed. then all EDPs related to that leg are disarmed. A monitor relationship terminates if there are no more EDP-Ns armed or the call clears. EDPs are disarmed by the gsmSSF as they are encountered and reported to the SCF. 5. ETSI . A control relationship terminates if there are no more EDP-Rs armed or the call clears. The following disarming rules apply: A statically armed DP is disarmed when a O/T-CSI is withdrawn in the HLR. There are two types of CAMEL relationships: A CAMEL control relationship if the gsmSCF is able to influence the call processing via the relationship. then all EDPs related to that call are disarmed.

164 number to be used for routing.1.3 Default Call Handling The Default Call Handling indicates whether the call shall be released or continued as requested in case of error in the gsmSSF to gsmSCF dialogue. For O-CSI only DP2 is used. 6.1. The BCSM identifies the points in basic call processing when Operator Specific Service (OSS) logic instances (accessed through the gsmSCF) are permitted to interact with basic call control capabilities.1 gsmSCF address Address to be used to access the gsmSCF for a particular subscriber.7.0 (1999-03) 6 6.1.1.0 Release 1996) 14 TS 101 044 V5. The address shall be an E.78 version 5. 6. For T-CSI only DP12 is used.1 6. 6.1.1 Description of CAMEL BCSMs General Handling The BCSM is used to describe the actions in an MSC/GMSC during originating.1. ETSI . an indication that the HLR shall send the location information of the called subscriber.1. 6.1 Description of CAMEL Subscriber Data Description of Originating/Terminating CAMEL Subscription Information (O/T-CSI) Content of the O/T-CSI This subclause defines the contents of the Originating/Terminating CAMEL Subscription Information. Figure 7.7. an indication that the HLR shall send the subscriber state of the called subscriber.1. 6.(GSM 03. forwarded or terminating calls.4 TDP List The TDP List indicates on which detection point triggering shall take place.2 Description of Subscriber Information in S R I Ack indicator This data indicates whether additional subscriber information shall be sent to the GMSC as part of the terminating call handling.1. 7 7.2 Service Key The Service Key identifies to the gsmSCF the service logic that should apply.1/1 shows the components that have been identified to describe a BCSM.

EDP-R Description: Indication that the O-CSI is analysed.2.7.7.2/1: Originating BCSM for CAMEL The following table defines the different DPs which apply to mobile originating and forwarded calls. A disconnect indication is received from the originating party or from the terminating party. Table 1: Definition of CAMEL Detection Points CAMEL Detection Point: DP2 Collected_Info DP7 O_Answer DP9 O_Disconnect [7]: DP2 DP7 DP9 DP Type TDP-R EDP-N EDP-N.1/1: BCSM Components 7. 7.2.1 Originating Basic Call State Model (O-BCSM) Description of O-BCSM The O-BCSM is used to describe the actions in an MSC during originating (MSC) or forwarded (MSC or GMSC) calls.2 7.(GSM 03. For each PIC a description can be found of the entry events.78 version 5.0 (1999-03) Transition DP Point In Call (PIC) Figure 7. Indication that the call is accepted and answered by the terminating party. ETSI . functions and exit events.0 Release 1996) 15 TS 101 044 V5. Routing & Alerting DP7 DP9 O_Active O_Answer O_Disconnect Figure 7. O_Null & Authorise_Origination_ Attempt_Collect_Info O_Exception DP2 Collected_Info Analyse.1 Description of the call model (PICs) This subclause describes the call model for originating and forwarded calls. When encountering a DP the O-BCSM processing is suspended at the DP and the MSC/GMSC indicates this to the gsmSSF which determines what action if any should be taken in case of the DP is armed.1.

Originating call: The ODB categories "barring of all outgoing calls is checked and ODB is invoked if necessary.78 version 5.1. 7. Waiting for indication from terminating half BCSM that the call has been answered by terminating party. 7. if the call encounters one of these exceptions during the PIC processing. (DP7 O_Answer) An exception condition is encountered . Information being analysed e. Functions: . Routing address being interpreted.1. An exception condition is encountered. Exit events: . NOTE: The ODB category “Barring of outgoing calls when roaming” causes the HLR to send the category “BAOC” if the VLR is not in the HPLMN.Interface is idled. O-CSI is analysed.7. For this PIC.7.g. Continued processing of call setup (e. Example exception conditions are: Calling party abandons call.2.O_Disconnect) or default handling of exceptions by gsmSSF/(G)MSC completed.2 Analyse. Routing & Alerting Entry events: .1.g. ETSI .. the exception event is not visible because there is no corresponding DP. Originating call: SETUP message containing the dialled number is received from MS.Originating call: CUG checks done in the originating MSC/VLR are performed. The called party is busy. . Call is being processed by the terminating half BCSM.Originating CSI is analysed. The called party does not answer the call.Information being analysed and/or translated according to dialling plan to determine routing address.Indication from the terminating half BCSM that the call is accepted and answered by terminating party.Collected Info) Functions: .2.Originating CSI is analysed.1 O_Null & Authorise_Origination_Attempt_Collect_Info Entry events: . Exit events: . (DP2 . Originating call: Outgoing barring services and ODB categories not already applied are checked and invoked if necessary. Originating call: The supplementary services "barring of all outgoing calls" is checked and invoked if necessary. Example exception conditions are: Calling party abandons call.0 Release 1996) 16 TS 101 044 V5.Disconnect and clearing of a previous call (DP9 .(GSM 03.. ringing) is taking place.1214 [7] the specific descriptions differ. Attempt to select the route for the call fails.this leads to the O_Exception PIC.1.0 (1999-03) It should be noted that although the names used for PICs match those used in ITU-T Q.

4 O_Exception Entry events: . This includes general actions necessary to ensure no resources remain inappropriately allocated such as: If any relationship exists between the gsmSSF and the gsmSCF send an error information flow closing the relationships and indicating that any outstanding call handling instructions will not run to completion The (G)MSC/gsmSSF should make use of vendor-specific procedures to ensure release of resources within the (G)MSC/gsmSSF so that line.O_Disconnect) An exception condition is encountered.Indication from the terminating half BCSM that the call is accepted and answered by the terminating party. or received from the terminating party via the terminating half BCSM. trunk and other resources are made available for new calls.1.An exception condition is encountered. When encountering a DP the T-BCSM processing is suspended at the DP and the GMSC indicates this to the gsmSSF which determines what action if any should be taken in case of the DP is armed.0 Release 1996) 17 TS 101 044 V5.1 Terminating Basic Call State Model (T-BCSM) Description of T-BCSM The T-BCSM is used to describe the actions in a GMSC during terminating calls.3 7.A disconnection indication is received from the originating party. Functions: .2.1.O_Answer) Functions: . exception events include any type of failure that means that the normal exit events for a PIC can not be met.Connection established between originating and terminating party.78 version 5. In addition to specific examples listed above.0 (1999-03) 7. (DP9 . ETSI .2. Exit events: .(GSM 03.Default handling of the exception condition by gsmSSF/(G)MSC completed. 7.1. (DP7 . Exit events: . Call release is awaited.7.7.1. 7.3 O_Active Entry events: .3.Default handling of the exception condition is being provided.

1 T_Null Entry events: . Call is accepted and answered by terminating party EDP-N.78 version 5.0 (1999-03) T_Null T_Exception DP12 Terminating_Attempt_Authorised Terminating Call Handling DP15 DP17 T_Active T_Answer T_Disconnect Figure 7. 7. Table 2: Description of T-BCSM DPs in the GMSC CAMEL Detection Point: DP12 Terminating_Attempt_Authorised DP15 T_Answer DP17 T_Disconnect [7]: DP12 DP15 DP17 DP Type TDP-R EDP-N Description: Indication that the T-CSI is analysed.(GSM 03. The ODB categories "barring of all incoming calls" and "barring of incoming calls when roaming" are checked and ODB is invoked if necessary. ETSI .3.1.1. 7. ISUP_IAM is received. The supplementary service "CUG" is checked and invoked if necessary.3/1: T-BCSM in the GMSC In the following table the different DPs (in the T-BCSM) are described. the appropriate information is analysed. information available and exit events.Interface is idled. The supplementary services "barring of all incoming calls" and "barring of incoming calls when roaming" are checked and invoked if necessary. Send_Routeing_Info information flow is sent to HLR.Disconnect and clearing of a previous call (DP 17) or default handling of exceptions by gsmSSF/GMSC completed.0 Release 1996) 18 TS 101 044 V5.1.1214 [7] the specific descriptions differ.7. For each PIC a description can be found of the entry events. EDP. functions. Functions: . T-CSI is received and analysed.7.1 Description of the call model (PICs) This subclause describes the call model for terminating calls in the GMSC.3. It should be noted that although the names used for PICs match those used in ITU-T Q.A disconnect indication is received from R the terminating party or from the originating party.

(DP17 .Indication that the call is accepted and answered by the terminating party. exception events include any type of failure that means that the normal exit events for a PIC can not be met.Response is received from HLR and terminating CSI (if available) is analysed.0 Release 1996) 19 TS 101 044 V5. The call setup to the MSC/GMSC was not successful.3 T_Active Entry events: . or received from the originating party via the originating half BCSM.Response is received from HLR and terminating CSI (if available) is analysed. Example exception condition is: Calling party abandons call.1. Waiting for the call to be answered by terminating party.0 (1999-03) Exit events: .7. (DP15 . the exception event is not visible because there is no corresponding DP. if the call encounters one of these exceptions during the PIC processing.1.A disconnection indication is received from the terminating party. Call supervision is being provided. Routing address and call type being interpreted. The GSM supplementary service call forwarding is invoked if necessary. Call release is awaited.3. In addition to specific examples listed above.7.3. Exit events: . An exception condition is encountered. The next route is being selected.The response from HLR is analysed. Exit events: . ETSI . Example exception conditions are: Calling party abandons call. For this PIC. An exception condition is encountered . 7.2 Terminating Call Handling Entry events: .T_Answer) Functions: . (DP 12 Terminating_Attempt_Authorised) Functions: .Call is accepted and answered by terminating party.this lead to the T_Exception PIC.78 version 5.(GSM 03. 7. The terminating party is being alerted.1.Connection established between originating and terminating party.1.T_Disconnect) An exception condition is encountered.

gsmSCF (1) CAMEL relationship MSC gsmSSF/CCF O(A-B) A-Party T(A-B) B-Party Figure 7. 7. For each scenario the used and unused BCSMs involved in the call are shown.4/1: BCSM Scenario for Mobile Originated Call ETSI .1. other GSM subscribers or any other addressable subscriber. but the modelling is not changed. If optimal routing is invoked the physical configurations may be different from those shown. trunk and other resources are made available for new calls.An exception condition is encountered. In addition to specific examples listed above. This is not shown in these scenarios. A control relationship with gsmSCF (1) will be created.78 version 5. Exit events: .3.1 Mobile Originated Call The O-BCSM for the call from A to B (labelled "O(A-B)") is invoked if the A-party has an active O-CSI.4 T_Exception Entry events: .0 Release 1996) 20 TS 101 044 V5.7.4.1.7. the physical separation of the logic functions shown shall not impact the modelling.4 BCSM Modelling of Call Scenarios This subclause describes how the BCSMs defined above are used to model GSM call scenarios. However. exception events include any type of failure that means that the normal exit events for PIC cannot be met. 7. This subclause describes the call scenarios without optimal routing.0 (1999-03) 7. This includes general actions necessary to ensure no resources remain inappropriately allocated such as: If any relationship exists between the gsmSSF and the gsmSCF send an error information flow closing the relationships and indicating that any outstanding call handling instructions will not run to completion The GMSC/gsmSSF should make use of vendor-specific procedures to ensure release of resources within the GMSC/gsmSSF so that line.Default handling of the exception condition by gsmSSF/GMSC completed.(GSM 03. Subscribers other than those being served by CAMEL may be either PSTN subscribers. Functions: . CAMEL may be applied simultaneously and independently for each GSM subscriber involved in a call.Default handling of the exception condition is being provided. In some cases these models may have an allocation to physical nodes different from that shown.

A new call leg to a "C" party is created if: a GSM call forwarding supplementary service forwards the call to C.78 version 5.7.3 Call Forwarding at the GMSC The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI.4/2: BCSM Scenario for Mobile Terminated Calls 7.4. The nodes gsmSCF (1) and gsmSCF (2) may be the same or different physical entities. The relationships with gsmSCF (1) and gsmSCF(2) may exist simultaneously. The two relationships are treated independently at the GMSC.0 Release 1996) 21 TS 101 044 V5. In this case an O-BCSM is always invoked for the forwarding party if an O-CSI has been received by the GMSC from the HLR. The BCSM T(A-B) and BCSM O(B-C) are linked by an internal interface which is assumed to behave in a similar way to an ISUP interface. A control relationship with gsmSCF (1) will be created. or a CAMEL service in a control relationship with T(A-B) performs a CAMEL-based call forwarding by using a Connect information flow containing the the forwarding information. A control relationship with gsmSCF (1) will be created.4. gsmSCF (1) CAMEL relationship GMSC gsmSSF/CCF O(A-B) A-Party T(A-B) MSC gsmSSF/CCF B-Party Figure 7. ETSI .2 Mobile Terminated Call The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI. In this case an O-BCSM is only invoked for the forwarding party if an O-CSI has been received by the GMSC from the HLR and ‘O-CSI Applicable’ flag is contained in the Connect information flow.0 (1999-03) 7. A control relationship with gsmSCF (2) will be created.7.(GSM 03.

7. A control relationship with gsmSCF (2) will be created. gsmSCF (1) CAMEL relationship (1) gsmSCF (2) CAMEL relationship (2) GMSC gsmSSF/CCF O(A-B) A-Party T(A-B) MSC gsmSSF/CCF T(B-C) C-Party O(B-C) B-Party "Surrogate" Figure 7. A control relationship with gsmSCF (1) will be created.4.4/3: BCSM Scenario for Call Forwarding at the GMSC 7. The relationships with gsmSCF (1) and gsmSCF(2) may exist simultaneously. Following processing at the GMSC the call will be extended to the MSC serving the B-party.7.4 Call Forwarding at the MSC The T-BCSM for the call from A to B (labelled "T(A-B)") is invoked if the B-party has an active T-CSI.(GSM 03.78 version 5.0 (1999-03) gsmSCF (1) CAMEL relationship (1) gsmSCF (2) CAMEL relationship (2) GMSC gsmSSF/CCF O(A-B) A-Party T(B-C) C-Party O(B-C) T(A-B) Internal "ISUPlike" interface B-Party "surrogate" Figure 7.4/4: BCSM Scenario for Call Forwarding at the MSC ETSI . a new call leg to C is established. The nodes gsmSCF (1) and gsmSCF (2) may be the same or different physical entities. but it is shown as being separate in the diagram below. This MSC may be physically integrated with the GMSC. If the B-party has an active O-CSI the BCSM O(B-C) is invoked. If a GSM call forwarding supplementary service acting at the MSC forwards the call to C.0 Release 1996) 22 TS 101 044 V5.

The procedures specific to CAMEL are specified in this subclause.1.2 Actions on receipt of Int_Error The MSC checks the default Call Handling parameter in O-CSI.1. 8.1.1.4 8. sends a Send Info For Outgoing Call to the VLR and waits in state Wait_For_MO_Call_Result_2. If the default call handling is to release the call. The MSC shall transparently modify the call parameters with the received information.5 Procedure CAMEL_OCH_MSC_DISC1 Procedure CAMEL_OCH_MSC_DISC2 Procedure CAMEL_OCH_MSC_DISC3 ETSI .18 [3]. the MSC continues processing without CAMEL support. 8.0 (1999-03) 8 8.1.1. 8.4 Actions on receipt of Int_Connect The MSC continues processing with modified call parameters. 8. Generic Number.(GSM 03.1. If the default call handling is to continue the call. The procedure returns a Fail result. Original Called Party Number and Redirecting Party ID to be ignored or modified. It sets the O-CSI suppression parameter.1.78 version 5.1 Procedures for CAMEL Handling of mobile originated calls Handling of mobile originated calls in the originating VMSC The functional behaviour of the originating VMSC is specified in GSM 03.1.1 8. The MSC sets the O-CSI suppression parameter.1. a Release transaction is sent to the MS and an Abort to the VLR. sends a Send Info For Outgoing Call to the VLR and waits in state Wait_For_MO_Call_Result_2.3 8. Call parameters which are not included in the Int_Connect message are unchanged.2 Procedure CAMEL_OCH_MSC_ANSWER The procedure Send_Access_Connect_If_Required is specified in GSM 03.1.7.7. The release cause received in the Int_Release_Call is used.1.1.1.0 Release 1996) 23 TS 101 044 V5.1 Procedure CAMEL_OCH_MSC_INIT A Release_Transaction is sent to the MS and an Abort to the VLR.1. The procedure returns a Fail result.3 Actions on receipt of Int_Continue The MSC continues processing without any modification of call parameters. 8. Signalling limitations or regulatory requirements may require the Calling Partys Category.1. sends a Send Info For Outgoing Call to the VLR and waits in state Wait_For_MO_Call_Result_2.1. The MSC then sends a PROGRESS message to the MS.1. It sets the OCSI suppression parameter.18 [3].1. 8.1.

78 version 5.0 Release 1996) 24 TS 101 044 V5.0 (1999-03) Procedure CAMEL_OCH_MSC_INIT Procedure in the originating VMSC to perform initial CAMEL handling for an outgoing call request CAM_OMI1(2) Signals to/from the right are to/from the gsmSSF O-CSI invocation? No Yes Result:= Pass Allocate call reference number Store original call parameters Int_Invoke_gsmSSF (O-CSI) Wait_for_ gsmSSF_ Invoked Int_gsmSSF_ Invoked Int_DP_ Collected_ Info DP_ _Collected_ _Info Figure 8.7.1-1: Procedure CAMEL_OCH_MSC_INIT (sheet 1 of 2) ETSI .7.(GSM 03.

Int_Release_Call Int_Error Int_Continue Int_Connect No Default call handling= continue call ? Yes Send_ Alerting_If_ Required See GSM 03.7.18 Modify call parameters with received information Set O-CSI Suppression Abort To VLR Send Info For Outgoing Call To VLR Wait_For MO_Call_ Result_2 Send Info For Outgoing Call negative response From VLR Complete Call From VLR Int_DP_O_Exception Result:=Pass Release transaction DP_Collected_Info Wait_For_MO_Call_Result_2 Wait_for_gsmSSF_Invoked Result:=Fail Release transaction Int_O-Exception Result:= Fail Figure 8. signals to/from the right are to/from the gsmSSF if not otherwise stated.0 Release 1996) 25 TS 101 044 V5.(GSM 03.1-2: Procedure CAMEL_OCH_MSC_INIT (sheet 2 of 2) ETSI .0 (1999-03) Procedure CAMEL_OCH_MSC_INIT Procedure in the originating VMSC to perform initial CAMEL handling for an outgoing call request DP_ Collected_ Info CAM_OMI2(2) Signals to/from the left are to/from the BSS.7.78 version 5.

78 version 5. signals to/from the right are to/from the gsmSSF if not otherwise stated.0 (1999-03) Procedure CAMEL_OCH_MSC_ANSWER Procedure in the originating VMSC to handle an answer for a CAMEL call CAM_OMA1(1) Signals to/from the left are to/from the BSS.(GSM 03.18 Send_Access_ Connect_If_ Required Rlease transaction CAMEL_OCH_ MSC_DISC1 CAMEL_OCH_ MSC_DISC2 No Release To destination exchange Result:= Pass Result:= Fail Figure 8.7.7.0 Release 1996) 26 TS 101 044 V5.1-3: Procedure CAMEL_OCH_MSC_ANSWER ETSI . gsmSSF exists? Yes Int_DP_O_Answer DP_O_Answer Int_Continue Int_Rlease_ Call Release transaction Release From destination exchange See GSM 03.

0 (1999-03) Procedure CAMEL_OCH_MSC_DISC_1 Procedure in the origi to perform CAMEL ha from the originating en CAMOD1_1(1) Signals to/from the left are to/from the BSS.0 Release 1996) 27 TS 101 044 V5. signals to/from the right are to/from the gsmSSF if not otherwise stated.(GSM 03.78 version 5.7.7. No gsmSSF exists? Yes Int_DP_O_ Disconnect /* legId = 1 */ DP_O_ Disconnect_1 Int_Error Int_Continue Int_Release_Call Release From destination exchange Int_DP_O_ Disconnect /* legId = 2 */ Release To destination exchange DP_O_ Disconnect Int_Error Int_Continue Int_Release_Call Result:= Normal_ handling Result:= CAMEL_ handling Figure 8.1-4: Procedure CAMEL_OCH_MSC_DISC1 ETSI .

0 (1999-03) Procedure CAMEL_OCH_MSC_DISC_2 Procedure in the originating VMSC to perform CAMEL handling for a call release from the destination end CAMOD2_1(1) Signals to/from the left are to/from the BSS. signals to/from the right are to/from the gsmSSF No gsmSSF exists? Yes Int_DP_O_ Disconnect /* legId = 2 */ DP_O_ Disconnect_2 Release transaction Int_Continue Int_Release_Call Int_Error Int_DP_O_ Disconnect /* legId = 1 */ DP_O_ Disconnect Int_Error Int_Continue Int_Release_Call Release transaction Result:= Normal_ handling Result:= CAMEL_ handling Result:= CAMEL_ handling Figure 8.7.7.(GSM 03.1-5: Procedure CAMEL_OCH_MSC_DISC2 ETSI .0 Release 1996) 28 TS 101 044 V5.78 version 5.

78 version 5.0 Release 1996) 29 TS 101 044 V5.0 (1999-03) Procedure CAMEL_OCH_MSC_DISC3 Procedure in the originating VMSC to handle premature release of a CAMEL call CAMOD3_1(1) No gsmSSF exists? Yes Int_O_ Exception To gsmSSF Figure 8.(GSM 03.7.1-6: Procedure CAMEL_OCH_MSC_DISC3 ETSI .7.

(GSM 03.7.18 [3].78 version 5.0 Release 1996) 30 TS 101 044 V5.1 Procedure CAMEL_OCH_VLR CAMOVLR1(1) Signals to/from the left are to/from the VMSC Procedure CAMEL_OCH_VLR Procedure in the originating VLR to handle an originating CAMEL call request Complete call Wait_For_ SIFOC_2 Abort Send Info For Outgoing Call Result:= Fail Result:= Pass Figure 8.2.1. The procedure specific to CAMEL is specified in this subclause.1.0 (1999-03) 8.7. 8.2 Handling of mobile originated calls in the originating VLR The functional behaviour of the originating VLR is specified in GSM 03.1-7: Procedure CAMEL_OCH_VLR ETSI .

(GSM 03. The further processing is described in subclause 8. any other parameters (Calling Partys Category and Generic Number) received in the Connect message are used to overwrite the corresponding ISUP parameters (for mapping see GSM 09. then an exception event is reported to the process gsmSSF.2 8.18 [3].1 8.3 Action on receipt of Int_Continue If an FTN has been stored the information received from the HLR is used to overwrite the corresponding call parameters. The procedures specific to CAMEL are specified in this subclause. Note that the MSISDN is replaced by the FTN as the Called party number. i. If: the Destination Number received from the gsmSCF (via the gsmSSF) is not the same as the stored ISUP Called party number.2.78 version 5.1. the Announcement Suppression Indicator is stored.0 Release 1996) 31 TS 101 044 V5. if received. a Send Routeing Info message including a T-CSI suppression parameter is sent to the HLR. If the default call handling is to release the call. The redirection counter is incremented. Original Called Party ID.e.2.2.2. Otherwise the following parameters.2. 8. are used to overwrite the corresponding ISUP parameters (for mapping see GSM 09. the MSISDN.3. If received.1 Procedure CAMEL_Set_ORA_Parameters Procedure CAMEL_MT_GMSC_INIT Action on receipt of Int_Release_Call The procedure returns a Fail result.1.18 [3].2 Action on receipt of Int_Error The GMSC checks the default Call Handling parameter in T-CSI. i. 8.3 with the addition that the Announcement Suppression indicator. and CUG information was received in the ISUP_IAM for the incoming call.2.e.2 8. If the Destination Number received from the gsmSCF (via the gsmSSF) is the same as the ISUP Called Party Number.4 Action on receipt of Int_Connect The GMSC shall send an ACM towards the originating exchange in order to stop any call timers.2.1. Redirecting Party ID and Redirection Information. the MSISDN. Call parameters which are not included in the Int_Connect message are unchanged. Generic Number.78 [6]): Destination Number.2. 8.2. is sent to the HLR in the Send_Routeing_Info message.1. the procedure returns a Fail result. the GMSC continues call handling without CAMEL support as described in subclause 8.2. The procedure Send_ACM_If_Required is specified in GSM 03. If the default call handling is to continue the call.1. If no FTN has been stored.0 (1999-03) 8.1.2.7. and a CUG active indication was received from the HLR. The Send Routeing Info includes a parameter to indicate which phase of CAMEL is supported by the GMSC/gsmSSF.1 Retrieval of routeing information Retrieval of routeing informationin the GMSC The functional behaviour of the GMSC is specified in GSM 03. Calling Partys Category.1.2.78 [6]). 8.2. if stored.1. and the procedure returns a Fail result.2.2. ETSI .7.

8.2.2..2. The procedure returns the FTN as the result.2. The O-CSI is passed to the process MT_CF_MSC in the Perform Call Forwarding request. 8.1. The procedure returns the FTN as the result.7.2.2.3 8.1.7.2.0 Release 1996) 32 TS 101 044 V5.1.1.78 version 5.1. if the Redirection counter has been decreased).8 Send Routeing Info ack with O-CSI and FTN in state Wait_For_Routeing_Info_2 The redirection counter is incremented.1. If the Announcement Suppression indicator has been received from the gsmSCF (via the gsmSSF) any announcements or tones shall be suppressed.0 (1999-03) As a network option loop prevention mechanisms may cause the redirection information to be ignored or modified (e.6 Procedure CAMEL_MT_GMSC_ANSWER Procedure CAMEL_MT_GMSC_DISC1 Procedure CAMEL_MT_GMSC_DISC2 Procedure CAMEL_MT_GMSC_DISC3 ETSI . Signalling limitations or regulatory requirements may require the Calling Partys Category.(GSM 03.5 8.4 8.7 Send Routeing Info ack with FTN in state Wait_For_Routeing_Info_2 The redirection counter is incremented. Generic Number.2.1. 8. 8. Original Called Party Number and Redirecting Party ID to be ignored or modified.2. The procedure returns a Fail result.5 Send Routeing Info negative response in state Wait_For_Routeing_Info_2 An exception event is reported to the process gsmSSF.2.1.6 Send Routeing Info ack with MSRN in state Wait_For_Routeing_Info_2 The procedure returns the MSRN as the result.g.2. 8.2.

7.7.78 version 5.0 (1999-03) Procedure CAMEL_Set_ORA_Parameters Procedure in the GMSC to set CAMEL parameters for the procedure Obtain_Routeing_Address CSORAP1(1) No gsmSSF exists? Yes Yes Call reference number allocated? No Allocate call reference number Figure 8.2-1: Procedure CAMEL_Set_ORA_Parameters ETSI .0 Release 1996) 33 TS 101 044 V5.(GSM 03.

7.2-2: Procedure CAMEL_MT_GMSC_INIT (sheet 1 of 4) ETSI .0 (1999-03) Procedure CAMEL_MT_GMSC_INIT Procedure in the GMSC to perform the initial handling for a CAMEL MT call CAM_TGI1(4) No CAMEL information received in SRI ack? Yes No MSRN received? Yes No FTN received? Yes Result:= MSRN Result:= FTN Result:= Fail Content of SRI ack T-CSI Set CSI=T-CSI T-CSI & O-CSI Set CSI=T-CSI T-CSI & FTN Set CSI=T-CSI T-CSI & O-CSI & FTN Set CSI=T-CSI O-CSI & FTN Set CSI=O-CSI Store O-CSI Store FTN Store O-CSI & FTN Set redirection information Int_Invoke_ gsmSSF (CSI) To gsmSSF Result:= FTN Wait_For_ gsmSSF_ Invoked Figure 8.(GSM 03.78 version 5.0 Release 1996) 34 TS 101 044 V5.7.

0 (1999-03) Procedure CAMEL_MT_GMSC_INIT Procedure in the GMSC to perform the initial handling for a CAMEL MT call Wait_For_ gsmSSF_ Invoked CAM_TGI2(4) Release Int_gsmSSF invoked Int_Error Int_T_ Exception Int_DP_ Termination attempt authorised Result:= Aborted Result:= Fail DP_Termination_ Attempt_ Authorised Figure 8.2-3: Procedure CAMEL_MT_GMSC_INIT (sheet 2 of 4) ETSI .7.0 Release 1996) 35 TS 101 044 V5.(GSM 03.78 version 5.7.

signals to/from the right are to/from the gsmSSF unless marked otherwise Release Int_ Continue Int_Connect Int_Release_ Call Int_Error No Int_T_ Exception Send_ACM_ If_Required Yes Default Call Handling= Continue Call? No Result:= Aborted Modify call parameters with received information Destination address modified? Yes Result:= Fail 1 1 Yes FTN stored? No Original Cd party subscribed to CUG? Yes No Set redirection information Set T-CSI suppression CUG info received for incoming call? Yes No 2 Send Routeing Info To HLR Int_T_ Exception Modify call parameters with received information Wait_For_ Routeing_ Info_2 Result:= Fail 2 Apply_O-CSI indicator present? Yes No No O-CSI stored? Yes FTN:= Destination address CMN:= Destination address Result:= FTN Result:= CMN Figure 8.0 (1999-03) Procedure CAMEL_MT_GMSC_INIT Procedure in the GMSC to perform the initial handling for a CAMEL MT call DP_Termination_ Attempt_ Authorised CAM_TGI3(4) Signals to/from the left are to/from the originating exchange.78 version 5.0 Release 1996) 36 TS 101 044 V5.(GSM 03.7.7.2-4: Procedure CAMEL_MT_GMSC_INIT (sheet 3 of 4) ETSI .

0 Release 1996) 37 TS 101 044 V5.2-5: Procedure CAMEL_MT_GMSC_INIT (sheet 4 of 4) ETSI .(GSM 03. signals to/from the right are to/from the gsmSSF unless marked otherwise Release Send Routeing Info negative response From HLR Int_Release Call Send Routeing Info ack From HLR Int_T_ Exception Int_T_ Exception Content of SRI ack MSRN Result:= Aborted Result:= Fail Result:= MSRN FTN Result:= FTN FTN & O-CSI Result:= FTN Figure 8.78 version 5.7.7.0 (1999-03) Procedure CAMEL_MT_GMSC_INIT Procedure in the GMSC to perform the initial handling for a CAMEL MT call Wait_For_ Routeing_ Info_2 CAM_TGI4(4) Signals to/from the left are to/from the originating exchange.

2-6: Procedure CAMEL_MT_GMSC_ANSWER ETSI . signals to/from the right are to/from the destination exchange unless marked otherwise No gsmSSF exists? Yes Result:= Pass Int_DP_T_ Answer To gsmSSF DP_T_Answer Int_Release From gsmSSF Int_Continue From gsmSSF Release Release Release CAMEL_MT_ GMSC_DISC1 CAMEL_MT_ GMSC_DISC2 Release Result= CAMEL handling? No Yes Yes Result= CAMEL handling? No Release Release Result:= Fail Result:= Pass Result:= Fail Figure 8.7.0 Release 1996) 38 TS 101 044 V5.78 version 5.7.(GSM 03.0 (1999-03) Procedure CAMEL_MT_GMSC_ANSWER Procedure in the GMSC to handle answer for a CAMEL call CAM_TGA1(1) Signals to/from the left are to/from the originating exchange.

0 Release 1996) 39 TS 101 044 V5.2-7: Procedure CAMEL_MT_GMSC_DISC1 ETSI .0 (1999-03) Procedure CAMEL_MT_GMSC_DISC1 Procedure in the GMSC to perform CAMEL handling for a call release from the originating end CAMTD1_1(1) Signals to/from the right are to/from the gsmSSF if not otherwise stated.(GSM 03.7.78 version 5. No gsmSSF exists? Yes Int_DP_T_ Disconnect /* legId = 1 */ DP_T_ Disconnect_1 Int_Error Int_Continue Int_Release_Call Release From destination exchange or process MT_CF_MSC Int_DP_T_ Disconnect /* legId = 2 */ Release To destination exchange or process MT_CF_MSC DP_T_ Disconnect Int_Error Int_Continue Int_Release_Call Result:= Normal handling Result:= CAMEL handling Figure 8.7.

7.(GSM 03.0 Release 1996) 40 TS 101 044 V5.0 (1999-03) Procedure CAMEL_MT_GMSC_DISC2 Procedure in the GMSC to perform CAMEL handling for a call release from the destination end CAMTD2_1(1) Signals to/from the left are to/from the originating exchange.2-8: Procedure CAMEL_MT_GMSC_DISC2 ETSI . signals to/from the right are to/from the gsmSSF No gsmSSF exists? Yes Int_DP_T_ Disconnect /* legId = 2 */ DP_T_ Disconnect_2 Release Int_Continue Int_Release_Call Int_Error Int_DP_T_ Disconnect /* legId = 1 */ DP_T_ Disconnect Int_Error Int_Continue Int_Release_Call Release Result:= Normal handling Result:= CAMEL handling Result:= CAMEL handling Figure 8.78 version 5.7.

7.7.2-9: Procedure CAMEL_MT_GMSC_DISC3 ETSI .0 (1999-03) Procedure CAMEL_MT_GMSC_DISC3 Procedure in the GMSC to handle premature release of a CAMEL call CAMTD3_1(1) No gsmSSF exists? Yes Int_T_ Exception To gsmSSF Figure 8.78 version 5.0 Release 1996) 41 TS 101 044 V5.(GSM 03.

2 8.3 Procedure CAMEL_HLR_INIT Procedure CAMEL_CSI_Check_HLR Procedure CAMEL_T_CSI_CHECK_HLR The procedure Provide_Subscriber_Info_HLR is specified in subclause 8.2.0 (1999-03) 8.78 version 5.2.7.2.4 Procedure CAMEL_O_CSI_CHECK_HLR ETSI .0 Release 1996) 42 TS 101 044 V5.1 8. 8.7.7.2.2 Retrieval of routeing information in the HLR The functional behaviour of the HLR is specified in GSM 03.2.2.2.18 [3].(GSM 03. 8. The procedures specific to CAMEL are specified in this subclause.2.2.

0 (1999-03) Procedure CAMEL_HLR_INIT Procedure in the HLR to perform the initial handling for an MT CAMEL call CAMHLRI1(1) No CAMEL subscriber? Yes Yes GMSC supports CAMEL phase 1? No Default handling? Bar call Set negative response: Call barred Continue Network specific Network specific action Including setting the result Result:= Pass Result:= Fail Result:= Pass Figure 8.7.2-8: Procedure CAMEL_HLR_INIT ETSI .78 version 5.7.0 Release 1996) 43 TS 101 044 V5.(GSM 03.

0 Release 1996) 44 TS 101 044 V5.7.0 (1999-03) Procedure CAMEL_CSI_Check_HLR Procedure in the HLR to check O-CSI & T-CSI for an MT call CCC_HLR1(1) CAMEL_T_CSI_ CHECK_HLR Result= T-CSI active? Yes No CAMEL_O_CSI_ CHECK_HLR Result:= CSI active Result:= Continue Figure 8.(GSM 03.7.78 version 5.2-9: Procedure CAMEL_CSI_Check_HLR ETSI .

7.0 (1999-03) Procedure CAMEL_T_CSI_CHECK_HLR Procedure in the HLR to check the T-CSI & set the SRI ack parameter accordingly CAMTCSI1(1) No T-CSI provisioned? Yes Yes Suppress T-CSI? No Subscriber info required? Yes No Provide_ Subscriber_ Info_HLR Set T-CSI parameter Result:= T-CSI active Result:= Continue Figure 8.2-10: Procedure CAMEL_T_CSI_CHECK_HLR ETSI .7.78 version 5.(GSM 03.0 Release 1996) 45 TS 101 044 V5.

7.7.2.78 version 5.3 Handling of provide roaming number request in the VLR The functional behaviour of the VLR is specified in GSM 03. The procedure specific to CAMEL is specified in this subclause.0 Release 1996) 46 TS 101 044 V5.0 (1999-03) Procedure CAMEL_O_CSI_CHECK_HLR Procedure in the HLR to check the O-CSI & set the SRI ack parameter accordingly CAMOCSI1(1) No O-CSI provisioned? Yes Set O-CSI parameter Figure 8. ETSI .18 [3].2-11: Procedure CAMEL_O_CSI_CHECK_HLR 8.(GSM 03.

2.1 Procedure CAMEL_SET_SOA CAMSOA1(1) Procedure CAMEL_SET_SOA Procedure in the VLR to set the Suppression of Announcements indicator as required for this call No Suppression of Announcements required? Yes Suppression of Announcements required:=False Suppression of Announcements required:=True Figure 8.78 version 5.7.(GSM 03.7.2-16: Procedure CAMEL_SET_SOA ETSI .0 (1999-03) 8.0 Release 1996) 47 TS 101 044 V5.3.

the inclusion of the suppression of announcements parameter in the Send Info For Incoming Call negative response if it was received in the Provide Roaming Number.18 [3]. if the Redirection counter has been decreased). 8.3 8.18 [3].4.4 respectively.78 version 5.1 Handling of mobile terminated calls Handling of mobile terminated calls handling in the terminating VMSC The functional behaviour of the terminating VMSC is specified in GSM 03. 8.0 (1999-03) 8.7.0 Release 1996) 48 TS 101 044 V5. As a network option. The only behaviour specific to CAMEL is: the inclusion of the O-CSI parameter in the Perform Call Forwarding message sent to the process MT_CF_MSC if it was received in the Send Info For Incoming Call ack.3. ETSI . 8. Original Called Party Number and Redirecting Party ID to be ignored or modified.1.4 Handling of forwarded calls The handling of forwarded calls in the GMSC or the terminating VMSC is specified in GSM 03. Call parameters which are not included in the Int_Connect message are unchanged.g.(GSM 03.4.1. loop prevention mechanisms may cause the redirection information to be ignored or modified (e.3. as an implementation option.1. the inclusion of the suppression of announcements parameter in the Send Info For Incoming Call ack if it was received in the Provide Roaming Number.1. Generic Number.2 Handling of mobile terminated calls in the terminating VLR The functional behaviour of the terminating VLR is specified in GSM 03. 8. the requirement to suppress the connection of announcements or tones if the VLR includes the suppression of announcements parameter in the Send Info For Incoming Call ack or Send Info For Incoming Call negative response.18 [3].7. The procedures specific to CAMEL are specified in this subclause.3 & 8.2 Procedure CAMEL_CF_ANSWER The procedures CAMEL_OCH_MSC_DISC1 & CAMEL_OCH_MSC_DISC2 are specified in subclauses 8. Signalling limitations or regulatory requirements may require the Calling Partys Category.78 [6]). The only behaviour specific to CAMEL is: the inclusion of the O-CSI parameter in the Send Info For Incoming Call ack if the call is to be forwarded and OCSI is included in the subscriber data for that subscriber in the VLR.1 Procedure CAMEL_CF_INIT Sheet 3: the parameters received in the Int_Connect message are used to overwrite the corresponding ISUP parameters (for mapping see GSM 09.

0 (1999-03) Procedure CAMEL_CF_MSC_INIT Procedure in the MSC to perform the initial CAMEL handling for a forwarded call CAMCMI1(3) Signals to/from the left are to/from the parent process.(GSM 03.7.4-1: Procedure CAMEL_CF_MSC_INIT (sheet 1 of 3) ETSI .78 version 5.7.0 Release 1996) 49 TS 101 044 V5. signals to/from the right are to/from the gsmSSF No O-CSI stored? Yes Result:= Pass Int_Invoke gsmSSF (O-CSI) Wait_For_ gsmSSF_Invoked CF cancelled Int_gsmSSF invoked Int_Error Int_O_ Exception Int_DP_ Collected_ Info Release Result:= Cancelled Result:= Fail DP_Collected_ Info Figure 8.

7.7.(GSM 03.78 version 5.4-2: Procedure CAMEL_CF_MSC_INIT (sheet 2 of 3) ETSI .0 (1999-03) Procedure CAMEL_CF_MSC_INIT Procedure in the MSC to perform the initial CAMEL handling for a forwarded call DP_Collected_ Info CAMCMI2(3) Signals to/from the left are to/from the parent process. signals to/from the right are to/from the gsmSSF Int_Release call Int_Error Int_Continue Int_Connect No Default Call Handling= Continue Call? Yes Modify call parameters with received information Release Result:= Fail Result:= Pass Figure 8.0 Release 1996) 50 TS 101 044 V5.

7.7.0 Release 1996) 51 TS 101 044 V5. signals to/from the right are to/from the gsmSSF CF cancelled Int_O_Exception Result:= Cancelled Figure 8.4-3: Procedure CAMEL_CF_MSC_INIT (sheet 3 of 3) ETSI .(GSM 03.0 (1999-03) Procedure CAMEL_CF_MSC_INIT Procedure in the MSC to perform the initial CAMEL handling for a forwarded call DP_Collected_ Info CAMCMI3(3) Signals to/from the left are to/from the parent process.78 version 5.

(GSM 03.78 version 5.7.0 Release 1996)

52

TS 101 044 V5.7.0 (1999-03)

Procedure CAMEL_CF_MSC_ANSWER
Procedure in the MSC to perform CAMEL handling for answer of a forwarded call

CAMCMA1(1)
Signals to/from the left are to/from the originating exchange; signals to/from the right are to/from the gsmSSF unless marked otherwise

No gsmSSF exists? Yes

Result:= Pass

Int_DP_O_ Answer

DP_O_Answer

Release

Release

From destination exchange

Int_Release

Int_Continue

CAMEL_OCH_ MSC_DISC1

CAMEL_OCH_ MSC_DISC2

Result= CAMEL handling? No

Yes

Yes

Result= CAMEL handling? No

Release

To destination exchange

Release

To destination exchange

Release

Release

Result:= Fail

Result:= Pass

Figure 8.4-4: Procedure CAMEL_CF_MSC_ANSWER

ETSI

(GSM 03.78 version 5.7.0 Release 1996)

53

TS 101 044 V5.7.0 (1999-03)

8.5
8.5.1

Handling of mobile calls in the gsmSSF
State Idle

The following actions are possible in the state Idle (shown in sheet 1):

8.5.1.1

Int_Invoke_gsmSSF

DP_Collected_Info or DP_Terminating_Attempt_Authorised is armed as an TDP, depending if T-CSI or O-CSI is received in Int_Invoke_gsmSSF. The gsmSSF returns a confirmation to the GMSC/MSC and waits in Wait_For_Request.

8.5.1.2

Int_DP_O/T_Answer or Int_DP_O/T_Disconnect

An Int_Continue is sent to the GMSC/MSC and the process gsmSSF returns to idle. This may occur when previous relationship with the gsmSCF has been terminated.

8.5.1.3

Int_O/T_Exception

The process gsmSSF returns directly to idle. This may occur when previous relationship with the gsmSCF has been terminated.

8.5.2
8.5.2.1

State Wait_For_Request
Int_DP_Collected_Info

The gsmSSF opens a control relationship with the gsmSCF by sending CAP_InitialDP. The gsmSSF waits in state Waiting_For_Instructions.

8.5.2.2

DP_Terminating_Attempt_Authorised

See subclause 8.5.2.1.

8.5.2.3

Int_O/T_Exception

The process gsmSSF returns directly to idle.

8.5.3
8.5.3.1

Waiting_For_Instructions
CAP_Request_Report_BCSM_Event

The gsmSSF arms the requested EDP, if the arming rules are fulfilled and returns to state Waiting_For_Instructions. The gsmSCF may request monitor for answer or/and disconnect of a party in the call. O/T_Answer may only be armed as EDP-N. O/T_Disconnect may be armed as an EDP-N or an EDP-R.

8.5.3.2

CAP_Continue

An Int_Continue is sent to request the GMSC/MSC to continue call set-up as originally requested. If DP_Disconnect is armed as an EDP-R the relationship with gsmSCF remains a control relationship and gsmSSF waits in state Monitoring., if DP Answer or DP Disconnect is armed as EDP-N the relationship is changed to a monitor relationship and gsmSSF waits in state Monitoring. If no remaining EDPs are armed, the control relationship between gsmSSF and the gsmSCF is terminated. The process gsmSSF returns to idle.

ETSI

(GSM 03.78 version 5.7.0 Release 1996)

54

TS 101 044 V5.7.0 (1999-03)

8.5.3.3

CAP_Connect

If the current DP is DP2 or DP12 an Int_Connect is sent to request the GMSC/MSC to continue the call setup with modified information. If DP_Disconnect is armed as an EDP-R the relationship with gsmSCF remains a control relationship and gsmSSF waits in state Monitoring., if DP Answer or DP Disconnect is armed as EDP-N the relationship is changed to a monitor relationship and gsmSSF waits in state Monitoring. If no remaining EDPs are armed, the control relationship between gsmSSF and the gsmSCF is terminated. The process gsmSSF returns to idle. If the current DP is not DP2 or DP12 an error is sent to the gsmSCF and the gsmSSF returns to the state Waiting_For_Instructions.

8.5.3.4

CAP_Release_Call

If CAP_Release_Call is received in the state Wait_For_Instructions, an Int_Release_Call is sent to the GMSC/MSC to release the call.

8.5.3.5

Timer expire

If the gsmSSF timer expires the transaction to the gsmSSF is aborted and an Int_Error is sent to the GMSC/MSC.

8.5.3.6

Int_O/T_Exception

If the gsmSSF receives an Int_Exception from the GMSC/MSC, its terminates the control relationship, sends Int_Continue to GMSC/MSC and returns to idle.

8.5.3.7

Int_DP_O/T_Disconnect

If the DP is armed for the leg indicated in Int_O/T_DP_Disconnect, a CAP_Event_Report_BCSM is sent to the gsmSCF and gsmSSF returns to state Waiting_For_Instructions.

8.5.4
8.5.4.1

Monitoring
Int_DP_O/T-Answer

If Int_DP_O/T_Answer is received, then the gsmSSF if the EDP-N is armed sends CAP_Event_Report_BCSM (Notify and Continue). If no other EDP is armed, the relationship with the gsmSCF is terminated and the process returns to idle. If armed EDPs still exist, the process returns to Monitoring.

8.5.4.2

Int_DP_O/T_Disconnect

If Int_DP_O/T_Disconnect is received and no EDP is armed for this DP then an Int_Continue is sent to the GMSC/MSC. If Int_DP_O/T_Disconnect is received and this DP is armed as EDP-N for the leg indicated in Int_DP_Disconnect, then the CAP_Event_Report_BCSM (notify and continue) is sent to the gsmSCF and an Int_Continue is sent to the GMSC/MSC. If no other EDP is armed, the relationship with the gsmSCF is terminated and the process returns to idle. If armed EDPs still exist, the process returns to Monitoring.

ETSI

(GSM 03.78 version 5.7.0 Release 1996)

55

TS 101 044 V5.7.0 (1999-03)

If Int_DP_O/T Disconnect is received and this DP is armed as EDP-R for the leg indicated in Int_DP_Disconnect, then the CAP_Event_Report_BCSM (interrupted) is sent to the gsmSCF and the gsmSSF waits in state Waiting_For_Instructions.

8.5.4.3

CAP_Release_Call

When a control relationship exists between the gsmSCF and gsmSSF (at least one EDP-R is armed), the gsmSCF may spontaneously instruct the gsmSSF to release the call at any time using the Release Call IF. The Release Call IF shall not be sent from the gsmSCF if only monitor relationship exists between the gsmSSF and the gsmSCF.

8.5.4.4

Int_O/T_Exception

If the gsmSSF receives an Exception event from the GMSC/MSC, it terminates the relationship (monitoring or control) with the gsmSCF and returns to idle.

8.5.5

Actions of the process gsmSSF in error cases

The detailed error handling for the process gsmSSF is specified in GSM 09.78.

ETSI

Int_Continue Int_gsmSSF Invoked Idle Idle Wait_For_ _Request Int_DP_ _Collected_ _Info Int_DP_ _Terminating_ _Attempt_ _Authorised Int_T_Exception or Int_O_Exception Start Tssf Open Control Relationship Idle CAP_InitialDP Waiting_For_ _Instructions Figure 8. 1(6) Idle Int_Invoke gsmSSF (CSI) Int_DP_O_Answer Int_DP_T_Answer Int_DP_O_Disconnect Int_DP_T_Disconnect Int_O_Exception Int_T_Exception Arm DP The received CSI states whether DP Collected_Info or DP Terminating_Attempt_ _Authorised shall be armed as TDP.0 Release 1996) 56 TS 101 044 V5. Signals to/from the left are to/from the processes CAMEL_MT_GMSC.5-1 gsmSSF (sheet 1 of 6) ETSI . CAMEL_OCH_ _MSC and CAMEL_CF_MSC.(GSM 03. CAMEL_CF_GMSC.78 version 5.7.0 (1999-03) Process gsmSSF Invocation of gsmSSF in MO. MT or CF call case. signals to/from the right are to/from the gsmSCF.7.

5-2 gsmSSF (sheet 2 of 6) ETSI . Waiting_For_ _Instructions 2(6) Signals to/from the left are to/from the processes CAMEL_MT_GMSC.0 Release 1996) 57 TS 101 044 V5. signals to/from the right are to/from the gsmSCF.7. Timer expiry Tssf CAP_Continue CAP_Connect Terminate Control Relationship stop Tssf Current DP = DP2 or DP12? Yes No ABORT Int_Continue stop Tssf Error Unexpected_ Component_ Sequence Int_Error Int_Connect Waiting_For_ _Instructions Idle Current DP= DP9 or DP17? Yes Set Outstanding_ _Requests = Outstanding_ _Requests .7.1 No Outstanding_ Requests > 0? No Yes Any remaining armed EDPs? Yes No Any remaining armed EDP-R? No Yes Terminate Control Relationship Terminate Control Relationship and open Monitor Relationship Change type of relationship Waiting_For_ _Instructions Monitoring Idle Figure 8. MT or CF call case.0 (1999-03) Process gsmSSF Invocation of gsmSSF in MO.78 version 5. CAMEL_OCH_ _MSC and CAMEL_CF_MSC. CAMEL_CF_GMSC.(GSM 03.

signals to/from the right are to/from the gsmSCF. Signals to/from the left are to/from the processes CAMEL_MT_GMSC.5-3 gsmSSF (sheet 3 of 6) ETSI . CAMEL_CF_GMSC.(GSM 03. CAMEL_OCH_ _MSC and CAMEL_CF_MSC.78 version 5.7.0 Release 1996) 58 TS 101 044 V5. MT or CF call case.0 (1999-03) Process gsmSSF Invocation of gsmSSF in MO. 3(6) Waiting_For_ _Instructions CAP_Request_ _ReportBCSM_ _Event CAP_ _Release_Call Int_T_Exception or Int_O_Exception Arm EDP Only requests that fulfil the arming rules are accepted. Stop Tssf Stop Tssf No Arming rules fulfilled? Terminate Control Relationship Terminate Control Relationship Yes Error Unexpected Data Value ABORT Int_Release_Call Int_Continue Waiting_For_ _Instructions Idle Idle Figure 8.7.

7.0 Release 1996) 59 TS 101 044 V5. Waiting_For_ _Instructions Figure 8. CAMEL_CF_GMSC. 4(6) Signals to/from the left are to/from the processes CAMEL_MT_GMSC.0 (1999-03) Process gsmSSF Invocation of gsmSSF in MO.78 version 5. signals to/from the right are to/from the gsmSCF.(GSM 03. Waiting_For_ _Instructions Int_DP_O_ _Disconnect /* legID */ Int_DP_T_ _Disconnect /* legID */ No DP armed for legID? Yes DP armed as EDP-R? No Yes CAP_Event_ _Report_BCSM (Notify & Continue) CAP_Event_ _Report_BCSM (Interrupted) Set Outstanding_ _Requests = Outstanding_ _Requests + 1 The gsmSSF can have two outstanding requests at DP_Disconnect since it can be armed for each call leg and a ISUP_Release shall be reported without buffering Disarm this DP The DP is only disarmed for the leg for which the event was received.5-4 gsmSSF (sheet 4 of 6) ETSI .7. CAMEL_OCH_ _MSC and CAMEL_CF_MSC. MT or CF call case.

0 (1999-03) Process gsmSSF Invocation of gsmSSF in MO. signals to/from the right are to/from the gsmSCF. Monitoring Int_DP_O_ _Answer Int_DP_T_ _Answer Int_DP_O_ _Disconnect /* legID */ Int_DP_T_ _Disconnect /* legID */ DP_O_ _Answer armed? No No DP_T_ _Answer armed? Yes Yes 1 No DP armed for legID? Yes No DP armed as EDP-R? Yes CAP_Event_ _Report_BCSM (Notify & Continue) CAP_Event_ _Report_BCSM (Notify & Continue) CAP_Event_ _Report_BCSM (Interrupted) Disarm this DP The DP is only disarmed for the leg for which the event was received. MT or CF call case.78 version 5. CAMEL_OCH_ _MSC and CAMEL_CF_MSC.5-5 gsmSSF (sheet 5 of 6) ETSI .7.(GSM 03. Disarm this DP Yes Set Outstanding_ _Requests = 1 Int_Continue Terminate Relationship Control or Monitor Relationship Start Tssf Monitoring Int_Continue Waiting_For_ _Instructions Idle Figure 8.0 Release 1996) 60 TS 101 044 V5.7. Disarm this DP 1 Any remaining armed EDPs? No The DP is only disarmed for the leg for which the event was received. CAMEL_CF_GMSC. 5(6) Signals to/from the left are to/from the processes CAMEL_MT_GMSC.

5-6 gsmSSF (sheet 6 of 6) ETSI .0 (1999-03) Process gsmSSF Invocation of gsmSSF in MO. signals to/from the right are to/from the gsmSCF. MT or CF call case.7. CAMEL_CF_GMSC. Signals to/from the left are to/from the processes CAMEL_MT_GMSC.(GSM 03.0 Release 1996) 61 TS 101 044 V5.7. CAMEL_OCH_ _MSC and CAMEL_CF_MSC. The gsmSCF shall not send a CAP_Release_Call in a monitor relationship Int_O_Exception or Int_T_Exception Terminate Control Relationship Terminate Relationship Control or Monitor Relationship Int_Release_Call ABORT Idle Idle Figure 8. 6(6) Monitoring CAP_ _Release_Call Handling of CAP_Release_Call is only specified in a control relationship.78 version 5.

the gsmSCF initiates a transaction with the HLR by sending an Any Time Interrogation Request.78 version 5.(GSM 03. Support for this procedure is a network operator option.0 Release 1996) 62 TS 101 044 V5. ATI_HLR1(1) Signals to/from the left are to/from the gsmSCF. Idle Any Time Interrogation No ATI accepted? Yes No MS known? Yes Provide_Subscriber_ Info_HLR /* Input data= requested info */ Set negative response: Unknown subscriber Set negative response: ATI not allowed Any_Time_ _Interrogation Response Any Time Interrogation negative Response Idle Idle Figure 8.6 Any Time Interrogation If a CAMEL based service needs the Subscriber State and/or the Location Information for the served subscriber.7. Process CAMEL_ATI_HLR Process in the HLR to handle a request for subscriber information (location info and/or subscriber state) from the gsmSCF.7.0 (1999-03) 8.6-1 Process CAMEL_ATI_HLR ETSI .

the HLR may as a network option derive the location number and/or Geographical Info from the VLR number.7.7 - Procedure Provide_Subscriber_Info_HLR The HLR has no location information for the subscriber (the HLR returns a not reachable reason of Not registered). The subscriber record is marked as MSC area restricted (the HLR returns a not reachable reason of Restricted area). The subscriber is marked as deregistered because of subscription restrictions on roaming (the HLR returns a not reachable reason of Not registered).18 [3]. The mapping from cell ID and location area to location number is network-specific and outside the scope of the GSM standard.7. The MS is not reachable if any of the following conditions is satisfied: If the VLR returns a Provide_Subscriber_Info Response. If the HLR has only the VLR number available as location information. NOTE: The handling in the VLR of Provide_Subscriber_Info Request is defined in GSM 03. ETSI . the HLR may use the returned Cell Id or Location Area to derive the location number and/or Geographical Info. the HLR uses the information in the response to set the Subscriber Info to be returned to the gsmSCF. The subscriber record is marked as MS purged (the HLR returns a not reachable reason of MS purged).78 version 5.0 Release 1996) 63 TS 101 044 V5. The subscriber record is marked as Roaming Restricted due to Unsupported Feature (the HLR returns a not reachable reason of Restricted area).(GSM 03. As a network option.0 (1999-03) 8.

0 Release 1996) 64 TS 101 044 V5.7.78 version 5.(GSM 03.0 (1999-03) Procedure Provide_Subscriber_Info_HLR Procedure in the HLR to retrieve information on the subscriber state and location PSI_HLR1(1) Signals to/from the right are to/from the VLR MS reachable? No Yes As determined from HLR data Provide Subscriber Info Wait_For_ Subscriber_ Info Provide Subscriber Info negative response Provide Subscriber Info ack No Location info required? Yes No Location info required? Yes Set Subscriber Info VLR number known? Yes No Location info:= VLR number Location info:= Unknown Location info:= VLR number No Subscriber state requested? Yes No Subscriber state requested? Yes Subscriber state:= Network determined not reachable Subscriber state:= Not provided by VLR Figure 8.6-2 Procedure Provide_Subscriber_Info_HLR ETSI .7.

IE is marked as Mandatory. Each Information Element. This categorisation is a functional classification.. Conditional. 9. ETSI . Optional or Not applicable for each different traffic case.8 CAMEL specific handling at subscriber data management in the HLR If the VLR does not support CAMEL phase 1 the HLR may apply ODB. CAMEL does not modify any of the standardized procedures for non-call related events including: 9 Description of information flows This clause contains the detailed description of the information flows used by CAMEL.2.1. transfer of SMS messages.1 syntax of the protocol. mobility management procedures.7. Mobile Originating call (MO).2 9..1.9 - Processing of Non-Call Related Events call independent supplementary service procedures.1 gsmSSF to gsmSCF information flows Activity Test Response Description This IF is the response to the Activity Test.1.e.0 Release 1996) 65 TS 101 044 V5. stage 2 information and not a stage 3 classifications to be used for the ASN. allow the call to continue without CAMEL or take network specific actions. The handling is subscriber specific.1.1. 8.1 9.0 (1999-03) 8.78 version 5. BCSM events as answer and disconnect) previously requested by the gsmSCF in a Request Report BCSM Event IF.1.1 Event Report BCSM Description This IF is used to notify the gsmSCF of a call-related event (i. i.1. Mobile Forwarded call (MF) and Mobile Terminating call (MT).2 Information Elements This IF contains no information elements.1 9.e. Roaming Restriction Due to Unsupported Feature.(GSM 03. 9.7. 9.

M This IE indicates the party in the call for which the event is reported. T-Answer.e.2 Information Elements The following information elements are required: Information element name MO MF MT Description Event type BCSM Event specific information BCSM M C M C M This IE specifies the type of event that is reported i. if available.78 version 5. O-Answer. O-Disconnect or T-Disconnect. i. C This IE indicates the call related information specific to the event.1.7.e.7.and T-Answer it is not required.2. Request or Notification. It will contain the "release Cause" for O.or T-Disconnect.0 Release 1996) 66 TS 101 044 V5. Leg ID Misc Call Info M M M M M Mandatory (The IE shall always be sent) C Conditional (The IE shall be sent.1. M This IE indicates the DP type. ETSI .1.(GSM 03.. if available) Not applicable 9.3. For O.3 9.1 Initial DP Description This IF is generated by the gsmSSF when a trigger is detected at a DP in the BCSM.0 (1999-03) 9. to request instructions from the gsmSCF..

For CF calls. For MT calls. Event Type BCSM high Layer Compatibility M C M C M This IE indicates the armed BCSM DP event (i.(GSM 03. Calling Party Number Calling Partys Category Call Reference Number M M M C C M C This IE carries the calling party number to identify the calling party or the origin of the call. C This IE indicates the type of the high layer compatibility..e. C This IE indicates the type of the bearer capability connection to the user. including ∗ and # digits. It may also include service selection information._Attempt_Authorised). the call reference number is set by the GMSC and included on the RCF call record in the GMSC and on the MT call record in the terminating MSC.7. pay phone. M This IE identifies the mobile subscriber. (continued) IMSI M M ETSI . the call reference number is set by the GMSC and included on the CF record in the GMSC or the MSC.1.7. M This IE may be used by the gsmSCF for inclusion in a network optional gsmSCF call record.. Collected_Info and Term. operator.78 version 5. For MO calls. C This IE indicates the type of basic service i.2 Information Elements The following information elements are required: Information element name MO MF MT Description Additional Calling Party Number Basic Service Code Bearer Capability Called Party Number Called Party BCD Number C M M C C C M - C The calling party number provided by the access signalling system of the calling user.3. the call reference number is set by the MSC and included in the MO call record..g.0 Release 1996) 67 TS 101 044 V5. ordinary subscriber). This IE contains the number used to identify the called party in the forward direction. which will be used to determine the ISDN-teleservice of a connected ISDN terminal.e. It is used only for the MO case. M This IE contains the number used to identify the called party in the forward direction. resulting in the Initial DP IF.0 (1999-03) 9. teleservice or bearer service. C Indicates the type of calling party (e. For the MO case this IE is not used.

18 [3]. . This IE indicates the directory number the call was redirected from. It is used to address the correct application/SLP within the gsmSCF. the MSC Address is set by the GMSC and included on the RCF call record in the GMSC and on the MT call record in the terminating MSC.18 [3]. See GSM 03.CAMELBusy: The MS is engaged on a transaction for a mobile originating or terminated circuit-switched call.0 Release 1996) 68 TS 101 044 V5. See GSM 03.NetworkDeterminedNotReachable: The network can determine from its internal data that the MS is not reachable.78 version 5. such as redirection counter.0 (1999-03) The following information elements are required (concluded): Information element name Location Information Location Number MO M M MF MT C C C See GSM 03.164 address of interrogating MSC in international format. In this case the location number may be derived from the cell id or location area of the calling party. For CF calls. M This IE identifies for the gsmSCF unambiguously the requested CAMEL service. the MSC Address is set by the MSC and included in the MO call record. For forwarded calls and mobile terminated calls this IE contains the location number received in incoming ISUP signalling. This IE may be used together with the Call Reference Number by the gsmSCF for inclusion in a network optional gsmSCF call record. if available) Not applicable ETSI .18 [3]. C This IE indicates the status of the MS. The mapping from cell ID and location area to location number is network-specific and outside the scope of the GSM standard. For mobile originated calls this IE represents the location of the calling party. Location Information contains the following information: Information element name Location Number CellIdOrLAI Geographical Information Age Of Location Information VLR number MO M C M M MF MT C C C C C See GSM 03.18 [3]. It contains forwarding related information. Original Called Party ID Redirecting Party ID Redirection Information Service Key Subscriber State M - C M M M - C C C This IE carries the dialled digits if the call has met call forwarding on the route to the gsmSSF. See GSM 03. . For MT calls.AssumedIdle: The state of the MS is neither "CAMELBusy" nor "NetworkDeterminedNotReachable".7. The states are: .7. the MSC Address is set by the GMSC and included on the CF record in the GMSC or the MSC.18 [3]. Description M Mandatory (The IE shall always be sent) C Conditional (The IE shall be sent. For MO calls.NotProvidedFromVLR: The VLR did not provide any information on subscriber state even though it was requested.18 [3]. . See GSM 03. Description MSC Address M M M E.(GSM 03.

This IE contains the generic number.(GSM 03. 9. This IE indicates that the O-CSI.2.2. If no reply is received.0 (1999-03) 9.1 gsmSCF to gsmSSF information flows Activity Test Description This IF is used to check for the continued existence of a relationship between the gsmSCF and gsmSSF.g. which e.1. pay phone.1 Connect Description This IF is used to request the gsmSSF to perform the call processing actions to route a call to a specific destination.g..2 9. This IE carries the dialled digits if the call has met call forwarding on route to the gsmSSF or is forwarded by the gsmSCF.0 Release 1996) 69 TS 101 044 V5. operator. then the gsmSSF will respond. 9. could be used to modify the calling line ID presented to the called user.2.2.2. To do so. 9. the gsmSSF may use destination information from the calling party and existing call set-up information depending on the information provided by the gsmSCF. This IE contains forwarding related information.1 9. Redirecting Party ID Redirection Information Suppression Of Announcements Generic Number O O O O O O O O O O O-CSI Applicable - - O M Mandatory (The IE shall always be sent) O Optional (Service logic dependent) Not applicable ETSI .2. This IE indicates the directory number the call was redirected from.2 Information Elements The following information elements are required: Information element name Calling Partys Category MO O MF O MT O Description This IE indicates the type of calling party (e. This IE indicates that announcements or tones generated as a result of unsuccessful call setup shall be suppressed. then the gsmSCF will assume that the gsmSSF has failed in some way and will take the appropriate action.78 version 5. If the relationship is still in existence.7.7. if present should be applied on the outgoing leg. ordinary subscriber). such as redirecting counter.2 Information Elements This IF contains no information elements.2.2.1. Its used to convey the additional calling party number. Destination Routing Address Original Called Party ID O O O O O O This IE contains the called party number towards which the call is to be routed.2 9.

.1 Continue Description This information flow requests the gsmSSF to proceed with call processing at the DP at which it previously suspended call processing to await gsmSCF instructions.0 (1999-03) 9. 9.7. O_Disconnect or T_Disconnect). 9.2. proceeds to the next point in call in the BCSM) without substituting new data from the gsmSCF.2.2.3 9.5.4.2.2 Information Elements This IF contains no information elements.2.0 Release 1996) 70 TS 101 044 V5.2.3.78 version 5.(GSM 03. 9. and continues basic call processing (i. This may be used by gsmSSF for generating specific tones to the different parties in the call or to fill in the "cause" in the release message..4.2.2.2.1 Release Call Description This IF is used to tear down by the gsmSCF an existing call at any phase of the call for all parties involved in the call.7. then send a notification back to the gsmSCF when the event is detected (see Event Report BCSM).4 9. ETSI .e.3.2 Information Elements The following information elements are required: Information element name MO MF MT Description Cause M M M A number giving an indication to the gsmSSF about the reason of releasing this specific call.5 9.1 Request Report BCSM Event Description This IF is used to request the gsmSSF to monitor for a call-related event (i. 9.e. The gsmSSF completes DP processing. O_Answer.5. T_Answer. M Mandatory (The IE shall always be sent) 9.2 Information Elements The following information elements are used: Information element name MO MF MT Description BCSM Event M M M This IE specifies the event or events of which a report is requested.

subscriber state Subscriber Identity M This IE identifies the subscriber for which the information is requested.IMSI .7.subscriber location . as request or notification.1 HLR to gsmSCF information flows Any Time Interrogation Response Description This IF is used by the HLR to provide the requested information to the gsmSCF.. M Mandatory (The IE shall always be sent) C Conditional 9. Monitor Mode M M M This IE indicates how the event should be reported i.78 version 5.MSISDN M Mandatory (The IE shall always be sent) 9.4 9.1.3. O_Answer. T_Answer.1 9.3 9.0 Release 1996) 71 TS 101 044 V5.. If not included. The Leg ID IE shall always be included for the events O-Disconnect and TDisconnect.0 (1999-03) BCSM Event contains the following information: Information element name MO MF MT Description Event type Leg ID M C M C M This IE specifies the type of event of which a report is requested (i.1 gsmSCF to HLR information flows Any Time Interrogation Request Description This IF is used to request information (subscriber state and location) from the HLR at any time.1.1 9.3. 9. The identity can be one of: .e. This IE indicates the type of subscriber information being requested: .(GSM 03. O_Disconnect or T_Disconnect).2 Information Elements The following information elements are required: Information element name Required Description gsmSCF Address Requested Info M M This IE indicates the address of the interrogating gsmSCF. C This parameter indicates the party in the call for which the event shall be reported.7.1.3.e.4. ETSI .4. default is the party created with Connect IF for the events O_Answer and T_Answer.

5.1 9.2 Information Elements The following information elements are required: Information element name Required Description Location Information Subscriber State C C This IE indicates the location of the served subscriber.5.0 (1999-03) 9.2 9.02 [5] and is used by the HLR to insert subscriber data in the VLR.18 [3]. See GSM 03. See GSM 03.2.AssumedIdle: The VLR has indicated that the state of the MS is neither "CAMELBusy" nor "NetworkDeterminedNotReachable". if available) 9. C Conditional (The IE shall be sent.(GSM 03. See GSM 03.18 [3]. 9.7. C Conditional (The IE shall be sent when deletion is requested) 9. . if requested and available) Location Information contains the following information: Information element name Required Description Location Number CellIdOrLAI Geographical Information Age Of Location Information VLR number C C C C C See GSM 03. .18 [3].2 Information Elements The Delete Subscriber Data contains the following CAMEL specific IE: Information element name Required Description CAMEL Subscription Info Withdraw C This IE identifies that all CSIs shall be deleted from the subscriber data in VLR.18 [3].02 [5] and is used by the HLR to delete subscriber data in the VLR.5.1.NotProvidedFromVLR: The VLR did not provide any information on subscriber state even though it was requested. .NetworkDeterminedNotReachable: The VLR has indicated that the network can determine from its internal data that the MS is not reachable.1.4.1.7.1 Insert Subscriber Data Description This IF is specified in GSM 09. See GSM 03. This IE indicates the status of the MS.0 Release 1996) 72 TS 101 044 V5.CAMELBusy: The VLR has indicated that the MS is engaged on a transaction for a mobile originating or terminated circuit-switched call. The possible values of the IE are: .78 version 5.1 HLR to VLR information flows Delete Subscriber Data Description This IF is specified in GSM 09.5 9. ETSI .18 [3].5.5. C Conditional (The IE shall be sent.

5. GMSC address C C Conditional (The IE shall be sent.5.2 Information Elements Insert Subscriber Data contains the following CAMEL specific IE: Information element name Required Description O-CSI C This IE identifies the subscriber as having originating CAMEL services.5. C Conditional (The IE shall be sent.1 Provide Subscriber Info Description This IF is specified in GSM 03. It contains the gsmSCFAddress.subscriber state Subscriber Identity M This IE identifies the subscriber for which the information is requested. DefaultCallHandling and TdpList. and a network optional call record from the gsmSCF.2. 9.3.18 [3] and is used by the HLR to request information (subscriber state and location) from the VLR at any time.subscriber location .4.5. The identity can be: .0 (1999-03) 9.4.78 version 5.0 Release 1996) 73 TS 101 044 V5.4 9.3.7. .1 Provide Roaming Number Description This IF is specified in GSM 03. if received from the GMSC in the Send Routeing Info) 9. This IE is used for correlation of call records outputted from the GMSC and the terminating MSC. ServiceKey.4 Information Elements Provide Roaming Number contains the following CAMEL specific IE: Information element name Required Description Suppression Of Announcements Call Reference Number C C This IE indicates that announcements or tones generated as a result of unsuccessful call setup shall be suppressed.IMSI: The IMSI shall be accompanied by a LMSI if one was provided by the VLR. This IE is the E.164 address of the GMSC.7. 9. M Mandatory (The IE shall always be sent) ETSI .3 9.5. if required) 9.5.(GSM 03.2 Information Elements Provide Subscriber Info contains the following CAMEL specific IE: Information element name Required Description Requested Info M This IE indicates the type of subscriber information requested.18 [3] and is used by the HLR to request a roaming number from the VLR.5.

02 [5] and is used by the VLR to indicate to the HLR the result of the Insert Subscriber Data IF.1 9. 9.AssumedIdle: The state of the MS is neither "CAMELBusy" nor "NetworkDeterminedNotReachable". .CAMELBusy: The MS is engaged on a transaction for a mobile originating or terminated circuit-switched call.1.0 (1999-03) 9. if requested and available) 9. C Conditional (The IE shall be sent.18 [3] and is used by the VLR to provide the requested information to the HLR.1.6.78 version 5.NetworkDeterminedNotReachable: The network can determine from its internal data that the MS is not reachable.6.2. The states are: .18 [3].(GSM 03.7.. . C Conditional (The IE shall always be sent when a CSI has been included in the ISD) 9.1 HLR to GMSC information flows Send Routeing Info ack Description This IF is specified in GSM 03.6.7.6.2 Information Elements Insert Subscriber Data ack contains the following CAMEL specific IE: Information element name Required Description Supported CAMEL Phases C This IE identifies which CAMEL phases are supported by the MSC/VLR.2 Information Elements Send Routeing Info ack contains the following CAMEL specific IE: ETSI .7.1 9.1.1 Provide Subscriber Info ack Description This IF is specified in GSM 03.2.2 9.1.6.18 [3] and is used by the HLR to transfer the requested routeing information.6.2 Information Elements Provide Subscriber Info Response contains the following CAMEL specific IE: Information element name Required Description Location Information Subscriber State C C This IE indicates the location of the served subscriber.7. 9. This IE indicates the status of the MS.1 VLR to HLR information flows Insert Subscriber Data ack Description This IF is specified in GSM 09.7.6 9. 9.7 9.0 Release 1996) 74 TS 101 044 V5. Only CAMEL phase 1 is used. The elements contained in the Location Information are specified in GSM 03.

78 version 5.18 [3]. ServiceKey.0 Release 1996) 75 TS 101 044 V5.0 (1999-03) Information element name Required Description Location Information O-CSI C2 C This IE indicates the location of the served subscriber. ServiceKey. DefaultCallHandling andTdpList.) 9. This IE indicates if the called party has a CUG subscription. teleservice or bearer service.CAMELBusy: The VLR has indicated that the MS is engaged on a transaction for a mobile originating or terminated circuit-switched call. Basic Service Code CUG Subscription Flag C C This IE indicates the type of basic service i.(GSM 03.18 [3]. . It shall only be sent if the T-CSI is active and included in the Send Routing Information ack.18 [3].7. Subscriber State C2 This IE indicates the status of the MS. Shall be sent if O-CSI is active.8.7. T-CSI C This IE identifies the subscriber as having terminating CAMEL services. It contains the gsmSCFAddress.NotProvidedFromVLR: The VLR did not provide any information on subscriber state even though it was requested. . Shall be sent if T-CSI is active and no Suppress T-CSI indicator is present in the SRI. This IE identifies the subscriber as having originating CAMEL services.e. DefaultCallHandling andTdpList. C Conditional (The IE shall be sent. It contains the gsmSCFAddress.1. See GSM 03. See GSM 03. The possible values of the IE are: .8. See GSM 03.AssumedIdle: The VLR has indicated that the state of the MS is neither "CAMELBusy" nor "NetworkDeterminedNotReachable". and CFU or CFNRc has been invoked. .1 9. if available) C2 Conditional (The IE shall be sent.18 [3]. Location Information contains the following information: Information element name Required Description Location Number CellIdOrLAI Geographical Information Age Of Location Information VLR number C C C C C See GSM 03.NetworkDeterminedNotReachable: The VLR has indicated that the network can determine from its internal data that the MS is not reachable.1 GMSC to HLR information flows Send Routeing Info Description ETSI .8 9. See GSM 03. or if both O-CSI and T-CSI are active. if available and indicated by Subscriber Information in Send Routeing Information Ack indicator..18 [3].

when it has been received from the gsmSCF.2 Information Elements Send Routeing Info contains the following CAMEL specific IE: Information element name Required Description Suppression Of Announcement C This IE indicates that announcements or tones generated as a result of unsuccessful call setup shall be suppressed.79 [4] and is used to request the GMSC to take over handling the call so that it can be forwarded from the GMSC. Shall be present if CAMEL handling applies. Shall be omitted from the first interrogation.164 address of the GMSC. i.. C Conditional. Suppress T-CSI C Suppression Of Announcement C Suppress T-CSI Supported CAMEL Phases Call Reference Number C M C GMSC address C C Conditional.7. otherwise shall be absent. Shall be omitted from the first interrogation.. Shall be sent in the second interrogation. For CAMEL this parameter shall be included in the second interrogation. This IE is the E. and a network optional call record from the gsmSCF.9 9. (The condition for the inclusion of IE is shown in the Description column) M Mandatory.78 version 5. i. This IE indicates that announcements or tones generated as a result of unsuccessful call setup shall be suppressed.1.0 (1999-03) This IF is described in GSM 03. For other services it may be needed in the first interrogation. when it has been received from the gsmSCF.(GSM 03.1 9.8. 9.e.e. This IE indicates that T-CSI shall be suppressed. Shall always be sent in the second interrogation This IE lists the supported CAMEL phases.9. shall be sent in the second interrogation. Shall be sent in the second interrogation if available.9.9.0 Release 1996) 76 TS 101 044 V5.1. shall be sent in the second interrogation if available. 9.1 VMSC to GMSC information flows Resume Call Handling Description This IF is described in GSM 03.18 [3] and is used to request information from the HLR to route an MT call. the condition for the presence of this IE is shown in the Description column ETSI . (The IE shall always be sent when the GMSC supports CAMEL) 9. This IE indicates that T-CSI shall be suppressed. This IE is used for correlation of call records output from the GMSC and the terminating MSC.7.2 Information Elements Resume Call Handling contains the following CAMEL specific IE: Information element name Required Description O-CSI C This IE indicates that CAMEL handling applies for a forwarded call.1.

9.0 Release 1996) 77 TS 101 044 V5.10.11. the condition for the presence of this IE is shown in the Description column 9.2 Information Elements Send Info For Outgoing Call contains the following CAMEL specific IE Information element name Required Description Suppress O-CSI C This IE indicates that O-CSI shall be suppressed.(GSM 03.10 9.7.10.11 9. Shall always be sent in the second interrogation.1 MSC to VLR information flows Send Info For Outgoing Call Description This IF is described in GSM 03.10.11.1.1.1 9.1 VLR to MSC information flows Complete Call Description This IF is described in GSM 03.7.1.18 [3] and is used to request the VLR to provide information to handle an outgoing call. ETSI .78 version 5.1 9.0 (1999-03) 9. C Conditional.18 [3] and is used to instruct the MSC to continue the connection of a call.

11. Shall be present if CAMEL handling applies.1 Send Info For Incoming Call ack Description This IF is described in GSM 03.3.7.1. Shall be present in the response to the first interrogation for an MO call if CAMEL handling applies. C Conditional. the condition for the presence of this IE is shown in the Description column ETSI .11.11.7. the condition for the presence of this IE is shown in the Description column 9.18 [3] and is used to indicate that the incoming call for which the MSC requested subscription information shall not be connected. C Conditional.11. As an implementation option.11.2.3 9. Shall be absent in the response to the second interrogation for an MO call and in the response to the interrogation for an MT call. 9.11.0 Release 1996) 78 TS 101 044 V5.2 Information Elements Send Info For Incoming Call ack contains the following CAMEL specific IE: Information element name Required Description O-CSI C This IE indicates that CAMEL handling applies for a forwarded call.2 Information Elements Complete Call contains the following CAMEL specific IE: Information element name Required Description O-CSI C This IE indicates that CAMEL handling applies for an MO call. This IE indicates that announcements or tones generated when the call is forwarded shall be suppressed. 9.(GSM 03. Suppression Of Announcement C C Conditional.11. the condition for the presence of this IE is shown in the Description column 9.18 [3]: Information element name Required Description Suppression Of Announcement C This IE indicates that announcements or tones generated as a result of unsuccessful call setup shall be suppressed. may be sent if it was received in the Provide Roaming Number for this call.2 Information Elements Send Info For Incoming Call negative response contains the following CAMEL specific IE which may be attached as a parameter to any of the negative response values defined in GSM 03.2 9.3. otherwise shall be absent. otherwise shall be absent.0 (1999-03) 9.18 [3] and is used to indicate that the incoming call for which the MSC requested subscription information shall be forwarded. Shall be sent if it was received in the Provide Roaming Number for this call.2.78 version 5.1 Send Info For Incoming Call negative response Description This IF is described in GSM 03.

0 5.1.0 5.0.78 03.5.0 5.0 6.0 ETSI .78 03.4.0 5.0 5.3.0 5.78 and 09.0 5.(GSM 03.1.0.0 (1999-03) Annex A (informative): Document Change History SPEC SMG# 03.0 5.0 5.2.78 03.4.0 5.7.78 03.1 5.0 5.2.0 5.0.78 03.2.78 03.1.3.0 5.4.2.1 5.3.6.0 5. Changes to ease the documentation of new services Removal of CallingPartyNumber from Connect Removal of the CalledPartyNumber for MO calls from IDP Use of the CallReference Number & GMSC address in SRI CAMEL phase 2 Redundant definition of Location Information elements Corrections to CAMEL relationship description Correction to CAMEL phase 1 for forwarded calls Error handling in GSM 03.3.0 5.78 03.0 5.0 5.0 5.0.6.0 5.2.0 5.7.78 03.78 03.0 5.0 5.0 5.78 03.78 version 5.4.78 03.0 5.78 03.1.5.2.78 03.78 03.7.78 03.0 5.78 s21 s22 s22 s22 s22 s22 s22 s23 s23 s24 s24 CR NEW A001 A002 A004 A005 A006 A007 A003 A010 A008 A009 PHASE VERS NEW_VERS 2+ 2+ 2+ 2+ 2+ 2+ 2+ R96 R96 R97 R96 2.78 03.3.78 03.1 5.0 6.78 03.0.0.78 03.6 Release by A party for forwarded calls and CAMEL Progress is to be sent on CONNECT reception Corrections (corresponds to A029) Clarification of handling of call forwarding 03.78 03.3.0 5.5.0 5.0 5.0 5.0 5.0 5.1.0.2.18.1.0 5.0 5.0.0 Release 1996) 79 TS 101 044 V5.1.0.78 s24 s24 s24 s25 s25 s25 s25 s26 s26 s26 s27 s28 A011 A013 A014 A008 A015 A016 A017 A020 A022 A023 A033 A047 R96 R96 R96 R97 R96 R96 R96 R96 R96 R96 R96 R96 5.0 SUBJECT CAMEL phase 1 (stage 2) CallingPartyNumber in Connect MSC Id for Call Reference Number Introduction of value 'not Provided from VLR" in subscriber state Setting of Location Number Clarification on handling of Connect and Continue operations Change to CAMEL phase 1 regarding * and # in Called Party Number Alignment with stage 3 specifications (09.4.78 03.0 5.1.0 5.5.4.0 5.0.78 paragraph 8.0 5.3.02) and clarifications Alignment subscriber status in CAMEL with MAP Support of CAMEL phase 2 (stage2) Concentration of description of core call handling functions in 03.0 5.1 5.3.

3.0 (1999-03) History Document history V5.0 V5.0 V5.1.78 version 5.6.1 V5.0 Release 1996) 80 TS 101 044 V5.7.5.7.0 V5.2 V5.2.7.0 April 1997 August 1997 November 1997 January 1998 July 1998 November 1998 March 1999 Publication Publication Publication Publication Publication Publication Publication ISBN 2-7437-2938-4 Dépôt légal : Mars 1999 ETSI .0.0 V5.(GSM 03.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->