RLM with relaxed measurement criteria. Draft CRs on CSI-RS-based relaxed RLM and SSB-based RLM for UEs fulfilling relaxed measurement criteria were endorsed, not agreed. A further draft CR addresses RLM for (e)RedCap UEs configured with those criteria.
Should LT5 (e)RedCap reuse legacy 1Rx requirements for RLM and BFD?
China Mobile and vivo each proposed reusing the legacy 1Rx TEvaluate_out_SSB,RedCap requirement. CATT observed that less than 5 MHz does not affect minimum or relaxed RedCap RLM and BFD requirements.
China MobileProposes reusing the legacy 1Rx TEvaluate_out_SSB,RedCap requirement for LT5.
Proposal 1: it is proposed to reuse the legacy 1Rx (e)RedCap TEvaluate_out_SSB,RedCap requirement for 1Rx (e)RedCap UE supporting LT5.
vivoAlso supports reusing the legacy 1Rx TEvaluate_out_SSB,RedCap requirement for LT5.
For RLM/BFD TEvaluate_out_SSB,RedCap of 1Rx (e)RedCap UE supporting LT5, support to reuse the legacy 1Rx (e)RedCap TEvaluate_out_SSB,RedCap requirement for 1Rx (e)RedCap UE supporting LT5.
SamsungProposes analyzing whether legacy FR2-NTN UE requirements can be reused.
RAN4 to analyze whether the legacy requirements for UE in FR2-NTN can be reused for HD-FDD VSAT UE in FR2-NTN: Cell reselection, including paging reception [...]
R4-2610627 Draft CR 38.133 Minimum RLM / BFD core requirements for LT5 (e)RedCap UE. Nokia. Draft CR. Register status: endorsed at R4-120.
R4-2610863 Draft CR on requirements of CSI-RS based relaxed RLM for (e)RedCap UE. OPPO. Draft CR. Register status: endorsed at R4-120.
R4-2611164 Draft CR on minimum requirement of SSB based radio link monitoring for UE fulfilling relaxed measurement criteria. CATT. Draft CR. Register status: endorsed at R4-120.
R4-2612459 Draft CR on (e)RedCap Intra-frequency measurements without measurement gaps for for Rel-20. Huawei (with HiSilicon). Draft CR. Register status: endorsed at R4-120.
R4-2612460 Draft CR on (e)RedCap Inter-frequency measurements without measurement gaps for for Rel-20. Huawei (with HiSilicon). Draft CR. Register status: endorsed at R4-120.
R4-2611719 Correction of Draft Big CR on support less than 5 MHz channel bandwidth for (e)RedCap UEs. Ericsson. Draft CR. Register status: endorsed at R4-120.
R4-2611720 CR on Release Independent support for Rel-20 (e)RedCap UEs Less than 5 MHz and RLM-BFD relaxation. Ericsson (with Anterix). CR. Register status: endorsed at R4-120.
R4-2611566 Introduction of Requirement on Radio Link Monitoring for (e)RedCap UE Configured with Relaxed Measurement Criteria. ZTE (with Sanechips). Draft CR. Register status: endorsed at R4-120.
R4-2610787 Discussion on RRM core requirements for (e)RedCap UE enhancement. China Mobile. Contribution. Register status: noted at R4-120.
R4-2611364 Remaining RRM issues for (e)RedCap UE enhancement. vivo. Contribution. Register status: noted at R4-120.
R4-2611163 Discussion on RRM core requirements of (e)RedCap UE enhancement. CATT. Contribution. Register status: noted at R4-120.
R4-2611648 Discussion on RRM impact of HD-FDD VSAT in FR2-NTN. Huawei (with HiSilicon). Contribution. Register status: noted at R4-120.
R4-2610909 Discussion on RRM requirements to support HD-FDD VSATs in both Ka and Ku bands with FR2 numerologies. Ericsson. Contribution. Register status: noted at R4-120.
R4-2610343 Discussion on HD-FDD for Ku band and Ka band with FR2 numerology. Samsung. Contribution. Register status: noted at R4-120.
R4-2611757 Discussion on RRM requirements for HD-FDD VSAT with FR2 numerology. ZTE (with Sanechips). Contribution. Register status: noted at R4-120.
R4-2611527 Discussion on RRM requirements for timing and frequency in initial access and connected mode. vivo. Contribution. Register status: noted at R4-120.
Coverage: RAN4 #120 (Maastricht, 2026-08-24 to 2026-08-28), agenda items 4.2.1.4, 7.14.4, 7.15.3, 7.4.3.2, 7.6.4.2, 7.6.6.2. Scout read 8 recorded decisions and 12 company positions or contribution passages on these agenda items (catalog synced 2026-09-29) and cites 8 decisions and 8 positions from 16 TDocs. Every quoted passage was matched verbatim against the TDoc text; the summaries around the quotes are Scout's reading. Register statuses are copied from the 3GPP TDoc register: not treated means a document was not handled on its own, though its content may have fed feature-lead summaries or merged revisions. Not covered: other agenda items and meetings, plenary TDocs and plenary decisions after the meeting, email discussions after the meeting, and anything not yet in the chair notes or register.
The pack has no evidence on the 6G UE group for RRM.
UE RF requirements are represented only by a single-company timing and frequency contribution, with no recorded decision in the pack.
No FFS item or working assumption is supplied for these topics.
Hottest topics
RRM core requirementssignificance 70 of 100, 110 TDocs
UE RF requirementssignificance 65 of 100, 60 TDocs
6G UE group for RRMsignificance 53 of 100, 18 TDocs
Moderator summary and conclusionssignificance 52 of 100, 76 TDocs
Introduce support of the higher power classes for the NTN NR bandssignificance 52 of 100, 26 TDocs
Built by 3GPP Scout from the public meeting record (2930 TDocs registered, catalog synced 2026-09-29). Significance scores rank topics by decisions, contention, breadth and volume. Excerpts are at most 25 words and link to the original on the 3GPP file server.