camel phase 3 in umts - tietoverkkolaboratorio - tkk · camel phase negotiation - 2g/3g issues •...

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

CAMEL Phase 3 in UMTS

Author: Sami Ollikainen,[email protected]

Supervisor: Professor Jorma Jormakka

Master’s Thesis made for Nokia Networks


Contents

• Introduction

• Presentation of tools and methods

• Review of previous research

• Results

• Own contribution

• Conclus ions


Introduction - B ackground

• When moving from 2G to 3G mobile networks ,lots of new services are introduced

• In 2G world, the main technique for controllingservices has been IN, Intelligent Networks(CAMEL, Customized Applications for Mobilenetwork Enhanced Logic)

• IN has many drawbacks and limitations

• S ervices evolution -> S ervice control evolution

• T hus , in 3G world, there shall be two maintechniques for service creation and control: INand open APIs (Application ProgrammingInterface) between service and network layer


Introduction - S tudy objectives

T he following 4 s tudy objectives are defined:• T o examine the evolution of service control, when moving

from 2G to 3G world

• T o find out IN evolution scenarios and what role IN playsin future mobile networks

• T o represent the network architecture for latest CAMELPhase (Phase 3), examine CAMEL protocol (CAP)interfaces in more detail and show as an example of howPrepaid service (PPS ) is implemented by the help ofCAMEL3 in 3GPP Release 1999 (R99) compliant UMT Snetwork

• T o examine, how can CAMEL3 core network s ignallingutilize open APIs (and vice versa)


Presentation of T ools and Methods

• A literature study was chosen as a researchmethod

• Used literature:• public 3GPP standards (especially CAMEL-standards

23.078 and 22.078)

• public research papers (IEEE CommunicationsMagazine, BT T echnology Journal, UMT S ForumReports etc)

• non-public Nokia Networks’s technical documentation


R eview of Previous R esearch

• UT MS S tandardization within 3GPP

• CAMEL S tandardization within 3GPP

• 3GPP R99 Architecture

• CAMEL and S ervice Control in UMT S


UMT S S tandardization within3GPP


3GPP Domains and S ubsystems

Circuit Switched Core Network Domain

Packet Switched Core Network Domain

Internet MultimediaCore Network Subsystem

ServicesSubsystem

MSC MSCServer

HLR

HLRGGSNSGSN HSSMGWCPS

•Location server•Application server•WAP gateway•etc.

•Border GW•Firewall•LIG

SOURCE: [Vei00]


CAME L S tandardization within3GPP


Why CAME L ?• L imitations in IN based on ET S I Core INAP CS 1

No mobile functionality (only vendor specific extens ions)

T oo much room for interpretations (multivendor sys tem is difficult)

• Need for"IN" supporting mobile terminals

S ervices not covered by standardised GS M services

S ervices for subscribers roaming outs ide the HPLMN

Eas ier multivendor interaction

• T he S tandardisation result was

Customised Applications for Mobile networkEnhanced Logic

or just CAME L


• Animal• IN network technologyfor mobile networks• Etc

SERVICESin SCP

Home PLMN /HLR

Visited PLMN/MSC, VLR, SGSN

CAMELSubscription Info(CSI)

What is CAME L ? (1/2)


What is CAME L ? (2/2)• CAMEL is an IN technology by

the help of which value-addedservices can be offered to themobile subscribers roaming inHPLMN or VPLMN

• CAMEL integrates INtechniques from fixed to mobilenetwork

• CAMEL is based on ET S I'sCore Intelligent NetworkApplication Part (INAP) andMobile Application Part (MAP)protocols

• CAMEL is being developed inPhases (Phases 1-3; Phase 4standardization work wasstarted in autumn 2000)

• Main CAMEL standards(3GPP) are 22.078, 23.078 and29.078

Table 4. CAMEL Application Areas.

CAMEL ApplicationArea

Subareas AffectedCoreDomain

Affected 3GPPStandards(other thanCAMELstandards)

UsedProtocols withCAMEL

Circuit Switched CallControl

• MO call

• MT call

• MF call

CS 23.018; 23.072,23.081, 23.082,23.083, 23.084,23.085, 23.086,23.087, 23.088,23.091, 23.093,23.135, 23.079

CAP, MAP

GPRS Interworking • GPRSSession

• PDPContext

PS 23.060, 32.015 CAP, MAP

Short Message Service MO-SMS Both 23.040 CAP, MAP

Supplementary ServiceInvocation

- CS 23.011, 23.091,23.084, 23.072,23.093

MAP

USSD - CS 23.090 MAP

Mobility Management - CS 23.018 MAP

Control andInterrogation ofSubscription Data

HLR – SCPinterface

CS, PS 23.008, 23.016 MAP

Subscriber State andLocation Retrieval

MSC-GMLCinterface

CS 23.016, 23.127 MAP


CAME L His tory: S tandardization inPhases

• Phases 1-2 for CircuitS witched (CS ) CoreDomain

• Phase 3 for both CS andPacket S witched (PS ) CoreDomains

• Phase 4 for IP MultimediaS ubsystem (IMS ); notdiscussed within this M.S c.T hes is

• T able is based on [Pal00]

Table 6. Comparison between different CAMEL Phases.

CAMEL Phase Phase 1 Phase 2 Phase 3

3GPP Domainaffected

CS CS CS, PS

PhaseCharacteristics

• Applicable to MOand MT calls

• No chargingoperations

• Noannouncements

• Limited DetectionPoints

• Chargingoperations

• New Call relatedDetection Points

• SS invocationnotification

• Announcementsand tones

• DTMF reception

• USSD betweenSCP and phone

• GPRS chargingoperations

• MO-SMSchargingoperations

• Dialled services(D-CSI, N-CSI)

• SCP-HLRinterface

• SCP control ofCW, CF andMPTY

• MobilityManagementfunctions

ServiceExamples

• Call Screenings

• Call Forwardings

• Call Redirections

• Call Routings

• Very simple VPN

• Prepaid

• Hunting

• Announcements

• Freephone

• Premium Rate

• PersonalDiscount

• LocationDependentDiscount

• ReverseCharging

• GPRS Prepaid

• Enhancement ofCS Prepaid

• Service numbers

• MultipleSubscriber Profile


CAME L Phase negotiation -requirements

• A network supporting CAMEL2 must also supportCAMEL1.

• A network supporting CAMEL3 must also supportCAMEL2 & CAMEL1.

• CAMEL4 shall provide the functionality of allprevious CAMEL Phases. Phase 4 networks ignalling shall support interworking with CAMELPhases 3 and 2.

• CAMEL3 is the lowest phase for S GS N.


CAME L Phase negotiation - 2G/3Gissues

• All CAMEL phases work in 2G and 3G.• CAMEL1 and CAMEL2 Location Information contains a Cell-

id parameter which contains the GS M cell or UMT S S erviceArea Identity (S AI).

• S tarting from CAMEL3 an additional parameter indicateswhether 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-system CS handover is not vis ible to the S CP, nor

change of user rate.T he PS QoS and change if QoS are indicated to the S CP.Inter-system PS RAU is vis ible to the S CP.

• CS Multicall feature usage is seen as multible independentcalls in the S CP.

S OURCE: [Pal00]


UMT S S ervices by UMT S Forum

• Reports No. 9 and No.13 introduce 6 UMT SS ervice Categories

• Each s ingleservice/applicationbelongs to severalS ervice Categories(not shown in theF igure, based on[Umt01])

UMTS Forum Report No. 9 Service Categories

MobileInternetAccess

MobileIntranet/ExtranetAccess

CustomisedInfotainment

MultimediaMessaging

Service(MMS)

LocationBasedService

Rich Voiceand Simple

Voice

UMTS Service Concepts and Applications

�

Downloadable Ring Tones / Graphics

�

Entertainment

�

Internet Games

�

Mobile Music

� Online Dating

�

Online Gambling

Entertainment

�

Financial Services

� Financial/Banking (E-cash)

�

Mobile Cash

�

Mobile E-Bill

� Mobile E-Salary

