IP Data Charging

(Overview of Nokia Siemens Network´s solution for

Session and Event Charging of IP data traffic)

Patricia Krenz
Mch/M
05th November 2009

For internal use

1 © Nokia Siemens Networks <Presentation> / <Author> / 16 Oct 2022
Agenda

• IP Charging - Overview
• IP Use Cases
– at Corba-Interface: event charging (mainly pre-rated)
– at Diameter-Interface: charging of session and events
▪ Events like MMS and SMS
▪ Sessions based on PDP context or dedicated service sessions
– IP service configuration
▪ IT-configuration (Web-TPD)
▪ Service configuration (SMAF)
– Rating parameter configuration (TariffTool)
• IP service ticketing
– Corba-service based tickets
– Diameter-service based tickets
For internal use
2 © Nokia Siemens Networks Presentation / Author / Date
Before we start…

There will be
much information
presented (even
in one slide) but
don´t worry it´s
just for providing
you an overall
look of the IP-
Charging World…

For internal use

3 © Nokia Siemens Networks Presentation / Author / Date
IP Charging – Overview
Agenda

• IP Charging - Overview
– Session and Event charging
– Network embedding
– NSN Charging approach
– Diameter based IP data online charging

For internal use

4 © Nokia Siemens Networks Presentation / Author / Date
Modes of online charging

Session charging: Event charging:

 For continuous services (e.g. streaming)  For discrete services like
the final price is not known at service start, messaging, the price can be
thus it can not be charged or reserved as a calculated completely before
whole beforehand. service usage.
 The charging system grants a number of  Quota handling is obsolete.
service units, e.g. minutes for voice calls or
volume of data, to the charging client. If
these units are used up, new units are
granted. At session termination, the
balance is adjusted according to the
service unit used.

For internal use

5 © Nokia Siemens Networks Presentation / Author / Date
Application Charging Models
MNO Example
Class

Applications & Content

On-Net Services
MNO/Partner
Services

Off-net Services
(Premium)

(Premium)
Messages

Download
Internet
Content
Use Cases Model

Event Time / Volume

IP Event IP sessions

For internal use

6 © Nokia Siemens Networks Presentation / Author / Date
IP Session and Event charging

Charge@once - Access Interfaces supporting IP data online

charging
Payment Corba

(Payment PlugIn (PPI),

Online IF proprietary)
(propr.)
Ro Diameter

(3GPP, VF-propr.,
Radius
NSN-FISN-based)
GTP´
(GPRS Tunnel
Protocol)

Event Session & Event

Note: GTP´ will be not released anymore from c@o select v1.6
For internal use onwards
7 © Nokia Siemens Networks Presentation / Author / Date
IP-Charging – Overview
Network-Embedding - charge@once select IP-environment
Management Service/User
SMAP Application Management
GUI
Corba Corba, http http
FTAM, (S)FTP

User
Repository LDAP @Commander
SNMP, Corba,
charge@once select FTP, UDP

proprietary B&R
AAA Networker IF
Server Radius

Online IF

Ro/
GTP´ Diameter Ro/ Payment
Diameter PlugIn
Voucher eGGSN
Manageme Packet Appl. Server as
Inspector (IPS, Flexi ISN), MMSC, e.g. SMSC,
nt System PoC Server SMSC
(VoMS) (CSG) MMSC
IP IP
Session Event
For internal use
8 © Nokia Siemens Networks Presentation / Author / Date
IP-Interfaces

• Application Server:
• 3GPP standardized:
Support of Ro/Diameter based event charging via Multimedia Messaging
Service Center (MMSC) or Short Message Service Center (SMSC)
• Proprietary:
- Support of event charging based on the Payment PlugIn for application
servers as e.g. Short Message Service Center (SMSC), Multimedia
Messaging Service Center (MMSC)
- Support of VoMS-based recharging via Online-Interface

• IP Traffic Analyzer:
• Support of Ro/Diameter based session and event charging via a packet
inspector as enhanced Gateway GPRS Support Node (eGGSN)
• Support of GTP' based session and event charging via a packet inspector as
Content Services Gateway (CSG)

For internal use

9 © Nokia Siemens Networks Presentation / Author / Date
Charging Approach
Charge at the most appropriate layer only
Avoid cumbersome correlation

Application Layer
• Single point of charging
 Application specific charging (e.g. for each service
mobile TV, Games, PoC…)
Applic.  Content-based • Suppress charging in
Server  3rd party
other network elements:
by APN, IP addresses,
IMS Session Layer
static or dynamic
 Charging for IMS-controlled sessions charging rules
(e.g. rich voice call)
 Time-based IMS session or event • Example: Charging at
CSCF  QoS based for media components
PoC-Server instead of
bearer charging and
Transport Layer IMS session charging
 Charging of data traffic at access
network (e.g. Internet access)
 Volume- or time-based or a
eGGSN combination of it
PoC: Push-to-Talk Over Cellular

For internal use

10 © Nokia Siemens Networks Presentation / Author / Date
Charging Approach
Recommended data charging approaches
Service category Preferred charging NE initiating
method charging
3rd Party Services (e.g. Internet Session charging with unit eGGSN
Access, Yahoo-IM) reservation (time- or volume
based or a combination)
IMS-Services (without AS) Session charging with unit IMS (S-CSCF)
(e.g. Rich Voice Call, Chat ) reservation (time-based)

IMS-Services involving Session charging or / and event Appl. Server or

dedicated Appl. Server charging dependent on the service IMS (S-CSCF)
(e.g. PoC, IM, Presence) alternatively

Operator-based Content Event charging adapted to the Appl. Server or

Services (e.g. Ringtones, specific service eGGSN alternatively
Mobile TV)
Native 3GPP Message Immediate event charging Appl. Server
Services
(e.g. SMS, MMS)

For internal use NE = Network element

11 © Nokia Siemens Networks Presentation / Author / Date
AS = Appl. Server
NSN Diameter interfaces
Billing
Backend

Service
OCS OAM
Administration

Diameter Diameter

SMS RTR/ MMS Relay/

IMS Gateway IPC Client PoC Client
SMSC Server

The following interfaces are supported:

 Flow-Based Charging (FBC) acc. TS 32.251 (V6.3.0) (aka as 3GPP DCCA PS), session charging
 IMS Charging acc.  TS 32.260 (V6.5.0), event/session charging
 MMS Charging acc.  TS 32.270 (V6.6.0), event charging
 PoC Charging acc.  TS 32.272 (V6.3.0). event & session charging
 SMS Charging acc. TS 32.274 (V8.0.1), event charging (support from c@o select v1.6 onwards)

based on:
 IETF Diameter Credit Control Application (DCCA) (RFC 4006)
 Diameter charging applications acc. TS 32.299 (V6.6.0)
For internal use
12 © Nokia Siemens Networks Presentation / Author / Date
3GPP Online Charging architecture (TS 32.240)

charge@once as OCS
3GPP network
consists of
CN OCS OCF, ABMF and RF
Domain Rc and Re are not
Rc ABMF relevant
C O CAP is not relevant
Service
T Ro
element C
CAP
F F
Sub-
RF
system Re

CTF: Charging Trigger Function

OCF: Online Charging Function
ABMF: Account Balance Management Function
RF: Rating Function
For internal use
13 © Nokia Siemens Networks Presentation / Author / Date
Diameter protocol – main features

Diameter is an AAA protocol, which supports:

supports
Failover (on application level) => not supported by select!
Transmission level security (IPsec, TLS)
Reliable transport (TCP, SCTP) => TCP only by select!
Agent support (Relay, Proxy, Redirect, Translation)
Peer-to-Peer (client/server initiated messages)
Capability negotiation
Error notification
Delivery of attribute value pairs (AVPs)
Extensibility (new AVPs)
Radius backward compatibility

For internal use

14 © Nokia Siemens Networks Presentation / Author / Date
Layering of Ro Protocols (described in TS 32.240)

Available
since
IMS MMS SMS PoC PS/
VF CLCI c@o V1.1
FBC (V7.6.1)
(E2005)
[GPRS Available
TS TS TS TS TS
session since
32. 260 32.270 32.274 32.272 32.251 c@o V1.2
charging –
(V7.6.2)
IPS2.0
Available
3GPP Diameter extension (TS 32.299) Inter- since
working] c@o V1.6
[3GPP specific mapping of IETF AVPs; new optional AVPs
including the grouped Service-Information AVP;
adapted message flows]

Diameter Credit Control Application (IETF RFC 4006)

Diameter Base (IETF RFC 3588)

For internal use

15 © Nokia Siemens Networks Presentation / Author / Date
Diameter Base Protocol
The following commands based on RFC 3588 are supported from @vantage V7.6
onwards.
Command-Name Abbrev. Description Code

Capabilities-Exchange- CER/CEA Only sent by CTF; 257

Request/-Answer is sent to exchange local capabilities

Device-Watchdog- DWR/DWA Both direction; 280

Request/-Answer is sent to a peer when no traffic has been exchanged between two peers;
At c@o 40 sec. is configured

Disconnect-Peer-Request/- DPR/DPA Both direction; 282

Answer is sent to a peer to inform its intentions to shutdown the transport connection;
@vantage sends DPR message as follows:
In re-booting case
For overload protection at a specified upper level
In some hard error cases, e.g. invalid message length
In case the CTF does not respond a DWR with DWA

Abort-Session-Request/- ASR/ASA Sent by c@o; 274

Answer to request that the session identified by the Session-Id will be stopped

Re-Auth-Request/-Answer RAR/RAA Sent by c@o; 258

to request that the user be re-authenticated and/or re-authorized

Note: The commands STR/STA (Session Termination Request/Answer) and ACR/ACA

(Accounting Request/Answer) are not supported with @vantage V7.6.

For internal use

