Content for TS 23.078 Word version: 18.0.0

1… 4.2… 4.3… 4.4… 4.5… 4.5.5… 4.6… 4.6.2 4.6.3… 4.6.7… 4.6.13… 5… 6… 6.5… 6.6… 7… 7.5… 8… 9… 10… 11…

1.1 Support of partial implementation of CAMEL phase 4 3.1 Definitions 3.2 Abbreviations 4.1 Architecture 4.1.1 Functional Entities used for CAMEL 4.1.2 Interfaces defined for CAMEL
...

1 Scope p. 20

The present document specifies the stage 2 description for the fourth phase (see TS 22.078) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services of operators which are not covered by standardized services even when roaming outside the HPLMN.

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

In the present document, 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 the HPLMN are controlled by different operators, and the gsmSCF and the HPLMN are therefore distinct entities.

The fourth phase of the CAMEL feature supports, in addition to the third phase of the CAMEL:

Interactions with Optimal Routing;
Call Party Handling;
DTMF Mid call procedure for Mobile Originated and Mobile Terminating calls;
Inclusion of flexible tone injection;
Provision of location information of called subscriber;
Provide location information during ongoing call;
CAMEL control over MT SMS;
Notification of GPRS mobility management to CSE;
Inclusion of ODB data in Any Time Modification;
Enhancement of Any Time Interrogation and Provide Subscriber Information for PS Domain;
Mobile Number Portability database interrogation;
Criteria for the provision of location information during ongoing call;
Enhanced Dialled Services;
Enhancement to Establish Temporary Connection;
CAMEL control of trunk originated calls.

CAMEL applicability to IP-based multimedia services is introduced in the fourth phase of the CAMEL. It is specified in TS 23.278.

CAMEL is not applicable to Emergency Setup (TS 12), i.e. if an Emergency call is requested, then the gsmSSF shall not be invoked.

The mechanism described in the present document addresses especially the need for information exchange between the VPLMN or IPLMN and the HPLMN for support of operator specific services. Any user procedures for the control of operator specific services are outside the scope of the present document. Subscribers who have subscribed to operator specific services and therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. In case a subscriber is marked to need CAMEL support, the appropriate procedures which provide the necessary information to the VPLMN or the HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with a gsmSCF which is controlled by the HPLMN.

The specification of operator specific services is outside the scope of the present document.

1.1 Support of partial implementation of CAMEL phase 4 |R5| p. 21

A functional entity (VMSC, GMSC or SGSN) may support the complete CAMEL phase 4 functionality or, as a network option, it may support the complete CAMEL phase 3 functionality and a partial implementation of CAMEL phase 4.

If a functional entity supports any part of CAMEL phase 4, then the HLR is informed of the CAMEL phase 4 CSIs supported. An SGSN may also indicate support of the Provide Subscriber Information IF. To indicate support of a specific CSI, a functional entity shall have the ability to trigger on any initial service event possible for that CSI.

If a VMSC or GMSC supports any of the CAMEL phase 4 circuit switched CSIs (O-CSI, D-CSI, T-CSI or VT-CSI), then the gsmSCF is informed of the CAMEL phase 4 circuit switched functionalities offered. The gsmSCF shall not send information flows or parameters that conflict with the functionalities offered by the VMSC or GMSC.

If a CAMEL subscriber attempts to register in a VMSC or SGSN which supports at least one CAMEL phase 4 CSI or the enhancement of Provide Subscriber Information IF, then the VMSC or SGSN indicates in the registration request to the HLR the phase of CAMEL which the VMSC or SGSN supports (at least phase 4). In addition, the VMSC or SGSN indicates which CAMEL phase 4 CSIs may be downloaded. An SGSN may also indicate support of the Provide Subscriber Information IF.

If a GMSC supports at least one CAMEL phase 4 CSI, then the GMSC indicates in the Send Routeing Info to the HLR the phase of CAMEL which the GMSC supports (at least phase 4). In addition, the GMSC indicates which CAMEL phase 4 CSIs may be downloaded.

