Scheduling enhancements for low band carrier aggregation with receiver switching

A semi-static switching pattern with enhanced cross-carrier scheduling and shared HARQ process identifiers addresses the challenges of FDD-SDL carrier transitions in low band carrier aggregation, improving reliability and efficiency in NR networks.

WO2026236513A1PCT designated stage Publication Date: 2026-11-12APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/US2026/027130
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Conventional NR scheduling and processing timelines do not accommodate for the switching gap needed when transitioning between FDD and SDL carriers in low band carrier aggregation, leading to scheduling conflicts, suboptimal resource utilization, and increased complexity due to unresolved issues with scheduling gaps, cross-carrier grants, and HARQ timelines.

Method used

Implement a semi-static switching pattern with defined UE processing timeline gaps and enhanced cross-carrier scheduling capabilities, allowing SDL to be self-scheduled or cross-carrier scheduled by FDD, and sharing HARQ process identifiers between carriers to streamline retransmissions and reduce latency.

Benefits of technology

This approach reduces scheduling conflicts, improves reliability, enhances spectral efficiency, and optimizes resource allocation by ensuring adequate switching times and flexible scheduling, thereby simplifying UE antenna design and maximizing peak antenna gain in low band carrier aggregation scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure US2026027130_12112026_PF_FP_ABST
    Figure US2026027130_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure generally relates to scheduling enhancements for low band (LB) carrier aggregation (CA) with receiver (Rx) switching. In some implementations, a user equipment (UE) receives control signaling that configures a switching pattern. The UE can determine a first time duration associated with communication on a frequency division duplexing (FDD) carrier and a second time duration asociated with reception on a supplementary downlink (SDL) carrier based on the switching pattern. The UE may determine whether to transmit or receive a signal in the first time duration or the second time duration based on the switching pattern and a carrier on which the signal is scheduled, where the carrier is either the FDD carrier or the SDL carrier.
Need to check novelty before this filing date? Find Prior Art

Description

Attorney Docket No. 56990-0096W01 / P71805WO1SCHEDULING ENHANCEMENTS FOR LOW BAND CARRIER AGGREGATION WITH RECEIVER SWITCHING CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 803,439, filed May 9, 2025, the entire contents of which are incorporated herein by reference.TECHNICAL FIELD

[0002] The present disclosure relates generally to wireless communication, and more specifically to scheduling enhancements for low band (LB) carrier aggregation (CA) with receiver (Rx) switching.BACKGROUND

[0003] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephony, data (e.g., voice, audio, video), messaging, and / or other services. The wireless communication networks have wireless access nodes that exchange wireless signals with the wireless user devices using one or more wireless network protocols, such as protocols described in various telecommunication standards promulgated by the European Telecommunications Standards Institute (ETSI) Third Generation Partnership Project (3GPP). The wireless communication networks facilitate mobile broadband service using technologies such as orthogonal frequency -division multiple access (OFDMA), multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features.Attorney Docket No. 56990-0096W01 / P71805WO1SUMMARY

[0004] One aspect of the present disclosure relates to a method including: receiving control signaling that configures a switching pattern for a user equipment (UE), determining a first time duration associated with communication on a frequency division duplexing (FDD) carrier and a second time duration associated with reception on a supplementary downlink (SDL) carrier based at least on the switching pattern, and determining whether to transmit or receive a signal in the first time duration or the second time duration based at least on the switching pattern and a carrier on which the signal is scheduled. The carrier is either the FDD carrier or the SDL carrier.

[0005] In some implementations, the FDD carrier (i) includes a downlink frequency band and a paired uplink frequency band and (ii) is used for both uplink and downlink on a primary cell (PCell).

[0006] In some implementations, the SDL carrier (i) includes an unpaired downlink frequency band and (ii) is used for downlink on a secondary cell (SCell).

[0007] In some implementations, the control signaling comprises radio resource control (RRC) signaling and the switching pattern comprises a semi-static switching pattern.

[0008] In some implementations, the UE is not expected to receive the signal via the SDL carrier in the first time duration. In some implementations, the signal comprises a channel state information reference signal (CSLRS), a synchronization signal block (SSB), a tracking reference signal (TRS), a physical downlink control channel (PDCCH), an active semi-persistent scheduled physical downlink shared channel (SPS-PDSCH), a dynamic grant physical downlink shared channel (DG-PDSCH) with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0009] In some implementations, the UE is not expected to receive the signal via the FDD carrier in the second time duration. In some implementations, the signal comprises a CSLRS, an SSB, a TRS, a PDCCH, an SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0010] In some implementations, SPS-PDSCH is activated for PDSCH reception via an FDD carrier in the first time duration. The UE is not expected to receive SPS-PDSCH via an SDL carrier during occasions that partially overlap with the second time duration.

[0011] In some implementations, SPS-PDSCH is activated for PDSCH reception via an SDL carrier in the second time duration. The UE is not expected to receive SPS-PDSCH via an FDD carrier during occasions that overlap with the first time duration.

[0012] In some implementations, the UE is not expected to transmit the signal via an FDD carrier in the second time duration. In some implementations, the signal comprises a physical random access channel (PRACH), a physical uplink control channel (PUCCH) unassociated with downlink control information (DCI), a PUCCH with repetitions scheduled in the first time duration and the second time duration, an active configured grant physical uplink shared channel (CG-PUSCH), a dynamic grant physical uplink shared channel (DG-PUSCH) with repetitions scheduled in the first time duration and the second time duration, a multi -grant PUSCH with at least one PUSCH scheduled in the first time duration and the second time duration, or a sounding reference signal (SRS).

[0013] In some implementations, the first duration is associated with a first antenna configuration, and wherein the second duration is associated with a second configuration. In some implementations, the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the first antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the second time duration. In some implementations, the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the second antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the first time duration.

[0014] In some implementations, a random access channel occasion (RO) associated with the FDD carrier and scheduled in the second time duration is considered invalid.

[0015] In some implementations, determining whether to transmit or receive the signal comprises dropping one or more PUCCH repetitions associated with the FDD carrier and scheduled in the second time duration, wherein the dropped PUCCH repetitions are not counted toward a number of repetition slots.

[0016] In some implementations, available PUCCH repetition slots start from a first available uplink slot in the first time duration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0017] Another aspect of the present disclosure relates to a UE including memory and one or more processors coupled to the memory and configured to, when executing instructions stored in the memory, cause the UE to perform any of the foregoing operations.

[0018] Another aspect of the present disclosure relates to a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform any of the foregoing operations.

[0019] Another aspect of the present disclosure relates to a method including: receiving control signaling that configures an antenna switching pattern for a user equipment (UE); determining a first time duration associated with a first antenna configuration and a second time duration associated with a second antenna configuration based on the antenna switching pattern; and determining whether to transmit or receive a signal in the first time duration or the second time duration based on the antenna switching pattern and a carrier on which the signal is scheduled.

[0020] In some implementations, the first antenna configuration enables transmission and reception on a frequency division duplexing (FDD) carrier.

[0021] In some implementations, the second antenna configuration enables reception on a supplemental downlink (SDL) carrier.

[0022] In some implementations, the control signaling includes radio resource control (RRC) signaling and the antenna switching pattern includes a semi-static antenna switching pattern.

[0023] In some implementations, the UE is not expected to receive the signal via an SDL carrier in the first time duration associated with the first antenna configuration.

[0024] In some implementations, the signal includes a channel state information reference signal (CSI-RS), a synchronization signal block (SSB), a tracking reference signal (TRS), a physical downlink control channel (PDCCH), an active semi -persistent scheduled physical downlink shared channel (SPS-PDSCH), a dynamic grant physical downlink shared channel (DG-PDSCH) with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0025] In some implementations, the UE is not expected to receive the signal via an FDD carrier in the second time duration associated with the second antenna configuration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0026] In some implementations, the signal includes a CSI-RS, an SSB, a TRS, a PDCCH, an SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0027] In some implementations, SPS-PDSCH is activated for PDSCH reception via an FDD carrier in the first time duration associated with the first antenna configuration, and the UE is not expected to receive SPS-PDSCH via an SDL carrier during occasions that partially overlap with the second time duration associated with the second antenna configuration.

[0028] In some implementations, SPS-PDSCH is activated for PDSCH reception via an SDL carrier in the second time duration associated with the second antenna configuration, and the UE is not expected to receive SPS-PDSCH via an FDD carrier during occasions that overlap with the first time duration associated with the first antenna configuration.

[0029] In some implementations, the UE is not expected to transmit the signal via an FDD carrier in the second time duration associated with the second antenna configuration.

[0030] In some implementations, the signal includes a physical random access channel (PRACH), a physical uplink control channel (PUCCH) unassociated with downlink control information (DCI), a PUCCH with repetitions scheduled in the first time duration and the second time duration, an active configured grant physical uplink shared channel (CG-PUSCH), a dynamic grant physical uplink shared channel (DG-PUSCH) with repetitions scheduled in the first time duration and the second time duration, a multi-grant PUSCH with at least one PUSCH scheduled in the first time duration and the second time duration, or a sounding reference signal (SRS).

