~sm~ - ptabdata.blob.core.windows.net · whilst every care has been taken in the preparation and...

GSM GSM 03.78

TECHNICAL April 1997

SPECIFICATION Version 5.0.0

Source: ETSI TC-SMG Reference: DTS/SMG-030378Q

ICS: 33.020

Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)

~sm~c~,o~;,~~ s~~s~r~n~ rou

~n~o~~u.r

Digital cellular telecommunications system (Phase 2+);

Customized Applications for Mobile network Enhanced Logic

(CAMEL) -Stage 2

(GSM 03.78)

ETSI

European Telecommunications Standards Institute

ETSI Secretariat

Postal address: F-06921 Sophia Antipolis CEDEX -FRANCEOffice address: 650 Route des Lucioles -Sophia Antipolis - Valbonne -FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat -Internet: [email protected]

Tel.: +33 4 92 94 42 00 -Fax: +33 4 93 65 47 16

Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.

OO European Telecommunications Standards Institute 1997. All rights reserved.

CISCO SYSTEMS, INC. Ex. 1124

Whilst every care has been taken in the preparation and publication of this document, errors incontent, typographical or otherwise, may occur. If you have comments concerning its accuracy, pleasewrite to "ETSI Editing and Committee Support Dept." at the address shown on the title page.


GSM 03.78 version 5.0.0 : April 1997

Contents

Foreword ..................... .

1 Scope ..................................................................................................................................................

2 Normative references ..........................................................................................................................

3 Definitions and abbreviations ...............................................................................................................3.1 Definitions .............................................................................................................................32 Abbreviations ........................................................................................................................

4 Architecture .........................................................................................................................................4.1 Functional Entities used for CAMEL .....................................................................................4.2 Interfaces defined for CAMEL ..............................................................................................

4.2.1 HLR - VLR interface .........................................................................................4.2.2 GMSC - HLR interFace .....................................................................................4.2.3 GMSC - gsmSSF interface ...............................................................................4.2.4 gsmSSF - gsmSCF interface ............................................................................4.2.5 MSC - gsmSSF interface ..................................................................................4.2.6 gsmSCF - HLR interFace ..................................................................................

5 Detection Points (DPs) ........................................................................................................................5.1 Definition and description .....................................................................................................5.2 DP processing rules .............................................................................................................

6 Description of CAMEL Subscriber Data ...............................................................................................6.1 Description of Originating/Terminating CAMEL Subscription Information (O/T-CSI) .............

6.1.1 Content of the O/T-CSI .....................................................................................6.1.1.1 gsmSCF address ....................................................................6.1.1.2 Service Key .............................................................................6.1.1.3 Default Call Handling ..............................................................6.1.1.4 TDP List ..................................................................................

6.2 Description of Subscriber Information in S R I Ack indicator .................................................

7 Description of CAMEL BCSMs ............................................................................................................7.1 General Handling .................................................................................................................7.2 Originating Basic Call State Model (O-BCSM) .....................................................................

7.2.1 Description of O-BCSM ....................................................................................7.2.1.1 Description of the call model (PICs) ........................................

7.2.1.1.1 O Null &Authorise_Origination_Attempt_Collect Info ........................................................

7.2.1.1.2 Analyse, Routing &Alerting ......................7.2.1.1.3 O Active ...................................................7.2.1.1.4 O_Exception .............................................

7.3 Terminating Basic Call State Model (T-BCSM) .....................................................................7.3.1 Description of T-BCSM .....................................................................................

7.3.1.1 Description of the call model (PICs) ........................................7.3.1.1.1 T Null .......................................................7.3.1.1.2 Terminating Call Handling .........................7.3.1.1.3 T Active ...................................................7.3.1.1.4 T_Exception ..............................................

7.4 BCSM Modelling of Call Scenarios .......................................................................................7.4.1 Mobile Originated Call ......................................................................................7.4.2 Mobile Terminated Call .....................................................................................7.4.3 Call Forwarding at the GMSC ..........................................................................7.4.4 Call Forwarding at the MSC .............................................................................

CISCO SYSTEMS, INC. Ex. 1124 Page 3

8 Procedures for CAMEL8.1 Handling of mobile originated calls .......................................................................................

8.1.1 Handling of Outgoing Call request in the MSC, ProcessCAMEL OCH MSC .........................................................................................8.1.1.1 Actions at state Wait For MO Call Result 1 ........................

8.1.1.1.1 Send Info For_Outgoing_Call_1Negative Response ..................................

8.1.1.1.2 Complete Call 1 ........................................8.1.1.2 Actions at state DP Collected Info .........................................

8.1.1.2.1 Int Release Call ......................................8.1.1.2.2 Int Error ..... ............................................8.1.1.2.3 Int Continue .............................................8.1.1.2.4 Int Connect ..............................................8.1.1.2.5 Release Transaction ................................

8.1.1.3 Actions at state Wait For MO Call Result 2 ........................8.1.1.3.1 Send_Info Negative Response .................8.1.1.3.2 I nt_Release_Call ......................................8.1.1.3.3 Release Transaction ................................8.1.1.3.4 Complete Call 2 ........................................

8.1.1.4 Actions at state Wait For ACM 2 ..........................................8.1.1.4.1 ISUP ACM . ............................................8.1.1.4.2 ISUP Connect ..........................................8.1.1.4.3 ISUP Release ..........................................8.1.1.4.4 Release Transaction ................................8.1.1.4.5 Int Release Call ......................................

8.1.1.5 Actions at state Wait For ANM 2 ..........................................8.1.1.5.1 Release Transaction ................................8.1.1.5.2 Int Release Call ......................................8.1.1.5.3 ISUP Answer ...........................................

8.1.1.6 Actions at DP O Answer .......................................................8.1.1.6.1 Int Continue .............................................8.1.1.6.2 Release Transaction ................................8.1.1.6.3 ISUP Release from destination

exchange ..................................................8.1.1.7 Actions at state Wait For Connect Ack 2 .............................8.1.1.8 Actions at state Wait For Clear 2 . ...... ..............................

8.1.1.8.1 Release Transaction ................................8.1.1.8.2 ISUP Release from destination

exchange ..................................................8.1.1.8.3 Int_Release_Call ......................................

8.1.2 Handling of Outgoing Call request in the VLR, processCAMEL OCH VLR ..........................................................................................8.1.2.1 Actions at state Wait For SIFOC ...........................................8.12.2 Actions at state Wait For SIFOC 2 .......................................

8.1.2.2.1 Send_Info_For_Outgoing_Call_2 .............8.1.2.2.2 Release ....................................................

8.2 Handling of mobile terminating calis .....................................................................................8.2.1 Handling of terminating call request in the GMSC, Process

CAMEL MT GMSC .........................................................................................8.2.1.1 Reception of ISUP_IAM ..........................................................8.2.1.2 Actions at state Wait_For_Routeing_Info_1 ............................

82.1.2.1 Send_Routeing_Info NegativeResponse.................................................

8.2.1.2.2 Send_Routeing_Info Ack with MSRN.......8.2.1.2.3 Send_Routeing_Info Ack with FTN...........8.2.1.2.4 Send_Routeing_Info Ack with T-CSI

and possibly FTN and/or O-CSI ................8.2.1.2.5 Send Routeing_Info Ack with O-CSI

and FTN ...................................................8.2.1.2.6 ISUP Release received from

originating exchange ................................8.2.1.3 Actions at state DP_Termination_Attempt_Authorised............

8.2.1.3.1 I nt_Release_Call ......................................



8.2.1.3.2 Int Error ..................................................8.2.1.3.3 Int Continue .............................................8.2.1.3.4 Int Connect ..............................................8.2.1.3.5 ISUP Release received from

originating exchange ................................8.2.1.4 Actions at state Wait_For Routeing_Info_2 ............................

8.2.1.4.1 Send_Routeing_Info NegativeResponse .................................................

82.1.4.2 Send_Routeing_Info Ack with MSRN.......8.2.1.4.3 Send_Routeing_Info Ack with FTN...........8.2.1.4.4 Send Routeing_Info Ack with O-CSI

and FTN ...................................................8.2.1.4.5 Int_Release_Call ......................................8.2.1.4.6 ISUP Release received from

originating exchange ................................8.2.1.5 Actions at state Wait For Answer 1 ......................................

8.2.1.5.1 ISUP_Release from originatingexchange ..................................................

8.2.1.52 ISUP Release from destinationexchange or processCAM EL_CF_MSC_GMSC ........................

8.2.1.5.3 I nt_Release_Cal I ......................................8.2.1.5.4 ISUP_Answer ...........................................

8.2.1.6 Actions at state DP T Answer ...............................................8.2.1.6.1 ISUP_Release from originating

exchange ..................................................8.2.1.6.2 ISUP Release from destination

exchange or processCAM EL_CF_MSC_GMSC ........................

8.2.1.6.3 I nt_Release_Cal I ......................................82.1.7 Int Continue ...........................................................................8.2.1.7 Actions at state Wait For Clear 1 .........................................

8.2.1.7.1 ISUP_Release from originatingexchange ..................................................

8.2.1.7.2 ISUP Release from destinationexchange or processCAM EL_CF_MSC_GMSC ........................

82.1.7.3 Int_Release_Call ......................................8.2.2 Handling of request for routing information, Process CAMEL_SRI_HLR.........

8.2.2.1 Reception of Send_Routeing_Info ..........................................8.22.1.1 Continue call handling ..............................8.2.2.1.2 Call forwarded ..........................................8.22.1.2.1 Call allowed ..............................................8.2.2.1.2.2 Call not allowed ........................................8.2.2.1.3 Call forwarding fails ..................................

8.2.2.2 Actions at state Wait For MSRN ...........................................8.2.2.2.1 Provide_Roaming_NumberAck from

VLR..........................................................8.2.2.2.2 Provide_Roaming_Number Negative

Response from VLR .................................8.2.2.2.2.1 Call allowed ..............................................8.2.2.2.2.2 Call not allowed ........................................

8.2.2.3 Macro CSI Check ...................................................................8.2.3 Handling of Subscriber Information retrieval in the HLR, Procedure

CAMEL PSI HLR ............................................................................................8.2.3.1 MS reachable ..........................................................................8.2.3.2 MS not reachable ....................................................................

8.2.3.2.1 Location Information requested ................8.2.3.2.2 Subscriber State requested ......................

8.2.3.3 Actions at state Wait For Information ....................................8.2.3.3.1 Provide_Subscriber_Info Response.........8.2.3.3.2 Provide_Subscriber_Info Negative

Response.................................................


8.2.4 Handling of provide roaming number request in the VLR,CAMEL PRN VLR ..........................................................................................8.2.4.1 Reception of Provide Roaming Number ..................................8.2.4.2 IMSI known in VLR .................................................................8.2.4.3 IMSI not known in VLR ...........................................................

82.5 Handling of call forwarding in the MSC/GMSC, ProcessCAMEL CF MSC GMSC ...............................................................................8.2.5.1 Actions at state DP Collected Info .........................................

8.2.5.1.1 ISUP Release from processCAMEL ICH MSC/CAMEL MT GMSC....... ...... ..................... ..... ............

8.2.5.1.2 I nt_Release_Cal I ......................................8.2.5.1.3 Int Error ...................................................8.2.5.1.4 Int Continue .............................................8.2.5.1.5 Int Connect ...........................................:..

8.2.52 Actions at state Wait For Answer ..........................................8.2.5.2.1 ISUP_Release from originating

exchange ................................................. .8.2.5.2.2 ISUP Release from destination

exchange................................................. .8.2.5.2.3 I nt_Release_Cal I ......................................8.2.52.4 ISUP_Answer ...........................................

8.2.5.3 Actions at state DP O Answer ...............................................8.2.5.3.1 Int Continue .............................................8.2.5.3.2 ISUP Release from process

CAMEL ICH MSC/CAMEL MT GMSC....... ...... ..................... ..... ............

8.2.5.3.3 ISUP Release from destinationexchange ..................................................

8.2.5.3.4 I nt_Release_Call ......................................8.2.5.4 Actions at state Wait For Clear .............................................

8.2.5.4.1 ISUP Release from processCAMEL ICH MSC/CAMEL MT MSC GMSC ..... ..................... ..... ............

