Description
Layer Convergence Information (LCI) is a protocol-level information element defined within the 3GPP specifications to facilitate the convergence and coordination of different protocol layers, primarily within the packet data convergence protocol (PDCP) and service data adaptation protocol (SDAP) contexts. It operates by carrying metadata that describes how upper-layer protocols or services are mapped onto lower-layer transport mechanisms, including details about header compression, security contexts, and quality of service (QoS) flow mappings. This information is exchanged between the user equipment (UE) and the network nodes, such as the gNB in 5G or eNB in LTE, during session establishment, handover procedures, or upon reconfiguration events.
The architecture for LCI involves its inclusion in control plane signaling messages, such as those defined in the NGAP (Next Generation Application Protocol) and RRC (Radio Resource Control) protocols. In practice, LCI parameters are encoded within information elements that specify convergence layer configurations, enabling dynamic adaptation to network conditions and service requirements. For instance, during a handover from LTE to 5G NR, LCI can convey how PDCP contexts should be maintained or reestablished, ensuring seamless data forwarding and minimal interruption. Key components include the LCI value itself, which may indicate specific convergence protocols or modes, and associated timers or flags that govern its validity and application.
LCI's role in the network is critical for supporting heterogeneous network environments and multi-connectivity scenarios. By providing a standardized way to signal layer convergence properties, it allows for efficient resource utilization, reduced overhead, and enhanced performance for services like voice over IP (VoIP) or streaming video. In 5G systems, LCI is integrated with network slicing and QoS mechanisms, enabling tailored protocol stacks for different slice types. Its specifications span multiple releases, reflecting its evolution to address new radio technologies and service demands, with detailed procedures outlined in technical specifications such as 25.346 for LTE and 29.500 for 5G core network protocols.
Purpose & Motivation
LCI was introduced to solve the problem of protocol layer misalignment and inefficiency in converged network environments, where multiple access technologies (e.g., LTE, 5G NR, Wi-Fi) and diverse services coexist. Prior to its standardization, managing protocol convergence—such as header compression or security context transfer—during mobility events or session modifications often led to increased latency, packet loss, or suboptimal resource usage. The creation of LCI was motivated by the need for a unified signaling mechanism that could dynamically coordinate layer configurations between the UE and network, ensuring consistent service delivery and backward compatibility.
Historically, as 3GPP networks evolved from Rel-6 onward, the proliferation of data services and the introduction of all-IP architectures highlighted limitations in existing protocol stacks, which were not designed for seamless interworking between different radio access networks (RANs). LCI addresses these limitations by providing a flexible information element that encapsulates convergence parameters, enabling networks to adapt protocol behaviors without requiring extensive renegotiation or service disruption. This is particularly important for scenarios like handovers between 4G and 5G, where maintaining session continuity and QoS is paramount.
The ongoing relevance of LCI lies in its support for advanced features like dual connectivity, network slicing, and ultra-reliable low-latency communication (URLLC). By standardizing how convergence information is communicated, it reduces implementation complexity and fosters interoperability across vendor equipment, ultimately contributing to a more efficient and scalable mobile network ecosystem.
Classification
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (20 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
Studied in Rel-6, normative work from Rel-17.
In Release 17, enhancements to the Layer Convergence Information (LCI) function introduced a new reporting condition for QoS Monitoring Information. Additionally, the format for conveying location information within the LCI framework was updated.
In Release 18, the LCI function was enhanced to support the provisioning of periodicity information at the service data flow level and to enable the support of congestion information measurement and reporting. Furthermore, updates were made to include ToSTC (Type of Service Traffic Class) information within the Flow Description for both the ChargeableParty and AsSessionWithQoS APIs. A correction was also applied to the error reporting for additional QoS information.
- Update Flow Description Information with ToSTC in ChargeableParty API TS 29.122CR0634
- Update Flow Description Information with ToSTC in AsSessionWithQoS API TS 29.122CR0636
- Support of the congestion information measurement and reporting TS 29.122CR0741
- Support the provisioning of periodicity information at service data flow level TS 29.122CR0814
- Correction to additional QoS information error report TS 29.122CR0868
In Release 19, the LCI function was enhanced to support the exposure of energy consumption information, which underwent several updates and corrections. It also introduced new capabilities for reporting AF request rate limitation information and enhanced data rate limitation information for Non-GBR service data flows. Furthermore, support was added for delivering multiplexed media information over the NEF interface and for reporting QoS notification events with direction information.
- Introduce (S)RTP Multiplexed Media Information TS 29.122CR0889
- Support Energy related information exposure TS 29.122CR0898
- Support of on-path N6 signaling information to deliver Media related information TS 29.122CR0902
- Support of AF request rate limitation information reporting TS 29.122CR0903
- Update rate limit information reporting TS 29.122CR0942
- Enhancements on Data Rate Limitation Information for Non-GBR service data flow TS 29.122CR0948
+ 7 more changes
Explore further
Broader topics and technologies where LCI plays a role.
Defining Specifications
3GPP specifications that define or reference LCI, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 25.346 vj00 | MBMS in UTRA Technical Specification | Rel-19 |
| TS 29.122 vj40 | T8 Reference Point for Northbound APIs | Rel-19 |
| TS 29.500 vj50 | 5GC Service Based Architecture Specification | Rel-19 |