Same User, Different Price: How a 4G Network Can Charge Each Service Differently

Two users on the same 4G network can pay different rates for the same data, and one user can pay different rates for different services. In 3GPP’s policy and charging control, the rate and the charging model can depend on whether the user is roaming, where they are, the time of day, and the QoS provided, and they can change mid-session: a user might download a certain volume for a service free of charge, after which the service continues at a chargeable rate. In this post I walk through how this works in TS 23.203: the charging models, how online charging enforces a usage limit on a specific service or application, how the network asks for more credit before it runs out, and why charging is done in either the PCEF or the TDF for a given session, never both.

Charging requirements in this section apply to both PCC rule based charging and ADC rule based charging. The charging system can select the applicable rate based on:

  • whether the user is in the home network or roaming;
  • the user’s location, at a finer granularity than roaming;
  • whether the user is using the service via a Closed Subscriber Group (CSG) cell;
  • the time of day;
  • the QoS provided to the service.

The charging rate or charging model applicable to a service data flow or detected application traffic can change after that traffic has been used for a certain amount of time and/or volume. For example, the user may be allowed to download a certain volume of data for that service free of charge, and after that allowance is used up, the service continues at a chargeable rate.

The charging rate or charging model applicable to a service data flow or detected application traffic may change as a result of events in the service (for example, the insertion of a paid advertisement within a user-requested media stream).

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.

With online charging, the network can enforce a usage limit for a user on a specific service (identified by a PCC rule) or application (identified by an ADC rule). Online charging is typically associated with prepaid users, but the specification also allows it for post-paid users.

The online charging system can set a threshold on the remaining credit, in time, volume or both, and send it to the PCEF or TDF to monitor. When the remaining credit falls below the threshold, the PCEF or TDF requests credit re-authorization and reports how much credit remains.

For online charging, an online charging action can be applied upon PCEF or TDF events (for example, re-authorization upon a QoS change). For detected applications, an online charging action can also be applied upon application start and stop events.

The PCEF or TDF can be informed that no interaction with the charging systems is required for a PCC or ADC rule. It then performs neither accounting nor credit control for that service data flow or detected application traffic, and no offline charging information is generated.

For a given IP-CAN session, charging and enforcement are done in either the PCEF or the TDF, but not both (this applies to all IP-CAN sessions of the same APN). This avoids double charging and overcharging when a packet is discarded at the PCEF or TDF.

Leave a Reply

Your email address will not be published. Required fields are marked *