8.2.5.4.2 ISUP Release from destinationexchange ..................................................

8.2.5.4.3 I nt_Release_Cal I ......................................8.2.6 Handling of incoming call handling in the MSC, process

CAMEL ICH MSG ...........................................................................................8.2.6.1 Wait For MT Call Result ......................................................8.2.6.2 Send_Info_For_Incoming_Call Ack .........................................

8.3 Handling of mobile calls in gsmSSF .....................................................................................8.3.1 State Idle ..........................................................................................................

8.3.1.1 I nt_Invoke_gsmSSF ................................................................8.3.12 Int DP O!T Answer or Int DP O/T Disconnect ...................8.3.1.3 I nt_O!T_Exception ............ .... ..... ....................................

8.3.2 State Wait_For_Request ..................................................................................8.3.2.1 I nt_D P_Collected_Info ............................................................8.32.2 DP_Terminating_Attempt_Authorised .....................................8.3.2.3 I nt_O/T_Exception ..................................................................

8.3.3 Waiting_For_Instructions ..................................................................................8.3.3.1 CAP_Request_Report_BCSM_Event .....................................8.3.3.2 CAP Continue ........................................................................8.3.3.3 CAP Connect .........................................................................8.3.3.4 CAP Release Call .................................................................8.3.3.5 Timer expire ... .......................................................................8.3.3.6 I nt_O!T_Exception ..................................................................8.3.3.7 Int DP O!T Disconnect .........................................................

8.3.4 Monitoring ............. ..... ...... ..........................................................................8.3.4.1 Int DP O/T-Answer ................................................................8.3.4.2 Int DP O/T Disconnect .........................................................8.3.4.3 CAP Release Call .................................................................8.3.4.4 I nt_O/T_Exception ..................................................................



8.4 Any Time Interrogation .........................................................................................................8.4.1 Handling of Any Time Interrogation Request in HLR, Process

CAMEL. ATI HLR ............................................................................................8.4.1.1 Reception of Any_Time_Interrogation Request .......................

8.4.1.1.1 MS known .................................................8.4.1.1.2 MS not known ...........................................

8.5 CAMEL specific handling at subscriber data management in HLR .......................................8.6 Processing of Non-Call Related Events ................................................................................

9 Description of information flows ...........................................................................................................9.1 gsmSSF to gsmSCF information flows .................................................................................

9.1.1 Activity Test Response .....................................................................................9.1.1.1 Description ..............................................................................9.1.1.2 Information Elements ..............................................................

9.1.2 Event Report BCSM .........................................................................................9.1.2.1 Description ..............................................................................9.1.2.2 Information Elements ..............................................................

9.1.3 Initial DP ...........................................................................................................9.1.3.1 Description ..............................................................................9.1.32 Information Elements ..............................................................

9.2 gsmSCF to gsmSSF information flows .................................................................................9.2.1 Activity Test ......................................................................................................

9.2.1.1 Description ..............................................................................9.2.1.2 Information Elements ..............................................................

9.2.2 Connect ............................................................................................................9.2.2.1 Description ..............................................................................9.2.2.2 Information Elements ..............................................................

9.2.3 Continue ...........................................................................................................9.2.3.1 Description ..............................................................................9.2.3.2 Information Elements ..............................................................

92.4 Release Call .....................................................................................................9.2.4.1 Description ..............................................................................9.2.4.2 Information Elements ..............................................................

9.2.5 Request Report BCSM Event ...........................................................................9.2.5.1 Description ..............................................................................9.2.5.2 Information Elements ..............................................................

9.3 gsmSCF to HLR information flows .......................................................................................9.3.1 Any Time Interrogation Request .......................................................................


9.4 HLR to gsmSCF information flows .......................................................................................9.4.1 Any Time Interrogation Response ....................................................................


9.5 HLR to VLR information flows ..............................................................................................9.5.1 Delete Subscriber Data ....................................................................................


9.5.2 Insert Subscriber Data ......................................................................................9.5.2.1 Description ..............................................................................9.5.2.2 Information Elements ..............................................................

9.5.3 Insert Subscriber Data Response ....................................................................9.5.3.1 Description ..............................................................................9.5.3.2 Information Elements ..............................................................

9.5.4 Provide Subscriber Info Request ......................................................................9.5.4.1 Description ..............................................................................9.5.4.2 Information Elements ..............................................................

9.5.5 Provide Roaming Number ................................................................................9.5.5.1 Description ..............................................................................9.5.5.2 Information Elements ..............................................................

9.6 VLR to HLR information flows ..............................................................................................9.6.1 Provide Subscriber Info Response ...................................................................

9.6.1.1 Description ..............................................................................


9.6.1.2 Information Elements ..............................................................9.7 HLR to GMSC information flows ...........................................................................................

9.7.1 Send Routeing Info Ack ....................................................................................9.7.1.1 Description ..............................................................................9.7.1.2 Information Elements ..............................................................

9.8 GMSC to HLR information flows ...........................................................................................9.8.1 Send Routeing Info ..........................................................................................


History.......................................................................................................................................................... .



Foreword

This Global System for Mobile communications Technical Specification (GTS) has been produced by the

Special Mobile Group (SMG) Technical Committee (TC) of the European Telecommunications Standards

Institute (ETSI).

This specification defines the stage 2 description of Customized Applications for Mobile network

Enhanced Logic (CAMEL) within the digital cellular telecommunications system (Phase 2/Phase 2+).

The contents of this TS are subject to continuing work within TC-SMG and may change following formal

TC-SMG approval. Should TC-SMG modify the contents of this GTS it will then be republished by ETSI

with an identifying change of release date and an increase in version number as follows:

Version 5.x.y

where:the third digit is incremented when editorial only changes have been incorporated in the

specification;

the second digit is incremented for all other types of changes, i.e. technical enhancements,corrections, updates, etc.


Blank page



1 Scope

This Technical Specification (TS) specifies the stage 2 description for the first phase (see GSM 02.78 [2])of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides themechanisms to support services of operators which are not covered by standardized GSM services evenwhen roaming outside the HPLMN.

The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the networkoperator to provide the subscribers with the operator specific services even when roaming outside theHPLMN.

In this specification, the GSM Service Control Function (gsmSCF) is treated as being part of the HPLMN.The regulatory environment in some countries may require the possibility that the gsmSCF and theHPLMN are controlled by different operators, and the gsmSCF and the HPLMN are therefore distinctentities.

In the first phase the CAMEL feature supports:- mobile originated and forwarded calls;- mobile terminating calls;- any time interrogation;- suppression of announcements;

Note that CAMEL is not applicable to Emergency Setup (TS 12), i.e., in case an Emergency call has beenrequested the gsmSSF shall not be invoked.

The mechanism described in this standard addresses especially the need for information exchangebetween the VPLMN or IPLMN and the HPLMN for support of operator specific services. Any userprocedures for the control of operator specific services are outside the scope of this standard.Subscribers who have subscribed to operator specific services and therefor need the functional support ofthe CAMEL feature shall be marked in the HPLMN and VPLMN. In case a subscriber is marked to needCAMEL support, the appropriate procedures which provide the necessary information to the VPLMN or tothe HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with agsmSCF which is controlled by the HPLMN.

The specification of operator specific services in HPLMN are outside the scope of this standard.

2 Normative references

This specification incorporates by dated and undated references, provisions from other publications.These normative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references, subsequent amendments to or revisions of any of these publicationsapply to this specification only when incorporated in it by amendment or revision. For undated referencesthe latest edition of the publication referred to applies.

[1] GSM 01.04 (ETR 350): "Digital cellular telecommunications system (Phase 2+);Abbreviations and acronyms".

[2] GSM 02.78: "Digital cellular telecommunications system (Phase 2+);Customized Applications for Mobile network Enhanced Logic (CAMEL) -stage 1

[3] GSM 03.18: "Digital cellular telecommunications system (Phase 2+); Basic callhandling".

[4] GSM 09.02 (ETS 300 974): "Digital cellular telecommunications system(Phase 2+); Mobile Application Part (MAP) specification".

[5] GSM 09.78: "Digital cellular telecommunications system (Phase 2+); CAMELApplication Part (CAP) specification".

[6] ITU-T Q.1214, May 1995: "Distributed Functional Plane for Intelligent NetworkCS-1"


3 Definitions and abbreviations

3.1 Definitions

For the purposes of this GTS, the following definitions apply:

Basic Call State Model (BCSM): The BCSM provides ahigh-level model of GMSC- or MSC/VLR-activities required to establish and maintain communication paths for users. As such, it identifies a set of

basic call activities in a GMSC or MSC/VLR and shows how these activities are joined together toprocess a basic call.

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).

GSM Service Control Function (gsmSCF): A functional entity that contains the CAMEL service logic toimplement OSS. It interfaces with the gsmSSF and the HLR.

GSM Service Switching Function (gsmSSF): A functional entity that interfaces the MSC/GMSC to thegsmSCF. The concept of the gsmSSF is derived from the IN SSF, but uses different triggeringmechanisms because of the nature of the mobile network.

Originating Basic Call State Model (O-BCSM): The originating half of the BCSM. The O-BCSMcorresponds to that portion of the BCSM associated with the originating party.

Originating CAMEL Subscription Information (O-CSI): The O-CSI identifies the subscriber as havingoriginating CAMEL services.

Point In Call (PIC): PICs identify MSC/VLR (GMSC) activities associated with one or more basiccall/connection states of interest to OSS service logic instances.

Location Information: Indicates the location of the served subscriber. The provision of locationinformation is independent of the MS status. As part of the location information, an indication of the age of

this information shall be delivered.

Service Key: The Service Key can identify to the gsmSCF the service logic that it should apply. TheService Key is administered by the HPLMN, and is passed transparently by the VPLMN/IPLMN to thegsmSCF. The Service Key is part of the T/O-CSI.

Subscriber State: See GSM 02.78 [2].

Terminating Basic Call State Model (T-BCSM): The terminating half of the BCSM. The T-BCSM

corresponds to that portion of the BCSM associated with the terminating party.

Terminating CAMEL Subscription Information (T-CSI): The T-CSI identifies the subscriber as havingterminating CAMEL services.

3.2 Abbreviations

Abbreviations used in this specification are listed in GSM 01.04

For the purposes of this TS, the following abbreviations apply

BCSM Basic Call State ModelCAMEL Customized Applications for Mobile network Enhanced LogicDP Detection PointEDP Event Detection PointGMSC Gateway MSCgsmSCF GSM Service Control FunctiongsmSSF GSM Service Switching FunctionHLR Home Location RegisterHPLMN Home PLMNIE Information Element



IFIPLMNMSCO-BCSMO-C SODBOSSPICPLMNSLPISMFT-BCSMT-CSITDPVLRVPLMN

4 Architecture

Information FlowInterrogating PLMNMobile service Switching CentreOriginating Basic Call State ModelOriginating CAMEL Subscription InformationOperator Determined BarringOperator Specific ServicePoint In CallPublic Land Mobile NetworkService Logic Program InstanceService Management FunctionTerminating Basic Call State ModelTerminating CAMEL Subscription InformationTrigger Detection PointVisitor Location RegisterVisited PLMN

4.1 Functional Entities used for CAMEL

This subclause describes the functional architecture needed to support CAMEL. Also the additions

needed to the basic GSM functionality are described. Figure /1 shows the functional entities involved in

calls requiring CAMEL support. The architecture is applicable to the first phase of CAMEL.

O<•--ay

~.

elnooming

~ ~ inn

L•'

V

~ ~'9i x~Roaming

3Fot~^'arded

W

', J

~ b

~ ill ~ ~ 3M

~~

W

Figure /1: Functional architecture for support of CAMEL

HLR: The HLR stores the O/T-CSI for subscribers requiring CAMEL support. The O-CSI is sent to the

VLR in case of Location Update or if the O-CSI is updated. The O/T-CSI is sent to the GMSC when the

HLR responds to a request for routing information. The HLR may provide an interface towards the

gsmSCF for the Any Time Interrogation procedure.

GMSC: When processing the calls for subscribers requiring CAMEL support the GMSC receives a

