NTZ

No-Transmit Zone

Radio Access Network →
Introduced in Rel-19 Also in: Core Network

NTZ is a geographical area or set of resources where a wireless device is prohibited from transmitting to prevent interference with other systems, such as incumbent users in shared spectrum.

Category
Radio Access Network
Introduced
Rel-19
Where
Services › IMS
Also touches
1 segments
Specifications
8 specs
NTZ Description Purpose Detected Changes Specifications

Description

A No-Transmit Zone (NTZ) is a regulatory and technical concept in 3GPP, particularly relevant for spectrum sharing and radio resource management. It defines a specific geographic region, or in some contexts a set of time-frequency resources, within which a User Equipment (UE) or a base station (gNB/eNB) is not allowed to transmit radio signals. The primary mechanism for enforcing an NTZ is through network-controlled policies delivered to the UE. The network, typically via the Access and Mobility Management Function (AMF) or the Policy Control Function (PCF), can provision the UE with NTZ configuration information, which includes geographic coordinates (e.g., a polygon or circle) and associated conditions.

Architecturally, NTZ management involves several core network functions. The Network Data Analytics Function (NWDAF) or other network exposure functions may determine the need for an NTZ based on external inputs, such as a spectrum access system (SAS) or regulatory database indicating protected incumbent users (e.g., fixed satellite service earth stations). This information is conveyed to the Policy Control Function, which formulates appropriate policies. These policies are then sent to the UE via the Access and Mobility Management Function as part of the UE configuration update procedure or initial registration. The UE's protocol stack, specifically the Radio Resource Control (RRC) layer, interprets these policies and enforces them by prohibiting transmissions when the UE's location (determined via its own GNSS or network-based positioning) falls within the defined NTZ.

The role of NTZ is critical in dynamic spectrum sharing scenarios, such as Citizens Broadband Radio Service (CBRS) or other shared/licensed-shared access regimes. It protects higher-priority incumbent users from harmful interference from mobile network transmissions. When a UE enters an NTZ, it must cease transmissions on the affected frequencies, potentially triggering a handover to another frequency or cell outside the zone. NTZ configurations can be dynamic, changing based on time of day or incumbent activity. This requires continuous UE positioning and policy enforcement. The specifications detail the signaling (e.g., in NAS messages) and parameters (like geographic area description, frequency range, and validity timer) needed to define and manage NTZs effectively across the network.

Purpose & Motivation

The NTZ concept was created to enable coexistence between mobile networks and other radio systems sharing the same frequency band, a problem that became acute with the introduction of dynamic spectrum sharing. Traditional static frequency allocation was insufficient for flexible, efficient spectrum use. Without NTZs, mobile transmissions could cause harmful interference to sensitive incumbent services, such as satellite communications or radar systems, leading to regulatory violations and service degradation for those incumbents.

The historical context includes the opening of shared spectrum bands like the 3.5 GHz CBRS band in the USA and similar bands globally. Regulators required mechanisms to protect incumbent users. 3GPP developed the NTZ framework to provide a standardized, network-controlled method for geographic exclusion of transmissions. This addresses the limitations of previous, more simplistic approaches like static exclusion zones or purely sensing-based solutions, which lacked the precision and policy control offered by integrated NTZ management. It allows mobile network operators to dynamically respect protection zones defined by a central spectrum controller, enabling more efficient and compliant use of shared spectrum resources. The creation of NTZ policies within the 5G core network architecture allows for scalable, automated enforcement essential for large-scale deployments.

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-18 1 change

In Release 18, the NTZ function was enhanced by clarifying the conditions for transmitting a "UAS services not allowed indication" to the UE, mirroring this clarification from a previous release. The specifications detail procedures for NTZ management, configuration, and activation, including mechanisms for the UAE Server to provision NTZ policies and for the UAE Client to report NTZ status changes like "NTZ imminent entry" and "NTZ exit" based on its location relative to the no-transmit zone.

  • Clarification on the condition of transmitting “UAS services not allowed indication” to the UE, mirror in Rel-18 TS 24.301CR3795
Rel-19 22 changes

In Release 19, the NTZ (No-Transmit Zone) function introduced new UAE-layer procedures for configuration, activation, and management, including a specific mechanism for a UAV to obtain a new USS NTZ policy after changing service suppliers. The release also defined UAE-layer/SEAL/LMS assisted NTZ enforcement, leveraging existing location monitoring for activation support, and extended NTZ restrictions to both 5GS and EPS. These enhancements established a complete framework for UAS application enablement services to manage and enforce no-transmit zones.

  • No-transmit zones configuration and execution for UAS TS 23.255CR0059
  • Support of No-Transmit Zones TS 23.256CR0136
  • Update general procedure for NTZ support over UAE layer TS 24.257CR0049
  • NTZ configuration procedure for NTZ support over UAE layer TS 24.257CR0050
  • NTZ activation procedure for NTZ support over UAE layer TS 24.257CR0051
  • New USS NTZ policy TS 24.257CR0053

+ 16 more changes

Explore further

Broader topics and technologies where NTZ plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 23.255 vj50 UAS Application Layer Support Rel-19
TS 23.256 vj50 UAS Support Architecture Enhancements Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.257 vj40 UAS Application Enabler (UAE) Layer Rel-19
TS 24.301 vj60 NAS protocol for Evolved Packet System Rel-19
TS 24.501 vj50 5G NAS Protocols Specification Rel-19
TS 29.257 vj40 Application layer support for Uncrewed Aerial System (UAS) Rel-19
TS 33.759 vj00 UAS Security Enhancements Phase 3 Study Rel-19