Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Radio Access Network

Acceptable Cell

Acceptable Cell

Radio Access Network →

Acceptable Cell is a cell that meets minimum conditions for limited service, allowing emergency calls and limited data as a fallback when no suitable cell is available.

Introduced
Rel-4
Where
User Equipment
Specifications
6 specs
Also in
Radio Access Network
Acceptable Cell Description Purpose What changed Neighbours Detected Changes Specifications

Description

An Acceptable Cell is a concept in 3GPP specifications that defines a cell on which a User Equipment (UE) can camp to obtain limited service when no Suitable Cell is available. The conditions for a cell to be considered acceptable are specified in the relevant technical specifications (e.g., TS 25.304 for UTRAN, TS 36.304 for E-UTRAN, TS 38.304 for NR). These conditions typically include: the cell is not barred, the cell is not reserved for operator use, and the UE is not prohibited from accessing the cell based on its access class or other restrictions. The cell must also meet certain signal quality thresholds, though these are less stringent than those for a suitable cell.

The primary purpose of an acceptable cell is to enable the UE to attempt emergency calls and, in some cases, receive limited services such as Earthquake and Tsunami Warning System (ETWS) or Commercial Mobile Alert System (CMAS) notifications. The UE can camp on an acceptable cell only when it cannot find a suitable cell, which would provide normal service. This ensures that the UE can still make emergency calls even in areas where only restricted cells are available, such as during network congestion, partial network outages, or when the UE is in a limited service state.

The process of cell selection and reselection involves the UE scanning for cells and evaluating them against the criteria for suitable and acceptable cells. The UE first attempts to find a suitable cell; if none is found, it may camp on an acceptable cell. The specific conditions for an acceptable cell are defined in the specifications and include checks on the cell's barring status, the UE's access class, and the cell's signal strength and quality. For example, in E-UTRAN, a cell is considered acceptable if it is not barred, not reserved, and the UE is not in a forbidden tracking area, and the cell selection criteria (S-criteria) are met.

In NB-IoT (Narrowband IoT), the definition of an acceptable cell was updated in Release 19 to exclude NB-IoT from the statement that the UE can always attempt emergency calls on an acceptable cell. This reflects the fact that NB-IoT is not designed for emergency calls, and thus the UE may not be able to make emergency calls on an acceptable NB-IoT cell. This change aligns with the specific characteristics of NB-IoT, which is optimized for low-power, low-data-rate applications and may not support voice services.

The concept of an acceptable cell is crucial for maintaining basic connectivity in adverse conditions. It allows the UE to stay connected to the network for emergency services and receive critical alerts, even when normal service is not available. This enhances the overall robustness and reliability of the network, ensuring that users can always reach emergency services when needed. The evolution of the definition over releases has been minimal, with the main change being the exclusion of NB-IoT from emergency call support in Release 19.

Purpose & Motivation

The Acceptable Cell concept exists to ensure that User Equipment (UE) can obtain limited service, particularly emergency calls, when no Suitable Cell is available. This is critical in scenarios such as network congestion, partial network failures, or when the UE is in a location with only restricted cells. Without this concept, a UE might be unable to make emergency calls in such situations, which could have life-threatening consequences.

Historically, as cellular networks evolved, the need for a fallback mechanism became apparent. Early networks might not have had such a concept, but with the introduction of more complex cell selection criteria and the need to support emergency services universally, the Acceptable Cell was defined. It addresses the limitation that a UE might not always find a cell that provides full service, but it should still be able to access emergency services.

The concept also supports regulatory requirements for emergency call support. Many countries mandate that emergency calls must be possible even without a SIM card or when the UE is in a limited service state. The Acceptable Cell ensures that the UE can camp on a cell that allows emergency calls, thus complying with these regulations. Over time, the definition has been refined to exclude technologies like NB-IoT that do not support emergency calls, ensuring that the concept remains relevant and accurate.

What changed in its specifications

The latest release-to-release comparison of specifications that define Acceptable Cell. Each summary describes the whole specification, not only this term.

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 25.304Rel-18 → Rel-19

Rel-19 adds Non-Terrestrial Networks (NTN) for IoT Phase 3 for LTE to 3GPP TS 25.304. It also adds a list of PLMNs with associated access technology restrictions to idle-mode cell selection and reselection.

Full comparison in TS 25.304 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (1 CRs across 1 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-19 1 change
  • oT-NTN correction for acceptable cell camping TS 36.304CR0894

Defining Specifications

3GPP specifications that define or reference Acceptable Cell, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 25.304 vj10 UE Idle Mode Procedures Rel-19 read
TS 25.367 vj00 Home NodeB Mobility Procedures Rel-19 read
TS 36.304 vj30 LTE UE Idle Mode Procedures Rel-19 read
TS 38.304 vj30 NR UE Idle and Inactive State Procedures Rel-19 read
TS 45.008 vj00 GSM Radio Link Control Specification Rel-19 read