[0031] In some implementations, the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the first antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the second time duration associated with the second antenna configuration.

[0032] In some implementations, the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the second antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the first time duration associated with the first antenna configuration.

[0033] In some implementations, a random access channel occasion (RO) associated with an FDD carrier and scheduled in the second time duration is considered invalid.Attorney Docket No. 56990-0096W01 / P71805WO1

[0034] In some implementations, determining whether to transmit or receive the signal includes dropping one or more PUCCH repetitions associated with an FDD carrier and scheduled in the second time duration, where the dropped PUCCH repetitions are not counted toward a number of repetition slots.

[0035] In some implementations, available PUCCH repetition slots start from a first available uplink slot in the first time duration associated with the first antenna configuration.

[0036] In some implementations, the method further includes: receiving an indication of a cross-carrier scheduling information element (IE) including scheduling cell information for an SDL carrier; and determining whether the SDL carrier can be cross-carrier scheduled by an FDD carrier based on the scheduling cell information.

[0037] In some implementations, determining whether the SDL carrier can be cross-carrier scheduled includes determining that the SDL carrier can be self-scheduled based on the scheduling cell information provided by the cross-carrier scheduling IE.

[0038] In some implementations, determining whether the SDL carrier can be cross-carrier scheduled includes determining that the SDL carrier can be self-scheduled or cross-carrier scheduled by the FDD carrier based on the scheduling cell information provided by the crosscarrier scheduling IE.

[0039] In some implementations, the method further includes transmitting capability information that indicates whether the UE supports cross-carrier scheduling, where determining whether the SDL carrier can be cross-carrier scheduled by the FDD carrier is based on the capability information.

[0040] In some implementations, the method further includes: transmitting a transport block (TB) via an FDD carrier in the second time duration, and receiving a PDSCH retransmission including hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback for the TB via an SDL carrier during the first time duration.

[0041] In some implementations, HARQ process identifiers (IDs) are shared between the FDD carrier and the SDL carrier.

[0042] In some implementations, the method further includes: receiving DCI via an FDD carrier during the first time duration, where the DCI schedules a DG-PDSCH or activates SPS-PDSCH on an SDL carrier.Attorney Docket No. 56990-0096W01 / P71805WO1

[0043] In some implementations, a time duration between the DCI and the DG-PDSCH or the SPS-PDSCH is greater than TLB -switch-

[0044] In some implementations, TLB-switch includes a threshold time duration for switching between the first antenna configuration and the second antenna configuration.

[0045] In some implementations, the method further includes: receiving a PDSCH via an SDL carrier during the second time duration associated with the second antenna configuration; and transmitting a PUCCH with HARQ-ACK feedback for the PDSCH via an FDD carrier during the first time duration.

