5G/NR - UL TxSwitching

UL TxSwitching

In 5G NR, uplink (UL) Tx-antenna switching is a feature that lets a UE dynamically move its two physical transmitter chains between different uplink carriers, so it can momentarily send two-layer MIMO on a capacity-focused band and then swing one chain back to a coverage-focused band when high throughput is no longer required. Instead of keeping each power amplifier permanently tied to a specific carrier—as older LTE devices do—the NR UE follows rules signalled once by RRC (how long the retune gap may be, which carriers form the pair, and where in the slot the hop must occur) and then automatically inserts a very short mute-and-retune pause whenever the scheduler directs the next PUSCH, PUCCH, or SRS grant to the opposite carrier. This approach squeezes extra uplink capacity out of the same two-Tx hardware budget, saves power by activating both chains only when needed, and gives operators flexibility to blend wide-band mid-/high-band performance with low-band coverage in real time.

Why UL TxSwitching ?
Release Evolution
Comparison to SUL
UE Capability Information
RRC Parameters
Examples

Why UL TxSwitching ?

When a 5 G handset aggregates a wide-band TDD carrier that can exploit two-layer MIMO with a narrow, low-frequency FDD carrier that needs only a single layer, engineers face a trade-off between hardware complexity and uplink performance.

For illustration of why we came up with the concept called UL Tx stiching, let's think of three different cases of operating UL CA with a narrowband FDD and windband TDD band as shown below. These three cases visualise the hardware dilemma a handset faces when it is doing uplink carrier aggregation (UL-CA) between a coverage carrier (a narrow-band, low-frequency FDD cell that needs at most one UL layer) and a capacity carrier (a wide-band, mid/high-frequency TDD cell that can exploit two UL layers)

Keeping a dedicated transmitter chain on each carrier while adding a third chain for the second TDD layer would maximise throughput, but such a three-PA design is expensive, power-hungry and impractical for modern smartphones. Conversely, fixing one chain per carrier and restricting the TDD cell to a single layer preserves the two-PA budget but sacrifices half of the wide-band carrier’s potential capacity. UL Tx-antenna switching offers a middle ground: the UE time-shares its two transmit chains, momentarily moving both to the TDD carrier whenever the scheduler needs a two-layer burst, then returning one chain to the FDD carrier for routine coverage. This mechanism unlocks near-ideal high-band uplink peaks without adding hardware, all at the cost of brief, carefully timed transmission gaps on the low-band link. This situation can be summarized in a table shown below. It shows why Case C (UL Tx Switching) is the most practical option.

Case	What happens	Hardware you would need	Throughput outcome
Case A – “Ideal but impossible”	The UE keeps sending 1-layer PUSCH on the FDD carrier every slot and bursts 2-layer PUSCH in the TDD UL symbols.	3 simultaneous Tx chains (2 + 1) – a form-factor, cost and SAR non-starter for a smartphone.	Best of both worlds, but unrealistic.
Case B – “Feasible but throttled”	The UE limits the TDD carrier to 1 layer, so the two available Tx chains can stay permanently split: one on FDD, one on TDD.	2 Tx chains (today’s handset reality).	No extra hardware, yet the wide-band carrier loses half its potential UL throughput.
Case C – “UL Tx-antenna switching”	Whenever the scheduler needs a 2-layer burst on the TDD carrier, both Tx chains momentarily hop over; the FDD carrier is muted for those few symbols. The chains hop back afterwards.	Still only 2 Tx chains, because they are time-shared instead of being driven in parallel.	You get the near-ideal 2-layer peaks of Case A most of the time, with only brief coverage gaps on the FDD carrier.

Why the feature is attractive

Cost & power: keeps the UE at the standard two RF power amplifiers; no extra PA, filter set or antenna feed is needed.
SAR & thermal limits: avoids pushing a third active transmitter into a tight handset enclosure.
Performance boost: delivers 2-layer UL bursts on the high-band carrier exactly when large data blocks or HARQ retransmissions demand them, rather than being permanently stuck at 1 layer.
Coverage safety-net: the low-band FDD link resumes right after the short switching gap, so cell-edge robustness is largely preserved.

Release Evolution

The UL Tx Switching functionality has been evolved over a few releases starting from Rel 16 through Rel 18.

Release 16: Baseline 1Tx→2Tx hopping

In Rel-16 the specification introduced the core idea of dynamic uplink switching between exactly two carriers. A UE with only two RF chains could still burst two-layer MIMO on a high-band TDD carrier by momentarily muting its low-band FDD link, inserting a short RF retune gap, then transmitting both chains on the TDD layer. This gave operators a pragmatic balance of coverage (via low-band FDD) and capacity (via wide-band TDD) without adding a third PA. All timing-gap rules, DL mute allowances and basic RRC parameters (band-pair definition, gap length and symbol boundary) were defined in TS 38.101, TS 38.133 and TS 38.214.

Release 17: Full 2Tx→2Tx, 3CC CA, SRS switching & power boost

Rel-17 significantly broadened the scope:

2Tx→2Tx mode allows the UE to swap both chains simultaneously in either direction—mid-band ↔ high-band—rather than only 1Tx→2Tx.
3CC aggregation support lets three distinct UL carriers participate in switching, enabling dynamic bursts across multiple layers and bands.
Explicit SRS-based hopping ensures that sounding reference signals follow the same antenna-switch pattern, so the network always has accurate channel estimates on the active carrier.
Power-boosting option (+3 dB) was added so that during a two-port burst the UE may temporarily raise its output power on the secondary carrier, improving SINR at the expense of battery.

All these enhancements required new RRC IEs and updates to TS 38.307 test cases to validate the multi-carrier and boosted-power behaviors.

Release 18: Granular capability bits, tighter DL interruption & clarified tests

Rel-18 refines and hardens the mechanism:

Per-band-pair capability bits allow a UE to declare exactly which band pairs support 1Tx→2Tx, which support 2Tx→2Tx, and at which switching option, replacing the coarse “one-size-fits-all” model with fine-grained control.
Tightened DL-interruption limits in TS 38.133 reduce the maximum PDCCH/PDSCH blackout windows during retune gaps, improving downlink reliability in dense scheduling scenarios.
Clarified test scenarios in TS 38.307 Annex B.15–B.17 cover edge cases like simultaneous grants on adjacent carriers, multi-band hopping under FR2, and overlapping SRS/PUSCH timing, ensuring robust UE implementation across diverse network configurations.