O/T-CSI from the HLR, indicating the GMSC to request instruction from the gsmSSF. 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.

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

""'~

.•~

VLR: The VLR stores the O-CSI as part of the subscriber data for subscribers roaming in the VLR area.


gsmSSF: see subclause 3.1.

gsmSCF: see subclause 3.1.

4.2 Interfaces defined for CAMEL

This subclause describes the different interfaces applicable to CAMEL. It specifies on a high level the

functions specific to CAMEL.

4.2.1 HLR - VLR interface

This interface is used to send the CAMEL related subscriber data to the visited PLMN and for provision of

MSRN. 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.

4.2.2 GMSC - HLR interface

This interface is used at terminating calls to exchange routing information, subscriber status, location

information, subscription information and suppression of announcements. The O/T-CSI that is passed to

the IPLMN is sent over this interface.

4.2.3 GMSC - gsmSSF interface

This is an internal interface. The interface is described in the specification to make it easier to understand

the handling of DPs (arming/disarming of DPs, DP processing etc.).

4.2.4 gsmSSF - gsmSCF interface

This intertace is used by the gsmSCF to control a call in a certain gsmSSF. Relationships on this interface

are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF.

4.2.5 MSC - gsmSSF interface

This an Internal interface. The interface is described in the specification to make it easier to understand

the handling of DPs (arming/disarming of DPs, DP processing etc.).

4.2.6 gsmSCF - HLR interface

This interface is used by the gsmSCF to request information from the HLR. Support of the gsmSCF - HLR

interface is a network operator option. As a network operator option the HLR may refuse to provide the

information requested by the gsmSCF.



5 Detection Points (DPs)

5.1 Definition and description

Certain basic call events may be visible to the GSM Service Control Function (gsmSCF). The DPs are thepoints in call at which these events are detected. The DPs for Mobile Originated Calls and MobileTerminated Calls are described in suclauses 7.2 and 7.3.

A DP can be armed in order to notify the gsmSCF that the DP was encountered, and potentially to allowthe gsmSCF to influence subsequent handling of the call. If the DP is not armed, the processing entitycontinues the processing without gsmSCF involvement.

Three different types of DPs are identified

Trigger Detection Point -Request (TDP-R)This detection point is statically armed and initiates a CAMEL control relationship whenencountered. Processing is suspended when the DP is encountered.

Event Detection Point -Request (EDP-R)This detection point is dynamically armed within the context of a CAMEL control relationship.Processing is suspended awaiting instructions from the gsmSCF when encountering the DP.

Event Detection Point -Notification (EDP-N)This detection point is dynamically armed within the context of a CAMEL control relationship.Processing is not suspended when encountering the DP.

The DPs are characterized by the following attributes:

a) Arming/disarming mechanism -The mechanism by which the DP is armed. A DP may be staticallyarmed or dynamically armed.

The following arming rules apply:- ADP is statically armed by provisioning the O/T-CSI in the HLR. A statically armed DP

remains armed until the O/T-CSI is withdrawn.- ADP is dynamically armed by the gsmSCF within the context of a CAMEL control

relationship (between the gsmSSF and the gsmSCF).

The following disarming rules apply:- A statically armed DP is disarmed when a O/T-CSI is withdrawn in the HLR. Only TDP-Rs

can be disarmed using this mechanism.- If an armed EDP is met, then it is disarmed.- If an EDP is met that causes the release of the related leg, then all EDPs related to that leg

are disarmed.- If a call is released, then all EDPs related to that call are disarmed.

b) Relationship -given that an armed DP was encountered, the gsmSSF provides an information flowvia a relationship.A relationship between the gsmSSF and the gsmSCF for the purpose of operator specific serviceprocessing is considered to be a CAMEL relationship. There are two types of CAMEL relationships:- A CAMEL control relationship if the gsmSCF is able to influence the call processing via the

relationship.- A CAMEL monitor relationship if the gsmSCF is not able to influence the call processing via

the relationship.

5.2 DP processing rules

Since a DP may be armed as an EDP-N or an EDP-R for the same call, the gsmSSF should apply thefollowing 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. Acontrol relationship terminates if there are no more EDP-Rs armed or the call clears. During acontrol relationship, EDPs are disarmed by the gsmSSF as they are encountered and reported tothe SCF, or when the call clears.

A control relationship changes to a monitor relationship if there are no more EDP-Rs armed and 1EDP-N armed. A monitor relationship terminates if there are no more EDP-Ns armed or the callclears. During a monitor relationship, EDP-Ns are disarmed by the gsmSSF as they areencountered and reported to the SCF, or when the call clears.

When the armed TDP-R is encountered triggering is unconditional.



6 Description of CAMEL Subscriber Data

6.1 Description- of OriginatinglTerminating CAMEL Subscription Information (O/T-CSI)

6.1.1 Content of the O/T-CSI

This subclause defines the contents of the OriginatinglTerminating CAMEL Subscription Information.

6.1.1.1 gsmSCF address

Address to be used to access the gsmSCF for a particular subscriber. The address shall be an E.164number to be used for routing.

6.1.1.2 Service Key

The Service Key identifies to the gsmSCF the service logic that should apply.

6.1.1.3 Default Call Handling

The Default Call Handling indicates whether the call shall be released or continued as requested in caseof error in the gsmSSF to gsmSCF dialogue.

6.1.1.4 TDP List

The TDP List indicates on which detection point triggering shall take place. For O-CSI only DP2 is used.ForT-CSI only DP12 is used.

6.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 theterminating call handling.

- an indication that the HLR shall send the location information of the called subscriber.

- an indication that the HLR shall send the subscriber state of the called subscriber.


7 Description of CAMEL BCSMs

7.1 General Handling

The BCSM is used to describe the actions in an MSC/GMSC during originating, forwarded or terminatingcal Is.

The BCSM identifies the points in basic call processing when Operator Specific Service (OSS) logicinstances (accessed through the gsmSCF) are permitted to interact with basic call control capabilities.

Figure 8.1/1 shows the components that have been identified to describe a BCSM.

i

~D

~JPoi~

Figure 7.1/1: BCSM Components

7.2 Originating Basic Call State Model (O-BCSM)

7.2.1 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.

When encountering a DP the O-BCSM processing is suspended at the DP and the MSC/GMSC indicatesthis to the gsmSSF which determines what action if any should be taken in case of the DP is armed.

Figure 7.2/1: Originating BCSM for CAMEL

The following table defines the different DPs which apply to mobile originating and forwarded calls.



Table 1: Definition of CAMEL Detection Points

CAMEL Detection Point: [6]: DP Type Description:

DP2 Collected Info DP2 TDP-R

DP7 O Answer DP7 EDP-N

DP9 O Disconnect DP9 EDP-N, EDP-R A disconnect indication is received from the

7.2.1.1 Description of the call model (PICs)

This subclause describes the call model for originating and forwarded calls. For each PIC a description

can be found of the entry events, functions and exit events.

It should be noted that although the names used for PICs match those used in ITU-T Q.1214 [6] the

specific descriptions differ.

7.2.1.1.1 O_Null & Authorise_Origination_Attempt Collect Info

Entry events:- Disconnect and clearing of a previous call (DP9 - O_Disconnect) or default handling of exceptions

by gsmSSF/(G)MSC completed.

Functions:- Interface is idled.- Originating call: SETUP message containing the dialled number is received from MS.

- Originating call: The supplementary services "barring of all outgoing calls" is checked and invoked

if necessary.- Originating call: The ODB categories "barring of all outgoing calls" and "barring of outgoing calls

when roaming" are checked and ODB is invoked if necessary.- Originating call: CUG checks done in the originating MSCNLR are performed.

- Forwarded call: Given the decision has been taken to forward an incoming call to a certain number,

the authority of the party to forward the call with the given properties is verified.

- Information being analysed e.g., O-CSI is analysed.

Exit events:- Originating CSI is analysed.- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions

during the PIC processing, the exception event is not visible because there is no corresponding DP.

Example exception conditions are:- Calling party abandons call.

7.2.1.1.2 Analyse, Routing &Alerting

Entry events:- Originating CSI is analysed. (DP2 -Collected Info)

Functions:- Information being analysed and/or translated according to dialling plan to determine routing

address.- Routing address being interpreted.- Originating call: Outgoing barring services and ODB categories not already applied are checked

and invoked if necessary.- Call is being processed by the terminating half BCSM. Continued processing of call setup (e.g.,

ringing) is taking place. Waiting for indication from terminating half BCSM that the call has been

answered by terminating party.

Exit events:- Indication from the terminating half BCSM that the call is accepted and answered by terminating

party. (DP7 - O_Answer)


- An exception condition is encountered -this leads to the O_Exception PIC. Example exceptionconditions are:

Calling party abandons call.- The called party is busy.- The called party does not answer the call.- Attempt to select the route for the call fails.

7.2.1.1.3 O Active

Entry events:- Indication from the terminating half BCSM that the call is accepted and answered by the

terminating party. (DP7 - O_Answer)

Functions:- Connection established between originating and terminating party. Call release is awaited.

Exit events:- A disconnection indication is received from the originating party, or received from the terminating

party via the terminating half BCSM. (DP9 - O_Disconnect)- An exception condition is encountered.

7.2.1.1.4 O_Exception

Entry events:- An exception condition is encountered. In addition to specific examples listed above, exception

events include any type of failure that means that the normal exit events for a PIC can not be met.

Functions:- Default handling of the exception condition is being provided. 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 instructionswill not run to completion

- The (G)MSC/gsmSSF should make use of vendor-specific procedures to ensure release ofresources within the (G)MSC/gsmSSF so that line, trunk and other resources are madeavailable for new calls.

Exit events:- Default handling of the exception condition by gsmSSF/(G)MSC completed.

7.3 Terminating Basic Call State Model (T-BCSM)

7.3.1 Description of T-BCSM

The T-BCSM is used to describe the actions in a GMSC during terminating calls.

When encountering a DP the T-BCSM processing is suspended at the DP and the GMSC indicates this tothe gsmSSF which determines what action if any should be taken in case of the DP is armed.



m

Figure 7.3/1: T-BCSM in the GMSC

In the following table the different DPs (in the T-BCSM) are described.

Table 2: Description of T-BCSM DPs in the GMSC

CAMEL Detection Point: [6]: DP Type Description:

DP12 Terminating_Attempt_Authorised DP12 TDP-R

DP15 T Answer DP15 EDP-N

DP17 T_Disconnect DP17 EDP-N, A disconnect indication is receivedEDP-R from the terminating party or from

7.3.1.1 Description of the call model (PICs)

This subclause describes the call model for terminating calls in the GMSC. For each PIC a descriptioncan be found of the entry events, functions, information available and exit events.

It should be noted that although the names used for PICs match those used in ITU-T Q.1214 [6] the

specific descriptions differ.

7.3.1.1.1 T_Null

Entry events:- Disconnect and clearing of a previous call (DP 17) or default handling of exceptions by

gsmSSF/GMSC completed.

Functions:- Interface is idled.- ISUP IAM is received, the appropriate information is analysed.- Send_Routeing_Info information flow is sent to HLR.- The supplementary services "barring of all incoming calls" and "barring of incoming calls when

roaming" are checked and invoked if necessary.- The ODB categories "barring of all incoming calls" and "barring of incoming calls when roaming"

are checked and ODB is invoked if necessary.- The supplementary service "CUG" is checked and invoked if necessary.- T-CSI is received and analysed.

Exit events:- Response is received from HLR and terminating CSI (if available) is analysed.- An exception condition is encountered. For this PIC, if the call encounters one of these exceptions

during the PIC processing, the exception event is not visible because there is no corresponding DP.

Example exception condition is:


- Calling party abandons call.

7.3.1.1.2 Terminating Call Handling

Entry events:- Response is received from HLR and terminating CSI (if available) is analysed. (DP 12

Terminating_Attempt_Authorised)

Functions:- The response from HLR is analysed.- Routing address and call type being interpreted. The next route is being selected.- The terminating party is being alerted. Waiting for the call to be answered by terminating party.- The GSM supplementary service call forwarding is invoked if necessary.

Exit events:- Call is accepted and answered by terminating party.- An exception condition is encountered -this lead to the T_Exception PIC. Example exception