[0046] In some implementations, a time duration between the PDSCH and the PUCCH is greater than Tproc, l+T[,B-switdi.

[0047] In some implementations, TprOc,i represents a current PDSCH processing timeline of the UE and TLB-switch includes a threshold time duration for switching between the first antenna configuration and the second antenna configuration.

[0048] In some implementations, the method further includes: receiving downlink control information (DCI) via an SDL carrier during the second time duration, where the DCI schedules a DG-PUSCH or activates a CG-PUSCH on an FDD carrier in the first time duration.

[0049] In some implementations, a time duration between the DCI and the DG-PUSCH or the CG-PUSCH is greater than Tproc, 2+T[,B-switcli.

[0050] In some implementations, TprOc,2 represents a current PUSCH preparation timeline of the UE and TLB-switch includes a threshold time duration for switching between the first antenna configuration and the second antenna configuration.

[0051] In some implementations, a PRACH occasion on an FDD carrier that starts less than Ngapsymbols after a last symbol of a switch between the first antenna configuration and the second antenna configuration is considered invalid.

[0052] In some implementations, the method further includes: receiving a PDCCH order via an SDL carrier in the second time duration, where the PDCCH order initiates a random access procedure on an FDD carrier in the first time duration; and transmitting a random access message via the FDD carrier during a PRACH occasion within the first time duration, where a time duration between the PDCCH order and the PRACH occasion is greater than a threshold.Attorney Docket No. 56990-0096W01 / P71805WO1

[0053] In some implementations, the method further includes: receiving DCI via an SDL carrier during the second time duration, where the DCI triggers a CSI report on a PUSCH associated with an FDD carrier; and receiving one or more aperiodic (AP) CSI-RS via the SDL carrier in accordance with the DCI.

[0054] In some implementations, the method further includes dropping a DG-PUSCH with the CSI report in response to determining that (i) a first time interval between the AP CSI-RS and the DG-PUSCH is less than or equal to a first threshold or (ii) a second time interval between the DCI and the DG-PUSCH is less than or equal to a second threshold.

[0055] In some implementations, the method further includes: receiving DCI via an SDL carrier during the second time duration, where the DCI triggers an aperiodic SRS (AP-SRS) on an FDD carrier in the first time duration; and determining a threshold time gap between the DCI and an SRS resource based on a codebook usage type associated with the SRS resource.

[0056] In some implementations, the method further includes transmitting the AP-SRS on the SRS resource via the FDD carrier in response to determining that a time duration between the DCI and the SRS resource exceeds the threshold time gap.

[0057] Another aspect of the present disclosure relates to one or more processors configured to, when executing instructions stored in a memory, perform any of the foregoing operations.

[0058] Another aspect of the present disclosure relates to a UE configured to perform any of the foregoing operations.

[0059] Another aspect of the present disclosure relates to a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform any of the foregoing operations.

[0060] The details of one or more embodiments of these systems and methods are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims.Attorney Docket No. 56990-0096W01 / P71805WO1 BRIEF DESCRIPTION OF THE FIGURES

[0061] FIG. 1 illustrates an example wireless network, according to some implementations.

[0062] FIG. 2 illustrates an example antenna switching pattern, according to some implementations.

[0063] FIG. 3 illustrates an example frequency band configuration, according to some implementations.

[0064] FIG. 4 illustrates an example of a dynamic grant (DG) physical downlink shared channel (PDSCH) repetition scheme, according to some implementations.

[0065] FIG. 5 illustrates an example of a physical uplink control channel (PUCCH) repetition scheme, according to some implementations.

[0066] FIG. 6 illustrates an example feedback transmission scheme, according to some implementations.

[0067] FIGs. 7-12 illustrate example user equipment (UE) processing timelines, according to some implementations.

[0068] FIG. 13 illustrates a flowchart of an example method for low band (LB) carrier aggregation (CA) with receiver (Rx) switching, according to some implementations.

[0069] FIG. 14 illustrates an example UE, according to some implementations.

[0070] FIG. 15 illustrates an example access node, according to some implementations.Attorney Docket No. 56990-0096W01 / P71805WO1DETAILED DESCRIPTION

[0071] In current New Radio (NR) deployments, low band (LB) carrier aggregation (CA) is used to extend coverage and boost capacity by combining a primary frequency division duplexing (FDD) carrier or primary cell (PCell) with a supplementary downlink (SDL) carrier or secondary cell (SCell). LB frequencies tend to offer broader coverage but narrower bandwidth. In some cases, receiver (Rx) switching techniques can be used to avoid the complexity of tuning an antenna to both LB carriers at once. In such cases, a user equipment (UE) alternates between receiving on FDD only (Case 1) and on SDL only (Case 2), often using a semi-static pattern configured via radio resource control (RRC) signaling. Existing rules can help resolve conflicts that arise when uplink and downlink transmissions overlap on a single unpaired carrier, but they do not fully address the unique challenges of LB-LB CA with Rx switching, especially with respect to scheduling gaps, cross-carrier grants, retransmissions, and processing timelines.

[0072] Conventional NR scheduling and processing timelines do not accommodate for the switching gap that is needed to switch from Case 1 to Case 2 (or vice versa). A UE that is switching from one state to another may be unable to receive / decode an FDD-scheduled physical downlink shared channel (PDSCH) on SDL that arrives within the antenna switching period. Further, legacy crossCarrierScheduling parameters limit an SDL SCell to selfscheduling or to being scheduled by FDD, but not both. Additionally, retransmissions of failed transport blocks (TBs) are typically confined to the cell on which they were first received, and existing HARQ timelines do not account for Rx switching delays. These issues can lead to scheduling conflicts, error cases (when grants overlap with a switching gap), suboptimal resource utilization, and added complexity in resolving timing errors.

[0073] Some aspects of the present disclosure relate to a semi-static switching pattern in which a UE alternates between two Rx antenna states according to an RRC configuration. In the switching gap period, the UE may not expect to receive (or, in some examples, to transmit) certain channels on the non-active carrier. For example, the UE may not be expected to receive channel state information reference signals (CSI-RS), synchronization signal blocks (SSB), tracking reference signals (TRS), physical downlink control channels (PDCCH), semi-persistent scheduled (SPS) PDSCH occasions, dynamic-grant (DG) PDSCH repetitions, or multi-grant PDSCH transmissions. Reception of any such channel within the switching gap period may be treated as an error case.Attorney Docket No. 56990-0096W01 / P71805WO1

[0074] To address UE processing timeline gaps, a new LB switching period (TLB-switch) can be added to existing PDSCH and physical uplink shared channel (PUSCH) processing times Tproqland Tproc 2so the gap between the end of the DCI on one carrier and the start of data on the other carrier does not fall within the Rx switching period. The schedulingCelllnfo field of the crossCarrierScheduling information element (IE) for SDL can be interpreted so that SDL may self-schedule (when the field is set to “own”) or be cross-carrier scheduled by FDD (when the field set to “other”). If the UE indicates a crossCarrierScheduling capability, SDL can be scheduled by PDCCH on either FDD or SDL. The present disclosure also provides for hybrid automatic repeat request (HARQ) process identifiers (ID) to be shared between FDD and SDL, enabling retransmission of a TB initially received on one carrier to be scheduled on the other.

[0075] As an example, a UE may be configured with a switching duration of four slots for Case 1 and a switching duration of three slots for Case 2, with a TLB-switch equal to two symbols. If a downlink DCI on FDD arrives at the end of slot 4 and schedules a dynamic-grant PDSCH on SDL, the PDSCH start time on SDL may be deferred so there is a two-symbol gap after slot 4, ensuring the antenna of the UE has completed the Rx switch. Likewise, if a physical uplink control channel (PUCCH) carrying hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback for a PDSCH on SDL is to be transmitted on FDD, the UE may calculate the PUCCH start occasion based on TLB-switch and Tproc land drop any PUCCH repetition that would fall within the next switching gap period. If the UE receives a DG-PUSCH for FDD with at least one repetition during the switching period, it may be flagged as an error. If crossCarrierScheduling is set to “other” for SDL, the UE can monitor PDCCH on both SDL and FDD, which provides greater scheduling flexibility.

[0076] By defining clear error cases and restrictions on reception / transmission during the switching interval, the UE can avoid overlapping grants and reduce scheduling conflicts. Incorporating a new Rx-switching period into existing PDSCH and PUSCH processing timelines can prevent missed grants due to insufficient switching time, thereby improving reliability and reducing the number of failed communications. Allowing SDL to be both selfscheduled and cross-carrier scheduled by FDD (subject to UE capability) can enhance spectral efficiency and improve the flexibility of resource allocation schemes. Sharing HARQ process IDs between carriers can streamline retransmissions and decrease latency by enabling crosscarrier retransmissions. The enhancements described herein can simplify UE antenna design,Attorney Docket No. 56990-0096W01 / P71805WO1maximize peak antenna gain for each carrier, and more effectively utilize LB resources in CA scenarios.

[0077] FIG. 1 illustrates an example wireless network 100, according to some implementations. The wireless network 100 includes a UE 102 and a base station 104, which are connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and base station 104 communicate using a system that supports controls for managing the access of the UE 102 to a network via the base station 104.

[0078] In some implementations, the wireless network 100 is a standalone (SA) network, e.g., that incorporates Fifth Generation (5G) New Radio (NR). In some other implementations, the wireless network 100 is a non- standalone (NS A) network that incorporates Long Term Evolution (LTE) and 5G NR. In these implementations, the wireless network 100 may be an Evolved Universal Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (EN-DC) network, or an NR-EUTRA Dual Connectivity (NE-DC) network. Furthermore, wireless networks implementing one or more other types of communication standards are possible, including future 3GPP systems (e.g., Sixth Generation “6G”), Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology, or the like. While aspects may be described herein using terminology commonly associated with 5GNR, aspects of the present disclosure can be applied to other systems, such as systems subsequent to 5G (e.g., 6G).

[0079] In the wireless network 100, the UE 102 and any other UE in the system may be, for example, any of a laptop computer, smartphone, tablet computer, machine-type device (such as smart meters or specialized devices for healthcare), intelligent transportation system, or any other wireless device. In network 100, the base station 104 provides the UE 102 network connectivity to a broader network (not shown). This UE 102 connectivity is provided via the air interface 108 in a base station service area provided by the base station 104. In some implementations, such a broader network may be a wide area network operated by a cellular network provider, or may be the Internet. Each base station service area associated with the base station 104 is supported by one or more antennas integrated with the base station 104. The service areas can be divided into a number of sectors associated with one or more particular antennas. Such sectors may be physically associated with one or more fixed antennas or may be assigned to a physical area with one or more tunable antennas or antenna settings adjustable in a beamforming process used to direct a signal to a particular sector.Attorney Docket No. 56990-0096W01 / P71805WO1

[0080] The UE 102 includes control circuitry 110 coupled with transmit circuitry 112 and receive circuitry 114. The transmit circuitry 112 and receive circuitry 114 may each be coupled with one or more antennas. The control circuitry 110 may include application-specific circuitry, baseband circuitry, or any of various combinations thereof. The transmit circuitry 112 and receive circuitry 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry and / or front-end module (FEM) circuitry.

[0081] In various implementations, aspects of the transmit circuitry 112, receive circuitry 114, and / or control circuitry 110 may be integrated in various ways to implement the operations described herein. The control circuitry 110 may be adapted or configured to perform various operations, such as those described elsewhere in this disclosure related to a UE. For example, the control circuitry 110 can determine whether to treat an upcoming DG-PUSCH transmission as an error case based on a time duration between the DG-PUSCH and a preceding uplink DCI transmission.

[0082] The transmit circuitry 112 can perform various operations described herein. For example, the transmit circuitry 112 can transmit a PUCCH if the time interval between the PUCCH and a preceding PDSCH is greater than Tproc l+ TLB-switch. Additionally, the transmit circuitry 112 may transmit using multiplexed uplink physical channels. The uplink physical channels can be multiplexed, e.g., according to time division multiplexing (TDM) or frequency division multiplexing (FDM), and in some implementations, along with carrier aggregation. The transmit circuitry 112 may be configured to receive block data from the control circuitry 110 for transmission on the air interface 108.

[0083] The receive circuitry 114 can perform various operations described herein. For example, the receive circuitry 114 can receive a DG-PDSCH if the time between the DG-PDSCH and a preceding downlink DCI is greater than TLB-switch. Additionally, the receive circuitry 114 may receive multiplexed downlink physical channels from the air interface 108 and relay the physical channels to the control circuitry 110. The downlink physical channels can be multiplexed, e.g., according to TDM or FDM, e.g., along with carrier aggregation. The transmit circuitry 112 and the receive circuitry 114 may transmit and receive, respectively, both control data and content data (e.g., messages, images, video) structured within data blocks that are carried by the physical channels.

[0084] FIG. 1 also illustrates the base station 104. In some implementations, the base station 104 may be a 5G radio access network (RAN), a next generation RAN, a E-UTRAN, a nonAttorney Docket No. 56990-0096W01 / P71805WO1terrestrial cell, or a legacy RAN, such as a UTRAN. As used herein, the term “5G RAN” or the like may refer to the base station 104 that operates in an NR wireless network 100, and the term “E-UTRAN” or the like may refer to a base station 104 that operates in an LTE wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each of which includes a physical communications interface or layer.

[0085] The base station 104 circuitry may include control circuitry 116 coupled (directly or indirectly) with transmit circuitry 118 and / or receive circuitry 120. The transmit circuitry 118 and receive circuitry 120 may each be coupled (directly or indirectly) with one or more antennas that may be used to enable communications via the air interface 108. The transmit circuitry 118 and receive circuitry 120 may be adapted to transmit and receive data, respectively, addressed to any UE connected to the base station 104. The receive circuitry 120 may receive uplink physical channel transmissions from one or more UEs, including the UE 102.

[0086] In FIG. 1, the one or more channels 106A, 106B are illustrated as an air interface to enable communicative coupling, and may be consistent with cellular communications protocols, such as an LTE protocol, Advanced LTE (LTE-A) protocol, LTE-based access to unlicensed spectrum (LTE-U), NR protocol, NR-based access to unlicensed spectrum (NR-U) protocol, and / or any other communications protocol(s). In some implementations, the UE 102 may directly exchange communication data via a ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink discovery channel (PSDCH), or a physical sidelink broadcast channel (PSBCH).

[0087] The present disclosure generally relates to scheduling enhancements for LB-LB CA with Rx switching. LB typically provides higher coverage and smaller bandwidth. SDL may be configured to use higher traffic for downlink. In LB, however, SDL may be in the vicinity of other bands (typically FDD). This is shown in FIG. 3, for example. Rx switching can simplify the UE antenna design and more effectively utilize peak antenna gain, which can be tuned to at most one downlink band. UE parameters, including at least a switching gap (if needed), and corresponding physical layer procedures may be defined to allow switching between Tx / Rx on FDD carrier 1 and no Rx on SDL carrier 2 (Case 1) and Rx on SDL carrier 2 and no Tx / Rx on FDD carrier 1 (Case 2). A semi-static switching pattern may be definedAttorney Docket No. 56990-0096W01 / P71805WO1based on an RRC configuration of the UE 102. An example antenna switching pattern is shown in FIG. 2.

[0088] For a single carrier in an unpaired band, when there is an overlap between uplink and downlink channels, resolution rules are defined in 3GPP TS 38.213, Section 11.1. In general, an uplink grant associated with DCI overrides a configured downlink grant (and vice versa). Overlap between dynamic uplink and downlink grants is an error case. Overlap of configured uplink and downlink grants is handled by the UE 102. Additional rules are defined for TDD.

[0089] Some aspects of the present disclosure relate to a semi-static switching pattern for switching between Case 1 and Case 2 (depicted in FIG. 2). In this semi-static switching pattern, the UE 102 is not expected to receive specific channels via SDL or FDD (even partially) within a time duration or switching gap associated with Case 1 (referred to hereinafter as the Case 1 duration) or Case 2 (referred to hereinafter as the Case 2 duration). For example, the UE 102 may not expect to receive the following channel s / signals associated with SDL (for Case 1) or FDD (for Case 2): CSLRS, SSB, TRS, PDCCH, an occasion of an active SPS-PDSCH, a repetition occasion of a DG-PDSCH with repetitions where at least one of the repetitions is scheduled within the Case 2 duration or the Case 1 duration, or a multi-grant PDSCH where at least one of the PDSCH transmissions is scheduled within the Case 2 duration or the Case 1 duration. If a repetition occasion of a DG-PDSCH or a multi -grant PDSCH is received within this timeframe, it is considered an error case (as shown in FIG. 4).

[0090] In some implementations, the UE 102 is not expected to transmit specific channels (even partially) within the Case 2 duration. For example, the UE 102 may not expect to transmit the following channel s / signals associated with FDD: physical random access channel (PRACH), PUCCH without repetitions when PUCCH is not associated with DCI (such as PUCCH for SPS HARQ or periodic CSI), PUCCH with repetitions when at least one of the repetition occasions is within the Case 1 duration, an occasion of active configured grant (CG) PUSCH, DG-PUSCH with repetitions where at least one of the repetitions is within the Case 1 duration, a multi-grant PUSCH where at least one of the PUSCHs is scheduled within the Case 1 duration, or sounding reference signal (SRS) symbols within the Case 2 duration.

[0091] If a legacy SSB to RACH occasion (RO) mapping is used, ROs within the Case 2 duration are considered invalid. For PUCCH with repetitions, the repetition occasions within the Case 1 duration are dropped and do not count toward the Np^p(e(^ number of repetition slots. FIG. 5 shows an example where NpjPceca^ = 2 and available PUCCH repetition slots startAttorney Docket No. 56990-0096W01 / P71805WO1from the first usable uplink slot in the Case 1 duration. If a DG-PUSCH or a multi-grant PUSCH is received and at least one of the PUSCH repetitions is within the Case 1 duration, it is considered an error case.

[0092] In existing NR schemes, the parameter crossCarrierScheduling configured for a serving cell indicates whether this serving cell is cross-carrier scheduled by another serving cell or whether it cross-carrier schedules another serving cell. An SCell can be self-scheduled or cross-carrier scheduled by another serving cell. In addition to being scheduled by PDCCH on the special cell (SpCell), the SpCell can be cross-carrier scheduled by another serving cell. For LB-LB CA with Rx switching, FDD is used for the PCell and SDL is used for the SCell. Thus, FDD can schedule SDL and / or be scheduled by SDL. However, SDL can only selfschedule or be scheduled by FDD (not both).

[0093] With the framework described herein, SDL can be cross-carrier scheduled by FDD and self-scheduled (subject to UE capability). To support this functionality, the schedulingCelllnfo field in crossCarrierScheduling for SDL may be interpreted as follows. If ‘own’ is configured, SDL cannot be scheduled by FDD. In this case, SDL is self-scheduling and can schedule FDD if schedulingCelllnfo in crossCarrierScheduling for FDD is set to ‘other’. Alternatively, if ‘other’ is configured, SDL can also be cross-carrier scheduled by FDD in addition to being scheduled by the PDCCH on SDL. If the UE 102 indicates a capability for crossCarrierScheduling, schedulingCelllnfo in crossCarrierScheduling for SDL can be ignored and SDL can be scheduled by PDCCH on SDL and / or PDCCH on FDD.

[0094] In existing NR schemes, retransmission of a failed TB on a serving cell is not expected to be scheduled on another serving cell. For LB-LB CA with RX switching, retransmission of a TB originally received on SDL within the semi-statically configured Case 2 duration is deferred until the next switching period provided for switching to Case 2. A similar constraint applies to TBs originally received on FDD within the semi-statically configured Case 1 duration.

[0095] With the framework described herein, PDSCH retransmission of a TB initially received on FDD can be scheduled on SDL (or vice versa), subject to UE capability. To support this functionality, HARQ process IDs can be shared between SDL and FDD. This is allowed because simultaneous reception of FDD and SDL is not expected. An example of this is shown in FIG. 6.Attorney Docket No. 56990-0096W01 / P71805WO1

[0096] As described herein, the UE 102 may switch between Case 1 and Case 2 according to a semi-static pattern. For example, the UE 102 may be configured with a Case 1 duration and a Case 2 duration, meaning the UE 102 knows when to semi-statically switch from / to Case 1 (or Case 2). After the UE 102 switches, the first grant in the new state can be a grant associated with DCI. However, current processing timelines do not incorporate switching gaps into different UE processing timelines.

[0097] In some implementations, if a downlink DCI on FDD schedules a DG-PDSCH (or activates SPS-PDSCH) on SDL, the time gap between the end of the DCI and the start of the PDSCH cannot be less than an LB switching period (TLB-switch), which represents a switching time between Case 1 and Case 2. A similar approach can be applied to the scheduling gap between the end of the downlink DCI on SDL and the start of the PDSCH scheduled on FDD. This is shown in FIG. 7, for example.

[0098] If a PUCCH carries HARQ-ACK for a PDSCH received on SDL, the time gap between the end of the PDSCH and the start of the PUCCH cannot be less than Tproc l+ TLB-switch after applying the timing advance (TA), where Tproc lis the current UE PDSCH processing timeline defined in 3GPP TS 38.214, Section 5.3:Tproc.i = (^i + + d2+ d3)(2048 + 144). k2~^Tc+ Text+ TLB-switch

[0099] This differs from uplinkTxSwitch, where the gap is defined between the end of the DCI and the start of the PUCCH. An example UE processing timeline is shown in FIG. 8.

[0100] If an uplink DCI on SDL schedules a DG-PUSCH (or activates CG-PUSCH) on FDD, the time gap between the end of the DCI and the start of the PUSCH cannot be less than TprOc,2 + TLB-switch after applying the TA, where TprOc,2 is the current UE PUSCH preparation timeline defined in 3GPP TS 38.214, Section 6.4. Alternatively, TLB-switch may be incorporated into TProc,2 as follows:Tproc,2 = max( N2+ d21+ d2)(2048 + 144). k2~fiTc+ Text+ Tswitch+ TLB-switch,d2 2)

[0101] This is shown in FIG. 9, for example.

[0102] A PRACH occasion in a PRACH slot on FDD may be considered invalid if it starts less than Ngapsymbols after a last symbol following an Rx switch. Ngapis defined in Table 8.1-2 of 3GPP TS 38.213, Section 8.1. Currently, Ngapis only applicable to TDD based on downlink symbols and PRACH occasion. If a RACH procedure on FDD is initiated by a PDCCH orderAttorney Docket No. 56990-0096W01 / P71805WO1received on SDL, the UE 102 may transmit a PRACH in the selected PRACH occasion for which a time between the last symbol of the PDCCH order reception and the first symbol of the PRACH transmission is not less than:NT, 2 d” ^BWPSwitching d” Delay d” ^switch d” ^SSB d” ^RF / B Bprepration d” LB-switch

[0103] This is shown in FIG. 10, for example. In this case, an uplink or secondary uplink (SUL) indicator may be a reserved bit in DCI 1 0. The remaining bit-fields can be interpreted according to legacy procedures. The parameters in the foregoing equation are defined in 3GPP TS 38.213, Section 8.1.

[0104] When the CSI request field of a DCI received on SDL triggers a CSI report(s) for PUSCH on FDD, TLB-switch may be added to TprOc,csi and T’proc,csi, as follows:Tproc,CSI (Z)(2048 + 144). k2 Tc+ Tswitch+ TLB-switchTproc.csi=(Z')(2048 + 144). k2 ^. Tc+ TLB-switch

[0105] where Z and Z’ are defined in 3GPP TS 38.214, Section 5.4. Alternatively, TLB-switch can be rounded up to the symbols and added to Z and Z’. This approach is different from uphnkTxSwilch, where Tswitch is added to TprOc,csi only. For example, as shown in FIG. 11, although the switch from Case 2 to Case 1 is semi-statically indicated, the UE 102 does not have enough time to measure aperiodic (AP) CSLRS and complete the Rx switch.

[0106] When a DCI received on SDL triggers an AP-SRS on FDD, for SRS in a resource set with usage set to 'codebook' or ‘antennaSwitching’, the time gap between the last symbol of the PDCCH and the first symbol of the SRS resource cannot be less than:^2 3” fTswitehl T [T B-switchl

[0107] Otherwise, the time gap between the last symbol of the PDCCH and the first symbol of the SRS resource cannot be less than:N2+ 14 + [Tswitch] + [TLB-switch]

[0108] where N2 is defined in 3GPP TS 38.214, Section 6.2.1.

[0109] FIG. 2 illustrates an example antenna switching pattern 200, according to some implementations. As shown in FIG. 2, the UE 102 may alternate between two semi-static antenna configurations. In a first antenna port configuration 202 (Case 1), the UE 102 can perform both transmission and reception on an FDD carrier (n5), while reception on the SDLAttorney Docket No. 56990-0096W01 / P71805WO1carrier (n29) is disabled. In a second antenna port configuration 204 (Case 2), the UE 102 can receive on the SDL carrier (n29), but transmission and reception may be disabled on the FDD carrier (n5). The UE 102 may be configured (via RRC signaling) with a switching duration for the first antenna port configuration 202 and a switching duration for the second antenna port configuration 204, ensuring that the antenna of the UE 102 is tuned to at most one downlink band at any given time.

[0110] FIG. 3 illustrates an example frequency band configuration 300, according to some implementations. In FIG. 3, a lower-band FDD carrier (e.g., band nl2) comprises a downlink frequency band (e.g., 869-894 MHz) and a paired uplink frequency band (e.g., 824-849 MHz) is used for both uplink and downlink on the PCell, while an unpaired SDL carrier (e.g., band n29) comprises a single downlink frequency band (e.g., 717-728 MHz) and is used for downlink on the SCell. This arrangement shows that an SDL carrier may be adjacent to one or more FDD carriers, which can lead to interference or complicate simultaneous reception. FIG.3 illustrates why Rx switching (e.g., between the two antenna configurations shown in FIG. 2) can be beneficial for LB-LB CA.[OHl] FIG. 4 illustrates an example of a DG-PDSCH repetition scheme 400, according to some implementations. In FIG. 4, the UE 102 transmits a PDSCH repetition #0 in slot n+2 (Case 2), a PDSCH repetition #1 in slot n+3 (Case 2), and a PDSCH repetition #2 in slot n+4 (Case 2). A PDSCH repetition #3 in slot n+5 is dropped because it falls within a Case 1 duration. The UE 102 may drop or treat any PDSCH repetition 402 that overlaps with the Case 1 duration as an error case.

[0112] FIG. 5 illustrates an example of a PUCCH repetition scheme 500, according to some implementations. In FIG. 5, the UE 102 transmits a PUCCH repetition #0 in slot n+1 (Case 1) and a PUCCH repetition #1 in slot n+5 (Case 1). A PUCCH repetition 502 that falls within a Case 2 duration may be dropped and not counted toward the configured Np^p(e(^ . In the example PUCCH repetition scheme 500,is 2.

[0113] FIG. 6 illustrates an example feedback transmission scheme 600, according to some implementations. In FIG. 6, HARQ process identifiers are shared between FDD and SDL to enable cross-carrier retransmissions. The UE 102 performs initial PDSCH HARQ #0 in slot n+2 (Case 2) and PDSCH HARQ #1 in slot n+3 (Case 2). PDSCH HARQ#2 in slot n+4 is unsuccessful, so the UE 102 performs a HARQ retransmission 602 in slot n+6 (Case 1). AsAttorney Docket No. 56990-0096W01 / P71805WO1described herein, sharing HARQ IDs may allow a TB originally received on one carrier (SDL) to be retransmitted on the other carrier (FDD) once the UE 102 has completed the Rx switch.

[0114] FIG. 7 illustrates an example UE processing timeline 700, according to some implementations. In FIG. 7, the UE receives a downlink DCI 702 in slot n+1 (Case 1) and a DG-PDSCH 704 in slot n+2 (Case 2). The duration between the downlink DCI 702 and the DG-PDSCH is greater than TLB-switch to ensure the UE 102 has enough time to switch from the first antenna port configuration 202 (Case 1) to the second antenna port configuration 204 (Case 2) before receiving the DG-PDSCH 704.

[0115] FIG. 8 illustrates an example UE processing timeline 800, according to some implementations. In FIG. 8, the UE 102 receives a PDSCH 802 in slot n+3 (Case 2) and transmits a corresponding PUCCH 804 in slot n+5 (Case 1). In some examples, the PUCCH 804 carries HARQ-ACK feedback for the PDSCH 802. As shown in the example UE processing timeline 800, the time interval between the PDSCH 802 and the PUCCH 804 is greater than Tproc l+ TLB-switch. Any PUCCH repetitions that fall within the switching gap between Case 2 and Case 1 may be dropped or deferred so that no uplink transmissions are sent during an Rx switch.

[0116] FIG. 9 illustrates an example UE processing timeline 900, according to some implementations. In FIG. 9, the UE 102 receives an uplink DCI 902 in a slot n+4 (Case 2) and transmits a DG-PUSCH 904 in a slot n+5 (Case 1). As shown in the example UE processing timeline 900, the time duration between the uplink DCI 902 and the DG-PUSCH 904 is greater than Tproc,2 + TLB-switch to accommodate for the Rx switch from SDL to FDD.

[0117] FIG. 10 illustrates an example UE processing timeline 1000, according to some implementations. In FIG. 10, the UE 102 transmits a random access message during an RO 1002 in slot n+5 (Case 1). To ensure the UE 102 has sufficient time to complete the Rx switch from Case 2 to Case 1 before transmitting the random access message, the interval between the start of the Case 1 switching gap and the start of the RO 1002 is greater than the RO duration + TLB-switch.

[0118] FIG. 11 illustrates an example UE processing timeline 1100, according to some implementations. In FIG. 11, the UE 102 receives an uplink DCI 1102 in slot n+3 (Case 2) and an AP CSI-RS 1104 in slots n+3 / 4 (Case 2). As shown in the example UE processing timeline 1100, a DG-PUSCH 1106 is scheduled in slot n+5 (Case 1). The interval between the uplink DCI 1102 and the DG-PUSCH 1106 is not greater than TprOc,csi + TLB-switcflbut the intervalAttorney Docket No. 56990-0096W01 / P71805WO1between the AP CSI-RS 1104 and the DG-PUSCH 1106 is less than T’proc,csi + Tin-switch so the UE 102 does not have enough time to measure the AP CSI-RS 1104 and finish the Rx switch from Case 2 to Case 1.

[0119] FIG. 12 illustrates an example UE processing timeline 1200, according to some implementations. In FIG. 12, the UE 102 receives a DCI 1202 in slot n+4 (Case 2) and transmits an AP SRS 1204 in a slot n+5 (Case 1). The interval between the DCI 1202 and the AP SRS 1204 is greater than N2+ TLB-switch so the UE 102 has enough time to complete the Rx switch from Case 2 to Case 1 before transmitting the AP SRS 1204.

[0120] FIG. 13 illustrates a flowchart of an example method 1300 for LB CA with Rx switching, according to some implementations. For clarity of presentation, the method 1300 is described in the context of the preceding figures. For example, the method 1300 can be performed by a UE, such as the UE 102 of FIG. 1. The method 1300 can also be performed by any suitable system, environment, software, hardware, or combination thereof. In some implementations, operations of the method 1300 can be run in parallel, in combination, in loops, or in any order. The example method 1300 shown in FIG. 13 can be modified or reconfigured to include additional, fewer, or different steps (not shown in FIG. 13), which can be performed in the order shown or in a different order.

[0121] At 1302, the UE receives control signaling that configures a switching pattern for the UE.

[0122] At 1304, the UE determines a first time duration associated with communication on a FDD carrier and a second time duration associated with reception on a SDL carrier based on the switching pattern.

[0123] At 1306, the UE determines whether to transmit or receive a signal in the first time duration or the second time duration based on the switching pattern and a carrier on which the signal is scheduled. The carrier is either the FDD carrier or the SDL carrier.

[0124] In some implementations, the FDD carrier (i) may include a downlink frequency band and a paired uplink frequency band and (ii) may be used for both uplink and downlink on a PCell.

[0125] In some implementations, the SDL carrier (i) may include an unpaired downlink frequency band and (ii) may be used for downlink on a SCell.Attorney Docket No. 56990-0096W01 / P71805WO1

[0126] In some implementations, the control signaling may include RRC signaling. The switching pattern may include a semi-static switching pattern.

[0127] In some implementations, the UE may not be expected to receive the signal via the SDL carrier in the first time duration. In some implementations, the signal may include a CSI-RS, a SSB, a TRS, a PDCCH, an active SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0128] In some implementations, the UE may not be expected to receive the signal via the FDD carrier in the second time duration. In some implementations, the signal may include a CSI-RS, an SSB, a TRS, a PDCCH, an SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0129] In some implementations, SPS-PDSCH may be activated for PDSCH reception via an FDD carrier in the first time duration. The UE may not be expected to receive SPS-PDSCH via an SDL carrier during occasions that partially overlap with the second time duration.

[0130] In some implementations, SPS-PDSCH may be activated for PDSCH reception via an SDL carrier in the second time duration. The UE may not be expected to receive SPS-PDSCH via an FDD carrier during occasions that overlap with the first time duration.

[0131] In some implementations, the UE may not be expected to transmit the signal via an FDD carrier in the second time duration. In some implementations, the signal may include a PRACH, a PUCCH unassociated with downlink control information (DCI), a PUCCH with repetitions scheduled in the first time duration and the second time duration, an active CG-PUSCH, a DG-PUSCH with repetitions scheduled in the first time duration and the second time duration, a multi-grant PUSCH with at least one PUSCH scheduled in the first time duration and the second time duration, or a SRS.

[0132] In some implementations, the first duration may be associated with a first antenna configuration. The second duration may be associated with a second configuration. In some implementations, the UE may not be expected to transmit a Type-1 or Type-2 CG-PUSCH using the first antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the second time duration. In some implementations, the UE may not be expected toAttorney Docket No. 56990-0096W01 / P71805WO1transmit a Type-1 or Type-2 CG-PUSCH using the second antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the first time duration.

[0133] In some implementations, a RO associated with the FDD carrier and scheduled in the second time duration may be considered invalid.

[0134] In some implementations, determining whether to transmit or receive the signal may include dropping one or more PUCCH repetitions associated with the FDD carrier and scheduled in the second time duration. The dropped PUCCH repetitions may not be counted toward a number of repetition slots.

[0135] In some implementations, available PUCCH repetition slots may start from a first available uplink slot in the first time duration.

[0136] FIG. 14 illustrates an example UE 1400, according to some implementations. The UE 1400 may be similar to and / or substantially interchangeable with the UE 102 of FIG. 1. The UE 1400 can be any mobile or non-mobile computing device, such as, for example, a mobile phone, computer, tablet, industrial wireless sensor, video device (for example, a camera or video camera), wearable device (for example, a smart watch), relaxed-IoT device, etc.

[0137] The UE 1400 can include processor 1402, RF interface circuitry 1404, memory / storage 1406, user interface 1408, sensors 1410, driver circuitry 1412, power management integrated circuit (PMIC) 1414, one or more antenna(s) 1416, and / or battery 1418. The components of the UE 1400 can be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof. The block diagram of FIG. 14 shows a high-level view of some of the components of the UE 1400. However, some of the components shown can be omitted, additional components may be present, and a different arrangement of the components shown can be used in other implementations.

[0138] The components of the UE 1400 may be coupled with various other components over one or more interconnects 1420, which can represent any type of interface, input / output, bus (local, system, or expansion), transmission line, trace, optical connection, etc., that allows various circuit components (on common or different chips or chipsets) to interact with one another.

[0139] The processor 1402 may include one or more processors. For example, the processor 1402 may include processor circuitry such as, for example, baseband processor circuitry (BB)Attorney Docket No. 56990-0096W01 / P71805WO11422A, central processor unit circuitry (CPU) 1422B, and graphics processor unit circuitry (GPU) 1422C. The processor 1402 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage 1406 to cause the UE 1400 to perform operations described herein.

[0140] In some implementations, the baseband processor circuitry 1422 A may access a communication protocol stack 1424 in the memory / storage 1406 to communicate over a 3 GPP compatible network. In general, the baseband processor circuitry 1422A may access the communication protocol stack to: perform user plane functions at a physical (PHY) layer, medium access control (MAC) layer, radio link control (RLC) layer, packet data convergence protocol (PDCP) layer, service data adaptation protocol (SDAP) layer, and protocol data unit (PDU) layer; and perform control plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and a non-access stratum (NAS) layer. In some implementations, the PHY layer operations may additionally / alternatively be performed by the components of the RF interface circuitry 1404. The baseband processor circuitry 1422A may generate or process baseband signals or waveforms that carry information in 3 GPP-compatible networks. In some implementations, the waveforms for NR may be based cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in the uplink or downlink, and discrete Fourier transform spread OFDM (DFT-S-OFDM) in the uplink.

[0141] The memory / storage 1406 may include one or more non-transitory, computer-readable media that includes instructions (for example, communication protocol stack 1424) that can be executed by the processor 1402 to cause the UE 1400 to perform various operations described herein. The memory / storage 1406 can include any type of volatile or non-volatile memory that may be distributed throughout the UE 1400. In some implementations, the memory / storage 1406 can be located on the processor 1402 itself (for example, LI and L2 cache), while other memory / storage 1406 is external to the processor 1402 but accessible thereto via a memory interface. The memory / storage 1406 may include any suitable volatile or non-volatile memory such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), Flash memory, solid-state memory, or any other type of memory device technology.Attorney Docket No. 56990-0096W01 / P71805WO1

[0142] The RF interface circuitry 1404 may include transceiver circuitry and radio frequency front module (RFEM) that allows the UE 1400 to communicate with other devices over a radio access network. The RF interface circuitry 1404 can include various elements arranged in transmit or receive paths. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0143] In the receive path, the RFEM may receive a radiated signal from an air interface via antenna(s) 1416 and proceed to filter and amplify (with a low-noise amplifier) the signal. The signal may be provided to a receiver of the transceiver that downconverts the RF signal into a baseband signal that is provided to the baseband processor.

[0144] In the transmit path, the transmitter of the transceiver up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM may amplify the RF signal through a power amplifier prior to the signal being radiated across the air interface via the antenna(s) 1416. In various implementations, the RF interface circuitry 1404 may be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0145] The antenna(s) 1416 may include one or more antenna elements to convert electrical signals into radio waves to travel through the air and to convert received radio waves over the air into electrical signals. In some implementations, the antenna elements may be arranged into one or more antenna panels. The antenna(s) 1416 may have antenna panels that are omnidirectional, directional, or a combination thereof, to enable beamforming and multiple input, multiple output communications. The antenna(s) 1416 can include any / all of microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. The antenna(s) 1416 may have one or more panels designed for one or more specific frequency bands, such as bands in FR1 or FR2.

