camel

1

Study Themes - Overview

• Lecture Block 1 - August 22 - 23, 2005– Study Theme 1: Introduction - NGN Services, Service Delivery Platforms

and Standards

– Study Theme 2: Intelligent Networks (IN) - Basics and Standards

– Study Theme 3: Intelligent Networks (IN) in Wireless – 3GPP CAMEL

– Study Theme 4: Open Network APIs (CORBA, Java) – OSA / Parlay / JAIN

– Study Theme 5: Open Network APIs (Web Services) – Parlay X / OMA Web Services

• Lecture Block 2 - October 3 - 4, 2005– Study Theme 6: NGN Protocols – SIP, DIAMETER

– Study Theme 7: IMS Basics and Standards overview

– Study Theme 8: IMS Architecture and Operation in Detail

– Study Theme 9: IMS Application Server Options and Applications

– Study Theme 10: Summary and Outlook

2

StudyStudy ThemeTheme 33

CAMELCAMEL

• Mobile value added service: Prepaid, VPN, VHE

• CAMEL architecture and service provisioning

• 3GPP Standardisation approach - Phases

• Phase 1 - Starters CAMEL - Prepaid roaming: Services, architecture, protocols

• Phase 2 - Real CAMEL/VPN, Services, architecture, protocols

• Phase 3 - CAMEL for GPRS/SMS: Services, architecture, protocols

• Phase 4 - CAMEL for Multiparty services: Services, architecture, protocols

• CAMEL Deployment status and Interoperability issues

3

Motivation for CAMEL

• GSM is a big success

• based on strict standards ensuring interoperability but providing limiteddegree of service differentiation

• Value added services are key for new revenuesà Mobile Prepaid

• Service Nodes enhance service portfolio but are limited to own network (no roaming support or specific solutions!!!)

• Idea:

Extend IN concept to mobile domain, but keep it focusedà CAMEL

• Main challenges: – IN in fixed networks did never support service interoperability but in mobile

networks we are confronted with roaming users

– In mobile networks we have strong heterogeneity of service platforms

4

Business Drivers for CAMEL

Service, Services, Services

• The 1st ( and still main) reason for implementing Camel is international roaming :

• GSM PrePaid– USSD- Call Back is a nightmare for end-users– Temporary PostPaid subscription is a nightmare for operators (and refused by

end users)

• VPN : ‘virtual company’ doesn’t stop at the border• VHE : everywhere like at home.

– How to call my customer care ?– How to get my voice mails ? – How to recharge my PrePaid account ?

è Camel increases roaming revenues

5

• Different vendors

(IN,SSS)

• Different INAP versions

• No Roaming for Prepaid

subscribers

• Other IN Services are not

available abroad

• Roaming for normal GSM

subscribers possible

Prepaid Roaming – A Killer Application

IN Subscriber

VPLMN HPLMN

ISUP ISUP

MSC MSC

ISUP

INAP*

SN

MSC MSC

Roaming not possible for PPS

Subscriber

Situation today with Service Node: NO Prepaid Roaming or very specific quick hack

6

Prepaid forecast: still growing !!

7

Evolution towards roaming Prepaid Support

• Before CAMEL: USSD-based Call Back

• CAMEL Phase 1:

– Simplified Call Handling

– Home-network SCP based rerouting

• CAMEL Phase 2:

– The real thing!

8

Pre-CAMEL: USSD-based Call Back

RoamingSubscriber =

Calling Party

VPLMN HPLMN

ISUP

MSC

ISUP

INAP

SN

SSP SSP

HLR

Called Party

System works like wake-up call – SCP/SN initiates call (on request)

⌦ Dial number (USSD String)

plus hang -up again

⌦ IN-System calls back

⌦ A-Party picks up

⌦ B-Party picks up

USSD1

2

4

3

9

Aspects concerning pre-CAMEL roaming

PROs:- Prepaid cards can be used abroad- Support of all common handsets with USSD capability- Existing infrastructure can be upgraded easily- Elimination of fraud due to online charging- Roaming agreements for postpaid subscribers could be used

CONs:- No online charging for SMS- Additional speech trunks and longer call setup times- Service is not the same for the user

10

3GPP CAMEL

• CAMEL = Customized Applications for Mobile Enhanced Logic

• CAMEL– Is the use of IN in mobile circuit switched and packet switched networks:

GSM/GPRS

– IN-based architecture enabling to offer operator specific services (OSS) to mobile subscribers even when roaming in another network (international roaming)

• CAMEL enables inter-network GSM/GPRS service control, by reusingthe existing international signaling transport infrastructure– CAMEL Application Protocol (CAP) is based on IN Capability Sets 1 and 2

– CAMEL additionally exploits Mobile Application Part (MAP)

• CAMEL Standardisation started in 1994 (as a GSM Phase 2+ Feature)

• CAMEL evolves in Phases, which are part of Releases!!!

11

Basic GSM / GPRS architecture

Home NetworkVisited Network

InterrogatingNetwork

CS

VMSC

HLR

VLRGMSC

MAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

SGSN GGSN PDNGPRS

12

CAMEL Phase 1 architecture



CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

13

• Standardized Interfaces CAMEL Application Part (CAP)

• IN services are availableinternationally

• Own IN Subscribers areable to roam

• Foreign IN Subscribersmay be supported, too

• IN user database may beused for new / advancedservices, e.g. m-payment

Prepaid Roaming with CAMEL