16 © Nokia Siemens Networks Presentation / Author / Date
Diameter Credit Control Application (DCCA)
The following commands based on IETF (Internet Engineering Task-Force) DCCA
(Draft 6) are supported from @vantage V7.6 onwards:
Command-Name Abbrev. Description Code

Credit-Control-Request/- CCR/CCA CCR is only sent by CTF; is sent to inquire quota 272
Answer CCA is sent by the OCS

The Diameter Credit-Control Application (DCCA) specifies an approach based on

a series of "interrogations":
 Initial interrogation
 Zero, one or more interim interrogations
 Final interrogation.
In addition to a series of interrogations, also a
 one time event (interrogation)
can be used e.g. in the case when service execution is always successful.
Summarized the following CCR types (AVP CC-Request-Type) are possible:
 CCR initial / update / terminate
 CCR event.

For internal use

17 © Nokia Siemens Networks Presentation / Author / Date
Agenda

• IP Charging - Overview
• IP Use Cases
– at Corba-Interface: event charging (mainly pre-rated)
– at Diameter-Interface: charging of session and events
▪ Sessions based on PDP context or dedicated service sessions
▪ Events like MMS and SMS
• IP service configuration
– IT-configuration (Web-TPD)
– Service configuration (SMAF)
• IP service ticketing
– Corba-service based tickets
– Diameter-service based tickets

For internal use

18 © Nokia Siemens Networks Presentation / Author / Date
IP Use Cases
at Corba-Interface: event charging (mainly pre-rated)

Use Cases
Name Operation
Immediate Charging chargeAmount
Payment in Parts/deferred payment authorizeAmount / captureAmount
Transfer transferAmount
Advice of Charge adviceOfCharge
Refund refundTA
Recharge rechargeAmount

Management Use Cases:

Subscribers Account List getConsumerAccountList
Subscribers state of a transaction getTAState

For internal use

19 © Nokia Siemens Networks Presentation / Author / Date
Payment PlugIN
Embedded Architecture

For internal use

20 © Nokia Siemens Networks Presentation / Author / Date
IP Use Cases
at Diameter Interface: charging of sessions and events
Agenda

• IP Diameter based Use Cases

– Session-based
▪ FBC Charging (Flow-based; acc. TS 32.251)
– Session and event based
▪ IMS Charging (IP Multimedia Subsystem; acc. TS 32.260)
▪ PoC Charging (Push-to-talk over Cellular; acc. TS 32.272)
– Event based
▪ MMS Charging (Multimedia Messaging Service; acc. TS 32.270)
▪ SMS Charging (Short-Message Service; acc. TS 32.274; from c@o select v1.5
onwards)
▪ “simple” event charging based on FBC
 Event Charging based on VF DCCA V2.0
 Event Charging based on Flexi-ISN V3.x (from c@o select v1.6 onwards)

For internal use

21 © Nokia Siemens Networks Presentation / Author / Date
IP Diameter based Use Cases – Session based
- FBC Charging - Architecture
 The inter-working with Cisco’s IPS 1) (consisting of eGGSN/SSG/CSG in one rack) or Flexi ISN
allows a standardized Session Charging via Ro/Diameter for IP traffic.
 eGGSN:
 analysis the IP packet streams and distinguishes between different URLs and traffic types
 requests further instructions and/or quota from charge@once V1.1ff and
 supervises the granted budget for time or volume.
 charge@once V1.1ff (‘Quota Server’):
 determines applicable rates dependent on provided IP information and subscriber data
 does quota calculation and
 instructs the eGGSN how to handle certain IP content (e.g. premium, blocking).

Radius User Self care

AAA charge@once V1.1ff
• Free Access

Local hosted Multimedia

Radius Ro/Diameter • Bill per Volume or Time
News (Quotes, Scores, Weather)
GTP´ • Bill per Time
eGGSN
Downloads (Ring tone, Screensaver)
• Bill per Click
aux. data flow charging flow bearer traffic
*1)
IPS2.0 phase-out at 12/08
For internal use
22 © Nokia Siemens Networks Presentation / Author / Date
 IP Diameter based Use Cases – Session based
- FBC Charging – Charging Method

The 3GPP TS 32.251 for FBC V6.3.0 defines for FBC charging the following Use
Case:
 Session Charging with Unit Reservation (SCUR).
This is used for
 Charging Data related to PDP contexts;
 Charging Data related to service data flows.

1. PDP context charging allows the GGSN to collect charging information

related to data volumes sent to and received by the UE/MS, categorised by
the QoS applied to the PDP context.
2. FBC is supported by the GGSN by the integrated TPF (Traffic Plane
Function; 3GPP terminology). When the TPF is present, the normal PDP
context charging is enhanced by the capability to categorise the PDP context
data volume by specific service data flows.

For internal use

23 © Nokia Siemens Networks Presentation / Author / Date
 IP Diameter based Use Cases – Session based
- FBC Charging – Traffic Flow and Rule concept
Rulebase 1
Example
One subscriber has 3 primary PDP Contexts Category_a (off-net)
open in parallel: Category_b (off-net)
2 Rulebases are assigned to the 3 PDP Contexts Category_c (on-net)
Category_d (enterprise)
Category_e (prohibited)
Rulebase1 assigned
to PDP Cxt #1 and #2
PDP Context #1:
interactive

PDP Context #2: GGSN FBC QS

SGSN
streaming
(c@o)
PDP Context #3:
background
Gn Gi
Rulebase2 assigned
Category to PDP Cxt #3
• defined by set of filter rules, e.g. IP-Address, URL
• identified by Rating-Group-ID at CLCI Rulebase 2
Rulebase Category_a (off-net)
• complete set of category definitions Category_f (off-net)
• different selection, based on APN, Category_g (on-net)
subscriber, roaming status, QoS, etc. Category_h (enterprise)
• identified by Rulebase-ID

For internal use

24 © Nokia Siemens Networks Presentation / Author / Date
 IP Session Setup (PDP context setup)
User Authentication & Authorization
1: PDP Context activation request
2: Authentication/Authorization
(User ID = MSISDN)
3: Authentication Accept
4: Open GPRS tunnel
5: Accounting Start Request
6: Forward Accounting Request (User ID,
IP Address)
charge 7: User Profile Request (User ID, IP Address)
AAA @once 8: User Profile Response (Rulebase*1 ID
(if prepaid subscriber))
9: Accounting Start Response
6 10: Forward Accounting Response
5 3 11: Forward HTTP Request
7 8
2 10 9

Content Specification Service Billing

Name Basis
1
A-Party GGSN IP-Monitor
4 IP/ proto/ Host URL any volume and/or
Mask port Name string time or
constant
eGGSN
simplified Rulebase*1 Layout, administered at eGGSN

*1: CSG uses the name billingplan instead of rulebase

aux. data flow charging flow bearer traffic
For internal use
25 © Nokia Siemens Networks Presentation / Author / Date
 - Service Authorization
Pre: PDP Context Active, User Authorized 9: Budget (granted volume) low:
1: HTTP Service Request Service Re-Authorization Request (CCRu)
2: Service Authorization Request (CCRi + opt. pre- (User ID, Service Name, used quota)
emptive Quota or Default-Quota (Flexi)) 10: Balance&Profile Handling, Rating
(User ID, Service Name, [requested quota]) 11: Service Re-Authorization Response
3: Balance&Profile Handling, Rating (granted quota) (CCAu)
4: Service Authorization Response (granted quota) [5..6 repeated; 5..11 repeated]
(CCAi) 12: PDP Context deletion (user disconnect)
5: Forward HTTP Service Request 13: Accounting Stop Request
6: (Forward) HTTP Service Response 14: Forward Accounting Request
7: (Forward) HTTP Service Request 15: Accounting Stop Response
8: (Forward) HTTP Service Response
18 16: Forward Accounting Response
charge
@once 17: Service Stop Request (User ID, Service
10 Name, used quota)
AAA 3 18: Balance&Profile Handling, Rating
17 4 19: Service Stop Response
14
9 11 Note: Cisco uses term “Quadran” instead of units or
13 16 15
2 19 quota)
1 7
5 7
A-Party 8 6 GGSN 1 7 AS
IP-Monitor
8 6
8 6
12

aux. data flow charging flow bearer traffic

For internal use
26 © Nokia Siemens Networks Presentation / Author / Date
IP Diameter based Use Cases – Session based
- FBC Charging – Quota Management 1
 Quota request is per category, per PDP context
 secondary PDP contexts must ask for their own quota
even if the primary or other secondary already has quota
for the rulebase category in question
 Quota quantification & consumption
• volume-quantified quota
• time-quantified quota
• Time & volume quantified quota
• event-quota
(only in VF-DCCA 2.0 and for Flexi ISN interconnection with
charge@once select v1.6)

For internal use

27 © Nokia Siemens Networks Presentation / Author / Date
IP Diameter based Use Cases – Session based
- FBC Charging – Quota Management 2
Quota Consumption Timer (QCT)
 Quota consumption timer is the way of detecting a
time envelope (only in VF-DCCA 2.0)
 With Quota Consumption Timer, several packets from
the same traffic category are linked together in a same
“time envelope”
 QCT can be deactivated by the server
 Time Envelope is the basis for reporting « active
usage »
<QCT <QCT <QCT

= QCT

Time envelope

For internal use

28 © Nokia Siemens Networks Presentation / Author / Date
IP Diameter based Use Cases – Session based
- FBC Charging – Quota Management 3
• Quota may be renegotiated
• Server can “arm” client-side triggers to initiate quota
renegotiation, such as
– change in roaming status e.g.
change in MCC-MNC, SGSN IP address
– change in RAT (radio access type: GSM, UMTS, WLAN)
– change in PDP QoS / Traffic Class
• Server can explicitly request renegotiation
• Quota is allocated with a (server-defined) validity time

For internal use