[0146] The user interface 1408 includes various input / output (VO) devices designed to enable user interaction with the UE 1400. The user interface 1408 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (for example, a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number orAttorney Docket No. 56990-0096W01 / P71805WO1combinations of audio or visual display, including, inter alia, one or more simple visual outputs / indicators (for example, binary status indicators such as light emitting diodes “LEDs” and multi -character visual outputs), or more complex outputs such as display devices or touchscreens (for example, liquid crystal displays “LCDs,” LED displays, quantum dot displays, projectors), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the UE 1400.

[0147] The sensors 1410 may include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems or nanoelectromechanical systems including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; temperature sensors (for example, thermistors); pressure sensors; image capture devices (for example, cameras or lensless apertures); light detection and ranging sensors; proximity sensors (for example, infrared radiation detector and the like); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other like audio capture devices; etc.

[0148] The driver circuitry 1412 may include software and hardware elements that operate to control particular devices that are embedded in the UE 1400, attached to the UE 1400, or otherwise communicatively coupled with the UE 1400. The driver circuitry 1412 may include individual drivers allowing other components to interact with or control various input / output (I / O) devices that may be present within, or connected to, the UE 1400. For example, driver circuitry 1412 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface, sensor drivers to obtain sensor readings of sensors 1410 and control and allow access to sensors 1410, drivers to obtain actuator positions of electro-mechanic components or control and allow access to the electro-mechanic components, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

[0149] The PMIC 1414 can manage power provided to various components of the UE 1400. In particular, with respect to the processor 1402, the PMIC 1414 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.

[0150] In some implementations, the PMIC 1414 may control, or otherwise be part of, various power saving mechanisms of the UE 1400. A battery 1418 may power the UE 1400, althoughAttorney Docket No. 56990-0096W01 / P71805WO1in some examples the UE 1400 may be mounted deployed in a fixed location and may have a power supply coupled to an electrical grid. The battery 1418 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in vehicle-based applications, the battery 1418 may be a typical lead-acid automotive battery.

[0151] FIG. 15 illustrates an example access node 1500, according to some implementations. The access node 1500 (also referred to as a base station or gNB) may be similar to and / or substantially interchangeable with base station 104. The access node 1500 can include one or more of processor 1502, RF interface circuitry 1504, core network (CN) interface circuitry 1506, memory / storage circuitry 1508, and one or more antenna(s) 1510. The processor 1502 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage circuitry 1508 to cause the access node 1500 to perform operations as described herein.

[0152] The components of the access node 1500 may be coupled with various other components over one or more interconnects 1512. The processor 1502, RF interface circuitry 1504, memory / storage circuitry 1508 (including communication protocol stack 1514), antenna(s) 1510, and interconnects 1512 may be similar to like-named elements shown and described with respect to FIG. 14. For example, the processor 1502 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1516A, central processor unit circuitry (CPU) 1516B, and graphics processor unit circuitry (GPU) 1516C.

[0153] The CN interface circuitry 1506 may provide connectivity to a core network, for example, a 5th Generation Core network (5GC) using a 5GC -compatible network interface protocol such as carrier Ethernet protocols, or some other suitable protocol. Network connectivity may be provided to / from the access node 1500 via a fiber optic or wireless backhaul. The CN interface circuitry 1506 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuitry 1506 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

[0154] As used herein, the terms “access node,” “access point,” or the like refers to equipment that provides the radio baseband functions for data and / or voice connectivity between a network and one or more users. An access node may also be referred to as a base station (BS),Attorney Docket No. 56990-0096W01 / P71805WO1gNB, RAN node, eNB, NodeB, roadside unit (RSU), transmission and reception point (TRP), TRxP, and so on. An access node can include ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like refers to an access node 1500 that operates in an NR or 5G system (for example, a gNB), and the term “E-UTRAN node” or the like refers to an access node 1500 that operates in an LTE or 4G system (e.g., an eNB). According to various implementations, the access node 1500 can be implemented as one or more of a dedicated physical device, such as a macrocell base station, and / or a low power base station for providing femtocells, picocells or other cells with smaller coverage areas, smaller user capacity, or higher bandwidth (compared to macrocells).

[0155] In some implementations, the access node 1500 can be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a cloud RAN (CRAN) and / or a virtual baseband unit pool (vBBUP). In vehicle-to-everything (V2X) scenarios, the access node 1500 may be or act as an RSU, which refers to any transportation infrastructure entity used for V2X communications. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE is referred to as a “UE-type RSU,” an RSU implemented in or by an eNB is referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB is referred to as a “gNB-type RSU,” and so forth.

[0156] In the preceding description, various components are described as performing a task or tasks. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0157] In some embodiments, one or more of the components described in the preceding figures may be configured to perform one or more operations, techniques, processes, or methods set forth in the examples section below. For example, the baseband circuitry described in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, access node, base station, or network element may be configured to operate in accordance with one or more of the examples set forth below.

