CAMEL Overview LZU 108 5718

CAMEL Overview
LZU 108 5718
Slide Number 1
CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1
Table of Contents
Module 1
CAMEL Phase 1 and 2
Module 2
CAMEL Phase 3
Module 3
CAMEL Phase 4
Slide Number 2
CAMEL Phase 1 and 2
Slide Number 3
Customized Applications for Mobile networks Enhanced

Logic
The ETSI GSM Releases

European standardization activities
CAMEL Phase 1 was standardized by ETSI in 1996, as
part of the GSM R96 package.
CAMEL Phase 2 was standardized by ETSI in 1997, as
part of the GSM R97 package.
In 1998, slight enhancements to CAMEL Phase 2 were
released by ETSI, as part of the GSM R98 package.
Slide Number 4
Customized Applications for Mobile networks Enhanced

Logic
The 3GPP 3G Core Network Releases

Global standardization activities
CAMEL Phase 3 was standardized by 3GPP in 1999, as
part of the 3G Core Network R99 package.
3GPP is currently approving the specification of the 3G
Core Network Release "Rel-4. Rel-4 does not contain
new functionality for CAMEL.
3GPP is in the progress of specifying 3G Core Network
Release Rel-5. Rel-5 contains CAMEL Phase 4.
Delivery is scheduled for March 2002...
Slide Number 5
Overview
Part I
CAMEL Phase 1
Part II
CAMEL Phase 2
Part III
Mobile Call Cases
Part IV
Charging
Part V
Special CAMEL Features
Part VI
CAMEL Subscription Information
Part VII
CAMEL Standard Evolution Path
Part VIII
Signaling
Slide Number 6
Part I - CAMEL Phase 1
Contents
GSM Network nodes >
Call Forwarding >
GSM nodes with SSP and SCP >
SCP Types >
Protocol overview >
BCSM principles >
Cross PLMN boundary protocols >
Slide Number 7
GSM Network - overview

inter-network communication
Ho me Ne two rk
HPLMN
HLR
- Subscribers are registered in HPLMN

- IN Services run in HPLMN
IPLMN
VPLMN
MAP
MAP
VLR
GMS C
Incoming line
Roa ming le g
Forwa rde d le g
Inte rro g ating Ne two rk
Calls terminate in interrogating

PLMN
Slide Number 8
MS C
MS
MO ca ll - Outgoing le g
(or Forwa rding le g)
Vis ite d Ne two rk
Subscribers may roam in VPLMNs

GSM Network - overview (protocol overview)

AUC
HLR
EIR
HPLMN
HPLMN may
contain multiple
HLRs
VPLMN/
IPLMN
MAP
MAP
MAP
GMSC
VLR
MAP
MSC
BSC
BSC
ISUP
ISUP/TUP
(or local
variant)
MSC & GMSC may be co-located

MAP = Mobile Application Part
ISUP = ISDN User Part
Slide Number 9
GSM Call Forwarding (1)

Four GSM Forwarding Categories exist:
Call Forwarding Unconditional
Call Forwarding on Not-reachable
Call Forwarding on Busy
Call Forwarding on No-Answer
CAMEL interacts with all Forwarding Categories.
Slide Number 10
!Early Call Forwarding:

Unconditional, Not-Reachable (implicitly detached;
switched off; no paging response, in combination with
pre-paging), Busy (in combination with CCBS)
!Late Call Forwarding:
Busy, No Answer, Not-Reachable (no paging
response)
Slide Number 11
!Early Call Forwarding occurs in the GMSC/HLR

!Late Call Forwarding occurs in the VMSC
!Late Call Forwarding may be optimally routed
back to the GMSC: Optimal Routing of Late Call
Forwarding (ORLCF)
Slide Number 12
GSM Network
(with SSP)
HLR
HPLMN
Service Switching Function

Switching node for IN Services
- MT calls
- MF calls (early forwarding)
- MF calls (late forwarding with optimal routing)
VPLMN/
IPLMN
SSF
VLR
MSC
BSC
Slide Number 13
SSF
GMSC
Service Switching Function

Switching node for IN Services
- MO BSC
calls
- MF calls (late forwarding, no ORLCF)
GSM Network
(with SSP and SCP)
HLR
Service Control Point

