5G/NR - UE Capability  

 

 

 

UE Capability in a Nutshell

 

  • What is it for ? UE capability is a RRC signaling mechanism by which UE can inform its capabilities to gNB
  • gNB request UE to inform about its capability by sending the message : UE Capability Enquiry and UE responds to this request by sending UE Capability Information message.
  • NR UE capability Information in general is much more complicated than LTE UE capability Information because NR Radio stack is more flexible and complex than LTE radio stack.
  • gNB may not want to get all the possible UE capability information and can restrict the type and amount of UE capability information by putting a specific requirements in UE capability Enquiry. The entire list of UE capabilities without any restriction can be too long and cause too much signaling overhead if it is transmitted in full size.
  • Some of the most important information on UE capability Information in NR would be : bandwidth information, Bandwidth(for single carrier) and Bandwidth Combination(for Carrier Aggregation), MIMO, Subcarrier Spacing etc.

UE Capability in Detail

The purpose (Function) of UE Capability Information in NR is same as LTE UE Capability Information. In LTE UE capability information carries the information in roughly two large category : RF/Physical layer information and Feature Group(FGI). NR also reports similar information (i.e, RF/PHY information and Feature sets) but much more diverse information than LTE.

For the details of the meaning of each IEs listed here, refer to 38.306. But to understand the exact meaning of the descriptions in 38.306, you would need to understand the whole NR specification... simply put, it would be life time job to understand the full details of what you see in the UE capability information. So.. don't be hurry.. take time trying to one at a time.  The best way is to take a look at specific IEs that you are interested one at a time and find some examples as shown below and try to understand the detailed meaning based on 38.306 and all other related specification.

Why UE capability checking is important ?

In modern LTE and 5G networks, the UE Capability Enquiry and UE Capability Information procedures play a critical role in enabling seamless communication and optimal resource allocation between the User Equipment (UE) and the network. These processes allow the network to gather detailed information about the UE's supported features, including frequency bands, carrier aggregation capabilities, modulation schemes, and advanced functionalities like MIMO and beamforming. By understanding the UE's capabilities, the network can efficiently tailor its configurations, ensuring compatibility, maximizing performance, and enabling advanced features such as dynamic spectrum sharing and dual connectivity. Moreover, these procedures are essential for supporting interworking between multiple radio access technologies (RATs), like LTE, NR, and legacy networks, to provide uninterrupted service and superior user experience. Neglecting these processes can lead to underutilization of resources, degraded service quality, and potential interoperability challenges, underscoring their significance in modern telecommunications systems.

  • Essential Role in Communication: UE Capability Enquiry and UE Capability Information procedures are vital for seamless communication and optimal resource allocation in LTE and 5G networks.
  • Detailed Capability Assessment: These processes allow the network to gather information about the UE's supported features, such as frequency bands, carrier aggregation, modulation schemes, and advanced functionalities like MIMO and beamforming.
  • Efficient Network Configuration: By understanding the UE's capabilities, the network can optimize configurations to ensure compatibility and maximize performance.
  • Enablement of Advanced Features: They facilitate advanced functionalities like dynamic spectrum sharing, dual connectivity, and beam management.
  • Inter-RAT Interoperability: These procedures are critical for smooth operation between multiple radio access technologies (RATs), such as LTE, NR, and legacy networks.
  • Avoidance of Resource Wastage: Proper execution ensures efficient resource allocation and avoids issues like underutilization or misconfiguration.
  • Enhanced User Experience: Ensures superior quality of service and uninterrupted network operation.

NOTE : One of the most frequent issues that I've heard of is 'I am trying to test my UE for this feature, but Network does not enable the feature'. In many of these cases, the root cause turned out to be because UE does not declaire the support of the feature in UE capability Information. If you have similar issue, my recommendation is to check UEcapability Information from your device.

 

Pitfalls of UE Capability Reporting

The UE Capability Enquiry and UE Capability Information procedures are critical for efficient network operations, but they are not without potential pitfalls. One significant challenge arises when a UE reports support for a capability during the capability information exchange, but in practice, the feature is either partially implemented or not functional in the real-world scenario. This discrepancy can lead to several issues:

  • Network Misconfiguration
    • The network may configure the UE for a feature it claims to support (e.g., carrier aggregation, high-order MIMO, or specific NR numerologies). However, if the UE's implementation of this feature is incomplete or non-functional, it can result in misaligned configurations. This can lead to session drops, failed handovers, or degraded service quality.
  • Resource Wastage
    • The network allocates resources, such as spectrum and scheduling grants, based on the UE's reported capabilities. If the UE cannot utilize these resources effectively, it wastes valuable network resources that could be allocated to other UEs.
  • Service Interruptions
    • Inaccurate capability reporting can cause interruptions in advanced services like VoLTE, VoNR, or carrier aggregation. For instance, if a UE reports support for 256QAM modulation but experiences errors when operating at higher modulation levels, it can degrade overall service performance.
  • Interoperability Issues
    • Networks often comprise equipment from multiple vendors. A mismatch between UE-reported capabilities and actual implementation can cause interoperability issues, particularly in features like dynamic spectrum sharing, dual connectivity, or beamforming, which rely on tight coordination between the UE and the network.
  • Testing and Validation Gaps
    • UEs sometimes pass compliance testing but fail in live network scenarios because the capability was not fully tested under diverse conditions. This gap between theoretical support and practical performance can lead to unexpected failures during deployment.
  • Increased Troubleshooting Complexity
    • Identifying and resolving issues caused by inaccurate UE capability reporting can be challenging. Network engineers must investigate whether the problem lies in the UE's implementation, network configurations, or an interaction between the two.
  • Impact on QoS and User Experience
    • When the network relies on false capability information, the quality of service (QoS) can be negatively impacted, leading to poor user experiences such as slower data rates, call drops, or inconsistent coverage.

Examples of Real-World Scenarios

  • A UE may claim support for carrier aggregation but fail to handle specific inter-band combinations due to hardware limitations.
  • A device might report support for advanced modulation schemes like 256QAM but lack the processing power to maintain acceptable error rates at higher modulation levels.
  • UEs might advertise compatibility with certain 5G numerologies or bandwidths but struggle with power management, causing early battery drain or overheating.

High Level Categories of UE capability

UE capabilities can be broadly classified into two main categories: Radio capabilities and Supported features.

Radio capabilities encompass the physical layer characteristics of the device, such as the frequency bands and bandwidths it can operate on, the modulation schemes it supports, and its MIMO capabilities (i.e., the number of antennas it can use for transmitting and receiving data). This category also includes the device's power class, which determines the maximum power it can transmit, and its support for carrier aggregation, allowing it to combine multiple frequency bands for increased data rates.

Supported features delve into the device's capabilities beyond the physical layer, encompassing functionalities like support for specific network technologies (e.g., LTE, NR), data transmission protocols, and advanced features like positioning and location services. This category also includes information about the device's software and hardware capabilities, ensuring compatibility with the network's services and applications.

Essentially, these two categories together provide a comprehensive overview of the device's communication capabilities, enabling the network to optimize the connection and provide the best possible user experience.

Supported Maximum Data Rates

These capabilities are essential for the network to allocate resources effectively and ensure optimal data transfer for various applications, from basic web browsing to demanding real-time services.

Downlink (DL) and Uplink (UL) Maximum Data Rates

These indicate the peak data speeds the UE can achieve when receiving (DL) and transmitting (UL) data. These rates are influenced by factors like the UE's category, supported modulation schemes, and MIMO capabilities. Higher data rates allow for faster downloads, smoother streaming, and quicker uploads.

  • Key Parameters for DL and UL Data Rates:
    • MaxDLDataRate: The maximum data rate for the downlink.
    • MaxULDataRate: The maximum data rate for the uplink.

Sidelink (SL) Maximum Data Rates

This specifies the maximum data rate for direct communication between UEs, bypassing the base station. Sidelink communication is crucial for proximity services like vehicle-to-everything (V2X) communication and public safety applications.

  • Key Parameters for SL Data Rates:
    • MaxSLtxDataRate: Maximum sidelink transmission data rate.
    • MaxSLrxDataRate: Maximum sidelink reception data rate.

Total Layer 2 Buffer Size for DL/UL and Sidelink

The total Layer 2 (L2) buffer size refers to the amount of data the UE can store in the RLC and PDCP layers during transmission and reception. It ensures efficient handling of data across multiple bearers.

  • Key Parameters:
    • MaxDLDataRate and MaxULDataRate: Used to determine the buffer size for DL and UL.
    • MaxSLtxDataRate and MaxSLrxDataRate: Used for sidelink buffer size.
    • RLC RTT (Round Trip Time): Delay values for RLC processing, dependent on numerology and frequency range.
    • X2/Xn delay + Queuing: Network-side delay assumptions:
      • 25ms if NR is the Secondary Cell Group (SCG).
      • 55ms if EUTRA is the SCG.

General UE Capability Parameters

The General UE Capability Parameters define the key features that allow a UE to work efficiently with the network in NR (New Radio) systems. These parameters include support for power-saving modes, handling multiple carriers, managing mobility, and optimizing performance for tasks like delay reporting and paging. They also enable the UE to communicate its capabilities, such as bandwidth, MIMO preferences, and overheating management, helping the network provide better performance and energy efficiency. These parameters ensure the UE can integrate smoothly into 5G networks and deliver a reliable user experience.

Definitions for parameters

Per

M

FDD-TDD DIFF

FR1-FR2 DIFF

accessStrat umRelease Indicates the access stratum release the UE supports as specified in TS 38.331 .

UE

Yes

No

No

crossCarrierS chedulingCon figurationRelease-r17 Indicates whether the UE supports using crossCarrier SchedulingCo nfigRelease* to release the co nfigurations configured by crossC arrierSchedu lingConfig*.

UE

No

No

No

delayBudget Reporting Indicates whether the UE supports delay budget reporting as specified in TS 38.331 [9].

UE

No

No

No

dl -DedicatedMessageSegment ation-r16 Indicates whether the UE supports reception of segmented DL RRC messages.

UE

No

No

No

drx-Preference-r16 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].

UE

No

No

No

gNB-SideRTT-BasedPDC-r17 Indicates whether the UE supports gNB-side RTT-based PDC, as specified in TS 38.300 . A UE supporting this feature shall also support**rtt-BasedPDC-CSI-RS-For Tracking-r17**and/or**rtt-BasedPDC-PRS-r17

UE

No

No

No

inactiveState Indicates whether the UE supports RRC_INACTIVE as specified in TS 38.331

UE

Yes

No

No

inactiveStateNTN-r17 Indicates whether the UE supports RRC_INACTIVE in NTN as specified in TS 38.331 [9]. It is mandated if the UE indicates the support of nonTerrestrialNetwork-r17.

UE

CY

No

No

inactiveStatePO-Determination-r17 Indicates whether the UE supports to use the same i_s to determine PO in RRC_INACTIVE state as in RRC_IDLE state.

UE

No

No

No

inDeviceCoexInd-r16 Indicates whether the UE supports IDC (In-Device Coexistence) assistance information as specified in TS 38.331 [9].

UE

No

No

No

maxBW-Preference-r16, maxBW-Preference-r17 Indicates whether the UE supports providing its preference of a cell group on the maximum aggregated bandwidth for power saving in RRC_CONNECTED, as specified in TS 38.331

UE

No

No

Yes(Incl FR2-2 DIFF)

maxCC-Preference-r16 Indicates whether the UE supports providing its preference of a cell group on the maximum number of secondary component carriers for power saving in RRC_CONNECTED, as specified in TS 38.331

UE

No

No

No

maxMIMO-LayerPreference-r16, maxMIMO-LayerPreference-r17 Indicates whether the UE supports providing its preference of a cell group on the maximum number of MIMO layers for power saving in RRC_CONNECTED, as specified in TS 38.331

UE

No

No

Yes(Incl FR2-2 DIFF)

maxMRB-Add-r17 Indicates the additional maximum number of MRBs that the UE supports for MBS multicast reception as specified in TS 38.331

UE

No

No

No

mcgRLF-RecoveryViaSCG-r16 Indicates whether the UE supports recovery from MCG RLF via split SRB1 (if supported) and via SRB3 (if supported) as specified in TS 38.331.

UE

No

No

No

minSchedulingOffsetPreference-r16 Indicates whether the UE supports providing its preference on the minimum scheduling offset for cross-slot scheduling of the cell group for power saving in RRC_CONNECTED, as specified in TS 38.331 .

UE

No

No

No

mpsPriorityIndication-r16 Indicates whether the UE supports mpsPriorityIndication on RRC release with redirect as defined in TS 38.331

UE

No

No

No

musim-GapPreference-r17 Indicates whether the UE supports providing MUSIM assistance information  with MUSIM gap preference and related MUSIM gap co nfiguration, as defined in TS 38.331 . UE supporting this feature supports 3 periodic gaps and 1 aperiodic gap.

UE

No

No

No

musimLeaveConnected-r17 Indicates whether the UE supports providing MUSIM assistance information with indication of leaving RRC_CONNECTED state  as defined in TS 38.331

UE

No

No

No

nonTerrestrialNetwork-r17 Indicates whether the UE supports NR NTN access. If the UE indicates this capability the UE shall support the following NTN essential features, e.g., timer extension in MAC/RLC/PDCP layers and RACH adaptation to handle long RTT, acquiring NTN specific SIB and more than one TAC per PLMN broadcast in one cell.

UE

No

No

No

ntn-ScenarioSupport-r17 Indicates whether the UE supports the NTN features in GSO scenario or NGSO scenario. If a UE does not include this field but includes nonTerrestrialNetwork-r17, the UE supports the NTN features for both GSO and NGSO scenarios, and also supports mobility between GSO and NGSO scenarios.

UE

No

No

No

onDemandSIB-Connected-r16 Indicates whether the UE supports the on-demand request procedure of SIB(s) or posSIB(s) while in RRC_CONNECTED, as specified in TS 38.331 .

UE

No

No

No

overheatingInd Indicates whether the UE supports overheating assistance information.

UE

No

No

No

pei-SubgroupingSupportBandList-r17 Indicates whether the UE supports receiving paging early indication in DCI format 2_7 as specified in TS38.304 [21] for a list of frequency band. The UE shall support UEID based subgrouping for a frequency band if it indicates supporting of paging early indication reception for the frequency band. The set of OFDM symbols within a slot where UE can monitor the PEI PDCCH in Type 2A CSS is the same as the requirement for paging PDCCH in Type 2 CSS for IDLE and INACTIVE mode UEs.

UE

No

No

No

partialFR2-FallbackRX-Req Indicates whether the UE meets only a partial set of the UE minimum receiver requirements for the eligible FR2 fallback band combinations as defined in Clause 4.2 of TS 38.101-2 and Clause 4.2 of TS 38.101-3 . If not indicated, the UE shall meet all the UE minimum receiver requirements for all the FR2 fallback combinations in TS 38.101-2 and TS 38.101-3. The UE shall support configuration of any of the FR2 fallback band combinations regardless of the presence or the absence of this field.

UE

No

No

No

ra-SDT-r17 Indicates whether the UE supports transmission of data and/or signalling over allowed radio bearers in RRC_INACTIVE state via Random Access procedure (i.e., RA-SDT) with 4-step RA type and if UE supports twoStepRACH-r16, with 2-step RA type, as specified in TS 38.331

UE

No

No

No

ra-SDT-NTN-r17 Indicates whether the UE supports transmission of data and/or signalling over allowed radio bearers in RRC_INACTIVE statein NTN via Random Access procedure (i.e., RA-SDT) with 4-step RA type and if UE supports two StepRACH-r16 for NTN, with 2-step RA type, as specified in TS 38.331 . A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17.

UE

No

No

No

redirectAtResumeByNAS-r16 Indicates whether the UE supports reception of redirectedCarrierInfo in an RRCRelease message in response to an RRCResumeRequest or RRCResumeRequest1 which is triggered by the NAS layer, as specified in TS 38.331

UE

No

No

No

reducedCP-Latency Indicates whether the UE supports reduced control plane latency as defined in TS 38.331

UE

No

No

No

referenceTimeProvision-r16 Indicates whether the UE supports provision of referenceTimeInfo in DLInformationTransfer* message and in SIB9 and reference time information preference indication via assistance information, as specified in TS 38.331

UE

No

No

No

releasePreference-r16 Indicates whether the UE supports providing its preference assistance information to transition out of RRC_CONNECTED for power saving, as specified in TS 38.331

UE

No

No

No

resumeWithStoredMCG-Cells-r16 Indicates whether the UE supports not deleting the stored MCG SCell configuration when initiating the resume procedure.

UE

No

No

No

resumeWithStoredSCG-r16 Indicates whether the UE supports not deleting the stored SCG configuration when initiating resume. The UE which indicates support for resumeWithStoredSCG-r16 shall also indicate support for *resumeWithSCG-Config-r16

UE

No

No

No

resumeWithSCG-Config-r16 Indicates whether the UE supports (re-)configuration of an SCG during the resume procedure.

UE

No

No

No

sliceInfoforCellReselection-r17 Indicates whether the UE supports slice-based cell reselection information in SIB and on RRC release for slice-based cell reselection in RRC_IDLE and RRC_INACTIVE as defined in TS 38.304 [21].

UE

No

No

No

splitSRB-WithOneUL-Path Indicates whether the UE supports UL transmission via MCG path and DL reception via either MCG path or SCG path, as specified for the split SRB in TS 37.340 . The UE shall not set the FDD/TDD specific fields for this capability (i.e. it shall not include this field in UE-MRDC-CapabilityAddXDD-Mode).

UE

No

No

No

splitDRB-withUL-Both-MCG-SCG Indicates whether the UE supports UL transmission via both MCG path and SCG path for the split DRB as specified in TS 37.340 . The UE shall not set the FDD/TDD specific fields for this capability (i.e. it shall not include this field in UE-MRDC-CapabilityAddXDD-Mode).

UE

Yes

No

No

srb3 Indicates whether the UE supports direct SRB between the SN and the UE as specified in TS 37.340 . The UE shall not set the FDD/TDD specific fields for this capability (i.e. it shall not include this field in UE-MRDC-CapabilityAddXDD-Mode). This field is not applied to NE-DC.

UE

Yes

No

No

srb-SDT-NTN-r17 Indicates whether the UE supports the usage of signalling radio bearer SRB2 over RA-SDT or CG-SDT in NTN, as specified in TS 38.331 . A UE supporting this feature shall also indicate support of ra-SDT-NTN-r17, or cg-SDT-r17 in NTN bands. A UE supporting this feature shall also indicate the support of *nonTerrestrialNetwork-r17.

UE

No

No

No

srb-SDT-r17 Indicates whether the UE supports the usage of signalling radio bearer SRB2 over RA-SDT or CG-SDT, as specified in TS 38.331 .A UE supporting this feature shall also indicate support of ra-SDT-r17 or cg-SDT-r17

UE

No

No

No

ul-GapFR2-Pattern-r17 Indicates FR2 UL gap pattern(s) supported by the UE for NR SA, for NR-DC without FR2-FR2 band combination, for NE-DC, and for (NG)EN-DC, if UE supports a band in FR2. The leading / leftmost bit (bit 0) corresponds to the FR2 UL gap pattern 0, the next bit corresponds to the FR2 UL gap pattern 1, as specified in TS 38.133 and so on. The UE shall set at least one of the bits to 1 for FR2 UL gap pattern 1 and 3, if the UE indicates support for ul-GapFR2-r17 in an FR2 band.

UE

CY

No

FR2 only

ul-RRC-Segmentation-r16 Indicates whether the UE supports uplink RRC seg mentation of  UECapabilityInformation* as specified in TS 38.331

UE

No

No

No

PDCP Parameters

PDCP (Packet Data Convergence Protocol) parameters define how data is processed, compressed, and managed over the 5G NR radio interface. They address aspects such as header compression (for both Ethernet and IP-based traffic), security features like ciphering and integrity protection, and advanced capabilities like PDCP duplication and Uplink Data Compression (UDC). These parameters ensure that data can be delivered efficiently and reliably, adapt to diverse network requirements, and maintain service quality across various deployment scenarios.

Key points include:

  • Header Compression: Defines mechanisms (e.g., ROHC, EHC) to reduce overhead for IP and Ethernet packets.
  • Security Functions: Manages ciphering and integrity protection for user data.
  • PDCP Duplication: Provides robust data delivery by replicating packets across multiple RLC entities.
  • PDCP Discard Timers: Governs how long data can be buffered before being dropped.
  • Uplink Data Compression: Optimizes bandwidth usage for uplink traffic through dictionary-based compression.

These parameters collectively enable PDCP to balance reliability, bandwidth efficiency, and latency, ensuring a high-quality user experience in 5G NR networks.

Definitions for parameters

Per

M

FDD-TDD DIFF

continueEHC-Context-r16 Indicates that the UE supports EHC context continuation operation where the UE keeps the established EHC context(s) upon PDCP re-establishment, as specified in TS 38.323

UE

No

No

continueROHC-Context Defines whether the UE supports ROHC context continuation operation where the UE does not reset the current ROHC context upon PDCP re-establishment, as specified in TS 38.323

UE

No

No

ehc-r16 Indicates that the UE supports Ethernet header compression and decompression using EHC protocol, as specified in TS 38.323 [16]. The UE indicating this capability and indicating support for at least one ROHC profile, shall support simultaneous configuration of EHC and ROHC on different DRBs/multicast MRBs.

UE

No

No

extendedDiscardTimer-r16 Indicates whether the UE supports the additional values of PDCP discard timer. The supported additional values are 0.5ms, 1ms, 2ms, 4ms, 6ms and 8ms, as specified in TS 38.331

UE

No

No

jointEHC-ROHC-Config-r16 Indicates whether the UE supports simultaneous configuration of EHC and ROHC protocols for the same DRB/multicast MRB.

UE

No

No

maxNumberROHC-ContextSessions Defines the maximum number of ROHC header compression context sessions supported by the UE across all DRBs and multicast MRBs, excluding context sessions that leave all headers uncompressed.

UE

No

No

maxNumberEHC-Contexts-r16 Defines the maximum number of Ethernet header compression contexts supported by the UE across all DRBs and multicast MRBs and across UE's EHC compressor and EHC decompressor. The indicated number defines the number of contexts in addition to CID = "all zeros" as specified in TS 38.323

UE

No

No

outOfOrderDelivery Indicates whether UE supports out of order delivery of data to upper layers by PDCP.

UE

No

No

pdcp-DuplicationMCG-OrSCG-DRB Indicates whether the UE supports CA-based PDCP duplication over MCG or SCG DRB as specified in TS 38.323

UE

No

No

pdcp-DuplicationMoreThanTwoRLC-r16 Defines whether the UE supports PDCP duplication with more than two RLC entities as specified in TS 38.323. The UE supporting this feature supports secondary RLC entity(ies) activation and deactivation based on duplication RLC Activation/Deactivation MAC CE as specified in TS 38.321. A UE supporting this feature shall also support pdcp-DuplicationMCG-OrSCG-DRB, pdcp-DuplicationSplitDRB, pdcp-DuplicationSplitSRB and pdcp-DuplicationSRB.

UE

No

No

pdcp-DuplicationSplitDRB Indicates whether the UE supports PDCP duplication over split DRB as specified in TS 38.323.

UE

No

No

pdcp-DuplicationSplitSRB Indicates whether the UE supports PDCP duplication over split SRB1/2 as specified in TS 38.323.

UE

No

No

pdcp-DuplicationSRB Indicates whether the UE supports CA-based PDCP duplication over SRB1/2 and/or, if (NG)EN-DC is supported, SRB3 as specified in TS 38.323.

UE

No

No

shortSN Indicates whether the UE supports 12 bit length of PDCP sequence number.

UE

Yes

No

supportedROHC-Profiles Defines which ROHC profiles from the list below are supported by the UE: >

- 0x0000 ROHC No compression (RFC 5795) >

- 0x0001 ROHC RTP/UDP/IP (RFC 3095, RFC 4815) >

- 0x0002 ROHC UDP/IP (RFC 3095, RFC 4815) >

- 0x0003 ROHC ESP/IP (RFC 3095, RFC 4815) >

- 0x0004 ROHC IP (RFC 3843, RFC 4815) >

- 0x0006 ROHC TCP/IP (RFC 6846) >

- 0x0101 ROHC RTP/UDP/IP (RFC 5225) >

- 0x0102 ROHC UDP/IP (RFC 5225) >

- 0x0103 ROHC ESP/IP (RFC 5225) >

- 0x0104 ROHC IP (RFC 5225)

A UE that supports one or more of the listed ROHC profiles shall support ROHC profile 0x0000 ROHC uncompressed (RFC 5795). An IMS voice capable UE shall indicate support of ROHC profiles 0x0000, 0x0001, 0x0002 and be able to compress and decompress headers of PDCP SDUs at a PDCP SDU rate corresponding to supported IMS voice codecs.

UE

No

No

udc-r17 Indicates whether the UE supports the uplink data compression operation as specified in TS 38.323 . The capability signalling comprises of the following parameters:

- *standardDictionary-r17* indicates whether the UE supports UL data compression with SIP static dictionary as defined in TS 38.323.

- *operatorDictionary-r17* indicates whether the UE supports UL data compression with operator defined dictionary. In this release, the UE can only support one operator defined dictionary. If the UE supports operator defined dictionary, the UE shall report

*versionOfDictionary-r17* and *associatedPLMN-ID-r17* of the stored operator defined dictionary as defined in TS 38.331. This parameter is not required to be present if the UE is in VPLMN. The *associatedPLMN-ID-r17* is only associated to the operator defined dictionary which has no relationship with UE's HPLMN ID.

- *continueUDC-r17* indicates whether the UE supports continuation of uplink data compression protocol operation where the UE does not reset the buffer upon PDCP re-establishment, as specified in TS 38.323

- *supportOfBufferSize-r17* indicates which compression buffer size the UE supports as specified in TS 38.323. Value kbyte4 means the UE supports 4096 bytes for compression buffer per UDC DRB. Value kbyte8 means the UE supports 8192 bytes for compression buffer per UDC DRB. A UE that supports the uplink data compression operation shall support 2048 bytes for compression buffer per UDC DRB and support up to 2 UDC DRBs.

UE

No

No

uplinkOnlyROHC-Profiles Indicates the ROHC profile(s) that are supported in uplink-only ROHC operation by the UE. - 0x0006 ROHC TCP (RFC 6846) A UE that supports uplink-only ROHC profile(s) shall support ROHC profile 0x0000 ROHC uncompressed (RFC 5795).

UE

No

No

MAC parameters

The MAC (Medium Access Control) parameters control how user equipment (UE) coordinates with the physical layer to transmit and receive data over the air interface. They define mechanisms for resource scheduling, handling uplink grants, data prioritization, and DRX (Discontinuous Reception) cycles, enabling devices to optimize power usage and performance. By specifying how and when the UE can skip transmissions, activate secondary cells, or apply DRX operations, these parameters help tailor network behavior to diverse operational needs.

Key aspects include:

  • Uplink Resource Allocation: Determines how the UE requests, schedules, and manages uplink grants to efficiently use available spectrum.
  • DRX Configuration: Manages active and sleep cycles for reduced power consumption while maintaining acceptable latency.
  • Data Prioritization: Allows the UE to prioritize traffic from different logical channels, ensuring critical data is sent first when grants overlap.
  • Advanced SCell Activation: Enables quick activation or resumption of secondary cells for carrier aggregation or dual connectivity scenarios, boosting throughput.
  • HARQ and Feedback Options: Regulates how the UE handles retransmissions, feedback, and certain specialized modes like disabled HARQ feedback in specific scenarios.

Definitions for parameters

Per

M

FDD-TDD DIFF

FR1-FR2 DIFF

autonomousTransmission-r16 Indicates whether the UE supports autonomous transmission of the MAC PDU generated for a deprioritized configured uplink grant as specified in TS 38.321. A UE supporting this feature shall also support lch-priorityBasedPrioritization-r16.

UE

No

No

No

directMCG-SCellActivation-r16, directMCG-SCellActivation-r17 Indicates whether the UE supports direct NR MCG SCell activation, as specified in TS 38.321, upon SCell addition, upon reconfiguration with sync of the MCG, as specified in TS 38.331.

UE

No

No

Yes (Incl FR2-2 DIFF)

directMCG-SCellActivationResume-r16, directMCG-SCellActivationResume-r17 Indicates whether the UE supports direct NR MCG SCell activation, as specified in TS 38.321, upon reception of an RRCResume message, as specified in TS 38.331.

UE

No

No

Yes (Incl FR2-2 DIFF)

directSCG-SCellActivation-r16, directSCG-SCellActivation-r17 Indicates whether the UE supports direct NR SCG SCell activation, as specified in TS 38.321, upon SCell addition and upon reconfiguration with sync of the SCG, both performed via an RRCReconfiguration message received via SRB3 or contained in an RRC(Connection)Reconfiguration message received via SRB1, as specified in TS 38.331  and TS 36.331. A UE indicating support of directSCG-SCellActivation-r16 shall indicate support of EN-DC or support of NGEN-DC as specified in TS 36.331 or support of NR-DC as specified in TS 38.331.

UE

No

No

Yes (Incl FR2-2 DIFF)

directSCG-SCellActivationResume-r16, directSCG-SCellActivationResume-r17 Indicates whether the UE supports direct NR SCG SCell activation, as specified in TS 38.321: - upon reception of an RRCReconfiguration included in an RRCConnectionResume message, as specified in TS 38.331 and TS 36.331, if the UE indicates support of EN-DC or NGEN-DC, and support of resumeWithSCG-Config-r16 as specified in TS 36.331, - upon reception of an RRCReconfiguration included in an RRCResume message, as specified in TS 38.331, if the UE indicates support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331. A UE indicating support of directSCG-SCellActivationResume-r16 shall indicate support of EN-DC or NGEN-DC and support of resumeWithSCG-Config-r16 as specified in TS 36.331 [17] or indicate support of NR-DC and of resumeWithSCG-Config-r16 as specified in TS 38.331.

UE

No

No

Yes (Incl FR2-2 DIFF)

