Operator-Controlled Service

Description

The Operator-Controlled Service is a concept in 3GPP Policy and Charging Control (PCC) architecture, introduced in Rel-8. It refers to a service for which the PCRF (Policy and Charging Rules Function) has complete PCC rule information, including service data flow filter information. This information can be obtained through configuration in the PCRF or dynamically via interaction with an Application Function (AF). The operator-controlled service is a key enabler for differentiated QoS and charging based on service type.

In the PCC architecture, the PCRF is the central entity that makes policy decisions and manages charging rules. For an operator-controlled service, the PCRF has all the necessary details to generate PCC rules that define how the service's data flows should be treated. This includes the service data flow filters, which identify the packets belonging to the service, and the QoS parameters, such as QCI and bit rates, and charging information. The PCRF can either be pre-configured with these rules or receive them from an AF via the Rx interface.

The operator-controlled service is contrasted with a UE-controlled service, where the UE requests specific QoS treatment and the PCRF may not have complete rule information. In the operator-controlled model, the operator has full control over the service treatment, ensuring that the service receives the appropriate QoS and charging. This is important for services that require guaranteed performance, such as VoLTE or enterprise applications.

Key components involved include the PCRF, PCEF (Policy and Charging Enforcement Function), and AF. The PCRF generates PCC rules and sends them to the PCEF, which enforces them in the gateway (e.g., P-GW). The AF can provide service information to the PCRF, such as media type and required bandwidth, to assist in rule generation. The PCRF may also interact with the SPR (Subscription Profile Repository) for subscriber-specific policies.

The operator-controlled service is essential for enabling operators to offer tiered services, apply sponsored data, and ensure QoS for critical applications. It allows operators to monetize network resources by charging differently based on service characteristics. With the evolution to 5G, the concept remains relevant, with the PCF (Policy Control Function) taking the role of the PCRF and the AF interacting via the N5 interface.

Purpose & Motivation

The Operator-Controlled Service was introduced to address the need for operators to have complete control over the policy and charging treatment of specific services. Before Rel-8, policy control was limited, and operators lacked the ability to dynamically manage QoS and charging based on service data flows. With the rise of over-the-top (OTT) services and the need to support operator services like VoLTE and IMS, a more sophisticated policy framework was required. The PCC architecture was developed to provide this, and the operator-controlled service is a key concept within it.

The primary problem it solves is the lack of granular control over service treatment. In earlier releases, operators could only apply coarse-grained policies, such as per-APN or per-subscriber. This made it difficult to offer differentiated services or to ensure QoS for specific applications. The operator-controlled service allows the PCRF to have complete knowledge of the service data flows, enabling precise enforcement of QoS and charging rules. This is particularly important for services that require guaranteed bit rates or special charging, such as emergency services, enterprise VPNs, or sponsored data.

Historically, the concept was introduced in Rel-8 as part of the PCC architecture. It has evolved with subsequent releases, with the PCRF being replaced by the PCF in 5G, but the fundamental idea remains: the operator has full control over the service's policy and charging. This enables new business models, such as sponsored data and premium QoS, and ensures that operators can manage their network resources effectively.