RAN-based Notification Area

Description

The RAN-based Notification Area (RNA) is a core mobility management concept for the RRC_INACTIVE state introduced in LTE (eNB-based) and evolved in NR (gNB-based). It defines a geographical area, configured by the RAN, within which a User Equipment (UE) can move freely without notifying the network of its cell-level location. The RNA is composed of one or more cells, which can be configured as a list of cells, a list of RAN areas (each being a group of cells), or a tracking area. When a UE transitions to RRC_INACTIVE, the last serving base station (the last serving gNB in NR or eNB in LTE) assigns it an RNA, typically based on UE mobility patterns, subscription, or network policy.

The primary operational mechanism involves the UE performing periodic or triggered RNA Updates. While in RRC_INACTIVE, the UE monitors system information to identify the RNA Identity of its current cell. If the UE moves to a cell whose RNA ID is not part of its assigned RNA, it must initiate an RNA Update procedure to inform the RAN of its new location and potentially get a new RNA assigned. This procedure is a lightweight RRC connection resume, reactivating the UE context stored in the RAN and the core network. Conversely, if the UE remains within its RNA, it can stay in this low-power state indefinitely. When downlink data arrives for the UE, the RAN initiates a paging procedure within all cells of the UE's last known RNA to locate and resume the connection.

The architecture relies on the RAN's ability to store the Access Stratum (AS) context of the UE and manage the RNA area. In NR, this is facilitated by the NG-RAN architecture where gNBs are interconnected via the Xn interface. The last serving gNB acts as the “Anchor” gNB, retaining the UE context. Other gNBs within the RNA can assist in paging. RNA configuration is signaled to the UE via RRCRelease messages and broadcast in system information blocks (SIBs). This mechanism decouples mobility management for inactive UEs from the core network's Tracking Area (TA), reducing signaling load on the N2/N3 interfaces and enabling faster state transitions compared to the traditional IDLE state procedures.

Purpose & Motivation

RNA was created to address the signaling overhead and power consumption challenges associated with the massive number of IoT and smartphone devices that transmit data infrequently but require always-on connectivity. Traditional LTE mobility relied on two main states: RRC_IDLE and RRC_CONNECTED. IDLE state required core network (MME) involvement for location updates (Tracking Area Updates) and paging, causing latency and signaling load. CONNECTED state kept radio resources active, wasting power for bursty traffic. The RRC_INACTIVE state, for which RNA is a key enabler, was introduced to provide a middle ground.

The motivation stemmed from 5G use cases like massive Machine-Type Communication (mMTC) and enhanced Mobile Broadband (eMBB) with bursty traffic patterns. RNA solves the problem by keeping the UE's context in the RAN, allowing mobility within an area without core network signaling. This drastically reduces the signaling storm that would occur if every small cell change required a Tracking Area Update. It also enables faster connection resume (compared to IDLE to CONNECTED transition) and better battery life than staying in CONNECTED. RNA represents a shift of mobility management responsibility from the core to the RAN, optimizing for scenarios where session continuity with low latency and low signaling is paramount.

Key Features

• Defines an area for mobility of UEs in RRC_INACTIVE state without location updates
• Configured and managed by the RAN (gNB/eNB), not the core network
• Triggers an RNA Update procedure when UE moves outside the assigned area
• Enables RAN-based paging within the RNA for downlink data notification
• Supports flexible configurations: cell list, RAN area list, or tracking area
• Reduces signaling to core network (AMF/MME) and saves UE battery compared to frequent TAUs

Evolution Across Releases

Defining Specifications