RoamingIN Subscriber

VPLMN HPLMN

ISUP ISUP

SSP SSP

ISUP

INAP,CAP

SCP

SSP SSP

CAP

Roaming possible for PPS

Subscriber

14

CAMEL Phases

• Camel Phase 1– Basic Call Control functionalities for GSM calls

• Camel Phase 2– ApplyCharging in VPLMN : GSM calls are monitored directly in VPLMN– Announcement : access to annoucements directly from the VPLMN

• Camel Phase 3– Handling of GPRS Sessions and pdp-contexts for session control, monitoring

(location update, QoS,…) and charging (time and volume triggers)– Support of SMS-MO through CS and PS networks– Anytime interrogation and modification of customer data in HLR– Mobility management enhancements

• Camel Phase 4– Multi-leg GSM call handling– Creation of a new GSM call– PLUS: Interworking with IP Multimedia Subsystem

15

SSPMSCVLRHome

PLMNVisitedPLMN

CSE(SCP)

Roamingsubscriber

SSPMSCHLR

SSPGMSC 1

2

3

4

CAP Dialogue

- Subscriber dials number- Send Initial Detection Point (IDP) - Route to Home PLMN- Receive Connect - Connect to B-party via Gateway MSC

1

52

4

63

7

6

5INAP Dialogue

CAMEL Phase 1: Re-routing via Home network

7

Called user

But: 80-90% of all calls are directed to the home network!

7

Problem: network tromboning!

Limited CAP operations:- i.e. no charging operations

16

PROs:

- Support of all common handsets

- Existing infrastructure can be upgraded easily (parallel protocols supportedmany vendor solutions)

- Elimination of fraud due to online charging

- Roaming agreements for postpaid subscribers could be used

- First step towards standard implementation

- Enabling of inbound roaming with CAP1

- Service looks / feels the same as for postpaid users

CONs:

- No online charging for SMS

- Additional speech trunks needed

Aspects concerning CAMEL Phase 1 roaming

17

HomePLMN

CAMEL Phase 2: Full Roaming

SSPMSCVLR Visited

PLMN

CSE(SCP)

roamingsubscriber

SSPMSCHLR

SSPGMSC 1

2

3

4

- Subscriber dials number- Send Initial Detection Point (IDP)- Receive Connect - Connect to B-party directly

1234

CAP Dialogue

IP

Enhanced CAP operations:- full charging operations- control of announcements

18

PROs:

- Support of all common handsets

- Existing infrastructure can be upgraded easily (parallel protocolssupported by many vendors)

- Elimination of fraud due to online charging

- Roaming agreements for postpaid subscribers can be used

- Enabling of inbound roaming with CAP2

- Service looks / feels the same as for postpaid user

- Saving speech trunks for rerouting

CONs:

- No online charging for SMS

Aspects concerning CAMEL Phase 2 roaming

19

CAMEL Phase 1

20

CAMEL Phase 1 Services

• Control of outgoing calls at the served subscriber’s VMSC: number translation, selective barring or enabling of calls depending onlocation, time of day, ...

• Control of incoming calls at the GMSC: re-routing, selective barring or enabling of calls depending on location, time of day, calling party identity, …

• Clearing the call at any time, using the CAMEL control at the originating or terminating side

• Any Time Interrogation: Location information and subscriber state

21




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

22

CAMEL Subscription Information

• Major challenges in deploying IN services in mobile networks:– lack of centralized Service management system (SMS) responsible for

trigger activation and criteria deployment

– Changing access networks (multiple visited networks)

• Solution: CAMEL Subscription Information (CSI) containing triggerinformation

• CSI is defined in a service specific way as part of HLR data and will thus be dynamically deployed in relevant service entities (e.g. VLR, SGSN, HLR, SMS-C, etc.) for roamed in users

• Service triggering entities make use of CSI for determining if CSE needs to be contacted

è Refer to 3GPP TS 23.078 for detailed descriptions of the various types of CAMEL Subscription Information.

23

CAMEL Subscription Information (cont.)

CSI Examples (for CAMEL Phase 1):

– Originating CAMEL Subscription Information (O-CSI)

is transferred to the VPLMN (at location update) and to the IPLMN (for an incoming call in the GMSC).

O-CSI contains trigger information that is required to invoke a CAMEL Service Logic for Mobile Originating calls (in the VMSC) and Mobile Forwarding calls (in the VMSC and the GMSC).

– Terminating CAMEL Subscription Information (T-CSI)

is transferred to the IPLMN for an incoming call in the GMSC.

T-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Terminating calls in the GMSC.

24




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

O-CSI

T-CSI O-CSI

25

CAMEL Phase 1 BCSMs and CAP

CAMEL - BCSM and CAMEL Application Part (CAP) Protocol

• CAMEL features are based on a simplified IN CS-1 BCSM supporting– 6 Detection Points (3 DPs in O-BCSM, 3 DPs in T -BCSM)

– 2 Trigger Detection Points

• Collected Information (O-BCSM)

• Termination Attempt Received (T-BCSM)

• CAMEL Application Part (CAP)– is based on ETSI Core INAP comprising seven operations:

• InitialDP, Continue, Connect, Release Call, EventReportBCSM, RequestReportBCSMEvent, Activity Test

26

CAMEL Phase 1 O_BCSM

O_Null & Authorize_Orgination_Attempt & Collect_Info

Analyse, Routing & Alerting

DP2

O_Exception