�

Stock Trading

Financial Services

�

Alerts

� Dictionary Research

�

Directories

�

Emergency Services (911)

� Flight Reservation

�

Info Services

�

Instant Weather Forecast

� M-information (user statistics)

�

Multimedia (video/audio real-time)

�

Personal Information Management (PIM)

� Restaurant Guide

�

Town Page (Yellow Page)

�

Virtual Home Environment (VHE)

Information Services

�

Advertising

�

B2B Business Data Applications

� eWallets & Shopping Enhancements

�

Just The Ticket

�

M-Commerce Transactions

� ME Commerce

�

Micro-Payments

�

Mobile Retailing

� Transaction Processing

Mobile Commerce

� Mobile Video (Streaming)

�

Mobile Videotelephony

�

Simple Voice

� Teen Video Chat (Non Real-Time)

�

Video Conferencing

�

Voice over IP (VoIP)

� Voice Portal

�

Voice-Activation

Conferencing

� E-mail / Messaging

�

E-mail Receipt (100 letters)

�

E-mail Transfer (100 letters)

� Instant Messaging / Message Aggregation

�

Machine-to-Machine

�

Mobile Chat (Non Real-Time)

� Mobile Instant Messaging (MIM)

�

Mobile Postcard

�

Multimedia Messaging

� Short Message Service (SMS)

�

Streaming Audio/Video (Non-Real Time)

�

Unified Messaging

Messaging

�

Application Synchronization

�

FTP Transfers

� Internet

�

Intranet

�

Mobile VPN

� Web Browsing

Internet Access / Networking

�

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

Location Based Services


CAME L Control of 3G S ervices

• UMT S services canbe categorised into 4different groups:

• Bas ic

• S upplementary

• Operator S pecific

• Multimedia

• CAMEL control canbe used with manyservices

• T able is based on[21978]

Table 7. 3G services requiring possibly CAMEL Control.

ServiceCategory

Name of Service

Basic Services Speech, emergency calls, low bit rate data, medium bit rate data, highbit rate data, high quality audio, low bandwidth video, high bandwithvideo

SupplementaryServices

Operator determined barring, user defined barring, call screening, calldeflection, call forwarding unconditional, call forwarding on busy (noreply and not reachable), call waiting, call hold, call transfer, callingnumber identification presentation/restriction, connected numberidentification presentation/restriction, multiple subscriber profile,multi-party, call completion services (e.g. CCBS), closed user group,advice of charge, calling name presentation

OperatorSpecificServices

Short number dialling, prepaid, VPN

Other Services Lawful interception, voice group-call service, voice broadcastservice, SMS, fax, ASCI, MExE, location services, SoLSA


PPS Penetration in S elected Countries• Prepaid S ervice (PPS ) can

be implemented in multipleways

• PPS allows a mobilesubscriber to pay fortelecommunicationservices before the actualusage, i.e. in advance

• PPS subscriberestablishes a prepaidaccount with the serviceprovider for access ingtelecom services

• IN Based Prepaid is justone type of Prepaid

• F igure is based on [Lil01]

Pen

etra

tion

(%)

Year

1996 1997 1998 1999 2000 2001 2002 2003 2004 20050 %

10 %

20 %

30 %

40 %

50 %

60 %

70 %

80 %

90 %

100 %

Italy

Mexico

Germany

WORLD

China P.R.

USA

Japan

India


3GPP R 99 Architecture


R 99 UMT S Network Architecture• Mobile T erminal• Radio Access

• 2G RAN - BS S• 3G RAN - UT RAN

• Core Network• Circuit S witchedCore NetworkDomain• Packet S witchedCore NetworkDomain

• S ervices andManagementS ubsystem (e.g.IN/S CE)

• F igure is based on[Net01b]

3G SGSN

RNCRNC

GSM

BSCBSC

WCDMA

ExternalIP networks

IPBackbone

PSTN/ISDN

Other PLMN

HLR

Transit MSCTransit MSC3G MSC3G MSC

GGSN

A

Iu-CS

Iu-PS

SS7

IN/SCEAPSE


3GPP R 99 UMT S S ervice Architecture• In the 3GPP R99

UMT S network,S S 7 s ignalling isheavily used forservice control

• T wo mainalternatives forservice creationand control:

• IN• OS A/ParlayAPI

• IN services arecreated in S CE (INS IBs); IN S ervicePlatform

• OS A services arecreated inAPPS Es (XML,Java servlets)

• F igure is based on[Vei00]

CS & PS Core Domains

Network OperatorApplication plane

Service Provider Application plane

SS7 backbone

SCE APPSE

Contentserver

PortalPlatformAPPSE

HLR

SGSNRoutr

GGSNSGSN

APPSE - Application ServerSCE - Service Creation and Execution

RadioAccess

Control

SS7 Backbone

MSC


CAME L and S ervice Control inUMT S


Virtual Home E nvironment (1/2)• Virtual Home Environment

