5G; NR; User Equipment (UE) radio access capabilities (3GPP TS 38.306 version 16.23.0 Release 16)

RTS/TSGR-0238306vgn0

General Information

Status
Not Published
Current Stage
12 - Citation in the OJ (auto-insert)
Completion Date
09-Apr-2026

Buy Documents

Standard

ETSI TS 138 306 V16.23.0 (2026-04) - 5G; NR; User Equipment (UE) radio access capabilities (3GPP TS 38.306 version 16.23.0 Release 16)

English language (164 pages)
sale 15% off
Preview
sale 15% off
Preview

Frequently Asked Questions

ETSI TS 138 306 V16.23.0 (2026-04) is a standard published by the European Telecommunications Standards Institute (ETSI). Its full title is "5G; NR; User Equipment (UE) radio access capabilities (3GPP TS 38.306 version 16.23.0 Release 16)". This standard covers: RTS/TSGR-0238306vgn0

RTS/TSGR-0238306vgn0

ETSI TS 138 306 V16.23.0 (2026-04) is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


TECHNICAL SPECIFICATION
5G;
NR;
User Equipment (UE) radio access capabilities
(3GPP TS 38.306 version 16.23.0 Release 16)

3GPP TS 38.306 version 16.23.0 Release 16 1 ETSI TS 138 306 V16.23.0 (2026-04)

