Xxa Presentation of 3GPP Charging Management-Sep 2004

7/31/2019 Xxa Presentation of 3GPP Charging Management-Sep 2004

1/46

1

Charging Management

in

3GPP SA5 SWGB

What the standards provide

Chair: Karl-Heinz Nenner (T-Mobile)Vice Chair: Gerald Grmer (Siemens AG)


2/46

2

SA5 SWGB

Rapporteur Group Structure

General Charging Session

Karl-Heinz Nenner(T-Mobile)

Bearer

ChargingSession

Benni Alexander

(Nokia)

IMS

ChargingSession

Gran Andersson

(Ericsson)

Service

ChargingSession

Gerald Grmer

(Siemens AG)


3/46

3

Table of contents

1. Motivation

2. Setting the scene for charging in 3GPP2.1 Charging Levels2.2 Charging Methods

3. Timeline

4. Release 64.1 Common Charging Architecture4.2 Common Interfaces and Applications

5. Additional Functionality5.1 The Online Charging System5.2 Flow based Bearer Charging


4/46

4

Motivation

The business principles behindThe Vendorbusiness paradigm:

to sell equipment to Operators, purpose of equipment is to build telecom networks

The Operatorbusiness paradigm: build and operate a (mobile) telecom network purpose of network is to provide end user services

The Customer usesand will be billed for- the end user services

Chargingis the central enabler for the end user billingthere will be no equipment sold, no network built and no service offered

unless the service can be billedcharging is at the core of the business for vendors and operators alike!


5/46

5

Motivation

The key terms in 3GPPaccounting: process of apportioning charges between the

Home Environment, Serving Network and Subscriber.

billing: function whereby CDRs generated by the charging

function(s) are transformed into bills requiring payment.

charging: a function within the telecommunications networkand the associated OCS/BD components wherebyinformation related to a chargeable event is collected,formatted, transferred and evaluated in order to make it

possible to determine usage for which the charged partymay be billed.

OCS: Online Charging System

BD: Billing Domain


6/46

6

Setting the scene for charging in 3GPP

Charging Levels

Bearer, Subsystem and Service charging

Charging Methods

Online versus Offline charging


7/467

Setting the scene

Charging Levels1. Bearer Charging, comprising

Charging for the Circuit Switched Domain Charging for the Packet Switched Domain (GPRS)

Charging for the I-WLAN

2. Subsystem Charging, i.e. IMS

3. Service Charging, comprising MMS LCS

More to come, e.g. MBMS, Push, Presence, Messaging

In future, OMA Services ?!


8/468

Setting the scene

Charging Methodsoffline charging:

Charging mechanism where charging information does notaffect, in real-time, the service rendered. The final result ofthis charging mechanism is the forwarding of CDR files to

the Billing Domain.

online charging:Charging mechanism where charging information canaffect, in real-time, the service rendered and therefore adirect interaction of the charging mechanism with

bearer/session/service control is required. The mechanismcomprises the execution of credit control and subscriberaccount balance management on the Online ChargingSystem.


9/469

Setting the scene

Bearer Charging :CS domainCS domain charging involves:

- the GMSC

- the MSC (server)

- the HLR- the EIR

Offline Charging:- CDR types for MOC, MTC,

IncGW, OutGW.

Online charging: CAMEL

TS 03.78/09.78 (GSM)

TS 23.078 / 29.078 (3GPP)

BillingSystem

VMSCServer

CS Domain

CDR

CDR

MGW

GMSCServer

MGW

HLR

SCF

CDR

Mc

Mc

BillingSystem

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

SCF

CDR

Mc

Mc

CAP

CAP

CDR

BillingSystem

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

SCF

CDR

Mc

Mc

BillingSystem

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

SCF

CDR

Mc

Mc

CAP

CAP

CDR

C

D

IuCSA IuCSA

BillingSystem

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

SCF

CDR

Mc

Mc

BillingSystem

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

SCF

CDR

Mc

Mc

CAP

CAP

CDR

BillingSystem

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

CDR

Mc

Mc

PSTN

BillingDomain

VMSCServer CDR

CDR

MGW

GMSCServer

MGW

HLR

gsm

SCF

CDR

Mc

Mc

CAP

CAP

CAP

CDR

C

IuCSA IuCSA

gsmSSF

gsmSSF


10/4610

Setting the scene

