Layer 3

Description

In 3GPP terminology, 'L3' refers to the Network Layer (Layer 3) of the OSI and protocol stack models. It encompasses two primary domains: the User Plane and the Control Plane. In the User Plane, L3 is synonymous with the Internet Protocol (IP), which provides logical addressing (IP addresses) and enables end-to-end packet routing across interconnected networks. The mobile network (GPRS, EPS, 5GS) essentially provides IP connectivity, making IP the ultimate L3 service delivered to the User Equipment (UE).

In the Control Plane, L3 refers to the higher-layer signaling protocols that manage the radio and network connections. This includes the Radio Resource Control (RRC) protocol between the UE and the radio access network (RAN), which is considered a L3 protocol within the radio interface protocol architecture. It also includes the Non-Access Stratum (NAS) protocols between the UE and the core network (MME in LTE, AMF in 5GC), which handle mobility management, session management, and authentication. These L3 control protocols are responsible for establishing, maintaining, and releasing signaling and data connections, performing handovers, and carrying higher-layer session management messages.

The architecture involves L3 protocols interacting with lower layers (L2 for link-layer functions, L1 for physical transmission) and upper layers (application layers). Key components include IP header processing for packet routing, RRC protocol state machines (Idle, Connected), NAS protocol messages (Attach, Service Request, PDU Session Establishment), and routing tables in network nodes. Its role is fundamental: L3 provides the intelligence for connectivity. It determines how data finds its path from source to destination across the complex topology of cells, base stations, routers, and gateways, and it controls the network resources required to maintain that connectivity as users move.

Purpose & Motivation

The concept of Layer 3 exists as a fundamental architectural principle to separate concerns in network design. It isolates the functions of physical transmission (L1) and data link control (L2) from the complex tasks of end-to-end delivery across multiple hops and networks. In mobile telecommunications, this separation is critical for scalability, interoperability, and mobility support.

The adoption of IP as the unifying L3 for the user plane was motivated by the global success of the Internet. 3GPP networks evolved to become IP access networks, providing seamless connectivity to the Internet and other IP-based services. This solved the problem of creating isolated, technology-specific data services and enabled a ubiquitous, standard network layer. For the control plane, defining specific L3 protocols (RRC, NAS) was necessary to solve the unique problems of wireless, mobile networks. These problems include managing scarce radio resources efficiently, handling handovers between cells and base stations without breaking connections, and providing secure authentication and session management while hiding the complexity of the radio access from the core network.

Historically, the move towards a clear L3/IP-based architecture began in earnest with 3GPP Release 99 (UMTS), which established a packet-switched core. This addressed the limitations of circuit-switched data services, which were inefficient for bursty data traffic. The L3 control protocols have evolved significantly from GSM's RR and MM protocols to the more sophisticated RRC and NAS of UMTS, LTE, and 5G, each iteration introducing more efficient signaling, support for new capabilities (like multiple radio bearers, dual connectivity), and reduced latency, all to better manage the IP-based connectivity at the heart of the service.

Key Features

• Provides logical addressing (IP addresses) for global end-to-end connectivity
• Enables routing and forwarding of packets across heterogeneous networks
• Hosts critical control-plane protocols: RRC (for radio resource management) and NAS (for core network signaling)
• Manages connection states (e.g., RRC_IDLE, RRC_CONNECTED)
• Supports mobility management functions like handover and tracking area updates
• Forms the basis for all IP-based services delivered over 3GPP networks

Evolution Across Releases

Defining Specifications