29 © Nokia Siemens Networks Presentation / Author / Date
IP Diameter based Use Cases – Session based
- FBC Charging – Quota Management 4
Quota Holding Timer (QHT)
• Quota holding timer is required to retain quota client side for a “short” period after
– the cessation of the traffic of the corresponding category in the PDP in question (volume);
and/or
– the end of a “time envelope” of traffic of the corresponding category in the PDP in question
(time)
• Quota Holding Timer can be deactivated by the server

Quota threshold (Qt)

• is intended to prevent traffic interruption between quota exhaustion and granting of
another quota –latency time
• is of the same value type as the quota granted (bytes or seconds)
• is defined as an absolute value
 Note: not supported at the interface to Flexi ISN ! Usage of „default quota“ plus „Final
Unit Indication“ AVP (FUI) is recommended

For internal use

30 © Nokia Siemens Networks Presentation / Author / Date
 IP Diameter based Use Cases – Session based
- FBC Charging – Quota Service specific handling -1-
Determine RoamingZone:
Various AVPs may be chosen to determine the roaming zone, which is later used by
the rating/charging logic (e.g. User-Location-Info AVP; MCC/MNC).
Subscriber Life-cycle:
Check subscriber data and deal with the results of “subscriber not found” or “subscriber
locked” or “contract not found”.
Initial Balance Check:
Before allowing access to a service-session a balance check may be performed and
requests rejected for subscribers which do not meet a threshold.
Preemptive Quota:
Certain categories may provide quota to the client without being asked (e.g. during the
CCR Initial processing).
Category Blacklisting:
Check for categories disallowed for the subscriber. The result is similar to the Initial
Balance Check, but an account check is not necessary.
Basic Fee:
Certain categories may imply the deduction of a basic fee. The basic fee will be
deducted only for the first category that requests it.
For internal use
31 © Nokia Siemens Networks Presentation / Author / Date
 IP Diameter based Use Cases – Session based
- FBC Charging – Quota Service specific handling – 2-

Teardown:
Under certain conditions an operator may want to terminate a running PDP context.

User Interaction:
An SMS may be sent when a balance falls below some threshold or a specific category
is used or some other condition is met.

Additional AVPs:
The operator may desire to send additional AVPs, which are provided for in the
standards (or not), which can be added to the response object. Typical examples are
QHT and QCT.

Redirection:
Redirection is supported by setting the Result-Code on category level and adding
certain AVPs. The client has to take the appropriate action (e.g. Advice-of-charge).

For internal use

32 © Nokia Siemens Networks Presentation / Author / Date
IP Diameter based Use Cases – Session based
- FBC Charging – Message flow acc. TS 32.251 (V6.3.0) (SCUR)

CLCI CLCI Server

Client IPS Diameter QS
logon (PDP CCR {initial, MSI, Rulebase-ID,…}
Req)
CCA {initial, RC=Success,…}

service req. CCR {update, MSCC(RG_1, …)}

(cat1) CCA {update, MSCC(RG_1, GSU(volume, 1000),
TH=100, VT=200, RC=Success,…), …}

service req. CCR {update, MSCC(RG_2, …}

(cat2) CCA {update, MSCC(RG_2, GSU(time, 120),
cat category
CCA Credit Control Answer
TH=5, VT=200, RC=Success,…), …} CCR Credit Control Request
GSU Granted Service Units
cat1 MSCC Multiple Service
CCR {update, MSCC(RG_1, USU(volume, 900),
threshold met Credit Control
Report-Reason= TH , …} MSI Multiple Service
CCA {update, MSCC(RG_1, GSU(volume, 1000), Indication
RC Result-Code
TH=100, VT=200, RC=Success,…), …}
RG Rating Group = category
= serviceId
CCR {final, MSCC(RG_1, USU(volume, 300), TH Threshold
Report-Reason= Final), MSCC(RG_2, USU(time, 60), USU Used Service Units
logoff (PDP Report-Reason= Final), term-cause= Logout …} VT Validity Time

Disc) CCA {final, RC=Success,…}

For internal use

33 © Nokia Siemens Networks Presentation / Author / Date
IP Session (bearer) charging via NSN Flexi ISN
using DCCA

NSN provides as product FBC-client the

Flexi ISN.

The following slides describe the different use cases provided at the
Diameter Interface according to the standards referenced in the slides
above.

For internal use

34 © Nokia Siemens Networks Presentation / Author / Date
Concept of User and Service Session
The Concept of User-Session and Service-Session is relevant for session charging:
FBC and IMS.

User-Session:
 A CCR Initial begins and a CCR Termination ends a User-Session.
 Ambiguous request/response parameters pertaining to the user-session are called Command-level.
 c@o QS internally: A User-Session has its own CAF-context.

Service-Session:
 A Service-Session corresponds to a sub-dialog within a User-Session.
 It is initiated the first time with an MSCC for a dedicated Category-Id (Rating-Group) and ends when
an MSCC is received with a termination reason (e.g. Reporting-Reason FINAL or QHT)
 Ambiguous request/response parameters pertaining to the service-session are called Category-
level.
 c@o QS internally: A Service-Session has its own CAF-context.
Note:
Be aware that usage of MSCCs does not necessarily imply usage of service-sessions;
the POC application for instance does not use service-sessions.

For internal use

35 © Nokia Siemens Networks Presentation / Author / Date
IP Session (bearer) charging via NSN Flexi ISN
using DCCA

charge@once

HLR

AAA Server
Authorization of Online
Customer,
Gr
2. Subscription data
4. CCR(I) 5. CCA(I) Quota Handling (session)
6./8. CCR(U) 7./9. CCA(U)
3. Authorization Radius 10. CCR(F) 11. CCA(F)
of GPRS Session

Diameter / Ro

1. Request Session Activation Gn GGSN DCCA-Client

10. Request Session De-Activation
12. PDP Context Release
Gi
Flexi ISN Application Server
SGSN
CCR…Credit Control Request
CCA…Credit Control Answer
I…Initial, U…Update, F…Final

For internal use

36 © Nokia Siemens Networks Presentation / Author / Date
Getting the Charging Profile
End User SGSN Flexi-ISN AAA NPS charge@once
(LDAP)

1. Create PDP
Context Request

2. SGSN gets the Charging

Characteristics from the HLR
3. PDP Context
Activation Request
4. User Profile Request

5. User Profile Answer

6. Authentication Req.

7. Authentication Resp.

(*) 8. Credit Control Request

10. PDP Context 9. Credit Control Answer
11. Create PDP Activation Response
Context Response

may contain the Charging Profile (*) it is configurable in ISN which Charging Profile to be used

For internal use

37 © Nokia Siemens Networks Presentation / Author / Date
Scenarios
PDP Context Activation

End User Access ISN Charge@once

An Initial CCR is always sent to

authorize the PDP context

1. “PDP Context Activation Request”

2. CCR (Initial Request, Session 1, User ID, bearer attributes AVPs
(e.g. APN, QoS, SGSN address), Rulebase-ID, Multiple Service
Indicator)

IBC
3. Credit Control Answer (RC=Success, Validity Time)

4. “PDP Context Activation Response”

For internal use

38 © Nokia Siemens Networks Presentation / Author / Date
Service Request

End User Access Flexi-ISN Charge@once

A service request triggers a

Update CCR
5. Service Request (S1)
6. Credit Control Request (Update Request, Session 1, User ID,
MSCC (RG1, RSU ( )))

this AVP is empty and it is used to let the 7. Rating & Quota
Configurable option: server know that quota is needed; will be Reservation
ignored by c@o
- Using a default quota to grant
the service after receiving the 8. Credit Control Answer (MSCC (RG1, GSU (Octets), Validity
Time, QHT))
message 5

9. RG1 is authorized and service is granted

• It can be configured in ISN whether to send or not the Service ID

in CCR (Note: charge@once uses the AVP Rating group id as
service indicator, the AVP service-id is not used)

For internal use

39 © Nokia Siemens Networks Presentation / Author / Date
New Service Request

End User Access Flexi-ISN charge@once

Active services: RG1

10. Service Request (RG2) 11. Credit Control Request (Update Request, Session 1, User
ID, MSCC (RG2, RSU ( )))

12. Rating & Quota

NOTE: The request contains only Reservation
data related to RG2, service-ID is not
sent
13. Credit Control Answer (MSCC (RG2, GSU (Time/Volume),
Validity Time, QHT))

14. RG2 is authorized and quota is granted

15. Service Request (RG1) Active services: RG1, RG2

RG1 still uses the quota allocated for RG1

NOTE: No signalling towards OCS! Active services: RG1, RG2

For internal use

40 © Nokia Siemens Networks Presentation / Author / Date
Quota Holding Time Expires

End User Access Flexi-ISN charge@once

Active services: RG1, RG2 Quota expiration triggers a

Update CCR

16. QHT expires for RG2 (*)

17. Credit Control Request (Update Request, Session 1,
(*) no activity for RG2 User ID, MSCC (RG2, USU (Time/Volume)))
for a time equal to QHT

18. Rating & Quota

NOTE: The request Commitment
contains only data related
to RG2
19. Credit Control Answer (MSCC (RG2,
GSU(time/volume)))

Note: Flexi-ISN uses the QHT

value statically configured in the
Flexi-ISN, if the OCS has not send
it

For internal use

41 © Nokia Siemens Networks Presentation / Author / Date
Validity Time Expires

End User Access Flexi-ISN charge@once

Validity Time expiration

Active services: RG1, RG2
triggers a Update CCR
20. Validity Time expires for RG2 (*)

21. Credit Control Request (Update Request, Session 1, User ID, MSCC
(*) Flexi-ISN needs to perform (RG2, USU (time/volume), RSU ( )))
an interim report for RG2

22. Rating & Quota Commitment,

Reverse Rating & New Quota Reservation
NOTE: The request contains
only data related to RG2; c@o
ignores the RSU 23. Credit Control Answer (MSCC (RG2,GSU (Time/Volume),
Validity Time))

Expiration of Validity Time at command

level triggers credit re-authorisation for all
the Rating Groups within the DCCA session

For internal use

42 © Nokia Siemens Networks Presentation / Author / Date
Granted Units Run Out

End User Access Flexi-ISN charge@once

Active services: RG1, RG2 Quota running out triggers

a Update CCR

24. Granted Units run out for

Rating Group 2 (RG2)

25. Credit Control Request (Update Request, Session1, User ID,

MSCC (RG2, USU (Time/Volume), RSU ( )))
NOTE: The request contains
only data related to RG2;
RSU is ignored by c@o
26. Rating & Quota Commitment,
Reverse Rating & New Quota Reservation

27. Credit Control Answer (MSCC (RG2, GSU (Time/Volume),

Validity Time))

For internal use

43 © Nokia Siemens Networks Presentation / Author / Date
QoS/SGSN/RAT Changes

End User Access Flexi-ISN charge@once

A change in PDP context related parameters

(QoS, SGSN, RAT) triggers a Update CCR (if
the trigger has not been deactivated statically
Active services resp. rating groups:
in ISN)
RG1, RG2
29. Credit Control Request (Update Request, Session 1, User ID, New
QoS/SGSN/RAT,
28. “PDP Context Modification Request” MSCC (RG1, USU (Volume/Time), RSU ( )),
MSCC (RG2, USU (Volume/Time), RSU ( )))

30. “PDP Context Modification Response”

31. Rating & Quota Commitment,
Reverse Rating & New Quota Reservation
For reasons of optimisation, all
services are multiplexed (QoS,
SGSN and RAT changes affect 32. Credit Control Answer (
all the RGs of this PDP MSCC (RG1, GSU (Volume/Time), Validity Time),
MSCC (RG2, GSU (Volume/Time), Validity Time))
context)

For internal use

44 © Nokia Siemens Networks Presentation / Author / Date
Diameter Server Initiated PDP Context Termination

End User Access Flexi-ISN Quota running out triggers charge@once

an Update CCR
Active services: RG2

24. Granted Units run out for

Rating Group 2

25. Credit Control Request (Update Request, Session1, User ID,

MSCC (RG2, USU (Time/Volume), RSU ( )))
NOTE: The request contains
only data related to RG2;
RSU is ignored by c@o 26. Rating & Quota Commitment:
low balance, teardown flag, last active
service/category

27. Credit Control Answer (RC=Terminate_PDP_Context, MSCC

(RG2…,))

28. Credit Control Request Termination Request, Session1, User ID,

MSCC (RG2, USU (Time/Volume), Report-Reason=final )))