If a VMSC/gsmSSF or GMSC/gsmSSF initiates contact with the gsmSCF using the Initial DP IF, or acknowledges a gsmSCF initiated contact using the Initiate Call Attempt ack IF, then the VMSC/gsmSSF or GMSC/gsmSSF indicates in the IF the CAMEL phase 4 functionalities offered to the gsmSCF.

If a VLR initiates contact with the gsmSCF using a Mobility Management Event Notification IF, then the VLR or SGSN indicates in the IF the functionalities offered to the gsmSCF.

1.1.1 CAMEL Phase 4 CSIs p. 21

A network entity may indicate to the HLR an offer of support for the following CAMEL phase 4 CSIs:

CAMEL phase 4 O-CSI;
CAMEL phase 4 D-CSI;
CAMEL phase 4 T-CSI;
CAMEL phase 4 VT-CSI;
CAMEL phase 4 MT-SMS-CSI;
CAMEL phase 4 MG-CSI;
CAMEL control of trunk originated calls;
Reporting of additional dialled digits.

An SGSN may also indicate support of the CAMEL phase 4 Provide Subscriber Information IF.

A functional entity (VMSC, GMSC or SGSN) may offer the CSIs in any combination applicable for this entity. A functional entity shall indicate to the HLR all the CSIs it offers. The HLR may ignore the offer of the supported CSIs if they are not applicable for the sending entity, but it shall not reject the operation in this case.

1.1.2 CAMEL Phase 4 Functionalities p. 21

The CAMEL phase 4 functionalities which may be offered to the gsmSCF are the following:

Creating additional parties in a call, Creating a new call (Initiate Call Attempt);
Placing an individual call party on hold or moving an individual call party to Call Segment 1, when Call Segment 1 does not exist (Split Leg);
Connecting an individual call party to the group (Move Leg);
Releasing an individual call party (Disconnect Leg);
Indication of the release of a call party or call segment (Entity Released);
Enhancements for subscriber interactions with the gsmSCF (Disconnect Forward Connection With Argument);
Inclusion of flexible tone injection (Play Tone);
DTMF Mid call procedure for MO and VT calls (DP O_Mid_Call, DP T_Mid_Call);
Provision of Charge Indicator at answer DP (Charge Indicator at DP O_Answer, DP T_Answer);
Support of Alerting DP (DP O_Term_Seized, DP Call_Accepted);
Provision of location information of subscriber at alerting DP (Location information at DP O_Term_Seized, DP Call_Accepted);
Provision of location information during an ongoing call (DP O_Change_Of_Position, DP T_Change_Of_Position);
Interactions with Basic Optimal Routeing (Basic OR Interrogation Requested in Connect and Continue With Argument, Route Not Permitted in DP O_Abandon);
Warning tone enhancements (Burstlist for Audible Indicator);
Enhancements of Call Forwarding indication (Forwarding Destination Number);
Criteria for the provision of location information during ongoing call (Criteria for DP O_Change_Of_Position and DP T_Change_Of_Position);
Subscribed Enhanced Dialled services (see description below);
Serving Network Enhanced Dialled Services (see description below);
SCUDIF notification during active phase of the call (DP O_Service_Change and T_Service_Change) ; and
Collection of additional dialled digits (Arming CollectedInfo DP as EDP-R).

For the Subscribed Enhanced Dialled Services and Serving Network Enhanced Dialled Services, the following information flows apply in addition to the information flows allowed at TDP Analysed_Information since CAMEL phase 3: Apply Charging, Call Information Request, Cancel (all requests) and Request Report BCSM Event together with their acknowledgements and reportings. In addition, all the other offered CAMEL phase 4 functionalities apply also to the enhanced dialled services.

A functional entity (VMSC or GMSC) may offer the functionalities in any combination applicable for this entity and applicable to the offered CSIs.

A functional entity (VMSC or GMSC) shall indicate to the gsmSCF all the functionallities it offers.

