Bearer capability

Description

Bearer capability is a core concept in 3GPP service and bearer management. It refers to a transmission function that the user equipment (UE) requests from the network. In essence, it describes the set of characteristics that a bearer service must provide to support a particular application or communication session. These characteristics include data rate, delay tolerance, error rate, traffic class, and other quality-of-service (QoS) parameters. The bearer capability is signaled from the UE to the network during session establishment, allowing the network to allocate appropriate resources and configure the bearer accordingly. It is defined in 3GPP TS 21.905 (Vocabulary for 3GPP Specifications) and TS 22.101 (Service aspects; Service principles).

The concept originated in the early days of GSM and UMTS, where bearer capability was used to specify the technical characteristics of a circuit-switched or packet-switched connection. In GSM, for example, the Bearer Capability Information Element (BCIE) was included in call setup messages to indicate whether the call was voice, data, or fax, and to specify parameters such as data rate and modem type. In UMTS and later LTE, the concept evolved into the more comprehensive QoS framework, where bearers are established with specific QoS class identifiers (QCIs) and allocation and retention priority (ARP) values. Despite this evolution, the term "bearer capability" remains in the 3GPP vocabulary as a general descriptor of the transmission function requested by the UE.

Architecturally, bearer capability sits at the boundary between the UE and the network's bearer management functions. When a UE initiates a service, it includes a bearer capability request in the session management signaling. The network evaluates this request against the user's subscription profile, available resources, and policy rules. If the request can be accommodated, the network establishes a bearer with the requested characteristics. If not, the network may negotiate a lower capability or reject the request. This negotiation is essential for ensuring that the network can manage its resources efficiently while meeting user expectations. In 5G, the concept is further refined with the introduction of QoS flows, which are the finest granularity of QoS treatment in the 5G System. Each QoS flow is associated with a QoS profile that includes parameters analogous to bearer capability.

The definition of bearer capability has undergone several wording changes across releases. In Rel-4, it was defined as "a transmission function which the mobile station requests to the network." In Rel-5, the term "mobile station" was replaced with "user equipment," but a typographical error introduced "reques3GPP TS" instead of "requests." This error was corrected in Rel-6. In Rel-7, the definition was refined to "A transmission function which the UE requests to the network," with capitalization and abbreviation changes. From Rel-8 onward, the definition has remained essentially stable, with only minor formatting variations. These changes reflect the broader evolution of 3GPP terminology, particularly the shift from "mobile station" to "user equipment" as the standard term for the end-user device.

Bearer capability is closely related to other 3GPP concepts such as bearer service, QoS, EPS bearer, and QoS flow. It provides the initial request that triggers bearer establishment, and it is the foundation upon which more detailed QoS parameters are built. Understanding bearer capability is essential for engineers working on session management, policy control, and resource allocation in cellular networks. Although the term is less prominent in 5G than in earlier generations, its conceptual legacy persists in the QoS flow framework, where the UE still requests specific service characteristics from the network.

Purpose & Motivation

Bearer capability exists to provide a standardized way for the user equipment to communicate its service requirements to the network. In early cellular systems, different services (voice, data, fax) required different transmission characteristics, and the network needed to know what the user was requesting before it could allocate resources. The bearer capability information element served this purpose, carrying parameters such as data rate, connection type, and error tolerance. Without it, the network would have to guess the user's needs, leading to inefficient resource allocation or failed connections.

As networks evolved from circuit-switched to packet-switched, the concept of bearer capability was adapted rather than replaced. In UMTS and LTE, the focus shifted to QoS parameters and bearer establishment procedures, but the fundamental idea remained: the UE requests a transmission function, and the network decides whether and how to provide it. This request-response model is essential for network control and policy enforcement. It allows operators to differentiate services, apply charging rules, and manage congestion.

Historically, the term has its roots in GSM and ISDN, where bearer capability was a well-defined information element. Its inclusion in 3GPP specifications from Rel-4 onward ensured continuity with legacy systems while accommodating new technologies. The wording changes from "mobile station" to "user equipment" reflect the broadening scope of 3GPP beyond traditional mobile phones to include a wide range of devices. Today, bearer capability is a foundational concept that underpins the more sophisticated QoS architectures of LTE and 5G.