Baseline capabilities

Description

Baseline capabilities refer to the fundamental set of functions that a terminal (user equipment, UE) must support to operate within a 3GPP network, even when no specific service is active. These capabilities are defined in 3GPP specifications 21.904 and 21.905, and they form the foundation for any UE to access network services. The baseline capabilities include the ability to search for a network, synchronize with it, and register with authentication. Additionally, the UE must be able to negotiate its capabilities with the network, maintain the registration, and eventually terminate it. This ensures that a UE can establish a basic connection and be reachable, even if it does not use any advanced features.

The concept is crucial for interoperability and network access. When a UE powers on, it performs a cell search to find a suitable network, reads system information to synchronize, and then initiates a registration procedure. During registration, the network authenticates the UE and may request the UE's capabilities to determine what services it can support. The baseline capabilities guarantee that these steps can be performed by any compliant UE, regardless of its additional features. This allows networks to serve a wide range of devices, from simple IoT modules to advanced smartphones, without requiring all devices to support the same optional features.

In practice, baseline capabilities are implemented in the UE's protocol stack, including the non-access stratum (NAS) and access stratum (AS) layers. The NAS layer handles registration, authentication, and capability negotiation, while the AS layer handles cell search and synchronization. The network side, including the base station and core network, must also support these baseline procedures to ensure that any UE can attach. The capabilities are typically exchanged during the initial attach procedure, where the UE sends its capability information to the network, and the network may accept or reject certain features based on its own capabilities and policies.

The term has evolved over releases, with the definition being updated to use the term "UE" instead of "terminal" and to adopt British spelling ("synchronise") in later releases. These changes are editorial and reflect the harmonization of terminology across 3GPP specifications. The core meaning remains the same: baseline capabilities are the minimum requirements for a UE to operate in a network without any specific service. This concept is essential for ensuring that networks can support a diverse ecosystem of devices and that devices can roam across different networks.

From a testing and certification perspective, baseline capabilities are verified through conformance tests that check the UE's ability to perform cell search, synchronization, registration, and capability negotiation. These tests are part of the UE certification process and ensure that devices meet the minimum requirements for network access. The baseline capabilities also serve as a reference for developers and network engineers to understand the essential functions that must be implemented in any UE.

Purpose & Motivation

The baseline capabilities concept exists to define a common minimum set of functions that any terminal must support to operate in a 3GPP network. Without such a definition, it would be difficult to ensure interoperability between devices and networks, as manufacturers might implement different subsets of features. The baseline capabilities provide a clear target for UE designers and network operators, ensuring that even the simplest devices can attach to the network and be managed.

The term solves the problem of service-less operation. A UE might not have any active service (e.g., no voice call or data session), but it still needs to be reachable for paging, location updates, and emergency calls. The baseline capabilities ensure that the UE can register with the network and maintain its registration, so that the network can reach it when needed. This is particularly important for IoT devices that may only transmit infrequently but must remain connected.

Historically, the definition was introduced in R99 and has been refined over releases to use consistent terminology (UE instead of terminal) and to clarify the scope. The stability of the definition over many releases indicates that the concept is fundamental and well understood. It continues to be relevant in 5G and beyond, as networks support an ever-growing variety of devices with different capabilities.