2 References p. 23

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications".

[2]

TS 22.004: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General on supplementary ".

[3]

TS 22.024: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Description of Charge Advice Information (CAI)".

[4]

TS 22.041: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Operator Determined Barring (ODB)".

[5]

TS 22.071: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Location Services (LCS); Service description, Stage 1".

[6]

TS 22.078: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1".

[7]

TS 23.003: "3rd Generation Partnership Project; Technical Specification Group Core Network; Numbering, addressing and identification".

[8]

TS 23.008: "3rd Generation Partnership Project; Technical Specification Group Core Network; Organization of subscriber data".

[9]

TS 23.011: "3rd Generation Partnership Project; Technical Specification Group Core Network; Technical realization of Supplementary Services".

[10]

TS 23.012: "3rd Generation Partnership Project; Technical Specification Group Core Network; Location management procedures".

[11]

TS 23.015: "3rd Generation Partnership Project; Technical Specification Group Core Network; Technical realization of Operator Determined Barring (ODB)".

[12]

TS 23.018: "3rd Generation Partnership Project; Technical Specification Group Core Network; Basic call handling; Technical realization".

[13]

TS 23.032: "3rd Generation Partnership Project; Technical Specification Group Core Network; Universal Geographical Area Description (GAD)".

[14]

TS 23.040: "3rd Generation Partnership Project; Technical Specification Group Terminals; Technical realization of the Short Message Service (SMS)".

[15]

TS 23.060: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2".

[16]

TS 23.072: "3rd Generation Partnership Project; Technical Specification Group Core Network; Call Deflection (CD) Supplementary Service; Stage 2".

[17]

TS 23.066: "3rd Generation Partnership Project; Technical Specification Group Core Network; Support of Mobile Number Portability (MNP); Technical realization; Stage 2".

[18]

TS 43.073: "3rd Generation Partnership Project; Technical Specification Group Core Network; Support of Localised Service Area (SoLSA); Stage 2".

[19]

TS 23.079: "3rd Generation Partnership Project; Technical Specification Group Core Network; Support of Optimal Routeing (SOR); Technical realization".

[20]

TS 23.082: "3rd Generation Partnership Project; Technical Specification Group Core Network; Call Forwarding (CF) supplementary services; Stage 2".

[21]

TS 23.084: "3rd Generation Partnership Project; Technical Specification Group Core Network; Multi Party (MPTY) supplementary service; Stage 2".

[22]

TS 23.085: "3rd Generation Partnership Project; Technical Specification Group Core Network; Closed User Group (CUG) supplementary service; Stage 2".

[23]

TS 23.088: "3rd Generation Partnership Project; Technical Specification Group Core Network; Call Barring (CB) Supplementary Services; Stage 2".

[24]

TS 23.090: "3rd Generation Partnership Project; Technical Specification Group Core Network; Unstructured Supplementary Service Data (USSD); Stage 2".

[25]

TS 23.091: "3rd Generation Partnership Project; Technical Specification Group Core Network; Explicit Call Transfer (ECT) supplementary service; Stage 2".

[26]

TS 23.093: "3rd Generation Partnership Project; Technical Specification Group Core Network; Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2".

[27]

TS 23.172: "3rd Generation Partnership Project; Technical Specification Group Core Network; Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2".

[28]

TS 23.271: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional stage 2 description of LCS".

[29]

TS 23.278: "3rd Generation Partnership Project; Technical Specification Group Core Network; Customised Applications for Mobile network Enhanced Logic (CAMEL) - IP Multimedia System (IMS) interworking; Stage 2".

[30]

TS 24.008: "3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3".

[31]

TS 24.011: "3rd Generation Partnership Project; Technical Specification Group Core Network; Point - to - Point (PP) Short Message Service (SMS); support on mobile radio interface".

[32]

TS 25.305: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Stage 2 Functional Specification of UE Positioning in UTRAN".

[33]

TS 25.413: "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; UTRAN Iu interface RANAP signalling".