These Release-18 updates make UL Tx-antenna-switching a robust, carrier-agnostic tool that operators can safely deploy even in the most demanding high-throughput and low-latency environments.

Comparision to SUL

In Release 15, 3GPP introduced “Supplemental Uplink” as a way to borrow uplink capacity from an FDD band whenever a TDD cell had downlink-only subframes. At a high level, the network configures the UE so that during the TDD cell’s DL slots—when it normally can’t send uplink—it instead fires its FDD transmitter on the companion band. From the UE’s perspective this requires either one or two RF chains: if it has two it could even split them between the FDD and TDD UL subframes. Because the FDD UL band typically uses 15 kHz subcarriers (versus 30 kHz in TDD), the supplemental link is narrower, so throughput gain is modest; on the other hand there is no RF retune delay, since each chain stays locked to its native band at all times.

Switched Uplink, which landed in Release 16, takes a more aggressive approach. Rather than permanently pinning one RF chain to each band, the UE momentarily “hops” both chains onto the high-band TDD carrier whenever the scheduler wants a two-layer MIMO burst, then returns one chain to the FDD carrier for coverage. This time-sharing lets the device deliver up to two full MIMO layers on the wide-band TDD link—roughly doubling peak UL throughput—while still preserving low-band coverage the rest of the time. The only trade-off is a short mute-and-retune gap (tens to a few hundred microseconds) each time the UE switches, which Release 16 bounds tightly and which later Releases refine further.

The comparison between SUL and UL Tx Switching is summarized in table as shown below (source : 2023 Switched Uplink in 5G-NR: Benefit & Deployment Consideration )

Description	Release 15 Supplemental UL	Rel 16 Switched UL
UL Tx Scenarios	Case 1: 1Tx on each band	Case 1: 1Tx on each band, OR Case 2: 2Tx on UL MIMO band
Peak UL Throughput	Low, due to limit on only 1Tx on each band	High, due to 2Tx on TDD band allowed, which is larger BW band as well
2L UL MIMO	No possible	Possible (Case 2 for both Option 1 & Option 2)
UL Switching Delay	No, since each of 2 UE RF chains locked to FDD band and TDD band	Yes, switching delay (35/140/210 µs), except Option 2, Case 1.

UE Capability Information

Before gNB decide whether to apply UL Tx Switching or not, the UE should advertises the feature in UE-NR-Capability. Followings are the list of UE capability Information that a UE would notify.

Band-pair level IEs (Per = BC)

ULTxSwitchingBandPair-r16 / ULTxSwitchingBandPair-v1700
- Status = FD – container that enables dynamic UL Tx switching (1Tx→2Tx or 2Tx→2Tx) for inter-band CA, SUL or (N)GEN-DC.
- bandIdx1-r16, bandIdx2-r16 – mandatory inside the IE; identify the two UL bands.
- uplinkTxSwitchingPeriod-r16 – mandatory when the UE claims 1Tx→2Tx; gap length (e.g. n35 = 35 µs).
- uplinkTxSwitchingPeriod2T2T-r17 – mandatory for 2Tx→2Tx; gap length for that mode.
- uplinkTxSwitchingDL-Interruption-r16 – optional; bitmap allowing DL mute during the gap (not valid for SUL-only or TDD+TDD pairs).
uplinkTxSwitchingOptionSupport-r16
- Status = CY – becomes mandatory when 1Tx→2Tx switching is advertised.
- switchcIUL = Option 1, dualUL = Option 2 (per TS 38 214 § 12).
uplinkTxSwitchingOptionSupport2T2T-r17
- Status = CY – becomes mandatory when 2Tx→2Tx switching is advertised.
- option1, option2 encoded as in TS 38 214 § 12.
- At least one option must also appear in uplinkTxSwitchingOptionSupport-r16.
uplinkTxSwitchingPowerBoosting-r16
- Status = No – optional flag that the UE can raise max Tx power on the active carrier while the other is muted.

Band-specific detail IE (Per = BC)

UplinkTxSwitchingBandParameters-v1700
- Status = No – each instance is optional and scoped to one band of the combination.
- bandIndex-r17 – mandatory inside the IE; points to the band able to switch.
- uplinkTxSwitching-PUSCH-TransCoherence-r16 – optional; codebook subset for scheduled PUSCH when the hop is triggered between the last SRS and that PUSCH.
  If absent, the UE re-uses the general pusch-TransCoherence capability.

RRC Parameters

When a gNB configures a handset for dynamic uplink antenna switching, it uses a handful of specialized information elements to control exactly how and when the UE moves its transmit chains between carriers. The uplinkTxSwitchingOption tells the device whether to perform a one-to-two-chain burst or a full two-to-two-chain handover, while the optional uplinkTxSwitchingPowerBoosting flag lets the network grant a temporary 3 dB boost on the secondary carrier during a two-port transmission. For pure two-chain handoffs, the uplinkTxSwitching-2T-Mode IE ensures the mute-and-retune gap matches the UE’s reported dual-Tx timing, falling back to single-to-dual-Tx rules only if it’s absent. In Release 18, the uplinkTxSwitching-DualUL-TxState field disambiguates the post-switch Tx-chain count when two-chain mode is in use, and the new uplinkTxSwitchingMoreBands container extends the basic pair-of-bands model to larger CA/SUL groupings. Together, these parameters give the gNB precise, per-scenario control over the UE’s UL-antenna behavior

UplinkConfig ::= SEQUENCE {

...

uplinkTxSwitching-r16 SetupRelease { UplinkTxSwitching-r16 } OPTIONAL, -- Need M

...

}

UplinkTxSwitching-r16 ::= SEQUENCE {

uplinkTxSwitchingPeriodLocation-r16 BOOLEAN,

uplinkTxSwitchingCarrier-r16 ENUMERATED {carrier1, carrier2}

}

