Extended Access Barring

Description

Extended Access Barring (EAB) is a feature standardized by 3GPP to provide enhanced control over network access during congestion scenarios, particularly relevant for networks with a high density of Machine-Type Communication (MTC) devices. It operates by allowing the network to broadcast barring information within system information blocks (SIBs), specifically SIB14 in LTE and SIB14/SIB15 in NR. This information defines which categories of User Equipments (UEs) are temporarily barred from initiating access to the network. UEs are configured with an EAB category, which can be based on their subscription profile (e.g., 'EAB for MTC devices') or other criteria. Upon reading the EAB parameters broadcast by the network, a UE applies the barring check before initiating any access procedure for mobile-originated calls, session requests, or signaling, unless for emergency services or high-priority access classes.

The architecture for EAB involves both the Radio Access Network (RAN) and the Core Network (CN). The CN, specifically the Mobility Management Entity (MME) in EPS or the Access and Mobility Management Function (AMF) in 5GS, can provide EAB configuration data to the RAN nodes (eNB/gNB). The RAN then incorporates this information into the broadcast system information. The barring parameters include a barring factor and a barring time, similar to traditional Access Class Barring (ACB), but are applied specifically to the configured EAB categories. The mechanism is stateless from the network's perspective after broadcast, as the UE autonomously enforces the barring.

EAB's role in the network is crucial for overload and congestion control, especially in the context of IoT and MTC deployments where a massive number of devices might simultaneously attempt access, potentially causing signaling storms. By selectively barring lower-priority or delay-tolerant devices, EAB ensures that radio and core network resources are preserved for human users, emergency services, and other high-priority communications. It represents a more granular and flexible approach compared to traditional ACB, which primarily differentiates based on a fixed set of 16 access classes.

Purpose & Motivation

EAB was introduced to address the specific challenge of network congestion caused by a massive influx of access attempts from Machine-Type Communication (MTC) devices, a key scenario in the Internet of Things (IoT). Traditional congestion control mechanisms like Access Class Barring (ACB) were designed primarily for human-centric traffic and offered limited granularity. ACB uses 16 access classes (0-9 for regular users, 10 for emergency, 11-15 for specific high-priority users like network staff), which proved insufficient for efficiently managing diverse IoT device categories with varying priorities and service requirements.

The creation of EAB was motivated by the need for a more sophisticated, subscription-based barring mechanism. It allows operators to define policies based on device type, subscription profile, or service characteristics rather than just a static class. This enables operators to protect the network during overload events—such as a power restoration after a blackout triggering millions of smart meters to reconnect—by barring only the low-priority MTC devices while allowing access for regular smartphones and critical services. EAB thus solves the problem of signaling overload from massive MTC deployments, ensuring network reliability and service availability for all users.

Key Features

• Broadcast-based barring information transmitted in SIB14 (LTE) and SIB14/SIB15 (NR)
• Configurable barring for specific UE categories based on subscription (e.g., MTC devices)
• UE-autonomous enforcement after reading system information
• Exemption for emergency sessions and high-priority access classes
• Parameters include barring factor (probability) and barring time duration
• Support in both EPS (LTE) and 5GS (NR) architectures

Evolution Across Releases

Defining Specifications