Radio Network Layer

Description

The Radio Network Layer (RNL) is a conceptual layer within the control plane protocol stack of 3GPP radio access networks, namely UTRAN and E-UTRAN. It represents the collection of protocols and functions that are specifically related to radio network operation and are independent of the transport technology used to carry the signaling messages. The RNL sits above the Transport Network Layer (TNL), which provides reliable transport services (e.g., over IP, ATM, or SCTP). This separation is a key architectural principle, allowing the radio network protocols to be designed without dependency on the specifics of the underlying transport.

In UTRAN, the RNL encompasses protocols like Radio Resource Control (RRC) on the Uu interface, Radio Access Network Application Part (RANAP) on the Iu interface, Radio Network Subsystem Application Part (RNSAP) on the Iur interface, and Node B Application Part (NBAP) on the Iub interface. These protocols carry out the core radio network functions. For example, RRC handles connection establishment, broadcast of system information, and handover signaling with the UE. RANAP is used for signaling between the RNC and the core network (CN), handling procedures like Radio Access Bearer (RAB) assignment, location reporting, and UE context management. The RNL protocols define the specific messages and procedures for these functions.

The RNL interacts with the Transport Network Layer through well-defined Service Access Points (SAPs). The TNL provides a bearer service for the RNL messages, handling aspects like connection management, data transfer, and error correction for the transport link itself. This layered approach ensures that the radio network logic (e.g., how a handover is decided and executed) is decoupled from how the handover command is physically delivered between network nodes. The same RNL protocol (e.g., RNSAP) can operate over different TNL realizations (e.g., IP-based or ATM-based). In E-UTRAN (LTE), the principle continues with protocols like S1-AP (on S1 interface) and X2-AP (on X2 interface) belonging to the RNL, operating over an SCTP/IP-based TNL.

Purpose & Motivation

The Radio Network Layer concept was introduced to provide a clear separation of concerns in the design of 3GPP radio access networks, starting with UTRAN. The primary problem it solves is the independence of radio network functionality from the evolving transport technologies. In the early days of 3G, transport networks were often based on ATM. However, the industry was rapidly moving towards all-IP networks. By defining a distinct RNL, 3GPP ensured that the complex radio control protocols (RRC, RANAP, etc.) would not need to be redesigned if the underlying transport technology changed from ATM to IP.

This abstraction motivated a more future-proof and flexible architecture. It allows network operators to choose and evolve their transport networks independently of their radio network software and features. The TNL can be optimized for cost, capacity, and reliability based on available technology (e.g., moving from T1/E1 lines to Ethernet backhaul), without impacting the logic of radio resource management or handovers defined in the RNL. Furthermore, this layering simplifies protocol design and testing, as the RNL protocols can be specified assuming a reliable data transfer service from the layer below. This principle has been carried forward from UTRAN into E-UTRAN and NG-RAN, proving its enduring value in network architecture.

Key Features

• Logical layer containing all radio-specific control plane protocols (e.g., RRC, RANAP, S1-AP, X2-AP)
• Provides complete independence from the underlying Transport Network Layer (TNL) technology
• Defines the procedures and messages for radio resource management, mobility, and bearer management
• Interacts with the TNL through standardized Service Access Points (SAPs)
• Enables the same radio network functions to work over different transport technologies (e.g., ATM, IP)
• A foundational architectural concept in both UTRAN and E-UTRAN protocol stacks

Evolution Across Releases

Defining Specifications