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

Glossary term · Identifier

CB-RNTI

Contention Based RNTI

Identifier →

CB-RNTI is a temporary identifier used in 3GPP networks for contention-based access, allowing multiple user devices to share uplink resources to simplify random access and reduce latency.

Introduced
Rel-19
Where
Radio Access Network › E-UTRAN (LTE)
Specifications
2 specs
CB-RNTI Description Purpose What changed Neighbours Specifications

Description

Contention Based RNTI (CB-RNTI) is a Rel-19 identifier introduced in 3GPP TS 36.300 and TS 36.321 for LTE and potentially adapted for 5G. It is used in the context of contention-based access, where multiple user equipments (UEs) may transmit on shared uplink resources without a dedicated grant. The CB-RNTI is a 16-bit value that scrambles the PDCCH (Physical Downlink Control Channel) and is used to identify a group of UEs that are allowed to contend for uplink resources. This is particularly relevant for machine-type communication (MTC) and small data transmissions, where the overhead of a full random access procedure (RACH) and scheduling request (SR) is prohibitive.

In operation, the network (eNB or gNB) allocates a set of uplink resources and signals the CB-RNTI to UEs via system information or dedicated signaling. When a UE has small data to send, it can directly transmit on the contention-based resources using the CB-RNTI for scrambling. If a collision occurs (multiple UEs transmit simultaneously), the network may not be able to decode any transmission, and UEs must retry after a backoff. To mitigate collisions, the network can assign multiple CB-RNTIs or use different time/frequency resources. The CB-RNTI is distinct from other RNTIs such as C-RNTI (Cell RNTI), RA-RNTI (Random Access RNTI), and TC-RNTI (Temporary C-RNTI).

Architecturally, CB-RNTI is part of the MAC layer procedures. It is configured by RRC and used by the MAC entity for contention-based uplink transmission. The UE must monitor the PDCCH for downlink control information (DCI) scrambled with CB-RNTI to know when and where to transmit. The DCI format may indicate the modulation and coding scheme (MCS), resource blocks, and HARQ information. The CB-RNTI can also be used for contention-based downlink transmissions, where the network sends data to a group of UEs and each UE determines if the data is intended for it based on higher-layer identifiers.

Key components include: (1) CB-RNTI allocation and configuration via RRC; (2) MAC procedures for contention-based transmission, including resource selection and collision resolution; (3) HARQ operation for contention-based transmissions, which may use asynchronous or synchronous HARQ; and (4) interaction with the random access procedure, as CB-RNTI can be used after initial access. The CB-RNTI is particularly beneficial for IoT devices that transmit infrequently and have low data volumes, as it reduces signaling overhead and power consumption.

In the network, CB-RNTI impacts the RAN and core network by enabling more efficient small data transmission. It can be combined with features like early data transmission (EDT) and preconfigured uplink resources (PUR) to further optimize. The 3GPP Rel-19 work on CB-RNTI likely extends these concepts to 5G NR, where contention-based access is being studied for reduced capability (RedCap) devices and massive IoT. CB-RNTI matters because it addresses the need for low-latency, low-overhead uplink access for a massive number of devices, which is a key requirement for 5G-Advanced and 6G.

Purpose & Motivation

CB-RNTI was created to enable efficient contention-based access for small data transmissions, reducing the signaling overhead and latency associated with traditional grant-based scheduling. In cellular networks, every uplink transmission typically requires a scheduling request (SR) and a grant from the base station, which involves multiple control messages. For IoT devices that send small, infrequent packets, this overhead is disproportionate and consumes significant energy and resources. CB-RNTI allows multiple UEs to share uplink resources without individual grants, simplifying the procedure.

Historically, contention-based access has been used in random access (RACH) for initial access, but not for general data transmission. With the rise of MTC and IoT, 3GPP studied ways to optimize small data transmission, leading to features like EDT in LTE Rel-13 and PUR in Rel-16. CB-RNTI in Rel-19 extends these ideas by providing a dedicated identifier for contention-based data transmission, enabling the network to manage collisions and HARQ more effectively.

The motivation is to support massive connectivity with low latency and high energy efficiency. CB-RNTI is a key enabler for 5G-Advanced use cases such as industrial IoT, wearables, and smart meters, where devices need to transmit small amounts of data sporadically. By reducing the control signaling, CB-RNTI helps extend battery life and improve network capacity.

What changed in its specifications

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

TS 36.300Rel-18 → Rel-19

Rel-19 added NTN IoT Phase 3 for LTE, covering regenerative payload S1 removal, Msg3 early data transmission, and ETWS/CMAS for NB-IoT NTN. It also added inter-RAT mobility from E-UTRAN terrestrial network to NR NTN, plus NR NTN feeder link switchover via handover.

Full comparison in TS 36.300 →
TS 36.321Rel-18 → Rel-19

Rel-19 adds to TS 36.321 a contention-based Msg3 early data transmission (CB-Msg3-EDT) procedure, along with new definitions and abbreviations. This is the only feature overview provided, so no other additions can be named.

Full comparison in TS 36.321 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-19 Initial

Initial introduction of Contention Based RNTI (CB-RNTI) in 3GPP specifications TS 36.300 and TS 36.321. This release defines the CB-RNTI for LTE and potentially 5G NR, enabling contention-based access for small data transmissions. The specifications outline the MAC procedures, RRC configuration, and HARQ operation for CB-RNTI.

Defining Specifications

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

SpecificationTitleRelease
TS 36.300 vj20 E-UTRAN Radio Interface Protocol Architecture Rel-19 read
TS 36.321 vj30 E-UTRA MAC Protocol Specification Rel-19 read