Usage Parameter Control (UPC)

Description

Usage Parameter Control (UPC) is a traffic management function defined in the 3GPP vocabulary and rooted in ATM and broadband bearer concepts. The definition states that it is a set of actions taken by the network to monitor and control the offered traffic and the validity of the connection with respect to the traffic contract negotiated between the user and the network. In other words, UPC is the policing mechanism that enforces the traffic parameters a user has agreed to, such as peak cell rate, sustainable cell rate, and maximum burst size.

Architecturally, UPC sits at the edge of the network, typically in the entry node of the bearer service where the user's traffic first enters the operator domain. When a connection is established, the user and network negotiate a traffic contract that describes the expected traffic characteristics. The UPC function then observes the actual traffic on that connection. It uses algorithms such as the Generic Cell Rate Algorithm (GCRA) or leaky bucket variants to determine, on a cell-by-cell or packet-by-packet basis, whether the traffic conforms to the contract. The GCRA defines an arrival curve and a tolerance, allowing short bursts up to the negotiated limits while flagging cells that exceed the declared rate.

When non-conforming traffic is detected, UPC can take several actions. It may discard offending cells immediately, tag them as lower priority so that they are dropped first if congestion occurs, or in some implementations buffer or shape them. The choice depends on the operator's policy and the service class. The key point is that UPC protects well-behaved connections: by limiting or discarding excess traffic from a misbehaving source, it prevents that source from consuming more than its fair share of network resources.

UPC also verifies the validity of the connection itself. This includes checking that the connection exists, that the traffic parameters correspond to the negotiated contract, and that the traffic is being carried on a legitimately established connection. In this sense, UPC is both a traffic policing function and a connection admission verification function, complementing Connection Admission Control (CAC), which decides at setup time whether a new connection can be accepted. Together, CAC and UPC form the two pillars of traffic contract enforcement: CAC ensures the network does not over-commit resources when admitting connections, and UPC ensures admitted connections stay within their promised behavior.

UPC is closely related to other traffic control functions such as traffic shaping, which smooths traffic at the source rather than policing it in the network, and to QoS classes that define which traffic gets preferential treatment. In 3GPP specifications such as 21.905 (vocabulary) and 22.100 (UMTS service aspects), the term appears as part of the QoS and traffic management framework. Although its origins are in ATM-based bearer services, the concept persists in packet networks as policers, token buckets, and rate limiters that enforce committed and peak information rates.

Purpose & Motivation

UPC exists to protect network resources and the QoS of compliant users from the effects of non-compliant or malicious traffic. Without policing, a single user or application could send traffic far above the negotiated rate, congesting links and degrading service for everyone else. The traffic contract provides the basis for this protection: the user declares expected traffic characteristics, the network reserves resources accordingly via admission control, and UPC enforces the declaration in real time.

Historically, UPC was formalized in ATM networks in the 1990s, where fixed-size cells and well-defined traffic descriptors made policing relatively straightforward using the Generic Cell Rate Algorithm. When 3GPP defined bearer services for UMTS and later packet domains, the vocabulary inherited UPC to describe equivalent policing actions. The limitation of relying only on admission control was that admission control cannot predict actual behavior after setup; a user admitted at a low rate might suddenly transmit at a much higher rate. UPC fills that gap by continuously monitoring and acting on violations.

By standardizing the term and its function, 3GPP allowed equipment vendors and operators to implement interoperable policing behavior. It also enabled service level agreements to be enforced automatically, giving operators a concrete tool to guarantee QoS for premium subscribers while limiting the impact of misbehaving terminals or applications.