drx-Adaptation-r16, drx-Adaptation-r17 Indicates whether the UE supports DRX adaptation comprised of the following functional components: - Configured ps-Offset for the detection of DCI format 2_6 with CRC scrambling by ps-RNTI and reported MinTimeGap before the start of drx-onDurationTimer of Long DRX - Indication of UE whether or not to start drx-onDurationTimer for the next Long DRX cycle by detection of DCI format 2_6 - Configured UE wakeup or not when DCI format 2_6 is not detected at all monitoring occasions outside Active Time - Configured periodic CSI report apart from L1-RSRP (ps-TransmitOtherPeriodicCSI) when impacted by DCI format 2_6 that drx-onDurationTimer does not start for the next Long DRX cycle - Configured periodic L1-RSRP report (ps-TransmitPeriodicL1-RSRP) when impacted by DCI format 2_6 that drx-onDurationTimer does not start for the next Long DRX cycle The capability signalling includes the minimum time gap between the end of the slot of last DCI format 2_6 monitoring occasion and the beginning of the slot where the UE would start the drx-onDurationTimer of Long DRX for each SCS. The value sl1 indicates 1 slot. The value sl2 indicates 2 slots, and so on. Support of this feature is reported for licensed and unlicensed bands, respectively. When this field is reported, either of sharedSpectrumChAccess-r16 or non-SharedSpectrumChAccess-r16 shall be reported, at least.

UE

No

No

Yes (Incl FR2-2 DIFF)

enhancedSkipUplinkTxConfigured-r16 Indicates whether the UE supports skipping UL transmission for a configured uplink grant only if no data is available for transmission and no UCI is multiplexed on the corresponding PUSCH of the uplink grant as specified in TS 38.321.

UE

No

Yes

No

enhancedSkipUplinkTxDynamic-r16 Indicates whether the UE supports skipping UL transmission for an uplink grant addressed to a C-RNTI only if no data is available for transmission and no UCI is multiplexed on the corresponding PUSCH of the uplink grant as specified in TS 38.321.

UE

No

Yes

No

enhancedUuDRX-forSidelink-r17 Indicates whether UE supports sidelink related Uu-DRX mechanisms for PDCCH monitoring. This field is only applicable if the UE supports sl-TransmissionMode1-r16.

UE

No

No

No

extendedDRX-CycleInactive-r17 Indicates whether UE supports the extended DRX in RRC_INACTIVE with values of 256, 512 and 1024 radio frames as specified in TS 38.331 [9]. The UE may indicate support for extended DRX in RRC_INACTIVE only if it supports extended DRX in RRC_IDLE.

UE

No

No

No

harq-FeedbackDisabled-r17 Indicates whether the UE supports disabled HARQ feedback for downlink transmission. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17.

UE

No

No

No

intraCG-Prioritization-r17 Indicates whether the UE supports the HARQ process ID selection based on LCH priority as specified in TS 38.321. A UE supporting this feature shall also support jointPrioritizationCG-Retx-Timer-r17.

UE

No

No

No

jointPrioritizationCG-Retx-Timer-r17 Indicates whether the UE supports simultaneous configuration of LCH based prioritization and cg-RetransmissionTimer-r16 as specified in TS 38.321. A UE supporting this feature shall also support lch-priorityBasedPrioritization-r16 and configuredGrantWithReTx-r16.

UE

No

No

No

lastTransmissionUL-r17 Indicates whether the UE supports starting the drx-HARQ-RTT-TimerUL after the end of the last transmission within a bundle as specified in TS 38.321.

UE

No

No

No

lch-PriorityBasedPrioritization-r16 Indicates whether the UE supports prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority as specified in TS 38.321.

UE

No

No

No

lch-ToConfiguredGrantMapping-r16 Indicates whether the UE supports restricting data transmission from a given LCH to a configured (sub-) set of configured grant configurations (see allowedCG-List-r16 in LogicalChannelConfig in TS 38.331) as specified in TS 38.321.

UE

No

No

No

lch-ToGrantPriorityRestriction-r16 Indicates whether the UE supports restricting data transmission from a given LCH to a configured (sub-) set of dynamic grant priority levels (see allowedPHY-PriorityIndex-r16 in LogicalChannelConfig in TS 38.331) as specified in TS 38.321.

UE

No

No

No

lch-ToSCellRestriction Indicates whether the UE supports restricting data transmission from a given LCH to a configured (sub-) set of serving cells (see allowedServingCells in LogicalChannelConfig). A UE supporting pdcp-DuplicationMCG-OrSCG-DRB or pdcp-DuplicationSRB (see PDCP-Config) shall also support lch-ToSCellRestriction.

UE

No

No

No

lcp-Restriction Indicates whether UE supports the selection of logical channels for each UL grant based on RRC configured restriction using RRC parameters allowedSCS-List, maxPUSCH-Duration, and configuredGrantType1Allowed as specified in TS 38.321.

UE

No

No

No

logicalChannelSR-DelayTimer Indicates whether the UE supports the logicalChannelSR-DelayTimer as specified in TS 38.321.

UE

No

Yes

No

longDRX-Cycle Indicates whether UE supports long DRX cycle as specified in TS 38.321.

UE

Yes

Yes

No

mg-ActivationCommPRS-Meas-r17 Indicates whether UE supports preconfiguration of MGs in RRC signalling for PRS measurements and the use of DL MAC CE from the gNB, as specified in TS 38.321, to activate/deactivate the preconfigured MG for PRS measurements.

UE

No

No

No

mg-ActivationRequestPRS-Meas-r17 Indicates whether UE supports preconfiguration of MGs in RRC signalling for PRS measurements and supports the use of UL MAC CE, as specified in TS38.321, to request the activation/deactivation of the preconfigured MG for PRS measurements. The UE can include this field only if the UE supports mg-ActivationCommPRS-Meas-r17.

UE

No

No

No

multipleConfiguredGrants Indicates whether UE supports more than one configured grant configurations (including both Type 1 and Type 2) in a cell group. For each cell, the UE supports at most one configured grant per BWP and the maximum number of configured grant configurations per cell group is 2. If absent, for each configured cell group, the UE only supports one configured grant configuration on one serving cell.

UE

No

Yes

No

multipleSR-Configurations Indicates whether the UE supports 8 SR configurations per PUCCH cell group as specified in TS 38.321.

UE

No

Yes

No

recommendedBitRate Indicates whether the UE supports the bit rate recommendation message from the gNB to the UE as specified in TS 38.321.

UE

No

No

No

recommendedBitRateMultiplier-r16 Indicates whether the UE supports the bit rate multiplier for recommended bit rate MAC CE as specified in TS 38.321, clause 6.1.3.20. This field is only applicable if the UE supports recommendedBitRate.

UE

No

No

No

recommendedBitRateQuery Indicates whether the UE supports the bit rate recommendation query message from the UE to the gNB as specified in TS 38.321. This field is only applicable if the UE supports recommendedBitRate.

UE

No

No

No

secondaryDRX-Group-r16 Indicates whether UE supports secondary DRX group as specified in TS 38.321.

UE

No

Yes

No

shortDRX-Cycle Indicates whether UE supports short DRX cycle as specified in TS 38.321.

UE

Yes

Yes

No

simultaneousSR-PUSCH-DiffPUCCH-groups-r17 Indicates whether the UE supports simultaneous transmission of SR and PUSCH in different PUCCH groups as specified in TS 38.321.

UE

No

No

No

singlePHR-P-r16 Indicates whether UE supports the P bit in single PHR MAC CE as specified in TS 38.321.

UE

No

No

No

skipUplinkTxDynamic Indicates whether the UE supports skipping of UL transmission for an uplink grant indicated on PDCCH if no data is available for transmission as specified in TS 38.321.

UE

No

Yes

No

spCell-BFR-CBRA-r16 Indicates whether the UE supports sending BFR MAC CE for SpCell BFR as specified in TS 38.321.

UE

No

No

No

srs-ResourceId-Ext-r16 Indicates whether the UE supports the extended 6-bit (Positioning) SRS resource ID in SP Positioning SRS Activation/Deactivation MAC CE, as specified in TS 38.321.

UE

No

No

No

sr-TriggeredBy-TA-Report-r17 Indicates whether the UE supports triggering of SR when a TA report is triggered and there are no available UL-SCH resources. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17.

UE

No

No

No

survivalTime-r17 Indicates whether the UE supports services with survival time requirement using configured grant resource and PDCP duplication, as specified in TS 38.321. A UE supporting this feature shall support pdcp-DuplicationMCG-orSCG-DRB or pdcp-DuplicationSplitDRB. A UE supporting this feature shall also support configuredUL-GrantType1-v1650 or configuredUL-GrantType2-v1650.

UE

No

No

No

tdd-MPE-P-MPR-Reporting-r16 Indicates whether the UE supports P-MPR reporting for Maximum Permissible Exposure, as specified in TS38.321.

UE

No

TDD only

FR2 only

ul-LBT-FailureDetectionRecovery-r16 Indicates whether the UE supports consistent uplink LBT detection and recovery, as specified in TS 38.321 [8], for cells operating with shared spectrum channel access. This field applies to all serving cells with which the UE is configured with shared spectrum channel access.

UE

No

No

No

uplink-Harq-ModeB-r17 Indicates whether the UE supports HARQ Mode B and the corresponding LCP restrictions for uplink transmission. A UE supporting this feature shall also indicate the support of nonTerrestrialNetwork-r17.

UE

No

No

No

Physical layer parameters - BandCombinationList parameters

These band parameters define how user equipment (UE) manages different frequency bands, supports various carrier aggregation scenarios, and handles advanced features like DAPS handover and dynamic uplink transmission. By specifying combinations for EUTRA and NR, bandwidth classes, power classes, and sidelink coexistence, they enable the UE to operate efficiently across multiple radio technologies and frequency ranges.

Key points include:

  • Band-Level Definitions: Specify which EUTRA and NR bands the UE supports, covering downlink and uplink frequencies.
  • Carrier Aggregation Classes: Define how aggregated transmissions are configured (e.g., bandwidth classes and maximum component carriers).
  • Multi-Band Operations: Enable NE-DC, EN-DC, or NR-DC by detailing how the UE can operate simultaneously across different radio access technologies and frequency bands.
  • Advanced Features: Allow for dynamic UL Tx switching, SRS switching across bands, DAPS handover for seamless mobility, and power class constraints for maximizing transmission power.
  • Sidelink Coexistence: Indicate how PC5-based sidelink communications can run in parallel with regular cellular (Uu) uplink/downlink transmissions.

Definitions for parameters

Per

M

FDD-TDD DIFF

FR1-FR2 DIFF

bandEUTRA Defines supported EUTRA frequency band by NR frequency band number, as specified in TS 36.101.

Band

Yes

N/A

N/A

bandList Each entry of the list should include at least one bandwidth class for UL or DL.

BC

Yes

N/A

N/A

bandNR Defines supported NR frequency band by NR frequency band number, as specified in TS 38.101-1  and TS 38.101-2 .

Band

Yes

N/A

N/A

ca-BandwidthClassDL-EUTRA Defines for DL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 36.101 . When all FeatureSetEUTRA-DownlinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent.

Band

No

N/A

N/A

ca-BandwidthClassDL-NR Defines for DL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 38.101-1  and TS 38.101-2 . When all FeatureSetDownlinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent. For FR1, the value 'F' shall not be used as it is invalidated in TS 38.101-1 .

Band

No

N/A

N/A

ca-BandwidthClassUL-EUTRA Defines for UL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 36.101 . When all FeatureSetEUTRA-UplinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent.

Band

No

N/A

N/A

ca-BandwidthClassUL-NR Defines for UL, the class defined by the aggregated transmission bandwidth configuration and maximum number of component carriers supported by the UE, as specified in TS 38.101-1  and TS 38.101-2 . When all FeatureSetUplinkId:s in the corresponding FeatureSetsPerBand are zero, this field is absent. For FR1, the value 'F' shall not be used as it is invalidated in TS 38.101-1

Band

No

N/A

N/A

ca-ParametersEUTRA Contains the EUTRA part of band combination parameters for a given (NG)EN-DC/NE-DC band combination.

BC

No

N/A

N/A

ca-ParametersNR Contains the NR band combination parameters for a given (NG)EN-DC/NE-DC and/or NR CA band combination.

BC

No

N/A

N/A

ca-ParametersNRDC Indicates whether the UE supports NR-DC for the band combination. It contains the NR band combination parameters applicable across MCG and SCG. If the band combination includes both FR1 and FR2 bands, a UE indicating support for NR-DC shall support synchronous NR-DC configuration where all serving cells of the MCG are in FR1 and all serving cells of the SCG are in FR2.

BC

No

N/A

N/A

featureSetCombination Indicates the feature set that the UE supports on the NR and/or MR-DC band combination by FeatureSetCombinationId.

BC

N/A

N/A

N/A

featureSetCombinationDAPS-r16 Indicates the feature set that the UE supports for DAPS handover on the NR band combination by FeatureSetCombinationId. A UE shall include this field if intra-frequency or inter-frequency DAPS handover is supported for this band combination. For a band entry where it indicates the support for intra-frequency DAPS handover, the UE shall include at least two CCs and shall support intra-frequency DAPS handover between any CC pair within the same band entry. If the number of CCs within a band combination is more than one and if inter-frequency DAPS handover is supported, UE shall support inter-frequency DAPS handover between every CC pair in the same or different band entries in the band combination, except for the CC pair within a band entry with bandwidth class A. A feature set including intraFreqDAPS-r16 can only be referred to by featureSetCombinationDAPS-r16, not by featureSetCombination. A feature set without intraFreqDAPS-r16 is only applied to inter-freq DAPS handover if it is referred to by featureSetCombinationDAPS. Both feature sets with and without intraFreqDAPS-r16 can be referred to by the same featureSetCombinationDAPS-r16.

BC

N/A

N/A

N/A

intrabandConcurrentOperationPowerClass-r16 Indicates the power class, of a particular Uu band combination and the intra-band PC5 band combination(s) on which the UE supports transmission of PC5 simultaneous with Uu uplink (as indicated by supportedTxBandCombListPerBC-Sidelink-r16). The leading/leftmost value corresponds to the band combination of the particular Uu band combination and the first intra-band PC5 band combination included in BandCombinationListSidelinkEUTRA-NR which is indicated with value 1 by supportedTxBandCombListPerBC-Sidelink-r16, the next value corresponds to the band combination of the particular Uu band combination and the second intra-band PC5 band combination included in BandCombinationListSidelinkEUTRA-NR, and so on. If this power class is higher than the power class that the UE supports on the individual Uu or PC5 interface of this band combination, the latter determines maximum TX power available in each interface.

BC

No

N/A

N/A

mrdc-Parameters Contains the band combination parameters for a given (NG)EN-DC/NE-DC band combination.

BC

No

N/A

N/A

ne-DC-BC Indicates whether the UE supports NE-DC for the band combination.

BC

No

N/A

N/A

powerClass, powerClass-v1610 Indicates power class the UE supports when operating according to this band combination. If the field is absent, the UE supports the default power class. If this power class is higher than the power class that the UE supports on the individual bands of this band combination (ue-PowerClass in BandNR), the latter determines maximum TX power available in each band. The UE sets the power class parameter only in band combinations that are applicable as specified in TS 38.101-1 and TS 38.101-3 . This capability is not applicable to IAB-MT.

BC

No

N/A

FR1 only

powerClassNRPart-r16 Indicates NR part power class the UE supports when operating according to this band combination. This field only applies for MR-DC BCs containing only single CC or intra-band CA in NR side in this release.

BC

No

N/A

FR1 only

scalingFactorTxSidelink-r16, scalingFactorRxSidelink-r16 Indicates, for a particular Uu band combination, the scaling factor for the PC5 band combination(s) on which the UE supports transmission/reception of PC5 simultaneous with Uu uplink/downlink respectively (as indicated by supportedTxBandCombListPerBC-Sidelink-r16 / supportedRxBandCombListPerBC-Sidelink-r16). The leading / leftmost value corresponds to the first band combination included in BandCombinationListSidelinkEUTRA-NR which is indicated with value 1 by supportedTxBandCombListPerBC-Sidelink-r16 / supportedRxBandCombListPerBC-Sidelink-r16, the next value to the second band combination, and so on. For each value of ScalingFactorSidelink-r16, value f0p4 indicates the scaling factor 0.4, f0p75 indicates 0.75, and so on.

BC

No

N/A

N/A

srs-SwitchingAffectedBandsListNR-r17 Indicates which other bands in the band combination are affected by the SRS switch and the dropping rules / timelines apply to the indicated bands when SRS carrier switching on target CC and other UL on source CC are overlapped in the same symbol. UE indicating support of this feature shall indicate support of srs-CarrierSwitch.

BC

No

N/A

N/A

SRS-SwitchingTimeNR Indicates the interruption time on DL/UL reception within a NR band pair during the RF retuning for switching between a carrier on one band and another (PUSCH-less) carrier on the other band to transmit SRS. switchingTimeDL/switchingTimeUL: n0us represents 0 us, n30us represents 30us, and so on. switchingTimeDL/switchingTimeUL is mandatory present if switching between the NR band pair is supported, otherwise absent. It is signalled per pair of bands per band combination.

FD

No

N/A

N/A

SRS-SwitchingTimeEUTRA Indicates the interruption time on DL/UL reception within an EUTRA band pair during the RF retuning for switching between a carrier on one band and another (PUSCH-less) carrier on the other band to transmit SRS. switchingTimeDL/switchingTimeUL: n0 represents 0 OFDM symbols, n0dot5 represents 0.5 OFDM symbols, n1 represents 1 OFDM symbol and so on. switchingTimeDL/switchingTimeUL is mandatory present if switching between the EUTRA band pair is supported, otherwise absent. It is signalled per pair of bands per band combination.

FD

No

N/A

N/A

srs-TxSwitch, srs-TxSwitch-v1610 Defines whether UE supports SRS for DL CSI acquisition as defined in clause 6.2.1.2 of TS 38.214. The capability signalling comprises of the following parameters: - supportedSRS-TxPortSwitch indicates SRS Tx port switching pattern supported by the UE, which is mandatory with capability signalling. - supportedSRS-TxPortSwitch-v1610, which is optional to report, indicates downgrading configuration of SRS Tx port switching pattern. - txSwitchImpactToRx indicates the lowest band entry number of the UL group that impacts the DL of this band entry. - txSwitchWithAnotherBand indicates the lowest band entry of the UL group that impacts each other’s UL. The UE may include txSwitchImpactToRx and txSwitchWithAnotherBand even if supportedSRS-TxPortSwitch is set to 'notSupported' for that band entry.

BC / FD

No

N/A

N/A

srs-AntennaSwitchingBeyond4RX-r17 Indicates whether the UE supports SRS Antenna switching for more than 4 Rx. The capability signalling comprises the following parameters: - supportedSRS-TxPortSwitchBeyond4Rx-r17 indicates a combination of supported xTyRs via an 11-bit bitmap. - entryNumberAffectBeyond4Rx-r17 indicates the entry number of the first-listed band with UL in the band combination that affects this DL. - entryNumberSwitchBeyond4Rx-r17 indicates the entry number of the first-listed band with UL in the band combination that switches together with this UL. The UE indicating support of this shall indicate support of srs-TxSwitch.

BC

No

N/A

N/A

supportedBandwidthCombinationSet Defines the supported bandwidth combination set for a band combination as defined in TS 38.101-1, TS 38.101-2 and TS 38.101-3. It is mandatory if the band combination has more than one NR carrier or is an intra-band (NG)EN-DC/NE-DC combination without additional inter-band NR and LTE CA component, or both. The corresponding bits of Bandwidth Combination Set 4 and Bandwidth Combination Set 5 shall not both be set to "1" for the same band combination.

BC

CY

N/A

N/A

supportedBandwidthCombinationSetIntraENDC Defines the supported bandwidth combination set for a band combination that allows configuration of at least one EUTRA serving cell and at least one NR serving cell in the same band, as defined in TS 38.101-3 . It is encoded as a bit map, where bit N is set to "1" if UE supports Bandwidth Combination Set N for this band combination. It is mandatory if the band combination is an intra-band (NG)EN-DC/NE-DC combination supporting both UL and DL intra-band (NG)EN-DC/NE-DC parts with additional inter-band NR/LTE CA component, and optional otherwise.

BC

CY

N/A

N/A

supportedTxBandCombListPerBC-Sidelink-r16, supportedRxBandCombListPerBC-Sidelink-r16 Indicates, for a particular Uu band combination, the PC5 band combination(s) on which the UE supports transmission/reception of PC5 simultaneously with Uu uplink/downlink respectively. The leading / leftmost bit (bit 0) corresponds to the first band combination included in BandCombinationListSidelinkEUTRA-NR, the next bit to the second band combination, and so on. Value 1 indicates simultaneous transmission/reception is supported.

BC

No

N/A

N/A

supportedBandCombListPerBC-SL-RelayDiscovery-r17, supportedBandCombListPerBC-SL-NonRelayDiscovery-r17 Indicates, for a particular Uu band combination, the PC5 Relay discovery and non-Relay discovery band combination(s) on which the UE supports simultaneous transmission/reception of PC5 data (Relay discovery or non-Relay discovery) and Uu uplink/downlink respectively. The leading / leftmost bit (bit 0) corresponds to the first band combination included in supportedBandCombinationListSL-RelayDiscovery-r17 / supportedBandCombinationListSL-NonRelayDiscovery-r17, the next bit to the second band combination, and so on. Value 1 indicates simultaneous transmission/reception is supported.

BC

No

N/A

N/A

ULTxSwitchingBandPair-r16, ULTxSwitchingBandPair-v1700 Indicates UE supports dynamic UL 1Tx-2Tx switching in case of inter-band CA, SUL, and (NG)EN-DC, and UL 2Tx-2Tx switching in case of inter-band CA and SUL as defined in TS 38.214 , TS 38.101-1  and TS 38.101-3 . The capability signalling comprises: - bandIndexUL1-r16 and bandIndexUL2-r16 indicate the band pair on which UE supports dynamic UL Tx switching. - uplinkTxSwitchingPeriod-r16 indicates the length of UL Tx switching period of 1Tx-2Tx switching. - uplinkTxSwitchingPeriod2T2T-r17 indicates the length of UL Tx switching period of 2Tx-2Tx switching. - uplinkTxSwitching-DL-Interruption-r16 indicates that DL interruption on the band will occur during UL Tx switching.

BC

FD

N/A

FR1 only

uplinkTxSwitching-OptionSupport-r16 Indicates which option is supported for dynamic UL 1Tx-2Tx switching for inter-band UL CA and (NG)EN-DC. switchedUL represents option 1, dualUL represents option 2, both represents both option 1 and 2. The field is mandatory for inter-band UL CA and (NG)EN-DC case where UE supports dynamic UL 1Tx-2Tx switching. UE shall not report the value both for (NG)EN-DC case.

BC

CY

N/A

FR1 only

uplinkTxSwitching-OptionSupport2T2T-r17 Indicates which option is supported for dynamic UL 2Tx-2Tx switching for inter-band UL CA. switchedUL represents option 1, dualUL represents option 2, both represents both option 1 and 2. The field is mandatory for inter-band UL CA cases where UE supports dynamic UL 2Tx-2Tx switching. The UE indicating support of this feature shall indicate support of at least one common switching option between uplinkTxSwitching-OptionSupport2T2T-r17 and uplinkTxSwitching-OptionSupport-r16.

BC

CY

N/A

FR1 only

uplinkTxSwitching-PowerBoosting-r16 Indicates the support of 3dB boosting on the maximum output power for UE transmission under the operation state in which 2-port transmission can be supported on carrier2 in case of inter-band UL CA case where UE supports dynamic UL Tx switching. A UE shall only indicate this capability in case the UE supports power class 3 for inter-band UL CA for the band combination as defined in TS 38.101-1.

BC

No

N/A

FR1 only

UplinkTxSwitchingBandParameters-v1700 Contains the UL Tx switching specific band parameters for a given band combination. - bandIndex-r17 indicates a band on which UE supports dynamic UL Tx switching with another band in the band combination. - uplinkTxSwitching2T2T-PUSCH-TransCoherence-r17 indicates support of the uplink codebook subset for the carrier(s) on a band capable of two antenna connectors on which UE supports dynamic UL 2Tx-2Tx switching. If absent, the per BC UE capability reported in uplinkTxSwitching-PUSCH-TransCoherence-r16 is applied, and if both fields are absent, the UE capability in pusch-TransCoherence is applied.

BC

No

N/A

FR1 only

uplinkTxSwitching-PUSCH-TransCoherence-r16 Indicates support of the uplink codebook subset when uplink 1Tx-2Tx switching is triggered between last transmitted SRS and scheduled PUSCH transmission, as specified in TS 38.101-1. A UE indicating support of full coherent codebook subset shall also support non-coherent codebook subset. If this field is absent, the supported uplink codebook subset indicated by pusch-TransCoherence applies when the uplink switching is triggered between last transmitted SRS and scheduled transmission.

BC

No

N/A

FR1 only

Physical layer parameters - BandNR parameters

The BandNR parameters describe how a 5G NR UE declares its radio capabilities for specific NR bands. This information covers the frequency ranges (FR1 and FR2), duplex modes (FDD, TDD, and, if applicable, supplementary uplink or downlink), maximum supported bandwidths, subcarrier spacings, and MIMO layers per band. The UE signals which bands it supports, the maximum channel bandwidth available in each band, and key features such as partial bandwidth usage or SRS (Sounding Reference Signal) beam management. The specification also details advanced capabilities, including multi-TRP or multiple antenna panel support, beamforming techniques, and timing advance enhancements that address large delays in non-terrestrial network or mmWave scenarios. Overall, the BandNR parameters allow a network to understand the scope of a UE’s band-specific constraints, enabling optimized scheduling, carrier aggregation, and beam management according to each device’s physical-layer capabilities.

Below is a concise overview of the BandNR-related Physical layer parameters for 5G NR UE capabilities