Bearer Charging :CS domainBasic principles

call records per call/duration

Multiple partial records for long calls

Tariff Time Change captured within CDR

All service invocation information inside CDRs

Major CS charging parameters Origination / Destination of call Invoked services (BS, TS, SS) Radio resource usage for data

Special Cases SMS (supported from the early days)

Mobile Originated SMS CDR Mobile Terminated SMS CDR

LCS (supported as of Rel-4) Mobile terminated location request CDR Mobile originated location request CDR Network induced location request CDR


11/4611

Setting the scene

Bearer Charging :PS domainPS domain (GPRS) charging

involves the SGSN and theGGSN

Offline Charging:- M-CDR records MM items whenuser is GPRS attached

- S-CDR and G-CDR capture PDPcontext charging

Online charging:

CAMEL based TS 03.78/09.78 (GSM)

TS 23.078 / 29.078 (3GPP)

Diameter based Built upon IETF DCC


12/4612

Setting the scene

Bearer Charging :PS domainBasic principles

There is no concept of service invocation, all traffic is plain IP

There is no concept of mobile termination, but uplink and downlink trafficinstead

CDRs are generated per user connection (PDP context)

CDRs are time and volume based Each CDR contains one or more volume containers, characterised by QoS and

Tariff Time

Uplink and downlink volume counted separately

Non-volatile storage of CDRs on the CGF

Major GPRS charging parameters User ID (origination) as in CS

APN (destination) Time, data volume, QoS

Special Cases: SMS and LCS as in CS domain


13/4613

Setting the scene

Bearer Charging :WLANWLAN: an interworking architecture for non-3GPP WLAN (i.e. 802.11)

with the 3GPP core network

In Rel-6, there are two relevant interworking scenarios

Scenario 2 is a SIM based authentication/authorisation, providing IPconnectivity via the WLAN Scenario 3with Access to 3GPP services (IMS, SMS, MMS, ) on top

of the above

Charging functionality is currently being specified in SA5 Will be similar to GPRS

Will make use of IETF AAA technology (use of Diameter) Time and data volume to be counted

in WLAN only in scenario 2 reported to VPLMN

in WLAN, VPLMN AAA and HPLMN AAA in scenario 3, where user traffictraverses VPLMN and HPLMN


14/4614

Setting the scene

Subsystem Charging

IP Multimedia Subsystem (IMS)

P-CSCF

M Subsystem

CSCFMGCF HSS

Cx

IP Multimedia Networks

IM-MGW

PSTN

Mc

Mb

Mg

Mm

MRFP

Mb

Mr

Mb

Legacy mobile signalli

CSCF

Mw

Go

PCF

Mw

Gm

BGCFMjMi

BGCF

Mk Mk

C, D, Gc, Gr

UE

Mb

Mb

Mb

MRFC

SLFDx

Mp

PSTN

PSTN


15/4615

Setting the sceneSubsystem Charging

IMS Charging : GeneralsProxy Call Session Control Function (CSCF)

Determines applicable I-CSCF Routes SIP signalling between UE and S-CSCF Resource control via embedded PCF

Serving CSCF Responsible for session control Interacts with service platforms May behave as SIP proxy or user agent

accepts requests and services them internally or translates / forwards them on may terminate and independently generate SIP transactions

Interrogation CSCF Determines applicable S-CSCF

Routes SIP signalling to / from foreign networks (Roaming)

Application Server Provides any kind of service Services are not standardised in the 3GPP specifications Examples: movie / music clips, news flash, soccer goals, .


16/4616

Setting the scene

Subsystem Charging

IMS Charging : Basic principlesCDRs are generated per IMS session / duration

Tariff Time Change is captured within CDR

All media component invocation information is inside the CDRs Each CDR contains one or more media component descriptors AS information is captured, if AS(s) is / are involved

many similarities with CS charging, BUT Completely different, distributed charging architecture

ACR start / stop / interim are generated per SIP message

CDRs are generated by CCF and then sent to BD

ACRs and CDRs are asynchronous

No transport network infomation (e.g. radio resources) If correlation with GPRS CDRs required, this is done by cross-

correlating GPRS and IMS Charging IDs

Correlation between IMS CDRs is required (e.g. CSCF CDRs, AS CDRs)all CDRs contain the same IMS Charging ID


17/4617


IMS Charging : Aspects