DP9 O_Active

DP7

Collected_Info

O_Answer

O_Disconnect

27

CAMEL Phase 1 T_BCSM

T_Null

Terminating Call Handling

DP12

T_Exception

DP17 T_Active

DP15

Term._Attempt_Authorized

T_Answer

T_Disconnect

28

CAMEL Detection Point Types

Three different types of DPs are identified in CAMEL

• Trigger Detection Point - Request (TDP-R).

This detection point is statically armed and initiates a CAMEL control relationship when encountered and there is no existing relationship due to the same CSI. 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 when encountering the DP and the gsmSSF waits for instructions from the gsmSCF.

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

29

Arming of DPs

• A DP for mobile terminating call handling is statically armed in GMSC as result of T-CSI delivery from HLR.

• A DP for forwarding leg handling is statically armed in GMSC as result of O-CSI delivery from HLR.

• A DP for mobile originating call or forwarded leg handling is statically armed in VMSC as result of O-CSI delivery from VLR.

• A DP is dynamically armed by the gsmSCF within the context of a CAMEL control relationship (between the gsmSSF and the gsmSCF).

30

CAMEL 1 Detection Points List

TDP

TDP

31

CAMEL Application Protocol (CAP) Phase 1

• gsmSSF to gsmSCF– Activity Test Response

– Event Report BCSM

– Initial DP

• gsmSCF to gsmSSF– Activity Test

– Connect

– Continue

– Release Call

– Request Report BCSM Event

32

PrePaid for CAMEL Phase 1 (1)

PrePaid „light“ Service using CAMEL phase 1

• no Announcements

• USSD based account enquiry and top-up

• gsmSCF releases call based on account balance– Advantage:

• Works with CAMEL1

• No tromboning of call legs

– Disadvantage:

• New User Interface,

• Timer resources at SCP needed,

• higher inaccuracy in account handling,

• effectively new service to be designed

33

Example: MOC with CAMEL – CSI Provision

HLR

MSC

Visited NetworkDestination Network

Home Network

VLR gsmSSF

1

T-CSI

O-CSI

O-CSI

2

1 Location Update Request

2 Insert Subscriber Data (O-CSI)

CSEgsmSCF

• Location Update and CapabilityNegotiation Phase

34

MOC with CAMEL Phase 1 PrePaid „light“

HLRHome Network

5

3

T-CSIO-CSI

4

3 Call Setup

4 CAP_Initial DP (CalledPartyBCD, service key..)

CSEgsmSCF

5 RequestReportBCSM (Answer), Connect Call to destination

6

6 Initial Address Message

MSC

Destination Network

VLR gsmSSF

O-CSI

• Call Setup and Completion

7 EventReportBCSM (Answer)

7

VisitedNetwork

35

PrePaid for CAMEL Phase 1 (2)

PrePaid „Rerouting“ Service using CAMEL phase 1

• CAMEL used to take call back to HPLMN

• Use of proprietary INAP or CAPv2 for call handling in HPLMN– Advantage: Service behaviour like in HPLMN

– Disadvantage: Tromboning of call legs if destination not in HPLMN, more signalling, Non-desired Service interaction with Barring of outgoing international calls

36

Example: Prepaid „CAMEL1 Rerouting“

HLR

MSC


Home Network

VLR gsmSSF3

T-CSI

O-CSI

O-CSI

4

3 Call Setup

4 CAP_Initial DP (CalledPartyBCD, service key..)

CSEgsmSCF

SRF

IP

• Call Rerouting via Home Network

GMSC SSP

5 Connect call to GMSC+CorrelationId

7 IN_Initial DP (CorrelationId) and other Interactions as withCAMEL 2

6 Initial Address Message to HPLMN

8

6 5

8 Initial Address Message to destination

7

37

CAMEL Phase 2

38

CAMEL Phase 2

• The second phase of CAMEL enhances the capabilities of Phase 1

• The following capabilities have been added:

- Additional event detection points (for error handling)- Interaction between a user and service using announcements, voice prompting

and information collection via in band interaction or USSD interaction.- Control of call duration and transfer of Advice of Charge Information to the

mobile station. - The CSE can be informed about the invocation of supplementary services (e.g

ECT, CD, MPTY).- For easy post processing, charging information from a serving node can be

integrated in normal call records.

39

CAMEL Phase 1

• O-CSIand T-CSI

• Basic DPs

• Basic calloperations

• 2-step Interrogation

• Any Time Interrogation

CAMEL Phase II enhancements

CAMEL Phase 2

• U-CSI, UG-CSI, SS-CSI, TIF-CSI• DPs including conditional triggers

- triggering of eventsFailure, Busy, No Answer, Abandon

• Charging facilities- online charging, ticket information

• User dialogs and announcements- assist procedure

• SS Invocation notification• USSD Operations

40




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

gsmSRF

USSD

41

Additional CAMEL Phase 2 CSI

CSI form Phase 1 plus:• Supplementary Service Invocation Notification CAMEL Subscription Information (SS-

CSI)is transferred to the VPLMN. SS-CSI is used to notify the CSE about the invocation of certain Supplementary Services.

• Translation information Flag CAMEL Subscription Information (TIF-CSI)is held in the HLR. TIF-CSI is used in the HLR for registering short Forwarded-to-Numbers (FTNs). When TIF-CSI is present, the subscriber is allowed to register short FTNs.When the subscriber invokes Call Deflection, TIF-CSI in the VPLMN allows the subscriber to deflect to short Deflected-to-Numbers.

