Who Charges the Traffic: the PCEF or the TDF? Application Detection and Control Explained
Application Detection and ControlApplication Detection and Control (ADC) detects application traffic, including its start and stop, and applies the enforcement actions and charging specified in the ADC/PCC rule. ADC is implemented either by the TDF or by the PCEF enhanced with ADC.
Depending on operator requirements, one of two models can be applied: solicited or unsolicited application reporting. Unsolicited application reporting is supported by the TDF only.
Solicited application reporting. The PCRF instructs the TDF, or the PCEF enhanced with ADC, by activating the appropriate ADC/PCC rules. Through these rules the PCRF.
- specifies which applications to detect;
- specifies whether the start and stop of the application traffic are reported (reporting can be muted per rule);
- may, in a dynamic ADC/PCC rule, specify the enforcement actions to apply to the detected traffic. The PCRF may activate application detection only if the user profile configuration allows it.
Unsolicited application reporting- The TDF is pre-configured with the applications to detect and report. The PCRF may enable enforcement in the PCEF based on the service data flow description provided by the TDF. User profile configuration indicating whether application detection and control can be enabled is not required.
Reporting to the PCRF (both models)-A report states whether it is for a start or a stop, the detected application identifier and, if deducible, the service data flow descriptions of the detected traffic. For application types whose descriptions are deducible, start and stop may be indicated multiple times, together with an application instance identifier. The TDF or the PCEF enhanced with ADC assigns this identifier dynamically, so the PCRF can correlate start and stop events with a specific service data flow description. Reporting does not depend on enforcement: unless muted, every start and stop is reported, even if the traffic is discarded by the rule’s enforcement actions. TDF operating in the solicited application reporting modelWhen the TDF cannot provide to the PCRF the service data flow description for the detected applications, the TDF performs charging, gating, redirection and bandwidth limitation for the detected applications, as defined in the ADC rule.
When the TDF provides the PCRF with the service data flow description, either the PCRF may take control of the actions resulting from application detection, by having charging and policy enforcement applied per service data flow, or the TDF itself may perform charging, gating, redirection and bandwidth limitation. It is the PCRF’s responsibility to coordinate the PCC rules with the ADC rules in order to ensure consistent service delivery.
To avoid charging the same traffic in both the TDF and the PCEF, TS 23.203 supports charging and enforcement implemented in either the PCEF or the TDF for a given IP-CAN session, but not both. This applies to all IP-CAN sessions of the same APN.
When the TDF is used for charging, the ADC rules determine the online and offline charging characteristics. Offline charging uses usage reporting over the Gzn interface, and online charging uses credit management and reporting over the Gyn interface. The PCEF is in this case not used for charging and enforcement (based on active PCC rules and APN-AMBR configuration), but still performs bearer binding based on the active PCC rules. In order to avoid traffic that is charged in the TDF later being discarded by the policing function in the PCEF, the assumption is that no GBR bearers are required when the TDF is the charging and policy enforcement point. In addition, the DL APN-AMBR in the PCEF must be configured with such high values that it does not result in discarded packets.
As an example of this either/or rule, the IMS APN, which requires dynamic PCC rules, can be configured for PCEF-based charging and enforcement, while a regular internet access APN is configured so that the TDF performs both. Because the IMS and internet access APNs are different, they correspond to different IP-CAN sessions, so each session still has only one charging and enforcement point.
An operator may also apply both the PCEF and the TDF for enforcement and charging in a single IP-CAN session, as long as the network is configured so that the traffic charged and enforced in the PCEF does not overlap with the traffic charged and enforced by the TDF. In this case, TS 23.203 recommends that the PCRF provide different charging keys to the PCEF and to the TDF.
TDF charging is applicable only to the solicited application reporting model. Usage monitoring can also be activated in conjunction with application detection and control, and it too is applicable only to the solicited application reporting model.