Major IMS charging parameters Origination / Destination of session Invoked media components (audio, video, etc.)

AS information, if applicableOffline Charging with 7 CDR types: 1 each per IMS node type P-CSCF captures session related information S-CSCF captures similar information as the P-CSCF, but

only S-CSCF CDR has AS related information

only P-CSCF CDR has information on authorised QoS

I-CSCF captures user registration events

AS captures service invocation information Others (more details in special cases below):

interworking with CS services

Conferencing

Online charging only in S-CSCF, AS and MRFC


18/4618


IMS Charging : Special cases

SIP Events create ACR Events instead of start/interim/stop messages SIP NOTIFY

SIP MESSAGE

SIP REGISTER SIP SUBSCRIBE

SIP Final Response indicating an unsuccessful SIP session set-up

SIP Final Response indicating an unsuccessful session-unrelated procedure

SIP CANCEL, indicating abortion of a SIP session set-up

I-CSCF completing a HSS Query that was issued for a SIP INVITE

AS service invocation events

CS interworking Several nodes support CS interworking, i.e. MGCF, MGW, BGCF

MGCF and BGCF can generate call related CDRs

Conferencing MRFC and MRFP provide conferencing capabilities (H.248)

MRFC can generate related CDRs


19/4619

Setting the sceneService Charging

Multimedia Messaging Service (MMS)

MM1

MM6MM7

MM4

MM1

MM3

...

Relay

MMS User

Agent A

External

Server #1

(e.g. E-Mail)

External

Server #2

(e.g. Fax)

External

Server #N

ForeignMMS

Relay/Server

MMS User

Agent B

Server

MMS Relay/Server

MM2

External

Server #3

(e.g. UMS)

MM5

MMS User

Databases

HLR

MMS VAS

Applications

MM9

Online

Charging

System

MM8

Post-

processing

System


20/4620


MMS Charging : Generals

Multimedia Messaging Service (MMS) is based on a specificservice node called the MMS Relay / Server (MMS R/S)

Originator MMS R/S serves the MM originator

Recipient MMS R/S serves the MM recipient

Inter-MMS R/S traffic uses SMTP (email)

Differences to SMS: Only one MMS R/S involved for intra-PLMN MM transfer, e.g. T-D1 to T-

D1 2 MMS R/S involved if originator and recipient are subscribed to

different networks (e.g. T-D1 to Vodafone) In SMS, only one SMSC is involved In contrast to SMS, MMS charging is standardised in the service area

(i.e. the MMS R/S), not the bearer domain (MSC/SGSN)


21/46

21


MMS Charging : Basic principlesThe MMS R/S collects charging information such as:

destination / source addresses used by the User Agent (UA)

identification of the MMS R/S(s) involved in the MM transaction the size of the MM and its components

storage duration, i.e. the time interval when a MM is saved on a non-volatile memory media identification of the bearer resources used for the transport of the MM,

i.e. the identity of the network and the network nodes

In scenarios involving a VASP, the charging information describesthe identification of the VASP and the amount of user data sentand received between the MMS R/S and the VASP.

The information listed above is captured for use cases in relationto: MM submission, retrieval and forwarding transactions involving the MMbox transactions involving a VASP


22/46

22

Setting the scene

Service Charging

MMS Charging : AspectsMajor charging parameters

Originator and Recipient (user agent & network)

MM volume (size)

Offline Charging MM1 CDR types to enable end user billing

MM submission, retrieval and forwarding Read reply, delivery report, notification, deletion Upload, download, removal from / to MMBox

MM4 CDR types intended for inter-network accounting MM exchange between MMS R/S in different networks

Read-reply and delivery reports MM7 CDR types for VASP transactions

Submission and cancellation Read-reply, delivery reports

Online Charging with Diameter Credit Control


23/46

23

Setting the scene

Service Charging

LoCation Service (LCS)

VGMLC

2G-MSC

3G-SGSN

2G-

SGSN

MSCserver

GERAN

UTRAN

UE

gsmSCF

LgGb

A

Lg

Lc Le

Iu

HSS/HLR

Iu

Iu

Lg

Um

UuLg

Lh

OSA-LCSExternal LCS

Client

Iu HGMLC RGMLCLr Lr

Lh

VPMLN

PPR

Lpp

PMD

Lid

Lid

PMD


24/46

24

Setting the scene