[34]

TS 29.002: "3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification".

[35]

TS 29.007: "3rd Generation Partnership Project; Technical Specification Group Core Network; General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".

[36]

TS 29.078: "3rd Generation Partnership Project; Technical Specification Group Core Network; Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4 CAMEL Application Part (CAP) specification".

[37]

TS 32.250: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication Management; Charging management; Circuit Switched (CS) domain charging".

[38]

TS 32.251: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication Management; Charging management; Packet Switched (PS) domain charging".

[39]

TS 48.008: "3rd Generation Partnership Project; Technical Specification Group GSM EDGE Radio Access Network; Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification".

[40]

ETSI EN 300 356-1 (V3.2.2): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services[ITU-T Recommendations Q.761 to Q.764 (1997), modified]".

[41]

ETSI EN 301 070-1 (V1.2.2): "Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP) version 3 interactions with the Intelligent Network Application Part (INAP); Part 1: Protocol specification [ITU-T Recommendation Q.1600 (1997), modified]".

[42]

GSM TR 03.47: "Example protocol stacks for interconnecting; Service Centre(s) (SC) and Mobile-services Switching Centre(s) (MSC)".

[43]

ITU-T Recommendation Q.763, December 1999: "Signalling System No. 7 - ISDN user part formats and codes".

[44]

ITU-T Recommendation Q.1224, September 1997: "Distributed Functional Plane for Intelligent Network Capability Set 2".

[45]

TS 23.087: "3rd Generation Partnership Project; Technical Specification Group Core Network; User-to-User Signalling (UUS) Supplementary Service - Stage 2".

[46]

TS 43.059: "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Functional stage 2 description of Location Services (LCS) in GERAN".

[47]

TS 23.081: "Line identification supplementary services; Stage 2".

[48]

TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2".

3 Definitions and abbreviations p. 26

3.1 Definitions p. 26

For the purposes of the present document, the following terms and definitions apply:

Basic Call State Model (BCSM):

BCSM provides a high-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 to process a basic call.

Call Control Function (CCF):

CCF is the Call Control Function in the network that provides call/service processing and control (see ITU-T Recommendation Q.1224 [44]).

Call Party Handling (CPH) Information Flow:

Any of the Disconnect Leg, Move Leg or Split Leg information flows.

Call Segment:

A call segment contains one or more legs that are controlled by the same CS_gsmSSF instance. The call parties in the same call segment can communicate with each other (using a conference bridge if necessary). Call segments are identified by a number, eg. CSID1 is the call segment with id number 1.

Call Segment Association (CSA):

A CSA contains one or more call segments. Legs can be moved between call segments within the CSA. There is a single CAP dialogue between the CSA and the gsmSCF.

Detection Points (DP):

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

Dialled Service CAMEL Subscription Information (D-CSI):

D-CSI identifies the subscriber as having originating CAMEL dialled services.

Forwarding MSC:

MSC which is either an MSC invoking a standardized Call Forwarding supplementary service or Call Deflection supplementary service; or an MSC invoking a CAMEL based call forwarding service.

Gateway MLC (GMLC):

functional entity that allows external LCS Clients to request real-time information about a Mobile Station. The information that can be requested from the GMLC is:

location of Mobile Station

See TS 23.271 and TS 25.305 or TS 43.059 for information on the GMLC.

Geodetic Information:

information defining the location of a mobile station, coded according to ITU-T Recommendation Q.763 [43]. The derivation of this information from other information defining the location of a mobile station is a network operator option. If an entity derives the geodetic information it shall also provide the equivalent geographical information.

Geographical Information:

information defining the location of a mobile station, coded according to TS 23.032.

GPRS CAMEL Subscription Information (GPRS-CSI):

GPRS-CSI identifies the subscriber as having GPRS CAMEL services.

GPRS Dialogue:

A dialogue between the gprsSSF and the gsmSCF. A single GPRS Dialogue may consist of one or more TCAP dialogues. Only one TCAP dialogue shall exists at one point in time for one gprsDialogue.