• USSD CAMEL Subscription Information (U-CSI)is held in the HLR; it is not sent to any other node. U-CSI contains trigger information which is used to invoke a USSD application in the CSE for the served subscriber.

• USSD General CAMEL Subscription Information (UG-CSI)is held in the HLR; it is not sent to any other node. UG-CSI contains trigger information which is used to invoke a USSD application in the CSE for all subscribers.

42




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

gsmSRF

USSD

O-CSI

T-CSI

TIF-CSI

SS-CSI

U-CSI UG-CSI

O-CSI

43

Special Resource Access in CAMEL Phase 2

Visited Network

Home Network

gsmSSF

gsmSRF

CSEgsmSCF

gsmSSF

gsmSSF

1. SRF in HPLMN is accessed fromVPLMN

Bilateral agreement allows accessto SRFs in VPLMN.

gsmSSF

2a. DistributedSRFs in VPLMN, standalone orintegrated 2b. Centralized SRFs in VPLMN

gsmSSF

gsmSRF

gsmSRF gsmSRF

44


O_Null & Authorise_Origination_Attempt_Collect_Info

DP2

O_Exception

DP9

DP7

Collected_Info

O_Answer

Basic Call transition Transition beyond Basic Call

DP4

DP5

DP6

O_Disconnect

O_Active

Route_Select_ Failure

O_Busy

O_No_Answer

DP10

O_Abandon

& Alerting

Analyse, Routing

45

CAMEL 2 O-BCSM Detection Points

CAMEL Detection Point: DP Type Description:

DP2 Collected_Info TDP-R Indication that the O-CSI is analysed.

DP 4 Route_Select_Failure EDP-N, EDP-R Indication that the call establishment failed

DP 5 O_Busy EDP-N, EDP-R Indication that:- a busy indication is received from the terminating party,- a not reachable event is determined upon a cause IE in the ISUP release message.

DP6 O_No_Answer EDP-N, EDP-R Indication that an application timer associated with the O_No_Answer DP expires

DP7 O_Answer EDP-N, EDP-R Indication that the call is accepted and answered by the terminating party.

DP9 O_Disconnect EDP-N, EDP-R A disconnect indication is received from the originating party or from the terminating party.

DP 10 O_Abandon EDP-N Indication that a disconnect indication is received from the originating party during the call establishment procedure

46


T_Null


DP12

T_Exception

DP17 T_Active

DP15

Terminating_Attempt_Authorised

T_Answer

Basic Call transition

Transition beyond Basic Call

DP13

DP14

T_Busy

T_No_Answer

DP18

T_Abandon

T_Disconnect

47



DP12 Terminating_Attempt_Authorised

TDP-R Indication that the T-CSI is analysed.

DP 13 T_Busy EDP-N, EDP-R Indication that:- a busy indication is received from the destination exchange,- Not reachable or call establishment failure event is determined from the HLR response or upon a cause IE in the ISUP release message.

DP 14 T_No_Answer EDP-N, EDP-R Indication that an application timer associated with the T_No_Answer DP expires

DP15 T_Answer EDP-N, EDP-R Call is accepted and answered by terminating party

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

DP 18 T_Abandon EDP-N A disconnect indication is received from the originating party during the call establishment procedure

48

CAP Phase 2

• gsmSSF – CSE– Activity Test ack– Apply Charging Report– Call Information Report– Event Report BCSM– Initial DP

• CSE – gsmSRF– Cancel– Play Announcement– Prompt and Collect User

Information– Activity Test

• gsmSRF - CSE– Assist Request Instructions– Prompt and Collect User

Information ack– Specialized Resource Report– Activity Test ack

• CSE - gsmSSF– Activity Test– Apply Charging– Call Information Request– Cancel– Connect– Connect to Resource– Continue– Establish Temporary Connection– Furnish Charging Information– Release Call– Request Report BCSM Event– Reset Timer– Send Charging Information

49

Functionality:Triggering of IN Services only under certain conditions like

• number length• leading digits• bearer service and capability• whether call is originating or forwarded

Operator Benefit:• Improved services• Reduced signalling load between SSP and SCP

Applications:• Short code access to own mailbox from visited PLMN

Conditional Triggering Criteria

50

1. <2200>3. <+43.676.2200>2. <2200>

Calling Mailbox

1. Subscriber dials a short number to reach mailbox2. Digit analysis initiates IN handling of call3. CSE translates short number to MSISDN

VPLMN HPLMN

Mail Box

„Visited MSC“

„Home MSC“

Example: CAMEL2: Short code access to mail box

CSE

MSC SSF

MSC SRF

51

Example: MOC with CAMEL2 (1)

HLR

MSC


Home Network

VLR gsmSSF

1

T-CSI

O-CSI

O-CSI

2

1 Location Update Request

2 Insert Subscriber Data (O-CSI)

CSEgsmSCF

gsmSRF

IP

• Location Update and CapabilityNegotiation Phase

52


HLR

MSC

Visited Network

Destination Network

Home Network

VLR gsmSSF

56

3

T-CSI

O-CSI

O-CSI

4

3 Call Setup

4 Initial DP (CalledPartyBCD, service key..)

5 Establish Temporary Connection

8 Connect to Resource,Play Announcement orPrompt and Collect

9 Disconnect Forward Connection

CSEgsmSCF

gsmSRF

IP