Service Charging

LCS Charging : Generals Charging information in the Service domain (GMLC) is collected

for inter-operator accounting purposes; a network requestinglocation info may be charged by the network providing thelocation info

The main charging parameters collected by the GMLCs are: Identity of the mobile subscriber to be located Identity of the entity requesting the location Identity of the GMLC or PLMN serving the LCS client

the quality of the location requested by / delivered to the client date / time the location procedure was requested by the client Usage of continuous/periodic tracking

LBS information, describing the service specific parameters inaddition to the above location resource information

The information listed above is captured for all BC use cases: Mobile Originated Location Request

Mobile Terminated Location Request Network Induced Location Request


25/46

25

Timeline of charging TS

Bearer, Subsystem and Service charging

Releases

Online & Offline charging


26/46

26


CS and PS domainsCS Offline Charging

TS 12.05 (GSM until Rel-98)

TS 32.005 (3GPP Rel-99)

TS 32.205 (3GPP Rel 4/5)

TS 32.250 (3GPP Rel-6)

PS Offline Charging

TS 12.15 (GSM Rel-97/98)

TS 32.015 (3GPP Rel-99) TS 32.215 (3GPP Rel 4/5)

TS 32.251 (3GPP Rel-6)

CS & PS Onlinecharging:CAMEL

TS 03.78/09.78 (GSM) TS 23.078 / 29.078 (3GPP)

PS Online Charging:based on IETF DCC

TS 32.251 (Rel-6)


27/46

27


IMS and Service ChargingIMS: Offline & Online Charging

TS 32.225 (3GPP Rel-4/5) -> TS 32.260 (3GPP Rel-6)

S-CSCF uses ISC interface for online charging

MMS: Offline Charging TS 32.235 (3GPP Rel-4/5) -> TS 32.270 (3GPP Rel-6)

Online Charging TS 32.270 (3GPP Rel-6)

LCS Offline & Online Charging

TS 32.271 (3GPP Rel-6)

As a major change, Rel-6 sees the introduction of commoncharging architecture, interfaces and applications for all3GPP charging


28/46

28

3GPP Release 6

Common Charging Architecture

Common Interfaces and Applications


29/46

29

Charging Standards Rel-6

Getting more organisedEvery new technology came with its own charging solution

Each domain was done independently

Each domain has its own functional description and interfaces

Result: Too many different architectures and solutions

HoweverFrom an abstract viewpoint, its always the same functionality,

regardless of system / technology Chargeable / billable items (events)

Calls / Sessions

Service Events

The same basic tasks Collect charging relevant information (usually from signalling parameters) Create CDRs / perform online credit control

Forward CDRs to billing domain

Identical information flow from network to Billing Domain / OCSaccording to the above basic tasks


30/46

30


Charging ArchitectureBilling Domain

ONLINE CHARGINGOFFLINE CHARGING

WLAN

BGCF

MGCF

MRFC

SIP AS

CRF

AF

CDF

TPF

CS -NE

SGSN

GGSN

CGF

OCSIMSGWF

P -CSCF

I-CSCF

S -CSCF

Service -NE


31/46

31


Common offline charging architecture

CN

Domain

Service

nodes

Sub-system

Billing

Domain

Rf Ga Bx

C

T

F

C

D

F

C

G

F

3GPP network


32/46

32


Common offline charging architectureCharging Trigger Function

Collects Metrics from the core system, based on system specifictriggers (e.g. signalling events)

Formats these metrics into charging events forwards charging events to the CDF via Rf reference point

Charging Data Function Collects charging events and formats them into CDRs according to

system specific rules Forwards CDRs to CGF via Ga reference point

Charging Gateway Function Provides non-volatile CDR file store

Uses Bx reference point for CDR file transfer to Billing DomainBilling domain Receives CDR files from CGF No further standardisation


33/46

33


Common online charging architecture

CN

Domain

Service

element

Sub-

system

Ro

C

T

F

3GPP network

CAP

O

C

F

ABMF

RF

OCS

Rc

Re


34/46

34


Common online charging architectureCommon approach for online charging

Same Diameter based interface (IETF Diameter CCA)

Same source collection (building on CTF)

CS and GPRS will retain CAMEL

GPRS will also see the addition of the Diameterinterface to GGSN; same as WLAN

All new Rel-6 services (MBMS, Push, Presence,Messaging, ) will use same offline and online