conditions are:- Calling party abandons call.- The call setup to the MSC/GMSC was not successful.

7.3.1.1.3 T Active

Entry events:- Indication that the call is accepted and answered by the terminating party. (DP15 - T_Answer)

Functions:- Connection established between originating and terminating party. Call supervision is being

provided.- Call release is awaited.

Exit events:- A disconnection indication is received from the terminating party, or received from the originating

party via the originating half BCSM. (DP17 - T Disconnect)- An exception condition is encountered. In addition to specific examples listed above, exception

events include any type of failure that means that the normal exit events for a PIC can not be met.

7.3.1.1.4 T_Exception

Entry events:- An exception condition is encountered. In addition to specific examples listed above, exception

events include any type of failure that means that the normal exit events for PIC cannot be met.

Functions:- Default handling of the exception condition is being provided. 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 instructionswill not run to completion

- The GMSC/gsmSSF should make use of vendor-specific procedures to ensure release ofresources within the GMSC/gsmSSF so that line, trunk and other resources are madeavailable for new calls.

Exit events:Default handling of the exception condition by gsmSSF/GMSC completed.



7.4 BCSM Modelling of Call Scenarios

This subciause describes how the BCSMs defined above are used to model GSM call scenarios. For

each scenario the used and unused BCSMs involved in the call are shown.

In some cases these models may have an allocation to physical nodes different from that shown.

However, the physical separation of the logic functions shown shall not impact the modelling. This

subclause describes the call scenarios without optimal routing. If optimal routing is invoked the physical

configurations may be different from those shown, but the modelling is not changed.

CAMEL may be applied simultaneously and independently for each GSM subscriber involved in a call.

This is not shown in these scenarios.

Subscribers other than those being served by CAMEL may be either PSTN subscribers, other GSM

subscribers or any other addressable subscriber.

7.4.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. A

control or monitoring relationship with gsmSCF (1) will be created.

gsmSCF (1)

CAP control ormonitoring relationship

MSCgsmSSF/CCF

',