GPRS Service Switching Function (gprsSSF):

functional entity that interfaces the SGSN to the gsmSCF. The concept of the gprsSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network.

GPRS Session:

GPRS session starts when the GPRS subscriber attaches to the GPRS data network. It ends when the GPRS subscriber detaches from the GPRS data network.

GSM Service Control Function (gsmSCF):

functional entity that contains the CAMEL service logic to implement OSS. It interfaces with the gsmSSF, the gsmSRF, the GMLC and the HLR.

GSM Service Switching Function (gsmSSF):

functional entity that interfaces the MSC or GMSC to the gsmSCF. The concept of the gsmSSF is derived from the IN SSF, but uses different triggering mechanisms because of the nature of the mobile network.

GSM Specialised Resource Function (gsmSRF):

functional entity which provides various specialized resources. It interfaces with the gsmSCF and with the MSC. This entity is defined in ITU-T Recommendation Q.1224 [44] with variations defined in the present document.

Inter-connecting MSC:

MSC which provides CAMEL support for incoming trunk calls.

Location Information:

indicates the location of the Mobile Station. The provision of location information is independent of the MS status. As part of the location information, an indication of the age of this information may be delivered.

Mobile Originating Short Message Service CAMEL Subscription Information (MO-SMS-CSI):

MO-SMS-CSI identifies the subscriber as having MO SMS CAMEL services. MO-SMS-CSI (CAMEL Phase 4) is identical to SMS-CSI (CAMEL Phase 3).

Mobile Station State:

similar to Subscriber State, but associated only with a Mobile Station, not with a subscriber.

Mobile Terminating Short Message Service CAMEL Subscription Information (MT-SMS-CSI):

MT-SMS-CSI identifies the subscriber as having MT SMS CAMEL services.

Mobility Management event CAMEL Subscription Information (M-CSI):

M-CSI identifies the subscriber as having Mobility Management event notification CAMEL services.

Mobility Management event GPRS CAMEL Subscription Information (MG-CSI):

MG-CSI identifies the GPRS subscriber as having Mobility Management event notification CAMEL services.

NA (North American):

prefix attached to certain information items used by North American PLMNs in connection with routing a call to a preferred or dialled long distance carrier.

Network CAMEL Service Information (N-CSI):

N-CSI identifies services offered on a per-network basis by the serving PLMN operator for all subscribers.

Originating Basic Call State Model (O-BCSM):

originating half of the BCSM. The O-BCSM corresponds to that portion of the BCSM associated with the originating party.

Originating CAMEL Subscription Information (O-CSI):

O-CSI identifies the subscriber as having originating CAMEL services.

Point In Association (PIA):

PIAs identify MSC/VLR or SGSN activities associated with one or more basic association/connection states of interest to OSS service logic instances.

Point In Call (PIC):

PICs identify MSC/VLR (GMSC) activities associated with one or more basic call/connection states of interest to OSS service logic instances.

Service Key:

Service Key identifies to the gsmSCF the service logic. The Service Key is administered by the HPLMN, and is passed transparently by the VPLMN/IPLMN to the gsmSCF. The Service Key is a part of the T/O/VT/D/GPRS/SMS/M-CSI.

Serving MLC:

functional entity that performs location information retrieval.

Short Message Control Protocol (SM-CP):

Protocol between the MSC or SGSN and the MS. This protocol, which is specified in TS 24.011, is used to carry RPDU elements between the MSC or SGSN and the MS.

Short Message Service Centre (SMSC):

also abbreviation SC is used for SMSC.

Subscriber State:

see TS 22.078.

Supplementary Service Notification CAMEL Subscription Information (SS-CSI):

SS-CSI identifies the subscriber as having supplementary service invocation notification CAMEL services.

Terminating Basic Call State Model (T-BCSM):

terminating half of the BCSM. The T-BCSM corresponds to that portion of the BCSM associated with the terminating party.