BandNR Basics

  • Band Identifiers (n#)
    • NR bands are labeled as “nXX” (e.g., n1, n78, n257).
    • Each band identifies a specific frequency range and duplex arrangement (FDD, TDD, SDL, SUL).
  • Frequency Ranges
    • FR1: ~410 MHz to 7.125 GHz
    • FR2: ~24.25 GHz to 52.6 GHz
  • Duplex Modes
    • FDD (Frequency Division Duplex): Separate UL and DL carriers.
    • TDD (Time Division Duplex): UL/DL share the same frequency but separated in time.
    • SUL/SDL (Supplementary Uplink/Downlink): Additional carriers used in parallel with primary UL/DL.

Band-Specific Capability Signaling

  • Supported Band Combinations
    • UE signals each band (e.g., n1, n3, n78) it can operate on and whether it supports CA (Carrier Aggregation) across multiple bands.
    • Indicates maximum aggregated bandwidth, number of component carriers, and possible MIMO layers per band or per combination.
  • Max Supported Bandwidth per Band
    • UE capability indicates the maximum RB (resource block) configuration or maximum channel bandwidth within each NR band.
  • Supported Subcarrier Spacings
    • For FR1: Typically 15 kHz, 30 kHz, (and possibly 60 kHz in certain higher sub-bands).
    • For FR2: Typically 60 kHz, 120 kHz (some UEs may also support 240 kHz in certain scenarios).
  • Maximum Transmission / Reception Layers
    • Specifies how many MIMO layers a UE can handle for DL (e.g., 2-layer, 4-layer, 8-layer) and UL (typically fewer).

Selected Physical Layer/Radio RF Parameters

  • Channel Bandwidth Sets
    • 5G NR channel bandwidths differ by band and subcarrier spacing.
    • For instance, FR1 might see maximum channel bandwidths of 50 MHz, 100 MHz, etc., depending on the band. FR2 can go up to 400 MHz or more.
  • Power Classes
    • For FR1: Commonly “PC3” (standard device) or “PC2” (higher power).
    • For FR2: Definitions exist for various power classes (e.g., PC1, PC2, PC6 for certain mmWave or RedCap scenarios).
  • Tx/Rx Antenna Configuration
    • UE indicates how many Rx/Tx antennas it supports.
    • Impacts maximum possible rank or MIMO layers.
  • Supported Modulations
    • Up to 256QAM in DL (FR1), 64QAM or 256QAM in UL (depending on band).
    • FR2 UEs often indicate whether 256QAM is supported (less common).
  • SRS (Sounding Reference Signal) / Beam Management
    • Per-band info on how many SRS resources can be configured, partial frequency sounding, or beam-based SRS transmissions in FR2.
    • Some advanced beam management parameters are signaled if the UE supports wideband or multiple-beam operations.

Advanced Feature Sup

  • Multiple Panel Support / Multi-TRP
    • If the UE supports advanced multi-TRP (transmission-reception-point) or multi-panel MIMO, it signals so in the band-specific capability.
  • Rate Matching & Legacy CRS
    • Some UEs indicate capabilities for rate-matching around LTE CRS in certain dynamic spectrum sharing deployments.
  • Partial Frequency / Bandwidth Configurations
    • UEs can support partial bandwidth usage, sub-band scheduling, or partial frequency sounding (especially relevant in FR1 for large bandwidths).
  • Timing & TA (Timing Advance) Enhancements
    • For NTN (Non-Terrestrial Networks) or advanced FR2 scenarios, UEs can indicate special timing offset or pre-compensation support to handle large delays.
Definitions for parameters

Per

M

FDD-TDD DIFF

FR1-FR2 DIFF

ack-NACK-FeedbackForMulticastWithDCI-Enable-r17 Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK-based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2. A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17.

Band

No

N/A

N/A

ack-NACK-FeedbackForSPS-MulticastWithDCI-Enable-r17 Indicates whether the UE supports DCI-based enabling/disabling ACK/NACK-based HARQ-ACK feedback configured per G-CS-RNTI for multicast by RRC signalling via DCI format 4_2. A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17.

Band

No

N/A

N/A

activeConfiguredGrant-r16 Indicates whether the UE supports up to 12 configured/active configured grant configurations in a BWP of a serving cell. This field includes: - maxNumberConfigsPerBWP-r16 for the maximum number of configured/active grants in a BWP; - maxNumberConfigsAllCC-r16 for the maximum number of configured/active grants across all serving cells in a MAC entity, and across MCG and SCG in NR-DC. UE can include this feature only if it supports either configuredUL-GrantType1/configuredUL-GrantType1-v1650 and/or configuredUL-GrantType2/configuredUL-GrantType2-v1650. NOTE:
  • For all reported FR1 bands, the same X1 value is reported for maxNumberConfigsAllCC-r16. For all reported FR2 bands, the same X2 value is reported.
  • The total number of configured/active grants across FR1 cells ≤ X1, across FR2 cells ≤ X2.
  • If CA includes some cells in FR1 and some in FR2, the total across all cells is ≤ max(X1, X2).

Band

No

N/A

N/A

additionalActiveTCI-StatePDCCH Indicates whether the UE supports one additional active TCI-State for control in addition to the supported number of active TCI-States for PDSCH. The UE can include this field only if maxNumberActiveTCI-PerBWP in tci-StatePDSCH is set to n1. Otherwise, the UE does not include this field.

Band

No

N/A

N/A

*aperiodicBeamReport Indicates whether the UE supports aperiodic 'CRI/RSRP' or 'SSBRI/RSRP' reporting on PUSCH. The UE provides the capability for the band number for which the report is provided (where the measurement is performed).

Band

Yes

N/A

N/A

aperiodicCSI-RS-AdditionalBandwidth-r17 Indicates the UE supported TRS bandwidths for fast SCell activation, in addition to 52 RBs, for a 10MHz UE channel bandwidth. This is applicable for FDD-only, FR1-only with 15kHz SCS, and indicates values addBW-Set1 or addBW-Set2. UE can include this feature only if it supports aperiodicCSI-RS-FastScellActivation-r17.

Band

No

FDD only

FR1 only

aperiodicCSI-RS-FastScellActivation-r17 Indicates whether the UE supports aperiodic CSI-RS for tracking for fast SCell activation. This field includes: - maxNumberAperiodicCSI-RS-PerCC-r17 for the maximum number of aperiodic CSI-RS resource set configs per CC; - maxNumberAperiodicCSI-RS-AcrossCCs-r17 for the maximum number of aperiodic CSI-RS resource set configs across CCs. NOTE: The NZP-CSI-RS for tracking fast SCell activation are not counted toward the max NZP-CSI-RS for CSI feedback.

Band

No

N/A

N/A

aperiodicTRS Indicates whether the UE supports DCI triggering aperiodic TRS associated with periodic TRS. This is applicable in FR2 only.

Band

No

N/A

Yes

asymmetricBandwidthCombinationSet Defines the supported asymmetric channel bandwidth combination for the band as defined in TS 38.101-1 [2]. If absent, the UE supports the default asymmetric set 0.

Band

No

N/A

N/A

bandNR Defines supported NR frequency band by NR band number, as specified in TS 38.101-1 [2], TS 38.101-2 [3], and TS 38.101-5 [34].

Band

Yes

N/A

N/A

beamCorrespondenceCSI-RS-based-r16 Indicates whether the UE support for beam correspondence based on CSI-RS allows selecting its UL beam based on CSI-RS measurement. TDD only, FR2 only. If UE supports beam correspondence CSI-RS-based, the network can expect UE to fulfill Rel-15 beam correspondence requirements. If UE supports neither beamCorrespondenceSSB-based-r16 nor beamCorrespondenceCSI-RS-based-r16, the gNB can expect the UE to fulfill beam correspondence based on Rel-15 beam requirements.

Band

No

TDD only

FR2 only

*beamCorrespondenceSSB-based-r16 Indicates whether the UE support for beam correspondence based on SSB allows selecting its UL beam based on SSB measurement. TDD only, FR2 only. If UE supports neither beamCorrespondenceSSB-based-r16 nor beamCorrespondenceCSI-RS-based-r16, the gNB can expect the UE to fulfill beam correspondence based on Rel-15 beam requirements.

Band

No

TDD only

FR2 only

beamCorrespondenceWithoutUL-BeamSweeping Indicates how UE supports FR2 beam correspondence without UL beam sweeping, as specified in TS 38.101-2 [3], clause 6.6. The UE fulfilling beam correspondence requirement without UL beam sweeping shall set the field to supported. The UE fulfilling beam correspondence with UL beam sweeping shall not report this field.

Band

Yes

N/A

FR2 only

beamManagementSSB-CSI-RS Defines support of SS/PBCH and CSI-RS based RSRP measurements. The capability comprises: - maxNumberSSB-CSI-RS-ResourceOneTx = max total number of one-port NZP CSI-RS + SS/PBCH blocks for L1-RSRP across all cells in a slot; - maxNumberCSI-RS-Resource = max total number of NZP-CSI-RS for L1-RSRP across all cells; - maxNumberCSI-RS-ResourceTwoTx = max total of two-port NZP CSI-RS for L1-RSRP in a slot across all cells; - supportedCSI-RS-Density indicates density one-RE-per-PRB if supported. - maxNumberAperiodicCSI-RS-Resource = max aperiodic CSI-RS across all serving cells. NOTE: On FR2, UE must report ≥8 for oneTx. On FR1, also mandated to report ≥8 for oneTx.

Band

Yes

N/A

FD

beamReportTiming, beamReportTiming-v1710 Indicates the number of OFDM symbols between the end of the last symbol of SSB/CSI-RS and the first symbol of the channel containing the beam report. UE includes this per supported SCS. (Applicable to FR1/FR2 if reported = Yes/N/A).

Band

Yes

N/A

N/A

beamSwitchTiming, beamSwitchTiming-v1710 Indicates the minimum OFDM symbols (sym224, sym336, etc.) between DCI triggering of aperiodic CSI-RS and aperiodic CSI-RS transmission. FR2 only. enableBeamSwitchTiming-r16 triggers the beam switch time of sym48 for certain CSI-RS configurations. For CSI-RS without repetition and no trs-info, UE applies sym48 if beamSwitchTiming-r16 is reported and enableBeamSwitchTiming-r16 is configured.

Band

No

N/A

FR2 only

bfd-Relaxation-r17 Indicates whether the UE supports BFD relaxation criteria and requirement as specified in TS 38.133 [5]. UE sets the capability consistently for all FDD-FR1, TDD-FR1, TDD-FR2-1, TDD-FR2-2 bands. A UE indicating support of this feature shall also indicate maxNumberCSI-RS-BFD, maxNumberSSB-BFD, and maxNumberCSI-RS-SSB-CBD.

Band

No

N/A

N/A

bwp-DiffNumerology Indicates whether the UE supports BWP adaptation up to 4 BWPs with different numerologies, via DCI and timer. Except SUL, UE only supports same numerology for active UL/DL BWP. For non-RedCap UE, the DL BWP includes CORESET#0 and SSB for PCell/PSCell; for RedCap UE, DL BWP might not include CORESET#0/SSB for PCell.

Band

No

N/A

N/A

bwp-SameNumerology Indicates whether UE supports BWP adaptation (up to 2 or 4 BWPs) with the same numerology, via DCI/timer. Except SUL, UE only supports same numerology for active UL/DL BWP. Non-RedCap UE includes CORESET#0/SSB in DL BWP for PCell/PSCell if present; RedCap UE BWP may exclude CORESET#0/SSB for PCell. For SCell(s), BWP includes SSB if SCell has SSB.

Band

No

N/A

N/A

bwp-WithoutRestriction Indicates support of BWP operation without bandwidth restriction. This means for PCell/PSCell, the DL BWP may not include CORESET#0/SSB. For SCell(s), the BWP may not include SSB.

Band

No

N/A

N/A

cancelOverlappingPUSCH-r16 Indicates whether UE supports cancellation of (repetition of the) PUSCH transmissions on all other intra-band serving cells. If UE supports this, UE also reports pa-PhaseDiscontinuityImpacts and ul-CancellationSelfCarrier-r16.

Band

No

N/A

N/A

cg-SDT-r17 Indicates whether the UE supports transmission of data/signalling over allowed radio bearers in RRC_INACTIVE via configured grant type 1 (CG-SDT). UE sets this capability consistently for all FDD-FR1, TDD-FR1, TDD-FR2 bands. For NTN, set consistently for all FDD-FR1 NTN bands. UE supporting multiple CG-SDT configurations if also indicates activeConfiguredGrant-r16. Otherwise, only one CG-SDT configuration.

Band

No

N/A

N/A

channelBWs-DL Indicates for each SCS the UE-supported DL channel bandwidths. If absent for a band/SCS, it implies support of standard bandwidths from [5...100MHz] or [50,100,200MHz] depending on FR1/FR2. This is valid for FR1/FR2-1 unless otherwise stated. For IAB-MT, 100MHz or 200MHz checks use channelBW-DL-IAB-r16.

Band

Yes

N/A

N/A

channelBWs-DL-SCS-120kHz-FR2-2-r17 (CY) Indicates UE-supported DL channel bandwidths for SCS 120kHz in FR2-2. The bits map to 100 and 400MHz. Both must be set to 1 if UE supports 120kHz SCS. UE supporting this must also indicate dl-FR2-2-SCS-120kHz-r17.

Band

CY

N/A

N/A

channelBWs-DL-SCS-480kHz-FR2-2-r17 (CY) Indicates UE-supported DL channel bandwidths for SCS 480kHz in FR2-2. The bits map to 400, 800, 1600MHz. 400MHz is mandatory if supporting 480kHz SCS. UE must also indicate dl-FR2-2-SCS-480kHz-r17.

Band

CY

N/A

N/A

channelBWs-DL-SCS-960kHz-FR2-2-r17 (CY) Indicates UE-supported DL channel bandwidths for SCS 960kHz in FR2-2. Bits map to 400, 800, 1600, 2000MHz. 400MHz is mandatory if UE supports 960kHz SCS. Must also indicate dl-FR2-2-SCS-960kHz-r17.

Band

CY

N/A

N/A

channelBWs-UL Indicates for each SCS the UE-supported UL channel bandwidths. Absence means UE supports standard bandwidth sets in FR1/FR2. This is valid only for FR1/FR2-1 unless otherwise stated. For IAB-MT, 100MHz or 200MHz checks use channelBW-UL-IAB-r16.

Band

Yes

N/A

N/A

channelBWs-UL-SCS-120kHz-FR2-2-r17 (CY) Indicates UE-supported UL bandwidths for SCS 120kHz in FR2-2. Bits map 100, 400MHz. Both are mandatory if UE supports 120kHz SCS. Must indicate ul-FR2-2-SCS-120kHz-r17.

Band

CY

N/A

N/A

channelBWs-UL-SCS-480kHz-FR2-2-r17 (CY) Indicates UE-supported UL bandwidths for SCS 480kHz in FR2-2. Bits map 400, 800, 1600MHz. 400MHz is mandatory if supporting 480kHz SCS. Must also indicate ul-FR2-2-SCS-480kHz-r17.

Band

CY

N/A

N/A

channelBWs-UL-SCS-960kHz-FR2-2-r17 (CY) Indicates UE-supported UL bandwidths for SCS 960kHz in FR2-2. Bits map 400, 800, 1600, 2000MHz. 400MHz is mandatory if UE supports 960kHz SCS. Must also indicate ul-FR2-2-SCS-960kHz-r17.

Band

CY

N/A

N/A

**channelBW-DL-IAB-r16 Indicates whether the IAB-MT supports 100MHz in FR1 DL or 200MHz in FR2 DL for a given SCS.

Band

No

N/A

N/A

**channelBW-UL-IAB-r16 Indicates whether the IAB-MT supports 100MHz in FR1 UL or 200MHz in FR2 UL for a given SCS.

Band

No

N/A

N/A

codebookComboParametersAddition-r16 Indicates the UE supports mixed codebook combinations and corresponding parameters. For mixed codebooks, UE can report active CSI-RS resources/ports for up to 4 mixed combinations in any slot. Specific codebook sets (type1 single panel, type2, eType2, etc.) are listed. Usage of multiple codebooks in a slot is only within supported sets.

Band

No

N/A

N/A

codebookParameters (FD) Indicates codebooks and corresponding parameters the UE supports. Includes type I single panel, type I multi-panel, type II codebooks with or without port selection. Each codebook type may define supportedCSI-RS-ResourceList, maxNumberTxPortsPerResource, etc. Usage of multiple codebooks simultaneously must adhere to these parameters.

Band

FD

N/A

N/A

codebookParametersAddition-r16 Indicates UE support of additional codebooks (e.g., eType2 R=1 or R=2) and corresponding parameters. UE can declare support of etype2R1-r16, etype2R2-r16, possibly with rank3-4. Codebook usage for advanced rank/port selection combos is included.

Band

No

N/A

N/A

codebookParametersfeType2-r17 Indicates UE support of Further Enhanced Port-Selection Type II Codebook (FeType-II) as in TS 38.214 [12], clause 5.2.2.2.7. UE including this field shall also include fetype2basic-r17 for basic FeType-II features. May include fetype2R1-r17, fetype2R2-r17, fetype2Rank3Rank4-r17. Codebook usage restricted to maxNumberTxPorts≥4, etc.

Band

No

N/A

N/A

codebookComboParameterMixedType-r17 Indicates the support of active CSI-RS resources and ports for mixed codebook types in any slot. UE can report up to 4 mixed codebook combinations in any slot, e.g. {Type 1 Single Panel + FeType II + port selection, etc.}. For each mixed codebook supported by the UE, supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources by referring to codebookVariantsList. - maxNumberTxPortsPerResource (with minimum 'p4') - maxNumberResourcesPerBand - totalNumberTxPortsPerBand (minimum 4) The UE supporting this feature shall indicate support of fetype2basic-r17, etype2R1-r16, codebookComboParametersAddition-r16, and so on.

Band

No

N/A

N/A

codebookComboParameterMultiTRP-r17 Indicates support of active CSI-RS resources and ports in the presence of multi-TRP CSI. The UE can report supported active CSI-RS resources and ports for up to 4 mixed codebook combinations. Several possible mixed codebook combos for NCJT (non-coherent joint transmission), eType2, etc. are listed (e.g. {NCJT + Type2 + Null}, {NCJT + eType2R1 + port selection + Null}, etc.). For each mixed codebook, supportedCSI-RS-ResourceListAdd-r16 indicates the list of supported CSI-RS resources by referring to codebookVariantsList. - maxNumberTxPortsPerResource is at least 'p4' - maxNumberResourcesPerBand - totalNumberTxPortsPerBand is at least 4 Note 1: A CMR pair for NCJT is counted as two activated resources; a CMR for sTRP is one resource. Note 2: This is relevant only when UE is configured with NCJT CSI in ≥1 CSI report setting. A UE indicating support of this feature shall also indicate mTRP-CSI-EnhancementPerBand-r17.

Band

No

N/A

N/A

condHandover-r16 Indicates whether the UE supports conditional handover (CHO) including up to 8 candidate cells. Except for NTN bands, the UE sets this capability consistently for all FDD-FR1, TDD-FR1, TDD-FR2-1, and TDD-FR2-2 bands respectively. For NTN, the UE sets capability for all FDD-FR1 NTN bands.

Band

No

N/A

N/A

condHandoverFailure-r16 Indicates whether the UE supports conditional HO during re-establishment if the selected cell is configured as candidate cell for CHO. Except NTN bands, UE sets the capability consistently for FDD-FR1/TDD-FR1/TDD-FR2-1/2. For NTN, similarly for FDD-FR1 NTN.

Band

No

N/A

N/A

condHandoverTwoTriggerEvents-r16 Indicates whether the UE supports two trigger events for the same execution condition in CHO. Mandatory if UE supports condHandover-r16. Except NTN, UE sets consistently for all bands, likewise for NTN.

Band

CY

N/A

N/A

condPSCellChange-r16 Indicates whether the UE supports conditional PSCell change with up to 8 candidate cells. UE sets capability consistently for all bands.

Band

No

N/A

N/A

condPSCellChangeTwoTriggerEvents-r16 Indicates UE supports 2 trigger events for the same execution condition for conditional PSCell change. Mandatory if UE supports condPSCellChange-r16.

Band

CY

N/A

N/A

configuredUL-GrantType1-v1650 Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant, UL-TWG-repK=1, for non-shared spectrum only. For shared spectrum, configuredUL-GrantType1-r16 applies. UE sets capability consistently for all bands. This field is included only if configuredUL-GrantType1 is absent.

Band

No

N/A

N/A

configuredUL-GrantType2-v1650 Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant, UL-TWG-repK=1, for non-shared spectrum only. For shared spectrum, configuredUL-GrantType2-r16 applies. UE sets capability consistently for all bands. This field is included only if configuredUL-GrantType2 is absent.

Band

No

N/A

N/A

cqi-4-BitsSubbandNTN-SharedSpectrumChAccess-r17 Indicates whether the UE supports CQI reporting with 4 bits per subband for NTN and shared spectrum channel access.

Band

No

N/A

N/A

crossCarrierScheduling-SameSCS Indicates whether UE supports cross-carrier scheduling for same numerology with CIF in carrier aggregation (where scheduling cell and scheduled cell share the same numerology).

Band

No

N/A

N/A

csi-ReportFramework Indicates whether the UE supports CSI report framework. This capability includes parameters: - maxNumberPeriodicCSI-PerBWP-ForCSI-Report, maxNumberPeriodicCSI-PerBWP-ForBeamReport, maxNumberAperiodicCSI-PerBWP-ForCSI-Report, maxNumberAperiodicCSI-PerBWP-ForBeamReport - maxNumberAperiodicCSI-triggeringStatePerCC - maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report and ...ForBeamReport - simultaneousCSI-ReportsPerCC UE is mandated to report csi-ReportFramework.

Band

Yes

N/A

N/A

csi-ReportFrameworkExt-r16 Indicates UE supports extension of max number of aperiodic CSI reports for all codebook types. If present, extended values replace those in csi-ReportFramework.

Band

No

N/A

N/A

csi-RS-ForTracking Indicates support of CSI-RS for tracking (TRS). Capability includes: maxBurstLength=2 (1 or 2 slots), maxSimultaneousResourceSetsPerCC, maxConfiguredResourceSetsPerCC≥8(Fr1)/16(Fr2), and maxConfiguredResourceSetsAllCC≥16(Fr1)/32(Fr2). UE must also report csi-RS-ForTracking.

Band

Yes

N/A

N/A

csi-RS-IM-ReceptionForFeedback Indicates support of CSI-RS and CSI-IM reception for CSI feedback. Includes parameters for NZP-CSI-RS and CSI-IM: maxConfigNumberNZP-CSI-RS-PerCC, maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC, maxConfigNumberCSI-IM-PerCC, maxNumberSimultaneousNZP-CSI-RS-PerCC, totalNumberPortsSimultaneousNZP-CSI-RS-PerCC. UE is mandated to report csi-RS-IM-ReceptionForFeedback.

Band

Yes

N/A

N/A

csi-RS-ProcFrameworkForSRS Indicates support of CSI-RS processing framework for SRS. Includes: - maxNumberPeriodicSRS-AssocCSI-RS-PerBWP, maxNumberAperiodicSRS-AssocCSI-RS-PerBWP, maxNumberSP-SRS-AssocCSI-RS-PerBWP - simultaneousSRS-AssocCSI-RS-PerCC

Band

No

N/A

FR2 only

defaultQCL-PerCORESETPoolIndex-r16 Indicates whether the UE supports default QCL assumption per CORESET pool index for multi-DCI-based multi-TRP in FR2. UE indicating this also supports multiDCI-MultiTRP-r16 and simultaneousReceptionDiffTypeD-r16.

Band

No

N/A

FR2 only

defaultQCL-TwoTCI-r16 Indicates whether the UE supports default QCL assumption with two TCI states using single-DCI-based multi-TRP in FR2. UE includes this only if simultaneousReceptionDiffTypeD-r16 is present.

Band

No

N/A

FR2 only

dmrs-BundlingNonBackToBackTX-r17 Indicates whether UE supports DM-RS bundling for non-back-to-back transmissions for consecutive slots on PUSCH/PUCCH, only for corresponding back-to-back transmission as previously reported. UE must also indicate at least one of dmrs-BundlingPUSCH-RepTypeA-r17, dmrs-BundlingPUSCH-RepTypeB-r17, dmrs-BundlingPUSCH-multiSlot-r17, or dmrs-BundlingPUCCH-Rep-r17.

Band

No

N/A

N/A

dmrs-BundlingPUCCH-Rep-r17 Indicates whether the UE supports DM-RS bundling for PUCCH repetitions (formats 1/3/4) over consecutive symbols. If UE indicates support, it must also support maxDurationDMRS-Bundling-r17 and pucch-Repetition-F1-3-4.

Band

No

N/A

N/A

dmrs-BundlingPUSCH-multiSlot-r17 Indicates whether the UE supports DM-RS bundling for TB processing over multiple slots on PUSCH over consecutive symbols. UE must also indicate maxDurationDMRS-Bundling-r17 and tb-ProcessingMultiSlotPUSCH-r17.

Band

No

N/A

N/A

dmrs-BundlingPUSCH-RepTypeA-r17 Indicates whether UE supports DM-RS bundling for PUSCH repetition type A over consecutive symbols. Must also indicate maxDurationDMRS-Bundling-r17 and at least one of type1-PUSCH-RepetitionMultiSlots, type2-PUSCH-RepetitionMultiSlots, or pusch-RepetitionMultiSlots.

Band

No

N/A

N/A

dmrs-BundlingPUSCH-RepTypeB-r17 Indicates whether UE supports DM-RS bundling for PUSCH repetition type B over consecutive symbols. Must also indicate maxDurationDMRS-Bundling-r17 and pusch-RepetitionTypeB-r16.

Band

No

N/A

N/A

dmrs-BundlingRestart-r17 Indicates whether UE supports restarting DM-RS bundling after certain DCI/MAC CE triggered events that violate power consistency or phase continuity. If UE indicates support, it must also indicate maxDurationDMRS-Bundling-r17.

Band

No

N/A

N/A

dynamicMulticastDCI-Format4-2-r17 Indicates whether the UE supports DCI format 4_2 (with CRC scrambled by G-RNTI) for multicast. UE supporting this shall also indicate dynamicMulticastPCell-r17.

Band

No

N/A

N/A

dynamicSlotRepetitionMulticastNTN-SharedSpectrumChAccess-r17 Indicates the max number of dynamic slot-level repetitions for group-common PDSCH for multicast under NTN & shared spectrum. Value n8=8, n16=16. UE shall also indicate dynamicMulticastPCell-r17.

Band

No

N/A

N/A

dynamicSlotRepetitionMulticastTN-NonSharedSpectrumChAccess-r17 Indicates max number of dynamic slot-level repetitions for group-common PDSCH for multicast in TN & non-shared spectrum. Value n8=8, n16=16. UE sets capability for all bands. Must also indicate dynamicMulticastPCell-r17.

Band

No

N/A

N/A

enhancedSkipUplinkTxConfigured-v1660 Indicates whether UE supports skipping UL transmissions if no data/UCI are available, as per TS 38.321 [8]. UE sets capability for all bands. This field is included only if enhancedSkipUplinkTxConfigured-r16 is absent.

Band

No

N/A

N/A

enhancedSkipUplinkTxDynamic-v1660 Indicates whether UE supports skipping UL transmission for a C-RNTI if no data/UCI are available, as per TS 38.321 [8]. UE sets capability for all bands. Included only if enhancedSkipUplinkTxDynamic-r16 is absent.

Band

No

N/A

N/A

enhancedType3-HARQ-CodebookFeedback-r17 Indicates whether the UE supports enhanced type 3 HARQ-ACK codebook feedback using DCI 1_1 & 1_2 triggers, possibly with two PUCCH configs based on PHY priority. Also covers enhancedType3-HARQ-Codebooks-r17 & maxNumberPUCCH-Transmissions-r17. UE only supports dynamic selection if it has >1 enhanced type 3 HARQ-ACK codebook. Must also indicate oneShotHARQ-feedback-r16.

Band

No

N/A

N/A

enhancedUL-TransientPeriod-r16 Indicates whether the UE supports enhanced UL performance for the transient period in FR1 as per TS 38.101-1 [2] and TS 38.101-5 [34]. If absent, UE supports 10us.

Band

No

N/A

FR1 only

eventA4BasedCondHandover-r17 Indicates whether the UE supports Event A4 based conditional handover in NTN bands, i.e. CondEventA4. UE supporting this also supports condHandover-r16 for NTN and nonTerrestrialNetwork-r17.

Band

No

N/A

N/A

extendedCP Indicates whether the UE supports 60kHz SCS with extended CP for PDCCH/PDSCH reception and PUCCH/PUSCH/SRS transmission.

Band

No

N/A

N/A

groupBeamReporting Indicates whether UE supports group-based RSRP reporting for two reference signals grouped.

Band

No

N/A

N/A

groupSINR-reporting-r16 Indicates whether UE supports group-based L1-SINR reporting. UE indicates support shall also include ssb-csirs-SINR-measurement-r16.

Band

No

N/A

N/A

handoverUTRA-FDD-r16 Indicates whether UE supports NR-to-UTRA-FDD CELL_DCH CS handover. Must support UTRA-FDD measurement and B-event triggered reporting, plus periodic UTRA-FDD measurement if HO to UTRA-FDD is indicated. Also implies IMS voice over NR.

Band

No

N/A

N/A

interSlotFreqHopInterSlotBundlingPUSCH-r17 Indicates UE supports enhanced inter-slot freq hopping with inter-slot bundling for PUSCH. Must also indicate at least one of dmrs-BundlingPUSCH-RepTypeA-r17, dmrs-BundlingPUSCH-RepTypeB-r17, or dmrs-BundlingPUSCH-multiSlot-r17.

Band

No

N/A

N/A

interSlotFreqHopPUCCH-r17 Indicates UE supports enhanced inter-slot freq hopping for PUCCH repetitions with DMRS bundling. Must also indicate dmrs-BundlingPUCCH-Rep-r17.

Band

No

N/A

N/A

maxDurationDMRS-Bundling-r17 Indicates whether the UE supports the maximum duration during which it maintains power/phase continuity for DM-RS bundling on PUSCH/PUCCH. DM-RS bundling applies only for UL with pi/2-BPSK, BPSK, QPSK.

Band

No

N/A

N/A

maxMIMO-LayersForMulti-DCI-mTRP-r16 Indicates interpretation of maxNumberMIMO-LayersPDSCH per PDSCH for multi-DCI-based mTRP. If not included, maxNumberMIMO-LayersPDSCH is interpreted as total layers across two PDSCH. UE also must support overlapPDSCHsFullyFreqTime-r16.

Band

No

N/A

N/A

maxHARQ-ProcessNumber-r17 Indicates the maximal supported UL/DL HARQ process numbers. u16d32 => UL=16, DL=32; u32d16 => UL=32, DL=16; u32d32 => UL=32, DL=32. Applies only for certain bands in TS 38.101-5 [34] or HAPS bands in TS 38.104 [35].

Band

No

N/A

N/A

maxNumberPUSCH-TypeA-Repetition-r17 Indicates whether UE supports up to 32 PUSCH Type A repetitions. A UE indicating this supports type1-PUSCH-RepetitionMultiSlots, type2-PUSCH-RepetitionMultiSlots, pusch-RepetitionTypeA-r16, or pusch-RepetitionTypeA-v16c0.

Band

No

N/A

N/A

mux-HARQ-ACK-DiffPriorities-r17 Indicates whether the UE supports HARQ-ACK multiplexing with different priorities on PUCCH/PUSCH. Includes: - separate coding for high/low priority HARQ-ACK on PUCCH - multiplexing high-priority HARQ-ACK + SR + low-priority HARQ-ACK, etc. on PUCCH - separate beta_offset values for priority combos on PUSCH with UL-SCH only - etc. UE shall also indicate twoHARQ-ACK-Codebook-type1-r16.

Band

No

N/A

N/A

jointReleaseConfiguredGrantType2-r16 Indicates whether the UE supports joint release in one DCI for ≥2 configured grant Type 2 configurations in a BWP of a serving cell. UE can include this only if activeConfiguredGrant-r16 is supported.

Band

No

N/A

N/A

jointReleaseSPS-r16 Indicates whether the UE supports joint release in one DCI for ≥2 SPS configurations in a BWP of a serving cell. UE can include this only if UE indicates sps-r16.

Band

No

N/A

N/A

k1-RangeExtension-r17 Indicates whether the UE supports extended K1 values (0..31) for unpaired spectrum. Only applies for certain bands in TS 38.101-5 [34] or HAPS in TS 38.104 [35].

Band

No

N/A

N/A

locationBasedCondHandover-r17 Indicates whether the UE supports location-based conditional handover, i.e. CondEventD1. UE supporting this also supports condHandover-r16 for NTN plus nonTerrestrialNetwork-r17.

Band

No

N/A

N/A

lowPAPR-DMRS-PDSCH-r16 Indicates whether UE supports low PAPR DMRS for PDSCH.

Band

No

N/A

N/A

lowPAPR-DMRS-PUCCH-r16 Indicates whether UE supports low PAPR DMRS for PUCCH format 3/4 with transform precoding and pi/2 BPSK. Mandatory with capability signalling. UE must also indicate pucch-F3-4-HalfPi-BPSK etc.

Band

Yes

N/A

N/A

lowPAPR-DMRS-PUSCHwithoutPrecoding-r16 Indicates whether UE supports low PAPR DMRS for PUSCH without transform precoding.

Band

No

N/A

N/A

lowPAPR-DMRS-PUSCHwithPrecoding-r16 Indicates whether UE supports low PAPR DMRS for PUSCH with transform precoding and pi/2 BPSK. Mandatory with capability signalling. UE must also indicate pusch-HalfPi-BPSK.

Band

Yes

N/A

N/A

maxDynamicSlotRepetitionForSPS-Multicast-r17 Indicates maximum number of dynamic slot-level repetitions for SPS group-common PDSCH for multicast. For TN, set consistently for all supported bands. For NTN, likewise. Must also indicate sps-Multicast-r17.

Band

No

N/A

N/A

maxModulationOrderForMulticast-r17 Defines the maximal modulation order for multicast PDSCH. If absent, UE uses the same as unicast. For FR1 up to 1024QAM, for FR2 up to 256QAM. Must also indicate dynamicMulticastPCell-r17.

Band

No

N/A

N/A

maxNumberActivatedTCI-States-r16 Indicates max activated TCI states. Includes maxNumberPerCORESET-Pool-r16 for TCI states per CORESET pool, and maxTotalNumberAcrossCORESET-Pool-r16 for total TCI states across pools. Must also support multiDCI-MultiTRP-r16.

Band

No

N/A

N/A

maxNumberCSI-RS-BFD (CY) Indicates maximal number of CSI-RS resources across CCs (MCG + SCG in NR-DC) for PDCCH quality monitoring (beam failure detection). Max signaled up to 16. If included in FR1 band, same value in all FR1 bands; if included in FR2, same in all FR2. UE supports max across FR1/FR2. Mandatory for FR2; optional for FR1.

Band

CY

N/A

N/A

maxNumberCSI-RS-SSB-CBD (CY) Defines the max number of different CSI-RS/SSB resources across CCs (MCG+SCG) for new beam IDs, up to 128 signaled. If included in FR1 band, same value in all FR1. If included in FR2 band, same in all FR2. Mandatory for FR2 (≥32), optional for FR1.

Band

CY

N/A

N/A

maxNumberG-CS-RNTI-r17 Defines max number of G-CS-RNTIs for SPS multicast. For TN or NTN, sets capability consistently. Must also indicate sps-Multicast-r17.

Band

No

N/A

N/A

maxNumberG-RNTI-r17 Defines max number of G-RNTIs for multicast. For TN or NTN, sets capability consistently. Must also indicate dynamicMulticastPCell-r17.

Band

No

N/A

N/A

maxNumberNonGroupBeamReporting Defines the support of non-group-based RSRP reporting using N_max RSRP values.

Band

Yes

N/A

N/A

maxNumberRxBeam, maxNumberRxBeam-v1720 (CY) Defines whether UE supports receive beamforming switching via NZP CSI-RS resource. UE reports one value per subcarrier spacing. Support is mandatory in FR2.

Band

CY

N/A

N/A

maxNumberRxTxBeamSwitchDL, maxNumberRxTxBeamSwitchDL-v1710 Defines number of Tx/Rx beam changes UE can perform in one slot on FR2. UE shall report one value per SCS supported. scs-15kHz and scs-30kHz not included in this release.

Band

No

N/A

FR2 only

maxNumberSCellBFR-r16 Defines the max number of SCells configured for SCell beam failure recovery simultaneously. UE also indicates maxNumberCSI-RS-BFD, maxNumberSSB-BFD, maxNumberCSI-RS-SSB-CBD.

Band

No

N/A

N/A

maxNumb erSSB-BFD Defines maximal number of different SSBs across all CCs, and across MCG and SCG in case of NR-DC, for UE to monitor PDCCH quality. In this release, the maximum value that can be signalled is 16. If the UE includes the field in an FR1 band, it shall set the same value in all FR1 bands. If the UE includes the field in an FR2 band, it shall set the same value in all FR2 bands. The UE supports a total number of resources equal to the maximum of the FR1 and FR2 value, but no more than the FR1 value across all FR1 serving cells and no more than the FR2 value across all FR2 serving cells. It is mandatory with capability signalling for FR2 and optional for FR1.

Band

CY

N/A

N/A

maxNumber-LEO-SatellitesPerCarrier-r17 Indicates the number of target LEO satellites the UE can monitor per carrier. For serving carrier, the number of target LEO satellites also includes the serving satellite. If this field is not included, the number of target satellites UE can monitor per carrier is 2. The value shall be larger than or equal to the reported value on maxNumber-NGSO-SatellitesWithinOneSMTC-r17.

Band

No

FDD only

FR1 only

maxNumber-NGSO-SatellitesWithinOneSMTC-r17 Indicates the number of different NGSO satellites for target cells that the UE supports of simultaneous measurements within a SMTC with value n1 corresponds to 1, value n2 corresponds to 2 and so on.

Band

No

FDD only

FR1 only

maxUplinkDutyCycle-PC2-FR1 Indicates the maximum percentage of symbols during a certain evaluation period that can be scheduled for uplink transmission to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. This field is applicable for FR1 power class 2 UE and also applicable for FR1 power class 1.5 UE as specified in clause 6.2.1 of TS 38.101-1 [2]. If the field and maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 are both absent, 50% shall be applied as the upper limit of the UL duty cycle for power class 2. Value n60 corresponds to 60%, value n70 corresponds to 70% and so on. This capability is not applicable to IAB-MT.

Band

No

N/A

FR1 only

maxUplinkDutyCycle-FR2 Indicates the maximum percentage of symbols during 1s that can be scheduled for uplink transmission at the UE maximum transmission power, so as to ensure compliance with applicable electromagnetic power density exposure requirements provided by regulatory bodies. This field is applicable for all power classes UE in FR2 as specified in TS 38.101-2 [3]. Value n15 corresponds to 15%, value n20 corresponds to 20% and so on. If the field is absent or the percentage of uplink symbols transmitted within any 1s evaluation period is larger than maxUplinkDutyCycle-FR2, the UE behaviour is specified in TS 38.101-2 [3]. This capability is not applicable to IAB-MT.

Band

No

N/A

FR2 only

maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 Indicates the maximum percentage of symbols during a certain evaluation period that can be scheduled for uplink transmission to ensure compliance with applicable electromagnetic energy absorption requirements provided by regulatory bodies. This field is only applicable for FR1 power class 1.5 UE as specified in clause 6.2.1 of TS 38.101-1 [2]. If the field and maxUplinkDutyCycle-PC2-FR1 are both absent, 25% shall be applied as the upper limit of the UL duty cycle for power class 1.5.

Band

No

N/A

FR1 only

mn-InitiatedCondPSCellChangeNRDC-r17 Indicates whether the UE supports MN initiated conditional PSCell change in NR-DC, which is configured by NR conditionalReconfiguration using MN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in MN initiated conditional PSCell change in NR-DC. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively.

Band

No

N/A

N/A

modifiedMPR-Behaviour Indicates whether UE supports modified MPR behaviour defined in TS 38.101-1 [2], TS 38.101-2 [3], and TS 38.101-5 [34].

Band

No

N/A

N/A

mpr-PowerBoost-FR2-r16 Indicates whether UE supports uplink transmission power boost by suspension of in-band emission (IBE) requirements as specified in TS 38.101-2 [3].

Band

No

TDD only

FR2 only

mpe-Mitigation-r17 Indicates the support of enhanced PHR reporting which includes pairs of (P-MPR, SSBRI/CRI). This feature also includes following parameters:
  • maxNumP-MPR-RI-pairs-r17 indicates the maximum number of reported P-MPR and SSBRI/CRI pairs;
  • maxNumConfRS-r17 indicates the maximum number of candidate RS(s) configured in a RRC pool for MPE mitigation.
NOTE: maxNumConfRS-r17 is also counted in maxTotalResourcesForOneFreqRange-r16 / maxTotalResourcesForAcrossFreqRanges-r16.

Band

No

N/A

FR2 only

mTRP-PUCCH-InterSlot-r17 Indicates whether the UE supports the following features:
  • support of PUCCH repetition scheme 1 (inter-slot repetition) with sequential mapping for repetitions larger than 2 and with cyclic mapping for 2 repetitions.
  • support of up to two PUCCH power control parameter sets/spatial relation information per PUCCH resource. The power control parameter sets only apply to FR1 and spatial relation information only applies to FR2.
  • supported PUCCH formats for PUCCH repetition scheme 1.

Band

No

N/A

N/A

mTRP-PUCCH-CyclicMapping-r17 Indicates whether the UE supports cyclic mapping for beam mapping/power control parameter set mapping for PUCCH repetitions scheme 1 and/or 3 when the number of repetitions is larger than 2. The UE that indicates support of this feature shall also indicate support of mTRP-PUCCH-InterSlot-r17.

Band

No

N/A

N/A

mTRP-PUCCH-SecondTPC-r17 Indicates whether the UE supports second TPC field for per TRP closed-loop power control for PUCCH with DCI formats 1_1 / 1_2. The UE that indicates support of this feature shall also indicate support of mTRP-PUCCH-InterSlot-r17.

Band

No

N/A

N/A

mTRP-PUSCH-twoCSI-RS-r17 Indicates whether the UE supports up to two NZP CSI-RS resources associated with the two SRS resource sets for non-codebook-based mTRP PUSCH. The UE that indicates support of this feature shall also indicate support of srs-AssocCSI-RS, csi-RS-IM-ReceptionForFeedbackPerBandComb and mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

N/A

mTRP-BFR-twoBFD-RS-Set-r17 Indicates whether the UE supports mTRP BFR based on two BFD-RS sets. The capability signalling comprises the following parameters:
  • maxBFD-RS-resourcesPerSetPerBWP-r17 indicates the maximum number of supported measured BFD-RS resources per set per BWP.
  • maxBFR-r17 indicates the maximum number of CCs per band configured with BFR (including spCell/SCell/MTRP BFR).
  • maxBFD-RS-resourcesAcrossSetsPerBWP-r17 indicates the supported maximum number of measured BFD-RS resources across two BFD-RS sets per BWP.
maxBFD-RS-resourcesAcrossSetsPerBWP-r17 is also counted in maxTotalResourcesForOneFreqRange-r16 and maxTotalResourcesForAcrossFreqRanges-r16.

Band

No

N/A

N/A

mTRP-BFR-PUCCH-SR-perCG-r17 Indicates the maximum number of supported PUCCH-SR resources for MTRP BFR per cell group. A UE that supports mTRP-BFR-twoBFD-RS-Set-r17 shall indicate support of this feature with at least 1 PUCCH-SR resources for MTRP BFR per cell group. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

Band

No

N/A

N/A

mTRP-BFR-association-PUCCH-SR-r17 Indicates whether the UE supports association between a BFD-RS resource set on SpCell and a PUCCH SR resource. The UE indicating support of this feature shall support mTRP-BFR-PUCCH-SR-perCG-r17. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

Band

No

N/A

N/A

mTRP-BFD-RS-MAC-CE-r17 Indicates the support of MAC-CE based update of explicit BFD-RS for mTRP BFR with maximum number of configured candidate BFD-RS per BWP for MAC-CE based update. The UE indicating support of this feature shall also indicate the support of mTRP-BFR-twoBFD-RS-Set-r17.

Band

No

N/A

N/A

mTRP-CSI-EnhancementPerBand-r17 Indicates support of CSI enhancements for multi-TRP including support of NZP CSI-RS resource pairs used as CMR (channel measurement resource) pairs for NCJT measurement hypothesis with N=1. This feature also includes following parameters:
  • maxNumNZP-CSI-RS-r17 indicates the maximum number of NZP CSI-RS resources in one CSI-RS resource set: Ks,max
  • cSI-Report-mode-r17 indicates the CSI report mode selection. Mode1 indicates mode 1 with X=0, mode2 indicates mode 2, both indicate the support of both mode 1 with X=0 and mode 2.
  • A list of supported combinations, up to 16, across all CCs simultaneously, where each combination includes:
    • maxNumTx-Ports-r17 indicates the maximum number of Tx ports in one NZP CSI-RS resource associated with an NCJT measurement hypothesis
    • maxTotalNumCMR-r17 indicates the maximum total number of CMRs for NCJT measurement
    • maxTotalNumTx-PortsNZP-CSI-RS-r17 indicates the maximum total number of Tx ports of NZP CSI-RS resources associated with NCJT measurement hypotheses
    • codebookModeNCJT-r17 indicates the supported codebook modes for NCJT CSI.

Band

No

N/A

N/A

mTRP-CSI-numCPU-r17 Indicates the number of CSI processing units (CPUs) occupied by a pair of CMRs for NCJT CSI hypotheses. Maximum number of CPUs is reported in csi-ReportFramework. The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17.

Band

No

N/A

N/A

mTRP-CSI-additionalCSI-r17 Indicates the maximum value of numberOfSingleTRP-CSI-Mode1. The UE indicating support of this feature shall also indicate 'mode1' or 'both' in cSI-Report-mode-r17 of mTRP-CSI-EnhancementPerBand-r17.

Band

No

N/A

N/A

mTRP-CSI-N-Max2-r17 Indicates the support of maximum number of CMR pairs Nmax=2 configured in NZP-CSI-RS-ResourceSet for a given CSI report setting. The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17.

Band

No

N/A

N/A

mTRP-CSI-CMR-r17 Indicates the support of a NZP CSI-RS resource referred by both a CMR pair configured for Rel-17 Multi-TRP CSI enhancement and a single CMR configured for Single-TRP measurement in a CSI reporting setting. The UE indicating support of this feature shall also indicate the support of mTRP-CSI-EnhancementPerBand-r17.

Band

No

N/A

FR2 only

mTRP-PDCCH-individual-r17 Indicates the support of monitoring of individual candidates when one of the linked PDCCH candidates uses the same set of CCEs as an individual (unlinked) PDCCH candidate, and they both are associated with the same DCI size, scrambling, and CORESET. The UE indicating support of this feature shall also indicate support of mTRP-PDCCH-Repetition-r17.

Band

No

N/A

N/A

mTRP-PDCCH-anySpan-3Symbols-r17 Indicates support of PDCCH repetition for PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot. It is applicable to 15kHz SCS only. The UE indicating support of this feature shall also indicate support of pdcchMonitoringSingleOccasion and mTRP-PDCCH-Repetition-r17.

Band

No

N/A

FR1 only

mTRP-PDCCH-TwoQCL-TypeD-r17 Indicates the support of determining two QCL-TypeD for time-domain overlapping CORESETs in the same CC or for intra-band CA when UE is configured with PDCCH repetition. The UE indicating support of this feature shall also indicate support of mTRP-PDCCH-Repetition-r17.

Band

No

N/A

FR2 only

mTRP-PUSCH-CSI-RS-r17 Indicates the support of CSI-RS processing framework for SRS with two associated CSI-RS resources. This feature also includes following parameters:
  • maxNumPeriodicSRS-r17 indicates the maximum number of periodic SRS resources associated with first and second CSI-RS per BWP.
  • maxNumAperiodicSRS-r17 indicates the maximum number of aperiodic SRS resources associated with first and second CSI-RS per BWP.
  • maxNumSP-SRS-r17 indicates the maximum number of semi-persistent SRS resources associated with first and second CSI-RS per BWP.
  • numSRS-ResourcePerCC-r17: UE can process Y SRS resources associated with first and second CSI-RS resources simultaneously in a CC. Includes Periodic/Semi-Persistent/Aperiodic SRS.
  • numSRS-ResourceNonCodebook-r17: UE can process up to X CSI-RS resources associated with SRS for non-codebook based transmission simultaneously.
The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-twoCSI-RS-r17.

Band

No

N/A

N/A

mTRP-PUSCH-cyclicMapping-r17 Indicates the support of cyclic mapping when the number of repetitions is larger than 2 with repetition type. The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

N/A

mTRP-PUSCH-secondTPC-r17 Indicates the support of second TPC field for per TRP closed-loop power control for PUSCH with DCI formats 0_1 and 0_2. The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

FR1 only

mTRP-PUSCH-twoPHR-Reporting-r17 Indicates the support of PHR reporting related to M-TRP PUSCH repetition (calculate two PHRs, each associated with a first PUSCH occasion corresponding to each SRS resource set, and report two PHRs). The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

N/A

mTRP-PUSCH-A-CSI-r17 Indicates the support of A-CSI report on two PUSCH repetitions. The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

FR1 only

mTRP-PUSCH-SP-CSI-r17 Indicates the support of SP-CSI report on two PUSCH repetitions. The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

N/A

mTRP-PUSCH-CG-r17 Indicates the support of CG PUSCH transmission towards M-TRPs using a single CG configuration. The UE uses same beam mapping principals as dynamic grant PUSCH repetition scheme. The UE indicating support of this feature shall also indicate the support of mTRP-PUSCH-TypeA-CB-r17 or mTRP-PUSCH-RepetitionTypeA-r17.

Band

No

N/A

N/A

mTRP-PUCCH-MAC-CE-r17 Indicates the support of updating two Spatial Relation Info’s and two sets of power control parameters for a group of PUCCH resources in a CC by MAC-CE. The UE indicates support of this feature shall also indicate support of mTRP-PUCCH-InterSlot-r17.

Band

No

N/A

N/A

mTRP-PUCCH-maxNum-PC-FR1-r17 Indicates the maximum number of power control parameter sets configured for multi-TRP PUCCH repetition in FR1. The UE indicating support of this feature shall also indicate the support of mTRP-PUCCH-InterSlot-r17.

Band

No

N/A

FR1 only

mTRP-inter-Cell-r17 Indicates the support of RRC configuration of additional PCI different from serving cell associated with the TCI state and/or QCL-info. This feature also includes following parameters:
  • maxNumAdditionalPCI-Case1-r17 indicates the maximum number of configured additional PCIs per CC is X1 (Case 1) when each configuration of SSB time domain positions and periodicity of the additional PCIs is the same as SSB time domain positions and periodicity of the serving cell PCI.
  • maxNumAdditionalPCI-Case2-r17 indicates the maximum number of configured additional PCIs per CC is X2 (Case 2) when the configurations of SSB time domain positions and periodicity of the additional PCIs is not according to Case 1.
The UE indicating support of this feature shall also indicate the support of multiDCI-MultiTRP-r16.

Band

No

N/A

N/A

mTRP-GroupBasedL1-RSRP-r17 Indicates the support of group based L1-RSRP reporting enhancements. This feature also includes following parameters:
  • maxNumBeamGroups-r17 indicates the maximum number N of beam groups (M=2 beams per beam group) in a single L1-RSRP reporting instance based on measurement on two CMR resource sets.
  • maxNumRS-WithinSlot-r17 indicates the maximum number of SSB and CSI-RS resources for measurement in both CMR sets within a slot across all CCs.
  • maxNumRS-AcrossSlot-r17 indicates the maximum number of configured SSB and CSI-RS resources for measurement in both CMR sets across all CCs.
maxNumRS-WithinSlot-r17 and maxNumRS-AcrossSlot-r17 are also counted in m axTotalResourcesForOneFreqRange-r16 and maxTotalResourcesForAcrossFreqRanges-r16.

Band

No

N/A

N/A

multiPDSCH-SingleDCI-FR2-1-SCS-120kHz-r17 Indicates whether the UE supports multi-PDSCH scheduling by single DCI for the operation with 120kHz SCS in FR2-1 and HARQ enhancements for both type 1 and type 2 HARQ codebook.

Band

No

N/A

N/A

multiPUCCH-HARQ-ACK-ForMulticastUnicast-r17 Indicates whether the UE supports two non-overlapping slot-based PUCCHs for ACK/NACK based HARQ-ACK feedback for multicast or for unicast and multicast with different priorities in a slot. For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. A UE supporting this feature shall also indicate support of priorityIndicatorInDCI-Multicast-r17 and twoHARQ-ACK-CodebookForUnicastAndMulticast-r17.

Band

No

N/A

N/A

multiPUSCH-SingleDCI-FR2-1-SCS-120kHz-r17 Indicates whether the UE supports multi-PUSCH scheduling by single DCI for the operation with 120kHz SCS in FR2-1 with non-contiguous allocation.

Band

No

N/A

N/A

multipleRateMatchingEUTRA-CRS-r16 Indicates whether the UE supports multiple E-UTRA CRS rate matching patterns, which is supported only for FR1. The capability signalling comprises the following parameters:
  • maxNumberPatterns-r16 indicates the maximum number of LTE-CRS rate matching patterns in total within a NR carrier using 15 kHz SCS.
  • maxNumberNon-OverlapPatterns-r16 indicates the maximum number of LTE-CRS non-overlapping rate matching patterns within a NR carrier using 15 kHz SCS.
The UE can report the value larger than 2 only if UE reports the value of maxNumberNon-OverlapPatterns-r16 is larger than 1. The UE can include this feature only if the UE indicates support of rateMatchingLTE-CRS.

Band

No

FDD only

FR1 only

multipleTCI Indicates whether UE supports more than one TCI state configurations per CORESET. UE is only required to track one active TCI state per CORESET. UE is required to support minimum between 64 and number of configured TCI states indicated by tci-StatePDSCH. This field shall be set to supported.

Band

Yes

N/A

N/A

nack-OnlyFeedbackForMulticastWithDCI-Enabler-r17 Indicates whether the UE supports DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-RNTI by RRC signalling via DCI format 4_2. A UE supporting this feature shall also indicate support of nack-OnlyFeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17.

Band

No

N/A

N/A

nack-OnlyFeedbackForSPS-MulticastWithDCI-Enabler-r17 Indicates whether the UE supports DCI-based enabling/disabling NACK-only based HARQ-ACK feedback configured per G-CS-RNTI by RRC signalling via DCI format 4_2. A UE that indicates support of this feature shall indicate support of nack-OnlyFeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17.

Band

No

N/A

N/A

nonGroupSINR-reporting-r16 Indicates N_max L1-SINR values reported when UE supports non-group based L1-SINR reporting. UE indicates support of this feature shall indicate support of ssb-csirs-SINR-measurement-r16.

Band

No

N/A

N/A

nr-UE-TxTEG-ID-MaxSupport-r17 Indicates the maximum number of UE TxTEG for SRS resource for positioning, which is supported and reported by UE for UL TDOA. The UE can include this field only if the UE supports srs-AllPosResources-r16.

Band

No

N/A

N/A

olpc-SRS-Pos-r16 Indicates whether the UE supports OLPC for SRS for positioning. The capability signalling comprises the following parameters:
  • olpc-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the serving cell in the same band.
  • olpc-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on SSB from the neighbouring cell in the same band.
  • olpc-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the neighbouring cell in the same band.
  • maxNumberPathLossEstimatePerServing-r16 indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning per serving cell in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions.

Band

No

N/A

N/A

olpc-SRS-PosRRC-Inactive-r17 Indicates whether the UE supports OLPC for SRS for positioning in RRC_INACTIVE. The capability signalling comprises the following parameters:
  • olpc-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the serving cell in the same band.
  • olpc-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on SSB from the neighbouring cell in the same band.
  • olpc-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports OLPC for SRS for positioning based on PRS from the neighbouring cell in the same band.
  • maxNumberPathLossEstimatePerServing-r16 indicates the maximum number of pathloss estimates that the UE can simultaneously maintain for all the SRS resource sets for positioning per serving cell in addition to the up to four pathloss estimates that the UE maintains per serving cell for the PUSCH/PUCCH/SRS transmissions.

Band

No

N/A

N/A

oneShotHARQ-feedbackPhy-Priority-r17 Indicates whether the UE supports transmission of type 3 HARQ-ACK codebook using the first or second PUCCH configuration based on PHY priority indication in the triggering DCI. A UE supporting this feature shall also indicate support of oneShotHARQ-feedback-r16 and twoHARQ-ACK-Codebook-type1-r16.

Band

No

N/A

N/A

oneShotHARQ-feedbackTriggeredByDCI-1-2-r17 Indicates whether the UE supports one-shot HARQ ACK feedback triggered by DCI format 1_2, comprised of the following functional components:
  • Supports feedback of type 3 HARQ-ACK codebook, triggered by a DCI 1_2 scheduling a PDSCH;
  • Supports feedback of type 3 HARQ-ACK codebook, triggered by a DCI 1_2 without scheduling a PDSCH using a reserved FDRA value.
A UE supporting this feature shall also indicate support of oneShotHARQ-feedback-r16 and dci-Format1-2And0-2-r16.

Band

No

N/A

N/A

oneSlotPeriodicTRS-r16 Indicates whether the UE supports one-slot periodic TRS configuration only when no two consecutive slots are indicated as downlink slots by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigDedicated. If the UE supports this feature, the UE needs to report csi-RS-ForTracking.

Band

No

TDD only

FR1 only

outOfOrderOperationDL-r16 Indicates whether the UE supports out of order operation for DL. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16. The capability signalling comprises the following parameters:
  • supportPDCCH-ToPDSCH-r16 indicates support out-of-order operation for PDCCH to PDSCH;
  • supportPDSCH-ToHARQ-ACK-r16 indicates support out-of-order operation for PDSCH to HARQ-ACK.

Band

No

N/A

N/A

outOfOrderOperationUL-r16 Indicates whether the UE supports out of order operation for UL. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16.

Note: Same closed loop index for power control across PUSCHs associated with different CORESETPoolIndex values is not supported by a UE indicating the support of this feature when TPC accumulation is enabled.

Band

No

N/A

N/A

overlapPDSCHsFullyFreqTime-r16 Indicates the maximal number of PDSCH scrambling sequences per serving cell when the UE supports PDSCHs with fully overlapping Resource Elements. The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16.

Note: A UE may assume that its maximum receive timing difference between the DL transmissions from two TRPs is within a Cyclic Prefix.

Band

No

N/A

N/A

overlapPDSCHsInTimePartiallyFreq-r16 Indicates whether the UE supports PDSCHs with partially overlapping Resource Elements. The UE that indicates support of this feature shall support overlapPDSCHsFullyFreqTime-r16.

Band

No

N/A

N/A

overlapRateMatchingEUTRA-CRS-r16 Indicates whether the UE supports two LTE-CRS overlapping rate matching patterns within a part of NR carrier using 15 kHz SCS overlapping with a LTE carrier. If the UE supports this feature, the UE needs to report multipleRateMatchingEUTRA-CRS-r16.

Band

No

N/A

FR1 only

parallelMeasurementWithoutRestriction-r17 Indicates whether the UE supports measurements on cells belonging to different satellites as the serving cell in parallel with normal operation (i.e. data/control transmission and/or reception, and L1 measurements) of serving cell without scheduling restrictions. The feature is applicable only when the serving satellite is NGSO. If not reported, for measurements in parallel with normal operation of serving cell scheduling restrictions shall apply.

Band

No

FDD only

FR1 only

parallelPRS-MeasRRC-Inactive-r17 Indicates whether the UE supports performing RRM measurement and PRS measurement in parallel. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

Band

No

N/A

N/A

pdcch-SkippingWithoutSSSG-r17 Indicates whether the UE supports up to 2-bit indication of PDCCH skipping by scheduling DCI if SSSG is not configured as specified in TS 38.213 [11], clause 10.4.

Band

No

N/A

N/A

pdcch-SkippingWithSSSG-r17 Indicates whether the UE supports 2-bit indication of SSSG switching between 2 SSSGs, PDCCH skipping by scheduling DCI, and timer based SSSG switching as specified in TS 38.213 [11], clause 10.4. UE supports search space set group switching capability-1 according to Table 10.4-1 of TS 38.213 [11]. UE indicating support of this feature shall also indicate support of pdcch-SkippingWithoutSSSG-r17 and sssg-Switching-1bitInd-r17.

Band

No

N/A

N/A

pdsch-1024QAM-2MIMO-FR1-r17 Indicates whether the UE supports 1024QAM modulation scheme for PDSCH with maximum 2 MIMO layers for FR1 as defined in TS 38.211 [6], MCS and CQI feedback tables based on 1024QAM modulation order as defined in TS 38.214 [12]. UE indicating support of this feature shall also indicate support of pdsch-256QAM-FR1 and shall not indicate support of pdsch-1024QAM-FR1-r17.

Band

No

N/A

FR1 only

pdsch-1024QAM-FR1-r17 Indicates whether the UE supports 1024QAM modulation scheme for PDSCH for FR1 as defined in TS 38.211 [6], MCS and CQI feedback tables based on 1024QAM modulation order as defined in TS 38.214 [12]. UE indicating support of this feature shall also indicate support of pdsch-256QAM-FR1 and shall not indicate support of pdsch-1024QAM-2MIMO-FR1-r17.

Band

No

N/A

FR1 only

pdsch-256QAM-FR2 Indicates whether the UE supports 256QAM modulation scheme for PDSCH for FR2 as defined in 7.3.1.2 of TS 38.211 [6].

Band

No

N/A

FR2 only

pdsch-MappingTypeB-Alt-r16 Indicates whether the UE supports PDSCH Type B scheduling of length 9 and 10 OFDM symbols, and DMRS shift for length-10 symbols. If the UE supports this feature, the UE needs to report pdsch-MappingTypeB.

Band

No

N/A

FR1 only

periodicBeamReport Indicates whether UE supports periodic ‘CRI/RSRP’ or ‘SSBRI/RSRP’ reporting using PUCCH formats 2, 3 and 4 in one slot.

Band

Yes

N/A

N/A

posSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 Indicates support of Positioning SRS transmission in RRC_INACTIVE state configured outside initial UL BWP. The capability signalling comprises the following parameters:
  • maxSRSposBandwidthForEachSCS-withinCC-FR1-r17 indicates the maximum SRS bandwidth supported for each SCS within a single CC for FR1;
  • maxSRSposBandwidthForEachSCS-withinCC-FR2-r17 indicates the maximum SRS bandwidth supported for each SCS within a single CC for FR2;
  • maxNumOfSRSposResourceSets-r17 indicates the max number of SRS Resource Sets for positioning supported by UE;
  • maxNumOfPeriodicSRSposResources-r17 indicates the max number of periodic SRS Resources for positioning;
  • maxNumOfPeriodicSRSposResourcesPerSlot-r17 indicates the max number of periodic SRS Resources for positioning per slot;
  • differentNumerologyBetweenSRSposAndInitialBWP-r17 indicates the support of different numerology between the SRS and the initial UL BWP;
  • srsPosWithoutRestrictionOnBWP-r17 indicates the support of SRS operation without restriction on the BW;
  • maxNumOfPeriodicAndSemipersistentSRSposResources-r17 indicates the max number of P/SP SRS Resources for positioning;
  • maxNumOfPeriodicAndSemipersistentSRSposResourcesPerSlot-r17 indicates the max number of P/SP SRS Resources for positioning per slot;
  • differentCenterFreqBetweenSRSposAndInitialBWP-r17 indicates the support of a different center frequency between the SRS for positioning and the initial UL BWP;
  • switchingTimeSRS-TX-OtherTX-r17 indicates the switching time between SRS TX and other TX in initial UL BWP or RX in initial DL BWP;
  • maxNumOfSemiPersistentSRSposResources-r17 indicates the max number of semi-persistent SRS Resources for positioning;
  • maxNumOfSemiPersistentSRSposResourcesPerSlot-r17 indicates the max number of semi-persistent SRS Resources for positioning per slot.
The UE can include this field only if the UE supports srs-PosResourcesRRC-Inactive-r17. Otherwise, the UE does not include this field.

Band

No

N/A

N/A

powerBoosting-pi2BPSK Indicates whether UE supports power boosting for pi/2 BPSK, when applicable as defined in 6.2 of TS 38.101-1 [2] v16.9.0. It is mandatory with capability signalling. This capability is not applicable to IAB-MT.

Band

CY

TDD only

FR1 only

priorityIndicatorInDCI-Multicast-r17 Indicates whether the UE supports DL priority indication for multicast in DCI, comprised of the following functional components:
  • Support of priority indicator field configured in DCI formats 4_2 with CRC scrambled with G-RNTI for multicast;
  • Supports two HARQ-ACK codebooks with different priorities to be simultaneously constructed different priorities for multicast and multicast at a UE.
For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForMulticast-r17 and dynamicMulticastDCI-Format4-2-r17.

Band

No

N/A

N/A

priorityIndicatorInDCI-SPS-Multicast-r17 Indicates whether the UE supports priority indicator field configured in DCI format 4_2 for multicast HARQ-ACK feedback of SPS multicast. For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands. A UE supporting this feature shall also indicate support of ack-NACK-FeedbackForSPS-Multicast-r17 and sps-MulticastDCI-Format4-2-r17.

Band

No

N/A

N/A

prs-MeasurementWithoutMG-r17 Indicates whether the UE supports using the threshold to compare the Rx time difference between the serving cell and a neighbor cell/TRP for PRS measurements, as defined in clause 9.9.1.2 of TS 38.133 [5], to determine whether the PRS from the non-serving cell satisfy the condition of PRS measurement outside MG. The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A-r17, prs-ProcessingWindowType1B-r17 and prs-ProcessingWindowType2-r17.

Band

No

N/A

N/A

prs-ProcessingCapabilityOutsideMGinPPW-r17 Indicates the DL-PRS Processing Capability outside MG of each of the supported PRS Processing Window (PPW) Type in the case the UE supports multiple PPW Types in a band and comprises the following subfields:
  • prsProcessingType-r17: Indicates the PPW Type for which the prs-ProcessingCapabilityOutsideMGinPPW-r17 are provided.
  • ppw-dl-PRS-BufferType-r17: Indicates DL-PRS buffering capability. ‘type1’ => sub-slot/symbol level buffering, ‘type2’ => slot level buffering.
  • ppw-durationOfPRS-Processing1-r17: Indicates the duration of DL-PRS symbols N in units of ms a UE can process every T ms assuming maximum DL-PRS bandwidth...
    • ppw-durationOfPRS-ProcessingSymbolsN-r17: This field specifies the values for N with values msDot125=0.125ms, msDot25=0.25ms, etc.
    • ppw-durationOfPRS-ProcessingSymbolsT-r17: This field specifies the values for T with values ms1=1ms, ms2=2ms, etc.
  • ppw-durationOfPRS-Processing2-r17: same idea but with N2, T2 for a second possibility.
  • ppw-maxNumOfDL-PRS-ResProcessedPerSlot-r17: the maximum number of DL PRS bandwidth in MHz the UE supports for PRS measurement outside MG within the PPW.
  • ppw-maxNumOfDL-Bandwidth-r17: the maximum number of DL PRS bandwidth in MHz for FR1 and FR2 for PRS measurement outside MG within the PPW.
The UE can include this field only if the UE supports one of prs-ProcessingWindowType1A-r17, prs-ProcessingWindowType1B-r17 and prs-ProcessingWindowType2-r17. Otherwise, the UE does not include this field.

Band

No

N/A

N/A

prs-ProcessingRRC-Inactive-r17 Indicates whether the UE supports PRS processing in RRC_INACTIVE.

Band

No

N/A

N/A

prs-ProcessingWindowType1A-r17 Indicates whether the UE supports PRS processing Type 1A, subject to the UE determining that DL PRS to be higher priority for PRS measurement outside MG and in a PRS processing window and the priority handling options of PRS as follows:
  • Option 1: Support of "st1" and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
  • Option 2: Support of "st1", "st2", and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
  • Option 3: Support of "st1" only defined in clause 5.1.6.5 of TS 38.214 [12].
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList-r16. A UE supporting this feature shall also indicate support of prs-ProcessingCapabilityOutsideMGinPPW-r17.

Band

No

N/A

N/A

prs-ProcessingWindowType1B-r17 Indicates whether the UE supports PRS processing Type 1B, subject to the UE determining that DL PRS to be higher priority for PRS measurement outside MG and in a PRS processing window and the priority handling options of PRS as follows:
  • Option 1: Support of "st1" and "st3".
  • Option 2: Support of "st1", "st2", and "st3".
  • Option 3: Support of "st1" only.
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList-r16. A UE supporting this feature shall also indicate support of prs-ProcessingCapabilityOutsideMGinPPW-r17.

Band

No

N/A

N/A

prs-ProcessingWindowType2-r17 Indicates whether the UE supports PRS processing Type 2, subject to the UE determining that DL PRS to be higher priority for PRS measurement outside MG and in a PRS processing window and the priority handling options of PRS as follows:
  • Option 1: Support of "st1" and "st3" defined in clause 5.1.6.5 of TS 38.214 [12].
  • Option 2: Support of "st1", "st2", and "st3".
  • Option 3: Support of "st1" only.
The UE can include this field only if the UE supports prs-ProcessingCapabilityBandList-r16. A UE supporting this feature shall also indicate support of prs-ProcessingCapabilityOutsideMGinPPW-r17.

Band

No

N/A

N/A

ptrs-DensityRecommendationSetDL For each supported sub-carrier spacing, indicates preferred threshold sets for determining DL PTRS density. It is mandated for FR2. For each supported sub-carrier spacing, this field comprises:
  • two values of frequencyDensity;
  • three values of timeDensity.

Band

CY

N/A

N/A

ptrs-DensityRecommendationSetUL For each supported sub-carrier spacing, indicates preferred threshold sets for determining UL PTRS density. For each supported sub-carrier spacing, this field comprises:
  • two values of frequencyDensity;
  • three values of timeDensity;
  • five values of sampleDensity.

Band

No

N/A

N/A

pucch-Repetition-F0-2-r17 Indicates whether the UE supports transmission of a PUCCH format 0 and 2 over multiple slots with the repetition factor 2, 4 or 8. A UE supporting this feature shall also indicate support of pucch-Repetition-F1-3-4.

Band

No

N/A

N/A

pucch-SpatialRelInfoMAC-CE Indicates whether the UE supports indication of PUCCH-spatialrelationinfo by a MAC CE per PUCCH resource. It is mandatory for FR2 and optional for FR1.

Band

CY

N/A

N/A

pusch-256QAM Indicates whether the UE supports 256QAM modulation scheme for PUSCH as defined in 6.3.1.2 of TS 38.211 [6].

Band

No

N/A

N/A

pusch-RepetitionMsg3-r17 Indicates whether the UE supports repetition of PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI.

Band

No

N/A

N/A

pusch-RepetitionMultiSlots-v1650 Indicates whether the UE supports transmitting PUSCH scheduled by DCI format 0_1 when configured with pusch-AggregationFactor > 1, as defined in clause 6.1.2.1 of TS 38.214 [12]. This applies only to non-shared spectrum channel access. For shared spectrum channel access, pusch-RepetitionMultiSlots-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively. The UE only includes pusch-RepetitionMultiSlots-v1650 if pusch-RepetitionMultiSlots is absent.

Band

Yes

N/A

N/A

pusch-RepetitionTypeA-v16c0 Indicates whether the UE supports the dynamic indication of the number of repetitions for PUSCH transmission as specified in TS 38.214 [12], clause 6.1.2.1. Support of this field is reported for shared spectrum channel access and non-shared spectrum channel access, respectively. UE indicating support of this feature shall support at least one of type2-PUSCH-RepetitionMultiSlots and pusch-RepetitionMultiSlots for shared spectrum and non-shared spectrum respectively. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively. The UE only includes pusch-RepetitionTypeA-v16c0 if pusch-RepetitionTypeA-r16 is absent.

Band

No

N/A

N/A

pusch-TransCoherence
Defines support of the uplink codebook subset by the UE for UL precoding for PUSCH transmission as described in clause 6.1.1.1 of TS 38.214 [12]. UE indicated support of partial coherent codebook subset shall also support non-coherent codebook subset. UE indicated support of full coherent codebook subset shall also support partial and non-coherent codebook subset.

Band

No

N/A

N/A

puschTypeA-RepetitionsAvailSlot-r17
Indicates whether UE supports dynamic and configured grant PUSCH repetitions based on available slots.

Transmission occasions for the repetitions for dynamic and configured grant PUSCH are determined on the basis of available slots.

A UE that indicates support of this feature shall support type1-PUSCH-RepetitionMultiSlots, type2-PUSCH-RepetitionMultiSlots or pusch-RepetitionMultiSlots.

Band

No

N/A

N/A

rateMatchingLTE-CRS
Indicates whether the UE supports receiving PDSCH with resource mapping that excludes the REs determined by the higher layer configuration LTE-carrier configuring common RS, as specified in TS 38.214 [12].

Band

Yes

N/A

N/A

releaseSPS-MulticastWithCS-RNTI-r17
Indicates whether UE supports unicast PDCCH scrambled with CS-RNTI to release SPS group-common PDSCH.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE that indicates the support of this feature shall indicate support of sps-Multicast-r17 and sps-r16.

Band

No

N/A

N/A

re-LevelRateMatchingForMulticast-r17
Indicates whether the UE supports group-common PDSCH RE-level rate matching for multicast, comprised of the following functional components:

- Supports SP ZP-CSI-RS for group-common PDSCH RE-mapping patterns;
- Supports P ZP-CSI-RS for group-common PDSCH RE-mapping patterns;
- Supports p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config-Multicast same as or different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config;
- Supports AP ZP-CSI-RS for group-common PDSCH RE-mapping patterns.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of dynamicMulticastPCell-r17. A UE supporting this feature in FR1 bands shall also indicate support of pdsch-RE-MappingFR1-PerSymbol or pdsch-RE-MappingFR1-PerSlot. A UE supporting this feature in FR2 bands shall also indicate support of pdsch-RE-MappingFR2-PerSymbol or pdsch-RE-MappingFR2-PerSlot.

NOTE: The total number of semi-persistent ZP-CSI-RS-ResourceSet that a UE can be configured with is the same as for unicast in Rel-16.

Band

No

N/A

N/A

rlm-Relaxation-r17
Indicates whether the UE supports RLM relaxation criteria and requirement as specified in TS 38.133 [5]. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

UE indicating support of this feature shall also indicate support of ssb-RLM and/or csi-RS-RLM.

Band

No

N/A

N/A

searchSpaceSetGrp-switchCap2-r17
Indicates whether UE supports search space set group switching capability 2 for FR1 according to Table 10.4-1 of TS 38.213 [11] for SSSG switching.

UE indicating support of this feature shall also indicate support of sssg-Switching-1bitInd-r17.

NOTE: For UE supporting this feature and also sssg-Switching-1BitInd-r17, sssg-Switching-2BitInd-r17, and/or pdcch-SkippingWithSSSG-r17, search space set group switching Capability-2 is applied to sssg-Switching-1BitInd-r17, sssg-Switching-2BitInd-r17, and/or pdcch-SkippingWithSSSG-r17.

Band

No

N/A

FR1 only

semi-PersistentL1-SINR-Report-PUCCH-r16
Indicates whether the UE supports semi-persistent L1-SINR report on PUCCH.

The UE indicating support of this feature shall include at least one of the following capabilities:

- supportReportFormat1-2OFDM-syms-r16 indicates support of report on PUCCH formats over 1 -- 2 OFDM symbols once per slot (or piggybacked on a PUSCH)
- supportReportFormat4-14OFDM-syms-r16 indicates support of report on PUCCH formats over 4 -- 14 OFDM symbols once per slot (or piggybacked on a PUSCH).

The UE indicating support of this feature shall also indicate support of ssb-csirs-SINR-measurement-r16.

Band

No

N/A

N/A

semi-PersistentL1-SINR-Report-PUSCH-r16
Indicates whether the UE supports semi-persistent L1-SINR report on PUSCH. The UE indicating support of this feature shall also indicate support of ssb-csirs-SINR-measurement-r16.

Band

No

N/A

N/A

separateCRS-RateMatching-r16
Indicates whether the UE supports rate match around configured CRS patterns which is associated with CORESETPoolIndex (if configured) and are applied to the PDSCH scheduled with a DCI detected on a CORESET with the same value of CORESETPoolIndex.

The UE that indicates support of this feature shall support multiDCI-MultiTRP-r16 and overlapRateMatchingEUTRA-CRS-r16. This is only applicable for 15kHz SCS.

Band

No

N/A

FR1 only

sfn-SimulTwoTCI-AcrossMultiCC-r17
Indicates whether the UE supports simultaneous activation of two TCI states for CORESETs with the same CORESET ID in all BWPs across a set of configured component carriers by single MAC-CE. The UE indicating support of this feature shall also indicate sfn-schemeA-r17 or sfn-schemeB-r17 or sfn-schemeA-PDCCH-only-r17.

The UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

Band

No

N/A

N/A

sfn-DefaultDL-BeamSetup-r17
Indicates whether the UE supports the following features:

- For FR2 only, PDSCH reception using default beam for enhanced SFN scheme when PDSCH is scheduled with offset less than threshold.
- For FR1 and FR2, PDSCH reception using default beam for enhanced SFN scheme when TCI field is not present in DCI format 1_0/1_1/1_2 when PDSCH is scheduled with offset equal or larger than the threshold, if applicable.
- For FR2 only, aperiodic CSI-RS reception using default beam for enhanced SFN scheme when scheduling offset is less than threshold.

The UE indicating support of this feature shall also indicate sfn-schemeA-r17 or sfn-schemeB-r17.

Band

No

N/A

N/A

sfn-DefaultUL-BeamSetup-r17
Indicates whether the UE supports the following features:

- Support of single-TRP PUCCH transmission using default beam when enhanced SFN PDCCH transmission scheme is configured.
- Support of single-TRP PUSCH transmission using default beam when enhanced SFN PDCCH transmission scheme is configured.
- Support of single-TRP SRS resource transmission using default beam when enhanced SFN PDCCH transmission scheme is configured.

The UE indicating support of this feature shall also indicate sfn-schemeA-r17 or sfn-schemeB-r17 or sfn-schemeA-PDCCH-only-r17.

Band

No

N/A

FR2 only

sfn-ImplicitRS-twoTCI-r17
Indicates whether the UE supports RS(s) with two TCI states configured implicitly for beam failure detection enhancement for HST.

Band

No

N/A

N/A

sfn-QCL-TypeD-Collision-twoTCI-r17
Indicates whether the UE supports identification of two QCL-TypeD properties for multiple overlapping CORESETs when a CORESET is activated with two TCI states which overlaps with another CORESET.

Band

No

N/A

N/A

simul-SpatialRelationUpdatePUCCHResGroup-r16
Indicates whether the UE support PUCCH resource groups per BWP for simultaneous spatial relation update. The UE indicating support of this also indicates the capabilities of supported SRS resources and maximum supported spatial relations for the supported bands using supportedSRS-Resources, maxNumberConfiguredSpatialRelations and pucch-SpatialRelInfoMAC-CE.

Band

No

N/A

N/A

simulTX-SRS-AntSwitchingIntraBandUL-CA-r16
Indicates whether the UE support simultaneous transmission of SRS on different CCs for intra-band UL CA. The UE indicating support of this feature shall include at least one of the following capabilities:

- supportSRS-xTyR-xLessThanY-r16 indicates support transmission of SRS for xTyR (x<y) based antenna switching and SRS for CB/NCB/BM on different CCs in overlapped symbol(s) for intra-band UL CA.
- supportSRS-xTyR-xEqualToY-r16 indicates support transmission of SRS for xTyR (x=y) based antenna switching and SRS for CB/NCB/BM on different CCs in overlapped symbol(s) for intra-band UL CA.
- supportSRS-AntennaSwitching-r16 Indicates whether the UE support simultaneous transmission of SRS for antenna switching on different CCs in overlapped symbol(s) for intra-band UL CA.

NOTE: For simultaneously antenna switching and antenna switching SRS in intra-band CAs with bands whose UL are switched together according to the reported supportSRS-AntennaSwitching-r16, the UE expects the same configuration of xTyR across the different CCs and the SRS resources overlapped in time domain from UE perspective are from the same UE antenna ports.

Band

No

N/A

N/A

simulSRS-MIMO-TransWithinBand-r16
Indicates the number of SRS resources for positioning and SRS resource for MIMO on a symbol within a band across multiple CCs. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field.

Band

No

N/A

N/A

simulSRS-TransWithinBand-r16
Indicates the number of SRS resources for positioning on a symbol within a band across multiple CCs. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field.

Band

No

N/A

N/A

simultaneousReceptionDiffTypeD-r16
Indicates whether the UE supports simultaneous reception with different QCL Type D reference signal as specified in TS38.213 [11].

Band

No

N/A

FR2 only

sn-InitiatedCondPSCellChangeNRDC-r17
Indicates whether the UE supports SN initiated inter-SN conditional PSCell change in NR-DC, which is configured by NR conditionalReconfiguration using SN configured measurement as triggering condition. The UE supporting this feature shall also support 2 trigger events for same execution condition in SN initiated inter-SN conditional PSCell change in NR-DC. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands respectively.

Band

No

N/A

N/A

spatialRelations, spatialRelations-v1640
Indicates whether the UE supports spatial relations. The capability signalling comprises the following parameters:

- maxNumberConfiguredSpatialRelations indicates the maximum number of configured spatial relations per CC for PUCCH and SRS. It is not applicable to FR1 and applicable to FR2 only. The UE is mandated to report 16 or higher values. maxNumberConfiguredSpatialRelations-v1640 indicates the maximum number of configured spatial relations per CC for PUCCH and SRS with UE supporting the configuration of maximum 64 PUCCH spatial relations per BWP per CC;
- maxNumberActiveSpatialRelations indicates the maximum number of active spatial relations with regarding to PUCCH and SRS for PUSCH, per BWP per CC. It is not applicable to FR1 and applicable and mandatory to report one or higher value for FR2 only;
- additionalActiveSpatialRelationPUCCH indicates support of one additional active spatial relation for PUCCH. It is mandatory with capability signalling if maxNumberActiveSpatialRelations is set to n1;
- maxNumberDL-RS-QCL-TypeD indicates the maximum number of downlink RS resources used for QCL type D in the active TCI states and active spatial relation information, which is optional.

The UE is mandated to report spatialRelations for FR2. if maxNumberConfiguredSpatialRelations-v1640 is reported, UE shall report value n96 in maxNumberConfiguredSpatialRelations.

Band

FD

N/A

FD

spatialRelationsSRS-Pos-r16
Indicates whether the UE supports spatial relations for SRS for positioning. The capability signalling comprises the following parameters:

- spatialRelation-SRS-PosBasedOnSSB-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the serving cell in the same band. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field;
- spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on CSI-RS from the serving cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnSSB-Serving-r16. Otherwise, the UE does not include this field;
- spatialRelation-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the serving cell in the same band. The UE can include this field only if the UE supports any of DL PRS Resources for DL AoD, DL PRS Resources for DL-TDOA or DL PRS Resources for Multi-RTT defined in TS37.355 [22], or srs-PosResources-r16. Otherwise, the UE does not include this field;
- spatialRelation-SRS-PosBasedOnSRS-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SRS in the same band. The UE can include this field only if the UE supports srs-PosResources-r16. Otherwise, the UE does not include this field;
- spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnSSB-Serving-r16. Otherwise, the UE does not include this field;
- spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE can include this field only if the UE supports spatialRelation-SRS-PosBasedOnPRS-Serving-r16. Otherwise, the UE does not include this field;

NOTE: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.

Band

No

N/A

FR2 only

spatialRelationsSRS-PosRRC-Inactive-r17
Indicates whether the UE supports spatial relations for SRS for positioning in RRC_INACTIVE.

The capability signalling comprises the following parameters:
- spatialRelation-SRS-PosBasedOnSSB-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the serving cell in the same band. The UE indicating support of this feature shall also indicate support of srs-PosResourcesRRC-Inactive-r17;
- spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on CSI-RS from the serving cell in the same band. The UE indicating support of this feature shall also indicate support of spatialRelation-SRS-PosBasedOnSSB-Serving-r16;
- spatialRelation-SRS-PosBasedOnPRS-Serving-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the serving cell in the same band. The UE indicating support of this feature shall also indicate support any of DL PRS Resources for DL AoD, DL PRS Resources for DL-TDOA or DL PRS Resources for Multi-RTT defined in TS37.355 [22], or srs-PosResourcesRRC-Inactive-r17;
- spatialRelation-SRS-PosBasedOnSRS-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SRS in the same band. The UE indicating support of this feature shall also indicate support of srs-PosResourcesRRC-Inactive-r17;
- spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on SSB from the neighbouring cell in the same band. The UE indicating support of this feature shall also indicate support of spatialRelation-SRS-PosBasedOnSSB-Serving-r16;
- spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 indicates whether the UE supports spatial relation for SRS for positioning based on PRS from the neighbouring cell in the same band. The UE indicating support of this feature shall also indicate support of spatialRelation-SRS-PosBasedOnPRS-Serving-r16.

NOTE: A PRS from a PRS-only TP is treated as PRS from a non-serving cell.

Band

No

N/A

FR2 only

sp-BeamReportPUCCH
Indicates support of semi-persistent ‘CRI/RSRP’ or ‘SSBRI/RSRP’ reporting using PUCCH formats 2, 3 and 4 in one slot.

Band

No

N/A

N/A

sp-BeamReportPUSCH
Indicates support of semi-persistent ‘CRI/RSRP’ or ‘SSBRI/RSRP’ reporting on PUSCH.

Band

No

N/A

N/A

sps-MulticastDCI-Format4-2-r17
Indicates whether the UE supports transmission and re-transmission scheduled by DCI format 4_2 with CRC scrambled with G-CS-RNTI for multicast SPS scheduling.

A UE that indicates support of this feature shall indicate support of sps-Multicast-r17.

Band

No

N/A

N/A

sps-MulticastMultiConfig-r17
Indicates whether the UE supports up to 8 SPS group-common PDSCH configurations per CFR for multicast on PCell. The value indicates the maximum number of activated SPS group-common PDSCH configurations per CFR for multicast.

The total number of SPS configurations for both multicast and unicast is no larger than 8 in a BWP of a serving cell. The total number of SPS configurations for both multicast and unicast in a cell group is no larger than 32.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE that indicates support of this feature shall indicate support of sps-Multicast-r17.

Band

No

N/A

N/A

sps-r16
Indicates whether the UE support of up to 8 configured SPS configurations in a BWP of a serving cell and up to 32 configured SPS configurations in a cell group. This field includes the following parameters:

- maxNumberConfigsPerBWP-r16 indicates the maximum number of active SPS configurations in a BWP of a serving cell.
- maxNumberConfigsAllCC-r16 indicates the maximum number of active SPS configurations across all serving cells in a MAC entity, and across MCG and SCG in case of NR-DC.

The UE can include this feature only if the UE indicates support of downlinkSPS.

NOTE:
- For all the reported bands in FR1, a same X1 value is reported for maxNumberConfigsAllCC-r16. For all the reported bands in FR2, a same X2 value is reported for maxNumberConfigsAllCC-r16.
- The total number of active SPS configurations across all serving cells in FR1 is no greater than X1.
- The total number of active SPS configurations across all serving cells in FR2 is no greater than X2.
- If the CA have some serving cell(s) in FR1 and some serving cell(s) in FR2, the total number of active SPS configurations across all serving cells is no greater than max(X1, X2).

Band

No

N/A

N/A

srs-AssocCSI-RS
Parameters for the calculation of the precoder for SRS transmission based on channel measurements using associated NZP CSI-RS resource (srs-AssocCSI-RS) as described in clause 6.1.1.2 of TS 38.214 [12]. UE supporting this feature shall also indicate support of non-codebook based PUSCH transmission.

This capability signalling includes list of the following parameters:
- maxNumberTxPortsPerResource indicates the maximum number of Tx ports in a resource;
- maxNumberResourcesPerBand indicates the maximum number of resources across all CCs within a band simultaneously;
- totalNumberTxPortsPerBand indicates the total number of Tx ports across all CCs within a band simultaneously.

Band

No

N/A

N/A

srs-combEight-r17
Indicates whether the UE supports comb-8 for SRS other than for positioning.

Band

No

N/A

N/A

srs-increasedRepetition-r17
Indicates whether the UE supports increased repetition patterns (8, 10, 12, 14 symbols) for SRS resource.

The UE supporting this feature shall also indicate the support of srs-StartAnyOFDM-Symbol-r16.

Band

No

N/A

N/A

srs-partialFreqSounding-r17
Indicates the support of partial frequency sounding for SRS for non-frequency hopping case.

The UE indicating support of this feature shall also indicate the support of srs-partialFrequencySounding-r17.

Band

No

N/A

N/A

srs-partialFrequencySounding-r17
Indicates whether the UE supports partial frequency sounding for SRS with frequency hopping.

Band

No

N/A

N/A

srs-PosResourcesRRC-Inactive-r17
Indicates support of positioning SRS transmission in RRC_INACTIVE for initial UL BWP. The capability signalling comprises the following parameters:

- maxNumberSRS-PosResourceSetPerBWP-r17 Indicates the max number of SRS Resource Sets for positioning supported by UE*;
- maxNumberSRS-PosResourcesPerBWP-r17 indicates the max number of P/SP SRS Resources for positioning;
- maxNumberSRS-ResourcesPerBWP-PerSlot-r17 indicates the max number of P/SP SRS Resources for positioning per slot;
- maxNumberPeriodicSRS-PosResources-r17 indicates the max number of periodic SRS Resources for positioning;
- maxNumberPeriodicSRS-PosResourcesPerSlot-r17 indicates the max number of periodic SRS Resources for positioning per slot;
- maxNumberPeriodicAndSemipersistentSRS-PosResources-r17 indicates the max number of P/SP SRS Resources for positioning;
- maxNumberPeriodicAndSemipersistentSRS-PosResourcesPerSlot-r17 indicates the max number of P/SP SRS Resources for positioning per slot;
- differentNumerologyBetweenSRSposAndInitialBWP-r17 indicates the support of different numerology between the SRS and the initial UL BWP;
- srsPosWithoutRestrictionOnBWP-r17 indicates the support of SRS operation without restriction on the BW;
- differentCenterFreqBetweenSRSposAndInitialBWP-r17 indicates the support of a different center frequency between the SRS for positioning and the initial UL BWP;
- switchingTimeSRS-TX-OtherTX-r17 indicates the switching time between SRS TX and other TX in initial UL BWP or RX in initial DL BWP;
- maxNumberSemiPersistentSRS-PosResources-r17 indicates the max number of semi-persistent SRS Resources for positioning;
- maxNumberSemiPersistentSRS-PosResourcesPerSlot-r17 indicates the max number of semi-persistent SRS Resources for positioning per slot.

NOTE: OLPC for SRS for positioning based on SSB from the last serving cell (the cell that releases UE from connection) is part of this feature. No dedicated capability signalling is intended for this component.

Band

No

N/A

N/A

srs-SemiPersistent-PosResourcesRRC-Inactive-r17
Indicates support of positioning SRS transmission in RRC_INACTIVE for initial UL BWP with semi-persistent SRS. UE indicating support of this feature shall indicate support of srs-PosResourcesRRC-Inactive-r17.

The capability signalling comprises the following parameters:
- maxNumOfSemiPersistentSRSposResources-r17 indicates the max number of semi-persistent SRS Resources for positioning;
- maxNumOfSemiPersistentSRSposResourcesPerSlot-r17 indicates the max number of semi-persistent SRS Resources for positioning per slot.

Band

No

N/A

N/A

srs-PortReport-r17
Indicates the maximum number of SRS ports for each UE reported quantity in reportQuantity-r17.

Band

No

N/A

N/A

srs-PortReportSP-AP-r17
Indicates that the UE supports the maximum number of SRS ports with semi-persistent/aperiodic capability value reporting.

The UE supporting this feature shall also indicate support of srs-PortReport-r17 and one of aperiodicBeamReport, sp-BeamReportPUCCH, sp-BeamReportPUSCH, ssb-csirs-SINR-measurement-r16, semi-PersistentL1-SINR-Report-PUCCH-r16 or semi-PersistentL1-SINR-Report-PUSCH-r16.

Band

No

N/A

N/A

srs-startRB-locationHoppingPartial-r17
Indicates whether the UE supports start RB location hopping in partial frequency SRS transmission across different SRS frequency hopping periods for periodic/semi-persistent/aperiodic SRS.

The UE supporting this feature shall also indicate the support of srs-partialFrequencySounding-r17.

Band

No

N/A

N/A

srs-TriggeringOffset-r17
Indicates the maximum number of configured available slots offsets for determining aperiodic SRS location based on available slot.

Band

No

N/A

N/A

srs-TriggeringDCI-r17
Indicates whether the UE supports triggering SRS in DCI 0_1/0_2 without data and without CSI.

Band

No

N/A

N/A

ssb-csirs-SINR-measurement-r16
Indicates the limitations of the UE support of SSB/CSI-RS for L1-SINR measurement.

This capability signalling includes list of the following parameters:

Per slot limitations:
- maxNumberSSB-CSIRS-OneTx-CMR-r16 indicates the maximum number of SSB/CSI-RS (1TX) across all CCs within a band for Channel Measurement Report
- maxNumberCSI-IM-NZP-IMR-res-r16 indicates the maximum number of CSI-IM/NZP-IMR resources across all CCs within a band
- maxNumberCSIRS-2Tx-res-r16 indicates the maximum number of CSI-RS (2TX) resources across all CCs within a band for Channel Measurement Report

Memory limitations:
- maxNumberSSB-CSIRS-res-r16 indicates the max number of SSB/CSI-RS resources across all CCs within a band as Channel Measurement Report
- maxNumberCSI-IM-NZP-IMR-res-mem-r16 indicates the maximum number of CSI-IM/NZP-IMR resources across all CCs within a band

Other limitations:
- supportedCSI-RS-Density-CMR-r16 indicates supported density of CSI-RS for Channel Measurement Report.
- maxNumberAperiodicCSI-RS-Res-r16 indicates the maximum number of aperiodic CSI-RS resources across all CCs within a band configured to measure L1-SINR (including CMR and IMR).
- supportedSINR-meas indicates the supported SINR measurements.
- supportedSINR-meas-r16 contains values {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR} representing {SSB as CMR with dedicated CSI-IM, SSB as CMR with dedicated NZP IMR, CSI-RS as CMR with dedicated NZP IMR configured, CSI-RS as CMR without dedicated IMR configured}.

supportedSINR-meas-v1670 indicates a 4-bit bitmap {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR}, where the leftmost bit corresponds to ssbWithCSI-IM, the next bit corresponds to ssbWithNZP-IMR and so on. UE indicating supportedSINR-meas-v1670 shall always indicate supportedSINR-meas-r16.

UE supporting this feature shall also indicate support of CSI-RS as CMR with dedicated CSI-IM.
UE indicating support of this feature shall also indicate support of periodicBeamReport and aperiodicBeamReport or sp-BeamReportPUCCH and sp-BeamReportPUSCH. UE indicating support of ssb-csirs-SINR-measurement-r16 shall support periodic and aperiodic L1-SINR report.

Band

No

N/A

N/A

sssg-Switching-1BitInd-r17
Indicates whether the UE supports 1-bit indication of SSSG switching between 2 SSSGs by scheduling DCI, and timer based SSSG switching, if pdcch-SkippingDurationList is not configured as specified in TS 38.213 [11], clause 10.4. UE supports search space set group switching capability-1 according to Table 10.4-1 of TS 38.213 [11].

Band

No

N/A

N/A

sssg-Switching-2BitInd-r17
Indicates whether the UE supports 2-bit indication of SSSG switching among 3 SSSGs by scheduling DCI and timer based SSSG switching, if pdcch-SkippingDurationList is not configured as specified in TS 38.213 [11], clause 10.4. UE supports search space set group switching capability-1 according to Table 10.4-1 of TS 38.213 [11].

UE indicating support of this feature shall also indicate support of sssg-Switching-1bitInd-r17.

Band

No

N/A

N/A

support64CandidateBeamRS-BFR-r16
Indicates UE support of configuring maximum 64 candidate beam RSs per BWP per CC. UE indicating support of this feature shall also indicate support of maxNumberCSI-RS-BFD, maxNumberSSB-BFD and maxNumberCSI-RS-SSB-CBD.

Band

No

N/A

N/A

supportCodeWordSoftCombining-r16
Indicates whether UE supports codeword soft combining for FDMSchemeB. UE indicates support of this feature depends on whether the supportFDM-SchemeB-r16 is also supported.

Band

No

N/A

N/A

supportFDM-SchemeA-r16
Indicates whether UE supports single DCI based FDMSchemeA.

Band

No

N/A

N/A

supportInter-slotTDM-r16
Indicates whether UE supports single-DCI based inter-slot TDM. This capability signalling includes the following:
- supportRepNumPDSCH-TDRA-r16 indicates support of RepNumR16 in PDSCH-TimeDomainResourceAllocation and the maximum value of RepNumR16;
- maxTBS-Size-r16 indicates maximum TBS size;
- maxNumberTCI-states-r16 indicates the maximum number of TCI states.

Band

No

N/A

N/A

supportNewDMRS-Port-r16
Indicates whether UE supports new DMRS port entry {0,2,3}. UE supports this feature should indicate support singleDCI-SDM-scheme-r16 for the band.

Band

No

N/A

N/A

supportRepNumPDSCH-TDRA-DCI-1-2-r17
Indicates support of repetitionNumber-v1730 in PDSCH-TimeDomainResourceAllocation for DCI format 1_2 and the maximum value of repetitionNumber-v1730. The UE indicating support of this field shall also indicate support of dci-Format1-2And0-2-r16.

Band

No

N/A

N/A

supportTDM-SchemeA-r16
Indicates whether UE supports single DCI based TDMSchemeA. The capability signalling includes the maximum TBS size.

Band

No

N/A

N/A

supportTwoPortDL-PTRS-r16
Indicates whether UE supports 2-port DL PT-RS. UE supports this feature should indicate support singleDCI-SDM-scheme-r16 for the band.

Band

No

N/A

N/A

ta-BasedPDC-NTN-SharedSpectrumChAccess-r17
Indicates whether the UE supports propagation delay compensation based on legacy TA procedure for NTN and shared spectrum channel access.

Band

No

N/A

N/A

tb-ProcessingMultiSlotPUSCH-r17
Indicates whether UE supports TB processing over multi-slot PUSCH for DG and Type 2 CG without repetition in RRC connected mode.

Band

No

N/A

N/A

tb-ProcessingRepMultiSlotPUSCH-r17
Indicates whether UE supports repetition of TB processing over multi-slot PUSCH in RRC connected mode.

UE supporting this feature shall also indicates support of tb-ProcessingMultiSlotPUSCH-r17.

Band

No

N/A

N/A

tci-StatePDSCH
Defines support of TCI-States for PDSCH. The capability signalling comprises the following parameters:

- maxNumberConfiguredTCIstatesPerCC indicates the maximum number of configured TCI-states per CC for PDSCH. For FR2, the UE is mandated to set the value at least to 64 (i.e. value 128 is an optional value). For FR1, the UE is mandated to set these values at least to the maximum number of allowed SSBs in the supported band;
- maxNumberActiveTCI-PerBWP indicates the maximum number of activated TCI-states per BWP per CC, including control and data. If a UE reports X active TCI state(s), it is not expected that more than X active QCL type D assumption(s) for any PDSCH and any CORESETs for a given BWP of a serving cell become active for the UE. The UE shall include this field.

Note the UE is required to track only the active TCI states. The UE is mandated to report tci-StatePDSCH.

Band

Yes

N/A

N/A

timeBasedCondHandover-r17
Indicates whether the UE supports time based conditional handover, i.e., CondEventT1 as specified in TS 38.331 [9]. A UE supporting this feature shall also indicate the support of condHandover-r16 for NTN bands and the support of nonTerrestrialNetwork-r17.

UE shall set the capability value consistently for all FDD-FR1 NTN bands.

Band

No

N/A

N/A

triggeredHARQ-CodebookRetx-r17
Indicates whether the UE supports triggered HARQ-ACK codebook re-transmission from an earlier PUCCH slot based on the triggering information in DCI format 1_1 and DCI format 1_2 (for a UE supporting DCI format 1_2 as indicated in dci-Format1-2And0-2-r16) and support the related PHY priority handling in terms of HARQ-ACK codebook selection and the applicable PUCCH configuration (for a UE supporting two HARQ-ACK codebooks / PUCCH config as indicated in twoHARQ-ACK-Codebook-type1-r16). The capability signalling comprises the following parameters:

- minHARQ-Retx-Offset-r17 indicates minimum value for the HARQ re-tx offset. Value n-7 corresponds to -7, value n-5 corresponds to -5, and so on.
- maxHARQ-Retx-Offset-r17 indicates maximum value for the HARQ re-tx offset.

NOTE: The minimum requirement for minHARQ-Retx-Offset-r17 and maxHARQ-Retx-Offset-r17 is valid for HARQ CBs consisted of HARQ Processes with a single HARQ bit per HARQ Process ID.

Band

No

N/A

N/A

trs-AdditionalBandwidth-r16
Indicates the UE supported TRS bandwidths, in addition to 52 RBs, for a 10MHz UE channel bandwidth. This field only applies for the BWPs configured with 52 RBs size and 15kHz SCS, in FDD bands.

Value trs-AddBW-Set1 indicates 28, 32, 36, 40, 44, 48 RBs.
Value trs-AddBW-Set2 indicates 32, 36, 40, 44, 48 RBs.

Band

No

FDD only

FR1 only

twoHARQ-ACK-CodebookForUnicastAndMulticast-r17
Indicates whether the UE supports two HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different priorities for unicast and multicast at a UE.

For TN, the UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands and all TDD-FR2 bands, associated with supported shared and non-shared spectrum respectively. For NTN, UE shall set the capability value consistently for all FDD-FR1 NTN bands.

A UE supporting this feature shall also indicate support of priorityIndicatorInDCI-Multicast-r17.

Band

No

N/A

N/A

twoPortsPTRS-UL
Defines whether UE supports PT-RS with 2 antenna ports for UL transmission.

Band

No

N/A

N/A

type1-HARQ-Codebook-r17
Indicates whether the UE supports Type-1 HARQ codebook enhancements when there are feedback-disabled HARQ processes**.* UE indicating support of this feature shall also indicate support of harq-FeedbackDisabled-r17.
This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35].

