Description
Best effort service is a service model defined by 3GPP as one that 'provides minimal performance guarantees, allowing an unspecified variance in the measured performance criteria.' This definition captures the essence of best effort delivery: the network will attempt to deliver data, but makes no promises about how quickly, how reliably, or at what rate. The measured performance — throughput, latency, jitter, packet loss — can vary widely and unpredictably based on network conditions, the number of active users, and the types of traffic being carried at any moment.
In the context of 3GPP networks, best effort service is the default service model for packet data connections that are not associated with specific QoS guarantees. When a user activates a PDP context (in GPRS/UMTS) or establishes a PDU session (in 5G) without requesting specific QoS parameters, the connection operates in best effort mode. Similarly, non-GBR bearers in LTE and non-guaranteed QoS flows in 5G implement best effort service principles, even though they may receive differentiated treatment based on scheduling priority and bit rates.
The architecture supporting best effort service relies on the inherent statistical multiplexing capability of packet-switched networks. Unlike circuit-switched networks, where a dedicated channel must be reserved for each connection, packet-switched networks allow many connections to share the same transmission resources. Best effort service leverages this by allowing all traffic to compete for available bandwidth, with the network scheduling and forwarding packets on a first-come, first-served basis or according to simple priority rules. When congestion occurs, packets may be queued, delayed, or dropped, and it is the responsibility of higher-layer protocols (primarily TCP) to detect and recover from these losses through retransmission and rate adaptation.
The practical implications of best effort service are significant for both operators and users. For operators, it enables maximally efficient use of network resources because capacity is never pre-allocated or wasted on idle connections. The trade-off is that during peak demand periods, all users experience degraded performance simultaneously. For users and application developers, best effort service means that applications must be designed to tolerate variability — web browsers buffer content, video players adapt their bit rate, and file transfers use TCP to handle congestion. Applications that cannot tolerate variability (like real-time voice or video) require higher QoS classes.
Despite its limitations, best effort service remains the dominant service model in mobile networks by volume. The vast majority of mobile data traffic — web browsing, social media, email, software updates, background sync — operates acceptably under best effort conditions. The model's simplicity, scalability, and cost-effectiveness make it indispensable, and even in 5G networks with sophisticated QoS frameworks, best effort service remains the foundation upon which more demanding services are layered.
Purpose & Motivation
Best effort service exists to provide a simple, scalable, and economical baseline for data communication that requires no explicit resource reservation or performance commitment from the network. Its fundamental purpose is to maximize the number of users and applications that can be served with the available network capacity by avoiding the inefficiency of dedicated resource allocation. This is particularly important in mobile networks, where radio spectrum is scarce and expensive, and where traffic patterns are highly variable.
The concept addresses the challenge of providing ubiquitous data connectivity at an affordable cost. If every data connection required guaranteed performance, the network would need to be dimensioned for peak demand across all users simultaneously, resulting in prohibitively expensive infrastructure that would be underutilized most of the time. Best effort service solves this by allowing the network to be dimensioned for average rather than peak demand, with the understanding that performance will degrade gracefully during busy periods.
Historically, the best effort model originated in the design of the Internet, where the end-to-end principle placed intelligence at the edges of the network rather than in the core. This philosophy proved remarkably successful for scaling data communication, and 3GPP adopted it for packet-switched mobile data services starting with GPRS. The best effort service model served as the foundation of mobile Internet access, with more sophisticated QoS mechanisms layered on top as technology and market demands evolved. Even in the 5G era, best effort service remains essential as the default and most widely used service model, providing the baseline connectivity upon which differentiated services are built.
What changed in its specifications
The latest release-to-release comparison of specifications that define Best effort service. Each summary describes the whole specification, not only this term.
Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TR 21.905 →Rel-19 brings only minor changes to TS 22.060: 0 clauses changed, with no change attributed to a release feature.
Full comparison in TS 22.060 →Release Timeline
Evolution Across Releases
An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.
Defining Specifications
3GPP specifications that define or reference Best effort service, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj20 | 3GPP Terminology and Definitions | Rel-19 read |
| TS 22.060 vj00 | GPRS Stage 1 Service Description | Rel-19 read |