Ollikainen 230402

CAMEL Phase 3 in UMTS
Author: Sami Ollikainen,

sami.ollikainen@nokia.com
Supervisor: Professor Jorma Jormakka
Master’s Thesis made for Nokia Networks
1 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

Contents
• Introduction
• Pres entation of tools and methods
• R eview of previous res earch
• R es ults
• Own contribution
• Conclus ions

Introduction - B ackground
• When moving from 2G to 3G mobile networks ,
lots of new s ervices are introduced
• In 2G world, the main technique for controlling
s ervices has been IN, Intelligent Networks
(CAME L, Cus tomized Applications for Mobile
network E nhanced Logic)
• IN has many drawbacks and limitations
• S ervices evolution -> S ervice control evolution
• T hus , in 3G world, there s hall be two main
techniques for s ervice creation and control: IN
and open APIs (Application Programming
Interface) between s ervice and network layer
Introduction - S tudy objectives
T he following 4 s tudy objectives are defined:
• T o examine the evolution of s ervice control, when moving
from 2G to 3G world
• T o find out IN evolution s cenarios and what role IN plays
in future mobile networks
• T o repres ent the network architecture for lates t CAME L
Phas e (Phas e 3), examine CAME L protocol (CAP)
interfaces in more detail and s how as an example of how
Prepaid s ervice (PPS ) is implemented by the help of
CAME L3 in 3GPP R eleas e 1999 (R 99) compliant UMT S
network
• T o examine, how can CAME L3 core network s ignalling
utilize open APIs (and vice vers a)
P res entation of T ools and Methods
• A literature s tudy was chos en as a res earch
method
• Us ed literature:
• public 3GPP s tandards (es pecially CAME L-s tandards
23.078 and 22.078)
• public res earch papers (IE E E Communications
Magazine, BT T echnology Journal, UMT S F orum
R eports etc)
• non-public Nokia Networks ’s technical documentation

R eview of P revious R es earch
• UT MS S tandardization within 3GPP

• CAME L S tandardization within 3GPP
• 3GPP R 99 Architecture
• CAME L and S ervice Control in UMT S

UMT S S tandardization within
3GP P

3GP P Domains and S ubs ys tems
Circuit Switched Services

Core Network Domain Subsystem
•Location server
•Application server
MSC MSC HLR •WAP gateway
Server •etc.
Packet Switched Internet Multimedia

Core Network Domain Core Network Subsystem
•Border GW
•Firewall
SGSN GGSN HLR •LIG CPS MGW HSS
SOURCE: [Vei00]
CAME L S tandardization within
3GP P

Why CAME L ?
• Limitations in IN bas ed on E T S I Core INAP CS 1
No mobile functionality (only vendor s pecific extens ions )
T oo much room for interpretations (multivendor s ys tem is difficult)
• Need for
"IN" s upporting mobile terminals
S ervices not covered by s tandardis ed GS M s ervices
S ervices for s ubs cribers roaming outs ide the HPLMN
E as ier multivendor interaction
• T he S tandardis ation res ult was
Cus tomis ed Applications for Mobile network

E nhanced L ogic
10
or jus t CAME L
© HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl
What is CAME L ? (1/2)
• Animal
• IN network technology
for mobile networks
• Etc
SERVICES
in SCP
Home PLMN /
CAMEL HLR
Visited PLMN/
Subscription Info
MSC, VLR, SGSN (CSI)

What is CAME L ? (2/2)
Table 4. CAMEL Application Areas. • CAME L is an IN technology by
the help of which value-added
CAMEL Application Subareas Affected Affected 3GPP Used
Area Core Standards Protocols with
Domain (other than
CAMEL
CAMEL
s ervices can be offered to the
standards)
mobile s ubs cribers roaming in
Circuit Switched Call
Control
• MO call CS 23.018; 23.072,
23.081, 23.082,
CAP, MAP
HPLMN or VPLMN
• MT call 23.083, 23.084,
• MF call
23.085, 23.086,
23.087, 23.088, • CAME L integrates IN
23.091, 23.093,
23.135, 23.079
techniques from fixed to mobile
GPRS Interworking • GPRS PS 23.060, 32.015 CAP, MAP network
Session
• PDP
• CAME L is bas ed on E T S I'
s
Context
Core Intelligent Network
Short Message Service MO-SMS Both 23.040 CAP, MAP
Application Part (INAP) and
Supplementary Service
Invocation
- CS 23.011, 23.091,
23.084, 23.072,
MAP
Mobile Application Part (MAP)
23.093
protocols
USSD - CS 23.090 MAP • CAME L is being developed in
Mobility Management - CS 23.018 MAP Phas es (Phas es 1-3; Phas e 4
Control and HLR – SCP CS, PS 23.008, 23.016 MAP s tandardization work was
s tarted in autumn 2000)
Interrogation of interface
Subscription Data
• Main CAME L s tandards

Subscriber State and MSC-GMLC CS 23.016, 23.127 MAP
Location Retrieval interface

(3GPP) are 22.078, 23.078 and
29.078
CAME L His tory: S tandardization in
P has es
Table 6. Comparison between different CAMEL Phases.
CAMEL Phase Phase 1 Phase 2 Phase 3
3GPP Domain CS CS CS, PS

affected
• Phas es 1-2 for Circuit
Phase
Characteristics
• Applicable to MO
and MT calls
• Charging
operations
• GPRS charging
operations S witched (CS ) Core
• No charging
operations
• New Call related
Detection Points
• MO-SMS
charging
Domain
• Phas e 3 for both CS and
operations
• No • SS invocation
announcements notification • Dialled services
• Limited Detection • Announcements

(D-CSI, N-CSI)
Packet S witched (PS ) Core
Points and tones • SCP-HLR
interface Domains
• DTMF reception
• USSD between
• SCP control of
CW, CF and • Phas e 4 for IP Multimedia
S ubs ys tem (IMS ); not
SCP and phone MPTY
• Mobility
Management
functions
dis cus s ed within this M.S c.
Service • Call Screenings • Prepaid • GPRS Prepaid T hes is
Examples
•
•
Call Forwardings
Call Redirections
•
•
Hunting
Announcements
• Enhancement of
CS Prepaid • T able is bas ed on [Pal00]
• Service numbers
• Call Routings • Freephone
• Multiple
• Very simple VPN • Premium Rate Subscriber Profile
• Personal
Discount
• Location
Dependent
Discount
• Reverse
Charging

CAME L P has e negotiation -
requirements
• A network s upporting CAME L2 mus t als o s upport
CAME L1.
• A network s upporting CAME L3 mus t als o s upport
CAME L2 & CAME L1.
• CAME L4 s hall provide the functionality of all
previous CAME L Phas es . Phas e 4 network
s ignalling s hall s upport interworking with CAME L
Phas es 3 and 2.
• CAME L3 is the lowes t phas e for S GS N.

CAME L P has e negotiation - 2G/3G
is s ues
• All CAME L phas es work in 2G and 3G.
• CAME L1 and CAME L2 Location Information contains a Cell-
id parameter which contains the GS M cell or UMT S S ervice
Area Identity (S AI).
• S tarting from CAME L3 an additional parameter indicates
whether Cell-id contains actually S AI.
• 3G has higher data rates in CS and PS .
T he CS Bearer Capability (BCIE ) is indicated to S CP.
Inter-s ys tem CS handover is not vis ible to the S CP, nor
change of us er rate.
T he PS QoS and change if QoS are indicated to the S CP.
Inter-s ys tem PS R AU is vis ible to the S CP.
• CS Multicall feature us age is s een as multible independent
calls in the S CP.
S OUR CE : [Pal00]
UMT S S ervices by UMT S F orum UMTS Forum Report No. 9 Service Categories
Mobile Multimedia
Mobile Location Rich Voice
Intranet/ Customised Messaging
Internet Based and Simple
Extranet Infotainment Service
Access Service Voice
Access (MMS)
• R eports No. 9 and No.

UMTS Service Concepts and Applications
13 introduce 6 UMT S
Entertainment Information Services S ervice Categories
Downloadable Ring Tones / Graphics Alerts
• E ach s ingle
Entertainment Dictionary Research
Internet Games Directories
Mobile Music Emergency Services (911)
Flight Reservation
s ervice/application
Online Dating
Online Gambling Info Services
Instant Weather Forecast
M-information (user statistics)
belongs to s everal
Multimedia (video/audio real-time)
Financial Services Personal Information Management (PIM)
Restaurant Guide
Financial Services Town Page (Yellow Page)
S ervice Categories
Financial/Banking (E-cash) Virtual Home Environment (VHE)
Mobile Cash
Mobile E-Bill
Mobile E-Salary
(not s hown in the

Stock Trading
Mobile Commerce
Advertising
F igure, bas ed on
B2B Business Data Applications
Conferencing
eWallets & Shopping Enhancements
Just The Ticket
Mobile Video (Streaming) M-Commerce Transactions
[Umt01])
Mobile Videotelephony ME Commerce
Simple Voice Micro-Payments
Teen Video Chat (Non Real-Time) Mobile Retailing
Video Conferencing Transaction Processing
Voice over IP (VoIP)
Voice Portal
Voice-Activation Messaging
E-mail / Messaging
Internet Access / Networking E-mail Receipt (100 letters)
E-mail Transfer (100 letters)
Instant Messaging / Message Aggregation
Application Synchronization Machine-to-Machine
FTP Transfers Mobile Chat (Non Real-Time)
Internet Mobile Instant Messaging (MIM)
Intranet Mobile Postcard
Mobile VPN Multimedia Messaging
Web Browsing Short Message Service (SMS)
Streaming Audio/Video (Non-Real Time)
Unified Messaging
Location Based Services

