Online/Offline Charging - Cisco ASR 5000 series Product Overview

Hide thumbs Also See for ASR 5000 series:
Table of Contents

Advertisement

▀ Features and Functionality - Base Software
3GPP TS 32.299 online mode ―Gy‖ DCCA, including:

Online/Offline Charging

The Cisco EPC platform offers support for online and offline charging interactions with external OCS and CGF/CDF
servers.
Online Charging
Gy/Ro Reference Interface
:
The StarOS 9.0 online prepaid reference interface provides compatibility with the 3GPP TS 23.203, TS 32.240, TS
32.251 and TS 32.299 specifications. The Gy/Ro reference interface uses Diameter transport and IPv6 addressing.
Online charging is a process whereby charging information for network resource usage must be obtained by the network
in order for resource usage to occur. This authorization is granted by the Online Charging System (OCS) upon request
from the network. The P-GW uses a charging characteristics profile to determine whether to activate or deactivate
online charging. Establishment, modification or termination of EPS bearers is generally used as the event trigger on the
PCRF to activate online charging PCC rules on the P-GW.
When receiving a network resource usage request, the network assembles the relevant charging information and
generates a charging event towards the OCS in real-time. The OCS then returns an appropriate resource usage
authorization that may be limited in its scope (e.g. volume of data or duration based). The OCS assigns quotas for rating
groups and instructs the P-GW whether to continue or terminate service data flows or IP CAN bearers.
The following Online Charging models and functions are supported:
Time based charging
Volume based charging
Volume and time based charging
Final Unit Indication and termination or redirection of service data flows when quota is consumed
Reauthorization triggers to rearm quotas for one or more rating groups using multi-service credit control
(MSCC) instances
Event based charging
▄ Cisco ASR 5000 Series Product Overview
Rating-Group for quota-to-traffic association
CC-Failure-Handling and CC-Session-Failover features
Final-Unit-Action TERMINATE behavior
Tariff-Time-Change feature.
Final-Unit-Action REDIRECT behavior
Quota-Holding-Time: This defines a user traffic idle time, on a per category basis, after which the usage
is returned and no new quota is explicitly requested
Quota-Thresholds: These AVPs define a low value watermark at which new quota will be sought before
the quota is entirely gone; the intent is to limit interruption of user traffic.
These AVPs exist for all quota flavors, for example ―Time-Quota-Threshold‖.
Trigger-Type: This AVP defines a set of events which will induce a re-authentication of the current
session and its quota categories.
PDN Gateway Overview
OL-22938-02

Advertisement

Table of Contents
loading

Table of Contents