Reference
RTS/TSGR-0238306vgn0
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 2 ETSI TS 138 306 V16.23.0 (2026-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 3 ETSI TS 138 306 V16.23.0 (2026-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 UE radio access capability parameters . 8
4.1 Supported max data rate . 8
4.1.1 General . 8
4.1.2 Supported max data rate for DL/UL . 8
4.1.3 Void . 9
4.1.4 Total layer 2 buffer size for DL/UL . 9
4.1.5 Supported max data rate for SL . 10
4.1.6 Total layer 2 buffer size for NR SL . 11
4.2 UE Capability Parameters . 11
4.2.1 Introduction. 11
4.2.2 General parameters . 13
4.2.3 SDAP Parameters . 15
4.2.4 PDCP Parameters . 16
4.2.5 RLC parameters . 18
4.2.6 MAC parameters . 19
4.2.7 Physical layer parameters . 23
4.2.7.1 BandCombinationList parameters . 23
4.2.7.2 BandNR parameters . 29
4.2.7.2a SharedSpectrumChAccessParamsPerBand . 51
4.2.7.3 CA-ParametersEUTRA . 56
4.2.7.4 CA-ParametersNR . 57
4.2.7.5 FeatureSetDownlink parameters . 69
4.2.7.6 FeatureSetDownlinkPerCC parameters . 75
4.2.7.7 FeatureSetUplink parameters . 78
4.2.7.8 FeatureSetUplinkPerCC parameters . 88
4.2.7.9 MRDC-Parameters . 91
4.2.7.10 Phy-Parameters . 95
4.2.7.11 Other PHY parameters . 109
4.2.7.12 NRDC-Parameters . 112
4.2.7.13 CarrierAggregationVariant . 113
4.2.7.14 Phy-ParametersSharedSpectrumChAccess . 114
4.2.8 Void . 116
4.2.9 MeasAndMobParameters . 117
4.2.9a MeasAndMobParametersMRDC . 124
4.2.10 Inter-RAT parameters . 124
4.2.10.1 Void. 125
4.2.10.2 Void. 125
4.2.11 Void . 125
4.2.12 Void . 125
4.2.13 IMS Parameters . 125
4.2.14 RRC buffer size . 125
4.2.15 IAB Parameters . 125
4.2.15.1 Mandatory IAB-MT features . 125
4.2.15.2 General Parameters . 131
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 4 ETSI TS 138 306 V16.23.0 (2026-04)
4.2.15.3 SDAP Parameters . 131
4.2.15.4 PDCP Parameters . 131
4.2.15.5 BAP Parameters . 131
4.2.15.6 MAC Parameters . 131
4.2.15.7 Physical layer parameters . 132
4.2.15.7.1 BandNR parameters . 132
4.2.15.7.2 Phy-Parameters . 132
4.2.15.8 MeasAndMobParameters Parameters . 133
4.2.15.9 MR-DC Parameters . 133
4.2.16 Sidelink Parameters . 133
4.2.16.1 Sidelink Parameters in NR . 133
4.2.16.1.1 Sidelink General Parameters . 133
4.2.16.1.2 Sidelink PDCP Parameters . 133
4.2.16.1.3 Sidelink RLC Parameters . 134
4.2.16.1.4 Sidelink MAC Parameters . 134
4.2.16.1.5 Other PHY parameters . 134
4.2.16.1.6 BandSidelink Parameters . 135
4.2.16.1.7 BandCombinationListSidelinkEUTRA-NR Parameter s . 141
4.2.16.2 Sidelink Parameters in E-UTRA . 142
4.2.16.2.1 BandSideLinkEUTRA parameters . 142
4.2.17 SON parameters . 142
4.2.18 UE-based performance measurement parameters . 143
4.2.19 High speed parameters . 144
5 Optional features without UE radio access capability parameters . 144
5.1 PWS features . 144
5.2 UE receiver features . 145
5.3 RRC connection . 145
5.4 Other features . 145
5.5 Sidelink Features . 145
5.6 RRM measurement features . 145
5.7 MDT and SON features . 146
6 Conditionally mandatory features without UE radio access capability parameters . 146
7 Void . 146
8 UE Capability Constraints . 146
Annex A (normative): Differentiation of capabilities . 148
A.1: TDD/FDD differentiation of capabilities in TDD-FDD CA . 148
A.2: FR1/FR2 differentiation of capabilities in FR1-FR2 CA . 149
A.3: TDD/FDD differentiation of capabilities for sidelink . 150
A.4: Sidelink capabilities applicable to Uu and PC5 . 151
A.5: General differentiation of capabilities in Cross-Carrier operation . 152
Annex B (informative): UE capability indication for UE capabilities with both FDD/TDD and
FR1/FR2 differentiations . 153
Annex C (informative): Change history . 155
History . 163

ETSI
3GPP TS 38.306 version 16.23.0 Release 16 5 ETSI TS 138 306 V16.23.0 (2026-04)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 6 ETSI TS 138 306 V16.23.0 (2026-04)
1 Scope
The present document defines the NR UE Radio Access Capability Parameters.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 38.101-1: "NR; User Equipment (UE) radio transmission and reception Part 1: Range 1
Standalone".
[3] 3GPP TS 38.101-2: "NR; User Equipment (UE) radio transmission and reception Part 2: Range 2
Standalone".
[4] 3GPP TS 38.101-3: "NR; User Equipment (UE) radio transmission and reception Part 3: Range 1
and Range 2 Interworking operation with other radios".
[5] 3GPP TS 38.133: "NR; Requirements for support of radio resource management".
[6] 3GPP TS 38.211: "NR; Physical channels and modulation".
[7] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR Multi-
connectivity".
[8] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[9] 3GPP TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[10] 3GPP TS 38.212: "NR; Multiplexing and channel coding".
[11] 3GPP TS 38.213: "NR; Physical layer procedures for control".
[12] 3GPP TS 38.214: "NR; Physical layer procedures for data".
[13] 3GPP TS 38.215: "NR; Physical layer measurements".
[14] 3GPP TS 36.101: "Evolved Universal Terrestrial Radio Access (E-UTRA) radio transmission and
reception".
[15] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA) User Equipment (UE)
radio access capabilities".
[16] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification".
[17] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource
Control (RRC); Protocol Specification".
[18] 3GPP TS 38.101-4: "NR; User Equipment (UE) radio transmission and reception Part 4:
Performance requirements".
[19] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer
procedures".
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 7 ETSI TS 138 306 V16.23.0 (2026-04)
[20] 3GPP TS 25.306: "UE radio access capabilities".
[21] 3GPP TS 38.304: "User Equipment (UE) procedures in Idle mode and RRC Inactive state".
[22] 3GPP TS 37.355: " LTE Positioning Protocol (LPP)".
[23] 3GPP TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification".
[24] 3GPP TR 38.822: "NR; User Equipment (UE) feature list".
[25] 3GPP TS 37.324: "E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification"
[26] 3GPP TS 38.314: "NR; Layer 2 Measurements".
[27] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for
support of radio resource management".
[28] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage-2".
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Fallback band combination: A Uu band combination that would result from another Uu band combination (parent
band combination) by releasing at least one SCell or uplink configuration of SCell, or SCG, or SUL. A PC5 band
combination that would result from another PC5 band combination (parent band combination) by releasing at least one
sidelink carrier. An intra-band non-contiguous band combination is not considered to be a fallback band combination of
an intra-band contiguous band combination. A fallback band combination supports the same channel bandwidth(s) for
each carrier as its parent band combination(s).
Fallback per band feature set: A feature set per band that has same or lower capabilities than the reported capabilities
from the reported feature set per band for a given band.
Fallback per CC feature set: A feature set per CC that has same or lower capabilities than the capabilities of UE (e.g.
supported MIMO layers, BW, modulation order) while keeping the numerology the same from the reported feature set
per CC for a given carrier per band.
3.2 Symbols
For the purposes of the present document, the following symbols apply:
MaxDLDataRate: Maximum DL data rate
MaxDLDataRate_MN: Maximum DL data rate in the MN
MaxDLDataRate_SN: Maximum DL data rate in the SN
MaxULDataRate: Maximum UL data rate
MaxSLtxDataRate: Maximum SL data rate in transmission
MaxSLrxDataRate: Maximum SL data rate in reception
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
BAP Backhaul Adaptation Protocol
BC Band Combination
BT Bluetooth
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 8 ETSI TS 138 306 V16.23.0 (2026-04)
DAPS Dual Active Protocol Stack
DL Downlink
EHC Ethernet Header Compression
FS Feature Set
FSPC Feature Set Per Component-carrier
IAB-MT Integrated Access Backhaul Mobile Termination
MAC Medium Access Control
MCG Master Cell Group
MN Master Node
MR-DC Multi-Radio Dual Connectivity
PDCP Packet Data Convergence Protocol
RLC Radio Link Control
RTT Round Trip Time
SCG Secondary Cell Group
SDAP Service Data Adaptation Protocol
SDL Supplementary Downlink
SN Secondary Node
SUL Supplementary Uplink
UL Uplink
WLAN Wireless Local Area Network
4 UE radio access capability parameters
4.1 Supported max data rate
4.1.1 General
The DL, UL and SL max data rate supported by the UE is calculated by band or band combinations supported by the
UE. A UE supporting NR (NR SA, MR-DC) shall support the calculated DL and UL max data rate defined in 4.1.2. A
UE supporting NR sidelink communication shall support the calculated SL max data rate defined in 4.1.5.
4.1.2 Supported max data rate for DL/UL
For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is computed
as follows.
J BW ( j),μ
 
N ⋅12
−6 ( j) ( j) ( j) PRB ( j)
 
data rate (in Mbps) = 10 ⋅ v ⋅Q ⋅ f ⋅ R ⋅ ⋅()1− OH
 m max
μ
 Layers 
T
j=1  s 
wherein
J is the number of aggregated component carriers in a band or band combination
R = 948/1024
max
For the j-th CC,
( j)
v is the maximum number of supported layers given by maxNumberMIMO-LayersPDSCH for downlink
Layers
and maximum of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for
uplink.
( j)
Q
is the maximum supported modulation order given by supportedModulationOrderDL for downlink and
m
supportedModulationOrderUL for uplink.
( j)
f is the scaling factor given by scalingFactor and can take the values 1, 0.8, 0.75, and 0.4.
μ
is the numerology (as defined in TS 38.211 [6])
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 9 ETSI TS 138 306 V16.23.0 (2026-04)
−3
μ
μ T =
s
μ
T
μ
s
14 ⋅ 2
is the average OFDM symbol duration in a subframe for numerology , i.e. . Note that
normal cyclic prefix is assumed.
BW()j ,μ
()j
N μ
BW
PRB
is the maximum RB allocation in bandwidth with numerology , as defined in 5.3 TS
()j
BW
38.101-1 [2] and 5.3 TS 38.101-2 [3], where is the UE supported maximum bandwidth in the given
band or band combination.
( j)
OH is the overhead and takes the following values

0.14, for frequency range FR1 for DL
0.18, for frequency range FR2 for DL
0.08, for frequency range FR1 for UL
0.10, for frequency range FR2 for UL
NOTE 1: Only one of the UL or SUL carriers (the one with the higher data rate) is counted for a cell operating
SUL.
NOTE 2: For UL Tx switching between carriers, only the supported MIMO layer combination across carriers that
results in the highest combined data rate is counted for the carriers in the supported maximum UL data
rate.
The approximate maximum data rate can be computed as the maximum of the approximate data rates computed using
the above formula for each of the supported band or band combinations.
For single carrier NR SA operation, the UE shall support a data rate for the carrier that is no smaller than the data rate
(�) ��� ���
computed using the above formula, with � =1 �� and component � ⋅� ⋅� is no smaller than 4.
������ �
(�) ��� ���
NOTE 3: As an example, the value 4 in the component above can correspond to � =1, � = 4 and � =
������ �
1.
For EUTRA in case of MR-DC, the approximate data rate for a given number of aggregated carriers in a band or band
combination is computed as follows.
J
−3
Data rate (in Mbps) = 10 ⋅ TBS
 j
j=1
wherein
J is the number of aggregated EUTRA component carriers in MR-DC band combination
��� is the total maximum number of DL-SCH transport block bits received or the total maximum number of

UL-SCH transport block bits transmitted, within a 1ms TTI for j-th CC, as derived from TS36.213 [19] based on
the UE supported maximum MIMO layers for the j-th CC, and based on the maximum modulation order for the
j-th CC and number of PRBs based on the bandwidth of the j-th CC according to indicated UE capabilities.
The approximate maximum data rate can be computed as the maximum of the approximate data rates computed using
the above formula for each of the supported band or band combinations.
For MR-DC, the approximate maximum data rate is computed as the sum of the approximate maximum data rates from
NR and EUTRA.
4.1.3 Void
4.1.4 Total layer 2 buffer size for DL/UL
The total layer 2 buffer size is defined as the sum of the number of bytes that the UE is capable of storing in the RLC
transmission windows and RLC reception and reassembly windows and also in PDCP reordering windows for all radio
bearers.
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 10 ETSI TS 138 306 V16.23.0 (2026-04)
The required total layer 2 buffer size in MR-DC is the maximum value of the calculated values based on the following
equations:
- MaxULDataRate_MN * RLCRTT_MN + MaxULDataRate_SN * RLCRTT_SN + MaxDLDataRate_SN *
RLCRTT_SN + MaxDLDataRate_MN * (RLCRTT_SN + X2/Xn delay + Queuing in SN)
- MaxULDataRate_MN * RLCRTT_MN + MaxULDataRate_SN * RLCRTT_SN + MaxDLDataRate_MN *
RLCRTT_MN + MaxDLDataRate_SN * (RLCRTT_MN + X2/Xn delay + Queuing in MN)
Otherwise it is calculated by MaxDLDataRate * RLC RTT + MaxULDataRate * RLC RTT.
NOTE: Additional L2 buffer required for preprocessing of data is not taken into account in above formula.
The required total layer 2 buffer size is determined as the maximum total layer 2 buffer size of all the calculated ones
for each band combination and the applicable Feature Set combination in the supported MR-DC or NR band
combinations. The RLC RTT for NR cell group corresponds to the smallest SCS numerology supported in the band
combination and the applicable Feature Set combination.
wherein
X2/Xn delay + Queuing in SN = 25ms if SCG is NR, and 55ms if SCG is EUTRA
X2/Xn delay + Queuing in MN = 25ms if MCG is NR, and 55ms if MCG is EUTRA
RLC RTT for EUTRA cell group = 75ms
RLC RTT for NR cell group is defined in Table 4.1.4-1
Table 4.1.4-1: RLC RTT for NR cell group per SCS
SCS (kHz) RLC RTT (ms)
15KHz 50
30KHz 40
60KHz 30
120KHz 20
4.1.5 Supported max data rate for SL
For NR sidelink, the approximate data rate is computed as follows.
��,�
� ⋅12
���
��
� �
data rate (in Mbps)= 10 ⋅� ⋅� ⋅� ⋅� ⋅ ⋅ 1−��
������ � ��� �


wherein
R = 948/1024,
max
� is the the maximum number of supported layers for sidelink transmission (or reception) given by UE
������
capability on supporting rank 2 PSSCH transmission and rankTwoReception,
is the maximum supported modulation order between 6 or 8 given by sl-Tx-256QAM and sl-Rx-256QAM,


� is the scaling factor for sidelink transmission and reception given by scalingFactorTxSidelink and
scalingFactorRxSidelink respectively, as specified in TS 36.331 [17] and TS 38.331 [9], and can take the
values 1, 0.8, 0.75, and 0.4.
μ
is the numerology (as defined in TS 38.211 [6])
−3
μ
μ
μ
T is the average OFDM symbol duration in a subframe for numerology , i.e. T = . Note that
s
s μ
14⋅2
normal cyclic prefix is assumed.
��,�
� is the maximum possible RB allocation in bandwidth BW for PSSCH, where BW is the UE supported
���
maximum bandwidth in the given band or band combination,
�� is the overhead and takes the following values
0.217, for frequency range FR1 for SL
0.25, for frequency range FR2 for SL

ETSI
3GPP TS 38.306 version 16.23.0 Release 16 11 ETSI TS 138 306 V16.23.0 (2026-04)
4.1.6 Total layer 2 buffer size for NR SL
The total layer 2 buffer size for NR sidelink communication is defined as the sum of the number of bytes that the UE is
capable of storing in the RLC transmission windows and RLC reception and reassembly windows and also in PDCP
reordering windows for all radio bearers for NR sidelink communication.
The required total layer 2 buffer size for NR sidelink communication is the maximum value of the calculated values
based on the following equations:
MaxSLtxDataRate * RLC RTT + MaxSLrxDataRate * RLC RTT.
NOTE: Additional L2 buffer required for preprocessing of data is not taken into account in above formula.
The required total layer 2 buffer size for NR sidelink communication is determined as the maximum total layer 2 buffer
size of all the calculated ones for each band combination and the applicable Feature Set combination in the supported
NR sidelink band combinations. The RLC RTT for NR sidelink communication corresponds to the smallest SCS
numerology supported in the band combination and the applicable Feature Set combination.
wherein
RLC RTT for NR sidelink communication is defined in Table 4.1.6-1
Table 4.1.6-1: RLC RTT for NR sidelink communication per SCS
SCS (kHz) RLC RTT (ms)
15KHz 200
30KHz 100
60KHz 50
120KHz 25
4.2 UE Capability Parameters
4.2.1 Introduction
The following clauses define the UE radio access capability parameters. Only parameters for which there is the
possibility for UEs to signal different values are considered as UE radio access capability parameters. Therefore,
mandatory features without capability parameters that are the same for all UEs are not listed here.
The network needs to respect the signalled UE radio access capability parameters when configuring the UE and when
scheduling the UE.
For capabilities that required to be set consistently for all FDD-FR1 bands (i.e. capabilities that are supposed to be per
UE), the UE shall also set capability values for all SUL bands with same values for FDD-FR1 bands if SUL band is
supported by the UE.
The UE may support different functionalities between FDD and TDD, and/or between FR1 and FR2. The UE shall
indicate the UE capabilities as follows. In the table of UE capability parameter in subsequent clauses, "Yes" in the
column by "FDD-TDD DIFF" and "FR1-FR2 DIFF" indicates the UE capability field can have a different value for
between FDD and TDD or between FR1 and FR2 and "No" indicates if it cannot. Regarding to the per UE capabilities
that are FDD/TDD differentiated(i.e. capabilities indicated as "Yes" in the column by "FDD-TDD DIFF"), the
corresponding capabilities indicated by the FDD capability is applied to SUL/SDL if SUL/SDL band is supported by
the UE. "FD" in the column indicates to refer the associated field description. "FR1 only" or "FR2 only" in the column
indicates the associated feature is only supported in FR1 or FR2 and "TDD only" indicates the associated feature is only
supported in TDD and not applicable to SUL/SDL carriers. "N/A" in the column indicates it is not applicable to the
feature (e,g. the signalling supports the UE to have different values between FDD and TDD or between FR1 and FR2).
1> set all fields of UE-NR/MRDC-Capability except fdd-Add-UE-NR/MRDC/Sidelink-Capabilities, tdd-Add-UE-
NR/MRDC/Sidelink-Capabilities, fr1-Add-UE-NR/MRDC-Capabilities and fr2-Add-UE-NR/MRDC-
Capabilities, to include the values applicable for all duplex mode(s) and frequency range(s) that the UE supports;
1> if UE supports both FDD (or SUL/SDL) and TDD and if (some of) the UE capability fields have a different
value for FDD (or SUL/SDL) and TDD:
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 12 ETSI TS 138 306 V16.23.0 (2026-04)
2> if for FDD (and, if the UE supports SUL/SDL, for SUL/SDL), the UE supports additional functionality
compared to what is indicated by the previous fields of UE-NR/MRDC-Capability/SidelinkParameters:
3> include field fdd-Add-UE-NR/MRDC/Sidelink-Capabilities and set it to include fields reflecting the
additional functionality applicable for FDD;
2> if for TDD, the UE supports additional functionality compared to what is indicated by the previous fields of
UE-NR/MRDC-Capability/SidelinkParameters:
3> include field tdd-Add-UE-NR/MRDC/Sidelink-Capabilities and set it to include fields reflecting the
additional functionality applicable for TDD;
1> if UE supports both FR1 and FR2 and if (some of) the UE capability fields have a different value for FR1 and
FR2:
2> if for FR1, the UE supports additional functionality compared to what is indicated by the previous fields of
UE-NR/MRDC-Capability:
3> include field fr1-Add-UE-NR/MRDC-Capabilities and set it to include fields reflecting the additional
functionality applicable for FR1;
2> if for FR2, the UE supports additional functionality compared to what is indicated by the previous fields of
UE-NR/MRDC-Capability:
3> include field fr2-Add-UE-NR/MRDC-Capabilities and set it to include fields reflecting the additional
functionality applicable for FR2;
NOTE 1: The fields which indicate "shall be set to 1" or "shall be set to supported" in the following tables means
these features are purely mandatory and are assumed they are the same as mandatory without capability
signalling.
NOTE 2: For the case where the UE is allowed to support different functionality between FDD and TDD and
between FR1 and FR2 according to the specification, the UE capability indication is clarified in Annex B.
For optional features, the UE radio access capability parameter indicates whether the feature has been implemented and
successfully tested. For mandatory features with the UE radio access capability parameter, the parameter indicates
whether the feature has been successfully tested. In the table of UE capability parameter in subsequent clauses, "Yes" in
the column by "M" indicates the associated feature is mandatory and "No" indicates the associated feature is optional.
"CY" in the column indicates the associated feature is conditional mandatory and the condition is described in the field
description and the associated feature is considered mandatory with capability parameter, when the described condition
is satisfied. "FD" in the column indicates to refer the associated field description. Some parameters in subsequent
clauses are not related to UE features and in the case, "N/A" is indicated in the column.
UE capability parameters have hierarchical structure. In the table of UE capability parameter in subsequent clauses,
"Per" indicates the level the associated parameter is included. "UE" in the column indicates the associated parameter is
signalled per UE, "Band" indicates it is signalled per band, "BC" indicates it is signalled per band combination, "FS"
indicates it is signalled per feature set (per band per band combination), "FSPC" indicates it is signalled per feature set
per component carrier (per CC per band per band combination), and "FD" in the column indicates to refer the associated
field description.
NOTE 3: Unless otherwise specified, for dependent capabilities with prerequisite capability in a finer granularity,
the UE should indicate support of the prerequisite capability in at least one finer granularity. And the
dependent capability is supported only in the finer granularity where the prerequisite capability is
supported, e.g. a UE indicating support of supportNewDMRS-Port-r16 (dependent capability which is
defined per band) should indicate at least one band combination where singleDCI-SDM-scheme-r16
(prerequisite capability which is defined per feature set) is supported in the corresponding band. In this
case, supportNewDMRS-Port-r16 is considered supported only in the corresponding band of the band
combination where singleDCI-SDM-scheme-r16 is supported.
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 13 ETSI TS 138 306 V16.23.0 (2026-04)
4.2.2 General parameters
ETSI
3GPP TS 38.306 version 16.23.0 Release 16 14 ETSI TS 138 306 V16.23.0 (2026-04)
Definitions for parameters Per M FDD- FR1-
TDD FR2
DIFF DIFF
accessStratumRelease UE Yes No No
Indicates the access stratum release the UE supports as specified in TS 38.331 [9].
delayBudgetReporting UE No No No
Indicates whether the UE supports delay budget reporting as specified in TS 38.331
[9].
dl-DedicatedMessageSegmentation-r16
UE No No No
Indicates whether the UE supports reception of segmented DL RRC messages.
drx-Preference-r16 UE No No No
Indicates whether the UE supports providing its preference of a cell group on DRX
parameters for power saving in RRC_CONNECTED, as specified in TS 38.331 [9].
inactiveState UE Yes No No
Ind
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...