a`~ B~ . ~ ~ .~~~-a~ _.A-Party B-Party

Figure 7.4/1 BCSM Scenario for Mobile Originated Call


7.4.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. Acontrol or monitoring relationship with gsmSCF (1) will be created.

gsmSCF (1)

CAP control ormonitorvig relationship

GMSC MSCgsmSSF/CCF gsmSSF/CCF

aA-B~ ~ - -~ TEA-B~ i

A-Party

Figure 7.4/2 BCSM Scenario for Mobile Terminated Calls

7.4.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. Acontrol or monitoring relationship with gsmSCF (1) will be created.

Anew call leg to a "C" party is created if:

a GSM call forwarding supplementary service forwards the call to C; or

a CAMEL service in a control relationship with T(A-B) uses a Connect information flow containingthe " O-CSI Applicable" flag.

If the B-party has an active O-CSI the BCSM O(B-C) is invoked. A control or monitoring relationship withgsmSCF (2) will be created.

The relationships with gsmSCF (1) and gsmSCF(2) may exist simultaneously. The two relationships aretreated independently at the GMSC. The BCSM T(A-B) and BCSM O(B-C) are linked by an internalinterface which is assumed to behave in a similar way to an ISUP interface.

The nodes gsmSCF (1) and gsmSCF (2) may be the same or different physical entities.



gsmSCF (1) ~ ~ gsmSCF (2)

CAP control or CAP control ormonitoring relationship monitoring relationship

~~) ~~)

GMSC Internal "ISUP-gsmSSF/CCF like" interface

_aA_B~ -- -' TEA-B~ _ UA Party B'P~'

"------ I

T(B-C) - ( O(B-C) "surrogate"

GParty

Figure 7.4/3 BCSM Scenario for Call Forwarding at the GMSC

7.4.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. A

control or monitoring relationship with gsmSCF (1) will be created. Following processing at the GMSC the

call will be extended to the MSC serving the B-party. This MSC may be physically integrated with the

GMSC, but it is shown as being separate in the diagram below.

If a GSM call forwarding supplementary service acting at the MSC forwards the call to C, a new call leg to

C is established. If the B-party has an active O-CSI the BCSM O(B-C) is invoked. A control or monitoring

relationship with gsmSCF (2) will be created.

The relationships with gsmSCF (1) and gsmSCF(2) may exist simultaneously.

The nodes gsmSCF (1) and gsmSCF (2) may be the same or different physical entities.

gsmSCF (1)

CAP control ormonitoring relationship~~)

gsmSCF (2)

CAP control ormonitoring relationship

l2)

GMSC MSCgsmSSF/CCF gsmSSF/CCF

~(A-B) ; - - ~ T(A-B) ~ ~ - -'

A-Party ------ ' -

' TB-C ~- -~ B'C

B-PartyC-Party "Surrogate"

Figure 7.4/4 BCSM Scenario for Call Forwarding at the MSC


8 Procedures for CAMEL

The SDLs in this specification illustrate how CAMEL modifies the normal call handling. They do notattempt to show all the details of call handling in nodes that support CAMEL. Relevant parts of

GSM 03.18 [3] apply in additions to these SDLs. For example, some inputs leading to unsuccessful call

attempts are not shown on these diagrams -corresponding clauses in GSM 03.18 [3] apply.

8.1 Handling of mobile originated calls

8.1.1 Handling of Outgoing Call request in the MSC, Process CAMEL_OCH_MSC

The description of the handling of the CM Service Request from the MS is omitted (see

Process_Access_Request_MSC of GSM 03.18 [3]), as it has no impact on CAMEL.

The MSC sends the Send_Info_For_Outgoing_Call_1 and waits in the state Wait_For_MO_Call_Result_1

(shown in sheet 1).

8.1.1.1 Actions at state Wait For MO Call Result 1

The following actions are possible in the state Wait_For_MO_Call_Result_1 (shown in sheet 2):

8.1.1.1.1 Send_Info_For_Outgoing_Call_1 Negative Response

See process OCH_MSC of GSM 03.18 [3].

8.1.1.1.2 Complete Call 1

If the MSC has not received any O-CSI in the Complete_Call_1 from the VLR then the Call Handling

continues as specified in the process OCH_MSC of GSM 03.18 [3] by building an ISUP_IAM messageand sending it to the destination exchange.

If the MSC has received O-CSI from the VLR then gsmSSF is invoked. The MSC sends the O-CSI to thegsmSSF. When the invocation of gsmSSF is confirmed, the MSC sends Int_DP Collected_Info to thegsmSSF and then waits for an answer from the gsmSSF in state DP_Collected_Info.

8.1.1.2 Actions at state DP Collected Info

The following actions are possible in the state DP_Collected_Info (shown in sheets 3 and 5):

8.1.1.2.1 Int_Release_Call

A Release Transaction is sent to the MS and a Release to the VLR. The release cause received in theInt Release Call is used. The MSC then releases all call resources and the process CAMEL_OCH_MSC

returns to idle.

8.1.1.2.2 Int_Error

The MSC checks in O-CSI the default Call Handling parameter.

If the default call handling is release call, a Release Transaction is sent to the MS. The MSC then

releases all call resources and the process CAMEL_OCH_MSC returns to idle.

If the default call handling is continue call, the MSC continues processing without CAMEL support. Itsends Send_Info_For_Ougoing_Call_2 to the VLR and waits in state Wait_For_MO_Call_Result_2.

8.1.1.2.3 Int Continue

The MSC continues processing without any modification of call parameters. It sendsSend_Info_For_Ougoing_Call_2 to the VLR and waits in state Wait_For_MO_Call_Result_2.



8.1.1.2.4 Int_Connect

The MSC continues processing with modified call parameters. The MSC shall transparently modify thecall parameters with the received information. The MSC then sends a Progress message to the MScontaining a progress indicator information element to stop call timers at the MS. Call parameters that arenot included in the Int_Connect message are unchanged.

The MSC sends Send Info_For Ougoing_Call_2 to the VLR and waits in stateWait_For_MO_Call Result 2 Because of signalling limitations or regulatory requirements, the CallingPartys Category, Generic Number may be ignored or modified, Original Called Party Number andRedirecting Party ID.

Handling of Calling Party Number is operator specific.

8.1.1.2.5 Release Transaction

If the gsmSSF receives a release message from the MS, the MSC sends Int_O_Exception to gsmSSF,releases all call resources and returns to idle.

8.1.1.3 Actions at state Wait For MO Call Result 2

The following actions are possible in the state Wait_For_MO_Call_Result_2 (shown in sheets 3 and 5):

8.1.1.3.1 Send_Info Negative Response

The MSC sends an indication to the gsmSSF that the call handling is aborted (Int_O_Exception) and aRelease_Transaction to the MS. The MSC then releases all call resources and the processCAMEL OCH MSC returns to idle.


A Release Transaction is sent to the MS. The release cause received in the Int Release Call is used.The MSC then releases all call resources and the process CAMEL_OCH_MSC returns to idle.


If the MSC received from the MS a release call indication then the MSC informs the gsmSSF that the callhandling has been aborted (Int_O_Exception), releases all call resources and returns to idle.

8.1.1.3.4 Complete Call 2

The MSC sends an ISUP_IAM and waits for the connection to be established (Wait_For_ACM_2).

8.1.1.4 Actions at state Wait For ACM 2

The following actions are possible in the state Wait_For_ACM_2 (shown in sheets 4 and 5):

8.1.1.4.1 ISUP_ACM

If the MSC receives ISUP ACM from destination exchange, the MSC alerts the calling party and waits inWait For ANM 2.

8.1.1.4.2 ISU P_Connect

If ISUP Connect is received from the destination exchange, the MSC informs the gsmSSF thatInt_DP_O_Answer has occurred, suspends the call process and waits in the state DP_O_Answer.

8.1.1.4.3 ISUP_Release

If the MSC received from the ISUP interface a release call indication then the MSC informs the gsmSSFthat the call handling has been aborted (Int_O_Exception), releases all call resources and returns to idle.



If the MSC received from the MS a release call indication then the MSC informs the gsmSSF that the call

handling has been aborted (Int_O_Exception), releases call resource and returns to idle.


A Release Transaction is sent to the MS and an ISUP Release is sent to the destination exchange. The

ISUP Release contains the release cause received in the Int Release Call. The received release cause

is also used in the release towards the MS. The MSC then releases all call resources and the process

CAMEL OCH MSC returns to idle.

8.1.1.5 Actions at state Wait For ANM 2

The following actions are possible in state Wait_For_ANM_2 (shown in sheets 4 and 5):


If the MSC receives from the MS a release call indication then the MSC informs the gsmSSF that the call

handling has been aborted (Int_O_Exception), releases all call resources and returns to idle.

8.1.1.5.2 I nt_Release_Ca

A Release Transaction is sent to the MS and an ISUP Release is sent to the destination exchange. The




8.1.1.5.3 ISU P_Answer

If the MSC receives ISUP Answer from the destination exchange, the MSC informs the gsmSSF that the

answer has been received (Int_DP_O_Answer) and waits in state DP_O_Answer.

8.1.1.6 Actions at DP O Answer

The following actions are possible in state DP_O_Answer (shown in sheets 4 and 6):


The gsmSSF instructs the MSC to continue call handling. The MSC sends a connect message to the MS

and waits in state Wait For Clear 2.


The DP O Disconnect is reported to the gsmSSF (Int_DP_O_Disconnect). This message contains an

indication (IegID=1) that the calling party has disconnected.

If Int Continue or Int Release Call is received from the gsmSSF, a ISUP_Release is forwarded to the

destination exchange. The MSC then releases all call resources and the process CAMEL_OCH_MSC

returns to idle.

If ISUP Release is received from the destination exchange before gsmSSF has responded to the

Int DP O_Disconnect (IegID=1), the DP O_Disconnect is reported to the gsmSSF. This message

contains an indication (IegID=2) that the called party has disconnected. When Int Continue or

Int Release_Call is received from the gsmSSF, the MSC releases all call resources and the process


8.1.1.6.3 ISUP_Release from destination exchange

The DP O Disconnect is reported to the gsmSSF. This message contains an indication (IegID=2) that the

called party has disconnected.



If Int Continue or Int_Release_Call is received from the gsmSSF, Release Transaction is forwarded to

the MS. If Int Release Call was received the received release cause is used. The MSC then releases all

call resources and the process CAMEL_OCH_MSC returns to idle.

If Release Transaction is received from the MS before gsmSSF has responded to the


contains an indication (IegID=1) that the calling party has disconnected. When Int Continue or

Int Release Call is received from the gsmSSF, the MSC releases all call resources and the process


8.1.1.7 Actions at state Wait For Connect Ack 2

See process OCH_MSC of GSM 03.18 [3].

8.1.1.8 Actions at state Wait For Clear 2

The following actions are possible in state Wait_For_Clear_2 (shown in sheets 5 and 6)


The DP O_Disconnect is reported to the gsmSSF. This message contains an indication (IegID=1) that

the calling party has disconnected.

If Int Continue or Int_Release Call is received from the gsmSSF, a ISUP_Release is forwarded to the

destination exchange. The ISUP Release contains, if Int Release_Call was received, the received

release cause. The MSC then releases all call resources and the process CAMEL_OCH_MSC returns to

idle.



contains an indication (IegID=2) that the called party has disconnected. When Int_Continue or

Int Release_Call is received from the gsmSSF, the MSC releases all call resources and the process





If Int Continue or Int_Release_Call is received from the gsmSSF, Release_Transaction is forwarded to

the MS. If Int Release Call was received the received release cause is used. The MSC then releases all

call resources and the process CAMEL_OCH_MSC returns to idle.

If Release Transaction is received from the MS before gsmSSF has responded to the

Int_DP O_Disconnect (IegID=2), the DP O_Disconnect is reported to the gsmSSF. This message


Int_Release Call is received from the gsmSSF, the MSC releases all call resources and the process


8.1.1.8.3 Int Release Call

A Release_Transaction is sent to the MS and an ISUP Release is sent to the destination exchange. The





8.1.2 Handling of Outgoing Call request in the VLR, process CAMEL_OCH_VLR

See process OCH_VLR in GSM 03.18 [3] for the handling before the state Wait_For_SIFOC.

8.1.2.1 Actions at state Wait For SIFOC

If the VLR receives an SIFOC message from the MSC, the VLR then performs the subscription check forthe provision of the basic service. If the Service is provisioned then it verifies if the subscriber has O-CSIin his subscriber profile. If no O-CSI is present then the normal checks apply.

If O-CSI is present then the VLR executes the procedure Check_BAOC specified in GSM 03.18 [3].

If as a result of this procedure the call is barred then the VLR returns a negative response to the MSC. Ifthe call is not barred then the VLR executes the procedure OG_CUG_Check specified in GSM 03.18 [3].

If as a result of this procedure the call is not allowed then the VLR returns a negative response to theMSC. If the call is allowed then the VLR executes both procedure Get_U_Subscription_Info_MO VLRand Get_AoC_Subscription_Info_VLR, returns information to the MSC including O-CSI and waits in thestate Wait For SIFOC 2.

8.1.2.2 Actions at state Wait For SIFOC 2

The following actions are possible in state Wait_For_SIFOC_2 (shown in sheet 2):

8.1.2.2.1 Send_Info_For_Outgoing_Call_2

When receiving the second SIFOC interrogation from the MSC, the VLR executes the procedureCheck_OG_Barring specified in GSM 03.18 [3].

If the call is barred the VLR returns a negative response to the MSC.

If the call is not barred the VLR returns a Complete_Call_2 message to the MSC.

8.1.2.2.2 Release

The process CAMEL_OCH_VLR returns to idle.



8.2 Handling of mobile terminating calls

8.2.1 Handling of terminating call request in the GMSC, Process CAMEL_MT_GMSC

8.2.1.1 Reception of ISUP_IAM

At the reception of an ISUP IAM the GMSC sends a Send Routeing Info to the HLR. The Send Routeing

Info includes an indication which phase of CAMEL is supported by the GMSC/gsmSSF. The GMSC waits

in state Wait_For_Routeing_Info_1.

8.2.1.2 Actions at state Wait_For_Routeing_Info_1

The following actions are possible in the state Wait For_Routeing_Info_1 depending on the result of the

Send Routeing Info sent to the HLR (shown in sheets 1 and 2):

8.2.1.2.1 Send_Routeing_Info Negative Response

See process MT_GMSC of GSM 03.18 [3].

8.2.1.2.2 Send_Routeing_Info Ack with MSRN


8.2.1.2.3 Send_Routeing_Info Ack with FTN


8.2.1.2.4 Send_Routeing_Info Ack with T-CSI and possibly FTN and/or O-CSI

If received, the FTN with related forwarding information and/or O-CSI are stored. The call processing is

suspended and the process gsmSSF is invoked. The event Int DP Termination_Attempt_Authorised is

reported to the gsmSSF. The GMSC waits in state DP_Termination_Attempt_Authorised.

8.2.1.2.5 Send_Routeing_Info Ack with O-CSI and FTN

The information received from the HLR is used to overwrite corresponding call parameters (for details see

process SRI HLR of GSM 03.18 [3]). The redirection counter is incremented and the process

CAMEL_CF MSC GMSC is invoked. Note that the MSISDN has been replaced by the FTN as the Called

Party Number. The continued processing in process CAMEL MT GMSC is described in process

MT GMSC of GSM 03.18 [3], ISUP signals from the right in GSM 03.18 are received from process

CAMEL_CF_MSC_GMSC instead of the destination exchange.

8.2.1.2.6 ISUP_Release received from originating exchange

An exception event is reported to the gsmSSF.

8.2.1.3 Actions at state DP_Termination_Attempt_Authorised

The following actions are possible in the state DP_Termination_Attempt_Authorised (shown in sheet 3):


An ISUP_Release is sent to the originating exchange and resources are released.

8.2.1.3.2 Int_Error

The GMSC checks in T-CSI the default Call Handling parameter.

If the default call handling is release call, an ISUP Release is sent to the originating exchange. The MSCthen releases all call resources and the process CAMEL_MT_GMSC returns to idle.


If the default call handling is continue call, the MSC continue call handling without CAMEL support see

subclause 8.2.1.3.3 Int Continue.


If a FTN has been stored the information received from HLR in state Wait For_Routeing_Info_1 is used

to overwrite corresponding call parameters (for details see GSM 03.18 [3]). Note that the MSISDN is

replaced by the FTN as the Called party number. The redirection counter is incremented. If O-CSI has

been stored the process CAMEL CF MSC_GMSC is invoked. Otherwise an ISUP_IAM is constructed

and the GMSC waits in state Wait For Answer 1.

If no FTN has been stored, a Send Routeing Info with suppressed T-CSI indication is sent to the HLR.

The Send Routing Info includes an indication which phase of CAMEL is supported by the

GMSC/gsmSSF. The GMSC waits in state Wait_For_Routeing_Info_2.


The GMSC shall send an ISUP_ACM towards the originating exchange in order to stop any call timers.

If the Destination Number received from the gsmSCF (via the gsmSSF) is the same as the ISUP Called

party number, i.e. the MSISDN, the following parameters, if received, are used to overwrite the

corresponding ISUP parameters (for mapping see GSM 09.78 [5]): Calling Partys Category, Calling Party

Number and Generic Number. If received, the Announcement Suppression Indicator is stored. The further

processing is described in subclause Int_Continue with the addition that the Announcement Suppression

indicator, if stored is sent to the HLR in the Send_Routeing_Info message.

If:- the Destination Number received from the gsmSCF (via the gsmSSF) is not the same as the stored

ISUP Called party number, i.e. the MSISDN; and

- a CUG active indication was received from the HLR in the state Wait_For_Routeing_Info_1;and

- CUG information was received in the ISUP_IAM for the incoming call,

then an exception event is reported to the process gsmSSF, an ISUP_Release is sent to the originating

exchange and all resources are released.

Otherwise the following parameters, if received, are used to overwrite the corresponding ISUP

parameters (for mapping see GSM 09.78 [5]): Destination Number, Calling Partys Category, Calling Party

Number, Generic Number, Original Called Party ID, Redirecting Party ID and Redirection Information. Call

parameters that are not included in the Int_Connect message are unchanged.

Because of loop prevention mechanisms the redirection information may as a network option be ignored

or modified (e.g., if the Redirection counter has been decreased).

If a O-CSI Applicable indication was received from the gsmSCF (via the gsmSSF) and the O-CSI was

received from the HLR in the state Wait For_Routeing_Info_1, the process CAMEL_CF_MSC_GMSC is

invoked. Otherwise an ISUP IAM is constructed.

Because of signalling limitations or regulatory requirements, the Calling Partys Category, Generic

Number, Original Called Party Number and Redirecting Party ID may be ignored of modified.

Handling of Calling Party Number is operator specific.



8.2.1.4 Actions at state Wait_For_Routeing_Info_2

The following actions are possible in the state Wait For_Routeing_Info_2 depending on the result of the

Send Routeing Info sent to the HLR (shown in sheets 4 and 5):



8.2.1.4.1 Send_Routeing_Info Negative Response

An ISUP Release is sent to the originating exchange. An exception event is reported to the process

gsmSSF. If the Announcement Suppression indicator has been received from the gsmSCF (via the

gsmSSF) any announcements or tones shall be suppressed. The resources are released.

8.2.1.4.2 Send_Routeing_Info Ack with MSRN

An ISUP_IAM with the MSRN as Called party number is constructed.

8.2.1.4.3 Send_Routeing_Info Ack with FTN

The information received from HLR is used to overwrite corresponding call parameters (for details see

GSM 03.18 [3]). The redirection counter is incremented. An ISUP_IAM is constructed.

8.2.1.4.4 Send_Routeing_Info Ack with O-CSI and FTN

The information received from the HLR is used to overwrite corresponding call parameters (for details see

GSM 03.18 [3]). The redirection counter is incremented and the process CAMEL_CF_MSC_GMSC is

invoked.

NOTE: The MSISDN is replaced by the FTN as the Called party number.


An ISUP Release is sent to the originating exchange. The ISUP Release contains the release cause

received in the Int Release Call. The GMSC then releases all call resources and the process

CAMEL MT GMSC returns to idle.



8.2.1.5 Actions at state Wait For Answer 1

The following actions are possible in the state Wait_For_Answer_1 (shown in sheet 6):

8.2.1.5.1 ISUP_Release from originating exchange

The ISUP Release is forwarded to the destination exchange or, in case an originating CAMEL service

has been invoked on the outgoing call leg, to the process CAMEL_CF_MSC_GMSC. An exception event

is reported to the process gsmSSF.

8.2.1.5.2 ISUP_Release from destination exchange or process CAMEL_CF_MSC_GMSC

The ISUP_Release is forwarded to the originating exchange. An exception event is reported to the

process gsmSSF.


An ISUP Release is sent to the destination exchange or, in case an originating CAMEL service has been

invoked on the outgoing call leg, to the process CAMEL_CF_MSC GMSC. An ISUP_Release is also sent

to the originating exchange. Both ISUP Release messages contain the release cause received in the

Int Release Call. The GMSC then releases all call resources and the process CAMEL_MT_GMSC

returns to idle.

8.2.1.5.4 I S U P_Answer

The DP_T_Answer is reported to the gsmSSF and the process CAMEL MT_GMSC waits in state

DP T Answer.


8.2.1.6 Actions at state DP T Answer

The following actions are possible in the state DP_T_Answer_1 (shown in sheets 6 and 7)


The DP_T Disconnect is reported to the gsmSSF. This message contains an indication (IegID=1) that thecalling party has disconnected.

If Int Continue or Int_Release_Call is received from the gsmSSF, ISUP_Release is forwarded to thedestination exchange or, in case an originating CAMEL service has been invoked on the outgoing call leg,to the process CAMEL_CF_MSC GMSC. The ISUP_Release contains, if Int_Release_Call was received,the received release cause. The GMSC then releases all call resources and the processCAMEL MT GMSC returns to idle.

If an ISUP_Release is received from the destination exchange before gsmSSF has responded to theInt_DP O Disconnect (IegID=1) or, in case an originating CAMEL service has been invoked on theoutgoing call leg, from the process CAMEL CF MSC GMSC, the DP T Disconnect is reported to thegsmSSF. This message contains an indication (IegID=2) that the called party has disconnected. WhenInt_Continue or Int_Release Call is received from the gsmSSF, the GMSC releases all call resources andprocess CAMEL_MT_GMSC returns to idle.


The DP_T_Disconnect is reported to the gsmSSF. This message contains an indication (IegID=2) that thecalled party has disconnected.

If Int Continue or Int Release Call is received from the gsmSSF, ISUP Release is forwarded to theoriginating exchange The ISUP_Release contains, if Int_Release_Call was received, the receivedrelease cause. The GMSC then releases all call resources and the process CAMEL_MT_GMSC returnsto idle.

If an ISUP Release is received from the originating exchange before gsmSSF has responded to theInt DP O_Disconnect (IegID=2), the DP T_Disconnect is reported to the gsmSSF. This messagecontains an indication (IegID=1) that the calling party has disconnected. When Int Continue orInt Release Call is received from the gsmSSF, the GMSC releases all call resources and the processCAMEL MT GMSC returns to idle.

8.2.1.6.3 Int_Release_Cal

An ISUP Release is sent to the destination exchange or, in case an originating CAMEL service has beeninvoked on the outgoing call leg, to the process CAMEL_CF_MSC GMSC. An ISUP_Release is also sentto the originating exchange. Both ISUP Release messages contain the release cause received in theInt Release Call. The GMSC then releases all call resources and the process CAMEL_MT_GMSCreturns to idle.

8.2.1.7 Int Continue

An ISUP_Answer is sent to the originating exchange and the process CAMEL_MT_GMSC waits in stateWait For Clear 1.

8.2.1.7 Actions at state Wait For Clear 1

The following actions are possible in the state Wait_For_Clear_1 (shown in sheet 7):


The DP T_Disconnect is reported to the gsmSSF. This message contains an indication (IegID=1) that thecalling party has disconnected.

If Int Continue or Int_Release_Call is received from the gsmSSF, ISUP_Release is forwarded to thedestination exchange or, in case an originating CAMEL service has been invoked on the outgoing call leg,



to the process CAMEL_CF_MSC GMSC. The ISUP_Release contains, if Int_Release_Call was received,

the received release cause. The GMSC then releases all call resources and the process


If an ISUP Release is received from the destination exchange before gsmSSF has responded to the

Int DP O Disconnect (IegID=1) or, in case an originating CAMEL service has been invoked on the

outgoing call leg, from the process CAMEL CF MSC GMSC, the DP T Disconnect is reported to the

gsmSSF. This message contains an indication (IegID=2) that the called party has disconnected. When

Int_Continue or Int_Release Call is received from the gsmSSF, the GMSC releases all call resources and

process CAMEL_MT_GMSC returns to idle.


The DP T Disconnect is reported to the gsmSSF. This message contains an indication (IegID=2) that the


If Int Continue or Int Release Call is received from the gsmSSF, ISUP Release is forwarded to the

originating exchange The ISUP Release contains, if Int_Release_Call was received, the received

release cause. The GMSC then releases all call resources and the process CAMEL_MT_GMSC returns

to idle.

If an ISUP Release is received from the originating exchange before gsmSSF has responded to the

Int DP O_Disconnect (IegID=2), the DP T_Disconnect is reported to the gsmSSF. This message


Int Release Call is received from the gsmSSF, the GMSC releases all call resources and the process



An ISUP Release is sent to the destination exchange or, in case an originating CAMEL service has been

invoked on the outgoing call leg, to the process CAMEL_CF_MSC GMSC. An ISUP_Release is also sent

to the originating exchange. Both ISUP Release messages contain the release cause received in the

Int Release Call. The GMSC then releases all call resources and the process CAMEL_MT_GMSC

returns to idle.


8.2.2 Handling of request for routing information, Process CAMEL_SRI_HLR

8.2.2.1 Reception of Send_Routeing_Info

At the reception of a Send Routeing_Info from the GMSC, the HLR executes the procedures

Check Parameters, Subscription_Check_HLR and First_Forwarding_HLR as described in process

SRI_HLR of GSM 03.18 [3].

If the GMSC does not support CAMEL phase 1 the HLR may apply ODB, allow the call to continue

without CAMEL or take network specific actions. The handling is subscriber specific.

8.2.2.1.1 Continue call handling

If the call is not to be forwarded and T-CSI is not present, a Provide_Roaming_Number is sent to the

VLR. The HLR waits in state Wait For MSRN.

If the call is not to be forwarded and T-CSI is present, a Send Routeing_Info Ack is sent to the GMSC

with T-CSI and O-CSI, if present. Also Subscriber Information (Location Information and/or Subscriber

State) is sent to the GMSC, if indicated by the Subscriber Information in SRI Ack indicator. The process

CAMEL SRI HLR returns to idle.

8.2.2.1.2 Call forwarded

The HLR executes the procedures Forward_CUG_Check as described in process SRI_HLR of

GSM 03.18 [3].

8.2.2.1.2.1 Call allowed

If the call is allowed, a Send Routeing Info Ack is sent to the GMSC with FTN and T-CSI/O-CSI if present.

8.2.2.1.2.2 Call not allowed

If the call is not allowed and T-CSI is not present, a Send_Routeing_Info Negative Response is sent and

the process CAMEL_SRI_HLR returns to idle.

If the T-CSI is present, a Send Routeing Info Ack is sent to GMSC with T-CSI and O-CSI, if present. Also

Subscriber Information (Location Information and/or Subscriber State) is sent to the GMSC, if indicated by

the Subscriber Information in SRI Ack indicator. The process CAMEL_SRI_HLR returns to idle.

8.2.2.1.3 Call forwarding fails

If the HLR fails to forward the call and T-CSI is not active, a Send_Routeing_Info Negative Response is

sent and the process CAMEL_SRI_HLR returns to idle.

If the T-CSI is present, a Send Routeing Info Ack is sent to GMSC with T-CSI and O-CSI, if present. The

process CAMEL_SRI_HLR returns to idle.

8.2.2.2 Actions at state Wait For MSRN

The following actions are possible in the state Wait For_MSRN depending on the result of the Provide

Roaming Number sent to the VLR (shown in sheet 2):

8.2.2.2.1 Provide_Roaming_NumberAckfromVLR

See process SRI_HLR of GSM 03.18 [3].

8.2.2.2.2 Provide_Roaming_Number Negative Response from VLR

The HLR executes the procedures PRN_Error_HLR and Forward_CUG_Check as described in process

SRI_HLR of GSM 03.18 [3].



8.2.2.2.2.1 Call allowed

If the call is allowed, a Send Routeing Info Ack is sent to the GMSC with FTN and T-CSI/O-CSI if present.

8.2.2.2.2.2 Call not allowed

If the call is not allowed and T-CSI is not present, a Send_Routeing_Info Negative Response is sent andthe process CAMEL_SRI_HLR returns to idle.

If the T-CSI is present, a Send Routeing Info Ack is sent to GMSC with T-CSI and O-CSI, if present. AlsoSubscriber Info is sent to the GMSC, if requested. The process CAMEL_SRI_HLR returns to idle.


8.2.2.3 Macro CSI_Check



8.2.3 Handling of Subscriber Information retrieval in the HLR, Procedure CAMEL_PSI_HLR

8.2.3.1 MS reachable

A Provide_Subscriber_Info Request is sent to VLR and the HLR waits in state Wait_For_Information.

If the VLR returns a Provide Subscriber_Info Response, the HLR uses the returned information to set the

Subscriber Info to be returned to the gsmSCF. As a network option, the HLR may use the returned Cell Id

or Location Area to derive the location number and/or Geographical Info.

NOTE: The handling in the VLR of Provide_Subscriber_Info Request is defined in

GSM 03.18 [3].

8.2.3.2 MS not reachable

8.2.3.2.1 Location Information requested

If VLR number is available in the HLR, then the Location Information is set to this parameter only.

If location information is not available in the HLR, no location information is set.

8.2.3.2.2 Subscriber State requested

The Subscriber State is set to "Network determined not reachable".

8.2.3.3 Actions at state Wait For Information

The following actions are possible in state Wait_For_Information depending on the result of the

Provide_Subscriber_Info Request sent to VLR.

8.2.3.3.1 Provide_Subscriber_Info Response

The Location Information or/and the Subscriber State are set to the received information.

8.2.3.3.2 Provide_Subscriber_Info Negative Response

This is handled as in suclause 8.2.3.2.



8.2.4 Handling of provide roaming number request in the VLR, CAMEL_PRN_VLR

8.2.4.1 Reception of Provide Roaming Number

At the reception of a Provide Roaming Number the VLR processes the request as specified in

GSM 03.18 [3] except for the handling of the Suppression of Announcement and Tones indicator.

8.2.4.2 IMSI known in VLR

If a roaming number is available and suppression of announcements and tones has been requested, the

VLR sets the SOA. See GSM 03.18 [3] for further processing.

8.2.4.3 IMSI not known in VLR

If a roaming number is available and suppression of announcements and tones has been requested, the

VLR sets the SOA. See GSM 03.18 [3] for further processing.



8.2.5 Handling of call forwarding in the MSC/GMSC, Process CAMEL_CF_MSC_GMSC

A mobile terminated call can be forwarded either in the GMSC (indicated by provision of Forwarded-To-Number from HLR or gsmSCF) or in the MSC (indicated by provisioning of Forwarded-To-Number fromVLR). The process CAMEL_CF_MSC_GMSC describes the handling in GMSC or MSC of the outgoingcall leg.

The process CAMEL CF_MSC_GMSC invokes the process gsmSSF and sends the O-CSI. When theinvocation of gsmSSF is confirmed, the process CAMEL_CF_MSC_GMSC sends an Int_Collected_Infoto the gsmSSF and waits in state DP_Collected_Info.

8.2.5.1 Actions at state DP Collected Info

The following actions are possible in state DP_Collected_Info (shown in sheet 2):

8.2.5.1.1 ISUP_Release from process CAMEL_ICH_MSC/CAMEL_MT_GMSC

An Int_O_Exception is sent to the gsmSSF. The process CAMEL_CF_MSC_GMSC releases allresources and returns to idle.


An ISUP Release is sent to the process CAMEL ICH MSC/CAMEL_MT_GMSC. The ISUP Releasecontains the release cause received in the Int_Release_Call. The process CAMEL_MT_GMSC thenreturns to idle.

8.2.5.1.3 Int_Error

The GMSC/MSC checks in O-CSI the default Call Handling parameter.

If the default call handling is release call, an ISUP Release is sent to the processCAMEL_ICH_MSC/CAMEL_MT_GMSC. The process CAMEL_CF_MSC_GMSC then returns to idle.

If the default call handling is continue call, the GMSC/MSC continue call handling . An ISUP IAM is sentto the destination exchange and the process CAMEL_ICH_MSC/CAMEL_MT_GMSC waits in stateWait For Answer.


An ISUP IAM is sent to the destination exchange to set up the call. The MSC waits in stateWait For Answer.


The GMSC/MSC sends an ISUP_ACM to the originating exchange in order to stop any call timers.

The received parameters are used to overwrite the corresponding ISUP parameters (for mapping seeGSM 09.78 (5]. The MSC/MSC sends an ISUP IAM to the destination exchange and waits in stateWait_For Answer. Call parameters that are not included in the Int_Connect message are unchanged.

Because of loop prevention mechanisms the redirection information may as a network option be ignoredor modified (e.g., if the Redirection counter has been decreased).

Because of signalling limitations, regulatory requirements, the Calling Partys Category, Generic Number,Original Called Party Number and Redirecting Party ID may be ignored or modified.

Handling of Calling Party Number is operator specific


8.2.5.2 Actions at state Wait For Answer


The ISUP Release is forwarded to the destination exchange and an exception event is reported to the

gsmSSF. The process CAMEL_CF_MSC_GMSC then returns to idle.


The ISUP_Release is forwarded to the process CAMEL ICH MSC/CAMEL MT_GMSC and an

exception event is reported to the gsmSSF. The process CAMEL_CF_MSC_GMSC then returns to idle.


An ISUP_Release is sent to the process CAMEL ICH_MSC/CAMEL_MT GMSC and to the terminating

exchange. Both ISUP_Release messages contain the release cause received in the Int_Release_Call.

The process CAMEL_CF_MSC_GMSC then returns to idle.

8.2.5.2.4 ISUP_Answer

The process CAMEL CF MSC_GMSC reports DP_O_Answer to the gsmSSF and waits in state

DP_O_Answer for instructions from the gsmSSF.

8.2.5.3 Actions at state DP O Answer

The following actions are possible in the state DP_O_Answer (shown in sheets 3 and 4):


The process CAMEL ICH MSC/CAMEL_MT_GMSC sends an ISUP_Answer to the originating exchange

and waits in state Wait For Clear.

8.2.5.3.2 ISUP_Release from process CAMEL_ICH_MSC/CAMEL_MT_GMSC

The DP_O Disconnect is reported to the gsmSSF. This message contains an indication (IegID=1) that the

calling party has disconnected.

If Int Continue or Int_Release Call is received from the gsmSSF, ISUP Release is forwarded to the

destination exchange. The ISUP Release contains, if Int Release Call was received, the received

release cause. The process CAMEL_CF_MSC_GMSC then returns to idle.


Int_DP_O_Disconnect (IegID=1), the DP O_Disconnect is reported to the gsmSSF. This message

contains an indication (IegID=2) that the called party has disconnected. When Int_Continue or

Int_Release_Call is received from the gsmSSF, the process CAMEL_CF_MSC_GMSC returns to idle.




If Int_Continue or Int_Release Call is received from the gsmSSF, ISUP Release is forwarded to the

process CAMEL ICH MSC/CAMEL MT GMSC. The ISUP Release contains, if Int Release_Call was

received, the received release cause. The process CAMEL_CF_MSC_GMSC returns to idle.

If ISUP Release is received from the CAMEL ICH MSC/CAMEL_MT GMSC before gsmSSF has

responded to the Int DP O Disconnect (IegID=2), the DP_O Disconnect is reported to the gsmSSF. This

message contains an indication (IegID=1) that the calling party has disconnected. When Int Continue or

Int_Release_Call is received from the gsmSSF, the process CAMEL_CF_MSC_GMSC returns to idle.




An ISUP_Release is sent to the process CAMEL ICH_MSC/CAMEL_MT GMSC and to the terminatingexchange. Both ISUP Release messages contain the release cause received in the Int_Release_Call.The process CAMEL_CF_MSC_GMSC then returns to idle.

8.2.5.4 Actions at state Wait For Clear

The following actions are possible in the state Wait_For_Clear (shown in sheet 4):

8.2.5.4.1 ISUP_Release from process CAMEL_ICH_MSC/CAMEL_MT_MSC_GMSC

The DP_O Disconnect is reported to the gsmSSF. This message contains an indication (IegID=1) that thecalling party has disconnected.

If Int_Continue or Int Release Call is received from the gsmSSF, ISUP Release is forwarded to thedestination exchange. The ISUP Release contains, if Int Release Call was received, the receivedrelease cause. The process CAMEL_CF_MSC_GMSC then returns to idle.

If ISUP Release is received from the destination exchange before gsmSSF has responded to theInt DP O_Disconnect (IegID=1), the DP O_Disconnect is reported to the gsmSSF. This messagecontains an indication (IegID=2) that the called party has disconnected. When Int_Continue orInt_Release_Call is received from the gsmSSF, the process CAMEL_CF_MSC_GMSC returns to idle.


The DP O Disconnect is reported to the gsmSSF. This message contains an indication (IegID=2) that thecalled party has disconnected.

If Int_Continue or Int_Release Call is received from the gsmSSF, ISUP Release is forwarded to theprocess CAMEL ICH MSC/CAMEL MT GMSC. The ISUP Release contains, if Int Release Call wasreceived, the received release cause. The process CAMEL_CF_MSC_GMSC then returns to idle.

If ISUP Release is received from the CAMEL ICH MSC/CAMEL_MT GMSC before gsmSSF hasresponded to the Int_DP O Disconnect (IegID=2), the DP_O Disconnect is reported to the gsmSSF. Thismessage contains an indication (IegID=1) that the calling party has disconnected. When Int Continue orInt_Release_Call is received from the gsmSSF, the process CAMEL_CF_MSC_GMSC returns to idle.


An ISUP_Release is sent to the process CAMEL_ICH_MSC/CAMEL_MT GMSC and to the terminatingexchange. Both ISUP Release messages contain the release cause received in the Int_Release_Call.The process CAMEL_CF_MSC_GMSC then returns to idle.



8.2.6 Handling of incoming call handling in the MSC, process CAMEL_ICH_MSC

See process ICH_MSC in 03.18 [3] for the handling before the state Wait_For_MT_Call_Result.

8.2.6.1 Wait For MT Call Result

Added to the basic handling of incoming calls tones and announcements generated as a result of

unsuccessful call setup shall be suppressed in case the SOA parameter has been stored. This subclause

only describes the case when the call is to be forwarded.

8.2.6.2 Send_Info_For_Incoming_Call Ack

A Perform CF including FTN and O-CSI, previously received from the VLR is sent to the processCAMEL CF MSC_GMSC. The MSC waits in state Wait_For_Clear. The further processing is specified in

process ICH_MSC of GSM 03.18 [3].


8.3 Handling of mobile calls in gsmSSF

8.3.1 State Idle

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

8.3.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 waitsin Wait_For_Request.

8.3.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 whenprevious relationship with the gsmSCF has been terminated.

8.3.1.3 I nt_O/T_Exception

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

8.3.2 State Wait_For_Request

8.3.2.1 Int_DP_Collected_Info

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

8.3.2.2 DP_Terminating_Attempt_Authorised

See subclause 8.3.2.1.


The process gsmSSF returns directly to idle.

8.3.3 Waiting_For_Instructions

8.3.3.1 CAP_Request_Report_BCSM_Event

The gsmSSF arms the requested EDP, if the arming rules are fulfilled and returns to stateWaiting_For_I nstructions.

The gsmSCF may request monitor for answer or/and disconnect of a party in the call. O!T_Answer mayonly be armed as EDP-N. O/T_Disconnect may be armed as an EDP-N or an EDP-R.

8.3.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 andgsmSSF waits in state Monitoring., if DP Answer or DP Disconnect is armed as EDP-N the relationship ischanged to a monitor relationship and gsmSSF waits in state Monitoring.

If no remaining EDPs are armed, the control relationship between gsmSSF and the gsmSCF isterminated. The process gsmSSF returns to idle.

8.3.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 callsetup with modified information.



If DP Disconnect is armed as an EDP-R the relationship with gsmSCF remains a control relationship andgsmSSF waits in state Monitoring., if DP Answer or DP Disconnect is armed as EDP-N the relationship ischanged to a monitor relationship and gsmSSF waits in state Monitoring.

If no remaining EDPs are armed, the control relationship between gsmSSF and the gsmSCF isterminated. 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 stateWaiting_For_I nstruction s.

8.3.3.4 CAP_Release_Call

If CAP_Release Call is received in the state Wait_For_Instructions, an Int_Release_Call is sent to theGMSC/MSC to release the call.

8.3.3.5 Timer expire

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


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.3.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 sentto the gsmSCF and gsmSSF returns to state Waiting_For_Instructions.

8.3.4 Monitoring

8.3.4.1 Int DP O/T-Answer

If Int DP O/T Answer is received, then the gsmSSF if the EDP-N is armed sendsCAP_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.3.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 tothe GMSC/MSC.

If Int DP O/T_Disconnect is received and this DP is armed as EDP-N for the leg indicated inInt DP Disconnect, then the CAP Event_Report_BCSM (notify and continue) is sent to the gsmSCF andan 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.

If Int DP O!T Disconnect is received and this DP is armed as EDP-R for the leg indicated inInt DP Disconnect, then the CAP Event Report_BCSM (interrupted) is sent to the gsmSCF and thegsmSSF waits in state Waiting_For_Instructions.

8.3.4.3 CAP_Release_Call

When a control relationship exists between the gsmSCF and gsmSSF (at least one EDP-R is armed), thegsmSCF 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 thegsmSSF and the gsmSCF.

8.3.4.4 I nt_O/T_Exce pti o n

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.4 Any Time Interrogation

If an OSS needs the Subscriber State and/or the Location Information, the gsmSCF initiates a transaction

to the HLR by sending a Any_Time_Interrogation Request. Support for this procedure is a network

operator option.

8.4.1 Handling of Any Time Interrogation Request in HLR, Process CAMEL_ATI_HLR

8.4.1.1 Reception of Any_Time_Interrogation Request

The HLR may at any time receive a Any Time Interrogation Request from the gsmSCF.

8.4.1.1.1 MS known

If the mobile subscriber is known in the HLR the Provide_Subscriber_Info procedure is called with the

requested information and an Any_Time_Interrogation Response with the requested information is sent to

the gsmSCF. The process CAMEL_ATI_HLR returns to idle.

8.4.1.1.2 MS not known

If the mobile subscriber is not known in the HLR, an Any_Time_interrogation Negative Response is sent

to the gsmSCF. The process CAMEL_ATI_HLR returns to idle.



8.5 CAMEL specific handling at subscriber data management in HLR

If the VLR does not support CAMEL phase 1 the HLR may apply ODB, allow the call to continue withoutCAMEL or take network specific actions. The handling is subscriber specific.

8.6 Processing of Non-Call Related Events

CAMEL does not modify any of the standardized procedures for non-call related events including:- call independent supplementary service procedures;- transfer of SMS messages;- mobility management procedures.


9 Description of information flows

This clause contains the detailed description of the information flows used by CAMEL.

Each Information Element, IE is marked as Mandatory, Conditional, Optional or Not applicable for eachdifferent traffic case, Mobile Originating call (MO), Mobile Forwarded call (MF) and Mobile Terminating call

(MT). This categorisation is a functional classification, i.e., stage 2 information and not a stage 3classifications to be used for the ASN.1 syntax of the protocol.

9.1 gsmSSF to gsmSCF information flows

9.1.1 Activity Test Response

9.1.1.1 Description

This IF is the response to the Activity Test.

9.1.1.2 Information Elements

This IF contains no information elements.

9.1.2 Event Report BCSM

9.1.2.1 Description

This IF is used to notify the gsmSCF of acall-related event (i.e., BCSM events as answer and disconnect)previously requested by the gsmSCF in a Request Report BCSM Event IF.


The following information elements are required:

Information element name MO MF MT Description

Event type BCSM M M M This IE specifies the type of event that is reported i.e.,O-Answer, T-Answer, O-Disconnect or T-Disconnect.

Event specific information C C C This IE indicates the call related information specific toBCSM the event. It will contain the "release Cause" for O- or

T-Disconnect, if available. For O- and T-Answer it is notrequired.

Leg ID M M M This IE indicates the party in the call for which the eventis reported.

Misc Call Info M M M This IE indicates the DP type, i.e., Request orNotification.

M Mandatory (The IE shall always be sent)C Conditional (The IE shall be sent, if available)- Not applicable

9.1.3 Initial DP

9.1.3.1 Description

This IF is generated by the gsmSSF when a trigger is detected at a DP in the BCSM, to requestinstructions from the gsmSCF.



Additional Calling Party - C C The calling party number provided by the access signallingNumber system of the calling user.

Basic Service Code C C C This IE indicates the type of basic service i.e., teleservice orbearer service.

Bearer Capability M C C This IE indicates the type of the bearer capability connectionto the user.

Called Party Number M M M This IE contains the number used to identify the called partyin the forward direction.

Calling Party Number M C C This IE carries the calling party number to identify the callingparty or the origin of the call.

Calling Partys Category M C C Indicates the type of calling party (e.g., operator, pay phone,ordinary subscriber).

Call Reference Number M M M This IE may be used by the gsmSCF for inclusion in anetwork optional gsmSCF call record.For MO calls, the call reference number is set by the MSCand included in the MO call record.For MT calls, the call reference number is set by the GMSCand included on the RCF call record in the GMSC and on theMT call record in the terminating MSC.For CF calls, the call reference number is set by the GMSCand included on the CF record in the GMSC or the MSC.

Event TypeBCSM M M M This IE indicates the armed BCSM DP event (i.e.,Collected Info and Term._Attempt_Authorised), resulting inthe Initial DP IF.

high Layer Compatibility C C C This IE indicates the type of the high layer compatibility,which will be used to determine the ISDN-teleservice of aconnected ISDN terminal.

IMSI M M M This IE identifies the mobile subscriber.

Location Information M - C See GSM 03.18 [3].

Location Number M C C For mobile originated calls this IE representing the location ofthe calling party. For all other call scenarios this IE containsthe location number received in incoming ISUP signalling.

Original Called Party ID - C C This IE carries the dialled digits if the call has met callforwarding on the route to the gsmSSF.

Redirecting Party ID - M C This IE indicates the directory number the call was redirectedfrom.

Redirection Information - M C It contains forwarding related information, such as redirectioncounter.

Service Key M M M This IE identifies for the gsmSCF unambiguously therequested CAMEL service. It is used to address the correctapplication/SLP within the gsmSCF.

Subscriber State _ _ ~ This IE indicates the status of the MS. The states are:- CAMELBusy: The MS is engaged on a transaction for a

mobile originating or terminated circuit-switched call.- NetworkDeterminedNotReachable: The network can

determine from its internal data that the MS is notreachable.

- Assumedldle: The state of the MS is neither "CAMELBusy"nor "NetworkDeterminedNotReachable".

Location Information contains the following information:



Location Number

CeIIIdOrLAI M -

Geographicallnformation C -

Age Of Location Information M - C

VLR number M -

M Mandatory (The IE shall always be sent)C Conditional (The IE shall be sent, if available)- Not applicable

9.2 gsmSCF to gsmSSF information flows

9.2.1 Activity Test


C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

See GSM 03.18 [3].

C See GSM 03.18 (3].

9.2.1.1 Description

This IF is used to check for the continued existence of a relationship between the gsmSCF and gsmSSF.

If the relationship is still in existence, then the gsmSSF will respond. If no reply is received, then the

gsmSCF will assume that the gsmSSF has failed in some way and will take the appropriate action.


This IF contains no information elements.

9.2.2 Connect

9.2.2.1 Description

This IF is used to request the gsmSSF to perform the call processing actions to route a call to a specific

destination. To do so, the gsmSSF may use destination information from the calling party and existing call

set-up information depending on the information provided by the gsmSCF.




Calling Partys Category O O O This IE indicates the type of calling party (e.g.,

Calling Party Number O O O

Destination Routing Address O O O

Original Called Party ID O O O

Redirecting Party ID

Redirection Information

SuppressionAnnouncements

• • •

• • •

Of - - O

Generic Number O O O

operator, pay phone, ordinary subscriber).

This IE contains the calling party number.

This IE contains the called party number towardswhich the call is to be routed.

This IE carries the dialled digits if the call has metcall forwarding on route to the gsmSSF or isforwarded by the gsmSCF.

This IE indicates the directory number the call wasredirected from.

This IE contains forwarding related information, suchas redirecting counter.

This IE indicates that announcements or tonesgenerated as a result of unsuccessful call setup shallbe suppressed.

This IE contains the generic number. Its used to


convey the additional calling party number, whiche.g. could be used to modify the calling line IDpresented to the called user.

O-CSI Applicable - - O - This IE indicates that the O-CSI, if present should beapplied on the outgoing leg.

M Mandatory (The IE shall always be sent)O Optional (Service logic dependent)- Not applicable

9.2.3 Continue

9.2.3.1 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. The gsmSSF completes DP

processing, and continues basic call processing (i.e., proceeds to the next point in call in the BCSM)

without substituting new data from the gsmSCF.


This IF contains no information elements

9.2.4 Release Call

9.2.4.1 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.




Cause M M M A number giving an indication to the gsmSSF about thereason of releasing this specific call. This may be used bygsmSSF for generating specific tones to the differentparties in the call or to fill in the "cause" in the releasemessage.

M Mandatory (The IE shall always be sent)

9.2.5 Request Report BCSM Event

9.2.5.1 Description

This IF is used to request the gsmSSF to monitor for acall-related event (i.e., O_Answer, T_Answer,

O Disconnect or T Disconnect), then send a notification back to the gsmSCF when the event is detected

(see Event Report BCSM).


The following information elements are used:


BCSM Event M M M This IE specifies the event or events of which a report isrequested.



BCSM Event contains the following information:


Event type M M M This IE specifies the type of event of which a report isrequested (i.e., O_Answer, T_Answer, O_Disconnect orT_Disconnect).

Leg ID C C C This parameter indicates the party in the call for which theevent shall be reported. If not included, default is the partycreated with Connect IF for the events O Answer andT_Answer. The Leg ID IE shall always be included for theevents O-Disconnect and T-Disconnect.

Monitor Mode M M M This IE indicates how the event should be reported i.e., asrequest or notification.

M Mandatory (The IE shall always be sent)C Conditional

9.3 gsmSCF to HLR information flows

9.3.1 Any Time Interrogation Request

9.3.1.1 Description

This IF is used to request information (subscriber state and location) from the HLR at any time.



Information element name Required Description

Requested Info M This IE indicates the type of subscriber information beingrequested:- subscriber location- subscriber state

Subscriber Identity M This IE identifies the subscriber for which the information isrequested. The identity can be one of:- IMSI- MSISDN


9.4 HLR to gsmSCF information flows

9.4.1 Any Time Interrogation Response

9.4.1.1 Description

This IF is used by the HLR to provide the requested information to the gsmSCF.




Information element name Re uire Description

Location Information C This IE indicates the location of the served subscriber.

Subscriber State C This IE indicates the status of the MS. The states are:- CAMELBusy: The MS is engaged on a transaction for a


determine from its internal data that the MS is not reachable.- Assumedldle: The state of the MS is neither "CAMELBusy"

nor "NetworkDeterminedNotReachable".

C Conditional (The IE shall be sent, if requested and available)


Information element name

Location Number

CeIIIdOrLAI

Geographical Information

Age Of Location Information

VLR number

Re ire Description

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C Conditional (The IE shall be sent, if available)

9.5 HLR to VLR information flows

9.5.1 Delete Subscriber Data

9.5.1.1 Description

This IF is specified in GSM 09.02 (4] and is used by the HLR to delete subscriber data in the VLR.


The Delete Subscriber Data contains the following CAMEL specific IE:


CAMEL Subscription Info C This IE identifies that all CSIs shall be deleted from the

Withdraw subscriber data in VLR.

C Conditional (The IE shall be sent when deletion is requested)

9.5.2 Insert Subscriber Data

9.5.2.1 Description

This IF is specified in GSM 09.02 [4] and used by the HLR to insert subscriber data in the VLR.




Insert Subscriber Data contains the following CAMEL specific IE:


O-CSI C This IE identifies the subscriber as having originating CAMELservices. It contains the gsmSCFAddress, ServiceKey,DefaultCallHandling and TdpList.

C Conditional (The IE shall be sent, if required)

9.5.3 Insert Subscriber Data Response

9.5.3.1 Description

This IF is specified in GSM 09.02 [4] and used by the VLR to indicate to the HLR the result of the InsertSubscriber Data IF.


Insert Subscriber Data Response contains the following CAMEL specific IE:


Supported CAMEL Phases C This IE identifies which CAMEL phases are supported by theMSC/VLR. Only CAMEL phase 1 is used..

C Conditional (The IE shall always be sent when a CSI has been included in the ISD)

9.5.4 Provide Subscriber Info Request

9.5.4.1 Description

This IF is used to request information (subscriber state and location) from the VLR at any time.


Provide Subscriber Info contains the following CAMEL specific IE:


Requested Info M This IE indicates the type of subscriber information to thegsmSCF.- subscriber location- subscriber state

Subscriber Identity M This IE identifies the subscriber for which the information isrequested. The identity can be:- IMSI: The IMSI shall be accompanied by a LMSI if one wasprovided by the VLR.


9.5.5 Provide Roaming Number

9.5.5.1 Description

This IF is specified in GSM 03.18 [3] and used by the HLR to request the VLR for a roaming number.



Provide Roaming Number contains the following CAMEL specific IE:


Suppression Of Announcements C This IE indicates that announcements or tonesgenerated as a result of unsuccessful call setup shallbe suppressed.

Call Reference Number C This IE is used for correlation of call records outputtedfrom the GMSC and the terminating MSC, and anetwork optional call record from the gsmSCF.

C Conditional (The IE shall be sent, if received from the GMSC in the Send Routeing Info)

9.6 VLR to HLR information flows

9.6.1 Provide Subscriber Info Response

9.6.1.1 Description

This IF is used by the VLR to provide the requested information to the HLR.


Provide Subscriber Info Response contains the following CAMEL specific IE:


Location Information C This IE indicates the location of the served subscriber.

Subscriber State C This IE indicates the status of the MS. The states are:- CAMELBusy: The MS is engaged on a transaction for a


determine from its internal data that the MS is notreachable.

- Assumedldle: The state of the MS is neither "CAMELBusy"nor "NetworkDeterminedNotReachable".

C Conditional (The IE shall be sent, if requested and available)



Location Number

CeIIIdOrLAI



VLR number

Required Description

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

- See GSM 03.18 [3].

C Conditional (The IE shall be sent, if available)- Not applicable



9.7 HLR to GMSC information flows

9.7.1 Send Routeing Info Ack

9.7.1.1 Description

This IF is specified in GSM 03.18 [3] and used by the HLR to transfer previously requested information.


Send Routeing Info Ack contains the following CAMEL specific IE:


Location Information C2 This IE indicates the location of the served subscriber.

O-CSI C This IE identifies the subscriber as having originating CAMELservices. It contains the gsmSCFAddress, ServiceKey,DefaultCallHandling and TdpList.Shall be sent if O-CSI is active, and CFU or CRNRc has beeninvoked, or if both O-CSI and T-CSI are active.

Subscriber State C2 This IE indicates the status of the MS. The states are:- CAMELBusy: The MS is engaged on a transaction for a


determine from its internal data that the MS is not reachable.- Assumedldle: The state of the MS is neither "CAMELBusy"

nor "NetworkDeterminedNotReachable".

T-CSI C This IE identifies the subscriber as having terminating CAMELservices. It contains the gsmSCFAddress, ServiceKeyDefaultCallHandling and TdpList.Shall be sent if T-CSI is active and no Suppress T-CSI indicatoris present in the SRI.

Basic Service Code C This IE indicates the type of basic service i.e., teleservice orbearer service.

CUG Subscription Flag C This IE indicates if the called party has a CUG subscription. Itshall only be sent if the T-CSI is active and included in the SendRouting Information Ack.



Location Number

CeIIIdOrLAI



VLR number

Required Description

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C See GSM 03.18 [3].

C Conditional (The IE shall be sent, if available)C2 Conditional (The IE shall be sent, if available and indicated by Subscriber Information in Send

Routeing Information Ack indicator.)


9.8 GMSC to HLR information flows

9.8.1 Send Routeing Info

9.8.1.1 Description

This IF is described in GSM 03.18 [3] and used to request the HLR for information.


Send Routeing Info contains the following CAMEL specific IE:


Suppression Of Announcement C This IE indicates that announcements or tones generatedas a result of unsuccessful call setup shall be suppressed.Shall be sent in the second interrogation if available, i.e.,when it has been received from the gsmSCF.

Suppress T-CSI C This IE indicates ifT-CSI shall be suppressed.Shall always be sent in the second interrogation

Supported CAMEL Phases M This IE lists the supported CAMEL phases.

Call Reference Number C This IE is used for correlation of call records outputted fromthe GMSC and the terminating MSC, and a networkoptional call record from the gsmSCF.

C Conditional (The IE shall be sent, if received from the gsmSCF or set by the gsmSSF)M Conditional (The IE shall always be sent when the GMSC supports CAMEL)



History

Document history

~ April 1997 ~ SMG version 5.0.0 Approved at SMG#21


~sm~ - ptabdata.blob.core.windows.net · whilst every care has been taken in the preparation and...

Documents