Introduction to IN/CAMEL

Subhabrata Biswas

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Contents

Evolution of call handling

Routing table
Call model
ISUP pros and cons
Introduction to IN
Introduction to CAMEL

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Evolution of Call Handling

Wireline phones

Analog phones, exchanges

Digital phones, exchanges
ISDN, ISUP, TUP
VoIP

Wireless phones
Digital exchanges
ISUP, ISDN, R2MF, TUP
VoIP

Applications outside the exchanges

ISUP, TUP, ISDN, R2MF
Expensive, non-optimized resource usage

IN
Vendor specific versions

CAMEL
Used in GSM networks

WIN
Used in CDMA networks
Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Routing Table

How does a switch know if a call

Should be sent to MTNL (local fixed line)
Should be sent to VSNL (international
calls)
Should be completed within the network

Routing table
Numbering plan analysis
Digit analysis
Left to right analysis and resolution

Route selection
Trunk selection
Circuit selection

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Call Routing Logical View

Switch

Voice trunks

Voice trunks
Signaling
channel

Signaling
channel

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Call Model

MO call model

Pre-paid/post-paid
Roaming/local subscriber
Call capability check
Profile check
Value added applications

MO

MT call model

Roaming/non-roaming
Pre-paid/post-paid
Profile check
Call capability check
Value added applications

Routing decisions
Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

MT

Value Added Services: ISUP Solution

Simple routing table based

decisions do not suffice
Routing decisions need to be
externalized

Channel dissociated signaling

(ISUP loopback)
Real-time integration with VAS
Service node based pre-paid
SC, SCA, CLI, OR for inbound
roamers
Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

ISUP Loopback Logical View

Switch

Voice trunks

Voice trunks
Signaling
channel

Signaling
channel
Signaling
channel

Voice trunks

Value Added Service

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Signaling
channel

ISUP Pros and Cons

Pros
Supports standardized application level
signaling
Wide acceptance

Cons

HPMN
Application

Signal and voice trunks go together

Voice trunks are expensive
Require special hardware
Circuit dedicated for the duration of a call

Difficult to have centralized application

server within a network
Requires ISUP circuits from every switch
Requires reconfiguration of every switch

Impractical to use across networks for

value added applications
Works on the principle of Hop-by-Hop

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

ISUP?
Not practical.

Switch
VPMN

Introducing IN
Fundamental requirements
Application should be able to control call progress
Application should be notified of call progress
Application should be able to interact with call
participants for better service
Application does not need voice trunks all the time
Application can be hosted on one or more computers
in a network
Application can be in a different network

SCCP provides more suitable addressing

mechanisms
TCAP provides context handling
A new protocol - Intelligent Networking (IN) is
born

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

The Essence of IN
Traditional Way

Intelligent Way
Introduce a new Feature

Fixed

Services

Fixed

Cellular

Introduce a new
Feature

Roamware Proprietary and Confidential

Cellular

Copyright Roamware Inc. 2003. All Rights Reserved.

IN Basics
Service Switching Point (SSP) uses the help
of Service Control Point (SCP) for making call
handling decisions
A switch is an SSP
An application, e.g. a pre-paid system, is an SCP

Works on top of SCCP/TCAP

Peer-to-peer messages
Centralized application is possible
Communication across networks is possible

No voice trunks involved

Reduces cost of solution

Configuration done on every switch (SSP)

Pre-defined points in call model where an IN
message can be exchanged
Known as Detection Points (DP)

MO and MT call models are handled differently

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Call Routing and IN

Switch

Voice trunks

Voice trunks
Signaling
channel

Signaling
channel
IN Messages

Value Added Service

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Detection Points
DP #

What it means

DP #

What it means

DP 1

Origination attempt authorized

DP 12

Termination attempt authorized

DP 2

Collected information

DP 3

Analyzed information

DP 4

Route select failure

DP 5

O-Called party busy

DP 13

T-Called party busy

DP 6

O-No answer

DP 14

T-No answer

DP 7

O-Answer

DP 15

T-Answer

DP 8

O-Mid call

DP 16

T-Mid call