charging functions


35/46

35


Structure of TS series32.240Charging Architecture

and Principles

32.250

CS-domainCharging

32.251

PS-domainCharging

32.252

WLANCharging

32.260

IM SubsystemCharging

32.270

MMSCharging

32.271

LCSCharging

32.295Charging Data

Record (CDR)transfer

32.297Charging Data

Record (CDR) file

format andtransfer

32.298

Charging Data

Record (CDR)

parameterdescription

32.299Diameter

ChargingApplication

32.27x

x ServiceCharging

32.296

Online Charging

System (OCS)

applications andinterfaces


36/46

36


Structure of TS seriesTS 32.240 Architecture and Principles Common online and offline charging architecture

General principles of Charging

One Middle Tier TS per domain / subsystem / service

Mapping of common architecture onto specific domain Domain / subsystem / service specific charging functionality,

especially type and content of CDRs and ACRs

Common interfaces and applications between the entities ofthe common architecture Rf and Ro Diameter application (TS 32.299)

Bx interface to Billing Domain (TS 32.297) Ga interface between CDF and CGF (TS 32.295)

CDR Parameter and ASN.1 Syntax Description (TS 32.298)

Special case: Online Charging System (OCS) (TS 32.296)


37/46

37

Additional functionality

The Online Charging System

Flow based Bearer Charging


38/46

38



39/46

39

The Online Charging SystemThe following components of an OCS have been identified

Charging functions for Session based charging

Event based charging

Account Balance Management Function (ABMF) Holds subscriber account

Controls addition / deduction of monetary amounts from account

Performs credit reservation on the account Management of counters applicable for the account

Rating Function (RF) unit determination: calculation of a number of non-monetary units

(service units, data volume, time and events);

price determination: calculation of monetary units (price) for agiven number of non-monetary units; tariff determination: determination of tariff information based on

the subscribers contractual terms and service being requested; Management of counters applicable for rating


40/46

40


TS 32.296: OCS applications and interfacesConfined to Re (Rating) interface in Rel-6

Two approaches are being standardised1. Rating engine model (Class A)

Charging function fetches data from the Account Balance

Management Function Charging function issues rating request towards the Rating

Function Charging function triggers counter / account update on the

Account Balance Management Function Design goal: allow common Rating Function for online & offline

charging

2. Extended rating engine model (Class B) Similar to the above, but the rating function also stores and

manages some of the counters needed for the rate calculation Requires additional scenario on Re to acknowledge service

delivery and counter update


41/46

41


Problem StatementThe problem:

Charging for bearer resources does not take into account thevalue of services accessed via these bearer resources

Integrated service pricing: when the tariff model calls for

subscribers paying for the service (e.g. MMS), the charges forbearer usage must be removed

Due to different bearer charges in roaming and non-roamingcases, the service price must depend on whether the customer ison the HPLMN or roaming on a foreign network

The solution: Make bearer charging service aware

Make service charging access aware

Make bearer and service charging roaming aware


42/46

42


Functionality Differentiate between different service data flows for the

purpose of charging, e.g. Web browsing IP Video Telephony MMS versus WAP traffic

.

Applicable to GPRS (GGSN TS 32.251) and WLAN (PDG)charging

Charging rules for online / offline charging are predefinedor provided from a CRF (TS 29.210)

Charging rules determine the CDR generation (offlinecharging) and credit control procedure (online charging)


43/46

43

Backup


44/46

44

Service Based Local Policy

(SBLP) :Introduction SBLP was defined in Rel-5 to enable the IMS to

control the QoS provided by the GPRS bearerservice based on the requirements of the

negotiated application services.

This is based on particular interest if the beareruses a high QoS and/or if an operator uses IMSnetwork entities to charge application services.

In Rel-6 the concept was extended for non-IMSapplication functions.


45/46

45


(SBLP) :ArchitectureUE

AF(e.g P-CSCF)

GGSN

PDF

Gq

GoPEP

User Plane

AF sessionsignallinge. g SIP

GPRS bearers


46/46


(SBLP) :Functions Policy Enforcement Point (PEP)

Policy Decision Function (PDF)

Application Function (AF)

Xxa Presentation of 3GPP Charging Management-Sep 2004

Documents

Transcript of Xxa Presentation of 3GPP Charging Management-Sep 2004