Band

No

N/A

N/A

type2-HARQ-Codebook-r17
Indicates whether the UE supports Type-2 HARQ codebook enhancements when there are feedback-disabled HARQ processes**.* UE indicating support of this feature shall also indicate support of harq-FeedbackDisabled-r17.
This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35].

Band

No

N/A

N/A

type1-PUSCH-RepetitionMultiSlots-v1650
Indicates whether the UE supports Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 1 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, type1-PUSCH-RepetitionMultiSlots-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes type1-PUSCH-RepetitionMultiSlots-v1650 if type1-PUSCH-RepetitionMultiSlots is absent.

Band

No

N/A

N/A

type2-PUSCH-RepetitionMultiSlots-v1650
Indicates whether the UE supports Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value equal to 2, 4, or 8 with a single repetition of the transport block within each slot, and redundancy version pattern as indicated by UL-TWG-RV-rep. A UE supporting this feature shall also support Type 2 PUSCH transmissions with configured grant as specified in TS 38.214 [12] with UL-TWG-repK value of one. This applies only to non-shared spectrum channel access. For shared spectrum channel access, type2-PUSCH-RepetitionMultiSlots-r16 applies. UE shall set the capability value consistently for all FDD-FR1 bands, all TDD-FR1 bands, all TDD-FR2-1 bands and all TDD-FR2-2 bands respectively.