6 Initial Address Message (ISUP)

• Call Setup Phase with User Interaction

7

7 Assist Request Instruction

89

X

53


HLR

MSC

Visited Network

Destination Network

Home Network

VLR gsmSSF

10

12

T-CSI

O-CSI

O-CSI

10 Connect (CalledPartyNumber)

11 Apply Charging (Timer, Tariff Change,..)

12 Initial Address Message (ISUP)

13 Apply Charging Report...

CSEgsmSCF

gsmSRF

IP

• Online charged connection Phase

1113

54

CAMEL and USSD

HLR

gsmSCF

MSC MS

Visiting Network

Home Network

VLR

MAP

MAP

CAMEL USSDapplication

USSD Handler

USSD Notifications to CSE require Trigger (U-CSI + UG-CSI) in HLR

USSD

55

CAMEL USSD

• Functional Elements:– HLR: The HLR stores for subscribers requiring CAMEL support the information

relevant to the current subscription regarding U-CSI. The UG-CSI is stored as global data applicable to all subscribers. The U-CSI and the UG-CSI are stored in the HLR only.

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

• Interfaces:– gsmSCF-HLR interface

This interface is used for USSD operations, both for gsmSCF-initiated dialogues and MS-initiated dialogues (relayed via HLR). It is a network operator option whether to support or not USSD operations on this interface.

56

CAMEL and USSD

• Note that the procedure at the CAMEL USSD application at the HLR is implementation dependent. The following text describes a recommended procedure:– The CAMEL USSD application shall check the U-CSI data assigned to the

specific subscriber. If the service code is present in the U-CSI the USSD is routed to the gsmSCF given by the gsmSCF address stored against the service code in the U-CSI.

– If the service code is not present in the U-CSI (or the subscriber does not have U-CSI defined) then the CAMEL USSD application shall check the UG-CSI data assigned to the HLR. If the service code is present in the UG-CSI then the USSD is routed to the gsmSCF given by the gsmSCF address stored against the service code in the UG-CSI.

– If the service code is not present in U-CSI or UG-CSI an error (unknown application) is returned to the USSD handler.

57

USSD to/from gsmSCF

gsmSCF to HLR operations

• Unstructured SS Request

• Unstructured SS Notify

• Process Unstructured SS Data ack

• Process Unstructured SS Request ack

HLR to gsmSCF operations

• Unstructured SS Request ack

• Unstructured SS Notify ack

• Process Unstructured SS Data

• Process Unstructured SS Request

• Begin Subscriber Activity

• Requires exchange of USSD CAMEL Subscription Information (U-CSI)

• Requires exchange of Content of the USSD General CAMEL Service Information (UG-CSI)

58

CAMEL Supplementary Service Notification

HLR gsmSCF

MSC Visited Network

Home Network

VLR

MAPMAP

MAP

At the invocation of any of the services ECT, CD and MPTY the VLR checks whether the criteria for sending a notification are fulfilled, i.e. whether the subscriber is provisioned with the SS-CSI and the particular invoked supplementary service is marked in the SS-CSI.

SS invoke

59

CAMEL SS related Functional Elements

• HLR: For subscribers requiring CAMEL support, the HLR stores the information relevant to the current subscription regarding SS-CSI. The SS-CSI is sent to the VLR at Location Update, on Data Restoration or if the SS-CSI is updated by administrative action. When processing an invocation of the CCBS supplementary service, the HLR shall send a notification of the invocation of the supplementary service to the gsmSCF if required by the SS-CSI.

• MSC:When processing an invocation of any of the supplementary services ECT, CD and MPTY, the MSC may receive an SS-CSI from the VLR, indicating that a notification of the invocation of the supplementary service shall be sent to the gsmSCF.

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

• gsmSCF: The gsmSCF receives the SS Invocation Notification from the MSC or HLR.

60

SS Notifications

MSC to gsmSCF operations

• SS Invocation Notification

HLR to VLR operations

• Delete Subscriber Data

• Insert Subscriber Data

HLR to gsmSCF operations

• SS Invocation Notification

VLR to MSC operations

• Invoke SS result

• Send Info For Incoming Call

Requires exchange of Supplementary Service Invocation Notification CAMEL Subscription Information (SS-CSI)

61

CAMEL Phase 3

62

CAMEL Phase 3

• CAMEL phase 3 adds many new features:– Services for MO SMS (basically charging and re-routing).

– Services for GPRS, both for the MO and MT sides (also basically for chargingand re-routing). This includes to monitor from attach to detach or PDP Contextsindividually.

– Notification of Mobility Management events (e.g. attach, detach, change of VLR area).

– New types of triggers (D-CSI, N-CSI, VT-CSI, etc).

– New triggering criteria (release cause for some events).

– AnyTimeModification operation.

– Interface to Location Services (based on MAP ATI).

• The bigger changes are services for GPRS, SMS and MobilityManagement.

63

CAMEL Phase 2

• O-CSI, T-CSI, U-CSI, UG-CSI, SS-CSI, TIF-CSI

• Basic and conditional DPs

• Basic call operationsand charging

• User dialogs• USSD operations• 2-step Interrogation• Any Time

Interrogation

CAMEL Phase 3 enhancements

CAMEL Phase 3

• GPRS-CSI, SMS-CSI, N-CSI,D-CSI, M-CSI, VT-CSI

• DPs and operations for GPRS • DPs and operations for MO-SMS• Mobility triggers• Enhanced MAP IF HLR - gsmSCF

