RAN-based Notification Area Update

Description

The RAN-based Notification Area Update (RNAU) is a fundamental mobility management procedure defined for the 5G New Radio (NR) system, specifically for User Equipment (UE) operating in the RRC_INACTIVE state. This state, introduced in 5G, is a low-power state where the UE's Access Stratum (AS) context is stored in both the UE and the last serving gNB (or NG-RAN node), but the UE is not actively transmitting or receiving user plane data. The UE is assigned a RAN Notification Area (RNA), which is a logical area defined by the RAN, typically comprising one or multiple cells. The purpose of the RNAU procedure is for the UE to periodically or event-triggered update the network when it moves outside its configured RNA, ensuring the network knows a paging area to locate the UE if downlink data arrives or for other network-initiated actions.

Architecturally, the RNAU procedure is initiated by the UE when a trigger condition is met, such as upon leaving the current RNA, upon expiry of a periodic RNAU timer, or upon cell reselection to a cell that is not part of the current RNA list. The UE performs the procedure by initiating a transition from RRC_INACTIVE to RRC_CONNECTED, specifically using the RRC Resume Request message. This message includes a Resume ID, which allows the receiving gNB (which may be different from the last serving gNB) to retrieve the UE's AS context from the previous gNB via the Xn interface. The procedure involves context retrieval, integrity protection verification, and security key update. Upon successful completion, the network may keep the UE in RRC_CONNECTED if there is pending data, or it may reconfigure a new RNA and move the UE back to RRC_INACTIVE.

The RNAU's role is critical for balancing mobility management efficiency with UE power saving. It decouples frequent location updates from the core network (5GC), handling them within the RAN. This reduces signaling load on the N2 and N3 interfaces towards the Access and Mobility Management Function (AMF) and User Plane Function (UPF). The RNA is managed by the RAN, allowing for more dynamic and traffic-adaptive area sizing compared to the core network's Tracking Areas (TAs). The procedure works in conjunction with RAN-based paging, where a gNB can page the UE within the last known RNA without involving the core network for initial paging, leading to faster call setup times and reduced latency for mobile terminated services.

Purpose & Motivation

RNAU was created to address the limitations of legacy mobility management, particularly for the massive number of IoT devices and smartphones with bursty data traffic expected in 5G. In 4G LTE, a UE in RRC_IDLE state would perform a Tracking Area Update (TAU) procedure with the core network (MME) whenever it moved outside its Tracking Area List. This involved always establishing an RRC connection and performing NAS signaling, which incurred significant signaling overhead, core network load, and UE battery consumption for what were often very short, infrequent data transmissions.

The introduction of the RRC_INACTIVE state in 5G NR required a corresponding RAN-centric mobility management mechanism. The purpose of RNAU is to enable efficient, lightweight location tracking for UEs that are inactive but have a valid AS context stored in the RAN. It solves the problem of frequent core network signaling by keeping location updates local to the RAN. This is motivated by the need to support enhanced Mobile Broadband (eMBB) with always-on connectivity expectations and massive Machine-Type Communications (mMTC) with a vast number of low-power devices. RNAU allows the network to maintain reachability for these UEs while optimizing the trade-off between location accuracy, signaling cost, and UE power consumption, which was not optimally balanced in previous generations.

Key Features

• Enables location updates for UEs in RRC_INACTIVE state without core network (AMF) involvement for the update itself
• Triggered by UE mobility outside the configured RAN Notification Area (RNA) or by a periodic timer
• Uses the RRC Resume procedure for context retrieval and security reactivation
• Allows the RAN to dynamically configure and manage the RNA size and composition
• Reduces signaling overhead on N2 interface and UE battery consumption compared to core-centric TAUs
• Supports RAN-based paging by keeping the UE's location known at the RNA level

Evolution Across Releases

Defining Specifications