[0158] Example l is a method including: receiving control signaling that configures an antenna switching pattern for a UE; determining a first time duration associated with a first antennaAttorney Docket No. 56990-0096W01 / P71805WO1configuration and a second time duration associated with a second antenna configuration based on the antenna switching pattern; and determining whether to transmit or receive a signal in the first time duration or the second time duration based on the antenna switching pattern and a carrier on which the signal is scheduled.

[0159] Example 2 includes the method of example 1, where the first antenna configuration enables transmission and reception on a FDD carrier.

[0160] Example 3 includes the method of example 2, where the second antenna configuration enables reception on an SDL carrier.

[0161] Example 4 includes the method of any of examples 1-3, where the control signaling includes RRC signaling and the antenna switching pattern includes a semi -static antenna switching pattern.

[0162] Example 5 includes the method of any of examples 1-4, where the UE is not expected to receive the signal via an SDL carrier in the first time duration associated with the first antenna configuration.

[0163] Example 6 includes the method of example 5, where the signal includes a CSLRS, a SSB, a TRS, a PDCCH, an active SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0164] Example 7 includes the method of any of examples 1-6, where the UE is not expected to receive the signal via an FDD carrier in the second time duration associated with the second antenna configuration.

[0165] Example 8 includes the method of example 7, where the signal includes a CSLRS, an SSB, a TRS, a PDCCH, an SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0166] Example 9 includes the method of any of examples 1-8, where: SPS-PDSCH is activated for PDSCH reception via an FDD carrier in the first time duration associated with the first antenna configuration; and the UE is not expected to receive SPS-PDSCH via an SDL carrier during occasions that partially overlap with the second time duration associated with the second antenna configuration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0167] Example 10 includes the method of any of examples 1-9, where: SPS-PDSCH is activated for PDSCH reception via an SDL carrier in the second time duration associated with the second antenna configuration; and the UE is not expected to receive SPS-PDSCH via an FDD carrier during occasions that overlap with the first time duration associated with the first antenna configuration.