- Any Time Subscription Interrogation- AT Modification- AT Notification

• SoLSA

64

MO SMS triggering

GPRS interaction Prepaid GPRS

Dialled services

CAMEL Phase 3 service examples

Sending Prepaid SMSs whenroaming

Mobility ManagementInformation related to the actual location: city phone, office zone, home zone

B-number related services(short numbers, special numbers,VMS,…)

Improved triggering Improved terminating services

65




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

gsmSRF

USSD

SGSNgprsSSF

GGSN PDN

SMSGPRS

66

CAMEL Phase 3 Functional Elements (cont.)

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

• gsmSSF: functional entity that interfaces the MSC/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.

• gsmSRF: functional entity which provides various specialized resources. It interfaces with the gsmSCF and with the MSC. This entity is defined in ITU-T Q.1214 with variations defined in the specification.

67

Additional CAMEL Phase 3 CSI

CSI from Phase 1 plus Phase 2 plus:

• Dialled Services CAMEL Subscription Information (D-CSI)

is transferred to the VPLMN (at location update) and IPLMN (for an incoming call in GMSC). D-CSI contains trigger information which is required to invoke a CAMEL service logic for subscribers dialled services.

• GPRS CAMEL Subscription Information (GPRS-CSI)

is transferred to the VPLMN. GPRS-CSI contains trigger information which is required to invoke a CAMEL Service Logic for GPRS Sessions and PDP Contexts.

• Mobility Management CAMEL Subscription Information (M -CSI)

is transferred to the VPLMN. M-CSI is used to notify the CSE about Mobility Management events.

• Network CAMEL Subscription Information (N-CSI)

is transferred to the VPLMN. N-CSI identifies services offered on a per-network basis by the serving PLMN operator for all subscribers. This CSI shall be stored in the MSC.

68

Additional CAMEL Phase 3 CSI (cont.)

• Short Message Service CAMEL Subscription Information (SMS-CSI)

is transferred to the VPLMN. SMS-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Originating Short Message submissions.

• VMSC Terminating CAMEL Subscription Information (VT-CSI)

is transferred to the VPLMN at location update. VT-CSI contains trigger information which is required to invoke a CAMEL Service Logic for Mobile Terminating calls in the VMSC.

69




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

gsmSRF

USSD

SGSNgprsSSF

GGSN PDN

SMSGPRS

VT-CSI

O-CSI

T-CSI

gprs-CSI

N-CSID-CSI

M-CSI

D-CSI

SMS-CSI

U-CSI UG-CSI

O-CSI

SS-CSI

TIF-CSI

SMS-CSI

70


O_Null & Authorise_Origination_Attempt_Collect_Info O_Exception

Collected_Info

O_Answer


O_Disconnect

O_Active

Route_Select_Failure

O_Busy

O_No_Answer

O_Abandon

& Alerting

Routing

Analysed_Information

Analyse_Information

O_active_failure

invalid_information

O_routing_and_alerting_failure

71



DP Collected_Info TDP-R Indication that the O-CSI is analysed.

DP Analysed_Information TDP-R Availability of routeing address and nature of address.

DP Route_Select_Failure TDP-R, EDP-N, EDP-R

Indication that the call establishment failed.

DP O_Busy EDP-N, EDP-R Indication that:- a busy indication is received from the terminating party,- a not reachable event is determined upon a cause IE in the ISUP

release message.DP O_No_Answer EDP-N, EDP-R Indication that:

- an application timer associated with the O_No_Answer DP expires,- a no answer event is determined upon a cause IE in the ISUP

release message.

DP O_Answer EDP-N, EDP-R Indication that the call is accepted and answered by the terminating party.

DP O_Disconnect EDP-N, EDP-R A disconnect indication is received from the originating party or from the terminating party.

DP O_Abandon EDP-N, EDP-R Indication that a disconnect indication is received from the originating party during the call establishment procedure.

72


T_Null


T_Exception

T_Active

Terminating_Attempt_Authorised

T_Answer


T_Busy

T_No_Answer

T_Abandon

T_Disconnect

T_active_failure

T_call_handling_failure

73



DP Terminating_Attempt_Authorised

TDP-R Indication that the T-CSI / VT_CSI is analysed.

DP T_Busy TDP-R (note 2), EDP-N, EDP-R

Indication that:- a busy indication is received from the destination exchange,- Busy event is determined in the visited MSC,- Not reachable or call establishment failure event is

determined from the HLR response or upon a cause IE in the ISUP release message.

DP T_No_Answer TDP-R (note 2), EDP-N, EDP-R

Indication that an application timer associated with the T_No_Answer DP expires .

DP T_Answer EDP-N, EDP-R Call is accepted and answered by terminating party.

DP T_Disconnect EDP-N, EDP-R A disconnect indication is received from the terminating party or from the originating party.

DP T_Abandon EDP-N, EDP-R A disconnect indication is received from the originating party during the call establishment procedure.

74

CAP Phase 3

• gsmSSF – CSE– Activity Test ack– Apply Charging Report– Call Information Report– Event Report BCSM– Initial DP

• CSE – gsmSRF– Cancel– Play Announcement– Prompt and Collect User

Information– Activity Test

• gsmSRF - CSE– Assist Request Instructions– Prompt and Collect User

Information ack– Specialized Resource Report– Activity Test ack

