Description
Time to Next Burst (TTNB) is a critical timing parameter within the Medium Access Control (MAC) layer of an Integrated Access and Backhaul (IAB) node operating under a shared spectrum regime, such as in 5G NR-Unlicensed (NR-U). Its primary function is to manage channel access in a fair and regulatory-compliant manner alongside other radio access technologies (RATs) like Wi-Fi (IEEE 802.11). The TTNB is determined and signaled as part of the channel access procedure, specifically following a successful Listen-Before-Talk (LBT) check. When an IAB node gains channel access, it is typically granted a Transmission Opportunity (TXOP) – a bounded time window during which it can transmit a burst of data frames. The TTNB is the time interval from the end of the current TXOP (or burst) to the expected start time of the node's next transmission burst.
Architecturally, the TTNB is calculated and utilized by the IAB node's distributed unit (IAB-DU). The process works as follows: Before transmitting, the IAB-DU performs an LBT procedure (e.g., Category 4 LBT, similar to Wi-Fi's CSMA/CA) to ensure the channel is idle. Upon successful access, it transmits its data burst. The determination of the TTNB can be based on several factors, including the node's own traffic backlog, quality of service (QoS) requirements of its served UEs and child IAB nodes, and potentially centralized scheduling hints from the IAB donor. This TTNB value may be implicitly derived from the node's scheduling algorithm or explicitly signaled to other entities. In some coordination schemes, an IAB node might announce its TTNB to neighboring nodes (via direct signaling or through the donor) to facilitate spatial reuse and minimize hidden node problems.
The key components involved are the IAB-DU's MAC scheduler and LBT entity. The TTNB directly influences the channel access pattern and latency for the traffic flowing through the IAB node. A short TTNB indicates the node intends to access the channel again soon, which is suitable for latency-sensitive or high-priority traffic. A long TTNB frees up the channel for other nodes or RATs, promoting fairness. The parameter is crucial for achieving the dual objectives of efficient NR-U operation: maximizing NR system throughput while ensuring fair coexistence with incumbent systems as required by regulations (e.g., ETSI EN 301 893 for 5 GHz band).
Purpose & Motivation
TTNB was introduced to solve the specific challenges of deploying 5G NR in unlicensed or shared spectrum bands, particularly within the IAB context. Traditional licensed spectrum operation uses tightly synchronized, scheduled access controlled solely by the gNB, which does not require mechanisms like TTNB. However, unlicensed spectrum mandates contention-based access (e.g., LBT) to ensure fair coexistence with other technologies like Wi-Fi. The problem is that without coordination, multiple IAB nodes belonging to the same network could contend against each other as well as against Wi-Fi, leading to inefficient channel use and increased collisions.
The creation of TTNB is motivated by the need to bring a degree of predictability and coordination to the inherently random LBT-based channel access within a managed IAB network. It addresses the limitation of purely distributed, independent LBT, which can lead to suboptimal performance for the NR system as a whole. By having a notion of 'time to next burst,' an IAB node can plan its channel access attempts, and this information can be used by parent or donor nodes to perform intelligent resource allocation and interference management across the IAB topology. This is especially important for backhaul links, which carry aggregated traffic and have stricter latency and reliability requirements than typical access links.
Historically, this concept builds upon coexistence mechanisms developed for LTE-Licensed Assisted Access (LAA) in Rel-13/14, which introduced LBT and TXOP. TTNB in Rel-19 IAB for NR-U extends these ideas into a multi-hop, mesh network context. It solves the additional complexity of ensuring that channel access on a backhaul link does not starve the access link of the same node or cause excessive latency for hops deep within the IAB network. Thus, TTNB is a key enabler for efficient, high-performance, and fair wireless self-backhauling in shared spectrum, which is vital for rapid and cost-effective network densification.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (8 CRs across 2 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 18, the Time to Next Burst (TTNB) function was introduced as a new capability for the downlink service data flow, indicated by a dedicated boolean parameter. This allows the network to explicitly signal support for detecting the TTNB indication as part of the downlink protocol description. Furthermore, TTNB handling was included within the broader feature for dynamically changing traffic characteristics.
In Release 19, the Time to Next Burst (TTNB) function was enhanced by introducing explicit support indications for both the detection of the TTNB indication and the Data Burst Size marking indication within the downlink protocol description. This allows the network to signal its capability to handle these dynamic traffic characteristics, specifically for a downlink service data flow, via new boolean parameters like `timetoNextBurstInd`. These enhancements are part of the broader feature supporting dynamically changing traffic characteristics.
- Introduce data burst size marking support indication TS 29.122CR0888
- Time to Next Burst Support Indication TS 29.122CR0899
- Support of all possible data burst sizes TS 29.122CR0987
- Support of data burst size marking indication handling TS 29.514CR0700
- Time to Next Burst Support Indication TS 29.514CR0710
- Support of all possible data burst sizes TS 29.514CR0812
Explore further
Broader topics and technologies where TTNB plays a role.
Defining Specifications
3GPP specifications that define or reference TTNB, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 29.122 vj40 | T8 Reference Point for Northbound APIs | Rel-19 |
| TS 29.514 vj40 | 5G System; Policy Authorization Service; Stage 3 | Rel-19 |
| TS 38.415 vj10 | PDU Session User Plane Protocol | Rel-19 |
| TS 38.425 vj10 | NR User Plane Protocol Specification | Rel-19 |