RAN-based Notification Area Code

Description

The RAN-based Notification Area Code (RANAC) is a fundamental component of the RRC_INACTIVE state mobility management in 5G New Radio (NR). A RAN-based Notification Area (RNA) is a logical area, composed of one or multiple cells, defined by the RAN for the purpose of tracking and paging a User Equipment (UE) that is in the RRC_INACTIVE state. The RANAC is the code that uniquely identifies this RNA within the scope of a gNodeB or a set of gNodeBs. When a UE enters RRC_INACTIVE, the network assigns it an RNA, and the UE stores the corresponding RANAC.

The operation revolves around the UE's mobility within this RNA. While in RRC_INACTIVE, the UE can move freely within the cells that belong to its assigned RNA without notifying the network, thus conserving battery power and reducing signaling. The UE performs periodic RNA Updates (RNAU) or is triggered to perform one when it moves to a cell that is outside its current RNA. During this RNAU procedure, the UE provides its last stored RANAC and other context information to the new cell, allowing the RAN to retrieve the UE's context from the previous serving gNodeB and update its location.

When downlink data arrives for a UE in RRC_INACTIVE, the RAN initiates a RAN-based paging procedure within the UE's last known RNA. The gNodeBs within that RNA broadcast a paging message containing the UE's identifier and the relevant RANAC. The UE, monitoring for paging in its current cell, responds if it is within the paged area. This mechanism is more efficient than core-network-level paging (via the 5GC) for inactive UEs, as it localizes the paging traffic to a smaller RAN-defined area. The RANAC is thus a key enabler for efficient state management, balancing the trade-off between signaling overhead and UE power consumption, which is particularly important for massive Machine-Type Communication (mMTC) and general mobile broadband users.

Purpose & Motivation

RANAC was created to address the signaling and power efficiency challenges associated with managing a massive number of connected devices, especially for IoT scenarios, in 5G networks. Previous states, like RRC_IDLE in LTE, required core network (MME) involvement for tracking area updates and paging, which could generate significant signaling load. The RRC_CONNECTED state, while keeping the UE context in the RAN, consumes more UE battery as the radio connection is maintained. The new RRC_INACTIVE state, and its associated RNA concept identified by RANAC, provides a middle ground.

The primary problem RANAC solves is enabling efficient location tracking and paging for UEs that are inactive but have data sessions that may resume shortly. By defining an RNA managed solely by the RAN, location updates (RNA Updates) do not burden the 5G Core (5GC) unless the UE moves beyond a RAN-controlled area. This reduces signaling on the N2 interface between the RAN and the AMF. Furthermore, RAN-based paging using the RANAC confines paging messages to a specific set of cells, reducing unnecessary paging load across the entire tracking area and enabling faster connection resumption.

This innovation was motivated by the 5G requirement to support massive IoT deployments with billions of devices that transmit data sporadically. For such devices, minimizing signaling and power consumption is paramount. RANAC, as part of the RNA mechanism, allows these devices to remain reachable by the network with minimal energy expenditure, extending battery life for years, while also ensuring the network can efficiently deliver incoming data when needed, fulfilling the promises of 5G mMTC and enhanced mobile broadband efficiency.

Key Features

• Uniquely identifies a RAN-based Notification Area (RNA) within 5G NR
• Enables UE mobility within the RNA without signaling (cell reselection)
• Triggers RNA Update procedure when UE moves outside its current RNA
• Used in RAN-based paging to locate UEs in RRC_INACTIVE state
• Reduces signaling to the 5G Core Network (5GC) for inactive UEs
• Critical for power-saving operation of IoT and mobile devices in RRC_INACTIVE

Evolution Across Releases

Defining Specifications