The UE only includes type2-PUSCH-RepetitionMultiSlots-v1650 if type2-PUSCH-RepetitionMultiSlots is absent.

Band

No

N/A

N/A

type3-HARQ-Codebook-r17
Indicates whether the UE supports Type-3 HARQ codebook enhancements when there are feedback-disabled HARQ processes**.* UE indicating support of this feature shall also indicate support of harq-FeedbackDisabled-r17.
This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35].

Band

No

N/A

N/A

txDiversity-r16
Indicates whether the UE supports transparent Tx diversity requirements as specified in the suffix G clauses of TS 38.101-1 [2] (see also clauses 4.2 and 4.3 of TS38.101-1 [2]).

Band

No

N/A

FR1 only

ue-OneShotUL-TimingAdj-r17
Indicates whether the UE supports one shot large UL timing adjustment.

UE indicating support of this feature shall indicate support of ue-PowerClass-v1700 set to ‘pc6’.

Band

No

N/A

FR2 only

ue-PowerClass, ue-PowerClass-v1610, ue-PowerClass-v1700
For FR1, if the UE supports the different UE power class than the default UE power class as defined in clause 6.2 of TS 38.101-1 [2], or in clause 6.2 of TS 38.101-5 [34], the UE shall report the supported UE power class in this field. For FR2, UE shall report the supported UE power class as defined in clause 6 and 7 of TS 38.101-2 [3] in this field.