[0168] Example 11 includes the method of any of examples 1-10, where the UE is not expected to transmit the signal via an FDD carrier in the second time duration associated with the second antenna configuration.

[0169] Example 12 includes the method of example 11, where the signal includes a PRACH, a PUCCH unassociated with DCI, a PUCCH with repetitions scheduled in the first time duration and the second time duration, an active CG-PUSCH, a DG-PUSCH with repetitions scheduled in the first time duration and the second time duration, a multi -grant PUSCH with at least one PUSCH scheduled in the first time duration and the second time duration, or an SRS.

[0170] Example 13 includes the method of any of examples 1-12, where the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the first antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the second time duration associated with the second antenna configuration.

[0171] Example 14 includes the method of any of examples 1-13, where the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the second antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the first time duration associated with the first antenna configuration.

[0172] Example 15 includes the method of any of examples 1-14, where an RO associated with an FDD carrier and scheduled in the second time duration is considered invalid.

[0173] Example 16 includes the method of any of examples 1-15, where determining whether to transmit or receive the signal includes dropping one or more PUCCH repetitions associated with an FDD carrier and scheduled in the second time duration, where the dropped PUCCH repetitions are not counted toward a number of repetition slots.

[0174] Example 17 includes the method of any of examples 1-16, where available PUCCH repetition slots start from a first available uplink slot in the first time duration associated with the first antenna configuration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0175] Example 18 includes the method of any of examples 1-17, further including: receiving an indication of a cross-carrier scheduling IE including scheduling cell information for an SDL carrier; and determining whether the SDL carrier can be cross-carrier scheduled by an FDD carrier based on the scheduling cell information.