• CSE - gsmSSF– Activity Test– Apply Charging– Call Information Request– Cancel– Connect– Connect to Resource– Continue– Continue with Argument– Disconnect Forward Connection– Establish Temporary Connection– Furnish Charging Information– Release Call– Request Report BCSM Event– Reset Timer– Send Charging Information

75

CAMEL Phase 4

76

CAMEL Phase 4 (Release 5)

• CAMEL Phase 4 is an integral part of 3GPP Core Network Release 5– Release 5 has been delivered in march 2002

• CAMEL Phase 4 enhances the capabilities of phase 3– CAMEL Phase 4 circuit switched call control encompasses all features of

previous CAMEL phases but extends these to completeness (see next slide)

– Support of 3GPP IP Multimedia Domain (IMS)

è Defined in separate document:

3GPP TS 23.278: (CAMEL) Phase 4 - Stage 2 IM CN Interworking (Rel 5)

• CAP V4 and previous CAP versions may be transported over IP (based on IETF SIGTRAN work)

• NOTE:

With CAMEL Phase 4, it is possible that only a limited subset of the new functionalities is supported, in addition to the complete support of CAMEL Phase 3.

77

CAMEL Phase 4

• CAMEL phase 4 adds many new features

– Call Party Handling for voice calls

– Midcall detection point

– Services for MT SMS (basically charging and re-routing)

– Mobility Management for GPRS

– Support of Optimal Routing

– Enhancements to Any Time Modification (ODB)

– Any Time Interrogation for Terminal Capabilities

– Flexible tones injection

– Location information during call

– Services for IMS

78

CAMEL Phase 4 Subsets

• An entity may support – complete CAMEL phase 4 or, as a network option,

– complete CAMEL phase 3 functionality and one or more subsets of CAMEL phase 4.

• The subsets of CAMEL phase 4 are the following:

- Relative to Circuit switched Call Control- CS call handling- Charging notification (with CS call handling)

– Relative to GPRS interworking- Notification of GPRS mobility management to CSE

- Relative to Short Message Services- CAMEL control over MT SMS

- Relative to Subscriber Location and State retrieval- GPRS Any Time Interrogation

79




CS

VMSC

gsmSCF HLRMAP

VLRgsmSSFGMSC

gsmSSF

MAPCAP

PSTN/PLMN PSTN/PLMN

RoamingLeg

PSTNPLMN

gsmSRF

USSD

SGSNgprsSSF

GGSN PDN

SMSGPRS

VT-CSI

O-CSI

T-CSI

gprs-CSI

N-CSID-CSI

M-CSI

D-CSI

U-CSI UG-CSI

O-CSI

SS-CSI

TIF-CSI

MT-SMS-CSIMO-SMS-CSI

MO-SMS-CSIMT-SMS-CSI

MG-CSI

80

CAMEL in IMS

• CAMEL architecture is integrated with IMS

• New functionality added: IM SSF (IMS Service Switching Function).

• Interfaces:– CSCF-IM SSF based on SIP (ISC: IMS Service Control).

– IM SSF-gsmSCF being defined (based on CAMEL Phase 3).

• IMS-CSI to define triggering criteria.

• State models based on CAMEL phase 3 with mapping to SIP methods/responses:– O-IM-BCSM for originating sessions.

– T-IM-BCSM for terminating sessions.

81Home Network

CAMEL Phase 4 in IMS Domain

Visited Network

IP Multimedia


CSE HSSMAP

imSSF

Cx

IP Multimedia

IP Multimedia Subsystem

GGSN

MGCFT-SGW

MGWPSTNPLMN

SIP SIP

proxyCSCF

SIP

S-CSCF

CAP over

IP

SGSN

• IM-SSF provides– Triggering of CAMEL services in gsmSCF

– Call State model (O-IM-BCSM / T-IM-BCSM) based on CAMEL Phase 3!

82

CAMEL Functional components

• IP Multimedia Service Switching Function (IM-SSF)– functional entity that is a SIP Application Server interfaces SIP to CAP.

• IP Multimedia CAMEL Subscription Information (IM-CSI)– identifies the subscriber as having IP Multimedia CAMEL services.

• Service Platform Trigger Points (STP)– the points in the SIP signalling that instruct the SIP AS, OSA SCS and IM-SSF

to trigger the service logic.

– For the IM-SSF the IP Multimedia Camel Subscriber Information (IM-CSI) defines them.

• Initial Filter Criteria (iFC)– filter criteria that are stored in the HSS as part of the user profile and are

downloaded to the S-CSCF upon user registration.

– They represent a provisioned subscription of a user to an application.

83

Release 5: CAP over IP

SSF Appl SW

CAP

TCAP

M3UA

SCCP

SCTP

IP

SSF

SCP Appl SW

CAP

TCAP

M3UA

SCCP

SCTP

IP

SCP

API Interface

SGW

SCCP

SSF

Appl SW

CAP

TCAP

M3UA

SCCP

SCTP

IP

SSF

SCP

Appl SW

CAP

TCAP

MTP3

SCCP

MTP2

LI

SCP

TCAP

M3UA

MTP2SCTP

MTP3

IP LI

Interworking node

CAP

CAP over IP stack

Based on the IETF SIGTRAN work!

CAP over IP interworking with SS7

84

MOC VoIP with CAMEL interaction

S-CSCF/imSSF HSSUE CSE

Visited network Home network

Invite

If calling subsc. is not registered, dialogue with HSS is opened to obtain O-CSI

InitialDP

