Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
Ty Interface Support
▀ Access Gateway Functionality for IMS Authorization
▄ Cisco ASR 5000 Series Enhanced Feature Configuration Guide
OL-22982-01
Charging Correlation
For IMS bearer charging, the IP Multimedia Core Network (IM CN) subsystem and the Packet Switched (PS) domain
entities are required to generate correlated charging data.
entities are required to generate correlated charging data.
In order to achieve this, the AGW provides the co-relation identifiers associated with the bearer along with its address to
the PDF. The PDF in turn sends the IMS Charging Identifier (ICID), which is provided by the P-CSCF, to the AGW.
The system generates the charging records including the co-related identifier as well as the ICID if received from PDF,
so that the correlation of charging data can be done with the billing system.
the PDF. The PDF in turn sends the IMS Charging Identifier (ICID), which is provided by the P-CSCF, to the AGW.
The system generates the charging records including the co-related identifier as well as the ICID if received from PDF,
so that the correlation of charging data can be done with the billing system.
The policy authorization transactions are carried over the Ty interface, which is based on the Diameter protocol.
Flow Based Charging with TPF/PCEF
Flow based charging handles differentiated charging of the bearer usage based on real time analysis of the service data
flows. Generally charging for the usage of bearer is based on subscriber at the bearer level. Flow based charging
provides a more granular charging mechanism where the charging is a dynamic function of the IP flows used by the
media for an application.
flows. Generally charging for the usage of bearer is based on subscriber at the bearer level. Flow based charging
provides a more granular charging mechanism where the charging is a dynamic function of the IP flows used by the
media for an application.
The Charging Rule Function (CRF) or PCRF is capable of provisioning charging rules to the system where the charging
rules are statically or dynamically defined at CRF/PCRF. A charging rule has a name, rating group, service identifier,
service data flow filter and other charging related parameters associated with it.
rules are statically or dynamically defined at CRF/PCRF. A charging rule has a name, rating group, service identifier,
service data flow filter and other charging related parameters associated with it.
The service data flow filters identify a flow and are unidirectional. These filters are associated with an IP 5 tuple
(protocol, local address, local port, remote address, remote port). In case of static or predefined filters, the IP flow will
be inspected by attributes beyond the 5 tuple of port, address and protocol. It is the function of Traffic Plane Function
(TPF)/ Policy and Charging Enforcement Function (PCEF) to analyze the data packet based on the installed flow filters.
If a packet does not match with the filters for the bearer, it is dropped by the TPF/PCEF. TPF/PCEF counts packets
based on individual flow for charging purpose.
(protocol, local address, local port, remote address, remote port). In case of static or predefined filters, the IP flow will
be inspected by attributes beyond the 5 tuple of port, address and protocol. It is the function of Traffic Plane Function
(TPF)/ Policy and Charging Enforcement Function (PCEF) to analyze the data packet based on the installed flow filters.
If a packet does not match with the filters for the bearer, it is dropped by the TPF/PCEF. TPF/PCEF counts packets
based on individual flow for charging purpose.
The charging rules also include the type of charging, (online or offline), the primary and secondary addresses for the
offline, and online charging systems as applicable for the credit control of the session.
offline, and online charging systems as applicable for the credit control of the session.
CRF/PCRF is also capable of generating unsolicited messages for provisioning charging rules for a bearer. The
TPF/PCEF is required to enforce the charging rules from any decision received from CRF/PCRF.
TPF/PCEF is required to enforce the charging rules from any decision received from CRF/PCRF.
The system supports the following charging rule operations over the Ty interface:
Installation, modification, and removal of dynamic charging rule using Ty interface.
Provide high priority to the dynamic charging rules over the static charging rules configured with the system.
Important:
The system does not need any static configuration knowledge of traffic categories (Rating-Groups)
dynamically received by CRF/PCRF and packets dropped due to the closure of ―gate‖ are not counted against the quota
for the matching category.
for the matching category.
A dynamic charging rule has the following attributes:
a charging rule name
service data flow filter(s)
precedence
―gate‖ status
QoS parameters