Car Navigation
Localised Info (Current User Location)
Localised Info (Future/Planned Location)
Location Sensitive (Billing/Routing)
Location Based M-Commerce
Navigation/Location
Telematics
Tracking/Personal Security
Virtual Mouse/Directional Wand

CAME L Control of 3G S ervices
Table 7. 3G services requiring possibly CAMEL Control. • UMT S s ervices can
Service
Category
Name of Service
be categoris ed into 4
different groups :
Basic Services Speech, emergency calls, low bit rate data, medium bit rate data, high
bit rate data, high quality audio, low bandwidth video, high bandwith • Bas ic
video
Supplementary Operator determined barring, user defined barring, call screening, call
• S upplementary
Services deflection, call forwarding unconditional, call forwarding on busy (no
reply and not reachable), call waiting, call hold, call transfer, calling
• Operator S pecific
number identification presentation/restriction, connected number
identification presentation/restriction, multiple subscriber profile,
• Multimedia
multi-party, call completion services (e.g. CCBS), closed user group,
advice of charge, calling name presentation • CAME L control can
be us ed with many
Short number dialling, prepaid, VPN
s ervices
Operator
Specific
Services
• T able is bas ed on
Other Services Lawful interception, voice group-call service, voice broadcast
service, SMS, fax, ASCI, MExE, location services, SoLSA
[21978]

P P S P enetration in S elected Countries
100 %
• Prepaid S ervice (PPS ) can
90 %
Italy
be implemented in multiple
ways
80 %
Mexico
• PPS allows a mobile
70 % s ubs criber to pay for
India
telecommunication
Penetration (%)
Germany
60 %
s ervices before the actual
50 % WORLD us age, i.e. in advance
China P.R. • PPS s ubs criber
es tablis hes a prepaid
40 %
30 % account with the s ervice

USA
provider for acces s ing
20 % telecom s ervices
10 %
Japan • IN Bas ed Prepaid is jus t
one type of Prepaid
• F igure is bas ed on [Lil01]
0%
1996 1997 1998 1999 2000 2001 2002 2003 2004 2005
Year
3GP P R 99 Architecture

R 99 UMT S Network Architecture
• Mobile T erminal
• R adio Acces s
HLR • 2G R AN - BS S
BSC
PSTN/ISDN
3G MSC Transit MSC • 3G R AN - UT R AN
A
GSM SS7
• Core Network
RNC
Iu-CS Other PLMN • Circuit S witched
Core Network
APSE Domain
WCDMA IN/SCE
Iu-PS
External
• Packet S witched
IP net works Core Network
Domain
3G SGSN
• S ervices and
IP
Backbone
GGSN
Management
S ubs ys tem (e.g.
IN/S CE )
• F igure is bas ed on
[Net01b]
3GP P R 99 UMT S S ervice Architecture
• In the 3GPP R 99
UMT S network,
S S 7 s ignalling is
APPSE - Application Server
heavily us ed for
SCE - Service Creation and Execution
APPSE Content Portal
Platform
s ervice control
server
Service Provider Application plane

• T wo main
alternatives for
Network Operator SCE APPSE s ervice creation
Application plane and control:
Radio
Access GGSN
• IN
HLR SGSN
MSC • OS A/Parlay
CS & PS Core Domains API
• IN s ervices are
SGSN
Routr SS7 Backbone
SS7 backbone created in S CE (IN
S IBs ); IN S ervice
Platform
• OS A s ervices are
Control
created in
APPS E s (XML,
Java s ervlets )
21 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl • F igure is bas ed on
[Vei00]
CAME L and S ervice Control in
UMT S

Virtual Home E nvironment (1/2)
• Virtual Home E nvironment
(VHE , s ee F igure) is
Home Network
HLR
defined as a concept for
Service Creation Environment Pers onal S ervice
Service Management E nvironment (PS E )
Service Data
Service portability acros s network
Control
boundaries and between
Serving Network
SSF Screening VLR terminals . T he concept of
the VHE is s uch that us ers
are cons is tently pres ented
Terminal
MExE Client MS
IC Card
SIM Toolkit
SIM
with the s ame
pers onalized features ,
Us er Interface
SOURCE: [Hum98]
cus tomis ation and