29. Credit Control Answer (Termination Request, RC=Success,

30. Logoff (PDP context) MSCC (RG2…,))

For internal use

45 © Nokia Siemens Networks Presentation / Author / Date
User Initiated PDP Context Termination

End User Access Flexi-ISN charge@once

Active services: RG1, RG2 A PDP context termination

triggers a Termination CCR

33. “PDP Context Deactivation Request” 34. CCR (Termination Request, Session1, User ID,
MSCC (RG1, USU (Time/Volume)),
MSCC (RG2, USU (Time/Volume)))

35. “PDP Context Deactivation Response”

36. Rating & Quota
Commitment

For reasons of optimisation, all 37. CCA ()

services are multiplexed (a
PDP context termination
causes anyway rating for all
used services)

For internal use

46 © Nokia Siemens Networks Presentation / Author / Date
FBC – mandatory AVPs
AVPs Description

Service-Context-Id Used to identify the service: here FBC

CC-Request-Type For “SCUR”: Initial, Update and Terminate
Requested-Service-Units In CCR initial: if pre-emptive quota is required
Service Information Contains a request for quota in CCR init,
in CCR Term/Event this is the delivery report
either: 3GPP-User-Location-Info relevant for rating
or: 3GPP-SGSN-Address
Multiple-Service-Credit-Control If present must contain the following AVPs.
Rating-Group Service/Category Identifier
Requested-Service-Units Only if new quota is requested (content is ignored)
Used-Service-Units Present for any category that is not newly requested
CC-Input-Octets For volume based categories: totally with CC-Output-Octets
CC-Output-Octets For volume based categories: totally with CC-Output-Octets
CC-Time For time based categories
CC-Service-Specific-Units For simple event categories
Tariff-Change-Usage If present a Used-Service-Units AVP before and after tariff switch

Reporting-Reason is expected
Either inside USU or outside USU expected
For internal use
47 © Nokia Siemens Networks Presentation / Author / Date
FBC online charging – rating criteria

The determination of the rating parameters are evaluated according to the

following steps.
• The roamingZone is determined by origination parameters of the A-side
(SGSN-IP Address and/or MCC/MNC)
• With the providerId and the subscriber dependent tariffType a key is
determined, which serves as access key for the provider specific tariff zone
mapping tables.
• The appropriate table is loaded.
• With the roamingZone and the called service name (serviceID) concatenated
with the APN a tariffZoneIndex is determined, which addresses a column in
the TimeWindow_MappingTable.
• The originatingTime of the session is mapped via a TimeWindowTable to a
timeWindowIndex, which addresses a row in the
TimeWindow_MappingTable.
• With the timeWindowIndex and the tariffZoneIndex an eParameter-Index is
determined, which addresses a set of e-parameter in the
eParameter_MappingTable.
• The appropriate set of e-parameters (e1 - e7) is retrieved and returned as
the final result of the tariff model determination.

For internal use

48 © Nokia Siemens Networks Presentation / Author / Date
Use Cases
at Diameter-Interface: charging of session and events

• IP Charging – Introduction
• Session Charging based on TS 32.251
• Event Charging based on
– TS 32.260 - IMS Charging
– TS 32.270 - MMS Charging
– TS 32.272 - PoC Charging
– TS 32.274 - SMS Charging (new with c@o select v1.5)

• Simple Event Charging based on TS 32.251

– Event Charging based on VF DCCA V2.0
– Event Charging based on Flexi-ISN V3.x

For internal use

49 © Nokia Siemens Networks Presentation / Author / Date
Proposed online Charging for IMS Services &
Applications
IMS Services & • Enrichment of native voice services by add. media
Applications • New ways of one-to-one and one-to-many communications

Online charging
PoC IM
Diameter
SIP applications IMS standardized platform for
SIP-based services in
CSCF MRCF wireless and fixed networks
IMS

Mobile Fixed
GSM, UMTS, WLAN xDSL, WLAN
CSCF Call Session Control Function
MRCF Media Resource Control Function

• Allows charging of recent Peer-to-Peer services as well as of

IMS Online conventional network-based operator services
Charging
• Supports migration of classical CS-services into NGN

For internal use

50 © Nokia Siemens Networks Presentation / Author / Date
IMS Online Charging Architecture
aligned with 3GPP Release 6
The following mechanisms
are supported by c@o:

 Session Charging with

Unit Reservation (SCUR)
 Event Charging with Unit
Reservation (ECUR)
 Immediate Event
Charging (IEC)

For internal use

51 © Nokia Siemens Networks Presentation / Author / Date
IMS Service Triggering
Charge@once is able to distinguish between the different charging scenarios based on the following AVPs:
 CC-Request-Type
 SIP-Method

The CC-Request-Type-AVP determines the type of CCR message:

1 = Initial_Request  CCRi (used for ECUR and SCUR)
2 = Update_Request  CCRu (used for SCUR)
3 = Termination_Request  CCRt (used for ECUR and SCUR)
4 = Event_Request  CCRe (used for IEC)

With the help of the SIP-Method-AVP (Service-Information / IMS-Information / Event-Type / SIP-Method)

charge@once is able to distinguish between ECUR and SCUR for CCRi messages. The SIP-Method-AVP
contains the SIP-Method, which triggered the CCR, e.g. :
SIP INVITE  SCUR
SIP NOTIFY  ECUR/IEC
SIP MESSAGE  ECUR/IEC
SIP REGISTER  ECUR/IEC
SIP SUBSCRIBE  ECUR/IEC
SIP REFER  ECUR/IEC
SIP PUBLISH  ECUR/IEC

For internal use

52 © Nokia Siemens Networks Presentation / Author / Date
IMS Session Establishment (SCUR)

S-CSCF charge@once

Use Case:
IMS-Registration
The duration of the SIP
session can be controlled by
CCR initial
a dedicated rating group.
Session setup begin
(SIP INVITE)
CCA initial
Granting and consumption of
Session established
Time Quota will be performed
(SIP 200 OK to INVITE) Budgeting by using the CC-Time AVP.
CCR update
CCA update

IMS-Session established

For internal use

53 © Nokia Siemens Networks Presentation / Author / Date
IMS Session Continuation (SCUR)
S-CSCF charge@nce

Use Case:
IMS-Session established

When the quota is fully

Budgeting
exhausted, the S-CSCF
Granted Units consumed CCR update
reports the used amount
and requests more Quota
CCA update with FUI
for this RG

Granted Units consumed

Initiate Session Release

Session end
(SIP BYE) CCR terminate

CCA terminate

IMS-Session is released

For internal use

54 © Nokia Siemens Networks Presentation / Author / Date
IMS Session Release (SCUR)

S-CSCF charge@once

IMS-Session established

Budgeting

Session end

(SIP BYE)
CCR terminate

CCA terminate

IMS-Session is released

For internal use

55 © Nokia Siemens Networks Presentation / Author / Date
IMS Event Charging with Unit Reservation (ECUR)

Use Case: Payload charging

S-CSCF charge@once
To control methods within a
SIP session (potentially:
IMS-Registration
INVITE, re-INVITE, UPDATE),
Service request
CCR inital
which contain payload, a
(SIP Message)
Unit Determination
dedicated rating group has to
Rating Control be defined.
Account Control