UplinkTxSwitchingMoreBands-r18::= SEQUENCE {

uplinkTxSwitchingBandList-r18 SEQUENCE (SIZE (1..maxSimultaneousBands))

OF FreqBandIndicatorNR OPTIONAL, -- Need M

uplinkTxSwitchingBandPairList-r18 UplinkTxSwitchingBandPairList-r18 OPTIONAL, -- Need M

uplinkTxSwitchingAssociatedBandDualUL-List-r18 UplinkTxSwitchingAssociatedBandDualUL-List-r18

OPTIONAL, -- Need M

...

}

UplinkTxSwitchingBandPairList-r18::= SEQUENCE (SIZE (1.. maxULTxSwitchingBandPairs))

OF UplinkTxSwitchingBandPairConfig-r18

UplinkTxSwitchingBandPairConfig-r18::= SEQUENCE {

bandInfoUL1-r18 UplinkTxSwitchingBandIndex-r18,

bandInfoUL2-r18 UplinkTxSwitchingBandIndex-r18,

switchingOptionConfigForBandPair-r18 ENUMERATED {switchedUL, dualUL},

switching2T-Mode-r18 ENUMERATED {enabled} OPTIONAL, -- Need S

switchingPeriodConfigForBandPair-r18 ENUMERATED {n35us, n140us} OPTIONAL, -- Need S

. ..

}

UplinkTxSwitchingAssociatedBandDualUL-List-r18::= SEQUENCE (SIZE (0..maxSimultaneousBands)) OF

UplinkTxSwitchingAssociatedBandDualUL-r18

UplinkTxSwitchingAssociatedBandDualUL-r18::= SEQUENCE {

transmitBand-r18 UplinkTxSwitchingBandIndex-r18,

associatedBand-r18 UplinkTxSwitchingBandIndex-r18

}

UplinkTxSwitchingBandIndex-r18::= INTEGER (1..maxSimultaneousBands)

Followings are the description for some of the key information elements

uplinkTxSwitchingPeriodLocation

Specifies whether the UL-Tx switching gap is placed on this uplink carrier (for inter-band UL CA, SUL or (NG)EN-DC as per TS 38.101-1/-3).
(NG)EN-DC: always set to TRUE on the NR carrier (the gap always occurs on NR).
Inter-band UL CA/SUL: set to TRUE on all uplink carriers of one band and FALSE on all carriers of the other band; carriers on the same band share the same value.

uplinkTxSwitchingCarrier

Identifies whether this uplink carrier is “carrier 1” or “carrier 2” in the dynamic-switching pair (per TS 38.101-1/-3).
(NG)EN-DC: the NR carrier is always configured as carrier 2.
Inter-band UL CA/SUL: all uplink carriers on one band are marked carrier 1, and those on the other band carrier 2; all carriers on the same band use the same designation.

uplinkTxSwitchingOption : Indicates which UL-Tx-switching option the gNB has configured for inter-band UL CA or (NG)EN-DC. It will be set to switchedUL if Option 1 (1Tx→2Tx) is used, or dualUL if Option 2 (2Tx→2Tx) is used. The network always provides this IE when the UE supports dynamic UL Tx switching in inter-band scenarios.
uplinkTxSwitchingPowerBoosting : Signals whether the UE is allowed to apply a +3 dB power boost on the “secondary” carrier during a 2-port UL burst in inter-band UL CA. Only power-class 3 UEs may be configured with this IE, and only when dynamic UL Tx-switching is active.
uplinkTxSwitching-2T-Mode : Turns on 2Tx→2Tx switching mode for inter-band UL CA or SUL, meaning the retune gap length equals the UE’s reported 2Tx-mode switching time. If this IE is absent (but UL Tx-switching is present), the UE defaults to 1Tx→2Tx switching rules: exactly one UL band in the pair is switch-enabled, only a single antenna-port SP-SRS/A-SRS is active, and non-codebook UL MIMO is disabled.
uplinkTxSwitching-DualUL-TxState (Rel-18) : When dualUL (2Tx→2Tx) switching is configured and the post-switch Tx-chain state is ambiguous, this IE indicates for each carrier whether the UE should assume 1Tx or 2Tx capability. It applies across all band pairs if uplinkTxSwitchingMoreBands is in use.
uplinkTxSwitchingMoreBands (Rel-18) : Provides a list of UL bands, band-pairs, and associated settings for multi-band UL Tx-switching (beyond the basic two-band case). It drives the creation of multiple ULTxSwitchingBandPair entries under complex CA/SUL configurations.

Examples

Example 1 : UL Tx Switching - 1Tx -> 2 Tx

This example exercises the complete 1Tx→2Tx UL antenna-switching procedure end-to-end. It first confirms that the network can discover and the UE can report its dynamic Tx-switching capability, then has the gNB install the exact timing and band-pair rules via RRC. Finally, it verifies that the UE’s lower layers actually mute the low-band chain, retune its RF path and burst two-layer MIMO on the high-band carrier whenever the scheduler demands it, all in accordance with the 3GPP UL Tx-switching specifications.

Dir	Message	Comments
UE <- NW	UE Capability Enquiry	NW Request for UE capability about UL Tx Switching
UE -> NW	UE Capability Information	UE notifies its capability on
UE <- NW	RRC Reconfiguration	UL Tx Switching
UE -> NW	RRC Reconfiguration Complete	NW Configure Rules for UL Tx Switching
UE <-> NW	<UL Tx Swithing >	Switching happens dynamically at low layer

The following log is from a test with Amarisoft Callbox and Amarisoft UE simulator

UE Capability Enquiry