CAP instructionsAnalysis for calls requiring IN i.e. trigger criteria in O-CSI

P-CSCF

A

I-CSCF

85

CAMEL Release 5 for IP Multimedia Subsystem

• As part of CAMEL Phase 4 CAP can be used for call, session, message control– CAMEL for 3GPP Release 5 IP Multimedia Subsystem is defined in an extra

specification:

• 3GPP TS 23.278: (CAMEL) Phase 4 - Stage 2 IM CN Interworking (Release 5)

• Further important References:

– 3GPP 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"

– 3GPP TS 22.228: "3rd Generation Partnership Project; Technical Specification Group Systems Aspects; IP Multimedia (IM) Subsystem –Stage 1

– 3GPP TS 23.228: "3rd Generation Partnership Project; Technical Specification Group Systems Aspects; IP Multimedia (IM) Subsystem –Stage 2

– 3GPP TS 23.218: "3rd Generation Partnership Project; Technical Specification Group Core Networks; IP Multimedia (IM) Session Handling; IP Multimedia Call Model - Stage 2

86

CAMEL(SCF)

S-CSCF

IM-SSF

HSS

MSC (SSF)

HLR

2G Circuit Switch Voice Network3G IP based Voice

and Data Network

SGSN (SSF)

2.5G Packet Switch GPRS Data Network

MAP

CAP

MAP

MAP

CAP

CAP

MAP

SIP

CAMEL Evolution

Camel Phase 1 + 2Camel Phase 4

Camel Phase 3

87

CAMEL Deployment

• Camel Phase 2 is ‘on the paper’ richer than Camel Phase 1, but in realityCamel Phase 1 is preferred so far:– Direct routing from VPLMN1 to VPLMN2 is complex to handle from the charging

view point

– Most of the roaming calls are made in direction of the HPLMN : re-routing

– calls in HPLMN with Camel Phase 1 do not provide huge tromboning overload

– Advice of charge and interactions can be made through USSD

• Only few Operators have moved to Camel Phase 3 – mainly for GPRS PrePaid,

– but many operators did implement alternativ approaches to CAMEL as CAMEL 3 is considered to complex and expensive!

• Camel phase 4 is still a bit far away …– No strong need for ‘conference’ types of applications yet

– IMS is not yet deployed globally and motivates other (SIP) application servers

88

Summary of CAMEL Deployment

• 40.96% of the operators interviewed to date have submitted responses (34 operators). Of this, 62% have deployed CAMEL (Phase 1 and/or 2).

• Of those operators who have not deployed CAMEL Phase II, 33.3% declared that Phase II would be deployed. The remaining has no plans orhas not reached a decision on the matter

89

Wireless IN - WIN

• WIN falls under the ANSI, TIA and T1standards bodies :

• ANSI represents US interests abroad in terms of technical and policy postitions

• TIA and T1 create standards for wireline and wireless– TR45 is a wireless division of TIA, TR45.2 subcommitte focuses on standards for mobile

and personal communications; ANSI-41 and WIN

– T1 creates network inter-connection and interoperability standards for wireline and wireless, T1S1/T1P1 subgroups develops standards and techncial reports related to wireless networks and services

• WIN standards follow a development process different from CAMEL:– As WIN standards are conceived they are assigned a project number, E.g. PN-4287

Prepaid charging

– Once adopted by TIA the PN becomes an interim standard, such as IS-771 WIN Phase 1

– After an interim standard has been published by TIA, there is a 3-year period of revisionand acceptance

– When industry adopts the interim standard it becomes part of ANSI 41 e.g. IS-771 istargeted to become part of ANSI 41-E

90

WIN Phase 1

• WIN Phase 1 Service Drivers– Calling Name Presentation IS-764 fast track, June 1988

– Voice Controlled Services

– Incoming Call Screening

– WIN Phase 1 services and features defined by IS-771

• WIN P1 is based on ANSI 41-D established the use of trigger profile for determiningmobile user features and capabilities while roaming (Origination Request message):– Based on IN capability set CS-2

– An Originating BCSM with 3 detection points

– A Terminating BCSM with 3 detection points

– Rules for use of triggers includes

• Service independence

• Trigger list includes service logic address info

• Triggered service logic has precedence

91

WIN 1 Architecture

• WIN Phase 1: 3GPP2 N.S0013-0

92

WIN Phase 2

• WIN Phase 2 service drivers were:– Prepaid Charging PN 4287 fast track

– Preferred Language, Free Phone

– Other Billing Services - Advice of Charge and Premium Rate

– Charging)

– Call Management Capabilities – rejection of annoying calls

– Location-based Services – position request message provides serving MSC, Location and cell information

• WIN Phase 2 services and features defined by the IS-826 for PrepaidCharging and IS-818 for preferred language and location based phase 1 and 911 based services

93

WIN Phase 3

• WIN-based location infrastructure defined by SRD submission by CTIA to the TIA standards process:

• WIN Phase 3 service drivers are:– Location based charging

– Fleet and asset management services

– Enhanced call routing services

– Location based information services

• WIN Phase 3 projects– Location services and architecture (PN 4818)

– Location services authorization/privacy/security (PN 4746)

– Location Services Enhancements (PN 4747)

– Related project in support of the FCC wireless 911 (PN 3890)

camel

Documents

gpp camel study theme

camel gsm

standards study theme

camel increases

applications study theme

diameter study theme

vhe camel architecture

rerouting camel phase