Description
The Assistance Information bit for Local Cache (AILC) is a specific signaling element defined within the LTE Radio Resource Control (RRC) protocol, primarily documented in 3GPP TS 36.331 (RRC protocol specification) and referenced in TS 36.323 (Packet Data Convergence Protocol specification). It functions as a single-bit flag transmitted by the eNodeB to the User Equipment (UE) within specific RRC messages, most notably within the System Information Block (SIB) type 2 or potentially within dedicated RRC signaling. The core purpose of this bit is to indicate whether the network supports and allows the UE to locally cache assistance information received from the network, particularly information related to positioning services.
Architecturally, AILC operates within the control plane of the LTE Radio Access Network (E-UTRAN). The eNodeB, as the controlling entity for radio resources, sets the value of the AILC bit based on network configuration and capabilities. When the UE receives an RRC message containing the AILC bit set to 'true' or 'supported', it interprets this as permission to store certain network-provided assistance data in its non-volatile memory (local cache). This cached data typically includes elements like cell identities, timing information, and other parameters that can aid in subsequent positioning procedures, such as Observed Time Difference of Arrival (OTDOA) or Enhanced Cell ID (E-CID).
From a procedural perspective, the mechanism works as follows: During initial access or a positioning session, the UE receives assistance data from the network via RRC or LPPa/LPP signaling. If the AILC bit is set, the UE can store this data. In future sessions, especially upon cell reselection or return from idle mode, the UE can first check its local cache for valid assistance information before requesting a fresh transmission from the network. The UE must manage the cache validity, often tied to a timestamp or a validity timer also provided by the network. This cache-and-reuse mechanism significantly reduces the need for repetitive signaling of largely static or slowly changing assistance data.
Its role in the network is to optimize positioning-related signaling and improve the user experience for location-based services. By minimizing the number of bytes that need to be transmitted over the air interface for positioning assistance, AILC contributes to reduced latency in obtaining a position fix, lower signaling load on the network, and decreased UE power consumption. It is a key enabler for efficient, network-assisted positioning in LTE and serves as a foundational concept for similar optimizations in 5G NR.
Purpose & Motivation
AILC was introduced to address the inefficiency of repeatedly transmitting the same, relatively static assistance information to a UE every time it needed to perform a positioning operation. Prior to its introduction, assistance data for techniques like OTDOA—which includes reference cell information, neighbor cell lists, and precise timing data—was typically sent in full during each positioning session. This created significant and unnecessary signaling overhead, especially for UEs that were stationary or moving within a limited area, as the assistance data for nearby cells remained largely unchanged.
The historical context for AILC's creation is the growing importance and demand for accurate, low-latency location services in LTE networks. Applications ranging from emergency (E911) services to commercial location-based services and IoT asset tracking required efficient positioning mechanisms. The traditional approach of full assistance data transfer per session was identified as a bottleneck, consuming radio resources and increasing the time-to-first-fix (TTFF) for positioning. AILC, as a simple 1-bit indicator, provided an elegant and low-overhead solution to this problem by enabling a client-side caching strategy.
It solves the problem by shifting the paradigm from a 'always-transmit' model to a 'cache-and-validate' model. This addresses limitations in spectral efficiency, network capacity, and UE battery life. The motivation was to create a standardized mechanism that allows networks to explicitly control and authorize caching behavior, ensuring interoperability between UEs and network equipment from different vendors while achieving the desired optimization gains.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (26 CRs across 5 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 15, the AILC (Assistance Information bit for Local Cache) function was newly introduced to the PDCP layer. This addition involved specifying a 1-bit field in the PDCP PDU header to indicate whether a corresponding uplink PDCP SDU may be transferred to a local cache entity when configured by upper layers. Specifically, the AILC bit is set to '1' to permit this potential transfer or to '0' otherwise, as defined through a Change Request to TS 36.323.
- Running 36.323 CR to introduce assistance information for local cache TS 36.323CR0211
- Introduce assistance information for local cache 36.331 CR TS 36.331CR3178
- Addition of broadcast of positioning assistance data TS 36.331CR3450
- Introduction of Geofencing information in CMAS TS 36.331CR3523
- SI message scheduling enhancement to avoid conflicts between legacy and positioning System Information TS 36.331CR3596
- Correction on system information blocks acquisition TS 36.331CR3614
+ 8 more changes
In Release 16, the new AILC (Assistance Information bit for Local Cache) function was introduced. This addition provides a 1-bit indicator within the PDCP header to signal whether a corresponding uplink PDCP SDU may be transferred to a local cache entity. Specifically, when the AILC field is set to '1', it indicates that the SDU may be transferred to the local cache, enabling more efficient data handling when the PDCP entity is configured accordingly by upper layers.
- Addition of broadcast of barometric pressure assistance data TS 36.331CR4026
- Broadcast of TBS assistance data TS 36.331CR4134
- Correction regarding placement of cell specific SSB QCL information TS 36.331CR4393
- Miscellaneous corrections on overheating assistance information for NR SCG TS 36.331CR4489
- Correction regarding overheating assistance for SCG TS 36.331CR4494
In Release 17, the new AILC (Assistance Information bit for Local Cache) function introduced a 1-bit indicator within the PDCP header to signal whether a PDCP SDU may be transferred to a local cache entity. This explicit bit, set to '1' to permit transfer or '0' to prohibit it, provided a standardized control mechanism for cache management that was not defined in prior releases. The function operates when the PDCP entity is configured by upper layers to utilize this assistance information.
In Release 18, the new feature for the "AILC" function introduced a dedicated 1-bit field in the PDCP header to act as assistance information for local caching. Specifically, this AILC field explicitly indicates whether the corresponding uplink PDCP SDU may be transferred to a local cache entity when the PDCP entity is configured by upper layers. This provides a direct signaling mechanism, where a value of '1' permits potential cache transfer, while '0' indicates it is not needed.
In Release 19, the new AILC (Assistance Information bit for Local Cache) function was introduced to provide control over data transfer to a local cache entity. Specifically, a 1-bit AILC field was added within the PDCP layer to indicate whether a corresponding uplink PDCP SDU may be transferred to the local cache when the PDCP entity is configured by upper layers. This allows the network to explicitly signal, on a per-SDU basis, if the data should be considered for local caching (set to 1) or not (set to 0).
Explore further
Broader topics and technologies where AILC plays a role.
Defining Specifications
3GPP specifications that define or reference AILC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 36.323 vj00 | PDCP Protocol Specification | Rel-19 |
| TS 36.331 vj00 | LTE RRC Protocol Specification | Rel-19 |