[0176] Example 19 includes the method of example 18, where determining whether the SDL carrier can be cross-carrier scheduled includes determining that the SDL carrier can be selfscheduled based on the scheduling cell information provided by the cross-carrier scheduling IE.

[0177] Example 20 includes the method of any of examples 18-19, where determining whether the SDL carrier can be cross-carrier scheduled includes determining that the SDL carrier can be self-scheduled or cross-carrier scheduled by the FDD carrier based on the scheduling cell information provided by the cross-carrier scheduling IE.

[0178] Example 21 includes the method of any of examples 18-20, further including transmitting capability information that indicates whether the UE supports cross-carrier scheduling, where determining whether the SDL carrier can be cross-carrier scheduled by the FDD carrier is based on the capability information.

[0179] Example 22 includes the method of any of examples 1-21, further including: transmitting a TB via an FDD carrier in the second time duration; and receiving a PDSCH retransmission including HARQ-ACK feedback for the TB via an SDL carrier during the first time duration.

[0180] Example 23 includes the method of example 22, where HARQ process IDs are shared between the FDD carrier and the SDL carrier.

[0181] Example 24 includes the method of any of examples 1-23, further including: receiving DCI via an FDD carrier during the first time duration, where the DCI schedules a DG-PDSCH or activates SPS-PDSCH on an SDL carrier.

[0182] Example 25 includes the method of example 24, where a time duration between the DCI and the DG-PDSCH or the SPS-PDSCH is greater than TLB-switch.

[0183] Example 26 includes the method of example 25, where TLB-switch includes a threshold time duration for switching between the first antenna configuration and the second antenna configuration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0184] Example 27 includes the method of any of examples 1-26, further including: receiving a PDSCH via an SDL carrier during the second time duration associated with the second antenna configuration; and transmitting a PUCCH with HARQ-ACK feedback for the PDSCH via an FDD carrier during the first time duration.

[0185] Example 28 includes the method of example 27, where a time duration between the PDSCH and the PUCCH is greater than TprOc,i+TLB -switch-

[0186] Example 29 includes the method of example 28, where TprOc,i represents a current PDSCH processing timeline of the UE and TLB-switch includes a threshold time duration for switching between the first antenna configuration and the second antenna configuration.

[0187] Example 30 includes the method of any of examples 1-29, further including: receiving DCI via an SDL carrier during the second time duration, where the DCI schedules a DG-PUSCH or activates a CG-PUSCH on an FDD carrier in the first time duration.

[0188] Example 31 includes the method of example 30, where a time duration between the DCI and the DG-PUSCH or the CG-PUSCH is greater than TprOc,2+TLB-switch.

[0189] Example 32 includes the method of example 31, where TprOc,2 represents a current PUSCH preparation timeline of the UE and TLB-switch includes a threshold time duration for switching between the first antenna configuration and the second antenna configuration.

[0190] Example 33 includes the method of any of examples 1-32, where a PRACH occasion on an FDD carrier that starts less than Ngapsymbols after a last symbol of a switch between the first antenna configuration and the second antenna configuration is considered invalid.

[0191] Example 34 includes the method of any of examples 1-33, further including: receiving a PDCCH order via an SDL carrier in the second time duration, where the PDCCH order initiates a random access procedure on an FDD carrier in the first time duration; and transmitting a random access message via the FDD carrier during a PRACH occasion within the first time duration, where a time duration between the PDCCH order and the PRACH occasion is greater than a threshold.

[0192] Example 35 includes the method of any of examples 1-34, further including: receiving DCI via an SDL carrier during the second time duration, where the DCI triggers a CSI report on a PUSCH associated with an FDD carrier; and receiving one or more AP CSLRS via the SDL carrier in accordance with the DCI.Attorney Docket No. 56990-0096W01 / P71805WO1