Terminating CAMEL Subscription Information (in the GMSC) (T-CSI):

T-CSI identifies the subscriber as having terminating CAMEL services in the GMSC.

Translation Information Flag (TIF-CSI):

TIF-CSI is a flag in the CAMEL subscriber data which indicates that when the subscriber registers a forwarded-to number, that the HLR shall not attempt to perform any translation, number format checks, prohibited FTN checks, call barring checks.

Trunk Originated CAMEL Service Information (TO-CSI):

TO-CSI identifies services offered by the PLMN operator to all incoming calls on a specific MSC trunk.

USSD CAMEL Subscription Information (U-CSI):

U-CSI identifies a set of subscriber specific mappings from a USSD service code to a gsmSCF address.

USSD General CAMEL Service Information (UG-CSI):

UG-CSI globally identifies a set of mappings from a USSD service code to a gsmSCF address. The global mapping applies to all HPLMN subscribers. If, for a particular service code, both U-CSI and UG-CSI are applicable then the U-CSI shall take precedence.

VMSC Terminating CAMEL Subscription Information (VT-CSI):

VT-CSI identifies the subscriber as having terminating CAMEL services in the VMSC.

3.2 Abbreviations p. 28

Abbreviations used in the present document are listed in TR 21.905.

For the purposes of the present document, the following abbreviations apply:

BCSM

Basic Call State Model

CAMEL

Customized Applications for Mobile network Enhanced Logic

CPH

Call Party Handling

Call Segment

Circuit Switched

CSA

Call Segment Association

CSG

Closed Subscriber Group

CSID

Call Segment (followed by an identification Number e.g. CSID1)

Detection Point

DTN

Deflected To Number

D-CSI

Dialled Services CAMEL Subscription Information

EDP

Event Detection Point

EDS

Enhanced Dialled Services

FTN

Forwarded To Number

GMLC

Gateway MLC

GMSC

Gateway MSC

GPRS

General Packet Radio Service

gprsSSF

GPRS Service Switching Function

GPRS-CSI

GPRS CAMEL Subscription Information

gsmSCF

GSM Service Control Function

gsmSRF

GSM Specialised Resource Function

gsmSSF

GSM Service Switching Function

HLR

Home Location Register

HPLMN

Home PLMN

ICA

Initiate Call Attempt

Information Element

Information Flow

Intelligent Peripheral

IPLMN

Interrogating PLMN

LCS

Location Services

LSA

Localised Service Area

M-CSI

Mobility Management event Notification CAMEL Subscription Information

Mobile Forwarding

MG-CSI

Mobility Management event Notification GPRS CAMEL Subscription Information

MLC

Mobile Location Centre

MNP

Mobile Number Portability

MNP SRF

Mobile Number Portability Signalling Relay Function

Mobile Originating

MO-SMS-CSI

Mobile Originated Short Message Service CAMEL Subscription Information

MSC

Mobile service Switching Centre

Mobile Terminating

Mobile Terminating in GMSC

MT-SMS-CSI

Mobile Terminating Short Message Service CAMEL Subscription Information

N-CSI

Network CAMEL Service Information

North American

NNI

Network Node Interface

O-BCSM

Originating Basic Call State Model

O-CSI

Originating CAMEL Subscription Information

ODB

Operator Determined Barring

Optimal Routeing

OSS

Operator Specific Service

PDP

Packet Data Protocol

PIC

Point In Call

PLMN

Public Land Mobile Network

SGSN

Serving GPRS Support Node

SLPI

Service Logic Program Instance

Short Message

SM-CP

Short Message Control Protocol

SMF

Service Management Function

SMLC

Serving MLC

SMRSE

Short Message Relay Service Element

SMS

Short Message Service

SMSC

Short Message Service Centre

SMS-CSI

Short Message Service CAMEL Subscription Information

SS-CSI

Supplementary Service Notification CAMEL Subscription Information

T-BCSM

Terminating Basic Call State Model