UE indicating support for pc6 supports the enhanced intra-NR RRM and demodulation processing requirements for FR2 to support high speed up to 350 km/h as specified in TS 38.133 [5]. This capability is not applicable to IAB-MT. The power class pc7 is only applicable for RedCap UEs operation in FR2.

Band

Yes

N/A

N/A

ue-specific-K-Offset-r17
Indicates whether the UE supports the reception of UE-specific K_offset comprised of the following functional components:

− Support of reception of UE-specific K_offset via MAC-CE
− Support of determining the timing of PUSCH, PUCCH, CSI reference resource, transmission of aperiodic SRS, activation of TA command, first PUSCH transmission in CG Type 2 with UE-specific Koffset

UE indicating support of this feature shall also indicate support of uplinkPreCompensation-r17 and uplink-TA-Reporting-r17 for this band.* This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35].

Band

No

N/A

N/A

ul-GapFR2-r17
Indicates whether the UE supports FR2 UL gap to perform BPS sensing for Tx power management by the use of uplink gap patterns as specified in TS 38.133 [5] if UE supports a band in FR2.

Band

No

No

FR2 only

unifiedJointTCI-BeamAlignDLRS-r17
Indicates the support of beam misalignment between the DL source RS in the TCI state to provide spatial relation indication and the PL-RS.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

FR2 only

unifiedJointTCI-commonMultiCC-r17
Indicates the support of common multi-CC TCI state ID update and activation.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

N/A

unifiedJointTCI-InterCell-r17
Indicates the support of Unified TCI with joint DL/UL TCI update for inter-cell beam management including following parameters:

additionalMAC-CE-PerCC-r17 indicates the number of K additional MAC-CEs to indicate joint TCI states per CC in a band.
additionalMAC-CE-AcrossCC-r17 indicates the number of K additional MAC-CE activated joint TCI states across all CC(s) in a band.

A UE indicating support of this shall also indicate support of unifiedJointTCI-r17 and unifiedJointTCI-mTRP-InterCell-BM-r17.

NOTE: A UE that supports unifiedJointTCI-InterCell-r17 supports K additional MAC-CE activated joint TCI states across all CC(s) in a band in addition to the maximum number of MAC-CE activated joint TCI states across all CC(s) in a band signalled in unifiedJointTCI-r17. The signalled value in additionalMAC-CE-AcrossCC-r17 plus the signalled value in maxActivatedTCIAcrossCC-r17 determine the maximum number of MAC-CE activated joint TCI states across all CC(s) in a band that are applied to intra and inter-cell beam management jointly.

Band

No

N/A

N/A

unifiedJointTCI-Legacy-CORESET0-r17
Indicates the support of indication/configuration of R17 TCI states for CORESET #0 and the respective PDSCH reception reusing the Rel-15/16 signalling/configuration design(s).

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

N/A

unifiedJointTCI-Legacy-SRS-r17
Indicates the support of indication/configuration of R17 TCI states for SRS (except for periodic/semi-persistent SRS for BM) reusing the Rel-15/16 signalling/configuration design(s).

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

N/A

unifiedJointTCI-Legacy-r17
Indicates the support of indication/configuration of R17 TCI states for aperiodic CSI-RS, PDCCH, PDSCH (except for TRS and for CORESET #0 and the respective PDSCH reception) reusing the Rel-15/16 signalling/configuration design(s).

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

N/A

unifiedJointTCI-ListSharingCA-r17
Indicates the support of reference BWP/serving cell index to indicate reference TCI state list shared by multiple BWPs/serving cells. The value indicates the maximum number of configured joint TCI state lists across all BWPs and all Serving cells in a band.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17. A UE that supports CA and unifiedJointTCI-r17 shall indicate support of this feature.

Band

No

N/A

N/A

unifiedJointTCI-mTRP-InterCell-BM-r17
Indicates the support of inter-cell beam measurement and reporting for inter-cell BM and mTRP. This feature includes support of L1-RSRP measurement and reporting on SSB(s) with PCI(s) different from serving cell PCI (additional PCI) and support of up to K SSBRI-RSRP pairs in one report where a pair is associated with a PCI different from serving cell PCI can be reported, where K is equal to maxNumberNonGroupBeamReporting.

This feature also includes following parameters:
maxNumAdditionalPCI-L1-RSRP-r17 indicates the maximum number of RRC-configured PCI(s) different from serving cell PCI for L1-RSRP measurement.
maxNumSSB-ResourceL1-RSRP-AcrossCC-r17 indicates the maximum number of SSB resources configured to measure L1-RSRP within a slot with PCI(s) same as or different from serving cell PCI [across all CC].

NOTE: maxNumSSBResource-L1-RSRP-AcrossCC-r17 is also counted in maxTotalResourcesForOneFreqRange-r16/maxTotalResourcesForAcrossFreqRanges-r16.

Band

No

N/A

N/A

unifiedJointTCI-multiMAC-CE-r17
Indicates the support of unified TCI state operation with joint DL/UL TCI update for intra- and inter-cell beam management with more than one MAC-CE activated joint TCI state per CC with MAC CE and DCI based TCI state indication in DCI formats 1_1 and 1_2 with and without DL assignment.

This capability signalling includes the following parameters:
minBeamApplicationTime-r17 indicates the minimum beam application time in Y symbols per SCS indicated only for FR2.
maxNumMAC-CE-PerCC-r17 indicates the maximum number of MAC-CE activated joint TCI states per CC in a band.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

NOTE 1: The maximum number of MAC-CE activated joint TCI states across all CC(s) in a band for more than one MAC-CE activated joint TCI state is signaled in unifiedJointTCI-r17.
NOTE 2: Activated joint TCI state(s) include all PDCCH/PDSCH receptions and PUSCH/PUCCH.

Band

No

N/A

N/A

unifiedJointTCI-PC-association-r17
Indicates the support of association between TCI state and UL PC settings except for PL RS for PUCCH, PUSCH, and SRS.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

N/A

unifiedJointTCI-perBWP-CA-r17
Indicates the support of TCI state list configuration per BWP when CA is configured.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17.

Band

No

N/A

N/A

unifiedJointTCI-r17
Indicates the support of unified TCI state operation with joint DL/UL TCI update for intra-cell beam management including the support of:

− One MAC-CE activated joint TCI state per CC in a band
− TCI state indication for update and activation of MAC CE based TCI state indication for one active TCI state

The capability signalling comprises the following parameters:
maxConfiguredJointTCI-r17 indicates the maximum number of configured joint TCI states per BWP per CC in a band.
maxActivatedTCIAcrossCC-r17 indicates the maximum number of MAC-CE activated joint TCI states across all CC(s) in a band.

If a UE supports unifiedJointTCI-InterCell-r17, the signalled component values (except additionalMAC-CE-AcrossCC-r17) also apply to inter-cell beam management,

NOTE: Activated joint TCI state(s) include all PDCCH/PDSCH receptions and PUSCH/PUCCH transmissions.

Band

No

N/A

N/A

unifiedJointTCI-SCellBFR-r17
Indicates the support of SCell BFR with unified TCI operation. The maximum number of CCs configured with SCell BFR with unified TCI framework in a band with SpCell BFR is given by maxNumberSCellBFR-r16. The UE supporting this feature assumes that maxNumberSCellBFR-r16 includes SpCell.

Band

No

N/A

N/A

unifiedSeparateTCI-commonMultiCC-r17
Indicates the Common multi-CC DL/UL-TCI state ID update and activation.

The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17.

Band

No

N/A

N/A

unifiedSeparateTCI-InterCell-r17
Indicates the support of unified TCI with separate DL/UL TCI update for inter-cell beam management with more than one MAC-CE activated separate TCI state per CC.

This feature also includes following parameters:
k-DL-PerCC-r17 indicates the number of additional MAC-CE activated DL TCI states per CC in a band
k-UL-PerCC-r17 indicates the number of additional MAC-CE activated UL TCI states per CC in a band
k-DL-AcrossCC-r17 indicates the number of additional MAC-CE activated DL TCI states across all CC(s) in a band
k-UL-AcrossCC-r17 indicates the number of additional MAC-CE activated UL TCI states across all CC(s) in a band

The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17.

NOTE: A UE that supports this feature supports K additional MAC-CE activated DL and K additional MAC-CE activated UL TCI states across all CC(s) in a band in addition to the maximum number of MAC-CE activated DL and UL TCI states across all CC(s) in a band signalled in unifiedSeparateTCI-r17. The signalled value in k-DL-AcrossCC-r17 (k-UL-AcrossCC-r17) plus the signalled value in maxActivatedDL-TCIAcrossCC-r17 (maxActivatedUL-TCIAcrossCC-r17) determine the maximum number of MAC-CE activated DL (UL) TCI states across all CC(s) in a band that are applied to intra and inter-cell beam management jointly.

Band

No

N/A

N/A

unifiedSeparateTCI-ListSharingCA-r17
Indicates the support of reference BWP/serving cell configured with reference TCI state pool shared by a set of BWPs/serving cells. The value indicates the maximum number of configured DL/UL TCI state pools across all BWPs and all serving cells in a band.

Band

No

N/A

N/A

unifiedSeparateTCI-multiMAC-CE-r17
Indicates TCI state indication for update and activation a) MAC-CE+DCI-based TCI state indication (use of DCI formats 1_1/1_2 with DL assignment)
and b) MAC-CE+DCI-based TCI state indication (use of DCI formats 1_1/1_2 without DL assignment).

This capability signalling includes the following parameters:
minBeamApplicationTime-r17 indicates the minimum beam application time in Y symbols per SCS.
maxActivatedDL-TCIPerCC-r17 indicates the maximum number of MAC-CE activated DL TCI states per CC in a band.
maxActivatedUL-TCIPerCC-r17 indicates the maximum number of MAC-CE activated UL TCI states per CC in a band.

The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17.

Band

No

N/A

N/A

unifiedSeparateTCI-perBWP-CA-r17
Indicates the support of DL/UL TCI state pool configuration per BWP for CA mode.

The UE indicating support of this feature shall also indicate support of unifiedSeparateTCI-r17.

Band

No

N/A

N/A

unifiedSeparateTCI-r17
Indicates the support of unified TCI state operation with joint DL/UL TCI update for intra-cell beam management including the support of:

− One MAC-CE activated DL TCI state per CC in a band
− One MAC-CE activated UL TCI state per CC in a band
− TCI state indication for update and activation including MAC CE based TCI state indication for one active DL/UL TCI state

The capability signalling comprises the following parameters:
maxConfiguredDL-TCI-r17 indicates the maximum number of configured DL TCI states per BWP per CC.
maxConfiguredUL-TCI-r17 indicates the maximum number of configured UL TCI states per BWP per CC.
maxActivatedDL-TCIAcrossCC-r17 indicates the maximum number of MAC-CE activated DL TCI states across all CC(s) in a band.
maxActivatedUL-TCIAcrossCC-r17 indicates the maximum number of MAC-CE activated UL TCI states across all CC(s) in a band.

The UE indicating support of this feature shall also indicate support of unifiedJointTCI-r17. If a UE supports unifiedSeparateTCI-InterCell-r17, the maxConfiguredDL-TCI-r17 and maxConfiguredUL-TCI-r17 apply to intra- and inter-cell beam management jointly.

Band

No

N/A

N/A

uplinkBeamManagement
Defines support of beam management for UL. This capability signalling comprises the following parameters:

maxNumberSRS-ResourcePerSet-BM indicates the maximum number of SRS resources per SRS resource set configurable for beam management, supported by the UE.
maxNumberSRS-ResourceSet indicates the maximum number of SRS resource sets configurable for beam management, supported by the UE.

If the UE does not set beamCorrespondenceWithoutUL-BeamSweeping to supported, the UE shall report this capability. This feature is optional for the UE that supports beam correspondence without uplink beam sweeping as defined in clause 6.6, TS 38.101-2 [3].

NOTE: The network uses maxNumberSRS-ResourceSet to determine the maximum number of SRS resource sets that can be configured to the UE for periodic/semi-persistent/aperiodic configurations as below:

 Maximum number of SRS resource sets across all time domain behaviour (periodic/semi-persistent/aperiodic) reported in maxNumberSRS-ResourceSet   Additional constraint on the maximum number of SRS resource sets configured to the UE for each supported time domain behaviour (periodic/semi-persistent/aperiodic)

... omitted example table of constraints ...

Band

No

N/A

FR2 only

uplinkPreCompensation-r17
Indicates whether the UE supports the uplink time and frequency pre-compensation and timing relationship enhancements comprised of the following functional components:

− Support of UE specific TA calculation based on its GNSS-acquired position and the serving satellite ephemeris.
− Support of common TA calculation according to the parameters provided by the network (UE considers common TA as 0 if the parameters are not provided)
− For TA update in RRC_CONNECTED state, support of combination of both open (i.e. UE autonomous TA estimation, and common TA estimation) and closed (i.e., received TA commands) control loops
− Support of pre-compensation of the calculated TA in its uplink transmissions
− Support of estimating UE-gNB RTT and delaying the start of RAR window by UE-gNB RTT
− Support of frequency pre-compensation to counter shift the Doppler experienced on the service link
− Support of determining timing of the scheduling of PUSCH, PUCCH and PDCCH ordered PRACH, CSI reference resource, transmission of aperiodic SRS activation of TA command, first PUSCH transmission in CG Type 2 with cell-specific K_offset if indicated
− Support of determining timing of the UE action and assumption on a downlink configuration carried by MAC CE command by K_mac if it is indicated and determining the timing of PDCCH monitoring in recovery search space using K_mac during beam failure recovery procedure
− Support of UE receiving cell-specific K_offset/K_mac in system information

Support of this feature in NTN bands is mandatory for UEs supporting nonTerrestrialNetwork-r17. This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35].

Band

CY

N/A

N/A

uplink-TA-Reporting-r17
Indicates whether the UE supports UE reporting of information related to TA pre-compensation as specified in TS 38.321 [8]**.*

UE indicating support of this feature shall also indicate support of uplinkPreCompensation-r17 for this band. This field is only applicable for bands in Table 5.2.2-1 in TS 38.101-5 [34] and HAPS operation bands in clause 5.2 of TS 38.104 [35].

Band

No

N/A

N/A

UE Capability Enquiry - NR

Followings overall structure of UE Capability Enquiries for NR.

 

UECapabilityEnquiry ::= SEQUENCE {

   rrc-TransactionIdentifier       RRC-TransactionIdentifier,

   criticalExtensions CHOICE {

      ueCapabilityEnquiry           UECapabilityEnquiry-IEs,

      criticalExtensionsFuture SEQUENCE {}

   }

}

 

UECapabilityEnquiry-IEs ::= SEQUENCE {

   ue-CapabilityRAT-RequestList     UE-CapabilityRAT-RequestList,

   lateNonCriticalExtension         OCTET STRING            OPTIONAL,

   ue-CapabilityEnquiryExt      OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL

}

 

UECapabilityEnquiry-v1560-IEs ::= SEQUENCE {

   capabilityRequestFilterCommon     UE-CapabilityRequestFilterCommon     OPTIONAL, -- Need N

   nonCriticalExtension              UECapabilityEnquiry-v1610-IEs        OPTIONAL

}

 

UECapabilityEnquiry-v1610-IEs ::= SEQUENCE {

   rrc-SegAllowed-r16                ENUMERATED {enabled}          OPTIONAL, -- Need N

   nonCriticalExtension              SEQUENCE {} OPTIONAL

}

 

UE-CapabilityRAT-RequestList ::= SEQUENCE (SIZE (1..maxRAT-CapabilityContainers))

                                     OF UE-CapabilityRAT-Request

 

UE-CapabilityRAT-Request ::= SEQUENCE {

   rat-Type RAT-Type,

   capabilityRequestFilter           OCTET STRING                 OPTIONAL, -- Need N

   ...

}

 

UE-CapabilityRequestFilterNR ::= SEQUENCE {

   frequencyBandListFilter           FreqBandList                 OPTIONAL, -- Need N

   nonCriticalExtension              UE-CapabilityRequestFilterNR-v1540     OPTIONAL

}

 

UE-CapabilityRequestFilterNR-v1540 ::= SEQUENCE {

   srs-SwitchingTimeRequest          ENUMERATED {true}            OPTIONAL, -- Need N

   nonCriticalExtension              SEQUENCE {} OPTIONAL

}

Example 01 > nr single band

  message c1: ueCapabilityEnquiry: {

    rrc-TransactionIdentifier 0,

    criticalExtensions ueCapabilityEnquiry: {

      ue-CapabilityRAT-RequestList {

        {

          rat-Type nr,

          capabilityRequestFilter {

            frequencyBandListFilter {

              bandInformationNR: {

                bandNR 78

              }

            }

          }

        }

      },

      ue-CapabilityEnquiryExt {

        nonCriticalExtension {

          rrc-SegAllowed-r16 enabled

        }

      }

    }

  }

Example 02 > nr multi band

{

  message c1: ueCapabilityEnquiry: {

    rrc-TransactionIdentifier 0,

    criticalExtensions ueCapabilityEnquiry: {

      ue-CapabilityRAT-RequestList {

        {

          rat-Type nr,

          capabilityRequestFilter {

            frequencyBandListFilter {

              bandInformationNR: {

                bandNR 1

              },

              bandInformationNR: {

                bandNR 2

              },

              bandInformationNR: {

                bandNR 3

              },

              bandInformationNR: {

                bandNR 4

              },

              bandInformationNR: {

                bandNR 5

              },

              bandInformationNR: {

                bandNR 6

              },

              bandInformationNR: {

                bandNR 7

              },

              bandInformationNR: {

                bandNR 8

              },

              bandInformationNR: {

                bandNR 9

              },

              bandInformationNR: {

                bandNR 10

              },

              bandInformationNR: {

                bandNR 41

              },

              bandInformationNR: {

                bandNR 78

              },

              bandInformationNR: {

                bandNR 79

              },

              bandInformationNR: {

                bandNR 80

              },

              bandInformationNR: {

                bandNR 81

              },

              bandInformationNR: {

                bandNR 82

              },

              bandInformationNR: {

                bandNR 83

              },

              bandInformationNR: {

                bandNR 84

              },

              bandInformationNR: {

                bandNR 86

              },

              bandInformationNR: {

                bandNR 89

              }

            }

          }

        }

      },

      ue-CapabilityEnquiryExt {

        nonCriticalExtension {

          rrc-SegAllowed-r16 enabled

        }

      }

    }

  }

}

UE Capability Information - NR

Following is the RRC message structure of UE capability Information message. But it may be too complicated and in many cases too confusing as well because of too many parameters and too complicated inter-dependencies among multiple parameters. I think the best way is to check out specific examples for various cases.

UECapabilityInformation ::= SEQUENCE {

     rrc-TransactionIdentifier               RRC-TransactionIdentifier,

     criticalExtensions CHOICE {

          ueCapabilityInformation            UECapabilityInformation-IEs,

          criticalExtensionsFuture           SEQUENCE {}

     }

}

 

UECapabilityInformation-IEs ::= SEQUENCE {

    ue-CapabilityRAT-ContainerList           UE-CapabilityRAT-ContainerList OPTIONAL,

    lateNonCriticalExtension                 OCTET STRING OPTIONAL,

    nonCriticalExtension                     SEQUENCE{} OPTIONAL

}

 

UE-CapabilityRAT-ContainerList ::=SEQUENCE (SIZE (0..maxRAT-CapabilityContainers)) OF UE-     CapabilityRAT-Container

    UE-CapabilityRAT-Container ::= SEQUENCE {

        rat-Type                            RAT-Type,

        ue-CapabilityRAT-Container          OCTET STRING

    }

 

 

RAT-Type ::= ENUMERATED {nr, eutra-nr, eutra, spare1, ...}

 

 

UE-NR-Capability ::= SEQUENCE {

   accessStratumRelease                AccessStratumRelease,

   pdcp-Parameters                     PDCP-Parameters,

   rlc-Parameters                      RLC-Parameters OPTIONAL,

   mac-Parameters                      MAC-Parameters OPTIONAL,   

   phy-Parameters                      Phy-Parameters,

   rf-Parameters                       RF-Parameters,

   measAndMobParameters                MeasAndMobParameters OPTIONAL,

   fdd-Add-UE-NR-Capabilities          UE-NR-CapabilityAddXDD-Mode OPTIONAL,

   tdd-Add-UE-NR-Capabilities          UE-NR-CapabilityAddXDD-Mode OPTIONAL,

   fr1-Add-UE-NR-Capabilities          UE-NR-CapabilityAddFRX-Mode OPTIONAL,

   fr2-Add-UE-NR-Capabilities          UE-NR-CapabilityAddFRX-Mode OPTIONAL,

   featureSets                         FeatureSets OPTIONAL,

   featureSetCombinations              SEQUENCE (SIZE (1..maxFeatureSetCombinations))

                                                 OF FeatureSetCombination OPTIONAL,

   lateNonCriticalExtension            OCTET STRING OPTIONAL,

   nonCriticalExtension                UE-NR-Capability-v1530 OPTIONAL

}

 