[0193] Example 36 includes the method of example 35, further including dropping a DG-PUSCH with the CSI report in response to determining that (i) a first time interval between the AP CSI-RS and the DG-PUSCH is less than or equal to a first threshold or (ii) a second time interval between the DCI and the DG-PUSCH is less than or equal to a second threshold.

[0194] Example 37 includes the method of any of examples 1-36, further including: receiving DCI via an SDL carrier during the second time duration, where the DCI triggers an AP-SRS on an FDD carrier in the first time duration; and determining a threshold time gap between the DCI and an SRS resource based on a codebook usage type associated with the SRS resource.

[0195] Example 38 includes the method of example 37, further including transmitting the AP-SRS on the SRS resource via the FDD carrier in response to determining that a time duration between the DCI and the SRS resource exceeds the threshold time gap.

[0196] Example 39 includes one or more processors configured to, when executing instructions stored in a memory, perform the method of any of examples 1-38.

[0197] Example 40 is a UE configured to perform the method of any of examples 1-38.

[0198] Example 41 is a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of examples 1-38.

[0199] Example 42 is a method including: receiving control signaling that configures a switching pattern for a UE, determining a first time duration associated with communication on a FDD carrier and a second time duration associated with reception on a SDL carrier based at least on the switching pattern, and determining whether to transmit or receive a signal in the first time duration or the second time duration based at least on the switching pattern and a carrier on which the signal is scheduled. The carrier is either the FDD carrier or the SDL carrier.

[0200] Example 43 includes the method of example 42, where the FDD carrier (i) comprises a downlink frequency band and a paired uplink frequency band and (ii) is used for both uplink and downlink on a PCell.

[0201] Example 44 includes the method of example 42, where the SDL carrier (i) comprises an unpaired downlink frequency band and (ii) is used for downlink on a SCell.

[0202] Example 45 includes the method of example 42, where control signaling comprises RRC signaling and the switching pattern comprises a semi-static switching pattern.Attorney Docket No. 56990-0096W01 / P71805WO1

[0203] Example 46 includes the method of example 42, where the UE is not expected to receive the signal via the SDL carrier in the first time duration.

[0204] Example 47 includes the method of example 46, where the signal comprises a CSI-RS, a SSB, a TRS, a PDCCH, an active SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0205] Example 48 includes the method of example 42, where the UE is not expected to receive the signal via the FDD carrier in the second time duration.

[0206] Example 49 includes the method of example 48, where the signal comprises a CSI-RS, an SSB, a TRS, a PDCCH, an SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

[0207] Example 50 includes the method of example 42, where SPS-PDSCH is activated for PDSCH reception via an FDD carrier in the first time duration, and where the UE is not expected to receive SPS-PDSCH via an SDL carrier during occasions that partially overlap with the second time duration.

[0208] Example 51 includes the method of example 42, where SPS-PDSCH is activated for PDSCH reception via an SDL carrier in the second time duration, and where the UE is not expected to receive SPS-PDSCH via an FDD carrier during occasions that overlap with the first time duration.

[0209] Example 52 includes the method of example 42, where the UE is not expected to transmit the signal via an FDD carrier in the second time duration.

[0210] Example 53 includes the method of example 52, where the signal comprises a PRACH, a PUCCH unassociated with DCI, a PUCCH with repetitions scheduled in the first time duration and the second time duration, an active CG-PUSCH, a DG-PUSCH with repetitions scheduled in the first time duration and the second time duration, a multi -grant PUSCH with at least one PUSCH scheduled in the first time duration and the second time duration, or a SRS.

[0211] Example 54 includes the method of example 42, where the first duration is associated with a first antenna configuration, and where the second duration is associated with a second configuration.Attorney Docket No. 56990-0096W01 / P71805WO1

[0212] Example 55 includes the method of example 54, where the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the first antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the second time duration.

[0213] Example 56 includes the method of example 54, where the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the second antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the first time duration.

[0214] Example 57 includes the method of example 42, where a RO associated with the FDD carrier and scheduled in the second time duration is considered invalid.

[0215] Example 58 includes the method of example 42, where determining whether to transmit or receive the signal comprises dropping one or more PUCCH repetitions associated with the FDD carrier and scheduled in the second time duration, where the dropped PUCCH repetitions are not counted toward a number of repetition slots.

[0216] Example 59 includes the method of example 42, where available PUCCH repetition slots start from a first available uplink slot in the first time duration.

[0217] Example 60 is a UE including memory and one or more processors coupled to the memory and configured to, when executing instructions stored in the memory, cause the UE to perform the method of any of examples 42-59.

[0218] Example 61 is a non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of examples 42-59.

[0219] Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0220] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.Attorney Docket No. 56990-0096W01 / P71805WO1

[0221] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

Attorney Docket No. 56990-0096W01 / P71805WO1CLAIMSWe Claim:

1. A method comprising:receiving control signaling that configures a switching pattern for a user equipment (UE);determining a first time duration associated with communication on a frequency division duplexing (FDD) carrier and a second time duration associated with reception on a supplementary downlink (SDL) carrier based at least on the switching pattern; and determining whether to transmit or receive a signal in the first time duration or the second time duration based at least on the switching pattern and a carrier on which the signal is scheduled, the carrier being either the FDD carrier or the SDL carrier.

2. The method of claim 1, wherein the FDD carrier (i) comprises a downlink frequency band and a paired uplink frequency band and (ii) is used for both uplink and downlink on a primary cell (PCell).

3. The method of claim 1, wherein the SDL carrier (i) comprises an unpaired downlink frequency band and (ii) is used for downlink on a secondary cell (SCell).

4. The method of claim 1, wherein the control signaling comprises radio resource control (RRC) signaling and the switching pattern comprises a semi-static switching pattern.

5. The method of claim 1, wherein the UE is not expected to receive the signal via the SDL carrier in the first time duration.

6. The method of claim 5, wherein the signal comprises a channel state information reference signal (CSI-RS), a synchronization signal block (SSB), a tracking reference signal (TRS), a physical downlink control channel (PDCCH), an active semi-persistent scheduled physical downlink shared channel (SPS-PDSCH), a dynamic grant physical downlink shared channel (DG-PDSCH) with repetitions scheduled in the first time duration and the second time duration, or a multi-grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.Attorney Docket No. 56990-0096W01 / P71805WO17. The method of claim 1, wherein the UE is not expected to receive the signal via the FDD carrier in the second time duration.

8. The method of claim 7, wherein the signal comprises a CSI-RS, an SSB, a TRS, a PDCCH, an SPS-PDSCH, a DG-PDSCH with repetitions scheduled in the first time duration and the second time duration, or a multi -grant PDSCH with at least one PDSCH scheduled in the first time duration and the second time duration.

9. The method of claim 1, wherein:SPS-PDSCH is activated for PDSCH reception via an FDD carrier in the first time duration; andthe UE is not expected to receive SPS-PDSCH via an SDL carrier during occasions that partially overlap with the second time duration.

10. The method of claim 1, wherein:SPS-PDSCH is activated for PDSCH reception via an SDL carrier in the second time duration; andthe UE is not expected to receive SPS-PDSCH via an FDD carrier during occasions that overlap with the first time duration.

11. The method of claim 1, wherein the UE is not expected to transmit the signal via an FDD carrier in the second time duration.

12. The method of claim 11, wherein the signal comprises a physical random access channel (PRACH), a physical uplink control channel (PUCCH) unassociated with downlink control information (DCI), a PUCCH with repetitions scheduled in the first time duration and the second time duration, an active configured grant physical uplink shared channel (CG-PUSCH), a dynamic grant physical uplink shared channel (DG-PUSCH) with repetitions scheduled in the first time duration and the second time duration, a multi -grant PUSCH with at least one PUSCH scheduled in the first time duration and the second time duration, or a sounding reference signal (SRS).

13. The method of claim 1, wherein the first duration is associated with a first antenna configuration, and wherein the second duration is associated with a second configuration.Attorney Docket No. 56990-0096W01 / P71805WO114. The method of claim 13, wherein the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the first antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the second time duration.

15. The method of claim 13, wherein the UE is not expected to transmit a Type-1 or Type-2 CG-PUSCH using the second antenna configuration if the Type-1 or Type-2 CG-PUSCH partially overlaps with the first time duration.

16. The method of claim 1, wherein a random access channel occasion (RO) associated with the FDD carrier and scheduled in the second time duration is considered invalid.

17. The method of claim 1, wherein determining whether to transmit or receive the signal comprises dropping one or more PUCCH repetitions associated with the FDD carrier and scheduled in the second time duration, wherein the dropped PUCCH repetitions are not counted toward a number of repetition slots.

18. The method of claim 1, wherein available PUCCH repetition slots start from a first available uplink slot in the first time duration.

19. A user equipment (UE) comprising:memory; andone or more processors coupled to the memory and configured to, when executing instructions stored in the memory, cause the UE to perform the method of any of claims 1-18.

20. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of claims 1-18.