{

message c1: ueCapabilityEnquiry: {

rrc-TransactionIdentifier 0,

criticalExtensions ueCapabilityEnquiry: {

ue-CapabilityRAT-RequestList {

{

rat-Type nr,

capabilityRequestFilter {

frequencyBandListFilter {

bandInformationNR: {

bandNR 7

bandInformationNR: {

bandNR 38

}

ue-CapabilityEnquiryExt {

capabilityRequestFilterCommon {

uplinkTxSwitchRequest-r16 true

nonCriticalExtension {

rrc-SegAllowed-r16 enabled

}

UE Capability Information

{

message c1: ueCapabilityInformation: {

rrc-TransactionIdentifier 0,

criticalExtensions ueCapabilityInformation: {

ue-CapabilityRAT-ContainerList {

{

rat-Type nr,

ue-CapabilityRAT-Container {

accessStratumRelease rel16,

pdcp-Parameters {

supportedROHC-Profiles {

profile0x0000 TRUE,

profile0x0001 TRUE,

profile0x0002 TRUE,

profile0x0003 FALSE,

profile0x0004 TRUE,

profile0x0006 FALSE,

profile0x0101 FALSE,

profile0x0102 FALSE,

profile0x0103 FALSE,

profile0x0104 FALSE

maxNumberROHC-ContextSessions cs16,

outOfOrderDelivery supported,

shortSN supported,

extendedDiscardTimer-r16 supported

rlc-Parameters {

am-WithShortSN supported,

um-WithShortSN supported,

um-WithLongSN supported,

extendedT-PollRetransmit-r16 supported,

extendedT-StatusProhibit-r16 supported

mac-Parameters {

mac-ParametersXDD-Diff {

longDRX-Cycle supported,

shortDRX-Cycle supported,

enhancedSkipUplinkTxDynamic-r16 supported,

enhancedSkipUplinkTxConfigured-r16 supported

}

phy-Parameters {

phy-ParametersCommon {

dynamicHARQ-ACK-Codebook supported,

spatialBundlingHARQ-ACK supported,

dynamicBetaOffsetInd-HARQ-ACK-CSI supported,

ra-Type0-PUSCH supported,

dynamicSwitchRA-Type0-1-PDSCH supported,

dynamicSwitchRA-Type0-1-PUSCH supported,

pdsch-MappingTypeA supported,

pdsch-MappingTypeB supported,

interleavingVRB-ToPRB-PDSCH supported,

pusch-RepetitionMultiSlots supported,

pdsch-RepetitionMultiSlots supported,

configuredUL-GrantType1 supported,

configuredUL-GrantType2 supported,

rateMatchingResrcSetSemi-Static supported,

rateMatchingResrcSetDynamic supported,

bwp-SwitchingDelay type1,

rateMatchingCtrlResrcSetDynamic supported,

maxLayersMIMO-Indication supported,

twoStepRACH-r16 supported,

pusch-RepetitionTypeA-r16 {

non-SharedSpectrumChAccess-r16 supported

}

phy-ParametersFRX-Diff {

twoFL-DMRS '11'B,

supportedDMRS-TypeDL type1And2,

supportedDMRS-TypeUL type1And2,

onePortsPTRS '11'B,

pucch-F2-WithFH supported,

pucch-F3-WithFH supported,

pucch-F4-WithFH supported,

pusch-HalfPi-BPSK supported,

pucch-F3-4-HalfPi-BPSK supported,

mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot {

sameSymbol supported

mux-SR-HARQ-ACK-PUCCH supported,

dl-SchedulingOffset-PDSCH-TypeA supported,

dl-SchedulingOffset-PDSCH-TypeB supported,

ul-SchedulingOffset supported,

dl-64QAM-MCS-TableAlt supported,

ul-64QAM-MCS-TableAlt supported,

cqi-TableAlt supported,

oneFL-DMRS-TwoAdditionalDMRS-UL supported,

twoFL-DMRS-TwoAdditionalDMRS-UL supported,

oneFL-DMRS-ThreeAdditionalDMRS-UL supported,

maxLayersMIMO-Adaptation-r16 supported

phy-ParametersFR1 {

pdsch-256QAM-FR1 supported

}

rf-Parameters {

supportedBandListNR {

{

bandNR 7,

mimo-ParametersPerBand {

pusch-TransCoherence fullCoherent,

beamManagementSSB-CSI-RS {

maxNumberSSB-CSI-RS-ResourceOneTx n32,

maxNumberCSI-RS-Resource n0,

maxNumberCSI-RS-ResourceTwoTx n0,

maxNumberAperiodicCSI-RS-Resource n0

codebookParameters {

type1 {

singlePanel {

supportedCSI-RS-ResourceList {

{

maxNumberTxPortsPerResource p32,

maxNumberResourcesPerBand 1,

totalNumberTxPortsPerBand 32

}

modes mode1andMode2,

maxNumberCSI-RS-PerResourceSet 1

}

csi-RS-IM-ReceptionForFeedback {

maxConfigNumberNZP-CSI-RS-PerCC 8,

maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC 32,

maxConfigNumberCSI-IM-PerCC n4,

maxNumberSimultaneousNZP-CSI-RS-PerCC 8,

totalNumberPortsSimultaneousNZP-CSI-RS-PerCC 64

csi-ReportFramework {

maxNumberPeriodicCSI-PerBWP-ForCSI-Report 1,

maxNumberAperiodicCSI-PerBWP-ForCSI-Report 1,

maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report 0,

maxNumberPeriodicCSI-PerBWP-ForBeamReport 1,

maxNumberAperiodicCSI-PerBWP-ForBeamReport 1,

maxNumberAperiodicCSI-triggeringStatePerCC n3,

maxNumberSemiPersistentCSI-PerBWP-ForBeamReport 0,

simultaneousCSI-ReportsPerCC 5

supportInter-slotTDM-r16 {

supportRepNumPDSCH-TDRA-r16 n16,

maxTBS-Size-r16 noRestriction,

maxNumberTCI-states-r16 1

lowPAPR-DMRS-PDSCH-r16 supported,

lowPAPR-DMRS-PUSCHwithoutPrecoding-r16 supported

bwp-WithoutRestriction supported,

bwp-SameNumerology upto4,

pusch-256QAM supported,

rateMatchingLTE-CRS supported,

channelBWs-DL fr1: {

scs-15kHz '1111000000'B,

scs-30kHz '0000000000'B,

scs-60kHz '0000000000'B

channelBWs-UL fr1: {

scs-15kHz '1111000000'B,

scs-30kHz '0000000000'B,

scs-60kHz '0000000000'B

}

{

bandNR 38,

mimo-ParametersPerBand {

pusch-TransCoherence fullCoherent,

beamManagementSSB-CSI-RS {

maxNumberSSB-CSI-RS-ResourceOneTx n32,

maxNumberCSI-RS-Resource n0,

maxNumberCSI-RS-ResourceTwoTx n0,

maxNumberAperiodicCSI-RS-Resource n0

codebookParameters {

type1 {

singlePanel {

supportedCSI-RS-ResourceList {

{

maxNumberTxPortsPerResource p32,

maxNumberResourcesPerBand 1,

totalNumberTxPortsPerBand 32

}

modes mode1andMode2,

maxNumberCSI-RS-PerResourceSet 1

}

csi-RS-IM-ReceptionForFeedback {

maxConfigNumberNZP-CSI-RS-PerCC 8,

maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC 32,

maxConfigNumberCSI-IM-PerCC n4,

maxNumberSimultaneousNZP-CSI-RS-PerCC 8,

totalNumberPortsSimultaneousNZP-CSI-RS-PerCC 64

csi-ReportFramework {

maxNumberPeriodicCSI-PerBWP-ForCSI-Report 1,

maxNumberAperiodicCSI-PerBWP-ForCSI-Report 1,

maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report 0,

maxNumberPeriodicCSI-PerBWP-ForBeamReport 1,

maxNumberAperiodicCSI-PerBWP-ForBeamReport 1,

maxNumberAperiodicCSI-triggeringStatePerCC n3,

maxNumberSemiPersistentCSI-PerBWP-ForBeamReport 0,

simultaneousCSI-ReportsPerCC 5

supportInter-slotTDM-r16 {

supportRepNumPDSCH-TDRA-r16 n16,

maxTBS-Size-r16 noRestriction,

maxNumberTCI-states-r16 1

lowPAPR-DMRS-PDSCH-r16 supported,

lowPAPR-DMRS-PUSCHwithoutPrecoding-r16 supported

bwp-WithoutRestriction supported,

bwp-SameNumerology upto4,

pusch-256QAM supported,

rateMatchingLTE-CRS supported,

channelBWs-DL fr1: {

scs-15kHz '0000000000'B,

scs-30kHz '1111000000'B,

scs-60kHz '0000000000'B

channelBWs-UL fr1: {

scs-15kHz '0000000000'B,

scs-30kHz '1111000000'B,

scs-60kHz '0000000000'B

}

supportedBandCombinationList {

{

bandList {

nr: {

bandNR 7,

ca-BandwidthClassDL-NR a,

ca-BandwidthClassUL-NR a

nr: {

bandNR 38,

ca-BandwidthClassDL-NR a

}

featureSetCombination 0,

ca-ParametersNR {

simultaneousRxTxInterBandCA supported,

diffNumerologyWithinPUCCH-GroupSmallerSCS supported

supportedBandwidthCombinationSet '1'B

{

bandList {

nr: {

bandNR 7,

ca-BandwidthClassDL-NR a

nr: {

bandNR 38,

ca-BandwidthClassDL-NR a,

ca-BandwidthClassUL-NR a

}

featureSetCombination 1,

ca-ParametersNR {

simultaneousRxTxInterBandCA supported,

diffNumerologyWithinPUCCH-GroupSmallerSCS supported

supportedBandwidthCombinationSet '1'B

{

bandList {

nr: {

bandNR 7,

ca-BandwidthClassDL-NR a,

ca-BandwidthClassUL-NR a

}

featureSetCombination 2

{

bandList {

nr: {

bandNR 38,

ca-BandwidthClassDL-NR a,

ca-BandwidthClassUL-NR a

}

featureSetCombination 3

}

appliedFreqBandListFilter {

bandInformationNR: {

bandNR 7

bandInformationNR: {

bandNR 38

}

supportedBandCombinationList-v1540 {

{

bandList-v1540 {

{

srs-TxSwitch {

supportedSRS-TxPortSwitch notSupported

}

{

}

ca-ParametersNR-v1540 {

csi-RS-IM-ReceptionForFeedbackPerBandComb {

maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC 16,

totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC 64

simultaneousCSI-ReportsAllCC 5

}

{

bandList-v1540 {

{

srs-TxSwitch {

supportedSRS-TxPortSwitch t2r2

}

ca-ParametersNR-v1540 {

csi-RS-IM-ReceptionForFeedbackPerBandComb {

maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC 16,

totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC 64

simultaneousCSI-ReportsAllCC 5

}

{

bandList-v1540 {

{

srs-TxSwitch {

supportedSRS-TxPortSwitch notSupported

}

{

bandList-v1540 {

{

srs-TxSwitch {

supportedSRS-TxPortSwitch t2r2

}

supportedBandCombinationList-UplinkTxSwitch-r16 {

{

bandCombination-r16 {

bandList {

nr: {

bandNR 7,

ca-BandwidthClassDL-NR a,

ca-BandwidthClassUL-NR a

nr: {

bandNR 38,

ca-BandwidthClassDL-NR a,

ca-BandwidthClassUL-NR a

}

featureSetCombination 4,

ca-ParametersNR {

simultaneousRxTxInterBandCA supported,

diffNumerologyWithinPUCCH-GroupSmallerSCS supported

supportedBandwidthCombinationSet '1'B

bandCombination-v1540 {

bandList-v1540 {

{

srs-TxSwitch {

supportedSRS-TxPortSwitch notSupported

}

{

srs-TxSwitch {

supportedSRS-TxPortSwitch t2r2

}

ca-ParametersNR-v1540 {

csi-RS-IM-ReceptionForFeedbackPerBandComb {

maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC 16,

totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC 64

simultaneousCSI-ReportsAllCC 5

}

supportedBandPairListNR-r16 {

{

bandIndexUL1-r16 1,

bandIndexUL2-r16 2,

uplinkTxSwitchingPeriod-r16 n140us

}

uplinkTxSwitching-OptionSupport-r16 switchedUL

}

measAndMobParameters {

measAndMobParametersCommon {

supportedGapPattern '1111111111111111111111'B,

handoverFDD-TDD supported,

nr-CGI-Reporting supported,

nr-NeedForGap-Reporting-r16 supported,

nr-CGI-Reporting-NPN-r16 supported

measAndMobParametersXDD-Diff {

handoverInterF supported

measAndMobParametersFRX-Diff {

ss-SINR-Meas supported,

handoverInterF supported,

simultaneousRxDataSSB-DiffNumerology supported

}

featureSets {

featureSetsDownlink {

{

featureSetListPerDownlinkCC {

}

{

featureSetListPerDownlinkCC {

}

featureSetsDownlinkPerCC {

{

supportedSubcarrierSpacingDL kHz15,

supportedBandwidthDL fr1: mhz20,

maxNumberMIMO-LayersPDSCH twoLayers,

supportedModulationOrderDL qam256

{

supportedSubcarrierSpacingDL kHz30,

supportedBandwidthDL fr1: mhz20,

maxNumberMIMO-LayersPDSCH twoLayers,

supportedModulationOrderDL qam256

}

featureSetsUplink {

{

featureSetListPerUplinkCC {

supportedSRS-Resources {

maxNumberAperiodicSRS-PerBWP n16,

maxNumberAperiodicSRS-PerBWP-PerSlot 6,

maxNumberPeriodicSRS-PerBWP n16,

maxNumberPeriodicSRS-PerBWP-PerSlot 6,

maxNumberSemiPersistentSRS-PerBWP n16,

maxNumberSemiPersistentSRS-PerBWP-PerSlot 6,

maxNumberSRS-Ports-PerResource n2

}

{

featureSetListPerUplinkCC {

supportedSRS-Resources {

maxNumberAperiodicSRS-PerBWP n16,

maxNumberAperiodicSRS-PerBWP-PerSlot 6,

maxNumberPeriodicSRS-PerBWP n16,

maxNumberPeriodicSRS-PerBWP-PerSlot 6,

maxNumberSemiPersistentSRS-PerBWP n16,

maxNumberSemiPersistentSRS-PerBWP-PerSlot 6,

maxNumberSRS-Ports-PerResource n2

}

featureSetsUplinkPerCC {

{

supportedSubcarrierSpacingUL kHz15,

supportedBandwidthUL fr1: mhz20,

mimo-CB-PUSCH {

maxNumberMIMO-LayersCB-PUSCH twoLayers,

maxNumberSRS-ResourcePerSet 1

maxNumberMIMO-LayersNonCB-PUSCH twoLayers,

supportedModulationOrderUL qam256

{

supportedSubcarrierSpacingUL kHz30,

supportedBandwidthUL fr1: mhz20,

mimo-CB-PUSCH {

maxNumberMIMO-LayersCB-PUSCH twoLayers,

maxNumberSRS-ResourcePerSet 1

maxNumberMIMO-LayersNonCB-PUSCH twoLayers,

supportedModulationOrderUL qam256

}

featureSetsDownlink-v1540 {

{

oneFL-DMRS-TwoAdditionalDMRS-DL supported,

additionalDMRS-DL-Alt supported,

twoFL-DMRS-TwoAdditionalDMRS-DL supported,

oneFL-DMRS-ThreeAdditionalDMRS-DL supported

{

oneFL-DMRS-TwoAdditionalDMRS-DL supported,

additionalDMRS-DL-Alt supported,

twoFL-DMRS-TwoAdditionalDMRS-DL supported,

oneFL-DMRS-ThreeAdditionalDMRS-DL supported

}

featureSetsUplinkPerCC-v1540 {

{

mimo-NonCB-PUSCH {

maxNumberSRS-ResourcePerSet 2,

maxNumberSimultaneousSRS-ResourceTx 1

}

{

mimo-NonCB-PUSCH {

maxNumberSRS-ResourcePerSet 2,

maxNumberSimultaneousSRS-ResourceTx 1

}

featureSetsUplink-v1610 {

{

ul-FullPwrMode1-r16 supported

{

ul-FullPwrMode1-r16 supported

}

featureSetCombinations {

{

nr: {

downlinkSetNR 1,

uplinkSetNR 1

}

{

nr: {

downlinkSetNR 2,

uplinkSetNR 0

}

{

nr: {

downlinkSetNR 1,

uplinkSetNR 0

}

{

nr: {

downlinkSetNR 2,

uplinkSetNR 2

}

{

nr: {

downlinkSetNR 1,

uplinkSetNR 1

}

{

nr: {

downlinkSetNR 2,

uplinkSetNR 2

}

{

nr: {

downlinkSetNR 1,

uplinkSetNR 1

}

{

nr: {

downlinkSetNR 2,

uplinkSetNR 2

}

nonCriticalExtension {

ims-Parameters {

ims-ParametersFRX-Diff {

voiceOverNR supported

}

nonCriticalExtension {

receivedFilters {

capabilityRequestFilterCommon {

uplinkTxSwitchRequest-r16 true

nonCriticalExtension {

rrc-SegAllowed-r16 enabled

}

nonCriticalExtension {

dl-DedicatedMessageSegmentation-r16 supported,

powSav-Parameters-r16 {

powSav-ParametersCommon-r16 {

maxCC-Preference-r16 supported,

releasePreference-r16 supported

powSav-ParametersFRX-Diff-r16 {

maxMIMO-LayerPreference-r16 supported

}

mac-Parameters-v1610 {

mac-ParametersFRX-Diff-r16 {

directMCG-SCellActivation-r16 supported

}

nonCriticalExtension {

ul-RRC-Segmentation-r16 supported

}

RRC Reconfiguration

{

message c1: rrcReconfiguration: {

rrc-TransactionIdentifier 0,

criticalExtensions rrcReconfiguration: {

nonCriticalExtension {

masterCellGroup {

cellGroupId 0,

mac-CellGroupConfig {

phr-Config setup: {

phr-PeriodicTimer sf500,

phr-ProhibitTimer sf200,

phr-Tx-PowerFactorChange dB3,

multiplePHR TRUE,

dummy FALSE,

phr-Type2OtherCell FALSE,

phr-ModeOtherCG real

skipUplinkTxDynamic FALSE

spCellConfig {

spCellConfigDedicated {

initialDownlinkBWP {

pdsch-Config setup: {

resourceAllocation resourceAllocationType1,

rbg-Size config1,

mcs-Table qam256,

prb-BundlingType staticBundling: {

bundleSize wideband

}

uplinkConfig {

initialUplinkBWP {

pucch-Config setup: {

resourceToAddModList {

{

pucch-ResourceId 14,

startingPRB 105,

intraSlotFrequencyHopping enabled,

secondHopPRB 0,

format format2: {

nrofPRBs 1,

nrofSymbols 2,

startingSymbolIndex 12

}

dl-DataToUL-ACK {

}

pusch-Config setup: {

txConfig codebook,

resourceAllocation resourceAllocationType1,

mcs-Table qam256,

mcs-TableTransformPrecoder qam256,

codebookSubset nonCoherent,

maxRank 1,

pusch-TimeDomainAllocationListDCI-0-1-r16 setup: {

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeA,

startSymbolAndLength-r16 41,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeA,

startSymbolAndLength-r16 27,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 54,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeA,

startSymbolAndLength-r16 41,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 67,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeA,

startSymbolAndLength-r16 55,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 81,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 80,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeA,

startSymbolAndLength-r16 69,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 101,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 40,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 53,

numberOfRepetitions-r16 n1

}

{

k2-r16 4,

puschAllocationList-r16 {

{

mappingType-r16 typeB,

startSymbolAndLength-r16 66,

numberOfRepetitions-r16 n1

}

srs-Config setup: {

srs-ResourceSetToAddModList {

{

srs-ResourceSetId 0,

srs-ResourceIdList {

resourceType periodic: {

usage codebook,

p0 -90,

pathlossReferenceRS ssb-Index: 0

}

srs-ResourceToAddModList {

{

srs-ResourceId 0,

nrofSRS-Ports port1,

transmissionComb n4: {

combOffset-n4 0,

cyclicShift-n4 5

resourceMapping {

startPosition 0,

nrofSymbols n1,

repetitionFactor n1

freqDomainPosition 0,

freqDomainShift 9,

freqHopping {

c-SRS 22,

b-SRS 3,

b-hop 0

groupOrSequenceHopping neither,

resourceType periodic: {

periodicityAndOffset-p sl80: 0

sequenceId 500

}

uplinkTxSwitching-r16 setup: {

uplinkTxSwitchingPeriodLocation-r16 TRUE,

uplinkTxSwitchingCarrier-r16 carrier1 // Notifies that this is carrier 1

}

pdsch-ServingCellConfig setup: {

nrofHARQ-ProcessesForPDSCH n16,

maxMIMO-Layers 2

csi-MeasConfig setup: {

csi-ReportConfigToAddModList {

{

reportConfigId 1,

carrier 1,

resourcesForChannelMeasurement 0,

csi-IM-ResourcesForInterference 1,

reportConfigType periodic: {

reportSlotConfig slots80: 3,

pucch-CSI-ResourceList {

{

uplinkBandwidthPartId 0,

pucch-Resource 14

}

reportQuantity cri-RI-PMI-CQI: NULL,

reportFreqConfiguration {

cqi-FormatIndicator widebandCQI,

pmi-FormatIndicator widebandPMI

timeRestrictionForChannelMeasurements notConfigured,

timeRestrictionForInterferenceMeasurements notConfigured,

codebookConfig {

codebookType type1: {

subType typeI-SinglePanel: {

nrOfAntennaPorts two: {

twoTX-CodebookSubsetRestriction '111111'B

typeI-SinglePanel-ri-Restriction '03'H

codebookMode 1

}

groupBasedBeamReporting disabled: {

cqi-Table table2,

subbandSize value1

}

tag-Id 0

}

sCellToAddModList {

{

sCellIndex 1,

sCellConfigCommon {

physCellId 501,

downlinkConfigCommon {

frequencyInfoDL {

absoluteFrequencySSB 521790,

frequencyBandList {

absoluteFrequencyPointA 520164,

scs-SpecificCarrierList {

{

offsetToCarrier 0,

subcarrierSpacing kHz30,

carrierBandwidth 51

}

initialDownlinkBWP {

genericParameters {

locationAndBandwidth 13750,

subcarrierSpacing kHz30

pdcch-ConfigCommon setup: {

controlResourceSetZero 10,

searchSpaceZero 0,

commonSearchSpaceList {

{

searchSpaceId 1,

controlResourceSetId 0,

monitoringSlotPeriodicityAndOffset sl1: NULL,

monitoringSymbolsWithinSlot '10000000000000'B,

nrofCandidates {

aggregationLevel1 n0,

aggregationLevel2 n4,

aggregationLevel4 n2,

aggregationLevel8 n1,

aggregationLevel16 n0

searchSpaceType common: {

dci-Format0-0-AndFormat1-0 {

}

searchSpaceSIB1 0,

searchSpaceOtherSystemInformation 1,

pagingSearchSpace 1,

ra-SearchSpace 1

pdsch-ConfigCommon setup: {

pdsch-TimeDomainAllocationList {

{

mappingType typeA,

startSymbolAndLength 40

{

mappingType typeA,

startSymbolAndLength 57

}

uplinkConfigCommon {

frequencyInfoUL {

scs-SpecificCarrierList {

{

offsetToCarrier 0,

subcarrierSpacing kHz30,

carrierBandwidth 51

}

p-Max 10

initialUplinkBWP {

genericParameters {

locationAndBandwidth 13750,

subcarrierSpacing kHz30

pusch-ConfigCommon setup: {

pusch-TimeDomainAllocationList {

{

k2 5,

mappingType typeA,

startSymbolAndLength 27

{

k2 4,

mappingType typeA,

startSymbolAndLength 27

{

k2 2,

mappingType typeA,

startSymbolAndLength 27

}

p0-NominalWithGrant -90

}

dummy ms500

ssb-PositionsInBurst mediumBitmap: '80'H,

dmrs-TypeA-Position pos2,

ssbSubcarrierSpacing kHz30,

tdd-UL-DL-ConfigurationCommon {

referenceSubcarrierSpacing kHz30,

pattern1 {

dl-UL-TransmissionPeriodicity ms5,

nrofDownlinkSlots 5,

nrofDownlinkSymbols 6,

nrofUplinkSlots 4,

nrofUplinkSymbols 6

}

ss-PBCH-BlockPower -42

sCellConfigDedicated {

initialDownlinkBWP {

pdcch-Config setup: {

controlResourceSetToAddModList {

{

controlResourceSetId 2,

frequencyDomainResources '111111110000000000000000000000000000000000000'B,

duration 1,

cce-REG-MappingType nonInterleaved: NULL,

precoderGranularity sameAsREG-bundle

}

searchSpacesToAddModList {

{

searchSpaceId 2,

controlResourceSetId 2,

monitoringSlotPeriodicityAndOffset sl1: NULL,

monitoringSymbolsWithinSlot '10000000000000'B,

nrofCandidates {

aggregationLevel1 n8,

aggregationLevel2 n4,

aggregationLevel4 n2,

aggregationLevel8 n0,

aggregationLevel16 n0

searchSpaceType ue-Specific: {

dci-Formats formats0-1-And-1-1

}

pdsch-Config setup: {

dmrs-DownlinkForPDSCH-MappingTypeA setup: {

dmrs-AdditionalPosition pos1

tci-StatesToAddModList {

{

tci-StateId 0,

qcl-Type1 {

referenceSignal ssb: 0,

qcl-Type typeD

}

resourceAllocation resourceAllocationType1,

rbg-Size config1,

mcs-Table qam256,

prb-BundlingType staticBundling: {

bundleSize wideband

zp-CSI-RS-ResourceToAddModList {

{

zp-CSI-RS-ResourceId 0,

resourceMapping {

frequencyDomainAllocation row4: '001'B,

nrofPorts p4,

firstOFDMSymbolInTimeDomain 4,

cdm-Type fd-CDM2,

density one: NULL,

freqBand {

startingRB 0,

nrofRBs 52

}

periodicityAndOffset slots80: 1

}

p-ZP-CSI-RS-ResourceSet setup: {

zp-CSI-RS-ResourceSetId 0,

zp-CSI-RS-ResourceIdList {

}

firstActiveDownlinkBWP-Id 0,

uplinkConfig {

initialUplinkBWP {

pusch-Config setup: {

txConfig codebook,

dmrs-UplinkForPUSCH-MappingTypeA setup: {

dmrs-AdditionalPosition pos1,

transformPrecodingDisabled {

}

pusch-PowerControl {

msg3-Alpha alpha1,

p0-AlphaSets {

{

p0-PUSCH-AlphaSetId 0,

p0 0,

alpha alpha1

}

pathlossReferenceRSToAddModList {

{

pusch-PathlossReferenceRS-Id 0,

referenceSignal ssb-Index: 0

}

sri-PUSCH-MappingToAddModList {

{

sri-PUSCH-PowerControlId 0,

sri-PUSCH-PathlossReferenceRS-Id 0,

sri-P0-PUSCH-AlphaSetId 0,

sri-PUSCH-ClosedLoopIndex i0

}

resourceAllocation resourceAllocationType1,

mcs-Table qam256,

mcs-TableTransformPrecoder qam256,

codebookSubset nonCoherent,

maxRank 2,

uci-OnPUSCH setup: {

betaOffsets semiStatic: {

betaOffsetACK-Index1 9,

betaOffsetACK-Index2 9,

betaOffsetACK-Index3 9,

betaOffsetCSI-Part1-Index1 7,

betaOffsetCSI-Part1-Index2 7,

betaOffsetCSI-Part2-Index1 7,

betaOffsetCSI-Part2-Index2 7

scaling f1

}

srs-Config setup: {

srs-ResourceSetToAddModList {

{

srs-ResourceSetId 0,

srs-ResourceIdList {

resourceType periodic: {

usage codebook,

p0 -90,

pathlossReferenceRS ssb-Index: 0

}

srs-ResourceToAddModList {

{

srs-ResourceId 0,

nrofSRS-Ports ports2,

transmissionComb n4: {

combOffset-n4 0,

cyclicShift-n4 1

resourceMapping {

startPosition 1,

nrofSymbols n1,

repetitionFactor n1

freqDomainPosition 0,

freqDomainShift 5,

freqHopping {

c-SRS 11,

b-SRS 3,

b-hop 0

groupOrSequenceHopping neither,

resourceType periodic: {

periodicityAndOffset-p sl80: 5

sequenceId 501

}

firstActiveUplinkBWP-Id 0,

pusch-ServingCellConfig setup: {

uplinkTxSwitching-r16 setup: {

uplinkTxSwitchingPeriodLocation-r16 FALSE,

uplinkTxSwitchingCarrier-r16 carrier2 // Notifies that this is carrier 2

}

pdcch-ServingCellConfig setup: {

pdsch-ServingCellConfig setup: {

nrofHARQ-ProcessesForPDSCH n16,

maxMIMO-Layers 2

csi-MeasConfig setup: {

nzp-CSI-RS-ResourceToAddModList {

{

nzp-CSI-RS-ResourceId 0,

resourceMapping {

frequencyDomainAllocation other: '000001'B,

nrofPorts p2,

firstOFDMSymbolInTimeDomain 3,

cdm-Type fd-CDM2,

density one: NULL,

freqBand {

startingRB 0,

nrofRBs 52

}

powerControlOffset 0,

scramblingID 501,

periodicityAndOffset slots80: 1,

qcl-InfoPeriodicCSI-RS 0

}

nzp-CSI-RS-ResourceSetToAddModList {

{

nzp-CSI-ResourceSetId 0,

nzp-CSI-RS-Resources {

}

csi-IM-ResourceToAddModList {

{

csi-IM-ResourceId 0,

csi-IM-ResourceElementPattern pattern1: {

subcarrierLocation-p1 s0,

symbolLocation-p1 4

freqBand {

startingRB 0,

nrofRBs 52

periodicityAndOffset slots80: 1

}

csi-IM-ResourceSetToAddModList {

{

csi-IM-ResourceSetId 0,

csi-IM-Resources {

}

csi-ResourceConfigToAddModList {

{

csi-ResourceConfigId 0,

csi-RS-ResourceSetList nzp-CSI-RS-SSB: {

nzp-CSI-RS-ResourceSetList {

}

bwp-Id 0,

resourceType periodic

{

csi-ResourceConfigId 1,

csi-RS-ResourceSetList csi-IM-ResourceSetList: {

bwp-Id 0,

resourceType periodic

}

tag-Id 0

}

uplinkTxSwitchingOption-r16 switchedUL

dedicatedNAS-MessageList {

'7E0244126635017E0042010977000B....'H

nonCriticalExtension {

needForGapsConfigNR-r16 setup: {

}

Reference

2023 Switched Uplink in 5G-NR: Benefit & Deployment Consideration - Qualcomm
5G Uplink Enhancement Technology - White Paper (ZTE)
5G Uplink Enhancement Techniques - Whitepaper (Mediatek)
T-Mobile Achieves Record-Breaking Uplink Speeds on its 5G Standalone Network Using UL Tx Switching - everythingRF (Feb 2024)

YouTube

5G Uplink-Tx-Switching feature explained (Uplink Carrier Aggregation) - Henrik (May 2024)