s ervices in whatever
network and whatever
terminal (within the
capabilities of the terminal
Virtual Home E nvironment (2/2)
• IN and CAME L are
independent
Service concepts from
Profile
Virtual Home
QoS (end-to-
Subscriptions
end) E nvironment
(VHE )
User Profile VHE • In practice, VHE
User Location
Logic
can be
implemented with
Terminal
Capabilities
Seamless CAME L
Roaming
Network • F igure is bas ed on
Capabilities
[Baz01]

VHE with OS A in R 99 UMT S network
Service layer
• CAME L (CAME L
Application Servers s erver, CS E ) is a
Service ... Service ... Service ... Service ... part of the VHE /OS A
architecture
Standardized
OSA
interfaces • T he main goal of
Network layer
VHE /OS A concepts
SCF SCF SCF SCF SCF
is to enable s ervice
UMTS call
control servers
HLR
CAMEL server
(CSE)
MExE server SAT server
development
24.08 MAP CAP WAP SAT independently of the
Transport network underlying networks
• T he interface
between s ervice and
network layer is
Service Capability Server (SCS)
s tandardized ->
SCF Service Capability Feature (SCF)
S OUR CE :
[Bos 01] s ervice creation
becomes fas ter,
eas ier and more
3G S ervice Creation with OS A
service creation environment (operator)
service platforms network capabilities
• Open S ervice
e.g.
- messaging
e.g.
- telephony Architecture (OS A)
Capabilities may be
- SMS - data
- location - supplementary
services
meant for terminal-

- CAMEL
Network
APIs
open interface (network/server-centric applications)
or network-centric
network operator products 3rd party products
applications
• T erminal vs .
new 3G products, e.g. created by service
- video clip download integrators:
- interactive games - content providers,
Network Centric
- application providers etc.
existing 2G products for circuit and
packet-data calls
Capabilities (OS A
open interface (terminal-centric applications) S CS s )
• F igure is bas ed on
[Har01a]
terminal capabilities
e.g.
service personalization - USAT
environment (customer) - MExE
- Web browser
- Operating System

IN Architecture Model
• IN Conceptional Model
(INCM) gives a
framework concerning
how network
SMF SMAF
intelligence is provided
and dis tributed within a
SCEF certain network
• INCM cons is ts of four
SDF
SCF
planes :
SRF
• S ervice
• Global F unctional
SSF SSF
• Dis tributed
CCAF CCF CCF CCF CCAF F unctional
• Phys ical
• F igure (bas ed on
[Q1204]) repres ents
Dis tributed F unctional
Plane architecture
Mapping between INCM and commercial
IN
• IN functionality is
dis tributed according to
Nokia Intelligent Networks Architecture INCM
• IN S ervice Platform (S CE ,
S CP, S MP, S MAP, IP etc)
SMP SCE
SMAP • S CP (gs mS CF )
• CS Core Domain
Service
Node IP
IP SCP SCP
• VMS C (gs mS S F )
CCB
SSP SS7 -net work SSP • GMS C (gs mS S F )

• HLR
NOKI NOK
A DX200 IA SGSN
CS Core Domain PS Core Doma in
CCB Customer Car e and Billing SMP Service Management Point

• PS Core Domain
SCP Service Control Point
• S GS N (gprs S S F )
SMAP Service Management Access Point
SSP Service Switching Point IP Intelligent Peripheral
SCE Service Creation Environment MSC Mobile Switching Center
NOKIA TELEC OMMUN IC ATIONS
• S S F s and S CF are
needed for CAME L
communication
28 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl • F igure is bas ed on
[Net01c]
IN E volution towards IS MF (1/2)
• T he key requirements for future development of the IN are that cus tomers
can acces s a wider variety of s ervices in a wider variety of ways , and that
they can cus tomize exis ting s ervices or even create new ones as s imply,
quickly, and cos t effectively as pos s ible. [Bre00]
• In practice, due to the key requirements pres ented above, IN s ervice logic
s hould be acces s ible from Internet terminals and contain components
res iding in both S CPs and Internet nodes . In this way, new Mobile Internet
Applications that provide the mutual s upport of network capabilities and
Internet content may be offered to the mobile s ubs cribers . [Bre00, Gre00b]
S OUR CE : [F in00]
PSTN and
traditional
Intelligent
Networks Next-
Hybrid
generation
networks
Internet and Internet networks
data telephony VoP
networks networks
Wireless
and cable Migration path
networks (increased capabilities)

IN E volution towards IS MF (2/2)
• IN mus t evolve towards
Application Servers (APPSEs):
open APIs and Intelligent
é
é
Network Operator
ASP Service Logic
APPLICATION LEVEL: Middleware
é Enterprise Execution Operator Independence
• Intelligent Middleware
External APIs:
é Other 3rd party
JAIN, OSA,
Parlay, PINT,
Spirits, TINA,
cons is ts of an Intelligent
S ervice Mediation F unction
INTELLIGENT SERVICE MEDIATION / MIDDLEWARE
TSAS Trusted Untrusted
Security Control
(IS MF ) that handles the
traffic between s ervice and
Service Level Agreements (QoS Policy Control),
CALL CONTROL LEVEL:
Network Authentication, Discovery, Registration Network + Protocol
Capabilities
API SERVICE CAPABILITIES
Independence
network layer
User Profile Address
• IS MF cons is ts of three
Location Mobility
Management Translation
main parts : S ervice

Call Control Billing User Status Messaging
Resources
API
Protocol Adapters Acces s , S ervice
Capabilities and
CAP
CORE NETWORK SIGNALLING
INAP MExE MAP GTP-C SIP
TRANSPORT LEVEL: T rans port
Vendor Independence
Wireless Wired Data

• Bas ic tas k of IS MF in Next-
Generation Network (NGN)
is to s plit different layers
and functionalities from
each other
• F igure 20 is bas ed on
AP P S E : CAME L bas ed S ervice Control
APPSE APPSE APPSE
SERVICE LAYER
NETWORK LAYER
OSA API
IN Platform
SCP
gsmSCF
gprsSSF gsmSSF ipSSF
SGSN MSC CSCF
F igure is bas ed on [Bos 01]

AP P S E : AP I bas ed S ervice Control
APPSE APPSE APPSE
SERVICE LAYER
NETWORK LAYER
OSA API
ISMF ISMF ISMF
SGSN GGSN CSCF
F igure is bas ed on [Bos 01]

S ize of B us ines s E volution within Value
Chain
• Important revolution occurs in
the s ize of different bus ines s
areas and their importance to
Services Content
Terminal Network Provision Provision
the mobile product value
chain. T he F igure 23 (bas ed
2G: on [Umt00a]) des cribes , how
this change occurs moving
from 2G mobile telecom -like
value chain towards Internet
–like value chain, Multimedia
Value Chain [Umt99]. It
s hows quite clearly that
Content and S ervices
Provis ion have bigger roles ,
whereas core network' s
3G: importance diminis hes , while
intelligence is moving away
from the core network
(Network layer) towards
applications (S ervice layer)
33 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl [Baz01].
P roduct Value Chain E volution (2G->3G)
• In the 3G World, different roles within the Value Chain are
[Har01a]: NO, S P, mobile virtual network operator (MVNO),
mobile Internet s ervice provider (M-IS P), portal (context)
provider, application provider, content provider, payment
proces s ing provider and s ys tem s ecurity provider. T he
F igure below is bas ed on [Har01a].
Content VAS Service Network Mobile

provider provider provider operator customer
Content,
Payment, Application Partial Service MVNO Network Mobile
(M)- ISP
Security provider provider provider operator customer
providers

Wholes aling affects Network Charging
• Wholes aling means ,
in practice, acces s
to 3rd party
Transaction Flows (Who bills whom?) companies from the
network operator' s
1 Service
point of view. T he
Customer
Provider network operator
6
s hould implement
3 this concept at
5 2 Advertiser
every level (e.g.
acces s to fibre,
Transport 4 Content acces s to call
Provider Provider control, acces s to
applications or
S OUR CE : [Umt00b]
provis ion of content
etc.) in order to
utilize core network
35 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl res ources as
efficiently as
2G and 3G World Comparis on
SERVICE CREATION AND MANAGEMENT
• Below are 2G and 3G

Closed 2G World Open 3G World
Worlds compared mainly in
Network side control of 2G
services
Network + Terminal side control
of 3G services; service the context of S ervice
Creation and Management
IN Platform specific service personalization
creation and management: Open service creation and
management environment: Open
(F ig. 26, bas ed on [Dao02,
closed interfaces
IN Platform + operator’s own APIs (JAIN, OSA, Parlay etc.)
mobile portals contains IN plays possibly middleware
application, call control and
transport layers
layer between applications and
transport Umt00c]). It is clearly s een
that the evolution is radical:
Skilled specialists (network Individual services can be
operator personnel) controlled by 3rd party APPSEs
the world becomes from

Long creation time of new (softswitch architecture)
service (years) Anyone can create new services
Network Operator (NO) plays Rapid new service creation times
one role: network provider
Telecom world Value Chain and
Network Operator (NO) has
multiples roles: mobile portal, clos ed voice-centric,
monopoly-like world towards
Business Models mobile ISP, communication
Price and Product: Simple price infrastructure provider
open, IP data-centric world,

structure (airtime) and voice as Internet world -like Value Chain
main product (voice-centric) and Business Models
Price and Product: Complex,
where each market party
Partnerships: Vertical integration
of network infrastructure and service-specific price structures;
device distribution subscriptions, messages,
"Write once, run in one place"
Technologies: CAMEL, WAP,
advertising, airtime, transactions
Partnerships: Strategic mus t co-operate and network
es pecially at horizontal level
USSD, SMS partnerships to emulate end-to-
end integration; Wholesaling
"Write once, run everywhere"
New entire services classes: m-
business, location-based
(horizontal integration)
services, multimedia messaging,
infotainment, edutainment etc. ins tead of the old vertical
type of integration (network
Network reconfiguration; Policy
Based Network Management
operator' s point of view).

New technologies: MExE, USAT,
APIs, VoIP: SIP (not in R99),
SS7 over IP (not in R99),
CORBA, new IETF protocols

R es ults
• CAME L Phas e 3 in 3GPP R 99

CAME L P has e 3 in 3GP P R 99
• CAME L Phas e 3 Architecture

• CAME L3 Operation Principles
• CAME L3 in S GS N
• CAME L3 in MS C
• CAME L3 in S ervice Platform
CAME L P has e 3 Architecture

CAME L 3 Architecture
Home Network HLR MAP gsmSCF
MAP
CAP
MAP CAP MAP CAP gprsSSF

MAP MAP
SGSN
gsmSSF VLR gsmSSF
GMSC Roaming leg VMSC

Incoming line MS
MAP
CAP MO call - Outgoing leg
Forwarded leg
(or Forwarding leg)
Interrogating Network Visited Network
gsmSRF
Home/Interrogating/Visited Network
F igure is bas ed on [23078]

Concepts (1/2)
• CS I CAME L S ubs cription Information - part
of s ubs criber data, which identifies that a
s ubs criber has CAME L s ervice(s ).
• OS S Operator S pecific S ervice (IN s ervice)
• gs mS CF GS M S ervice Control F unction.
• gs mS S F GS M S ervice S withing F unction.
• CAP CAME L Application Part
• HPLMN Home Public Land Mobile Network
• VPLMN Vis ited Public Land Mobile Network
• IPLMN Interrogating Public Land Mobile Network

Concepts (2/2)
• O-BCS MOriginating Bas ic Call S tate Model
• T -BCS M T erminating Bas ic Call S tate Model
• gs mS R F GS M S pecialis ed R es ource F unction.
• US S D Uns tructured S upplementary S ervice Data
• gprs S S F GPR S S ervice S witching F unction
• S GS N S erving GPR S S upport Node

CAME L 3 Operation principles

B as ic CAME L 3 Operation
(P DP Context is us ed as an example)
• CAME L3 operation
UE/UTRAN SGSN SCP GGSN HLR
occurs in different
phas es . T he three main
Attach procedure
Attach Request
phas es are CS I from

Update GPRS Location
Insert Subscriber Data

Attach Accept
PDP Context Activation procedure HLR , E ncountering new

Activate PDP Context Request
Initial DP GPRS Detection Point and
Apply Charging GPRS, FCI GPRS, SCI GPRS, Continue
Create PDP Context Request Continuing/R eleas ing the

Activate PDP Context Accept
Create PDP Context Response
Call. Let' s look at certain
Apply Charging Report GPRS
ACR GPRS Ack, Apply Charging s ignalling procedures , in
this cas e related to the
GPRS, FCI GPRS, SCI GPRS
PDP Context Deactivation procedure
PDP Context. F igure is

Deactivate PDP Context Request
Apply Charging Report GPRS, Event Report GPRS
bas ed on [23060,
ACR GPRS Ack, SCI GPRS, Continue GPRS
Delete PDP Context Request
Deactivate PDP Context Accept

Delete PDP Context Response
23078].
• In addition, S CP can
DATA TRANSFER DURING ACTIVE
GPRS-CSI FROM HLR
PDP CONTEXT + CAP SIGNALLING
L3-MM, L3-SM or
GTP-C SIGNALLING
NEW DP ENCOUNTERED
+ CAP SIGNALLING make inquiries to HLR
44 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl and HLR can update
CS I data in MCS /S GS N.
CAME L S ubs cription Information (CS I)
Table 11. CAMEL Subscription Information elements. Those CSIs that are not sent from
HLR are marked with grey colour.
Name of Description Affected Affected CAMEL SS-CSI Supplementary Service Invocation CS MSC \ 2
CSI Core Network Phase Notification CAMEL Subscription VLR
Domain Element Information (SS-CSI) is transferred to the
VPLMN. SS-CSI is for Supplementary
D-CSI Dialled Services CAMEL Subscription CS MSC \ 3
Services MAP notifications.
Information (D-CSI) is transferred to the VLR,
VPLMN (at Location Update) and IPLMN GMSC T-CSI Terminating CAMEL Subscription CS GMSC 1
(for an incoming call in GMSC). D-CSI is Information (T-CSI) is transferred to the
for HPLMN controlled dialled services.
IPLMN for an incoming call in the GMSC.
N-CSI N-CSI is for VPLMN controlled dialled CS MSC\ 3 T-CSI is for Mobile Terminating calls in
services. VLR the GMSC.
GPRS- GPRS CAMEL Subscription Information PS SGSN 3 TIF-CSI Translation information Flag CAMEL CS MSC \ 2
CSI (GPRS-CSI) is transferred to the VPLMN. Subscription Information (TIF-CSI) is VLR
GPRS-CSI is for control of GPRS transferred to the VPLMN. TIF-CSI is
Sessions and PDP Contexts. used in the HLR for registering short
Forwarded-to-Numbers (FTNs).
M-CSI Mobility Management CAMEL CS MSC \ 3
Subscription Information (M-CSI) is VLR U-CSI USSD CAMEL Subscription Information CS HLR 2
transferred to the VPLMN. M-CSI is for (U-CSI) is held in the HLR; it is not sent to
Mobility Management MAP any other node. U-CSI is for USSD
notifications.
application (for the served subscriber).
O-CSI Originating CAMEL Subscription CS GMSC 1
Information (O-CSI) is transferred to the
UG-CSI USSD General CAMEL Subscription CS HLR 2
VPLMN (at Location Update) and to the Information (UG-CSI) is held in the HLR;
IPLMN (for an incoming call in the it is not sent to any other node. UG-CSI is
GMSC). O-CSI is for Mobile Originating for USSD application (for all
calls (in the VMSC) and Mobile subscribers).
Forwarding calls (in the VMSC and the
GMSC). VT-CSI VMSC Terminating CAMEL Subscription CS MSC \ 3
Information (VT-CSI) is transferred to the VLR
SMS-CSI Short Message Service CAMEL CS, PS SGSN + 3 VPLMN at Location Update. VT-CSI is
Subscription Information (SMS-CSI) is MSC / for Mobile Terminating calls in the
transferred to the VPLMN. SMS-CSI is VLR VMSC.
for controlling Mobile Originating Short
Message submissions.
T able is bas ed on [22078]

CAME L S ubs cription Information (CS I)
content
• T rigger Detection Point (DP2, DP12 etc)
• gs mS CF addres s (Global T itle of the S CP)
• S ervice Key (identifies the s ervice logic in the S CP)
• Default Call/S MS /GPR S Handling (Continue or R eleas e, if
CAP dialogue fails )
• Capability Handling (CAP protocol vers ion, not for MAP
CS Is )
• T rigger criteria (e.g. dialled number, bas ic s ervice, reas on
code etc)
• CS I s tate (active/deactive).
• CS E Notification on CS I change.

CAME L S tate Models
• (Call) S tate Model is the view that the S CP has about the
progres s of a call/s hort mes s age/PDP context etc.
• S tate models cons is t of Detection Points (DP) and Point In
Call (PIC) / Point In As s ociation (PIA). DPs are reported to the
S CP/CS E .
• T rigger Detection Point (T DP-R ) is a detection point in which
CAP dialogue is initiated by the S S F .
• E vent Detection Point (E DP) is reported only if S CP has
armed s o. An E DP can either be armed as :
- E DP-N: DP is reported and proces s ing continues in S S F
automatically.
- E DP-R : DP halts proces s ing in S S F , proces s ing continues
when the S CP s ends down a final ins truction (Continue,
Connect, R eleas e)
CAP over S S 7 s tack
API Interface
S S F Application S W S CP Application S W
CAP CAP
T CAP T CAP
S CCP S CCP
MT P3 MT P3
MT P2 MT P2
LI LI
SSF S CP
F igure is bas ed on [29078]

CAME L 3 in S GS N

CAME L 3 GP R S Attach/Detach S tate
Model
• DP Attach T DP -R
• DP Change Of P os ition GP R S S es s ion
Detached T DP -R , E DP -N
• DP Detach E DP -N, E DP -R
Attach request
Detached AD_Exception
Attach
User- or network initiated
detach
Attached
Intra-SGSN Routeing
Inter SGSNRouteing area
area update
update
Change of Position GPRS session
S OUR CE : [23078]

CAME L 3 P DP Context S tate Model
• DP P DP Context E s tablis hment
T DP -R , E DP -R , E DP -N
Idle
• DP P DP Context E s tablis hment
Acknowledgement
PDP Context T DP -R , E DP -R , E DP -N
Setup Req
PDP Context Est. • DP Change Of P os ition Context
T DP -R , E DP -R , E DP -N
PDP Context PDP_Context_ C_Exception
Disconnection Setup • DP P DP Context Dis connection
PDP Context
E DP -N, E DP -R
Setup Ack.
PDP Context Est. Ack.
User or network PDP_Context_
initiated disc. Established
Routeing area update
Change of Position context
Routeing area update

Change of
Position context
S OUR CE : [23078]

CAME L 3 S tate Model for MO S MS
• DP S MS _Collected_InfoT DP -R
• DP O_S MS _F ailure E DP -N, E DP -R SMS Null & Start &
Authorize
SMS_Exception
• DP O_S MS _S ubmitted E DP -N, E DP -R
DP SMS_Collected_Info
DP O_SMS_Failure
SMS Analyse &

Routing
DP O_SMS_Submitted O_SMS_Exception
S OUR CE : [23078]

CAME L 3 with GP R S Interworking
• In the T able 12 above (bas ed on
Table 12. CAMEL3 effect on GPRS Interworking.
[23060, 23078]) four different
GPRS GPRS Signalling Number of DPs State Models: Type of CAP parameters des cribing CAME L3
Signalling
Area
Procedure encountered Attach/Detach
vs. PDP Context
Dialogue:
Session vs.
effect on the PDP Context are
Context pres ented. At firs t, bas ic GPR S
MM GPRS Attach 1 Attach/Detach Session procedures belong either to
MM GPRS Detach 1 Attach/Detach Session Mobility (GPR S S es s ion) or
SM PDP Context 2 Both Both
S es s ion Management (PDP
Activation Context). T hen, number of DPs
SM PDP Context 1 Both Both among each s ignalling
Modification procedure is pres ented; us ually it
SM PDP Context 2 Both Both varies between 1-3. Next,
Deactivation
affecting S tate Models are given
MM Inter SGSN RAU 2 Both Both
and finally, the type of CAP
MM SRNC Relocation 2 Both Both
dialogue. T he CAP dialogue can
MM Intersystem
change (2G <->
2 Both Both be PDP Context or GPR S
3G) S es s ion s pecific, i.e. individual
PDP Contexts can be controlled
within a group of active Contexts
(per GPR S S es s ion; CAME L
GPR S S cenario 1) or s ingle
bas is (per PDP Context; CAME L
GP R S S es s ion bas ed CAME L Dialogue
Handling
• T wo CAME L S tate Models mus t be implemented:
CAME L GPR S Attach/Detach
CAME L GPR S PDP Context
• CAME L GPR S Control and Interaction per GPR S S es s ion
UE is in "Attached" s tate or goes from "Idle" to "Attached" s tate (during
Attach procedure) when CAME L Interaction, T riggering or Continuing CAP
communication in E DP-R /E DP-N, s tarts
CAME L Interaction with S CP occurs within S es s ion Dialogue
CAME L T riggering occurs once for the whole GPR S S es s ion in the s ame
S GS N
SGSN / SSP SCP
GPRS Dialogue
A/D
SM Information flow related to
the Session
PDP#1
PDP Context #1
PDP#2
PDP Context #2
54 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl S OUR CE : [23078]
P DP Context bas ed CAME L Dialogue
Handling
• S ingle CAME L S tate Model mus t be implemented:
CAME L GPR S PDP Context
• CAME L GPR S Control and T riggering per PDP Context
during GPR S S es s ion
UE always in "Attached" s tate when CAME L
interaction s tarts and ends
All CAME L activities occur within PDP Context
Dialogue
SGSN / SSP SCP
GPRS Dialogue #1
PDP#1
PDP context #1
PDP#2
PDP context #2
GPRS Dialogue #2
55 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl S OUR CE : [23078]
CAP v3 Operations for GP R S
Table 14. The CAP operations for GPRS Interworking.
CAP Operation Direction Purpose
• T he CAP operations
ActivityTestGPRS SCP -> SGSN SCP tests CAP connection.
ActivityTestGPRSAck SGSN -> SCP SGSN acknowledges.
ApplyChargingGPRS SCP -> SGSN SCP sends threshold limits

and tsw (Prepaid). between the S GS N's
ApplyChargingReportGPRS SGSN -> SCP SGSN reports transferred
data and/or elapsed time.
gprs S S F and the S CP' s
ApplyChargingReportGPRSAck SCP -> SGSN SCP acknowledges.
gs mS CF are pres ented in
next page (T able 14, bas ed
CancelGPRS SCP -> SGSN SCP cancels all DPs and
reports.
on [23078, 29078]). As it can

ConnectGPRS SCP -> SGSN SCP gives new APN.
ContinueGPRS SCP -> SGSN SCP orders SGSN to

continue suspended
processing. be s een, the GPR S
EntityReleasedGPRS SGSN -> SCP SGSN informs SCP on
abnormal event in SGSN. Interworking includes 18
EntityReleasedGPRSAck
EventReportGPRS
SCP -> SGSN
SGSN -> SCP

SCP acknowledges.
SGSN informs SCP on DPs

different CAP operations for
encountered.
the CAME L3. T hos e CAP
operations that are s een in
EventReportGPRSAck SCP -> SGSN SCP acknowledges.
FurnishChargingInformationGPRS SCP -> SGSN SCP gives free format
F igures for the IN Bas ed

charging data into CDR.
InitialDPGPRS SGSN -> SCP Establishes CAP connection
Prepaid have been marked

(1st operation).
ReleaseGPRS SCP -> SGSN SCP orders SGSN to release
with grey colour.

GPRS Session and/or PDP
Contexts.
RequestReportGPRSEvent SCP -> SGSN SCP orders SGSN to notify,

when new DP is met.
ResetTimerGPRS SCP -> SGSN SCP refreshes gprsSSF

CAME L 3 with MO-S MS
• In the T able 13 below (bas ed on [23060, 23078])
corres ponding parameters for S MS S ending are pres ented.
T he CAME L3 affects only MO-S MS S ending (MT -S MS is a
Phas e4 is s ue). T hen, number of the DPs is , in the cas e of the
MO-S MS , 2 due to the fact that the S CP mus t be contacted
before and after MO-S MS s ending has been occurred. T he
MO-S MS includes only one S tate Model that is common for
both Domains (CS , PS ). T he MO-S MS CAME L utilizes long
T CAP dialogues . [23078].
Table 13. CAMEL3 effect on MO-SMS.

SMS SMS Signalling Number of DPs State Model Type of CAP
Signalling Procedure encountered Dialogue
Area
MO-SMS MO-SMS 2 MO-SMS MO-SMS

(packet- Sending
switched)

CAP v3 Operations for MO-S MS
Table 15. The CAP operations for MO-SMS (PS + CS). • T he CAP operations
CAP Operation Direction Purpose
between the S GS N' s
ConnectSMS SCP -> SGSN SCP gives new APN.
s ms S S F and the S CP's
gs mS CF are pres ented in
ContinueSMS SCP -> SGSN SCP orders SGSN to
continue suspended
processing.
EventReportSMS SGSN -> SCP SGSN informs SCP on DPs

T able 15 (bas ed on
encountered.
[23078, 29078]). As it can
InitialDPSMS SGSN -> SCP Establishes CAP connection
(1st operation). be s een, the MO-S MS
FurnishChargingInformationSMS SCP -> SGSN SCP gives free format includes 8 different CAP
operations for the
charging data into CDR.
ReleaseSMS SCP -> SGSN SCP orders SGSN to release

MO-SMS Sending.
CAME L3. T hos e CAP
RequestReportSMSEvent SCP -> SGSN SCP orders SGSN to notify,
when new DP is met. operations that are s een in
ResetTimerSMS SCP -> SGSN SCP refreshes gprsSSF F igures for the IN Bas ed
Prepaid have been
timers.
marked with grey colour.

CAME L 3 in MS C

CAME L 3 O-B CS M
• DP Collected_Info T DP -R O_Null & Authorise_Origination_
O_Exception
Attempt_Collect_Info
• DP Analys ed_Information
T DP -R O_Abandon
• DP R oute_S elect_F ailure Collected_Info

T DP -R , invalid_information
E DP -N, E DP -R Analyse_Information
• DP O_B us y E DP -N, E DP -R
• DP O_No_Ans wer E DP -N, E DP -R
• DP O_Ans wer E DP -N, E DP -R
• DP O_Dis connect E DP -N, E DP -R Analysed_Information
• DP O_Abandon E DP -N, E DP -R
Route_Select_
Routing Failure
& Alerting O_Busy
O_No_Answer
O_Answer O_routing_and_alerting_failure
O_Active
O_active_failure
O_Disconnect
Basic Call transition

S OUR CE : [23078]

CAME L 3 T -B CS M
• DP T erminating_Attempt_Authoris ed
T DP -R T_Null T_Exception
• DP T _B us y T DP -R , E DP -N, E DP -R T_Abandon
• DP T _No_Ans wer T DP -R , E DP -N, E DP - Terminating_Attempt_Authorised

R
• DP T _Ans wer E DP -N, E DP -R
T_Busy
• DP T _Dis connect E DP -N, E DP -R
• DP T _Abandon E DP -N, E DP -R Terminating Call Handling T_No_Answer
T_call_handling_failure
T_Disconnect
T_Answer
T_Active T_active_failure
Basic Call transition
S OUR CE : [23078]

CAME L 3 S tate Model for MO S MS
• DP S MS _Collected_InfoT DP -R
• DP O_S MS _F ailure E DP -N, E DP -R SMS Null & Start &
Authorize
SMS_Exception
• DP O_S MS _S ubmitted E DP -N, E DP -R
DP SMS_Collected_Info
DP O_SMS_Failure
SMS Analyse &

Routing
DP O_SMS_Submitted O_SMS_Exception
S OUR CE : [23078]

CAME L 3 with CS P hone Call
Table 17. CAMEL3 effect on Circuit Switched Call Control.
• T he CAME L functionality affects

CS Phone CS Phone Call SubArea of Signalling State Number of
Call Signalling Models: DPs in the
Signalling
Area
Procedure O-BCSM
vs. T-
State Model
the CS Domain in the following
BCSM
areas [23078]: Circuit S witched
MM IMSI Attach - - -
Call Control, S hort Mes s age
MM IMSI Detach - - -
S ervice, S upplementary S ervice
CC Mobile Originated
Call
- O-BCSM 8
Invocation, US S D, Mobility
CC Mobile Forwarded - Both 8 + 6 = 14 Management, Control and
Call
Interrogation of S ubs cription Data
CC Mobile Terminated
Call
• in GMSC T-BCSM 6
and S ubs criber S tate and
• in VMSC
Location R etrieval (T able 4,
CC Interaction with
Supplementary
• Line Identification Both 8 + 6 = 14
bas ed on [23078]). Mos t of them
Services • Call Forwarding
Services are already within earlier CAME L
• Call Barring Services Phas es , i.e. Phas e 1 and Phas e
• Call Deflection 2; introducing the CAME L3 jus t
Services
brings enhancements to thes e
•
areas . T he mos t important
Closed User Group
CAME L Application Area is

MM Inter MSC - - -
Handover
MM Intersystem change - - - Circuit S witched Call Control. It

(2G <-> 3G)
includes S tate Models and CAP
s ignals for controlling CS Phone
Call (s ee T able 17, bas ed on
CAP Operations for CS P hone Call
Table 18. The CAP operations for Circuit Switched Call Control. MSC contains gsmSSF ContinueWithArgument SCP -> MSC SCP orders MSC to
continue suspended
+ possibly internal SRF. IP contains gsmSRF.
processing with modified
CAP Operation Direction Purpose information.
SCP -> MSC SCP tests CAP connection. DisconnectForwardConnection SCP -> MSC SCP orders MSC to
ActivityTest
disconnect connection with
IP (gsmSRF).
ActivityTestAck MSC -> SCP MSC acknowledges.
EstablishTemporaryConnection SCP -> MSC SCP orders MSC to
ApplyCharging SCP -> MSC SCP sends threshold limits establish connection with
and tsw (Prepaid). e.g. IP (gsmSRF).
MSC -> SCP MSC reports transferred EventReportBCSM MSC -> SCP MSC reports SCP on
ApplyChargingReport
encountered DP (call-related
data and/or elapsed time. event).
AssistRequestInstructions IP, MSC -> MSC, IP gives SCP info to FurnishChargingInformation SCP -> MSC SCP gives free format
SCP associate with InitialDP. charging data into CDR.
InitialDP MSC -> SCP Establishes CAP connection

CallGap SCP -> MSC SCP activates/modifies/
(1st operation).
removes call gap
mechanism from MSC. PlayAnnouncement SCP -> MSC SCP gives IP instructions on
playing announcements
CallInformationRequest SCP -> MSC SCP orders MSC to record /tones to subscriber.
specific info on single call. PromptAndCollectUserInformation SCP -> MSC, SCP interacts with the
IP calling party to collect
CallInformationReport MSC -> SCP MSC reports SCP specific information.
call info of a single call.
PromptAndCollectUserInformation MSC -> SCP MSC, IP acknowledges
Cancel SCP -> MSC SCP cancels all DPs and Ack
reports. ReleaseCall SCP -> MSC SCP orders MSC to
terminate the ongoing call.
Connect SCP -> MSC SCP orders MSC to route
the call to a specific RequestReportBCSMEvent SCP -> MSC SCP orders MSC to notify,
destination. when new DP is met.
ResetTimer SCP -> MSC SCP refreshes gprsSSF

ConnectToResource SCP -> MSC The ongoing call is timers.
connected to IP (gsmSRF).
SendChargingInformation SCP -> MSC SCP gives AoC
Continue SCP -> MSC SCP orders MSC to information.
continue suspended SpecializedResourceReport MSC -> SCP MSC, IP responses to
processing. PlayAnnouncement
operation (when
T able is bas ed on [23078, 29078]

CAME L 3 in S ervice P latform

CAME L 3 in S ervice P latform
• T here mus t be implemented within the gs mS CF exactly the
s ame S tate Models , CAME L Detection Points and CAP
operations as in the gprs S S F and the gs mS S F . Otherwis e,
CAP communication between thes e entities will not s ucceed.
• F rom the S ervice Platform point of view, it cons is ts of s everal

IN elements and components and gives various benefits for
the network operator, s ervice provider and s ubs criber.

Own contribution: IN B as ed P repaid
by the help of CAME L 3
IN Bas ed Prepaid is us ed as an example to s how,

how CAME L3 can be utilized in both CS and PS
Core Domains

IN B as ed P repaid - Operation P rinciple
• F rom the charging point of view, the prepaid is an addition to normal
charging. T his means in practice that charges for telecommunication
s ervices are applied to the prepaid s ervice account by decrementing this
account in real-time. T he prepaid mobile s ubs criber may be notified about
his /her real-time account information at the beginning, during, or at the
end of the telecommunications s ervice currently in us e. When the account
balance is low enough the s ubs criber is pos s ibly notified (via S MS s ending
or tone accouncements ) s o that the s ubs criber has a chance to refill the
account. When the account balance drops below a pre-defined thres hold,
the s ubs criber’s us e of telecommunications s ervices is barred by the
s ervice provider. T he Prepaid is applicable to CS Phone Calls , Mobile
Originated (MO), Mobile F orwarded (MF ) and Mobile T erminated (MT ),
GPR S and MO-S MS .
• In the IN architecture the prepaid account is held in S ervice Control Point

(S CP). T he information that the s ubs criber is a CAME L s ubs criber is
provis ioned to the HLR . All CS I elements available are downloaded from
the HLR during Attach, Location Update and Inter S GS N R AU procedures
to the MS C/S GS N. T he S CP gives limits to the MS C (Apply Charging;
68
time limit) and the S GS N (Apply Charging GPR S ; time, data or both
limits ), and they report thos e limits back in Apply Charging R eport
IN B as ed P repaid in P S Core Domain
• S es s ion Management
• PDP Context Activation
• PDP Context Modification
• PDP Context Deactivation
• Mobility Management
• (UMT S ) GPR S Attach
• (UMT S ) GPR S Detach
• S R NC R elocation + Inter S GS N R AU
• MO-S MS S ending
• Micro-Billing S cenario (CAME L3 + OS A API)
ALL FIGURES ARE BASED ON [23060, 23078]
P DP Context Activation (Context
MS
Dialogue)
3G-SGSN GGSN SCP
The GPRS Session is going on and mobile subscriber tries to activate PDP Context, i.e. to start data transfer...
Activate PDP Context Request • PDP Context S tate

Model
Initial DP GPRS (DP PDP Context Establishment)
Furnish Charging Information GPRS
Request Report GPRS Event
Continue GPRS • DP PDP Context

Create PDP Context Request E s tablis hment
Create PDP Context Response (Charging ID)
Event Report GPRS (DP PDP Context Establishment Ack) • DP PDP Context
Event Report GPRS Ack E s tablis hment Ack
Apply Charging GPRS (maxTransferredVolume)
Apply Charging GPRS (maxElapsedTime)
Continue GPRS
The mobile subscriber can transfer data now. Simultaneously, Prepaid charging is going on, too.
Activity Test GPRS
Activity Test GPRS Ack
Data limit is reached in 3G-SGSN - must be reported to SCP. If there are both limits
- data and time - pending, BOTH limits are reported with two different ’Apply Charging
Report GPRS’ operations.
Apply Charging Report GPRS (transferredVolume, active)

Apply Charging Report GPRS Ack
Apply Charging Report GPRS (elapsedTime, active)


Apply Charging GPRS (maxElapsedTime)

S GS N Initiated P DP Context
Modification
MS 3G-SGSN GGSN SCP • PDP
Context
S tate Model
The GPRS Session is going on. This PDP Context is active. The subscriber tries to watch a video footage
after reading an electric newspaper -> QoS is changing...
Update PDP Context Request • Point In

Update PDP Context Response
As s ociation
(PIA)
Modify PDP Context Request
PDP_Contex
Modify PDP Context Accept t_E s tablis he
Apply Charging ReportGPRS (Volume, Negotiated QoS) d
The GPRS Session is going on. This PDP Context is active and has new QoS parameters now.

MS Initiated P DP Context Deactivation
MS 3G-SGSN GGSN SCP

• PDP Context
The GPRS Session is going on. This PDP Context is active. The subscriber wants to stop the connection to Internet, i.e.
to terminate the data transfer occasion....
S tate Model
Deactivate PDP Context Request • DP PDP
Apply Charging ReportGPRS (transferredVolume, not active) Context
Dis connection
Event Report GPRS (DP PDP Disconnection met)
Event Report GPRS Ack
Continue GPRS
Deactivate PDP Context Accept
The GPRS Session is still going on. This PDP Context is deactivated, i.e. the subscriber can’t transfer any data with this
PDP Context.

UMT S GP R S Attach (S es s ion Dialogue)
• GPR S
MS 3G-SGSN SCP HLR
Attach/Detach
Mobile subscriber tries to attach to the Packet Switched Core Network Domain...
S tate Model
Attach Request
• DP Attach
Insert Subscriber Data • After Attach procedure,
Insert Subscriber Data Ack
PDP Context(s ) is
activated ->
Initial DP GPRS (DP Attach)
Request Report GPRS Event

• DPs PDP Context
E s tablis hment and
Apply Charging GPRS (Tcp + Tsw for GPRS Session)
PDP Context
Furnish Charging Information GPRS (for GPRS Session) E s tablis hment Ack
Continue GPRS (PDP Context S tate
Attach Accept Model) for PDP
Context are
Mobile subscriber is attached to the Packet Switched Core Network Domain (there is credit left in
his Prepaid account in SCP).
encountered; s ignalling
is quite s imilar than in
Context Dialogue
(except that ' Initial DP
73 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl GPR S 'is not s ent any
more to S CP)
UMT S GP R S Detach (S es s ion Dialogue)
MS 3G-SGSN GGSN SCP
• GPR S Attach/Detach
S tate Model
The GPRS Session is going on. The mobile subscriber has stopped transferring data and tries to detach
from the network...
Detach Request

• DP Detach
• PDP Context S tate
Model
Apply Charging Report GPRS (Data+Time; for PDP Context)
• DP PDP Context
Furnish Charging Information GPRS (for PDP Context)
Event Report GPRS (DP PDP Context Disconnection)
Event Report GPRS Ack Dis connection

Continue GPRS (for PDP Context)
There may be several PDP Context Deactivations before DP Detach for GPRS Session is encountered...
Apply Charging Report GPRS (Time; for GPRS Session)
Furnish Charging Information GPRS (for GPRS Session)
Event Report GPRS (DP Detach)
Continue GPRS (for GPRS Session)
Detach Accept
The GPRS Session is over and the subscriber is detached from the Packet Switched Core Network Domain.

S R NC R elocation in old 3G-S GS N
(S es s ion Dialogue)
MS Old 3G-SGSN New 3G-SGSN GGSN SCP
Mobile subscriber is roaming between two Routing Areas. Data Transfer is possibly going on (mobile in PMM-Connected mode).
• Attach/Detach S tate
Model
Source RNC decides to
initiate SRNS relocation...
Forward Relocation Request
Establishment of Radio Access Bearers between

Target RNC and new 3G-SGSN
• DP Detach, Change of
Forward Relocation Response Pos ition
Apply Charging Report GPRS (DataVolume, active)

• PDP Context S tate
Event Report GPRS (DP PDP Disconn., Change of Position)

Model
• DP PDP Context
Update PDP Context Request
Update PDP Context Response

Dis connection, Change of
Pos ition
Forward Relocation Complete
Forward Relocation Complete Acknowledge
DP PDP Context Disconnection was encountered for all active PDP Contexts, before DP Detach for GPRS Session is met. All Downlink
and Uplink data for this GPRS Session (for all active PDP Contexts) are transferred via new 3G-SGSN and new RNC (Target RNC).
Apply Charging Report GPRS (Time, for GPRS Session)
Event Report GPRS (DP Detach, Change of Position)
Source RNC detects that this SRNS

relocation was successful (Iu-PS is
released by the Old 3G-SGSN)

Inter S GS N R AU in new 3G-S GS N
(S es s ion Dialogue)
• Attach/Detach
MS New 3G-SGSN HLR SCP
S tate Model
Inter SGSN RAU is going on. Old 2G/3G-SGSN has terminated CAP connection with SCP. New 3G-SGSN has already updated its
PDP and MM Contexts. The GPRS Session and different PDP Contexts are active in new 3G-SGSN.
Routing Area Update Request
Update GPRS Location (Supported Camel Phases)

• DP Change of
Insert Subscriber Data (GPRS-CSI + SMS-CSI)
Insert Subscriber Data Ack

Pos ition S es s ion
• PDP Context
Initial DP GPRS (DP Change of Position Session)
Prepaid account check.

If no credit left,
’Release GPRS’ is
sent back.
S tate Model
Request Report GPRS Event (Change of Position Context) • DP Change of
Apply Charging GPRS (Tcp + Tsw for GPRS Session)

Pos ition Context
Routing Area Update Accept
DP ’Change of Position Session’ was met in Attach/Detach State Model...let’s handle all ’Change of Position Context’ DPs for different
active PDP Contexts (according to PDP Context State Model).
Event Report GPRS (DP Change of Position Context)
Apply Charging GPRS (Time, Data, Tsw for PDP Context)
Session Dialogue is active for GPRS Session and its different PDP Contexts in new 3G-SGSN now (Prepaid charging is going on).

MO-S MS S ending
MS 3G-SGSN SCP SMS-IWMSC • MO-S MS S tate
Mobile subscriber is attached to the Packet Switched Core Network Domain. The GPRS
Model
• DP
Session is going on. The subscriber tries to send a mobile-originated SMS (MO-SMS).
SMS Message Transfer

S MS _Collected
Initial DP SMS (DP SMS Collected Info)
_Info
SCP checks the Prepaid
account. If no credit left, • DP O_S MS
_S ubmitted
’Release SMS’ is sent back.
Request Report SMS Event (DP O-SMS-Submitted)
Continue SMS
ForwardShortMessage
MO-SMS is sent to
SMS Centre.
Delivery Report
Delivery Report
Event Report GPRS (DP O-SMS-Submitted)
This MO-SMS Sending was successful. The GPRS Session is still going on.

IS MF with OS A AP I for m-Commerce
payments
• In the F igure 56 below
(bas ed on [Gre01, Lil01,
MS gprsSSF/3G-SGSN HLR gsmSCF/SCP Data Session Data Session Manager APPSE 23060, 23078, 29998])
forward
enableDataSessionNotification the mobile s ubs criber
Insert Subscriber Data (GPRS-CSI)
AnyTimeModification
reads an electric
Application triggers are enabled in the network. Now, the subscriber must make a connection towards New Services’s Server by activating a new PDP Context for that.
news paper from a
Activate PDP Context Request
commercial Internet S ite
Initial DP GPRS
forward
(News S ervices ) and
dataSessionEventNotify
pays for that in real-time
forward
connectReq
utilizing his Prepaid
Request Report GPRS Event account within the S CP.
Connect GPRS
T he s ignalling is s hown
Context creation in GGSN successful. in the s ituation, where
Event Report GPRS
the S ervice Acces s has
forward
connectRes already been granted by
Apply Charging GPRS
forward
superviseDataSessionReq
the Core Network
Continue GPRS
forward
connectReq
(S ervice Acces s level is
not s hown). Us ually, the
PDP Context is activated between Mobile Terminal and New Service’s Server existing within public Internet. Then, the mobile subscriber reads/downloads the electrical newspaper and pays for that in
real-time from his Prepaid account within IN Platform. Key question: how IN Platform knows the exact sum that must be deducted from Prepaid account: access/volume/time based charging. Next, the Prepaid account is
the mobile subscriber leaves this Server -> IN Platform asks 3G-SGSN to report all transferred data / elapsed time...3G-SGSN responds for that...
common for both the
Apply Charging Report GPRS Core Domains . As it can
be s een, the gs mS CF
Prepaid account is deducted. The same sum (volume/time/real money) is delivered to the APPSE, too.
forward
does not handle s ervice
superviseDataSessionRes
logic execution any
more. T he s ervice logic
execution is under the
APPS E ' s res pons ibility
now (pos s ibly outs ide
Core Network, if it is
78 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl owned by the 3rd party
s ervice provider).
IN B as ed P repaid in CS Core Domain
• Call Control
• Mobile Originated Phone Call
• Mobile T erminated Phone Call
• Mobility Management
• Location Update
ALL FIGURES ARE BASED ON [23018, 23078]

Mobile Originated Call E s tablis hment
MS VMSC/VLR SCP PSTN
• CAME L3 O-BCS M
Mobile subscriber is attached to the Circuit Switched Core Network Domain and tries to make a phone call... • DP Collected_Info
Setup ( B# )
InitialDP ( B#, IMSI, MSISDN, Location, CallRef#, ServiceKey)
RequestReportBCSMEvent (armed DPs)
FurnishChargingInformation
ApplyCharging ( Tcp, Tsw, ReleaseIfExceeded=No, Tone )
Continue
ISUP_IAM( B# )
ISUP_ACM
Alert
ISUP_ANM
Connect
Circuit Switched Phone Call is established between A and B subscribers.

Mobile Originated Call R eleas e
MS VMSC/VLR SCP PSTN • CAME L3 O-
BCS M
Mobile subscriber is attached to the Circuit Switched Core Network Domain
and CS phone call is going on. Time limit expires. • DP
O_Dis connect
Apply Charging Report (Time limit)
ReleaseCall
ISUP_REL
Release
SCP ordered VMSC to terminate the CS phone call immediately. Thus, the mobile
subscriber is detached from the Circuit Switched Core Network Domain.

Mobile T erminated Call E s tablis hment
PSTN GMSC HLR SCP VLR/VMSC-B
• CAME L3 T -
Mobile subscriber is attached to the Circuit Switched Core Network Domain and receives a phone call...
BCS M
ISUP_IAM( MSISDN)
MAP-SRI( MSISDN, SupportedCamelPhase, GMSC#) • DP T erminating_

MAP-SRI-ack( O-CSI, T-CSI, VLR# ) Attempt_Authorized
InitialDP( VLR#, IMSI, MSISDN etc )
RequestReportBCSMEvent( armed DPs )
ApplyCharging( Tcp, Tsw )
Continue
MAP-SRI(MSISDN,SupportedCamelPhases, GMSC#)
MAP-ProvideRoamingNumber( SupportedCamelPhase, GMSC#)
MAP-PRN-ack ( MSRN)
MAP-SRI-ack( MSRN )
ISUP_IAM( MSRN )
ISUP-ANM
ISUP_ANM
Circuit Switched Phone Call is established between A and B subscribers.

Mobile T erminated Call R eleas e
• CAME L3 T -
PSTN GMSC HLR SCP VLR/VMSC-B BCS M
Mobile subscriber is attached to the Circuit Switched Core Network Domain and terminates the • DP
ongoing call... T _Dis connect
ISUP-REL
ApplyChargingReport (Time limit)
EventReportBCSM( T_Disconnect, leg-B etc)
Continue
ISUP-REL
Mobile subscriber is attached to the Circuit Switched Core Network Domain, and the call is
terminated.

L ocation Update (M-CS I not pres ent)
• With the M-CS I,
CS Core
MS MSC/VLR HLR
Network
Domain Attach
and Detach
LocationUpdatingRequest
procedures can
MAP-UpdateLocation(supportedCamelPhases) be reported to
the gs mS CF ,
MAP-UpdateLocation_Acknowledgement (CSIs)
too. In the
LocationUpdatingAccept CAME L Phas e
3, however,
Inter S ys tem
Change
between the
2G-MS C and
the 3G-MS C, is
not vis ible to
the gs mS CF .
[Net01f]
• F igure is bas ed
on [23018,
Conclus ions (1/2)
• T he s ervice control experiences a real evolution: more players
in the field, new technologies (terminal, radio acces s , core
network), network operators mus t open their networks for
other companies (wholes aling), new value chain models , new
bus ines s models , multiple s ervice s cenarios . T he mos t
important concept is the VHE .
• T he IN s hall have a role in the future mobile networks ; but the

role of the IN changes from the s ole technology to jus t one
technology alternative in 3G s ervice creation and control. T he
mos t important benefits of the IN are s afe and s ecure s olution
and s tandardized, open interfaces . T he bigges t drawback is
that all IN bas ed s olutions are quite expens ive for the network
operator.

Conclus ions (2/2)
• T he CAME L Phas e 3 architecture affects the R 99 UMT S network
by introducing INCM entities (S S F s ) in the core network. T he
utilized protocols are CAP and MAP that increas e S S 7 s ignalling
load of the network. T he mos t important s ervice is Prepaid. T he
Prepaid concept may be later enhanced towards m-Commerce and
different micro-billing s cenarios . T he main purpos e of the CAME L is
to give roaming s upport for s ubs cribers moving outs ide HPLMN
area.
• T he CAME L Phas e 3 core network s ignalling can utilize APIs , s uch

as OS A and Parlay API, for more flexible s ervice control between
the network and the s ervice layer. By the help of the APIs , the
s ervice layer devices do not have to know the details of the core
network at all. T his makes pos s ible more flexible and rapid s ervice
and application development es pecially for the 3rd parties . T he
CAME L and APIs together create more value for all participants
within the 3G product value chain: operators and application
86
developers get more revenue and a mobile s ubs criber is entitled to
R eferences (1/3)
[21978] 3GPP T echnical R eport 21.978: CAME L Control of VoIP
S ervices , 3GPP T S G CN, vers ion 3.0.0, June 2000
[22078] 3GPP S ervice Des cription 22.078: Cus tomized Applications for Mobile
network E nhanced Logic (CAME L); S ervice des cription - S tage 1,
3GPP T S G CN, vers ion 3.8.0, June 2001
[23018] 3GPP T echnical S pecification 23.018: Bas ic call handling; T echnical
realization, 3GPP T S G CN, vers ion 3.8.0, June 2001
[23060] 3GPP T echnical S pecification 23.060: General Packet R adio S ervice
(GPR S ); S ervice des cription; S tage 2, 3GPP T S G S A, vers ion 3.8.0,
June 2001
[23078] 3GPP T echnical S pecification 23.078: Cus tomized Applications for Mobile
network E nhanced Logic (CAME L) Phas e 3 – S tage 2, 3GPP T S G
CN, vers ion 3.9.0, June 2001
[29002] 3GPP T echnical S pecification 29.002: Mobile Application Part (MAP)
s pecification, 3GPP T S G CN, vers ion 3.9.0, June 2001
[29078] 3GPP T echnical S pecification 29.078: Cus tomized Applications for Mobile
network E nhanced Logic (CAME L) Phas e 3 – CAME L Application
Part (CAP), 3GPP T S G CN, vers ion 3.8.0, June 2001
[Bak00] Bakker, J., McGoogan, J., Opdyke, W., Panken, F .: R apid Development and
Delivery of Converged S ervices Us ing APIs , Bell Labs
T echnical Journal, Vol. 5, No. 3, Bell Labs , July-S eptember 2000
87
[Baz01] Bazin, C., Ceccaldi, B., F ouquet, G.: Prototype for a S ervice Architecture for
Next Generation Networks , Intelligent Network Works hop, IE E E ,

R eferences (2/3)
[Net01b] Nokia 3G S olution, WCDMA & E DGE , T echnical S ummary, Nokia Networks , March
2001
[Net01c] Nokia IN Platform, Product Des cription, Nokia Networks , June 2001
[Bos 01] Bos , L., Leroy, S .: T oward an All-IP-Bas ed UMT S S ys tem Architecture, IE E E
Network, 0890- 8044/01, IE E E , January-F ebruary 2001
[Bre00] Brennan, R ., Jennings , B., McArdle, C., Curran, T .: E volutionary T rends in Intelligent
Networks , IE E E Communications Magazine, 0163-6804/00, IE E E ,
June 2000
[Coo01] Cooks on, M., S mith, D.: 3G s ervice control, Britis h T elecom T echnology Journal, Vol.
19, No. 1, January 2001
[Dao02] Daoud, F ., Mohan, S .: S trategies for Provis ioning and Operating VHE S ervices in
Multi-Acces s Networks , IE E E Communications Magazine, 0163-6804/02,
IE E E , January 2002
[F in00] F inkels tein, M., Garrahan, J., S hrader, D., Weber, G.: T he F uture of the Intelligent
Network, IE E E Communications Magazine, 0163-6804/00, IE E E , June 2000
[Gre00b] Grech, M., McKinney, R ., S harma, S ., S tanaway, J., Varney, D., Vemuri, K.:
Delivering S eamles s S ervices in Open Networks Us ing Intelligent S ervice
Mediation, Bell Labs T echnical Journal, Vol. 5, No. 3, Bell Labs , July-
S eptember 2000
[Gre01] Grech, M., Unmehopa, M.: Us ing Open S ervice Acces s to E nable Mobile Internet
88 Applications
© HUT 2002 in/ 23.04.2002, M.S c. T hes is s eminar/ S aOlUMT S Networks , 3G Mobile Communication T echnologies ,
ollikainen_230402.PPT
Conference Publication No. 477, IE E E , 2001

R eferences (3/3)
[Hum98] Humphrey, J. : Interworking and the IN Platform ; Detailing the Development of the
GS M CAME L S tandard for Interworking IN, T elecommunications , Conference
Publication No. 451, April 1998
[Lil01] Lilge, M.: E volution of Prepaid S ervice towards a R eal-T ime Payment S ys tem, 0-
7803-7047-3/01, IE E E , 2001
[Pal00] Palviainen K. : CAME L3 T raining Material, Nokia Networks , 2000
[Q1204] IT U-T R ecommendation Q.1204: Intelligent Network Dis tributed F unctional Plane
Architecture, IT U-T , March 1993
[Umt99] T he F uture Mobile Market – Global T rends and Developments with a F ocus on
Wes tern E urope, R eport No. 8, UMT S F orum, March 1999
[Umt00a] S haping the Mobile Multimedia F uture – An E xtended Vis ion from the UMT S F orum,
R eport No. 10, UMT S F orum, S eptember 2000
[Umt00b] E nabling UMT S T hird Generation S ervices and Applications , R eport No. 11, UMT S
F orum, October 2000
[Umt00c] T he UMT S T hird Generation Market – S tructuring the S ervice R evenue Opportunities ,
R eport No. 9, UMT S F orum, S eptember 2000
[Umt01] T he UMT S T hird Generation Market – Phas e II: S tructuring the S ervice R evenue
Opportunities , R eport No. 13, UMT S F orum, April 2001
[Vei00] Veikkolainen, S . : E volution to 3G Core Network, Internal T raining Cours e, Nokia
89 © HUTNetworks ,
2002 ollikainen_230402.PPT
MOR E 2000
October
/ 23.04.2002, M.S c. T hes is s eminar/ S aOl
R E F E R E NCE S CAN BE F OUND F R OM T HE T HE S IS IT S E L

Ollikainen 230402

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Ollikainen 230402

Enviado por

Direitos autorais:

Formatos disponíveis

CAMEL Phase 3 in UMTS

Author: Sami Ollikainen,

1 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

2 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

5 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

• UT MS S tandardization within 3GPP

6 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

7 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

Circuit Switched Services

Packet Switched Internet Multimedia

9 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

Cus tomis ed Applications for Mobile network

11 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

• Main CAME L s tandards

12 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

3GPP Domain CS CS CS, PS

• Limited Detection • Announcements

13 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

14 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

• R eports No. 9 and No.

(not s hown in the

Location Based Services

16 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

17 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

30 % account with the s ervice

19 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

Service Provider Application plane

22 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

cus tomis ation and

24 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

meant for terminal-

26 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

SSP SS7 -net work SSP • GMS C (gs mS S F )

CS Core Domain PS Core Doma in

CCB Customer Car e and Billing SMP Service Management Point

29 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

main parts : S ervice

Wireless Wired Data

APPSE APPSE APPSE

gprsSSF gsmSSF ipSSF

SGSN MSC CSCF

F igure is bas ed on [Bos 01]

APPSE APPSE APPSE

ISMF ISMF ISMF

SGSN GGSN CSCF

F igure is bas ed on [Bos 01]

Content VAS Service Network Mobile

34 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

• Below are 2G and 3G

the world becomes from

open, IP data-centric world,

operator' s point of view).

36 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

• CAME L Phas e 3 in 3GPP R 99

37 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

• CAME L Phas e 3 Architecture

39 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

MAP CAP MAP CAP gprsSSF

gsmSSF VLR gsmSSF

GMSC Roaming leg VMSC

Interrogating Network Visited Network

F igure is bas ed on [23078]

41 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl

42 © HUT 2002 ollikainen_230402.PPT / 23.04.2002, M.S c. T hes is s eminar/ S aOl