T-CSI

Terminating CAMEL Subscription Information (in the GMSC)

TDP

Trigger Detection Point

TO-CSI

Trunk Originated CAMEL Service Information

TPDU

Transfer Protocol Data Unit

TIF-CSI

Translation Information Flag

U-CSI

USSD CAMEL Subscription Information

UG-CSI

USSD General CAMEL Service Information

UNI

User Network Interface

VLR

Visitor Location Register

VPLMN

Visited PLMN

Mobile Terminating in VMSC

VT-CSI

VMSC Terminating CAMEL Subscription Information

4 Circuit switched Call Control p. 30

4.1 Architecture p. 30

4.1.1 Functional Entities used for CAMEL p. 30

This subclause describes the functional architecture needed to support CAMEL. Also the additions needed to the basic functionality are described. Figure 4.1 shows the functional entities involved in calls requiring CAMEL support. The architecture is applicable to the forth phase of CAMEL.

Copy of original 3GPP image for 3GPP TS 23.078, Fig. 4.1: Functional architecture for support of CAMEL

Figure 4.1: Functional architecture for support of CAMEL
(⇒ copy of original 3GPP image)

HLR:

For subscribers requiring CAMEL support, the HLR stores the information relevant to the current subscription regarding O-CSI, D-CSI, T-CSI, VT-CSI and TIF-CSI. The O-CSI is sent to the VLR at Location Update, on data restoration or if the O-CSI is updated by administrative action. The D-CSI is sent to the VLR at Location Update, on data restoration or if the D-CSI is updated by administrative action. The VT-CSI is sent to the VLR at Location Update, on data restoration or if the VT-CSI is updated by administrative action. The TIF-CSI is sent to the VLR at Location Update, on data restoration or if the TIF-CSI is updated by administrative action. The O/D/T-CSI is sent to the GMSC when the HLR responds to a request for routeing information.

GMSC:

When processing the calls for subscribers requiring CAMEL support, the GMSC receives an O/D/T-CSI from the HLR, indicating the GMSC to request instructions 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 an O-CSI and / or D-CSI and / or VT-CSI from the VLR indicating the MSC to request instructions 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, D-CSI, VT-CSI and TIF-CSI as a part of the subscriber data for subscribers roaming in the VLR area.

gsmSSF:

see subclause 3.1.

gsmSCF:

see subclause 3.1.

gsmSRF:

see subclause 3.1.

4.1.2 Interfaces defined for CAMEL p. 31

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

4.1.2.1 HLR - VLR interface p. 31

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.1.2.2 GMSC - HLR interface p. 31

This interface is used at terminating calls to exchange routeing information, subscriber status, location information, subscription information and suppression of announcements. The CAMEL related subscriber data that is passed to the IPLMN is sent over this interface.

4.1.2.3 GMSC - gsmSSF interface p. 31

This is an internal interface. The interface is described in the present document to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

4.1.2.4 gsmSSF - gsmSCF interface p. 31

This interface is used by the gsmSCF to control a call in a certain gsmSSF and to request the gsmSSF to establish a connection with a gsmSRF. Relationships on this interface are opened as a result of the gsmSSF sending a request for instructions to the gsmSCF or opened as a result of the gsmSCF sending a request to the gsmSSF to initiate a new call.

4.1.2.5 MSC - gsmSSF interface p. 31

This is an internal interface. The interface is described in the present document to make it easier to understand the handling of DPs (arming/disarming of DPs, DP processing etc.).

4.1.2.6 gsmSCF - HLR interface p. 31

This interface is used by the gsmSCF to request information from the HLR. As a network operator option the HLR may refuse to provide the information requested by the gsmSCF.

4.1.2.7 gsmSCF - gsmSRF interface p. 31

This interface is used by the gsmSCF to instruct the gsmSRF to play tones/announcements to the users.

4.1.2.8 GMSC - MSC interface p. 31

This interface is used to transfer control of a call from a VMSC back to a GMSC for optimal routeing.