3GPP Scout / Meetings / RAN4 #120
RAN4 #120Final
At a glance
LB-CA work included endorsement of the 38.133 big CR, an L1-SINR draft CR, and a PCell PL-RS switch-delay draft CR.
Sources: R4-2612502, Samsung (Contribution. Register status: endorsed at R4-120.); R4-2612500, ZTE (Draft CR. Register status: endorsed at R4-120.); R4-2612501, CATT (Draft CR. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © Samsung, ZTE, CATT.
Draft CRs on LT5 (e)RedCap minimum RLM/BFD and relaxed RLM requirements were endorsed.
Sources: R4-2610627, Nokia (Draft CR. Register status: endorsed at R4-120.); R4-2610863, OPPO (Draft CR. Register status: endorsed at R4-120.); R4-2611164, CATT (Draft CR. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © Nokia, OPPO, CATT.
pCR text on UAV background and Rel-20 UAV bands was approved for TR 38.767 as non-normative text.
Sources: R4-2610755, China Mobile (pCR. Register status: approved at R4-120.); R4-2612665, ZTE (pCR. Register status: approved at R4-120.). 3GPP TSG RAN WG4 #120. © China Mobile, ZTE.
Your topic
Follow a topic and get its next outcome by email.
Scout emails you when a new agreement or decision on it is recorded, with the source for each. Or ask Scout and get an answer that cites the exact TDoc. Free to start.
Another topic or company? Follow it
| Agenda item | Topic | TDocs | Agreed here | Still open |
|---|---|---|---|---|
| 7.8.4 | RRM core requirements | 31 | 3 | 1 |
| 7.7.4 | UE RF requirements | n/a | 1 | 0 |
| 7.12.1 | Moderator summary and conclusions | n/a | 1 | 0 |
| 7.4.3.2 | RRM core requirements | 25 | 1 | 1 |
| 5.8.2 | UE RF requirements | n/a | 0 | 0 |
| 7.17.1 | Moderator summary and conclusions | n/a | 0 | 0 |
7.8.4RRM core requirements
Draft CRs on RLM requirements, SCell activation and deactivation, and L3 measurement for LB-CA via switching were endorsed.
Sources: R4-2611390, vivo (Draft CR. Register status: endorsed at R4-120.); R4-2612493, Nokia (Draft CR. Register status: endorsed at R4-120.); R4-2612494, MediaTek (Draft CR. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © vivo, Nokia, MediaTek.
Draft CRs on L1-RSRP for SDL SCell and PCell, TCI state switch delay, and BFD/CBD were endorsed.
Sources: R4-2612496, OPPO (Draft CR. Register status: endorsed at R4-120.); R4-2612497, LG Electronics (Draft CR. Register status: endorsed at R4-120.); R4-2612498, Huawei (Draft CR. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © OPPO, LG Electronics, Huawei.
Draft CRs on L1-SINR measurement and PCell PL-RS switch delay, plus the 38.133 RRM big CR, were endorsed.
Sources: R4-2612500, ZTE (Draft CR. Register status: endorsed at R4-120.); R4-2612501, CATT (Draft CR. Register status: endorsed at R4-120.); R4-2612502, Samsung (Contribution. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © ZTE, CATT, Samsung.
7.4.3.2RRM core requirements
Draft CRs covering LT5 (e)RedCap minimum RLM/BFD and relaxed RLM requirements were endorsed.
Sources: R4-2610627, Nokia (Draft CR. Register status: endorsed at R4-120.); R4-2610863, OPPO (Draft CR. Register status: endorsed at R4-120.); R4-2611164, CATT (Draft CR. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © Nokia, OPPO, CATT.
7.7.4UE RF requirements
The approved change adds background to the UAV study.
Sources: R4-2610755, China Mobile (pCR. Register status: approved at R4-120.); R4-2612665, ZTE (pCR. Register status: approved at R4-120.). 3GPP TSG RAN WG4 #120. © China Mobile, ZTE.
7.12.1Moderator summary and conclusions
The approved minutes cover RRM work for NR AI/ML mobility.
Sources: R4-2612436, OPPO (Contribution. Register status: approved at R4-120.); R4-2612437, OPPO (Way forward. Register status: approved at R4-120.); R4-2612440, Huawei (Way forward. Register status: approved at R4-120.). 3GPP TSG RAN WG4 #120. © OPPO, Huawei.
7.4.3.2RRM core requirements
China Mobile and vivo support reusing the legacy 1Rx TEvaluate_out_SSB,RedCap requirement. CATT says less than 5 MHz does not affect minimum RLM/BFD requirements, including relaxed requirements.
| Company | What they propose | Source |
|---|---|---|
| China Mobile | Proposes reusing the legacy 1Rx TEvaluate_out_SSB,RedCap requirement for LT5.Their wordsProposal 1: it is proposed to reuse the legacy 1Rx (e)RedCap TEvaluate_out_SSB,RedCap requirement for 1Rx (e)RedCap UE supporting LT5. | R4-2610787Proposal 1, paragraph 18 · register: noted |
| CATT | Says less than 5 MHz does not affect minimum or relaxed RLM/BFD requirements.Their wordsLess than 5MHz will do not have an impact on the minimum requirement for RLM and BFD for RedCap UE, and the principle apply for [...] | R4-2611163Observation 1, paragraph 17 · register: noted |
| vivo | Supports reusing the legacy 1Rx TEvaluate_out_SSB,RedCap requirement for RLM/BFD.Their wordsFor 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. | R4-2611364Proposal 1, paragraph 40 · register: noted |
7.7.4UE RF requirements
ZTE and Sanechips oppose distinguishing omni-directional antennas from antenna arrays for RF requirements. CATT's position concerns minimum output power and maximum input level under a 13º up-tilt assumption.
| Company | What they propose | Source |
|---|---|---|
| ZTE (with Sanechips) | Opposes distinguishing omni-directional antennas from antenna arrays for RF requirements.Their wordsThere is no need to distinguish RF requirements for omni-directional antenna and antenna array. | R4-2611509Proposal 1, paragraph 15 · register: noted |
| CATT | Limits its point to minimum output power and maximum input level under a 13º up-tilt assumption.Their wordsAs the minimum 2D coverage for UAV is much larger than NR under the assumption of up tilt 13º, current NR minimum output power and [...] | R4-2610299Proposal 1, paragraph 19 · register: noted |
China Mobile proposes reusing the legacy UE power-class definition for UAV output power. CATT separately cites current NR minimum output power and maximum input level requirements under a 13º up-tilt assumption.
| Company | What they propose | Source |
|---|---|---|
| China Mobile | Proposes reusing the legacy UE power-class definition for UAV output power.Their wordsProposal 1: Reuse the legacy UE power class definition to specify UAV UEs output power. | R4-2610754Proposal 1, paragraph 12 · register: noted |
| CATT | Says current NR minimum output power and maximum input level requirements cover both antenna types under its stated assumption. | R4-2610299Proposal 1, paragraph 19 · register: noted |
Company contributions to 3GPP TSG RAN WG4 #120. Each TDoc is © the company named in its row. These are proposals, not decisions.
Still open
The LB-CA 38.133 big CR is recorded as endorsed, not as an agreed or approved CR.
Source: R4-2612502, Samsung (Contribution. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © Samsung.
The LT5 (e)RedCap RLM draft CRs are recorded as endorsed, not as agreed or approved CRs.
Sources: R4-2610627, Nokia (Draft CR. Register status: endorsed at R4-120.); R4-2610863, OPPO (Draft CR. Register status: endorsed at R4-120.); R4-2611164, CATT (Draft CR. Register status: endorsed at R4-120.). 3GPP TSG RAN WG4 #120. © Nokia, OPPO, CATT.
Whether LT5 will reuse the legacy 1Rx TEvaluate_out_SSB,RedCap requirement remains a point to track.
Sources: R4-2610787, China Mobile (Proposal 1, paragraph 18); R4-2611364, vivo (Proposal 1, paragraph 40). 3GPP TSG RAN WG4 #120. © China Mobile, vivo.
Whether UAV RF requirements distinguish antenna types remains unresolved across the submitted positions.
Sources: R4-2611509, ZTE with Sanechips (Proposal 1, paragraph 15); R4-2610299, CATT (Proposal 1, paragraph 19). 3GPP TSG RAN WG4 #120. © ZTE, Sanechips, CATT.
Whether UAV output power will use the legacy UE power-class definition remains a proposal to track.
Source: R4-2610754, China Mobile (Proposal 1, paragraph 12). 3GPP TSG RAN WG4 #120. © China Mobile.
Coverage: RAN4 #120 (Maastricht, 2026-08-24 to 2026-08-28), agenda items 7.8.4, 7.7.4, 7.12.1, 7.4.3.2, 5.8.2, 7.17.1.
Scout read 27 recorded decisions and 6 company positions or contribution passages on these agenda items (catalog synced 2026-10-19) and cites 17 decisions and 6 positions from 23 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 supplied decision items identify approved way-forwards by title but do not include their technical content.
The supplied decision items do not record an outcome on the LT5 evaluation-period or UAV antenna-type proposals.
Next outcome
Get the RAN4 #120-bis outcome by email.
Scout emails you when RAN4 records a new agreement or decision, with the source for each. Free to start.
Built by 3GPP Scout from the public meeting record (2930 TDocs registered, catalog synced 2026-10-19). Significance scores compare each topic's activity at this meeting with the group's topics over the past 12 months. Excerpts are at most 25 words and link to the original on the 3GPP file server.