Reservation Control
The granting and consumption
CCA inital
Service delivery
(GSU = 1) of Quota (Service specific
(SIP Message) CCR terminate
(USU = 1)
units) is handled in this
Rating Control scenario.
Service execution Account Control
If the control of payload is
(SIP 200 OK) CCA terminate
required, then the OCS will
grant Quota for the specific
IMS-Session is released
Rating Group within the CCAi.
The CC-Service-Specific-Units
AVP (within MSCC / Granted-
Service-Units) is used for this
purpose.
For internal use
56 © Nokia Siemens Networks Presentation / Author / Date
Use Cases
at Diameter-Interface: charging of session and events

• IP Charging – Introduction
• Session Charging based on TS 32.251
• Event Charging based on
– TS 32.260 - IMS Charging
– TS 32.270 - MMS Charging
– TS 32.272 - PoC Charging
– TS 32.274 - SMS Charging (new with c@o select v1.5)

• Simple Event Charging based on TS 32.251 (planned for c@o

select V1.7)
– Event Charging based on VF DCCA V2.0
– Event Charging based on Flexi-ISN V3.x

For internal use

57 © Nokia Siemens Networks Presentation / Author / Date
MMS Charging
Options to realize the MMS charging

• MMS via Payment PlugIN  NSN proprietary

• MMS MO/MT via Diameter  3GPP TS 32.270
• MMS MO/MT via Diameter based on 3GPP MMS standard
(TS 32.270)  Vodafone proprietary
• MMS MO/MT based on FBC  not TS 32.251 v6
conform
(SSU AVP based)

For internal use

58 © Nokia Siemens Networks Presentation / Author / Date
MMS Charging
MMS charging via Payment Plug-In (PPI)
• Charging of MMS and a refund via prop. IP protocol (PPI) is shown
• 1 Dialogue for immediate charging, refund dialogue only in negat. case

c@o

charge
Amount
charge
Amount
HLR
Conf

refund refund
Conf

PayPlugIn

SGSN MSC/VLR
MSC/VLR SGSN MMS MMSC MMS

A-Party (PPS) B-Party

For internal use

59 © Nokia Siemens Networks Presentation / Author / Date
MMS Charging
MMS MO charging via Diameter (3GPP 32.270 V6.6.0)
• Standard defines for Originator MMS (MMS MO) charging on MM submission only (IEC),
no refund mechanism has been standardized yet

d ed in ff c@o
u .2
Incl lect 1
o se Credit Credit

c@ Control
Request
Control
Answer
HLR

Diam Client

SGSN MMSC SGSN VLR

VLR MMS MO MMS MT

A-Party (PPS) B-Party

For internal use

60 © Nokia Siemens Networks Presentation / Author / Date
MMS Charging
MMS MT charging via Diameter (3GPP 32.270 V6.6.0)
• Standard defines for Recipient MMS (MMS MT) charging also on MM retrieval
(ECUR)

c@o
d ed in ff
u .2
Incl lect 1
o se Reserve Reserve

c@ Unit Unit

HLR
Request Response

Debit Debit
Unit Unit
Request Response

Diam Client Pos. confirmation

Content SGSN
Server MMS
MMSC VLR
MMS MT

B-Party (PPS)

For internal use

61 © Nokia Siemens Networks Presentation / Author / Date
MMS online charging

Single MMS online charging:

Either the sender or the recipient will be charged.
 If the sender is charged IEC is used.
 If the recipient is charged ECUR is used.
Note: This behavior is defined within 3GPP.

Multiple recipients handling:

There are two possibilities to support multiple recipients in the MMS context:
1. For each MMS recipient a single online charging interrogation takes place.
2. The recipient address occurs multiple in a single interrogation.
Charge@once supports both methods.

Restriction:
for 1): Bonus handling based on multiple recipients is not possible.
for 2): if subscribers account balance is not sufficient to charge for all recipient,
then request will be denied.

For internal use

62 © Nokia Siemens Networks Presentation / Author / Date
MMS online charging – rating criteria

The following rating criteria resp. steps are applied for MMS charging in charge@once
select:

1. Message-Type:
in order to distinguish between mobile-originating and mobile-terminating MMS
handling.
2. MMS recipients’ roaming zones:
The roaming zone is decoded from
Recipient-Address.Address-Domain.3GPP-IMSI-MCC-MNC.
Note: originator (sender) roaming zone is not considered !
3. MMS size:
This size is quantified into equal-size blocks, e.g. 0-10, 10-20, 20-30, >30. The
number of such blocks (e.g. num_blocks = 3) and the quantified size (e.g. qsize =
10) are configurable.
4. Resulting Price:
The pair (roaming zone, block) is mapped onto a price via a table, which may be
administrated with the Tariff-tool.
In case no entry is found, a default price is chosen.

For internal use

63 © Nokia Siemens Networks Presentation / Author / Date
MMS online charging – Diameter mandatory AVPs

The following AVPs are mandatory for rating of an MMS event (sent within CCR):

AVPs Description
Service-Context-Id Used to identify the service: here MMS

RSU:
CC-Service-Specific-Units Always “1”
Service Information Contains a request for quota in CCR init,
in CCR Term/Event this is the delivery report
PS-Info:
3GPP-User-Location-Info relevant for rating
MMS-Info:
Message-Size relevant for rating
Message-Type relevant for rating
Submission-Time Tickets only
Recipient-Address may be present multiple times, but at least once
3GPP-IMSI-MCC-MNC Relevant for rating

For internal use

64 © Nokia Siemens Networks Presentation / Author / Date
Call Flow: MMS-MO (IEC)

MMS UA MMS-C c@o

1. MM1_submit_REQ

2.CCRe(RSU = SSU 1)

3. CCAe(GSU=SSU 1,
Result =success)

4. MM1_submit.RES

For internal use

65 © Nokia Siemens Networks Presentation / Author / Date
Call-Flow: MMS-MT handling (ECUR)

MMS UA MMS-C c@o

1.MMS Transfer
2a.MM1_notify.REQ

2b. MM1_notify.RES

3. MM1_retrieve_REQ

4.CCRi(RSU = SSU 1)

5.CCAi(GSU=SSU 1,
Result =success)

6. MM1_retrieve.RES

7. MM1_retrieve_ACK

8.CCRt(RSU = SSU 1)

9.CCAt(GSU=SSU 1,
Result =success)

For internal use

66 © Nokia Siemens Networks Presentation / Author / Date
Use Cases
at Diameter-Interface: charging of session and events

• IP Charging – Introduction
• Session Charging based on TS 32.251
• Event Charging based on
– TS 32.260 - IMS Charging
– TS 32.270 - MMS Charging
– TS 32.272 - PoC Charging
– TS 32.274 - SMS Charging (new with c@o select v1.5)

• Simple Event Charging based on TS 32.251 (planned for c@o

select V1.7)
– Event Charging based on VF DCCA V2.0
– Event Charging based on Flexi-ISN V3.x

For internal use

67 © Nokia Siemens Networks Presentation / Author / Date
 PoC Quota Service
Use Cases

The 3GPP TS 32.272 for PoC V6.6.0 defines for PoC charging
 Session Charging with Unit Reservation (SCUR).

Examples:
 Charging of Talk bursts (sent or received)
 Charging of PoC session participation

Additionally an Instant Personal Alert (IPA) will be handled as event based

charging (ECUR).
This applies to a reduced process, which is started by an CCR initial and
terminated by an CCR termination (without further CCR updates).

For internal use

69 © Nokia Siemens Networks Presentation / Author / Date
PoC online charging - rating criteria
As rating criteria the following parameters resp. steps applies :
1. Category used:
e.g. definition of the following categories on client and server side (depends on client capability):
Cat. A: Sent Talk Bursts with 2 active participants;
Cat. B: Sent Talk Bursts with >2 active participants;
Cat. C: Received Talk Bursts.
or:
Cat. A: Sent Talk Bursts
Cat. B: Receive Talk Burst.
2. Credit pool mechanism:
The credit pool will be managed by the set of the multipliers for each category.
In case three categories are supported, three multipliers M1, M2, M3 will be configured. The sum of
units granted (granted quotas) will be calculated as
Sum of all units = (GSU1*M1)+(GSU2*M2)+(GSU3*M3)
The PoC server has to ensure that the used service units C1, C2, C3 satisfy
(C1*M1)+(C2*M2)+(C3*M3) < Granted Quotas
3. roaming zone:
MCC/MNC presented in 3GPP-User-Location-Info AVP is used for roaming zone determination.
4. Price:
The corresponding price levels for the roaming zones (e.g. home or visited networks) has to be used
to adjust the weighted sum of units consumed .

For internal use

70 © Nokia Siemens Networks Presentation / Author / Date
PoC online charging – mandatory AVPs
The following AVPs are mandatory for rating of a PoC session resp. a talk burst exchange
(sent within CCR):

AVPs Description
Service-Context-Id Used to identify the service: here PoC
Service-Identifier e.g.:
11 - Talk burst sending with 2 active participants
12 - Talk burst sending with >2 active participants
20 - Talk burst receiving
30 - Instant Personal Alert (IPA)

Service Information Contains a request for quota in CCR init,

….. in CCR Term/Event this is the delivery report
PoC-Info:
Number of participants relevant for rating
Participants-Involved relevant for rating (addresses)
PoC-Server-Role identifies the PoC server as participating or controlling PoC server
PoC-Session-Type relevant for rating
PoC-Session-Id Unique identifier of the PoC Session

PoC-Controlling-Address relevant for rating

As result the PoC server gets the G-S-U-Pool-Identifier with info about the type of units to be
considered (CC-Unit-Type: “4” = service-specific-units ) and the value of it for each rating-
group.
For internal use
71 © Nokia Siemens Networks Presentation / Author / Date
 PoC Quota Service