UE-NR-CapabilityAddXDD-Mode ::= SEQUENCE {

   phy-ParametersXDD-Diff             Phy-ParametersXDD-Diff OPTIONAL,

   mac-ParametersXDD-Diff             MAC-ParametersXDD-Diff OPTIONAL,

   measAndMobParametersXDD-Diff       MeasAndMobParametersXDD-Diff OPTIONAL

}

 

UE-NR-CapabilityAddXDD-Mode-v1530 ::= SEQUENCE {

   eutra-ParametersXDD-Diff           EUTRA-ParametersXDD-Diff

}

 

UE-NR-CapabilityAddFRX-Mode ::= SEQUENCE {

   phy-ParametersFRX-Diff             Phy-ParametersFRX-Diff OPTIONAL,

   measAndMobParametersFRX-Diff       MeasAndMobParametersFRX-Diff OPTIONAL

}

 

 

UE-NR-CapabilityAddFRX-Mode-v1540 ::= SEQUENCE {

   ims-ParametersFRX-Diff            IMS-ParametersFRX-Diff OPTIONAL

}

 

UE-NR-Capability-v1530 ::= SEQUENCE {

   fdd-Add-UE-NR-Capabilities-v1530   UE-NR-CapabilityAddXDD-Mode-v1530 OPTIONAL,

   tdd-Add-UE-NR-Capabilities-v1530   UE-NR-CapabilityAddXDD-Mode-v1530 OPTIONAL,

   dummy                              ENUMERATED {supported} OPTIONAL,

   interRAT-Parameters                InterRAT-Parameters OPTIONAL,

   inactiveState                      ENUMERATED {supported} OPTIONAL,

   delayBudgetReporting               ENUMERATED {supported} OPTIONAL,

   nonCriticalExtension               UE-NR-Capability-v1540 OPTIONAL

}

 

UE-NR-Capability-v1540 ::= SEQUENCE {

   sdap-Parameters                   SDAP-Parameters OPTIONAL,

   overheatingInd                    ENUMERATED {supported} OPTIONAL,

   ims-Parameters                    IMS-Parameters OPTIONAL,

   fr1-Add-UE-NR-Capabilities-v1540  UE-NR-CapabilityAddFRX-Mode-v1540 OPTIONAL,

   fr2-Add-UE-NR-Capabilities-v1540  UE-NR-CapabilityAddFRX-Mode-v1540 OPTIONAL,

   fr1-fr2-Add-UE-NR-Capabilities    UE-NR-CapabilityAddFRX-Mode OPTIONAL,

   nonCriticalExtension              UE-NR-Capability-v1550 OPTIONAL

}

 

UE-NR-Capability-v1550 ::= SEQUENCE {

   reducedCP-Latency                ENUMERATED {supported} OPTIONAL,

   nonCriticalExtension             SEQUENCE {} OPTIONAL

}

 

UE-EUTRA-Capability-v1510-IEs ::= SEQUENCE {

    irat-ParametersNR-r15                   IRAT-ParametersNR-r15                   OPTIONAL,

    featureSetsEUTRA-r15                    FeatureSetsEUTRA-r15                    OPTIONAL,

    pdcp-ParametersNR-r15                   PDCP-ParametersNR-r15                   OPTIONAL,

    fdd-Add-UE-EUTRA-Capabilities-v1510     UE-EUTRA-CapabilityAddXDD-Mode-v1510    OPTIONAL,

    tdd-Add-UE-EUTRA-Capabilities-v1510     UE-EUTRA-CapabilityAddXDD-Mode-v1510    OPTIONAL,

    nonCriticalExtension                    UE-EUTRA-Capability-v1520-IEs           OPTIONAL

}

 

IRAT-ParametersNR-r15 ::=       SEQUENCE {

    en-DC-r15                       ENUMERATED {supported}                      OPTIONAL,

    eventB2-r15                     ENUMERATED {supported}                      OPTIONAL,

    supportedBandListNR-r15         SupportedBandListNR-r15                     OPTIONAL

}

 

UE-EUTRA-Capability-v1520-IEs ::= SEQUENCE {

    measParameters-v1520                    MeasParameters-v1520,   

    nonCriticalExtension                    SEQUENCE {}     OPTIONAL

}

 

UE-EUTRA-CapabilityAddXDD-Mode-v1510 ::=    SEQUENCE {

    pdcp-ParametersNR-r15                   PDCP-ParametersNR-r15       OPTIONAL

}

 

PDCP-ParametersNR-r15 ::=       SEQUENCE {

    rohc-Profiles-r15                   ROHC-ProfileSupportList-r15,

    rohc-ContextMaxSessions-r15         ENUMERATED {

                                            cs2, cs4, cs8, cs12, cs16, cs24, cs32,

                                            cs48, cs64, cs128, cs256, cs512, cs1024,

                                            cs16384, spare2, spare1}            DEFAULT cs16,

    rohc-ProfilesUL-Only-r15                SEQUENCE {

        profile0x0006-r15                       BOOLEAN

    },

    rohc-ContextContinue-r15            ENUMERATED {supported}              OPTIONAL,

    outOfOrderDelivery-r15              ENUMERATED {supported}              OPTIONAL,

    sn-SizeLo-r15                       ENUMERATED {supported}              OPTIONAL,

    ims-VoiceOverNR-PDCP-MCG-Bearer-r15 ENUMERATED {supported}              OPTIONAL,

    ims-VoiceOverNR-PDCP-SCG-Bearer-r15 ENUMERATED {supported}              OPTIONAL

}

 

UE-MRDC-Capability ::=  SEQUENCE {

    measParametersMRDC                  MeasParametersMRDC                  OPTIONAL,

    rf-ParametersMRDC                   RF-ParametersMRDC,

    generalParametersMRDC               GeneralParametersMRDC-XDD-Diff      OPTIONAL,

    fdd-Add-UE-MRDC-Capabilities        UE-MRDC-CapabilityAddXDD-Mode       OPTIONAL,

    tdd-Add-UE-MRDC-Capabilities        UE-MRDC-CapabilityAddXDD-Mode       OPTIONAL,

    fr1-Add-UE-MRDC-Capabilities        UE-MRDC-CapabilityAddFRX-Mode       OPTIONAL,

    fr2-Add-UE-MRDC-Capabilities        UE-MRDC-CapabilityAddFRX-Mode       OPTIONAL,

    featureSetCombinations              SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OPTIONAL,

    lateNonCriticalExtension            OCTET STRING                        OPTIONAL,

    nonCriticalExtension                SEQUENCE {}                         OPTIONAL

}

 

UE-MRDC-CapabilityAddXDD-Mode ::=   SEQUENCE {

    measParametersMRDC-XDD-Diff     MeasParametersMRDC-XDD-Diff     OPTIONAL,

    generalParametersMRDC-XDD-Diff      GeneralParametersMRDC-XDD-Diff      OPTIONAL

}

 

UE-MRDC-CapabilityAddFRX-Mode ::=   SEQUENCE {

    measParametersMRDC-FRX-Diff     MeasParametersMRDC-FRX-Diff

}

 

GeneralParametersMRDC-XDD-Diff ::= SEQUENCE {

    splitSRB-WithOneUL-Path             ENUMERATED {supported}      OPTIONAL,

    splitDRB-withUL-Both-MCG-SCG        ENUMERATED {supported}      OPTIONAL,

    srb3                                ENUMERATED {supported}      OPTIONAL,

    ...

}

 

RF-ParametersMRDC ::= SEQUENCE {

    supportedBandCombinationList        BandCombinationList                 OPTIONAL,

    appliedFreqBandListFilter           FreqBandList                        OPTIONAL

}

 

UE-NR-CapabilityAddXDD-Mode ::= SEQUENCE {

   phy-ParametersXDD-Diff           Phy-ParametersXDD-Diff OPTIONAL,

   mac-ParametersXDD-Diff           MAC-ParametersXDD-Diff OPTIONAL,

   measAndMobParametersXDD-Diff     MeasAndMobParametersXDD-Diff OPTIONAL

}

 

UE-NR-CapabilityAddXDD-Mode-v1530 ::= SEQUENCE {

   eutra-ParametersXDD-Diff        EUTRA-ParametersXDD-Diff

}

 

UE-NR-CapabilityAddFRX-Mode ::= SEQUENCE {

   phy-ParametersFRX-Diff          Phy-ParametersFRX-Diff OPTIONAL,

   measAndMobParametersFRX-Diff    MeasAndMobParametersFRX-Diff OPTIONAL

}

 

UE-NR-CapabilityAddFRX-Mode-v1540 ::= SEQUENCE {

   ims-ParametersFRX-Diff         IMS-ParametersFRX-Diff OPTIONAL

}

 

FeatureSets ::= SEQUENCE {

   featureSetsDownlink                   SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF

                                                          FeatureSetDownlink OPTIONAL,

   featureSetsDownlinkPerCC              SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF

                                                          FeatureSetDownlinkPerCC OPTIONAL,

   featureSetsUplink                     SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF

                                                          FeatureSetUplink OPTIONAL,

   featureSetsUplinkPerCC                SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF

                                                          FeatureSetUplinkPerCC OPTIONAL,

    ...,

   [[

      featureSetsDownlink-v1540          SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF

                                                          FeatureSetDownlink-v1540 OPTIONAL,

   featureSetsUplink-v1540               SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF

                                                          FeatureSetUplink-v1540 OPTIONAL,

   featureSetsUplinkPerCC-v1540          SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF

                                                          FeatureSetUplinkPerCC-v1540 OPTIONAL

   ]]

}

 

FeatureSetCombination ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FeatureSetsPerBand

 

FeatureSetsPerBand ::= SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSet

 

FeatureSet ::= CHOICE {

   eutra SEQUENCE {

      downlinkSetEUTRA           FeatureSetEUTRA-DownlinkId,

      uplinkSetEUTRA             FeatureSetEUTRA-UplinkId

   },

   nr SEQUENCE {

      downlinkSetNR              FeatureSetDownlinkId,

      uplinkSetNR                FeatureSetUplinkId

   }

}

 

FeatureSetDownlink ::= SEQUENCE {

   featureSetListPerDownlinkCC     SEQUENCE (SIZE (1..maxNrofServingCells))

                                             OF FeatureSetDownlinkPerCC-Id,

   intraBandFreqSeparationDL       FreqSeparationClass OPTIONAL,

   scalingFactor                   ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL,

   crossCarrierScheduling-OtherSCS ENUMERATED {supported} OPTIONAL,

   scellWithoutSSB                 ENUMERATED {supported} OPTIONAL,

   csi-RS-MeasSCellWithoutSSB      ENUMERATED {supported} OPTIONAL,

   dummy1                          ENUMERATED {supported} OPTIONAL,

   type1-3-CSS                     ENUMERATED {supported} OPTIONAL,

   pdcch-MonitoringAnyOccasions    ENUMERATED {withoutDCI-Gap, withDCI-Gap} OPTIONAL,

   dummy2                          ENUMERATED {supported} OPTIONAL,

   ue-SpecificUL-DL-Assignment     ENUMERATED {supported} OPTIONAL,

   searchSpaceSharingCA-DL         ENUMERATED {supported} OPTIONAL,

   timeDurationForQCL SEQUENCE {

      scs-60kHz              ENUMERATED {s7, s14, s28} OPTIONAL,

      scs-120kHz             ENUMERATED {s14, s28} OPTIONAL

   } OPTIONAL,

   pdsch-ProcessingType1-DifferentTB-PerSlot SEQUENCE {

      scs-15kHz              ENUMERATED {upto2, upto4, upto7} OPTIONAL,

      scs-30kHz              ENUMERATED {upto2, upto4, upto7} OPTIONAL,

      scs-60kHz              ENUMERATED {upto2, upto4, upto7} OPTIONAL,

      scs-120kHz             ENUMERATED {upto2, upto4, upto7} OPTIONAL

   } OPTIONAL,

   dummy3                        DummyA OPTIONAL,

   dummy4                        SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyB OPTIONAL,

   dummy5                        SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyC OPTIONAL,

   dummy6                        SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyD OPTIONAL,

   dummy7                        SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyE OPTIONAL

}

 

FeatureSetDownlink-v1540 ::= SEQUENCE {

   oneFL-DMRS-TwoAdditionalDMRS-DL      ENUMERATED {supported} OPTIONAL,

   additionalDMRS-DL-Alt                ENUMERATED {supported} OPTIONAL,

   twoFL-DMRS-TwoAdditionalDMRS-DL      ENUMERATED {supported} OPTIONAL,

   oneFL-DMRS-ThreeAdditionalDMRS-DL    ENUMERATED {supported} OPTIONAL,

   pdcch-MonitoringAnyOccasionsWithSpanGap SEQUENCE {

      scs-15kHz            ENUMERATED {set1, set2, set3} OPTIONAL,

      scs-30kHz            ENUMERATED {set1, set2, set3} OPTIONAL,

      scs-60kHz            ENUMERATED {set1, set2, set3} OPTIONAL,

      scs-120kHz           ENUMERATED {set1, set2, set3} OPTIONAL

   } OPTIONAL,

   pdsch-SeparationWithGap              ENUMERATED {supported} OPTIONAL,

   pdsch-ProcessingType2 SEQUENCE {

      scs-15kHz           ProcessingParameters OPTIONAL,

      scs-30kHz           ProcessingParameters OPTIONAL,

      scs-60kHz           ProcessingParameters OPTIONAL

   } OPTIONAL,

   pdsch-ProcessingType2-Limited SEQUENCE {

      differentTB-PerSlot-SCS-30kHz     ENUMERATED {upto1, upto2, upto4, upto7}

   } OPTIONAL,

   dl-MCS-TableAlt-DynamicIndication    ENUMERATED {supported} OPTIONAL

}

 

DummyA ::= SEQUENCE {

   maxNumberNZP-CSI-RS-PerCC              INTEGER (1..32),

   maxNumberPortsAcrossNZP-CSI-RS-PerCC   ENUMERATED {p2, p4, p8, p12, p16, p24, p32, p40,

                                                      p48, p56, p64, p72, p80, p88, p96, p104,

                                                      p112, p120, p128, p136, p144, p152, p160,

                                                      p168, p176, p184, p192, p200, p208, p216,

                                                      p224, p232, p240, p248, p256},

   maxNumberCS-IM-PerCC                   ENUMERATED {n1, n2, n4, n8, n16, n32},

   maxNumberSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {n5, n6, n7, n8, n9, n10, n12, n14, n16,

                                                        n18, n20, n22, n24, n26, n28, n30, n32,

                                                        n34, n36, n38, n40, n42, n44, n46, n48,

                                                        n50, n52,n54, n56, n58, n60, n62, n64},

   totalNumberPortsSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {p8, p12, p16, p24, p32, p40, p48,

                                                               p56, p64, p72, p80, p88, p96,

                                                               p104, p112, p120, p128, p136,

                                                               p144, p152, p160, p168, p176,

                                                               p184, p192, p200, p208, p216,

                                                               p224, p232, p240, p248, p256}

}

 

DummyB ::= SEQUENCE {

   maxNumberTxPortsPerResource                   ENUMERATED {p2, p4, p8, p12, p16, p24, p32},

   maxNumberResources                            INTEGER (1..64),

   totalNumberTxPorts                            INTEGER (2..256),

   supportedCodebookMode                         ENUMERATED {mode1, mode1AndMode2},

   maxNumberCSI-RS-PerResourceSet                INTEGER (1..8)

}

 

DummyC ::= SEQUENCE {

   maxNumberTxPortsPerResource                  ENUMERATED {p8, p16, p32},

   maxNumberResources                           INTEGER (1..64),

   totalNumberTxPorts                           INTEGER (2..256),

   supportedCodebookMode                        ENUMERATED {mode1, mode2, both},

   supportedNumberPanels                        ENUMERATED {n2, n4},

   maxNumberCSI-RS-PerResourceSet               INTEGER (1..8)

}

 

DummyD ::= SEQUENCE {

   maxNumberTxPortsPerResource                 ENUMERATED {p4, p8, p12, p16, p24, p32},

   maxNumberResources                          INTEGER (1..64),

   totalNumberTxPorts                          INTEGER (2..256),

   parameterLx                                 INTEGER (2..4),

   amplitudeScalingType                        ENUMERATED {wideband, widebandAndSubband},

   amplitudeSubsetRestriction                  ENUMERATED {supported} OPTIONAL,

   maxNumberCSI-RS-PerResourceSet              INTEGER (1..8)

}

 

DummyE ::= SEQUENCE {

   maxNumberTxPortsPerResource                ENUMERATED {p4, p8, p12, p16, p24, p32},

   maxNumberResources                         INTEGER (1..64),

   totalNumberTxPorts                         INTEGER (2..256),

   parameterLx                                INTEGER (2..4),

   amplitudeScalingType                       ENUMERATED {wideband, widebandAndSubband},

   maxNumberCSI-RS-PerResourceSet             INTEGER (1..8)

}

 

FeatureSetDownlinkPerCC ::= SEQUENCE {

   supportedSubcarrierSpacingDL               SubcarrierSpacing,

   supportedBandwidthDL                       SupportedBandwidth,

   channelBW-90mhz                            ENUMERATED {supported} OPTIONAL,

   maxNumberMIMO-LayersPDSCH                  MIMO-LayersDL OPTIONAL,

   supportedModulationOrderDL                 ModulationOrder OPTIONAL

}

 

Phy-Parameters ::=  SEQUENCE {

    phy-ParametersCommon            Phy-ParametersCommon                OPTIONAL,

    phy-ParametersXDD-Diff          Phy-ParametersXDD-Diff              OPTIONAL,

    phy-ParametersFRX-Diff          Phy-ParametersFRX-Diff              OPTIONAL,

    phy-ParametersFR1               Phy-ParametersFR1                   OPTIONAL,

    phy-ParametersFR2               Phy-ParametersFR2                   OPTIONAL

}

 

Phy-ParametersCommon ::=    SEQUENCE {

    csi-RS-CFRA-ForHO                   ENUMERATED {supported}          OPTIONAL,

    dynamicPRB-BundlingDL               ENUMERATED {supported}          OPTIONAL,

    sp-CSI-ReportPUCCH                  ENUMERATED {supported}          OPTIONAL,

    sp-CSI-ReportPUSCH                  ENUMERATED {supported}          OPTIONAL,

    nzp-CSI-RS-IntefMgmt                ENUMERATED {supported}          OPTIONAL,

    type2-SP-CSI-Feedback-LongPUCCH     ENUMERATED {supported}          OPTIONAL,

    precoderGranularityCORESET          ENUMERATED {supported}          OPTIONAL,

    dynamicHARQ-ACK-Codebook            ENUMERATED {supported}          OPTIONAL,

    semiStaticHARQ-ACK-Codebook         ENUMERATED {supported}          OPTIONAL,

    spatialBundlingHARQ-ACK             ENUMERATED {supported}          OPTIONAL,

    dynamicBetaOffsetInd-HARQ-ACK-CSI   ENUMERATED {supported}          OPTIONAL,

    pucch-Repetition-F1-3-4             ENUMERATED {supported}          OPTIONAL,

    ra-Type0-PUSCH                      ENUMERATED {supported}          OPTIONAL,

    dynamicSwitchRA-Type0-1-PDSCH       ENUMERATED {supported}          OPTIONAL,

    dynamicSwitchRA-Type0-1-PUSCH       ENUMERATED {supported}          OPTIONAL,

    pdsch-MappingTypeA                  ENUMERATED {supported}          OPTIONAL,

    pdsch-MappingTypeB                  ENUMERATED {supported}          OPTIONAL,

    interleavingVRB-ToPRB-PDSCH         ENUMERATED {supported}          OPTIONAL,

    interSlotFreqHopping-PUSCH          ENUMERATED {supported}          OPTIONAL,

    type1-PUSCH-RepetitionMultiSlots    ENUMERATED {supported}          OPTIONAL,

    type2-PUSCH-RepetitionMultiSlots    ENUMERATED {supported}          OPTIONAL,

    pusch-RepetitionMultiSlots          ENUMERATED {supported}          OPTIONAL,

    pdsch-RepetitionMultiSlots          ENUMERATED {supported}          OPTIONAL,

    downlinkSPS                         ENUMERATED {supported}          OPTIONAL,

    configuredUL-GrantType1             ENUMERATED {supported}          OPTIONAL,

    configuredUL-GrantType2             ENUMERATED {supported}          OPTIONAL,

    pre-EmptIndication-DL               ENUMERATED {supported}          OPTIONAL,

    cbg-TransIndication-DL              ENUMERATED {supported}          OPTIONAL,

    cbg-TransIndication-UL              ENUMERATED {supported}          OPTIONAL,

    cbg-FlushIndication-DL              ENUMERATED {supported}          OPTIONAL,

    dynamicHARQ-ACK-CodeB-CBG-Retx-DL   ENUMERATED {supported}          OPTIONAL,

    rateMatchingResrcSetSemi-Static     ENUMERATED {supported}          OPTIONAL,

    rateMatchingResrcSetDynamic         ENUMERATED {supported}          OPTIONAL,

    bwp-SwitchingDelay                  ENUMERATED {type1, type2}       OPTIONAL,

    ...

}

 

Phy-ParametersXDD-Diff ::=  SEQUENCE {

    dynamicSFI                          ENUMERATED {supported}          OPTIONAL,

    twoPUCCH-F0-2-ConsecSymbols         ENUMERATED {supported}          OPTIONAL,

    twoDifferentTPC-Loop-PUSCH          ENUMERATED {supported}          OPTIONAL,

    twoDifferentTPC-Loop-PUCCH          ENUMERATED {supported}          OPTIONAL,

    ...

}

 

Phy-ParametersFRX-Diff ::=  SEQUENCE {

    dynamicSFI                          ENUMERATED {supported}          OPTIONAL,

    oneFL-DMRS-TwoAdditionalDMRS        BIT STRING (SIZE (2))           OPTIONAL,

    twoFL-DMRS                          BIT STRING (SIZE (2))           OPTIONAL,

    twoFL-DMRS-TwoAdditionalDMRS        BIT STRING (SIZE (2))           OPTIONAL,

    oneFL-DMRS-ThreeAdditionalDMRS      BIT STRING (SIZE (2))           OPTIONAL,

    supportedDMRS-TypeDL                ENUMERATED {type1, type2}       OPTIONAL,

    supportedDMRS-TypeUL                ENUMERATED {type1, type2}       OPTIONAL,

    semiOpenLoopCSI                     ENUMERATED {supported}          OPTIONAL,

    csi-ReportWithoutPMI                ENUMERATED {supported}          OPTIONAL,

    csi-ReportWithoutCQI                ENUMERATED {supported}          OPTIONAL,

    onePortsPTRS                        BIT STRING (SIZE (2))           OPTIONAL,

    twoPUCCH-F0-2-ConsecSymbols         ENUMERATED {supported}          OPTIONAL,

    pucch-F2-WithFH                     ENUMERATED {supported}          OPTIONAL,

    pucch-F3-WithFH                     ENUMERATED {supported}          OPTIONAL,

    pucch-F4-WithFH                     ENUMERATED {supported}          OPTIONAL,

    freqHoppingPUCCH-F0-2               ENUMERATED {notSupported}       OPTIONAL,

    freqHoppingPUCCH-F1-3-4             ENUMERATED {notSupported}       OPTIONAL,

    mux-SR-HARQ-ACK-CSI-PUCCH           ENUMERATED {supported}          OPTIONAL,

    uci-CodeBlockSegmentation           ENUMERATED {supported}          OPTIONAL,

    onePUCCH-LongAndShortFormat         ENUMERATED {supported}          OPTIONAL,

    twoPUCCH-AnyOthersInSlot            ENUMERATED {supported}          OPTIONAL,

    intraSlotFreqHopping-PUSCH          ENUMERATED {supported}          OPTIONAL,

    pusch-LBRM                          ENUMERATED {supported}          OPTIONAL,

    pdcch-BlindDetectionCA              ENUMERATED {supported}          OPTIONAL,

    tpc-PUSCH-RNTI                      ENUMERATED {supported}          OPTIONAL,

    tpc-PUCCH-RNTI                      ENUMERATED {supported}          OPTIONAL,

    tpc-SRS-RNTI                        ENUMERATED {supported}          OPTIONAL,

    absoluteTPC-Command                 ENUMERATED {supported}          OPTIONAL,

    twoDifferentTPC-Loop-PUSCH          ENUMERATED {supported}          OPTIONAL,

    twoDifferentTPC-Loop-PUCCH          ENUMERATED {supported}          OPTIONAL,

    pusch-HalfPi-BPSK                   ENUMERATED {supported}          OPTIONAL,

    pucch-F3-4-HalfPi-BPSK              ENUMERATED {supported}          OPTIONAL,

    almostContiguousCP-OFDM-UL          ENUMERATED {supported}          OPTIONAL ,

    sp-CSI-RS                           ENUMERATED {supported}          OPTIONAL,

    sp-CSI-IM                           ENUMERATED {supported}          OPTIONAL,

    tdd-MultiDL-UL-SwitchPerSlot        ENUMERATED {supported}          OPTIONAL,

    multipleCORESET                     ENUMERATED {supported}          OPTIONAL,

    ...

}

 

Phy-ParametersFR1 ::=   SEQUENCE {

    pdcchMonitoringSingleOccasion       ENUMERATED {supported}          OPTIONAL,

    scs-60kHz                           ENUMERATED {supported}          OPTIONAL,

    pdsch-256QAM-FR1                    ENUMERATED {supported}          OPTIONAL,

    pdsch-RE-MappingFR1                 ENUMERATED {n10, n20}           OPTIONAL,

    ...

}

 

Phy-ParametersFR2 ::=   SEQUENCE {

    calibrationGapPA                    ENUMERATED {supported}          OPTIONAL,

    pdsch-RE-MappingFR2                 ENUMERATED {n6, n20}            OPTIONAL,

    ...

}

 

RF-Parameters ::= SEQUENCE {

    supportedBandListNR                 SEQUENCE (SIZE (1..maxBands)) OF BandNR,

    supportedBandCombinationList        BandCombinationList              OPTIONAL,

    appliedFreqBandListFilter           FreqBandList                     OPTIONAL

}

 

BandNR ::=  SEQUENCE {

    bandNR                          FreqBandIndicatorNR,

    modifiedMPR-Behaviour           BIT STRING (SIZE (8))                       OPTIONAL,

    mimo-ParametersPerBand          MIMO-ParametersPerBand                      OPTIONAL,

    extendedCP                      ENUMERATED {supported}                      OPTIONAL,

    multipleTCI                     ENUMERATED {supported}                      OPTIONAL,

    bwp-WithoutRestriction          ENUMERATED {supported}                      OPTIONAL,

    bwp-SameNumerology                  ENUMERATED {upto2, upto4}               OPTIONAL,

    bwp-DiffNumerology                  ENUMERATED {upto4}                      OPTIONAL,

    crossCarrierSchedulingDL-SameSCS        ENUMERATED {supported}              OPTIONAL,

    crossCarrierSchedulingUL-SameSCS        ENUMERATED {supported}              OPTIONAL,

    pdsch-256QAM-FR2                ENUMERATED {supported}                      OPTIONAL,

    pusch-256QAM                    ENUMERATED {supported}                      OPTIONAL,

    ue-PowerClass                   ENUMERATED {pc2, pc3}                       OPTIONAL,

    rateMatchingLTE-CRS             ENUMERATED {supported}                      OPTIONAL,

    ...

}

 

MIMO-ParametersPerBand ::= SEQUENCE {

    tci-StatePDSCH                      SEQUENCE {

        maxNumberConfiguredTCIstatesPerCC   ENUMERATED {n4, n8, n16, n32, n64}   OPTIONAL,

        maxNumberActiveTCI-PerBWP           ENUMERATED {n1, n2, n4, n8}          OPTIONAL

    }                                                                            OPTIONAL,

    additionalActiveTCI-StatePDCCH      ENUMERATED {supported}                   OPTIONAL,

    pusch-TransCoherence                ENUMERATED {nonCoherent,

                                                    partialNonCoherent,

                                                    fullCoherent}                OPTIONAL,

    beamCorrespondence                  ENUMERATED {supported}                   OPTIONAL,

    periodicBeamReport                  ENUMERATED {supported}                   OPTIONAL,

    aperiodicBeamReport                 ENUMERATED {supported}                   OPTIONAL,

    sp-BeamReportPUCCH                  ENUMERATED {supported}                   OPTIONAL,

    sp-BeamReportPUSCH                  ENUMERATED {supported}                   OPTIONAL,

    beamManagementSSB-CSI-RS            BeamManagementSSB-CSI-RS                 OPTIONAL,

    maxNumberRxBeam                     INTEGER (2..8)                           OPTIONAL,

    maxNumberRxTxBeamSwitchDL           SEQUENCE {

        scs-15kHz                           ENUMERATED {n4, n7, n14}             OPTIONAL,

        scs-30kHz                           ENUMERATED {n4, n7, n14}             OPTIONAL,

        scs-60kHz                           ENUMERATED {n4, n7, n14}             OPTIONAL,

        scs-120kHz                          ENUMERATED {n4, n7, n14}             OPTIONAL,

        scs-240kHz                          ENUMERATED {n4, n7, n14}             OPTIONAL

    }                                                                            OPTIONAL,

    maxNumberNonGroupBeamReporting      ENUMERATED {n1, n2, n4}                  OPTIONAL,

    groupBeamReporting                  ENUMERATED {supported}                   OPTIONAL,

    uplinkBeamManagement                SEQUENCE {

        maxNumberSRS-ResourcePerSet         ENUMERATED {n2, n4, n8, n16, n32},

        maxNumberSRS-ResourceSet            INTEGER (1..8)

    }                                                                            OPTIONAL,

    maxNumberCSI-RS-BFR                 INTEGER (1..64)                          OPTIONAL,

    maxNumberSSB-BFR                    INTEGER (1..64)                          OPTIONAL,

    maxNumberCSI-RS-SSB-BFR             INTEGER (1..256)                         OPTIONAL,

    twoPortsPTRS-DL                     ENUMERATED {supported}                   OPTIONAL,

    twoPortsPTRS-UL                     ENUMERATED {supported}                   OPTIONAL,

    supportedSRS-Resources              SRS-Resources                            OPTIONAL,

    srs-TxSwitch                        SRS-TxSwitch                             OPTIONAL,

    maxNumberSimultaneousSRS-PerCC      INTEGER (1..4)                           OPTIONAL,

    beamReportTiming                    SEQUENCE {

        scs-15kHz                           ENUMERATED {sym2, sym4, sym8}        OPTIONAL,

        scs-30kHz                           ENUMERATED {sym4, sym8, sym14}       OPTIONAL,

        scs-60kHz                           ENUMERATED {sym8, sym14, sym28}      OPTIONAL,

        scs-120kHz                          ENUMERATED {sym14, sym28, sym56}     OPTIONAL

    }                                                                            OPTIONAL,

    ptrs-DensityRecommendationSetDL     SEQUENCE {

        scs-15kHz                           PTRS-DensityRecommendationDL         OPTIONAL,

        scs-30kHz                           PTRS-DensityRecommendationDL         OPTIONAL,

        scs-60kHz                           PTRS-DensityRecommendationDL         OPTIONAL,

        scs-120kHz                          PTRS-DensityRecommendationDL         OPTIONAL

    }                                                                            OPTIONAL,

    ptrs-DensityRecommendationSetUL     SEQUENCE {

        scs-15kHz                           PTRS-DensityRecommendationUL         OPTIONAL,

        scs-30kHz                           PTRS-DensityRecommendationUL         OPTIONAL,

        scs-60kHz                           PTRS-DensityRecommendationUL         OPTIONAL,

        scs-120kHz                          PTRS-DensityRecommendationUL         OPTIONAL

    }                                                                            OPTIONAL,

    csi-RS-ForTracking                      CSI-RS-ForTracking                   OPTIONAL,

    aperiodicTRS                            ENUMERATED {supported}              OPTIONAL,

    ...

}

 