(VHE , see F igure) isdefined as a concept forPersonal S erviceEnvironment (PS E)portability across networkboundaries and betweenterminals . T he concept ofthe VHE is such that usersare cons is tently presentedwith the samepersonalized features ,User Interfacecustomisation andservices in whatevernetwork and whateverterminal (within thecapabilities of the terminal

Service Creation Environment

Service Management

Service Data ServiceControl

Home NetworkHLR

Serving NetworkSSF Screening VLR

TerminalMExE Client MS

IC CardSIM Toolkit

SIM

SOURCE: [Hum98]


Virtual Home E nvironment (2/2)

VHELogic

ServiceProfile

QoS (end-to-end)

User Location

NetworkCapabilities

TerminalCapabilities

User Profile

Subscriptions

SeamlessRoaming

• IN and CAMEL areindependentconcepts fromVirtual HomeEnvironment(VHE)

• In practice, VHEcan beimplemented withCAMEL

• F igure is based on[Baz01]


VHE with OS A in R 99 UMT S network• CAMEL (CAMEL

server, CS E) is apart of the VHE/OS Aarchitecture

• T he main goal ofVHE/OS A conceptsis to enable servicedevelopmentindependently of theunderlying networks

• T he interfacebetween service andnetwork layer iss tandardized ->service creationbecomes faster,eas ier and more

Application ServersService layer

...Service ...Service...Service...Service

Network layer

SCF

UMTS callcontrol servers

SCF

HLR

SCF

CAMEL server(CSE)

SCF

MExE server

SCF

SAT server

Transport network

24.08 MAP CAP WAP SAT

StandardizedOSA

interfaces

Service Capability Server (SCS)

SCF Service Capability Feature (SCF)

S OURCE:[Bos01]


3G S ervice Creation with OS A

• Open S erviceArchitecture (OS A)Capabilities may bemeant for terminal-or network-centricapplications

• T erminal vs .Network CentricCapabilities (OS AS CS s)

• F igure is based on[Har01a]

service creation environment (operator)

service platformse.g.- messaging- SMS- location

network capabilitiese.g.- telephony- data- supplementaryservices- CAMEL

open interface (network/server-centric applications)

service personalizationenvironment (customer)

terminal capabilitiese.g.- USAT- MExE- Web browser- Operating System

network operator productsnew 3G products, e.g.- video clip download- interactive games

existing 2G products for circuit andpacket-data calls

3rd party productscreated by serviceintegrators:- content providers,- application providers etc.

open interface (terminal-centric applications)

NetworkAPIs


IN Architecture Model• IN Conceptional Model

(INCM) gives aframework concerninghow networkintelligence is providedand dis tributed within acertain network

• INCM cons is ts of fourplanes:

• S ervice

• Global Functional

• Dis tributedFunctional

• Phys ical

• F igure (based on[Q1204]) representsDis tributed FunctionalPlane architecture

SMF

SCF

CCAF CCF

SSF

CCF

SSF

SDF

SMAF

SRF

SCEF

CCAFCCF


Mapping between INCM and commercialIN

• IN functionality isdis tributed according toINCM

• IN S ervice Platform (S CE,S CP, S MP, S MAP, IP etc)

• S CP (gsmS CF)

• CS Core Domain

• VMS C (gsmS S F)

• GMS C (gsmS S F)

• HLR

• PS Core Domain

• S GS N (gprsS S F)

• S S Fs and S CF areneeded for CAMELcommunication

• F igure is based on[Net01c]

NOKIA TELECOMMUNICATIONS

Nokia Intelligent Networks Architecture

SMP SMAP IP MSC

Service Management PointService Management Access PointIntell igent PeripheralMobile Switching Center

SCESMP

SMAP

CS Core Domain

ServiceNode IP

NO 00KIADX2

SSP

IP

PS Core Domain

NOKIASGSN

SSP

Customer Care and BillingService Control PointService Switching PointService Creation Environment

CCBSCP SSP SCE

SCP SCP

SS7-network

CCB


IN E volution towards IS MF (1/2)

Next-generationnetworks

Wirelessand cablenetworks

Internet anddata

networks

PSTN andtraditionalIntelligentNetworks

Internettelephony

Hybridnetworks

VoPnetworks

Migration path(increased capabilities)

• T he key requirements for future development of the IN are that customerscan access a wider variety of services in a wider variety of ways , and thatthey can customize exis ting services or even create new ones as s imply,quickly, and cost effectively as poss ible. [Bre00]

• In practice, due to the key requirements presented above, IN service logicshould be access ible from Internet terminals and contain componentsres iding in both S CPs and Internet nodes. In this way, new Mobile InternetApplications that provide the mutual support of network capabilities andInternet content may be offered to the mobile subscribers . [Bre00, Gre00b]

S OURCE: [F in00]


IN E volution towards IS MF (2/2)

Application Servers (APPSEs):é Network Operatoré ASPé Enterpriseé Other 3rd party

APPLICATION LEVEL:Operator Independence

INTELLIGENT SERVICE MEDIATION / MIDDLEWARE

Trusted Untrusted

Security Control

SERVICE CAPABILITIES

Location

Call Control

User ProfileManagement

Billing

AddressTranslation

User Status

Mobility

Messaging

CALL CONTROL LEVEL:Network + ProtocolIndependence

TRANSPORT LEVEL:Vendor Independence

CORE NETWORK SIGNALLING

Protocol Adapters

CAP INAP MExE MAP SIP

Wireless Wired Data

NetworkCapabilities

API

ResourcesAPI

Service LogicExecutionExternal APIs:

JAIN, OSA,Parlay, PINT,Spirits, TINA,

TSAS

Service Level Agreements (QoS Policy Control),Authentication, Discovery, Registration

GTP-C

• IN must evolve towardsopen APIs and IntelligentMiddleware

• Intelligent Middlewarecons is ts of an IntelligentS ervice Mediation Function(IS MF) that handles thetraffic between service andnetwork layer

• IS MF cons is ts of threemain parts : S erviceAccess , S erviceCapabilities andT ransport

• Bas ic task of IS MF in Next-Generation Network (NGN)is to split different layersand functionalities fromeach other

• F igure 20 is based on


APPS E : CAME L based S ervice Control

IN Platform

APPSEAPPSE APPSE

SCP

gsmSCF

SGSN CSCF

gprsSSF ipSSF

MSC

gsmSSF

SERVICE LAYER

NETWORK LAYEROSA API

F igure is based on [Bos01]


APPS E : API based S ervice Control

SERVICE LAYER

NETWORK LAYEROSA API

SGSN CSCF

ISMF ISMF

GGSN

ISMF

APPSEAPPSE APPSE

F igure is based on [Bos01]


S ize of B us iness E volution within ValueChain

3G:

Terminal NetworkServicesProvision

ContentProvision

2G:

• Important revolution occurs inthe s ize of different bus inessareas and their importance tothe mobile product valuechain. T he F igure 23 (basedon [Umt00a]) describes, howthis change occurs movingfrom 2G mobile telecom -likevalue chain towards Internet–like value chain, MultimediaValue Chain [Umt99]. Itshows quite clearly thatContent and S ervicesProvis ion have bigger roles ,whereas core network'simportance diminishes, whileintelligence is moving awayfrom the core network(Network layer) towardsapplications (S ervice layer)[Baz01].


Product Value Chain E volution (2G->3G)

Contentprovider

VASprovider

Serviceprovider

Networkoperator

Mobilecustomer

Content,Payment,Securi typroviders

Appl icationprovider

Partialprovider (M)- ISP Mobi le

customerServiceprovider

MVNO Networkoperator

• In the 3G World, different roles within the Value Chain are[Har01a]: NO, S P, mobile virtual network operator (MVNO),mobile Internet service provider (M-IS P), portal (context)provider, application provider, content provider, paymentprocess ing provider and system security provider. T heF igure below is based on [Har01a].


Wholesaling affects Network Charging

Customer

ContentProvider

TransportProvider

ServiceProvider

Advertiser

1

23

4

5

6

Transaction Flows (Who bills whom?)

• Wholesaling means,in practice, accessto 3rd partycompanies from thenetwork operator'spoint of view. T henetwork operatorshould implementthis concept atevery level (e.g.access to fibre,access to callcontrol, access toapplications orprovis ion of contentetc.) in order toutilize core networkresources asefficiently as

S OURCE: [Umt00b]


2G and 3G World ComparisonSERVICE CREATION AND MANAGEMENT

� Network side control of 2Gservices

� IN Platform specific servicecreation and management:closed interfaces

� IN Platform + operator’s ownmobile portals containsapplication, call control andtransport layers

� Skilled specialists (networkoperator personnel)

� Long creation time of newservice (years)

� Network Operator (NO) playsone role: network provider

� Telecom world Value Chain andBusiness Models

� Price and Product: Simple pricestructure (airtime) and voice asmain product (voice-centric)

� Partnerships: Vertical integrationof network infrastructure anddevice distribution

� "Write once, run in one place"

� Technologies: CAMEL, WAP,USSD, SMS

Closed 2G World

� Network + Terminal side controlof 3G services; servicepersonalization

� Open service creation andmanagement environment: OpenAPIs (JAIN, OSA, Parlay etc.)

� IN plays possibly middlewarelayer between applications andtransport

� Individual services can becontrolled by 3rd party APPSEs(softswitch architecture)

� Anyone can create new services

� Rapid new service creation times

� Network Operator (NO) hasmultiples roles: mobile portal,mobile ISP, communicationinfrastructure provider

� Internet world -like Value Chainand Business Models

� Price and Product: Complex,service-specific price structures;subscriptions, messages,advertising, airtime, transactions

� Partnerships: Strategicpartnerships to emulate end-to-end integration; Wholesaling

� "Write once, run everywhere"

� New entire services classes: m-business, location-basedservices, multimedia messaging,infotainment, edutainment etc.

� Network reconfiguration; PolicyBased Network Management

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

Open 3G World

• Below are 2G and 3GWorlds compared mainly inthe context of S erviceCreation and Management(F ig. 26, based on [Dao02,Umt00c]). It is clearly seenthat the evolution is radical:the world becomes fromclosed voice-centric,monopoly-like world towardsopen, IP data-centric world,where each market partymust co-operate and networkespecially at horizontal level(horizontal integration)instead of the old verticaltype of integration (networkoperator's point of view).


R esults

• CAMEL Phase 3 in 3GPP R99


CAME L Phase 3 in 3GPP R 99

• CAMEL Phase 3 Architecture

• CAMEL3 Operation Principles

• CAMEL3 in S GS N

• CAMEL3 in MS C

• CAMEL3 in S ervice Platform


CAME L Phase 3 Architecture


CAME L 3 Architecture

HLR gsmSCF

GMSC

VLR

VMSC

MAP

gsmSSF gsmSSF

gsmSRF

Roaming legMSIncoming line

MAP CAP CAP

MAP

MAP

Interrogating Network

Home Network

Visited Network

CAPForwarded leg MO call - Outgoing leg

(or Forwarding leg)

Home/Interrogating/Visited Network

MAP

MAP

CAPMAP

SGSN

gprsSSF

F igure is based on [23078]


Concepts (1/2)

• CS I CAMEL S ubscription Information - partof subscriber data, which identifies that asubscriber has CAMEL service(s).

• OS S Operator S pecific S ervice (IN service)

• gsmS CF GS M S ervice Control Function.

• gsmS S F GS M S ervice S withing Function.

• CAP CAMEL 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

• gsmS RF GS M S pecialised Resource Function.

• US S D Unstructured S upplementary S ervice Data

• gprsS S F GPRS S ervice S witching Function

• S GS N S erving GPRS S upport Node


CAME L 3 Operation principles


B as ic CAME L 3 Operation(PDP Context is used as an example)

• CAMEL3 operationoccurs in differentphases. T he three mainphases are CS I fromHLR, Encountering newDetection Point andContinuing/Releas ing theCall. Let's look at certains ignalling procedures, inthis case related to thePDP Context. F igure isbased on [23060,23078].

• In addition, S CP canmake inquiries to HLR

and HLR can updateCS I data in MCS /S GS N.

NEW DP ENCOUNTERED + CAP SIGNALLING

GPRS-CSI FROM HLR

L3-MM, L3-SM orGTP-C SIGNALLING

PDP Context Deactivation procedure

PDP Context Activation procedure

Attach procedure

GGSN HLRSCPSGSNUE/UTRAN

Attach RequestUpdate GPRS Location

Insert Subscriber Data

Attach Accept

Activate PDP Context RequestInitial DP GPRS

Apply Charging GPRS, FCI GPRS, SCI GPRS, Continue

Create PDP Context Request

Create PDP Context Response

Activate PDP Context Accept

Deactivate PDP Context Request

Apply Charging Report GPRS, Event Report GPRS

ACR GPRS Ack, SCI GPRS, Continue GPRS

Delete PDP Context Request

Delete PDP Context ResponseDeactivate PDP Context Accept

Apply Charging Report GPRS

ACR GPRS Ack, Apply ChargingGPRS, FCI GPRS, SCI GPRS

DATA TRANSFER DURING ACTIVEPDP CONTEXT + CAP SIGNALLING


CAME L S ubscription Information (CS I)Table 11. CAMEL Subscription Information elements. Those CSIs that are not sent fromHLR are marked with grey colour.

Name ofCSI

Description AffectedCoreDomain

AffectedNetworkElement

CAMELPhase

D-CSI Dialled Services CAMEL SubscriptionInformation (D-CSI) is transferred to theVPLMN (at Location Update) and IPLMN(for an incoming call in GMSC). D-CSI isfor HPLMN controlled dialled services.

CS MSC \VLR,GMSC

3

N-CSI N-CSI is for VPLMN controlled dialledservices.

CS MSC\VLR

3

GPRS-CSI

GPRS CAMEL Subscription Information(GPRS-CSI) is transferred to the VPLMN.GPRS-CSI is for control of GPRSSessions and PDP Contexts.

PS SGSN 3

M-CSI Mobility Management CAMELSubscription Information (M-CSI) istransferred to the VPLMN. M-CSI is forMobility Management MAPnotifications.

CS MSC \VLR

3

O-CSI Originating CAMEL SubscriptionInformation (O-CSI) is transferred to theVPLMN (at Location Update) and to theIPLMN (for an incoming call in theGMSC). O-CSI is for Mobile Originatingcalls (in the VMSC) and MobileForwarding calls (in the VMSC and theGMSC).

CS GMSC 1

SMS-CSI Short Message Service CAMELSubscription Information (SMS-CSI) istransferred to the VPLMN. SMS-CSI isfor controlling Mobile Originating ShortMessage submissions.

CS, PS SGSN +MSC /VLR

3

SS-CSI Supplementary Service InvocationNotification CAMEL SubscriptionInformation (SS-CSI) is transferred to theVPLMN. SS-CSI is for SupplementaryServices MAP notifications.

CS MSC \VLR

2

T-CSI Terminating CAMEL SubscriptionInformation (T-CSI) is transferred to theIPLMN for an incoming call in the GMSC.T-CSI is for Mobile Terminating calls inthe GMSC.

CS GMSC 1

TIF-CSI Translation information Flag CAMELSubscription Information (TIF-CSI) istransferred to the VPLMN. TIF-CSI isused in the HLR for registering shortForwarded-to-Numbers (FTNs).

CS MSC \VLR

2

U-CSI USSD CAMEL Subscription Information(U-CSI) is held in the HLR; it is not sent toany other node. U-CSI is for USSDapplication (for the served subscriber).

CS HLR 2

UG-CSI USSD General CAMEL SubscriptionInformation (UG-CSI) is held in the HLR;it is not sent to any other node. UG-CSI isfor USSD application (for allsubscribers).

CS HLR 2

VT-CSI VMSC Terminating CAMEL SubscriptionInformation (VT-CSI) is transferred to theVPLMN at Location Update. VT-CSI isfor Mobile Terminating calls in theVMSC.

CS MSC \VLR

3

T able is based on [22078]


CAME L S ubscription Information (CS I)content

• T rigger Detection Point (DP2, DP12 etc)• gsmS CF address (Global T itle of the S CP)• S ervice Key (identifies the service logic in the S CP)• Default Call/S MS /GPRS Handling (Continue or Release, if

CAP dialogue fails )• Capability Handling (CAP protocol vers ion, not for MAP

CS Is)• T rigger criteria (e.g. dialled number, bas ic service, reason

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 theprogress of a call/short message/PDP context etc.

• S tate models cons is t of Detection Points (DP) and Point InCall (PIC) / Point In Association (PIA). DPs are reported to theS CP/CS E .

• T rigger Detection Point (T DP-R) is a detection point in whichCAP dialogue is initiated by the S S F .

• Event Detection Point (EDP) is reported only if S CP hasarmed so. An EDP can either be armed as:

- EDP-N: DP is reported and process ing continues in S S Fautomatically.

- EDP-R: DP halts process ing in S S F , process ing continueswhen the S CP sends down a final instruction (Continue,Connect, Release)


CAP over S S 7 s tack

S S F Application S W

CAP

T CAP

MT P3

S CCP

MT P2

LI

S S F

S CP Application S W

CAP

T CAP

MT P3

S CCP

MT P2

LI

S CP

API Interface

F igure is based on [29078]


CAME L 3 in S GS N


CAME L 3 GPR S Attach/Detach S tateModel

Inter SGSNRouteing areaupdate

Attached

Attach request

Detached

User- or network initiateddetach

AD_Exception

Attach

Detached

Change of Position GPRS session

Intra-SGSN Routeingarea update

• DP Attach T DP-R• DP Change Of Position GPRS S ess ion

T DP-R , E DP-N• DP Detach E DP-N, E DP-R

S OURCE: [23078]


CAME L 3 PDP Context S tate Model

PDP ContextSetup Req

PDP_Context_Setup

PDP_Context_Established

Idle

C_Exception

PDP Context Est.

PDP ContextSetup Ack.

PDP Context Est. Ack.

Routeing area update

User or networkinitiated disc.

PDP ContextDisconnection

Routeing area update

Change ofPosition context

Change of Position context

• DP PDP Context E s tablishmentT DP-R , E DP-R , E DP-N

• DP PDP Context E s tablishmentAcknowledgement

T DP-R , E DP-R , E DP-N

• DP Change Of Position ContextT DP-R , E DP-R , E DP-N

• DP PDP Context DisconnectionE DP-N, E DP-R

S OURCE: [23078]


CAME L 3 S tate Model for MO S MS

• DP S MS _Collected_InfoT DP-R• DP O_S MS _Failure E DP-N, E DP-R

• DP O_S MS _S ubmitted E DP-N, E DP-R

SMS Analyse & Routing

SMS_ExceptionSMS Null & Start &Authorize

DP SMS_Collected_Info

DP O_SMS_Submitted

DP O_SMS_Failure

O_SMS_Exception

S OURCE: [23078]


CAME L 3 with GPR S Interworking• In the T able 12 above (based on

[23060, 23078]) four differentparameters describing CAMEL3effect on the PDP Context arepresented. At firs t, bas ic GPRSprocedures belong either toMobility (GPRS S ess ion) orS ess ion Management (PDPContext). T hen, number of DPsamong each s ignallingprocedure is presented; usually itvaries between 1-3. Next,affecting S tate Models are givenand finally, the type of CAPdialogue. T he CAP dialogue canbe PDP Context or GPRSS ess ion specific, i.e. individualPDP Contexts can be controlledwithin a group of active Contexts(per GPRS S ess ion; CAMELGPRS S cenario 1) or s inglebas is (per PDP Context; CAMEL

Table 12. CAMEL3 effect on GPRS Interworking.

GPRSSignallingArea

GPRS SignallingProcedure

Number of DPsencountered

State Models:Attach/Detachvs. PDP Context

Type of CAPDialogue:Session vs.Context

MM GPRS Attach 1 Attach/Detach Session

MM GPRS Detach 1 Attach/Detach Session

SM PDP ContextActivation

2 Both Both

SM PDP ContextModification

1 Both Both

SM PDP ContextDeactivation

2 Both Both

MM Inter SGSN RAU 2 Both Both

MM SRNC Relocation 2 Both Both

MM Intersystemchange (2G <->3G)

2 Both Both


GPR S S ess ion based CAME L DialogueHandling• T wo CAMEL S tate Models must be implemented:

CAMEL GPRS Attach/Detach

CAMEL GPRS PDP Context

• CAMEL GPRS Control and Interaction per GPRS S ess ionUE is in "Attached" s tate or goes from "Idle" to "Attached" s tate (during

Attach procedure) when CAMEL Interaction, T riggering or Continuing CAPcommunication in EDP-R/EDP-N, s tarts

CAMEL Interaction with S CP occurs within S ess ion Dialogue

CAMEL T riggering occurs once for the whole GPRS S ess ion in the sameS GS N

SGSN / SSP SCP

A/DSM

PDP#2SM

PDP#1SM

GPRS Dialogue

Information flow related toPDP Context #1

Information flow related tothe Session

Information flow related toPDP Context #2

S OURCE: [23078]


PDP Context based CAME L DialogueHandling

• S ingle CAMEL S tate Model must be implemented:CAMEL GPRS PDP Context

• CAMEL GPRS Control and T riggering per PDP Contextduring GPRS S ess ion

UE always in "Attached" s tate when CAMELinteraction starts and ends

All CAMEL activities occur within PDP ContextDialogue

SGSN / SSP SCP

PDP#2SM

PDP#1SM

GPRS Dialogue #2

Information flow related toPDP context #1

Information flow related toPDP context #2

GPRS Dialogue #1

S OURCE: [23078]


CAPv3 Operations for GPR STable 14. The CAP operations for GPRS Interworking.

CAP Operation Direction Purpose

ActivityTestGPRS SCP -> SGSN SCP tests CAP connection.

ActivityTestGPRSAck SGSN -> SCP SGSN acknowledges.

ApplyChargingGPRS SCP -> SGSN SCP sends threshold limitsand tsw (Prepaid).

ApplyChargingReportGPRS SGSN -> SCP SGSN reports transferreddata and/or elapsed time.

ApplyChargingReportGPRSAck SCP -> SGSN SCP acknowledges.

CancelGPRS SCP -> SGSN SCP cancels all DPs andreports.

ConnectGPRS SCP -> SGSN SCP gives new APN.

ContinueGPRS SCP -> SGSN SCP orders SGSN tocontinue suspendedprocessing.

EntityReleasedGPRS SGSN -> SCP SGSN informs SCP onabnormal event in SGSN.

EntityReleasedGPRSAck SCP -> SGSN SCP acknowledges.

EventReportGPRS SGSN -> SCP SGSN informs SCP on DPsencountered.

EventReportGPRSAck SCP -> SGSN SCP acknowledges.

FurnishChargingInformationGPRS SCP -> SGSN SCP gives free formatcharging data into CDR.

InitialDPGPRS SGSN -> SCP Establishes CAP connection(1st operation).

ReleaseGPRS SCP -> SGSN SCP orders SGSN to releaseGPRS Session and/or PDPContexts.

RequestReportGPRSEvent SCP -> SGSN SCP orders SGSN to notify,when new DP is met.

ResetTimerGPRS SCP -> SGSN SCP refreshes gprsSSF

• T he CAP operationsbetween the S GS N'sgprsS S F and the S CP'sgsmS CF are presented innext page (T able 14, basedon [23078, 29078]). As it canbe seen, the GPRSInterworking includes 18different CAP operations forthe CAMEL3. T hose CAPoperations that are seen inF igures for the IN BasedPrepaid have been markedwith grey colour.


CAME L 3 with MO-S MS

Table 13. CAMEL3 effect on MO-SMS.

SMSSignallingArea

SMS SignallingProcedure

Number of DPsencountered

State Model Type of CAPDialogue

MO-SMS(packet-switched)

MO-SMSSending

2 MO-SMS MO-SMS

• In the T able 13 below (based on [23060, 23078])corresponding parameters for S MS S ending are presented.T he CAMEL3 affects only MO-S MS S ending (MT -S MS is aPhase4 issue). T hen, number of the DPs is , in the case of theMO-S MS , 2 due to the fact that the S CP must be contactedbefore and after MO-S MS sending has been occurred. T heMO-S MS includes only one S tate Model that is common forboth Domains (CS , PS ). T he MO-S MS CAMEL utilizes longT CAP dialogues. [23078].


CAPv3 Operations for MO-S MS

• T he CAP operationsbetween the S GS N'ssmsS S F and the S CP'sgsmS CF are presented inT able 15 (based on[23078, 29078]). As it canbe seen, the MO-S MSincludes 8 different CAPoperations for theCAMEL3. T hose CAPoperations that are seen inF igures for the IN BasedPrepaid have beenmarked with grey colour.

Table 15. The CAP operations for MO-SMS (PS + CS).


ConnectSMS SCP -> SGSN SCP gives new APN.

ContinueSMS SCP -> SGSN SCP orders SGSN tocontinue suspendedprocessing.

EventReportSMS SGSN -> SCP SGSN informs SCP on DPsencountered.

InitialDPSMS SGSN -> SCP Establishes CAP connection(1st operation).

FurnishChargingInformationSMS SCP -> SGSN SCP gives free formatcharging data into CDR.

ReleaseSMS SCP -> SGSN SCP orders SGSN to releaseMO-SMS Sending.

RequestReportSMSEvent SCP -> SGSN SCP orders SGSN to notify,when new DP is met.

ResetTimerSMS SCP -> SGSN SCP refreshes gprsSSFtimers.


CAME L 3 in MS C


CAME L 3 O-B CS M

O_Null & Authorise_Origination_Attempt_Collect_Info

O_Exception

Collected_Info

O_Answer

Basic Call transition

O_Disconnect

O_Active

Route_Select_Failure

O_Busy

O_No_Answer

O_Abandon

& Alerting

Routing

Analysed_Information

Analyse_Information

O_active_failure

invalid_information

O_routing_and_alerting_failure

• DP Collected_Info T DP-R• DP Analysed_Information

T DP-R

• DP Route_S elect_FailureT DP-R ,E DP-N, E DP-R

• DP O_Busy E DP-N, E DP-R• DP O_No_Answer E DP-N, E DP-R• DP O_Answer E DP-N, E DP-R• DP O_Disconnect E DP-N, E DP-R

• DP O_Abandon E DP-N, E DP-R

S OURCE: [23078]


CAME L 3 T -B CS M

T_Null

Terminating Call Handling

T_Exception

T_Active

Terminating_Attempt_Authorised

T_Answer

Basic Call transition

T_Busy

T_No_Answer

T_Abandon

T_Disconnect

T_active_failure

T_call_handling_failure

• DP T erminating_Attempt_AuthorisedT DP-R

• DP T _B usy T DP-R , E DP-N, E DP-R• DP T _No_Answer T DP-R , E DP-N, E DP-

R• DP T _Answer E DP-N, E DP-R

• DP T _Disconnect E DP-N, E DP-R• DP T _Abandon E DP-N, E DP-R

S OURCE: [23078]


CAME L 3 S tate Model for MO S MS

• DP S MS _Collected_InfoT DP-R• DP O_S MS _Failure E DP-N, E DP-R

• DP O_S MS _S ubmitted E DP-N, E DP-R

SMS Analyse & Routing

SMS_ExceptionSMS Null & Start &Authorize

DP SMS_Collected_Info

DP O_SMS_Submitted

DP O_SMS_Failure

O_SMS_Exception

S OURCE: [23078]


CAME L 3 with CS Phone CallTable 17. CAMEL3 effect on Circuit Switched Call Control.

CS PhoneCallSignallingArea

CS Phone CallSignallingProcedure

SubArea of Signalling StateModels:O-BCSMvs. T-BCSM

Number ofDPs in theState Model

MM IMSI Attach - - -

MM IMSI Detach - - -

CC Mobile OriginatedCall

- O-BCSM 8

CC Mobile ForwardedCall

- Both 8 + 6 = 14

CC Mobile TerminatedCall

• in GMSC

• in VMSC

T-BCSM 6

CC Interaction withSupplementaryServices

• Line Identification

• Call ForwardingServices

• Call Barring Services

• Call DeflectionServices

• Closed User Group

Both 8 + 6 = 14

MM Inter MSCHandover

- - -

MM Intersystem change(2G <-> 3G)

- - -

• T he CAMEL functionality affectsthe CS Domain in the followingareas [23078]: Circuit S witchedCall Control, S hort MessageS ervice, S upplementary S erviceInvocation, US S D, MobilityManagement, Control andInterrogation of S ubscription Dataand S ubscriber S tate andLocation Retrieval (T able 4,based on [23078]). Most of themare already within earlier CAMELPhases, i.e. Phase 1 and Phase2; introducing the CAMEL3 justbrings enhancements to theseareas. T he most importantCAMEL Application Area isCircuit S witched Call Control. Itincludes S tate Models and CAPs ignals for controlling CS PhoneCall (see T able 17, based on


CAP Operations for CS Phone CallTable 18. The CAP operations for Circuit Switched Call Control. MSC contains gsmSSF+ possibly internal SRF. IP contains gsmSRF.


ActivityTest SCP -> MSC SCP tests CAP connection.

ActivityTestAck MSC -> SCP MSC acknowledges.

ApplyCharging SCP -> MSC SCP sends threshold limitsand tsw (Prepaid).

ApplyChargingReport MSC -> SCP MSC reports transferreddata and/or elapsed time.

AssistRequestInstructions IP, MSC ->SCP

MSC, IP gives SCP info toassociate with InitialDP.

CallGap SCP -> MSC SCP activates/modifies/removes call gapmechanism from MSC.

CallInformationRequest SCP -> MSC SCP orders MSC to recordspecific info on single call.

CallInformationReport MSC -> SCP MSC reports SCP specificcall info of a single call.

Cancel SCP -> MSC SCP cancels all DPs andreports.

Connect SCP -> MSC SCP orders MSC to routethe call to a specificdestination.

ConnectToResource SCP -> MSC The ongoing call isconnected to IP (gsmSRF).

Continue SCP -> MSC SCP orders MSC tocontinue suspendedprocessing.

ContinueWithArgument SCP -> MSC SCP orders MSC tocontinue suspendedprocessing with modifiedinformation.

DisconnectForwardConnection SCP -> MSC SCP orders MSC todisconnect connection withIP (gsmSRF).

EstablishTemporaryConnection SCP -> MSC SCP orders MSC toestablish connection withe.g. IP (gsmSRF).

EventReportBCSM MSC -> SCP MSC reports SCP onencountered DP (call-relatedevent).

FurnishChargingInformation SCP -> MSC SCP gives free formatcharging data into CDR.

InitialDP MSC -> SCP Establishes CAP connection(1st operation).

PlayAnnouncement SCP -> MSC SCP gives IP instructions onplaying announcements/tones to subscriber.

PromptAndCollectUserInformation SCP -> MSC,IP

SCP interacts with thecalling party to collectinformation.

PromptAndCollectUserInformationAck

MSC -> SCP MSC, IP acknowledges

ReleaseCall SCP -> MSC SCP orders MSC toterminate the ongoing call.

RequestReportBCSMEvent SCP -> MSC SCP orders MSC to notify,when new DP is met.

ResetTimer SCP -> MSC SCP refreshes gprsSSFtimers.

SendChargingInformation SCP -> MSC SCP gives AoCinformation.

SpecializedResourceReport MSC -> SCP MSC, IP responses toPlayAnnouncementoperation (when

T able is based on [23078, 29078]


CAME L 3 in S ervice Platform


CAME L 3 in S ervice Platform

• T here must be implemented within the gsmS CF exactly thesame S tate Models , CAMEL Detection Points and CAPoperations as in the gprsS S F and the gsmS S F . Otherwise,CAP communication between these entities will not succeed.

• F rom the S ervice Platform point of view, it cons is ts of severalIN elements and components and gives various benefits forthe network operator, service provider and subscriber.


Own contribution: IN B ased Prepaidby the help of CAME L 3

IN Based Prepaid is used as an example to show,how CAMEL3 can be utilized in both CS and PSCore Domains


IN B ased Prepaid - Operation Principle• F rom the charging point of view, the prepaid is an addition to normal

charging. T his means in practice that charges for telecommunicationservices are applied to the prepaid service account by decrementing thisaccount in real-time. T he prepaid mobile subscriber may be notified abouthis/her real-time account information at the beginning, during, or at theend of the telecommunications service currently in use. When the accountbalance is low enough the subscriber is poss ibly notified (via S MS sendingor tone accouncements) so that the subscriber has a chance to refill theaccount. When the account balance drops below a pre-defined threshold,the subscriber’s use of telecommunications services is barred by theservice provider. T he Prepaid is applicable to CS Phone Calls , MobileOriginated (MO), Mobile Forwarded (MF) and Mobile T erminated (MT ),GPRS 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 subscriber is a CAMEL subscriber isprovis ioned to the HLR. All CS I elements available are downloaded fromthe HLR during Attach, Location Update and Inter S GS N RAU proceduresto the MS C/S GS N. T he S CP gives limits to the MS C (Apply Charging;time limit) and the S GS N (Apply Charging GPRS ; time, data or bothlimits), and they report those limits back in Apply Charging Report


IN B ased Prepaid in PS Core Domain• S ess ion Management

• PDP Context Activation• PDP Context Modification• PDP Context Deactivation

• Mobility Management• (UMT S ) GPRS Attach• (UMT S ) GPRS Detach• S RNC Relocation + Inter S GS N RAU

• MO-S MS S ending• Micro-Billing S cenario (CAMEL3 + OS A API)

ALL FIGURES ARE BASED ON [23060, 23078]


PDP Context Activation (ContextDialogue)

• PDP Context S tateModel

• DP PDP ContextEstablishment

• DP PDP ContextEstablishment 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.

The mobile subscriber can transfer data now. Simultaneously, Prepaid charging is going on, too.

The GPRS Session is going on and mobile subscriber tries to activate PDP Context, i.e. to start data transfer...

MS GGSN SCP3G-SGSN

Initial DP GPRS (DP PDP Context Establishment)

Request Report GPRS Event

Continue GPRS

Event Report GPRS (DP PDP Context Establishment Ack)

Apply Charging GPRS (maxTransferredVolume)

Continue GPRS

Activity Test GPRS

Activity Test GPRS Ack

Apply Charging Report GPRS (transferredVolume, active)

Apply Charging Report GPRS Ack

Activate PDP Context Request

Create PDP Context Request

Create PDP Context Response (Charging ID)



Event Report GPRS Ack

Furnish Charging Information GPRS

Apply Charging Report GPRS (elapsedTime, active)

Apply Charging GPRS (maxElapsedTime)

Apply Charging GPRS (maxTransferredVolume)Apply Charging GPRS (maxElapsedTime)


S GS N Initiated PDP ContextModification

• PDPContextS tate Model

• Point InAssociation(PIA)PDP_Context_Established

The GPRS Session is going on. This PDP Context is active and has new QoS parameters now.

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

MS GGSN SCP3G-SGSN

Apply Charging ReportGPRS (Volume, Negotiated QoS)

Apply Charging GPRS (maxTransferredVolume)



Update PDP Context Request

Update PDP Context Response

Modify PDP Context Request

Modify PDP Context Accept


MS Initiated PDP Context Deactivation

• PDP ContextS tate Model

• DP PDPContextDisconnection

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.

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

MS GGSN SCP3G-SGSN


Apply Charging ReportGPRS (transferredVolume, not active)

Event Report GPRS (DP PDP Disconnection met)

Continue GPRS

Deactivate PDP Context Request


Delete PDP Context Response

Deactivate PDP Context Accept




UMT S GPRS Attach (S ess ion Dialogue)

• GPRSAttach/DetachS tate Model

• DP Attach

• After Attach procedure,PDP Context(s) isactivated ->

• DPs PDP ContextEstablishment andPDP ContextEstablishment Ack(PDP Context S tateModel) for PDPContext areencountered; s ignallingis quite s imilar than inContext Dialogue(except that 'Initial DPGPRS ' is not sent anymore to S CP)

Mobile subscriber is attached to the Packet Switched Core Network Domain (there is credit left in his Prepaid account in SCP).

Mobile subscriber tries to attach to the Packet Switched Core Network Domain...

SCP HLR3G-SGSNMS

Attach Request

Insert Subscriber Data

Attach Accept

Insert Subscriber Data Ack

Initial DP GPRS (DP Attach)


Apply Charging GPRS (Tcp + Tsw for GPRS Session)

Continue GPRS

Furnish Charging Information GPRS (for GPRS Session)


UMT S GPRS Detach (S ess ion Dialogue)

• GPRS Attach/DetachS tate Model

• DP Detach


• DP PDP ContextDisconnection

The GPRS Session is over and the subscriber is detached from the Packet Switched Core Network Domain.

There may be several PDP Context Deactivations before DP Detach for GPRS Session is encountered...

The GPRS Session is going on. The mobile subscriber has stopped transferring data and tries to detach from the network...

SCPGGSN3G-SGSNMS

Detach Request


Delete PDP Context Response

Apply Charging Report GPRS (Data+Time; for PDP Context)


Event Report GPRS (DP PDP Context Disconnection)


Apply Charging Report GPRS (Time; for GPRS Session)


Event Report GPRS (DP Detach)


Detach Accept

Continue GPRS (for PDP Context)

Continue GPRS (for GPRS Session)

Furnish Charging Information GPRS (for PDP Context)



S R NC R elocation in old 3G-S GS N(S ess ion Dialogue)

• Attach/Detach S tateModel

• DP Detach, Change ofPos ition


• DP PDP ContextDisconnection, Change ofPos ition

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

Mobile subscriber is roaming between two Routing Areas. Data Transfer is possibly going on (mobile in PMM-Connected mode).

Source RNC detects that this SRNS relocation was successful (Iu-PS is released by the Old 3G-SGSN)

Establishment of Radio Access Bearers between Target RNC and new 3G-SGSN

Source RNC decides to initiate SRNS relocation...

SCPGGSNNew 3G-SGSNOld 3G-SGSNMS

Apply Charging Report GPRS (DataVolume, active)


Event Report GPRS (DP PDP Disconn., Change of Position)




Apply Charging Report GPRS (Time, for GPRS Session)



Event Report GPRS (DP Detach, Change of Position)



Forward Relocation Request

Forward Relocation Response

Update PDP Context Request

Update PDP Context Response

Forward Relocation Complete

Forward Relocation Complete Acknowledge


Inter S GS N R AU in new 3G-S GS N(S ess ion Dialogue)

• Attach/DetachS tate Model

• DP Change ofPos ition S ess ion

• PDP ContextS tate Model

• DP Change ofPos ition Context

Session Dialogue is active for GPRS Session and its different PDP Contexts in new 3G-SGSN now (Prepaid charging is going on).

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

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.

SCP

Prepaid account check. If no credit left, ’Release GPRS’ is sent back.

HLRNew 3G-SGSNMS

Update GPRS Location (Supported Camel Phases)

Insert Subscriber Data (GPRS-CSI + SMS-CSI)

Insert Subscriber Data Ack

Initial DP GPRS (DP Change of Position Session)

Request Report GPRS Event (Change of Position Context)


Apply Charging GPRS (Tcp + Tsw for GPRS Session)


Routing Area Update Accept

Event Report GPRS (DP Change of Position Context)




Apply Charging GPRS (Time, Data, Tsw for PDP Context)

Routing Area Update Request


MO-S MS S ending

• MO-S MS S tateModel

• DPS MS _Collected_Info

• DP O_S MS_S ubmitted

This MO-SMS Sending was successful. The GPRS Session is still going on.

SCP

SCP checks the Prepaid account. If no credit left, ’Release SMS’ is sent back.

Mobile subscriber is attached to the Packet Switched Core Network Domain. The GPRS Session is going on. The subscriber tries to send a mobile-originated SMS (MO-SMS).

SMS-IWMSC

MO-SMS is sent to SMS Centre.

3G-SGSNMS

SMS Message Transfer

Initial DP SMS (DP SMS Collected Info)

Request Report SMS Event (DP O-SMS-Submitted)

Continue SMS

ForwardShortMessage

Delivery Report

Event Report GPRS (DP O-SMS-Submitted)

Delivery Report


IS MF with OS A API for m-Commercepayments

• In the F igure 56 below(based on [Gre01, Lil01,23060, 23078, 29998])the mobile subscriberreads an electricnewspaper from acommercial Internet S ite(News S ervices) andpays for that in real-timeutilizing his Prepaidaccount within the S CP.T he s ignalling is shownin the s ituation, wherethe S ervice Access hasalready been granted bythe Core Network(S ervice Access level isnot shown). Usually, thePrepaid account iscommon for both theCore Domains. As it canbe seen, the gsmS CFdoes not handle servicelogic execution anymore. T he service logicexecution is under theAPPS E's respons ibilitynow (poss ibly outs ideCore Network, if it isowned by the 3rd partyservice provider).

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 inreal-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, thethe mobile subscriber leaves this Server -> IN Platform asks 3G-SGSN to report all transferred data / elapsed time...3G-SGSN responds for that...

Prepaid account is deducted. The same sum (volume/time/real money) is delivered to the APPSE, too.

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.

APPSEData Session ManagerData SessiongsmSCF/SCPHLRgprsSSF/3G-SGSN

Context creation in GGSN successful.

MS

enableDataSessionNotificationforward

AnyTimeModificationInsert Subscriber Data (GPRS-CSI)

Activate PDP Context RequestInitial DP GPRS

forwarddataSessionEventNotify

connectReq

forward


Connect GPRS

Event Report GPRS

forwardconnectRes

superviseDataSessionReq

forward

Apply Charging GPRS

Apply Charging Report GPRS

forwardsuperviseDataSessionRes


connectReqforward


Continue GPRS



IN B ased Prepaid 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 tablishment

• CAMEL3 O-BCS M• DP Collected_InfoMobile subscriber is attached to the Circuit Switched Core Network Domain and tries to make a phone call...

Circuit Switched Phone Call is established between A and B subscribers.

PSTNSCPVMSC/VLRMS

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


Mobile Originated Call R elease

• CAMEL3 O-BCS M

• DPO_Disconnect

SCP ordered VMSC to terminate the CS phone call immediately. Thus, the mobile subscriber is detached from the Circuit Switched Core Network Domain.

Mobile subscriber is attached to the Circuit Switched Core Network Domain and CS phone call is going on. Time limit expires.

PSTNSCPVMSC/VLRMS

Apply Charging Report (Time limit)


ReleaseCall

ISUP_REL

Release



Mobile T erminated Call E s tablishment

• CAMEL3 T -BCS M

• DP T erminating_Attempt_Authorized

Circuit Switched Phone Call is established between A and B subscribers.

Mobile subscriber is attached to the Circuit Switched Core Network Domain and receives a phone call...

VLR/VMSC-BSCPHLRGMSCPSTN

ISUP_IAM( MSISDN)

MAP-SRI( MSISDN, SupportedCamelPhase, GMSC#)

MAP-SRI-ack( O-CSI, T-CSI, VLR# )

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


Mobile T erminated Call Release

• CAMEL3 T -BCS M

• DPT _Disconnect

Mobile subscriber is attached to the Circuit Switched Core Network Domain, and the call is terminated.

Mobile subscriber is attached to the Circuit Switched Core Network Domain and terminates the ongoing call...

VLR/VMSC-BSCPHLRGMSCPSTN

ISUP-REL

ApplyChargingReport (Time limit)

EventReportBCSM( T_Disconnect, leg-B etc)


Continue

ISUP-REL


L ocation Update (M-CS I not present)• With the M-CS I,

CS CoreNetworkDomain Attachand Detachprocedures canbe reported tothe gsmS CF,too. In theCAMEL Phase3, however,Inter S ystemChangebetween the2G-MS C andthe 3G-MS C, isnot vis ible tothe gsmS CF.[Net01f]

• F igure is basedon [23018,

HLRMSC/VLRMS

LocationUpdatingRequest

MAP-UpdateLocation(supportedCamelPhases)

MAP-UpdateLocation_Acknowledgement (CSIs)

LocationUpdatingAccept


Conclus ions (1/2)

• T he service control experiences a real evolution: more playersin the field, new technologies (terminal, radio access , corenetwork), network operators must open their networks forother companies (wholesaling), new value chain models , newbus iness models , multiple service scenarios . T he mostimportant concept is the VHE .

• T he IN shall have a role in the future mobile networks ; but therole of the IN changes from the sole technology to just onetechnology alternative in 3G service creation and control. T hemost important benefits of the IN are safe and secure solutionand standardized, open interfaces. T he biggest drawback isthat all IN based solutions are quite expens ive for the networkoperator.


Conclus ions (2/2)• T he CAMEL Phase 3 architecture affects the R99 UMT S network

by introducing INCM entities (S S Fs) in the core network. T heutilized protocols are CAP and MAP that increase S S 7 s ignallingload of the network. T he most important service is Prepaid. T hePrepaid concept may be later enhanced towards m-Commerce anddifferent micro-billing scenarios . T he main purpose of the CAMEL isto give roaming support for subscribers moving outs ide HPLMNarea.

• T he CAMEL Phase 3 core network s ignalling can utilize APIs , suchas OS A and Parlay API, for more flexible service control betweenthe network and the service layer. By the help of the APIs , theservice layer devices do not have to know the details of the corenetwork at all. T his makes poss ible more flexible and rapid serviceand application development especially for the 3rd parties . T heCAMEL and APIs together create more value for all participantswithin the 3G product value chain: operators and applicationdevelopers get more revenue and a mobile subscriber is entitled to


R eferences (1/3)[21978] 3GPP T echnical Report 21.978: CAMEL Control of VoIP

S ervices , 3GPP T S G CN, vers ion 3.0.0, June 2000

[22078] 3GPP S ervice Description 22.078: Customized Applications for Mobilenetwork Enhanced Logic (CAMEL); S ervice description - 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 echnicalrealization, 3GPP T S G CN, vers ion 3.8.0, June 2001

[23060] 3GPP T echnical S pecification 23.060: General Packet Radio S ervice(GPRS ); S ervice description; S tage 2, 3GPP T S G S A, vers ion 3.8.0,June 2001

[23078] 3GPP T echnical S pecification 23.078: Customized Applications for Mobilenetwork Enhanced Logic (CAMEL) Phase 3 – S tage 2, 3GPP T S GCN, vers ion 3.9.0, June 2001

[29002] 3GPP T echnical S pecification 29.002: Mobile Application Part (MAP)specification, 3GPP T S G CN, vers ion 3.9.0, June 2001

[29078] 3GPP T echnical S pecification 29.078: Customized Applications for Mobilenetwork Enhanced Logic (CAMEL) Phase 3 – CAMEL ApplicationPart (CAP), 3GPP T S G CN, vers ion 3.8.0, June 2001

[Bak00] Bakker, J., McGoogan, J., Opdyke, W., Panken, F .: Rapid Development andDelivery of Converged S ervices Us ing APIs , Bell LabsT echnical Journal, Vol. 5, No. 3, Bell Labs, July-S eptember 2000

[Baz01] Bazin, C., Ceccaldi, B., Fouquet, G.: Prototype for a S ervice Architecture forNext Generation Networks , Intelligent Network Workshop, IEEE ,


R eferences (2/3)[Net01b] Nokia 3G S olution, WCDMA & EDGE, T echnical S ummary, Nokia Networks , March

2001

[Net01c] Nokia IN Platform, Product Description, Nokia Networks , June 2001

[Bos01] Bos , L., Leroy, S .: T oward an All-IP-Based UMT S S ystem Architecture, IEEENetwork, 0890- 8044/01, IEEE , January-February 2001

[Bre00] Brennan, R ., Jennings , B., McArdle, C., Curran, T .: Evolutionary T rends in IntelligentNetworks , IEEE Communications Magazine, 0163-6804/00, IEEE ,June 2000

[Coo01] Cookson, M., S mith, D.: 3G service control, British 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 inMulti-Access Networks , IEEE Communications Magazine, 0163-6804/02,IEEE , January 2002

[F in00] F inkelstein, M., Garrahan, J., S hrader, D., Weber, G.: T he Future of the IntelligentNetwork, IEEE Communications Magazine, 0163-6804/00, IEEE , June 2000

[Gre00b] Grech, M., McKinney, R ., S harma, S ., S tanaway, J., Varney, D., Vemuri, K.:Delivering S eamless S ervices in Open Networks Us ing Intelligent S erviceMediation, 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 Access to Enable Mobile InternetApplications in UMT S Networks , 3G Mobile Communication T echnologies,Conference Publication No. 477, IEEE , 2001


R eferences (3/3)[Hum98] Humphrey, J. : Interworking and the IN Platform ; Detailing the Development of the

GS M CAMEL S tandard for Interworking IN, T elecommunications , ConferencePublication No. 451, April 1998

[Lil01] Lilge, M.: Evolution of Prepaid S ervice towards a Real-T ime Payment S ystem, 0-7803-7047-3/01, IEEE , 2001

[Pal00] Palviainen K. : CAMEL3 T raining Material, Nokia Networks , 2000

[Q1204] IT U-T Recommendation Q.1204: Intelligent Network Distributed Functional PlaneArchitecture, IT U-T , March 1993

[Umt99] T he Future Mobile Market – Global T rends and Developments with a Focus onWestern Europe, Report No. 8, UMT S Forum, March 1999

[Umt00a] S haping the Mobile Multimedia Future – An Extended Vis ion from the UMT S Forum,Report No. 10, UMT S Forum, S eptember 2000

[Umt00b] Enabling UMT S T hird Generation S ervices and Applications, Report No. 11, UMT SForum, October 2000

[Umt00c] T he UMT S T hird Generation Market – S tructuring the S ervice Revenue Opportunities ,Report No. 9, UMT S Forum, S eptember 2000

[Umt01] T he UMT S T hird Generation Market – Phase II: S tructuring the S ervice RevenueOpportunities , Report No. 13, UMT S Forum, April 2001

[Vei00] Veikkolainen, S . : Evolution to 3G Core Network, Internal T raining Course, NokiaNetworks , October 2000MORE REFERENCES CAN BE FOUND FROM T HE T HES IS IT S ELF .

camel phase 3 in umts - tietoverkkolaboratorio - tkk · camel phase negotiation - 2g/3g issues •...

Documents