PoC 3GPP (TS 32.272) message flow (SCUR): Session Participation
Controlling Particip.
UE-1 S-CSCF 1 PoC Server c@o S-CSCF 2 PoC Server UE-2
SIP based IMS Registration
Start PoC Session Charging
S1
SIP INVITE for User 1 and User 2
SIP INVITE
CCR (initial, UE-1,(Service-Id=Session)(Service-Id=TalkBurst))
S1
CCA (UE-1,(Service-Id=Session,GSU=10min),(Service-Id=TalkBurst,GSU=5MB))
CCR (initial, UE-2,(Service-Id=Session)(Service-Id=TalkBurst))

CCA (UE-2,(Service-Id=Session,GSU=5min),(Service-Id=TalkBurst,GSU=3MB))
SIP INVITE
SIP INVITE SIP INVITE
SIP INVITE
200 OK
200 OK
200 OK
200 OK
Start Budget Control
for UE-1 and UE-2
200 OK 200 OK

ACK
ACK
ACK ACK
ACK
ACK
PoC Session Successfully Established / Talk Bursts can be exchanged
For internal use
72 © Nokia Siemens Networks Presentation / Author / Date
 PoC Quota Service
PoC 3GPP (TS 32.272) message flow (SCUR): Talk Burst Exchange
Controlling Particip.
UE-1 S-CSCF 1 PoC Server c@o S-CSCF 2 PoC Server UE-2
PoC Session Successfully Established / Talk Burst exchange

RTCP: Floor Request B1

RTCP: Floor Grant
B1 Start Talk Burst Charging
RTP: Talk Burst
B2 Stop Talk Burst Charging
RTCP: Floor Release
B2
RTCP: Floor Idle
Budget Control
New units are needed

CCR (update, UE-1,Service-Id=TalkBurst,USU=4.5MB)

CCA (UE-1,Service-Id=TalkBurst,GSU=5MB)
Legend:
Budget Control
New units are received SIP Signalling

RTP Bearer Traffic

RTCP Signaling Traffic

For internal use

73 © Nokia Siemens Networks Presentation / Author / Date
Use Cases
at Diameter-Interface: charging of session and events

• IP Charging – Introduction
• Session Charging based on TS 32.251
• Event Charging based on
– TS 32.260 - IMS Charging
– TS 32.270 - MMS Charging
– TS 32.272 - PoC Charging
– TS 32.274 - SMS Charging (new with c@o select v1.6; alternative
options)

• Simple Event Charging based on TS 32.251 ( planned for c@o select

V1.7)
– Event Charging based on VF DCCA V2.0
– Event Charging based on Flexi-ISN V3.x

For internal use

74 © Nokia Siemens Networks Presentation / Author / Date
SMS Charging
Options to realize the SMS charging PO-based

Pre-rated Events:
• SMS MO via Payment Plug-In (esp. for roaming)
• SMS MT via Payment Plug-In (esp. for content charging)

Un-rated Events:
• SMS MO/MT via Diameter (TS 32.274)
• SMS MO/MT via Diameter based on VF Ro SMS V1.1.0 -
based on 3GPP MMS standard (TS 32.270)
(not considered in this slide-set)
For internal use
75 © Nokia Siemens Networks Presentation / Author / Date
SMS Charging
SMS MO / MT charging via Payment Plug-In (PPI)

• Charging of SMS and a refund via prop. IP protocol (PPI) is shown

• 1 Dialogue for immediate charging, refund dialogue only in negative case

c@o

charge charge HLR

Amount Amount
Conf

refund refund
Conf

PayPlugIn

VLR SSP/MSC SMS MO

SMSC SSP/MSC VLR
SMS MT

A-Party (PPS) B-Party

For internal use

76 © Nokia Siemens Networks Presentation / Author / Date
SMS Charging
SMS MO charging via Diameter (3GPP 32.274 V8.0.1)
• Immediate Event Charging (IEC) of SMS
• Refund dialogue only in negative case.

w ith c@o
d
rte t 1.6
p o
Sup selec
o Debit Debit

c@ Unit
Request
Unit
Response
(CCRe) (CCAe)

Debit Debit
Unit Unit
Request Response
(Refund (Refund
Account: Account:
CCRe*1) CCAe*1 )

Diam Client Neg. confirmation

HLR/ SSP/MSC SSP/MSC HLR/
VLR SMS MO
SMSC VLR
SGSN SMS SGSN

A-Party (PPS) B-Party

*1
– Refund is supported by an IEC with AVP Requested_Action set to „Refund“. Additionally the Message-ID AVP shall be used for
correlation purpose.
For internal use
77 © Nokia Siemens Networks Presentation / Author / Date
SMS Charging
SMS MT charging via Diameter (3GPP 32.274 V8.0.1)
• Event Charging with Unit Reservation (ECUR) of SMS
• Refund dialogue implicitly - only in negative case

w ith c@o
d
rte t 1.6
po c
Sup o sele Reserve Reserve
c@ Unit
Request
Unit
Response
(CCRi) (CCAi)

Debit Debit
Unit Unit
Request Response
(Refund (Refund
Account:
HLR/
Account:
CCRt) CCAt) VLR
Diam Client Neg. confirmation
MSC/ SSP
HLR/ MSC/ SSP
SMS
SMSC SGSN
VLR SGSN SMS MT

Premium SMS

A-Party (PPS) Content B-Party

Provider

For internal use

78 © Nokia Siemens Networks Presentation / Author / Date
SMS – Diameter-based Service-specific Information
The following table defines the service-spec information relevant for SMS which may be used for
rating/charging purpose (3GPP TS 32.274).
Note: For the VF propr. solution the field „SM Message Text“ is provided additionally.

For internal use

79 © Nokia Siemens Networks Presentation / Author / Date
Use Cases
at Diameter-Interface: charging of session and events

• IP Charging – Introduction
• Session Charging based on TS 32.251
• Event Charging based on
– TS 32.260 - IMS Charging
– TS 32.270 - MMS Charging
– TS 32.272 - PoC Charging
– TS 32.274 - SMS Charging (new with c@o select v1.5)

• Simple Event Charging based on TS 32.251 (supported with c@o

select V1.6)
– Event Charging based on VF DCCA V2.0 (not considered within this slide-set)
– Event Charging based on Flexi-ISN V3.x

For internal use

80 © Nokia Siemens Networks Presentation / Author / Date
 FBC Quota Service
Online Charging Methods
The 3GPP TS 32.251 for FBC V6.3.0 defines for FBC
charging

 Session Charging with Unit Reservation (SCUR).

Enhancements for simple Event recognition and charging is

provided with charge@once v1.6

 Event Charging based on SCUR (FBC)

Restrictions:
 No dedicated Event-request (AVP „CC-Request-Type“ (416)) but AVP CC-
Service-specific-Units (417) is used.
 Support of interoperability with Flexi-ISN (>=V3.2) functionality to charge
simple events.

For internal use

81 © Nokia Siemens Networks Presentation / Author / Date
IP Session (bearer) charging via NSN Flexi ISN
using DCCA

charge@once

HLR

AAA Server
Authorization of Online
Customer,
Gr
2. Subscription data
4. CCR(I) 5. CCA(I) Quota Handling (session)
6./8. CCR(U) 7./9. CCA(U)
3. Authorization Radius 10. CCR(F) 11. CCA(F)
of GPRS Session

Diameter / Ro

1. Request Session Activation Gn GGSN DCCA-Client

10. Request Session De-Activation
12. PDP Context Release
Gi
Flexi ISN Application Server
SGSN
CCR…Credit Control Request
CCA…Credit Control Answer
I…Initial, U…Update, F…Final

For internal use

82 © Nokia Siemens Networks Presentation / Author / Date
Event Charging based on FBC
Use Case: MMS MO/MT charging via Flexi-ISN
• Based on TS 32.251 the AVP CC-Service-Specific Units is used (not 3GPP
compliant!).

w ith c@o
o rted 1.6
p t
Sup o selec SGSN
c@
Reserve
Unit
Reserve
Unit VLR
Request Response

Debit Debit Pos. confirmation

Unit Unit
Content Request Response

Server
MMS MT

MMS MT Diam Client

Flexi-ISN MMSC B-Party (PPS)
MMS
SGSN
VLR MMS MO

A-Party (PPS)

For internal use

83 © Nokia Siemens Networks Presentation / Author / Date
Let´s have a break

For internal use

84 © Nokia Siemens Networks Presentation / Author / Date
IP Ticketing
Event based charging can either be performed:
• Proprietary – via Payment Corba Interface
• Standardized acc. 3GPP standardized Application-based Diameter
releases.

IP Event or Session Tickets will be generated in the following cases:

• Call tickets are written if the charging transaction is performed
successfully.
• In case of an error a confirmation ticket is written.
Principles:
 For each charging transaction a ticket is written.
 For events (without reservation): one ticket is written.
 For each user session multiple tickets according to the charging
transactions are written.
 No dedicated session end ticket is generated in case of session
end:
For each service/category a ticket with ticket-end identifier is
written.

For internal use

85 © Nokia Siemens Networks Presentation / Author / Date
IP Tickets – Payment Corba

General Hint:
Payment Corba requests can either be handled by the PaymentCore or by SLEE-
based application (SLEE = Service Logic Execution Environment).
PaymentCore is only needed if a transactional context storage for more than 24
hours is needed (in case of long-lasting transactions) and a separation of charging
and call&control platform is given (e.g. in case of charging@vantage and
IN@vantage platform). Note: normally not required by operators.

For IP-based charging tickets created by PaymentCore the following ticket types
can be used:
• 0x22/0x21 IP based charging tickets
• 0x24 payment and logging tickets.
The setting of TPD-parameter „UsePaymentTicketFormat“ is mandatory:
• True = 0x24 payment and logging tickets
• False = 0x22/0x21 IP based charging call and confirmation tickets