DP 9

O-Disconnect

DP 17

T-Disconnect

DP 10

O-Abandon

DP 18

T-Abandon

The provision of Detection Points (DPs) is required in the ISUP basic call
handling in order to access IN functionality and to allow IN service logic
influence the processing of IN calls. The detection points (DPs) indicate
points in call (PICs) at which transfer of control can occur.

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

IN Message Sequence Chart

Call initiated. SSP needs to
consult SCP for call control
decision.
SCP asks SSP to keep it
informed of call status events.
SCP asks SSP to continue
processing the call normally.
SSP says that the B party did
not answer the call.
SCP asks SSP to keep it
informed of call status events.
SCP asks SSP to connect the
call to an alternate number.
SSP informs SCP that the B
party has answered the call.
SSP informs SCP that B party
has hung up the phone.
Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

IN: Pros and Cons

Pros
Protocol on top of SCCP
Very lightweight in terms of signaling

Does not necessitate voice trunks for application

invocation
Reduced cost of solution

Can use IVR (Intelligent Peripheral or IP) for

interactive applications
Enables centralized applications
Pre-paid systems moved to IN quickly

Enables communication across operators

Pre-paid roaming should have benefited from this

Cons
ETSI standard has not been used widely
Too many vendor specific protocols/versions
Made communication across operators impossible

Requires configuration on every SSP (or switch)

High OAMP overhead
Pre-paid roaming becomes cumbersome (and actually
never gained acceptance)

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Introducing CAMEL

CAMEL Customized Application for

Mobile Enhanced Logic
Builds on the concepts of IN
Works on SCCP/TCAP
Has the same Detection Points

Addresses the shortcomings of IN

Standardized in the whole GSM world
No vendor specific specification/version
Does not require configuration on every SSP
for MO call model
Imports CAMEL Subscription Information (CSI)
from HLR

Evolving protocol
Every version is called a phase
Networks worldwide are at different phases
Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

MO Call Handling with CAMEL

CSI for MO activity (o-CSI) are transferred to VLR in MAPUPDATE-LOCATION transaction from the HLR
Calls are supported in all phases
Call forwarding supported in CAMEL phase 2
SMS supported in CAMEL phase 3

SSP uses this CSI to consult SCP during MO activities

No static configuration required on SSP for MO activities
Enables multiple SSP-s in a network very easily

CSI contains the Global Title of the SCP

Can contain HPMN global title
Can work across operators

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

MO Call Handling with CAMEL Visualization

A Party

Update Location Txn

SSP

(Includes o-CSI data)

VLR

HLR
GMSC
Initial DP

RRB / CONTINUE
SCP

VPMN

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

HPMN

B Party

MT Call Handling with CAMEL

GMSC is configured to obtain CSI for MT calls (tCSI) from HLR

SSP uses the CSI data to interact with the SCP
No static configuration required in the SSP
Makes it easy to roll out services

MT calls are usually handled in the HPMN only

No need for interaction between operators for MT calls

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

MT Call Handling with CAMEL Visualization

)
ssed
e
r
p
p
o t su
n
I
S
t-C
SRI (
D ata
t-CSI

HLR

GMSC
RR
B

In
iti

/C

ON

TI

al

NU

DP

HPMN

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

SCP

B Party

CAMEL: Pros and Cons

Pros
Protocol on top of SCCP
Very lightweight in terms of signaling

Does not necessitate voice trunks for

application invocation
Reduced cost of solution

Can use IVR (Intelligent Peripheral or IP) for

interactive applications
Enables centralized applications
Enables communication across operators
Pre-paid roaming with MO service has been
possible because of CAMEL

Cons
Requires CAMEL roaming relationship between
operators
Adoption is very slow
CAMEL phase 3 has been adopted by a handful
of operators

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Networks Today

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Questions?

CAMEL Specifications: 3GPP 29002, 23078, 29078

ETSI INAP Specification: Q12*
Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.

Thank you!

For more information:

Email : subhabrata.biswas@roamware.com

Roamware Proprietary and Confidential

Copyright Roamware Inc. 2003. All Rights Reserved.