BeamManagementSSB-CSI-RS ::=    SEQUENCE {

    maxNumberSSB-CSI-RS-ResourceOneTx   ENUMERATED {n8, n16, n32, n64},

    maxNumberSSB-CSI-RS-ResourceTwoTx   ENUMERATED {n0, n4, n8, n16, n32, n64},

    supportedCSI-RS-Density             ENUMERATED {one, three, oneAndThree}

}

 

CSI-RS-ForTracking ::=              SEQUENCE {

    burstLength                         INTEGER (1..2),

    maxSimultaneousResourceSetsPerCC    INTEGER (1..8),

    maxConfiguredResourceSetsPerCC      INTEGER (1..64),

    maxConfiguredResourceSetsAllCC      INTEGER (1..128)

}

 

PTRS-DensityRecommendationDL ::=    SEQUENCE {

    frequencyDensity1                   INTEGER (1..276),

    frequencyDensity2                   INTEGER (1..276),

    timeDensity1                        INTEGER (0..29),

    timeDensity2                        INTEGER (0..29),

    timeDensity3                        INTEGER (0..29)

}

 

PTRS-DensityRecommendationUL ::=    SEQUENCE {

    frequencyDensity1                   INTEGER (1..276),

    frequencyDensity2                   INTEGER (1..276),

    timeDensity1                        INTEGER (0..29),

    timeDensity2                        INTEGER (0..29),

    timeDensity3                        INTEGER (0..29),

    sampleDensity1                      INTEGER (1..276),

    sampleDensity2                      INTEGER (1..276),

    sampleDensity3                      INTEGER (1..276),

    sampleDensity4                      INTEGER (1..276),

    sampleDensity5                      INTEGER (1..276)

}

 

SRS-Resources ::=   SEQUENCE {

    maxNumberAperiodicSRS-PerBWP                    ENUMERATED {n1, n2, n4, n8, n16},

    maxNumberAperiodicSRS-PerBWP-PerSlot            INTEGER (1..6),

    maxNumberPeriodicSRS-PerBWP                     ENUMERATED {n1, n2, n4, n8, n16},

    maxNumberPeriodicSRS-PerBWP-PerSlot             INTEGER (1..6),

    maxNumberSemiPersitentSRS-PerBWP                ENUMERATED {n1, n2, n4, n8, n16},

    maxNumberSP-SRS-PerBWP-PerSlot                  INTEGER (1..6),

    maxNumberSRS-Ports-PerResource                  ENUMERATED {n1, n2, n4}

}

 

SRS-TxSwitch ::=    SEQUENCE {

    supportedSRS-TxPortSwitch           ENUMERATED {t1r2, t1r4, t2r4, t1r4-t2r4, tr-equal},

    txSwitchImpactToRx                  ENUMERATED {true}  OPTIONAL

}

 

PDCP-Parameters ::= SEQUENCE {

    supportedROHC-Profiles  SEQUENCE {

        profile0x0000       BOOLEAN,

        profile0x0001       BOOLEAN,

        profile0x0002       BOOLEAN,

        profile0x0003       BOOLEAN,

        profile0x0004       BOOLEAN,

        profile0x0006       BOOLEAN,

        profile0x0101       BOOLEAN,

        profile0x0102       BOOLEAN,

        profile0x0103       BOOLEAN,

        profile0x0104       BOOLEAN

    },

    maxNumberROHC-ContextSessions   ENUMERATED {cs2, cs4, cs8, cs12, cs16, cs24, cs32, cs48,

                                                cs64, cs128, cs256, cs512, cs1024, cs16384,

                                                spare2, spare1},  

    uplinkOnlyROHC-Profiles         ENUMERATED {supported}  OPTIONAL,

    continueROHC-Context            ENUMERATED {supported}  OPTIONAL,

    outOfOrderDelivery              ENUMERATED {supported}  OPTIONAL,

    shortSN                         ENUMERATED {supported}  OPTIONAL,

    ...

}

 

RLC-Parameters ::= SEQUENCE {

    am-WithShortSN                  ENUMERATED {supported}  OPTIONAL,

    um-WithShortSN                  ENUMERATED {supported}  OPTIONAL,

    um-WIthLongSN                   ENUMERATED {supported}  OPTIONAL,

    ...

}

 

MAC-Parameters ::= SEQUENCE {

    mac-ParametersCommon            MAC-ParametersCommon    OPTIONAL,

    mac-ParametersXDD-Diff          MAC-ParametersXDD-Diff  OPTIONAL

}

 

MAC-ParametersCommon ::=    SEQUENCE {

    lcp-Restriction                 ENUMERATED {supported}  OPTIONAL,

    pucch-SpatialRelInfoMAC-CE      ENUMERATED {supported}  OPTIONAL,

    ...

}

 

MAC-ParametersXDD-Diff ::=  SEQUENCE {

    skipUplinkTxDynamic             ENUMERATED {supported}  OPTIONAL,

    logicalChannelSR-DelayTimer     ENUMERATED {supported}  OPTIONAL,

    longDRX-Cycle                   ENUMERATED {supported}  OPTIONAL,

    shortDRX-Cycle                  ENUMERATED {supported}  OPTIONAL,

    multipleSR-Configurations       ENUMERATED {supported}  OPTIONAL,

    multipleConfiguredGrants        ENUMERATED {supported}  OPTIONAL,

    ...

}

 

MeasAndMobParameters ::= SEQUENCE {

    measAndMobParametersCommon      MeasAndMobParametersCommon OPTIONAL,

    measAndMobParametersXDD-Diff    MeasAndMobParametersXDD-Diff OPTIONAL,

    measAndMobParametersFRX-Diff    MeasAndMobParametersFRX-Diff OPTIONAL

}

 

MeasAndMobParametersCommon ::= SEQUENCE {

    supportedGapPattern            BIT STRING (SIZE (22)) OPTIONAL,

    ssb-RLM                        ENUMERATED {supported} OPTIONAL,

    ssb-AndCSI-RS-RLM              ENUMERATED {supported} OPTIONAL,

    ...,

    [[

        eventB-MeasAndReport       ENUMERATED {supported} OPTIONAL,

        handoverFDD-TDD            ENUMERATED {supported} OPTIONAL,

        eutra-CGI-Reporting        ENUMERATED {supported} OPTIONAL,

        nr-CGI-Reporting           ENUMERATED {supported} OPTIONAL

    ]],

    [[

       independentGapConfig        ENUMERATED {supported} OPTIONAL,

       periodicEUTRA-MeasAndReport ENUMERATED {supported} OPTIONAL,

       handoverFR1-FR2             ENUMERATED {supported} OPTIONAL,

       maxNumberCSI-RS-RRM-RS-SINR ENUMERATED {n4, n8, n16, n32, n64, n96} OPTIONAL

    ]],

    [[

       nr-CGI-Reporting-ENDC       ENUMERATED {supported} OPTIONAL

    ]]

}

 

MeasAndMobParametersXDD-Diff ::= SEQUENCE {

    intraAndInterF-MeasAndReport  ENUMERATED {supported} OPTIONAL,

    eventA-MeasAndReport          ENUMERATED {supported} OPTIONAL,

    ...,

    [[

       handoverInterF             ENUMERATED {supported} OPTIONAL,

       handoverLTE                ENUMERATED {supported} OPTIONAL,

       handover-eLTE              ENUMERATED {supported} OPTIONAL

    ]]

}

 

MeasAndMobParametersFRX-Diff ::= SEQUENCE {

    ss-SINR-Meas                            ENUMERATED {supported} OPTIONAL,

    csi-RSRP-AndRSRQ-MeasWithSSB            ENUMERATED {supported} OPTIONAL,

    csi-RSRP-AndRSRQ-MeasWithoutSSB         ENUMERATED {supported} OPTIONAL,

    csi-SINR-Meas                           ENUMERATED {supported} OPTIONAL,

    csi-RS-RLM                              ENUMERATED {supported} OPTIONAL,

    ...,

    [[

       handoverInterF                       ENUMERATED {supported} OPTIONAL,

       handoverLTE                          ENUMERATED {supported} OPTIONAL,

       handover-eLTE                        ENUMERATED {supported} OPTIONAL

    ]],

    [[

       maxNumberResource-CSI-RS-RLM         ENUMERATED {n2, n4, n6, n8} OPTIONAL

    ]],

    [[

       simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL

    ]]

}

 

MeasParameters ::= SEQUENCE {

    measParametersCommon            MeasParametersCommon        OPTIONAL,

    measParametersXDD-Diff          MeasParametersXDD-Diff      OPTIONAL,

    measParametersFRX-Diff          MeasParametersFRX-Diff      OPTIONAL

}

 

MeasParametersCommon ::= SEQUENCE {

    supportedGapPattern             BIT STRING (SIZE (22))          OPTIONAL,

    ...

}

 

MeasParametersXDD-Diff ::=  SEQUENCE {

    intraAndInterF-MeasAndReport    ENUMERATED {supported}  OPTIONAL,

    eventA-MeasAndReport            ENUMERATED {supported}  OPTIONAL,

    ...

}

 

MeasParametersFRX-Diff ::=  SEQUENCE {

    ss-SINR-Meas                        ENUMERATED {supported}      OPTIONAL,

    csi-RSRP-AndRSRQ-MeasWithSSB        ENUMERATED {supported}      OPTIONAL,

    csi-RSRP-AndRSRQ-MeasWithoutSSB     ENUMERATED {supported}      OPTIONAL,

    csi-SINR-Meas                       ENUMERATED {supported}      OPTIONAL,

    csi-RS-RLM                          ENUMERATED {supported}      OPTIONAL,

    ...

}

Examples  of UE Capability:

     

    Example 1 : Click here to get the example of full Capability Information for ENDC/NSA.

                    This is from a sample log from Amarisoft

     

    Example 2 : Click hereto get the example of full Capability Information for SA.

                    This is from a sample log from Amarisoft

     

    Example 3 : An example of NSA band combination from Example 1.

      rf-ParametersMRDC {

        supportedBandCombinationList {

        {

          bandList {

          eutra: {

            bandEUTRA 8, ca-BandwidthClassDL-EUTRA a,

            ca-BandwidthClassUL-EUTRA a

          },

          nr: {

            bandNR 78,

            ca-BandwidthClassDL-NR a,

            ca-BandwidthClassUL-NR a

          }

          },

          featureSetCombination 0,

          mrdc-Parameters {

            simultaneousRxTxInterBandENDC supported,

            asyncIntraBandENDC supported

          },

          supportedBandwidthCombinationSet '0'B

        },

    Example 4 : An example of supported bandwidth in SA.

      channelBWs-DL-v1530 fr1: {

        scs-15kHz '0000000000'B,

        scs-30kHz '0000001111'B,=> support 40,50,60,80 and 100 (max BW)

        scs-60kHz '0000000000'B

      },

      channelBWs-UL-v1530 fr1: {

        scs-15kHz '0000000000'B,

        scs-30kHz '0000001111'B,=> support 40,50,60,80 and 100 (max BW) s

        cs-60kHz '0000000000'B

      }

      38.306 specifies the meaning of this IE as follows :

       

      channelBWs-DL/channelBWs-UL :

      Indicates for each subcarrier spacing whether the UE supports channel bandwidthslower than the maximum channel bandwidth as defined in TS 38.101-1  and TS 38.101-2 . If this parameter is not included, it mean that the UE supports the channel bandwidths among [5, 10, 15, 20, 25, 30, 40, 50, 60, 80, 100] in FR1 and [50, 100, 200] in FR2.

       

      For FR1, the bits starting from the leading / leftmost bit indicate 5, 10, 15, 20, 25, 30, 40, 50, 60 and 80MHz. For FR2, the bits starting from the leading / leftmost bit indicate 50, 100 and 200MHz.

       

      NOTE : it is assumed that the maximum bandwidth (in most case 100Mhz in FR1 SCS30, 50 Mhz in FR1 SCS 15, 400 Mhz FR2) is supported by default.

       

     

    Example 5 : DMRS Type / pucch format, frequency hopping / multiple CORESET

       

      phy-ParametersFRX-Diff {

        twoFL-DMRS '10'B, supported

        DMRS-TypeDL type1,

        supportedDMRS-TypeUL type1,

        pucch-F2-WithFH supported,

        pucch-F3-WithFH supported,

        pucch-F1-3-4WithoutFH notSupported,

        almostContiguousCP-OFDM-UL supported,

        multipleCORESET supported,

        mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot { sameSymbol supported },

        oneFL-DMRS-TwoAdditionalDMRS-UL supported

      },

       

      38.306 specifies the meaning of this IE as follows :

       

      twoFL-DMRS (MappingTypeB, DMRS length = 2)

      Defines whether the UE supports DM-RS pattern for DL reception and/or UL transmission with 2 symbols front-loaded DM-RS without additional DM-RS symbols.

       

      twoFL-DMRS-TwoAdditionalDMRS

      Defines whether the UE supports DM-RS pattern for DL reception and/or UL transmission with 2 symbols front-loaded DM-RS with one additional 2 symbols DMRS.

       

      NOTE : front-loaded DMRS mean mappingType B

       

      featureSetsDownlink-v1540 {

        {

          oneFL-DMRS-TwoAdditionalDMRS-DL supported,

          twoFL-DMRS-TwoAdditionalDMRS-DL supported,

          oneFL-DMRS-ThreeAdditionalDMRS-DL supported

        }

      }

       

    Example 6 : HARQ, PUSCH RaType, PDSCH MappingType, Number of SearchSpace

       

      phy-ParametersCommon {

        dynamicHARQ-ACK-Codebook supported,

        semiStaticHARQ-ACK-Codebook supported,

        ra-Type0-PUSCH supported,

        dynamicSwitchRA-Type0-1-PDSCH supported,

        dynamicSwitchRA-Type0-1-PUSCH supported,

        pdsch-MappingTypeA supported,

        rateMatchingResrcSetSemi-Static supported,

        rateMatchingResrcSetDynamic supported,

        bwp-SwitchingDelay type1,

        maxNumberSearchSpaces n10,

        rateMatchingCtrlResrcSetDynamic supported,

        maxLayersMIMO-Indication supported

      },

       

    Example 7 : Subcarrier Spacing, Max Bandwidth, Modulation Scheme, MIMO layers

       

      featureSets {

        featureSetsDownlink {

          {

            featureSetListPerDownlinkCC { 1 },

            type1-3-CSS supported

          }

        },

        featureSetsDownlinkPerCC {

          {

            supportedSubcarrierSpacingDL kHz30,

            supportedBandwidthDL fr1: mhz100,

            maxNumberMIMO-LayersPDSCH fourLayers,

            supportedModulationOrderDL qam256

          }

        },

        featureSetsUplinkPerCC {

          {

            supportedSubcarrierSpacingUL kHz30,

            supportedBandwidthUL fr1: mhz100,

            mimo-CB-PUSCH {

            maxNumberMIMO-LayersCB-PUSCH twoLayers,

            maxNumberSRS-ResourcePerSet 1

          },

        supportedModulationOrderUL qam256

      },

       

    Example 8 : SRS

       

      featureSetsUplink {

        { .....

         supportedSRS-Resources {

           maxNumberAperiodicSRS-PerBWP n1,

           maxNumberAperiodicSRS-PerBWP-PerSlot 1,

           maxNumberPeriodicSRS-PerBWP n1,

           maxNumberPeriodicSRS-PerBWP-PerSlot 1,

           maxNumberSemiPersitentSRS-PerBWP n1,

           maxNumberSP-SRS-PerBWP-PerSlot 1,

           maxNumberSRS-Ports-PerResource n1

         },

      featureSetsUplinkPerCC {

         { ...

           mimo-CB-PUSCH

            {

              maxNumberMIMO-LayersCB-PUSCH oneLayer,

              maxNumberSRS-ResourcePerSet 1

             },

      ...

       

      38.306 defines the meaning of IEs as follows :

       

      maxNumberSRS-ResourcePerSet : the maximum number of SRS resources per SRS resource set configured for codebook based transmission to the UE.

 

    Example 9 :Max Number of BWP and Subcarrier spacing for the BWPs

       : Following example says the UE support max 4 BWPs in n78 and the subcarrier spacing for all the BWPs should be same.

          rf-Parameters {

              supportedBandListNR {

                {                

                {

                  bandNR 78,

                  ...

                  bwp-SameNumerology upto4,

                  ...

                },

 

            phy-Parameters {

              phy-ParametersCommon {

                ...

                bwp-SwitchingDelay type1,

                ...

              },

 

            featureSetsDownlink {

              {

                  ...

                  pdsch-ProcessingType1-DifferentTB-PerSlot {

                    scs-15kHz upto2,

                    scs-30kHz upto2,

                    scs-60kHz upto2,

                    scs-120kHz upto2

                  },

               ...

 

         Example 11 : SRB3

 

            generalParametersMRDC {

              srb3 supported

            },

            fdd-Add-UE-MRDC-Capabilities {

              generalParametersMRDC-XDD-Diff {

                srb3 supported

              }

            },

            tdd-Add-UE-MRDC-Capabilities {

              measAndMobParametersMRDC-XDD-Diff {

                sftd-MeasPSCell supported,

                sftd-MeasNR-Cell supported

              },

              generalParametersMRDC-XDD-Diff {

                srb3 supported

              }

            },

 

       Example 12 : Uplink MIMO

 

             featureSetsUplinkPerCC {

                {

                  supportedSubcarrierSpacingUL kHz30,

                  supportedBandwidthUL fr1: mhz100,

                  channelBW-90mhz supported,

                  mimo-CB-PUSCH {

                    maxNumberMIMO-LayersCB-PUSCHoneLayer,// MIMO not supported

                    maxNumberSRS-ResourcePerSet 1

                  },

                  maxNumberMIMO-LayersNonCB-PUSCHoneLayer,

                  supportedModulationOrderUL qam64

                }

 

        featureSetsUplinkPerCC {

        {

           supportedSubcarrierSpacingUL kHz30,

           supportedBandwidthUL fr1: mhz20,

           mimo-CB-PUSCH {

              maxNumberMIMO-LayersCB-PUSCHtwoLayers,// MIMO supported

              maxNumberSRS-ResourcePerSet 1

            },

              supportedModulationOrderUL qam256

           }

        },

              NOTE : Refer to maxNumberMIMO-LayersCB-PUSCH in 38.306

 

        Example 13 : SRS Antenna Switching

        supportedBandCombinationList-v1540 {

          {

            bandList-v1540 {

              {

                srs-TxSwitch {

                  supportedSRS-TxPortSwitch t1r2

                }

              }

            },

            ca-ParametersNR-v1540 {

              csi-RS-IM-ReceptionForFeedbackPerBandComb {

                maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC 8,

                totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC 64

              },

              simultaneousCSI-ReportsAllCC 8

            }

          },

          ....

         }

 

              Example 14 : SA Supportablity

        There is no direct indicator for SA support in UE capability Information (as far as I know). You may check the SA supportability using a NAS message as shown below. You can find this information from Attach Request in LTE and RegistrationRequest in NR SA

         

        UE network capability:

          0xf0 (EEA0=1, 128-EEA1=1, 128-EEA2=1, 128-EEA3=1, EEA4=0, EEA5=0, EEA6=0, EEA7=0)

          0x70 (EIA0=0, 128-EIA1=1, 128-EIA2=1, 128-EIA3=1, EIA4=0, EIA5=0, EIA6=0, EIA7=0)

          0xc0 (UEA0=1, UEA1=1, UEA2=0, UEA3=0, UEA4=0, UEA5=0, UEA6=0, UEA7=0)

          0x40 (UCS2=0, UIA1=1, UIA2=0, UIA3=0, UIA4=0, UIA5=0, UIA6=0, UIA7=0)

          0x19 (ProSe-dd=0, ProSe=0, H.245-ASH=0, ACC-CSFB=1, LPP=1, LCS=0, 1xSRVCC=0, NF=1)

          0x80 (ePCO=1, HC-CP CIoT=0, ERw/oPDN=0, S1-U data=0, UP CIoT=0, CP CIoT=0, ProSe-relay=0, ProSe-dc=0)

          0xb0 (15 bearers=1, SGC=0,N1mode=1, DCNR=1, CP backoff=0, RestrictEC=0, V2X PC5=0, multipleDRB=0)

         

        Or you may indirectly confirm on SA supportability from LTE UE capability as below

         

        irat-ParametersNR-v1540 {

         eutra-EPC-HO-ToNR-TDD-FR1-r15 supported,

         sa-NR-r15 supported,

         supportedBandListNR-SA-r15 {

           {

              bandNR-r15 41

           },

           {

              bandNR-r15 78

           }

         }

         

 

                 Example 15 : NSA Supportability - NAS Capability

        For NSA, there should be two major feature should be supported. One is lower layer band combination and the other one is higher layer dual connectivity. Higher layer dual connectivity (i.e, dual connectivity with NR) is notified by a NAS message with a parameter calledDCNR. This feature is configured in UE network capability in Attach Request (in case of LTE) or Registration Request (in case of NR).

        NOTE : This is for NSA Supportability with NAS point of view. For the lower layer capability of NSA Supportability, Refer to Example 16.

         

        UE network capability:

          0xf0 (EEA0=1, 128-EEA1=1, 128-EEA2=1, 128-EEA3=1, EEA4=0, EEA5=0, EEA6=0, EEA7=0)

          0x70 (EIA0=0, 128-EIA1=1, 128-EIA2=1, 128-EIA3=1, EIA4=0, EIA5=0, EIA6=0, EIA7=0)

          0xc0 (UEA0=1, UEA1=1, UEA2=0, UEA3=0, UEA4=0, UEA5=0, UEA6=0, UEA7=0)

          0x40 (UCS2=0, UIA1=1, UIA2=0, UIA3=0, UIA4=0, UIA5=0, UIA6=0, UIA7=0)

          0x19 (ProSe-dd=0, ProSe=0, H.245-ASH=0, ACC-CSFB=1, LPP=1, LCS=0, 1xSRVCC=0, NF=1)

          0x80 (ePCO=1, HC-CP CIoT=0, ERw/oPDN=0, S1-U data=0, UP CIoT=0, CP CIoT=0, ProSe-relay=0, ProSe-dc=0)

          0xb0 (15 bearers=1, SGC=0, N1mode=1,DCNR=1, CP backoff=0, RestrictEC=0, V2X PC5=0, multipleDRB=0)

 

      Example 16 : NSA Supportability - RRC Capability

         

        For RRC and Lower Layer Capability of NSA, UE should notify something as shown below.

        {

          rat-Type eutra-nr,

          ueCapabilityRAT-Container {

            measAndMobParametersMRDC {

              measAndMobParametersMRDC-FRX-Diff {

                simultaneousRxDataSSB-DiffNumerology supported

              }

            },

            rf-ParametersMRDC {

              supportedBandCombinationList {

                {

                  bandList {

                    eutra: {

                      bandEUTRA 1,

                      ca-BandwidthClassDL-EUTRA a,

                      ca-BandwidthClassUL-EUTRA a

                    },

                    nr: {

                      bandNR 78,

                      ca-BandwidthClassDL-NR a,

                      ca-BandwidthClassUL-NR a

                    }

                  },

                  featureSetCombination 0,

                  mrdc-Parameters {

                    dynamicPowerSharingENDC supported,

                    simultaneousRxTxInterBandENDC supported

                  },

                  powerClass-v1530 pc2

                }

              },

              appliedFreqBandListFilter {

                bandInformationEUTRA: {

                  bandEUTRA 1

                },

                bandInformationNR: {

                  bandNR 78

                }

              },

              supportedBandCombinationList-v1540 {

                {

                  bandList-v1540 {

                    {

                      srs-TxSwitch {

                        supportedSRS-TxPortSwitch notSupported

                      }

                    },

                    {

                      srs-TxSwitch {

                        supportedSRS-TxPortSwitch t1r2

                      }

                    }

                  },

                  ca-ParametersNR-v1540 {

                    csi-RS-IM-ReceptionForFeedbackPerBandComb {

                      maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC 8,

                      totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC 64

                    },

                    simultaneousCSI-ReportsAllCC 8

                  }

                }

              }

            },

            generalParametersMRDC {

              splitDRB-withUL-Both-MCG-SCG supported

            },

            featureSetCombinations {

              {

                {

                  eutra: {

                    downlinkSetEUTRA 3,

                    uplinkSetEUTRA 1

                  }

                },

                {

                  nr: {

                    downlinkSetNR 1,

                    uplinkSetNR 1

                  }

                }

              }

            }

          }

        }

 

    Example 17 : Parameters determining Ideal Max Throughput

       

      This is pretty complicated story and explained in a separate note here.

How to handle the ever increasing size of UE capability Information ? - RRC Segmentation

As far as I recall, I have seen many issues even from LTE only cases in later 3GPP release in terms of processing UE capability information in both UE and network (or network simulator) side.

Sometimes UE fails to generate the well structured UE capability information with huge set of features, especially when the number of carrier aggregation gets increased. And problems heppens in network side in similar situation failing to decode properly the lengthy and complicated UE capability Information message.

This issue has become even more serious in NR (both SA and NSA). NR UE capability features in NR is much more complicated than LTE. When the number of aggregated carrier gets increases, the size of the UE capability Information message exceeds the maximum size of RRC signaling message.

To workaround this situation, a new mechanism of RRC signaling is introduced. The new mechanism is called 'Segmented RRC Message'. For further details of this mechanism, I would like to share what Anupam Shrivastava kindly contributed as below.

With the introduction of new UE-capa every release the size of RRC is increasing( below study on UE-capa IE introduction with different 3gpp releases from Rel-15.1 till Rel-17) and in scenarios of CA, HO there are situations when the RRC size will exceed the limit for 9k bytes as explained above for the NR, to overcome this situation we need to fragment/segment the capa into smaller chunks for which Segmentation is introduced, though it comes with a cost of additional delay in UECapabilityinformation received by gNB , as gNB need extra time to receive all segments and then reassemble them.

 

The maximum supported size of a PDCP SDU is 9000 bytes. The maximum supported size of a PDCP Control PDU is 9000 bytes. So the UE capability Information with size greater than 9000 byte should be split into multiple rrc messages and then combined later.

The RRC message carrying each of the segment is as follows :

ULDedicatedMessageSegment-r16 ::= SEQUENCE {

   criticalExtensions CHOICE {

      ulDedicatedMessageSegment-r16                 ULDedicatedMessageSegment-r16-IEs,

      criticalExtensionsFuture                             SEQUENCE {}

   }

}

ULDedicatedMessageSegment-r16-IEs ::= SEQUENCE {

   segmentNumber-r16                                     INTEGER (0..15),

   rrc-MessageSegmentContainer-r16                  OCTET STRING,

   rrc-MessageSegmentType-r16                        ENUMERATED {notLastSegment, lastSegment},

   lateNonCriticalExtension                                 OCTET STRING OPTIONAL,

   nonCriticalExtension                                      SEQUENCE {} OPTIONAL

}

Example 01 >

Following is an example log from Amarisoft Callbox (gNB) and UEsim.

 

[1] First Segment

{

  message messageClassExtension: c2: ulDedicatedMessageSegment-r16: {

    criticalExtensions ulDedicatedMessageSegment-r16: {

      segmentNumber-r16 0,

      rrc-MessageSegmentContainer-r16 '48821EB0694CE8100C0241E0601C0660140702D...'H,

      rrc-MessageSegmentType-r16 notLastSegment

    }

  }

}

 

[2] Second / Last Segment

{

  message messageClassExtension: c2: ulDedicatedMessageSegment-r16: {

    criticalExtensions ulDedicatedMessageSegment-r16: {

      segmentNumber-r16 1,

      rrc-MessageSegmentContainer-r16 '00A471434003800780000...0'H,

      rrc-MessageSegmentType-r16 lastSegment

    }

  }

}

 

[3] Recombined Message

{

  message c1: ueCapabilityInformation: {

    rrc-TransactionIdentifier 0,

    criticalExtensions ueCapabilityInformation: {

      ue-CapabilityRAT-ContainerList {

        ....

            },

            nonCriticalExtension {

              nonCriticalExtension {

                ims-Parameters {

                  ims-ParametersFRX-Diff {

                    voiceOverNR supported

                  }

                },

                nonCriticalExtension {

                  nonCriticalExtension {

                    receivedFilters {

                      nonCriticalExtension {

                        rrc-SegAllowed-r16 enabled

                      }

                    },

                    nonCriticalExtension {

                      nonCriticalExtension {

                        dl-DedicatedMessageSegmentation-r16 supported,

                        powSav-Parameters-r16 {

                          powSav-ParametersCommon-r16 {

                            releasePreference-r16 supported

                          }

                        },

                        nonCriticalExtension {

                          nonCriticalExtension {

                            nonCriticalExtension {

                              ul-RRC-Segmentation-r16 supported

                            }

Reference

[1]