In case of SLEE only

• 0x22/0x21 IP based charging tickets are produced.

For internal use

86 © Nokia Siemens Networks Presentation / Author / Date
Ticket-Types

Ticket name (related to use case) Ticket type Version TT-specific

directory
Event charging via payment plugin tickets Call 0x22 cat

Confirmation 0x21 cft

Payment/Logging 0x24 see PC-Table

Payment transaction Administration (PTA) PTA-files -- PTA_Data

Event charging via Radius (Web/Wap proxy) Call 0x22 cat

Confirmation 0x21 cft

Event and session charging via Diameter Call 0x22 cat

Confirmation 0x21 cft

Session and Content charging via GTP´ Call 0x22 cat

Confirmation 0x21 cft

Session and content charging via Diameter Call 0x22 cat

Confirmation 0x21 cft

For internal use

87 © Nokia Siemens Networks Presentation / Author / Date
Payment Core Ticket-Types

The Payment Transaction Administration (PTA) detects all transactions with the
states surely inconsistent or possibly inconsistent during charging operations and
indicates the failures or recovery results. These failures or recovery results are
written into a PTA files (tickets).

For internal use

88 © Nokia Siemens Networks Presentation / Author / Date
IP Service Configuration
IP services will be configured

via Web-TPD
- Related to their IP-configuration (client/server):
- server/client IP address configuration
- interface security insurance (SSL, IPSec, MAC)
- Related to Corba-application specific IT-configuration
(like client traffic handling/load)
- Related to platform functionality like ticketing:
- Ticket type, dimensioning, ticket directory assignment
- Ticket suppression
via SMAF
- Service related configuration like session service based configuration of
thresholds, validity timer, service specific default quota portions, initialization
of special handlings like IBC (Initial balance check)

via TariffTool / OfferManager

- E.g. RoamingAreaTable, APN table, prices (e-parameter or triple-p-set)

For internal use

89 © Nokia Siemens Networks Presentation / Author / Date
TPD parameter relevant for IP charging
 IP Traffic Control
Cluster Global Traffic Limit vs. Client Traffic Limit:
The possible maximum number of all incoming IP-based messages per hour is defined
within the parameter ClusterGlobal_IP_TrafficLimit.

Additionally the dedicated traffic limits for each logical client can be configured using the
following config-parameters resp. tables:
ETC_ClientTraffic:
table which consists of all logical clients and their corresponding maximum allowed IP
traffic:
• logicalclientID
• Traffic_limit
• Extendedtrafficcontrol_status (on/off/block): on=traffic limit is active, off=traffic is not
limited, block=client is disabled temporarily

ETC_ClientIdentific:
Assignment of one or more physical client IDs to each logical client:
• physical_clientID: either the first 4 digits of the TransactionID for the Corba interface or
the IP
address for the GTP´/ Diameter interface
• logical_clientID: name of the client defined in the table ETC_ClientTraffic.

For internal use

90 © Nokia Siemens Networks Presentation / Author / Date
TPD parameter relevant for IP charging
 Ticket security insurance

Tickets can be encrypted by using MACs (Message Authentication

Codes).
TPD-Parameter „Rtp_Tic_Mac“ switches the MAC generation on/off
generally.
Beside the global parameter a further configuration parameter for
each ticket type is applicable.

For internal use

91 © Nokia Siemens Networks Presentation / Author / Date
TPD parameter relevant for IP charging
GOB relevance

For payment Corba based tickets the GOB-relevance is configurable at the so-
called Decision Matrix.
For each completed and closed GoB ticket file an additional file with the GoB
ticket file's check sum is generated by the Ticket Manager in order to fulfill the
Journal-Function.
Logging Tickets written for administrative tasks or to log failures are generally
not GoB relevant.

For charge@once all written call- and payments tickets are basically of GoB
relevance and therefore not limited to mCommerce scenarios any more

For internal use

92 © Nokia Siemens Networks Presentation / Author / Date
TPD parameter relevant for IP charging
 Payment Core Ticket Suppression, GOB relevance
Tickets can be suppressed if configured in table „decision matrix“.
Ticket Ticket Ticket
Payment scenario productID GoB WritePrepaid
Account 1 Account 2 Account 3

Merchant or - depends on depends on

chargeAmount Consumer yes
PSPLogin productID productID

Merchant or - depends on depends on

authorizeAmount Consumer yes
PSPLogin productID productID

Merchant or - Same as for

captureAmount Consumer no Same as for authorize
PSPLogin authorize

Merchant2 depends on the

Source Target yes
entry for depends on the entry for
Consumer1 Consumer1 or
transferAmount DEFAULT- DEFAULT-DECISION
or or DEFAULT-
DECISION or productID
Merchant1 Consumer2 DECISION
or productID

yes depends on the depends on the entry for

or entry for DEFAULT- DEFAULT-DECISION
rechargeAmount Consumer Merchant
DEFAULT- DECISION or
DECISION or productID productID

Merchant or depends on depends on

refund Consumer yes
PSPLogin productID productID

 If the productID is not present (e.g. transferAmount, rechargeAmount) the DEFAULT-DECISION entry (default productID
in the decision matrix) defines the values of “GoB” and “WritePrepaid”. These entries are Class D parameters and the
default setting is: GoB = “1”; WritePrepaid = “TRUE”
 If the DEFAULT-DECISION entry is deleted “GoB” is internally set to “1” and “WritePrepaid” is set to “TRUE” for
transferAmount and rechargeAmount.
 In order to suppress a PrepaidTicket for “transferAmount” or “rechargeAmount” the values for “GoB” and “WritePrepaid”
of the DEFAULT-DECISION entry have to be changed !
 If one of the involved accounts of a “transferAmount” operation owns a postpaid consumer it is not possible to suppress
this ticket !
For internal use
93 © Nokia Siemens Networks Presentation / Author / Date
Ticketing – session based

IP session based ticketing

Pre-condition:
• For each user one session context for session specific data is established.
• For each service activated by the user, one service context with service
specific data is established.

IP Tickets are generated in the following cases:

• For each Quota-Inquiry-Request resp. service inquiry request sent by the IP-
client a call ticket (version: 0x22) is written.
The information is taken from the session- and service context.
• In case of an error (abnormal behavior) a confirmation ticket (version 0x21) is
written.

For internal use

94 © Nokia Siemens Networks Presentation / Author / Date
Ticketing – Event based

Event based charging can either be Ticket

performed: Description
Type
 Proprietary – via Payment
Corba Interface Payment tickets are used to register all
 Standardized acc. 3GPP account movements and dependent data (due
standardized Application-based to recharging, charging, balancing,
Diameter releases. settlement, internal transfer, etc. activities)
during a payment transaction.
Payment Additionally reservations made to an account
IP Event Tickets provided by Payment Corba Ticket are written into payment tickets.
are either Payment specific ones or based on Available Ticket formats:
@vantage tickets. Payment Ticket 0x24, (written by Payment
Core)
IN Call Ticket 0x22 , (written by Payment
IP Event Tickets provided by Diameter QS Core and CORBA Charging Service)
are generated in the following cases:
• Call tickets (0x22) are written if Logging Tickets are used
the charging transaction is - to log error situations of payment features
performed successfully and
- to log errors caused by account inquiries
• In case of an error a Logging
Available Ticket formats:
confirmation ticket (version Ticket Payment Ticket 0x24, (written by Payment
0x21) is written. Core)
IN Confirmation Ticket 0x21 , (written by
Payment Core and CORBA Charging Service)

For internal use

95 © Nokia Siemens Networks Presentation / Author / Date
Diameter Session based Tickets – Call Tickets
Call Tickets (Format 0x22) are written in case eGGSN QS

of
 Category related: for each incoming CCR Initial Request (may
have more than one category)
request per category
 CCR Initial (only with pre-emptive
quota), Write Call Ticket
per Category
 CCR Update,
 CCR Final.
CCR Initial Response (may
have more than one category)

 Each time a Message reaches the service

and a writing access to the subscriber’s
account is made. This includes messages CCR Update/ Terminate
with usage = 0. Request (may have more than
one category)
 No call tickets are written for UserProfile
requests or ContentAuthorisation.
Write Call Ticket
 If a confirmation ticket is written, no call per Category

ticket is written in that situation.

CCR Update/ Terminate
Response (may have more
than one category)

For internal use

96 © Nokia Siemens Networks Presentation / Author / Date
Diameter Session based Tickets – Confirmation
Tickets
Confirmation Tickets (Format 0x21) are written
in case of eGGSN QS

 an error (abnormal behavior), that leads to a category stop.

CCR Initial Request (may
 every (re-) authorization failure: have more than one category)
e.g. Balance low, but this error doesn’t lead to service stop.
Example: error
situation: bad
subscriber id
Use case related examples:
 Balance Low
write confirmation
 OverCharge situation without enough money ticket per
category
 Configuration failed
 AVP error (invalid AVP value, missing AVP, …..)
 Initial balance check failed CCR Initial Response (may
have more than one category)
 BadUserId – Subscriber Locked, Subscriber not found
Not successful
 Bad service id Not successful
Not sucessful
 Rating or Charging function error
 Missing Parameter
 TooManyServices, BadServiceId
 TearDown
 Traffic limitation reached
 Sending of an ASR

For internal use

97 © Nokia Siemens Networks Presentation / Author / Date
 Ticket Content of IP session based transactions
IP session tickets consists of two major parts of information:
- Session specific information
- Service specific information.

Session specific information are e.g.:

Ticket Parameter Description

UserLocationInfo MCC/MNC
ServiceProviderID local subscriber data: identifies the service provider the
customer is related to
TariffParameterID contract resp. tariff identification
CorrelationID for correlating call and conf tickets belonging to the same
service/category within a user session
(contains 3GPP-GGSN-Address, 3GPP-Charging-ID,
rating-group).