Execution Environment
for IN Services
HPLMN
VPLMN/
IPLMN
SSF
SSF and SCP
may be colocated: "SSCP"
BSC
Slide Number 14
SCP
SCP
SSF
GMSC
VLR
MSC
BSC
HPLMN may contain

multiple SCPs
SCP Types
!SCP-T (AXE platform based)
!SCP-J (Jambala SCP, Jambala Application
Server; Telorb based)
!SCS (Service Capability Server; Telorb based)
!CCN (Cost Control Node; Telorb based)
For the CAMEL standard: all nodes are referred to as "SCP".

Slide Number 15
GSM Network
GSM/CAMEL Protocol overview
SCP
HLR
HPLMN
VPLMN/
IPLMN
MAP
CAP
MAP
MAP
CAP
SSP
VLR
MSC
BSC
SSP
MAP
ISUP
BSC
GMSC
ISUP
CAP = CAMEL Application Part

Slide Number 16
CAMEL/GSM BCSM Principles (1)
Call handling is specified in GSM TS 03.18 ("Basic Call

Handling"). Interaction between the BCSM and the gsmSSF is
specified in GSM TS 03.78 ("CAMEL stage 2").
BSCMs have Detection Points (DPs) and Call States. The SCP
may be contacted at DPs for Service Logic invocation or for
instructions.
For every Mobile Originating Call or Mobile Forwarded Call, an

instance of an O-BCSM is invoked in the MSC or GMSC.
For every Mobile Terminating Call, an instance of a T-BCSM is

invoked in the GMSC.
CAMEL Phase 1, Phase 2, Phase 3 and Phase 4 have different

BCSMs (more TDPs/EDPs).
Slide Number 17
CAMEL/GSM BCSM Principles (2)

Three types of DPs exist:
Trigger Detection Point (TDP). A TDP that may be statically

armed. A CAMEL Service may be invoked from a TDP,
provided that trigger conditions, if available, are fulfilled.
Event Detection Point Notify (EDP-N): An EDP-N may be

dynamically armed within a Service Logic. When an EDP-N is
met, the SCP is notified. Call processing continues.
Event Detection Point Interrupt (EDP-R): An EDP-R may be

dynamically armed within a Service Logic. When an EDP-R is
met, the SCP is notified. Call processing is suspended. The SSF
waits for instructions from the SCP.
Slide Number 18
CAMEL Phase 1 O-BCSM

Instance of OBCSM is invoked
SCP is contacted
Called party
answers
Calling party or
Called party
disconnects
O_Null & Autho ris e _Orig inatio n_

Atte mpt_Co lle c t_Info
DP2
Co lle c te d _Info
O_Exc e ptio n
SCP gives
instructions
Analys e , Ro uting & Ale rting
Call is routed
DP7
O_Ans w e r
SCP is notified
Call is active
DP9
O_Dis c o nne c t
Slide Number 19
O_Ac tive
SCP may give

instructions
CAMEL Phase 1 T-BCSM

Instance of TBCSM is invoked
T_Exc e ptio n
T_Null
SCP is contacted
Called party
answers
DP12
Te rm inating _Atte m pt_Authoris e d
SCP gives
instructions
Te rminating Call Handling
Calling party or
Called party
disconnects
Call is routed
DP15
DP17
T_Dis c o nne c t
Slide Number 20
T_Ac tive
T_Ans w e r
SCP is notified
Call is active
SCP may give
instructions
Invocation of BCSMs
Invocation of O-BCSM in MSC for MO call
Invocation of T-BCSM in GMSC for MT call
Invocation of O-BCSM in MSC/GMSC for MF call
"virtual" BCSMs
Multiple CAMEL relationships per call
Slide Number 21
Mobile Originating Call

If O-CSI present, then
CAMEL Service is started
gsmSCF (1)
CAMEL relationship
Call set up received from

access network;
O-BCSM is invoked
O(A-B)
T(A-B)
A-Party
B-Party
Call is routed (ISUP IAM)
MSC/gsmSSF
Slide Number 22
virtual T-BCSM is invoked

Mobile Terminating Call

gsmSCF (1)
CAMEL relationship
O(A-B)
T(A-B)
If T-CSI received from

HLR, then CAMEL Service
is started
O(A-B)
T(A-B)
A-Party
B-Party
GMSC/gsmSSF
MSC/gsmSSF
Call is routed (ISUP IAM)

Call enters GMSC;
Call is internally propagated
virtual O-BCSM is invoked
to terminating side;
T-BCSM is invoked
Slide Number 23
Mobile Forwarded Call (GMSC)

gsmSCF (1)
If O-CSI received from

HLR, then CAMEL
Service is invoked
gsmSCF (2)
CAMEL relationship (1)
Terminating call
handling
Call Forwarding
is initiated
Internal "ISUP- like" interface
O(A-B)
T(A-B)
T(B-C)
O(B-C)
A-Party
C-Party
GMSC/gsmSSF
Call is routed
(ISUP IAM)
Slide Number 24
B-Party
O-BCSM for
forwarding leg is
invoked
virtual T-BCSM
is invoked
Simultaneous CAMEL Services

Mobile Forwarded Call (VMSC)
O(A-B)
gsmSCF (2)
gsmSCF (1)
Terminating Call
Handling
O(A-B)
T(A-B)
A-Party
T(B-C)
T(A-B)
B-Party
MSC/gsmSSF
Simultaneous
CAMEL Services
Call is routed
(ISUP IAM)
Slide Number 25
Call
Forwarding
O(B-C)
C-Party
GMSC/gsmSSF
Call enters VMSC;

virtual O-BCSM,
virtual T-BCSM
is invoked
virtual T-BCSM
is invoked
If O-CSI present
in VLR, then
CAMEL service
is started
O-BCSM is
invoked
Cross PLMN boundary protocols
HLR - VLR (MAP V3)
Location Update, Restore Data
Provide Subscriber Info, Provide Roaming Number
GMSC - HLR (MAP V3) - (normally within the same PLMN)
Send Routing Info / Ack
MSC - GMSC (MAP V3)
Resume Call Handling
SCP - HLR (MAP V3) - (normally within the same PLMN)
Any Time Interrogation
SSP - SCP (CAP V1)
InitialDP, Continue, Connect etc.
Slide Number 26
Evolution of CAMEL Application Part (CAP)

! ITU-T CS; Q.1210 series (Core INAP CS1)
! ETSI EN 300 374 series (ETSI CS1)
! ETSI EN TS 101 046 - GSM TS 09.78 (CAMEL Application Part,
CAP V1, V2)
! 3GPP TS 29.078 (CAMEL Application Part, CAP V3, V4)
>> CAP is a derivative of ETSI CS1 <<

Slide Number 27
Part II - CAMEL Phase 2
Contents
Full roaming pre-paid charging >
User Interaction >
SSIN >
USSD >
Supported CAP operations >
Cross PLMN boundary protocols >
Slide Number 28
GSM Network - CAMEL Phase 2

Charging Operations - Pre-paid roaming
HLR
Charging Operations
SCP
HPLMN
IPLMN
VPLMN
SSP
VLR
BSC
Slide Number 29
MSC
SSP
GMSC
BSC
GSM Network
Intelligent Peripheral
(with SSP, SCP and IP/SRF)
HLR
Interaction with
subscriber
IP
SCP
HPLMN
VPLMN/
IPLMN
SSP
SSP
GMSC
VLR
MSC
SRF
Special Resource
Function
BSC
MS
Slide Number 30
BSC
Interaction with
subscriber

Protocol overview (slide 1: User Interaction)
MAP
HLR
HPLMN
VPLMN/
IPLMN
SCP
IP
CAP
MAP
MAP
ISUP
ISUP
CAP
SSP
VLR
SSP
MAP
MSC
BSC
CAP
GMSC
ISUP
BSC
ISUP

Slide Number 31

Protocol overview (slide 2: SSIN)
MAP
HLR
HPLMN
VPLMN/
IPLMN
SCP
MAP
CAP
MAP
CAP
MAP
SSP
VLR
SSP
MAP
MSC
GMSC
ISUP
ISUP
SSIN = Supplementary Service

Invocation Notification
BSC
BSC

Slide Number 32
Principles of User Interaction

>> Announcements may be played and information may be
collected at:
Call set up (DP Collected Info)
Call set up failure (DP Busy, DP No-Answer, DP Route-Select-Failure)
Call termination (DP Disconnect)
>> Follow-on calls may be initiated by the SCP

>> User interaction may be achieved by means of:
integrated Special Resource Function (SRF)
assisting SSF with integrated SRF
Intelligent Peripheral (IP)
Slide Number 33

Protocol overview (slide 3: USSD)
HLR
HPLMN
VPLMN/
IPLMN
SCP
MAP
MAP
CAP
MAP
CAP
SSP
VLR
SSP
MAP
MSC
GMSC
ISUP
ISUP
USSD = Unstructured
Supplementary Service Data
BSC
BSC

Slide Number 34
Overview of CAP v2 operations

Basic Call Control
InitialDP(IDP)
Connect (CON)
Continue (CUE)
ReleaseCall (REL)
RequestReportBCSMEvent (RRB)
EventReportBCSM (ERB)
ResetTimer (RST)
ActivityTest (AT)
Slide Number 35
Supported CAP V2 operations

(continued)
Charging
ApplyCharging (ACH) - Call duration control
ApplyChargingReport (ACR)
CallInformationRequest (CIRq) - Call statistics gathering
CallInformationReport (CIRp)
FurnishChargingInformation (FCI) - 40 octets of free format data
SendChargingInformation (SCI) - Advice-of-Charge information
Slide Number 36
Supported CAP V2 operations

(continued)
User Interaction
ConnectToResource (CTR)
EstablishTemporaryConnection (ETC)
DisconnectForwardConnection (DFC)
AssistRequestInstruction (ARI)
PlayAnnouncement (PA)
PromptAndCollectUserInformation (P&C)
SpecializedResourceReport (SRR)
Slide Number 37
Cross PLMN boundary protocols
MSC - SCP (MAP V3)
Supplementary Service Invocation Notification
SCP - HLR (MAP V3) - (normally within the same PLMN)
Unstructured Supplementary Service Data
SCP - IP (CAP V2) - (normally within the same PLMN)
PlayAnnouncement, Prompt&Collect etc.
Slide Number 38
Part III - Mobile Call cases

Contents
Slide Number 39
Mobile Originating call (MO call) >

Mobile Terminating call (MT call) >
Mobile Forwarding call (MF call) - early forwarding >
Mobile Forwarding call (MF call) - late forwarding >
IN Call Setup - MO Call

Service Logic
HLR
(MO Service)
HPLMN
SCP
IN trigger
SSP
VLR
GMSC
MSC
(+31 70 656 9911)

+31 70 656 9911
BSC
MS
Slide Number 40
BSC
(diversion address)
VPLMN
IN Call Setup - MT Call

Service Logic
HLR
(MT Service)
SCP
HPLMN
VPLMN
IN trigger
SSP
VLR
GMSC
MSC
+31 70 767 9911
BSC
MS
Slide Number 41
BSC
IPLMN
IN Call Setup - MF Call (early forwarding)

Service Logic
HLR
(MF Service)
SCP
HPLMN
VPLMN
IN trigger
SSP
VLR
GMSC
MSC
0901-264 99 99
C-party
BSC
MS
Slide Number 42
BSC
Early forwarding
takes place
IPLMN
IN Call Setup - MF Call (late forwarding)

Service Logic
HLR
(MF Service)
SCP
HPLMN
VPLMN
SSP
VLR
IN trigger
MSC
C-party
0901-264 99 99
BSC
MS
Slide Number 43
GMSC
Late forwarding BSC

takes place
IPLMN
Part IV - Charging (CDRs)
Contents
Mobile Originated call cases >
Mobile Terminated call cases >
Slide Number 44
Mobile Originated Call cases

Call Data Records
HLR
Clearing
House
Administration
Systems
SCP
IDP
(CRN + MSCA)
HPLMN
VPLMN/
IPLMN
Billing
Gateway
TAP Records
SSP
SSP
VLR
GMSC
MSC
Call Data Records

Slide Number 45
Billing
Gateway
TAP3 standard
CDRs
Mobile Terminated Call cases

Call Data Records
Billing Gateway
HLR
SCP
SRI
(CRN + GMSCA)
HPLMN
VPLMN/
IPLMN
PRN
(CRN + GMSCA)
SSP
VLR
IDP
(CRN + GMSCA)
SSP
GMSC
MSC
IAM (ISUP)
Call Data Records

Slide Number 46
Call Data Records

Charging Considerations
Call Detail Records of the various call cases may contain CAMEL
specific data elements (CDRs produced in MSC, GMSC, SCP); refer to
GSM TS 12.05.
CDRs produced in the MSC (in VPLMN) may be correlated with CDRs
produced in the SCP (in HPLMN)
Each CAMEL Phase requires support of a specific TAP level (CAMEL

Phase 1: TAP 2.2; CAMEL Phase 2: TAP 3).
CAMEL markings in the CDRs need to be supported by administration

systems, charging systems, statistics systems, clearing houses etc.
Operators may charge a CAMEL invocation fee.
Slide Number 47
Part V - Special CAMEL Features
Contents
Any Time Interrogation >
Unstructured Supplementary Service Data >
Notification on Call Forwarding >
Supplementary Service Invocation Notification >
Short Forwarded-to-Numbers >
Slide Number 48
Any Time Interrogation (ATI)

HLR knows current VLR
of subscriber.
HLR may reject ATI
request.
HPLMN
HLR
...
IPLMN
SSF
VMSC
SCP
ATI result (MAP)
Provide Subscriber Info (MAP)

Provide Subscriber Info Ack (MAP)
VPLMN
VLR
Script
ATI request (MAP)
Script requires info about

subscriber; knows HLR
address. CAP
SSF GMSC
CAP
Subscriber State (choice)
Location Information
- CAMEL Busy
Location Number
- Assumed Idle
- Network Determined not Reachable
CellIdOrLAI
Geographical Information
Age Of Location Information
Lookup table
Slide Number 49
Subscriber is registered in VPLMN

Mobile Originated/Terminated CAMEL Service is active
VLR number
USSD (Terminal Initiated)

USSD
Script
HLR checks internal USSD handler
USSD result (MAP)
HLR checks U-CSI for subscriber

HLR checks UG-CSI
HLR
HPLMN
USSD request (MAP)
USSD result (MAP)

USSD request (MAP)
SCP
Service Key
VPLMN
VLR
USSD Link
VMSC
USSD Request
USSD Result

Slide Number 50
text
text
text
text
...
Text Only
Slide Number 51
Text Only
Slide Number 52
USSD (Network Initiated)

HLR knows current VLR
for subscriber.
HLR
HPLMN
Script
USSD request (MAP)
SCP
USSD result (MAP)
USSD request (MAP)

USSD result (MAP)
MSISDN/IMSI
Script needs to send

information to subscriber
VPLMN
VLR
IPLMN
SSF
CAP
USSD Link
VMSC
USSD Result
USSD Request

Mobile Originated/Terminated
CAMEL Service is active
Slide Number 53
CAP
text
text
text
text
...
SSF
GMSC
Notification on conditional call forwarding

(Early forwarding - example scenario)
Subscriber has T-CSI...
HPLMN
VPLMN
VLR
PSI Res
PSI
PRN
PRN Res
VMSC
IN Triggering Call Processing

Script
takes place... Continues...
HLR GSM Forwarding
Notification... SCP diverts SCP
the call...
CAP
2nd SRI
SRI Ack
(incl. FTN)
1st SRI
SSF
SRI Ack
(incl T-CSI)
IPLMN
GMSC
IAM (ISUP)
Call is forwarded
to C-Party
Slide Number 54
Notification on conditional call forwarding

(Late forwarding - example scenario)
Subscriber has T-CSI...
HPLMN
VPLMN
VLR
HLR
(1)
Terminating service
logic is started...
GSM Forwarding
Notification...
SCP diverts
(1) the call...
Terminating call
handling messages...
Call is routed to
the VMSC...
VMSC
(3)
Script
SCP
(2)
(4)
(4)
CAP
IPLMN
SSF
IAM (ISUP)
(3)
RCH (MAP)
(1)
GMSC
(4)
IAM (ISUP)
(5)
Subscriber busy...
Slide Number 55
Call is forwarded
to C-Party
Supplementary Service Invocation Notification

(example scenario)
Subscriber has
SS-CSI
SSIN
Handler
FDS
HLR
SCP
Proprietary interface
SS-CSI is sent at
Location Update
HPLMN
SSIN (MAP)
VPLMN
VLR
SS-CSI
IPLMN
Call is set up...
VMSC
GMSC
SS handling is not affected
Subscriber invokes MPTY
Slide Number 56
Short Forwarded-to-Numbers
Subscriber registers
in VLR; has "short
FTN".
SCP
SCP translates the
number
IDP ("356")
Forwarding is
initiated
(e.g.. no reply)
VLR
HLR
Script
FTN-NRy = "356"
TIF-CSI is active
CON("+31.161.249911")
VMSC
GMSC
Call is forwarded to
the office
(+31.161.249911)
Slide Number 57
Call enters
GMSC
Call is routed to VMSC
Short FTNs - the principles

Subscriber needs TIF-CSI in HLR in order to register a short
FTN; HLR skips certain FTN validity checks.
Short FTN may be sent down to VLR or GMSC which
supports CAMEL Phase 2 or higher; VLR skips certain FTN
validity checks.
Short FTN is used in conjunction with O-CSI; CAMEL
translates the Short FTN to an E.164 compliant number.
Short FTN may be used in HPLMN and in VPLMN.
Short FTN may be sent to GMSC in ORLCF handling;
GMSC shall support CAMEL Phase 2.
Slide Number 58
Part VI - CAMEL Subscription Information

CAMEL Phase 1
Originating CSI (O-CSI)

Terminating CSI (T-CSI)
CAMEL Phase 2
Translation Information Flag CSI (TIF-CSI)

Supplementary Services-CSI (SS-CSI)
USSD-CSI (U-CSI)
CAMEL Phase 3
Slide Number 59
Dialed Services-CSI (D-CSI)

Short Message Service-CSI (SMS-CSI)
GPRS-CSI
Mobility Management-CSI (M-CSI)
Location Update
CAMEL subscription information distribution
O-CSI
Ho me Ne two rk
SS-CSI
(TIF-CSI)
IPLMN
MAP
HLR
O-CSI
SS-CSI
(TIF-CSI)
HPLMN
Insert Subscriber Data

Location Update
MAP
VLR
GMS C
Incoming line
Forwa rde d le g
Roa ming le g
O-CSI
SS-CSI
(TIF-CSI)
MS C
Slide Number 60
MS
TIF-CSI is supported in
CAMEL Phase 2, GSM R98
VPLMN
Vis ite d Ne two rk
Subscriber enters other PLMN

Interrogation
CAMEL subscription information distribution
Ho me Ne two rk
IPLMN
GMSC requests routing

info from HLR
(MT call)
Mobile Terminating
Call
HPLMN
VPLMN
MAP
Send Routing Info
O-CSI
T-CSI
Forwa rde d le g
Slide Number 61
Send Routing Info

MAP acknowledgement
GMS C
Incoming line
HLR may
suppress T-CSI
when subscriber
is in the Home
Network.
HLR
O-CSI
T-CSI
VLR
Roa ming le g
O-CSI
T-CSI
MS C
MS
Vis ite d Ne two rk
Stationary CAMEL subscription information

Ho me Ne two rk
HLR
IPLMN
MAP
TIF-CSI (CAMEL Phase 2)

U-CSI (CAMEL Phase 2)
UG-CSI (CAMEL Phase 2)
HPLMN
VPLMN
MAP
VLR
GMS C
Incoming line
Forwa rde d le g
Slide Number 62
Roa ming le g
MS C
MS
Vis ite d Ne two rk
CAMEL Capability Handling

(example scenario - Location Update)
Subscriber has:
HLR shall not send

CAMEL Phase 2
O-CSI to this VLR.
CAMEL Phase 2 O-CSI
HLR
CAMEL Phase 1 O-CSI

SS-CSI
HPLMN
VPLMN
IPLMN
LU (MAP)
VLR supports CAMEL Phase 1
VLR
O-CSI
VMSC
HPLMN operator shall ensure that the
SCP supports the CAMEL Phases
indicated in O-CSI.
GMSC
MS enters VLR Service Area

Slide Number 63
CAMEL Capability Handling

(example scenario - Interrogation)
Subscriber has:
CAMEL Phase 2 O-CSI
CAMEL Phase 1 O-CSI
HLR shall not send

CAMEL Phase 2 O-CSI/
T-CSI to this GMSC.
HLR
CAMEL Phase 2 T-CSI

CAMEL Phase 1 T-CSI
HPLMN
SRI (MAP)
VPLMN
GMSC supports CAMEL Phase 1
VLR
VMSC
IPLMN
O-CSI/
T-CSI
GMSC
Terminating Call arrives
Slide Number 64
Contents of O-CSI
(for MO and forwarding services)
! gsmSCF Address - to address the SCP in the HPLMN
! Service Key - to identify the Service Logic in the SCP
! TDP List - to indicate which events may lead to triggering - only DP
Collected Info is allowed
! Default Call Handling - indication to continue or release the call in the
case of IN dialogue error
! CAMEL Capability Handling - requested CAP protocol version for the
IN dialogue
! Conditional Triggers - to identify when triggering shall take place
(CAMEL Phase 2 only)
Slide Number 65
Contents of T-CSI
(for MT services)
! Service Key - to identify the Service Logic in the SCP
! TDP List - to indicate which events may lead to triggering - only DP
Terminating Attempt Authorized is allowed
! Default Call Handling - indication to continue or release the call in the
case of IN dialogue error
! CAMEL Capability Handling - requested CAP protocol version for the
IN dialogue
! Conditional Triggers - to identify when triggering shall take place
(CAMEL Phase 2 only)
Slide Number 66
Contents of SS-CSI (CAMEL Phase 2)

(for supplementary service invocation notification
! List with SS codes
the following SS codes are allowed:
- Call Deflection (CD)
- Explicit Call Transfer (ECT)
- Multi Party (MPTY)
Slide Number 67
Contents of U-CSI/UG-CSI (CAMEL Phase 2)

(for unstructured supplementary service data)
U-CSI/UG-CSI consists of a list of pairs of the following items:
! Service Code - to identify the USSD Service
U-CSI is subscriber specific
UG-CSI is generic per PLMN
Slide Number 68
Part VII - CAMEL Standard Evolution Path
CAMEL Phase 1 (GSM R96) >

CAMEL Phase 2 (GSM R97/R98) >
CAMEL Phase 3 (GSM R99) >
...
Slide Number 69
CAMEL Phase 1 - Service Overview

(not exhaustive)
! Number Translation
! Outgoing Call Filtering/Barring
! Virtual Private Network
! Location Dependent Services
! Call re-routing
! Real-distance charging
Slide Number 70

(not exhaustive)
! Pre-paid calls for roaming subscribers
(mobile originating, terminating and forwarded calls)
! Advice-of-charge (mobile originating calls)
! Short Forwarded-to-Numbers (VPN)
! User Interaction
! Supplementary Service Invocation Notification (Fraud
Detection)
! Conditional Service Triggering
! Home network interaction with USSD
Slide Number 71

(not exhaustive)
! CAMEL control of GPRS (e.g.. pre-paid GPRS)
! CAMEL control of MO SMS (e.g. pre-paid SMS)
! Mobility Management (e.g.. for Private Number)
! Location Services
! Dialed Services (multiple service keys)
! Dynamic CAMEL Trigger Management
! MT Advice-of-Charge
Slide Number 72
CAMEL Standards Overview

GSM Release
GSM R96
GSM R97
GSM R98
Year
1996
1997
1998
Org.
ETSI
ETSI
ETSI
CAMEL Version
CAMEL Phase 1
CAMEL Phase 2
CAMEL Phase 2
(enhanced)
GSM R99
1999
3GPP
CAMEL Phase 3
ETSI GSM and 3GPP 3G specifications may be obtained from

www.3gpp.org
Slide Number 73
GSM CAMEL Standards Specifications

(not exhaustive)
GSM TS
02.78
03.78
09.78
3G TS
22.078
23.078
29.078
Title
CAMEL Service Requirements
CAMEL Technical Implementation
CAMEL Application Part (CAP)
03.08
03.16
03.18
09.02
23.008
23.016
23.018
29.002
Organization of subscriber data

Subscriber Data Management
Basic Call Handling
Mobile Application Part (MAP)
GSM CAMEL TS: for GSM R96, R97, R98

3G CAMEL TS: for GSM R99
Slide Number 74
Signaling for CAMEL
Contents
CAP/MAP Signaling Principles
CAP Signaling over Signaling System 7
CAP Signaling over IP
SCP Load Sharing
SSN Usage
Slide Number 75
CAP Signaling Principles

!
!
!
!
!
!
!
CAP runs over SS7 (CCITT/ITU-T)

CAP requires White TCAP (AC required)
CAP may use White SCCP or Blue SCCP (possible data loss
when using Blue SCCP)
No requirements on MTP
CAP uses SSN = 146 (transition from old CAP SSN 5 to new CAP
SSN 146)
gsmSCF Address is encoded as Global Title (for cross-PLMN
boundary signaling)
Global Title is translated to Signaling Point Code (SPC) + (local)
SSN
Slide Number 76
MAP Signaling Principles

!
!
!
!
!
!
!
MAP runs over SS7 (CCITT/ITU-T)

MAP version 3 is required for transport of CAMEL triggers
MAP may use White TCAP or Blue TCAP (default AC used in
the case of Blue TCAP)
MAP may use White SCCP or Blue SCCP (message
segmentation may be needed in the case of Blue SCCP)
No requirements on MTP
MAP entities have dedicated SSN (specified in 03.03 / 23.003)
SCF uses SSN=147 for MAP signaling (old SSN = 5)
Slide Number 77
CAP Signaling over Signaling System 7

CAP Signaling Entity
Transaction Capability Application Part
Signaling Connection Control Part
Message Transfer Part
Physical Network
...
...
...
MSC/VLR
gsmSSF
But what lies ahead of us...
Service
gsmSCF
Signaling
TCAP
SCCP
MTP
MSC/VLR
Slide Number 78
SCCP
MTP
TCAP
SCCP
MTP
STP
SCP
CAP Signaling over IP

(GSM Release R00)
Also for MAP and other signaling protocols
...
...
...
MSC/VLR
gsmSSF
TCAP
SCCP
Service
gsmSCF
No impact on TCAP and

SCCP
TCAP
SCCP
--- IP --MSC/VLR
Slide Number 79
SCP
Sub System Number (SSN) Usage

Each functional entity has a dedicated SSN
SSF
SSN=
146
SCF
SCF
(CAP)
(MAP)
SSN=
146
SSN= SSN=6
147
HLR
VLR MSC
SSN=7
SSN=8
EIR
SSN=9
SSN Analysis...
Entity is selected, but...
clash of SSNs...SSN is used to address a functional entity

Possible Solutions...
MSC/SSF
Slide Number 80
IDP (SSN = 146)
AC Analysis
SSF uses different SSN

CAMEL Overview LZU 108 5718

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CAMEL Overview LZU 108 5718

Transféré par

Droits d'auteur :

Formats disponibles

CAMEL Overview

LZU 108 5718

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

CAMEL Phase 1 and 2

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

CAMEL Phase 1 and 2

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

Customized Applications for Mobile networks Enhanced

The ETSI GSM Releases

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

Customized Applications for Mobile networks Enhanced

The 3GPP 3G Core Network Releases

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

Mobile Call Cases

Special CAMEL Features

CAMEL Subscription Information

CAMEL Standard Evolution Path

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

Part I - CAMEL Phase 1

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

GSM Network - overview

- Subscribers are registered in HPLMN

Calls terminate in interrogating

Subscribers may roam in VPLMNs

GSM Network - overview (protocol overview)

MSC & GMSC may be co-located

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

GSM Call Forwarding (1)

Call Forwarding Unconditional

Call Forwarding on Not-reachable

Call Forwarding on Busy

Call Forwarding on No-Answer

CAMEL interacts with all Forwarding Categories.

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

GSM Call Forwarding (2)

!Early Call Forwarding:

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

GSM Call Forwarding (3)

!Early Call Forwarding occurs in the GMSC/HLR

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

Service Switching Function

Service Switching Function

Service Control Point

HPLMN may contain

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

For the CAMEL standard: all nodes are referred to as "SCP".

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

CAP = CAMEL Application Part

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

CAMEL/GSM BCSM Principles (1)

Call handling is specified in GSM TS 03.18 ("Basic Call

For every Mobile Originating Call or Mobile Forwarded Call, an

For every Mobile Terminating Call, an instance of a T-BCSM is

CAMEL Phase 1, Phase 2, Phase 3 and Phase 4 have different

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

CAMEL/GSM BCSM Principles (2)

Trigger Detection Point (TDP). A TDP that may be statically

Event Detection Point Notify (EDP-N): An EDP-N may be

Event Detection Point Interrupt (EDP-R): An EDP-R may be

CAMEL Phase 1& 2 1/03813 LZU 108 5718 Rev. PA1

CAMEL Phase 1 O-BCSM

O_Null & Autho ris e _Orig inatio n_

Analys e , Ro uting & Ale rting