sessionStartTime time of session start

sessionDuration duration of the uses session in seconds
sessionUsedQv accumulated volume used up during user session
SessionUsedQt accumulated time used up during user session
SessionUsedMoney accumulated consumed money during user session

For internal use

98 © Nokia Siemens Networks Presentation / Author / Date
Ticketing – IP session content
Service specific information:

Ticket Parameter Description

numberSvc number of services/categories (max. 16)
------------------------ service substructure* ---------------------------------------------------------------------
SvcType free, volume, time, dual, logon (VF propr.);
[event (usage of service-specific-units)]
SvcID categoryID provided in AVP rating group
SvcDuration Duration of the complete service

SvcUsedQv accumulated sum about consumed volume quota

SvcUsedQt accumulated sum about consumed time quota
SvcUsedMoney accumulated sum about consumed money
numberTS number of Tariff Switches
------------------------- (for each TS): ------------------------------------------------------------------------------
svcTSusedQv accumulated used volume (bytes) within tariff
svcTSusedQt accumulated used time (seconds) within tariff
svcTSusedMoney accumulated used money (euro) within tariff

Reference: A50020-A3294-K-1-76D6

For internal use

99 © Nokia Siemens Networks Presentation / Author / Date
New IP-Features provided with charge@once
select v1.7 and v1.8

charge@once select v1.7 provides

 Fair Usage Policy
 Bill-Shock prevention (postpaid)

charge@once select v1.8 provides

 Bill-Shock prevention (prepaid)
 Gy-Alignement to v7 (corr. with FISN v4)

For internal use

100 © Nokia Siemens Networks Presentation / Author / Date
Fair Usage Policy: Gx for Pre-defined Policies
Challenge:
• Excess usage may require on-line policy changes – e.g. blocking or bandwidth limiting
certain services, or downgrading the QoS / Bandwidth for the on-going user session
• 3GPP defines Policy and Charging Control (PCC) and On-line Charging architectures,
where the related functionalities are performed at the Policy Control Server (PCS) and at the
On-line Charging System (OCS), contacted via separate Diameter based Gx and Gy
interfaces
• Policies and usage control may be linked together as policies may depend on usage
• Operators with an existing OCS may wish to host simple policies in the same server
rather than investing in a heavier architecture
Solution:
• Flexi ISN enables a simplified architecture where the policy & charging control and on-line
usage monitoring & control can be performed through a single Diameter DCCA interface
• This is realised by combining selected capabilities of Gx to Gy as they are technically very
similar
• Note: Plain PCC functions (e.g. Gx capabilities only) are also supported
Benefits:
• Enables fast response to excess or abusive usage
• Simplified architecture minimizes CAPEX and OPEX
• Enables usage based policies over a single interface, without the need to have separate
On-line Charging and Policy Control systems
• 3GPP standardized Policy Control architecture is also supported
For internal use
101 © Nokia Siemens Networks Presentation / Author / Date
Gx for Pre-defined Policies
Use Case: User Specific
Policies 2. PCS checks what is the QoS and
(e.g. standard Gx) Services (e.g. pre-defined policies) that
User A Policy are authorized for this user (e.g. User
QoS=“medium” Profile)
HTTP service enabled
User B Policy PCS
QoS=“high”
ALL TRAFFIC service
enabled
3. PCS sends the User
A policies to Flexi ISN
Gx
1. Upon PDP context setup, Flexi ISN
contacts Policy Control Server over Gx
interface for user A policies
User A
Internet

4. PDP context is opened with QoS Service configuration (pre-defined

“medium” (moderate bandwidth), user is policies):
allowed to do HTTP browsing Flexi ISN
• HTTP
Traffic matching rule “port 80”
Charging parameters
BW, location, roaming restrictions
• ALL TRAFFIC
Traffic matching rule “all traffic”
Charging parameters
For internal use
102 © Nokia Siemens Networks Presentation / Author / Date
BW, location, roaming restrictions
Gx for Pre-defined Policies
Use Case: Fair Usage Policy, Usage Based
Limits
(e.g. Gx and Gy combined)
2. PCS/OCS checks the QoS and Services
User B Policy for this user. Usage threshold is not
If usage threshold exceeded exceeded. Quota is set to remaining usage
QoS=“low” until threshold
else User B usage:
QoS=“high” PCS/OCS Cumulative monthly usage counter
ALL TRAFFIC service Usage threshold 4GB
enabled
6. PCS notices that usage threshold is 3. PCS/OCS sends the User B policies and remaining
exceeded quota to Flexi ISN
Gx 7. PCS/OCS sends the updated policies to Flexi ISN
downgrading QoS
1. Upon PDP context setup, Flexi ISN
contacts Policy Control Server over Gx 5. Quota runs out, Flexi ISN reports
User B interface for user B policies usage

Internet

4. PDP context is opened with

QoS “high”, all traffic is enabled. Service configuration (pre-defined
Flexi ISN starts to monitor quota policies):
consumption Flexi ISN
• HTTP
8. Flexi ISN modifies the PDP context QoS, Traffic matching rule “port 80”
users bandwidth is lowered Charging parameters
BW, location, roaming restrictions
• ALL TRAFFIC
Traffic matching rule “all traffic”
Charging parameters
For internal use
103 © Nokia Siemens Networks Presentation / Author / Date
BW, location, roaming restrictions
New IP-Features provided with charge@once
select v1.7 and v1.8

charge@once select v1.7 provides

 Fair Usage Policy
 Bill-Shock prevention (postpaid)

charge@once select v1.8 provides

 Bill-Shock prevention (prepaid)
 Gy-Alignement to v7

For internal use

104 © Nokia Siemens Networks Presentation / Author / Date
Bill-Shock-Prevention
EU-Regulation EC 717/2007
 To avoid Bill shocks for data, the roaming regulation EC 717/2007 is amended with article (6a) “ Transparency and
safeguard mechanisms for regulated data roaming services” which ensure the following:

From 1 July 2009 latest:

 Home Provider should deliver roaming customers mobile or other device personalized tariff information ( AoC) on
the charges applicable to the provision of data services when the roaming customer initiates a data roaming service in
an EU state other than his home network. ( Req. 1)
 Not concerned with this clause, are customers who explicitly notify their Home provider that AoC is not needed.( Req.
2)
From 1 July 2010 latest:
 CSPs should offer their roaming customers ( Pre-Postpaid) the possibility to set for free a maximum consumption
limit for data ( Req. 3)
 Customers get appropriate notification when approaching the limit ( Req. 4)
 Customers get blocked for additional consumption when the limit is reached and get appropriate notification ( Req. 5)
 De-block customers if explicitly wished by customer to set another consumption credit and resume with his data
service( Req. 6)

For internal use

105 © Nokia Siemens Networks Presentation / Author / Date
Bill-Shock-Prevention
Consumption Monitoring for Postpaid subscribers
Usage 50€ limit =80 € Consumption
Consumption Limit =80 €
Credit =0 €
limit =50 €

Usage 40€ Cut session

Credit control
Credit control

Threshold 1 Threshold 2
(80%) (100%)

cycle date=billing date De-blocking Reset consumption

received from at billing day
Send First Send Second customer with
Notification Notification + new increased
information how to consumption limit
continue
For internal use
106 © Nokia Siemens Networks Presentation / Author / Date
Bill-Shock-Prevention: NSN solution
CCR: Credit Control Request
OCS with
CCA: Credit Control Answer BSP functionality
RGn: Rating group configured in ISN
and c@o select
RG1, UseAA Data services
AoC

User Profile: Allowed MMS Streaming e-mail

Services for User A are Radius
sent to ISN: S1, S2, S3,

CCA: Grant/ Terminate/

Server
Postpaid with Credit
Fe

CCR: Initial/ Final

Control t ch WAP Downloading PoC
Us
er
P

Redirect
ro
d
te
file

an
gr
is
PDP context has been activated S1

Gn
SGSN

Flexi ISN Redirect

Service Request (S1) Redirect if AoC or Server
(Session Control) redirect if 100% BSP limit
Foreign network is reached - for further
proceeding
AoC for S1: Browsing 3 €/ MB
For internal use
107 © Nokia Siemens Networks Presentation / Author / Date
Thank You !

For internal use

108 © Nokia Siemens Networks <Presentation> / <Author> / 16 Oct 2022
Backup

For internal use

109 © Nokia Siemens Networks <Presentation> / <Author> / 16 Oct 2022
References

Content Document-Identifier

Ticketing

Event Charging – Payment PlugIN A50020-A3285-J000-2-76D6

Charging Ticketing IF-Spec P50020-Q1003-B600-08-7659

(GTP´; Diameter FBC; Corba, Radius)

IF-Description

Ro-Diameter for FBC A50020-A3275-K-1-76D6

Ro-Diameter for FBC with Flexi ISN A50020-A3279-K-2-76D6

Ro-Diameter for IMS A50020-A3276-K-2-76D6

Ro-Diameter for MMS A50020-A3277-K-3-76D6

Ro-Diameter for PoC A50020-A3278-K-2-76D6

Ro-Diameter for SMS P50020-Q3669-B500-01-76D6

Payment PlugIN A50020-A3245-K-1-76D6

For internal use

110 © Nokia Siemens Networks Presentation / Author / Date
References

Content Document Identifier

Service Specification

Fspec for FBC P50020-Q1344-B600-05-7659

Fspec for MMS P50020-Q1345-B600-04-7659

Fspec for IMS P50020-Q1343-B600-06-7659

Fspec for PoC P50020-Q1343-B600-06-7659

Diameter AVP usage

Microsoft Excel
Worksheet

For internal use

111 © Nokia Siemens Networks Presentation / Author / Date