Methods for carrier switching via a switching pattern
The low band carrier aggregation switching technique with a switching pattern addresses network congestion and complexity issues by enabling efficient carrier switching, enhancing network performance and reducing costs in 5G networks.
Patent Information
- Application Number
- PCT/CN2025/093790
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Low band carrier aggregation in 5G networks faces challenges such as network congestion in densely populated areas and low utilization rates due to the need for separate RF chains or common RF chains with complex configurations, which increase cost and complexity.
Implementing a low band carrier aggregation switching technique with a switching pattern configuration and UE requirements that allow effective switching between two component carriers based on a time window, using a configuration received from a network entity.
Enhances network efficiency and reduces operational costs by allowing seamless carrier switching, improving coverage and penetration while simplifying RF architecture.
Smart Images

Figure CN2025093790_12112026_PF_FP_ABST
Abstract
Description
METHODS FOR CARRIER SWITCHING VIA A SWITCHING PATTERNTECHNICAL FIELD
[0001] The present disclosure relates generally to wireless communication, and more particularly, to a low band carrier switching based on a switching pattern.BACKGROUND
[0002] The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR) . An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN) , a user equipment (5G UE) , etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and / or increased capacity compared to prior generation cellular communication systems.
[0003] Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, etc. ) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, low band carrier aggregation involves combining multiple low-frequency bands to improve coverage and penetration through obstacles. One example of a low-frequency band can support an uplink and downlink communication. However, this type of low band frequency band can suffer from a network congestion, especially in a densely populated area. Another example of a low band frequency band can offer an increased network coverage but can only support a downlink communication, which causes a low utilization rate. BRIEF SUMMARY
[0004] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
[0005] Carrier aggregation in fifth generation (5G) networks and beyond can enhance the performance and efficiency of mobile networks. By using the available spectrum through carrier aggregation, network operators can efficiently manage network resources, leading to enhanced service quality and reduced operation cost. Low band carrier aggregation involves combining multiple low-frequency bands to improve coverage and penetration through obstacles (e.g., buildings) . Low-frequency bands, typically below 1 Gigahertz (GHz) , can provide an extensive network coverage, making them desirable for a reliable connectivity (e.g., fewer dead zones, etc. ) especially in rural areas where deploying high-frequency bands may not be feasible. In addition, low band carrier aggregation can maintain a stable network connection in indoor settings, where higher frequency signals may struggle to penetrate obstacles.
[0006] One example of a low-frequency band can support an uplink and downlink communication. However, this type of low band frequency band can suffer from a network congestion, especially in a densely populated area. Another example of a low band frequency band can offer an increased network coverage but can only support a downlink communication, which causes a low utilization rate. Deploying low band carrier aggregation of multiple low-frequency bands can require significant changes in the user equipment (UE) infrastructure. The changes can include providing a separate radio frequency (RF) chain for each low-band carrier or a common RF chain supporting these multiple low-frequency bands. While a dedicated RF chain may provide enhanced performance, the increasing cost associated with additional hardware and components may be a barrier for network operators. The dedicated RF chain may also increase the complexity of the existing RF front end architecture. A common RF chain supporting these multiple low-frequency bands may offer a simple and cost effective solution. However, using this common RF chain configuration to accommodate multiple frequency bands with a small frequency separation may be challenging.
[0007] Aspects of the present disclosure address the above-noted and other deficiencies by implementing a low band carrier aggregation switching technique including a switching pattern configuration and UE requirements that allows the UE to switch effectively between two component carriers.
[0008] According to some aspects, the UE receives, from a network entity, a configuration indicating a switching pattern for carrier switching; switches between a first carrier and a second carrier, based on a time window having a limited number of switches associated with the switching pattern; and communicates, with the network entity and based on the switching, on one of the first carrier or the second carrier.
[0009] According to some aspects, the network entity, transmits, to a UE, a configuration indicating a switching pattern for carrier switching; and communicates with the UE on one of a first carrier or a second carrier.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells according to an embodiment.
[0011] FIG. 2A illustrates an example diagram of a switching pattern according to an embodiment.
[0012] FIG. 2B illustrates an example diagram of a switching pattern configuration according to an embodiment.
[0013] FIG. 3A illustrates an example scenario of a location of a switching gap according to an embodiment.
[0014] FIG. 3B illustrates another example scenario of a location of a switching gap according to an embodiment.
[0015] FIG. 4A illustrates an example scenario that supports hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission according to an embodiment.
[0016] FIG. 4B illustrates an example scenario of the overlapping of switching gap and the states of cell discontinuous reception (DRX) according to an embodiment.
[0017] FIG. 5 is a signaling diagram illustrating an example of carrier switching procedure according to an embodiment.
[0018] FIG. 6 is an example procedure for triggering a switch from a secondary cell (SCell) to a primary cell (PCell) according to an embodiment.
[0019] FIG. 7 is another example procedure for triggering a switch from a SCell to a PCell according to an embodiment.
[0020] FIG. 8 illustrates an example scenario of an overlap between the switching gap and the measurement gap according to an embodiment.
[0021] FIG. 9A illustrates a method, which can be implemented by a UE for switching between a PCell and a SCell according to an embodiment.
[0022] FIG. 9B illustrates a method, which can be implemented by a UE for switching between a frequency division duplex (FDD) carrier and a supplemental downlink (SDL) carrier according to an embodiment.
[0023] FIG. 10 is a flowchart of a method of wireless communication at a UE according to an embodiment.
[0024] FIG. 11 is a flowchart of a method of wireless communication at a network entity according to an embodiment.
[0025] FIG. 12 is a diagram illustrating a hardware implementation for an example UE apparatus according to some embodiments.
[0026] FIG. 13 is a diagram illustrating a hardware implementation for one or more example network entities according to some embodiments.DETAILED DESCRIPTION
[0027] FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations / network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110) . For example, a CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU) , a virtual distributed unit (VDU) , or a virtual central unit (VCU) . The base station / network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108) , may be referred to as a transmission reception point (TRP) .
[0028] Operations of the base station 104 and / or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN) , which may also be referred to a cloud radio access network (C-RAN) . Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d, 104e and / or the RUs 106a, 106b, 106c, 106d may communicate with the UEs 102a, 102b, 102c, 102d, and / or 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and / or base stations 104 may simultaneously serve the UEs 102, such as by intra-cell and / or inter-cell access links between the UEs 102 and the RUs 106 / base stations 104.
[0029] The RU 106, the DU 108, and the CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information / signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information / signals between the DU 108 and the CU 110. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and / or receive the information / signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.
[0030] The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.
[0031] The RUs 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the RUs 106.
[0032] Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown) . The base stations 104 may be associated with macrocells for higher-power cellular base stations and / or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network. ”
[0033] Transmissions from a UE 102 to a base station 104 / RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104 / RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink / forward link communication to the UE 102d or receive an uplink / reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d / RU 106d.
[0034] Communication links between the UEs 102 and the base stations 104 / RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104 / RUs 106 may utilize a spectrum bandwidth of YMHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary component carrier may be associated with a primary cell (PCell) and a secondary component carrier may be associated with a secondary cell (SCell) .
[0035] Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication / D2D link utilizes a spectrum for a wireless wide area network (WWAN) associated with uplink and downlink communications. Such sidelink / D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc.
[0036] The UEs 102 and the base stations 104 / RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS) ) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b. The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104 / RUs 106 may or may not be the same.
[0037] In further examples, beamformed signals may be communicated between a first base station / RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.
[0038] The base station 104 may include and / or be referred to as a network entity. That is, “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and / or the CU 110. The base station 104 may also include and / or be referred to as a next generation evolved Node B (ng-eNB) , a next generation NB (gNB) , an evolved NB (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108, and / or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN) . In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station / RU 106a. In such cases, the base station 104e can be a master node and the base station / RU 106a can be a secondary node.
[0039] Still referring to FIG. 1, any of the UEs 102 may include a carrier switching component 140 configured to receive a configuration indicating a switching pattern for carrier switching; switch between a first carrier and a second carrier, based on a time window having a limited number of switches associated with the switching pattern; and communicate, with the network entity and based on the switching, on one of the first carrier or the second carrier.
[0040] The base stations 104 or a network entity of the base stations 104 may include a carrier switching configuration component 150 configured to transmit, to a UE 102, a configuration indicating a switching pattern for switching between a first carrier and a second carrier based on a time window having a limited number of switches associated with the switching pattern; and communicate, with the UE 102 and based on the switching pattern, on one of the first carrier or the second carrier. Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A) , and other wireless technologies, such as 6G.
[0041] FIG. 2A illustrates an example diagram 200 of a carrier switching pattern according to an embodiment. Referring to FIG. 2A, the network entity 104 configures a carrier switching pattern 224 (or may be referred to as switching pattern or semi-static switching pattern) in the form of bitmap. Each bit in the bitmap indicates the configured carrier for the corresponding slot. For example, bit ‘0' indicates the frequency division duplex (FDD) carrier 1 is in use (i.e., the UE 102 is transmitting and receiving (Tx / Rx) on an FDD carrier while there is no receiving (Rx) on a supplementary downlink (SDL) carrier) and bit ‘1' indicates SDL carrier 2 is in use (i.e., the UE 102 is Rx on the SDL carrier while there is no Tx / Rx on an FDD carrier) . Still referring to FIG. 2, the network entity 104 configures the carrier switching pattern 224 as {0 1 0 1 } to indicate the UE 102 may switch from FDD carrier 1 to SDL carrier 2 to FDD carrier 1 to SDL carrier 2. The carrier switching pattern may start from the beginning of system frame number (SFN) 0 of PCell.
[0042] FIG. 2B illustrates an example diagram 250 of a switching pattern configuration according to an embodiment. Referring to FIG. 2B, a switching pattern configuration 1 261A may include a periodicity, P1 263A, a bitmap1 264A, number of switches X1 within duration Y1 265A, a switching threshold T1 266A, and a priority rule R1 267A. Similarly, a switching pattern configuration 2 261B may include a periodicity, P2 263B, a bitmap2 264B, number of switches X2 within duration Y2 265B, a switching threshold T2 266B, and a priority rule R2 267B.
[0043] These switching patterns allows the UE 102 to switch between two main operational states: Case 1: Tx / Rx on the FDD carrier and no Rx on the SDL carrier. That means the UE 102 is transmitting and receiving on an FDD carrier while there is no receiving on SDL. Case 2: Rx on the SDL carrier and no Tx / Rx on the FDD carrier. That means the UE 102 is receiving on the SDL carrier while there is no transmitting and receiving on the FDD carrier.
[0044] In some embodiments, when the UE 102 receives an RRC message configuring or modifying the semi-static switching pattern (e.g., periodicity, start offset, bitmap, ... ) , the UE 102 is expected to start operating according to the configured or the updated pattern. The UE 102 can be expected to start operating according to the pattern after a specified / configured time offset (e.g., with reference to SFN 0 of the PCell) or when the new RRC configuration becomes active (e.g., at the transmission of the RRC reconfiguration complete message) .
[0045] In some embodiments, since the UE 102 is initially at the PCell it could be expected that the UE starts with a bit in the bitmap indicating operation at the PCell. If the bitmap starts with a bit indicating SCell, it could be expected that a switching gap is applied before the start of the operation with the new / configured pattern or at the start of the operation with the new / configured pattern.
[0046] In some embodiments, the UE 102 indicates the maximum X number of switches within Y slots, the values of Y and / or P in the UE capability report.
[0047] In some embodiments, the network entity 104 configures the UE 102 with one set of predefined switching patterns (e.g., with different periodicities, bitmap structures, number of switches, ..., etc. ) via a radio resource control (RRC) signaling. The network entity 104 may indicate a specific switching pattern, for example, by indicating (via downlink control information (DCI) or medium access control-control element (MAC-CE) ) an index from a predefined table.
[0048] In some embodiments, the network entity 104 configures a sliding window within any continuous number Y of slots (which could span across the pattern periodicities) , and the number of carrier switches in the continuous window of Y slots must not exceed X. The sliding window technique helps avoid clustering of the switches, which might not be solved by a simple limit within the overall periodicity P.
[0049] In some embodiments, the network entity 104 configures a threshold, T, representing a minimum number of slots between switches within a window. The UE may determine a number of switches, X, in a window, Y based on a condition. In an implementation, the condition includes the number of switches, X, in the window is less than the Y divided by the threshold, T (i.e., X < Y / T) . For example: for a periodicity, P = 10 millisecond (ms) (which is 10 slots at 15 Kilohertz (kHz) subcarrier spacing (SCS) , assuming 1 ms slots) ; Y = 5 ms (5 slots) ; T = 2 (slots / switch, meaning on average at least 2 slots between switches, or a switch occurs no more frequently than every 2 slots on average within the window) ; Therefore, X < 5 slots / 2 slots / switch => X < 2.5 switches. Since X is an integer, this means X can be 0 (no switch) , 1 switch, or 2 switches.
[0050] In some embodiments, the UE 102 may remain operating on a particular carrier for a minimum number of consecutive slots (e.g., a fixed number or a ratio of P, such as P / 2, etc. ) before switching again to another carrier.
[0051] In some implementations, the network entity 104 configures up to Xl switches within the transmission of a synchronization signal block (SSB) burst (e.g., within the period P) . The SSB burst may refer to the actual transmitted SSB burst, which may be configured by the network entity 104 via RRC signaling (e.g., system information blockl (SIB1) ) . Alternatively, the SSB burst may refer to the nominal SSB burst (e.g., SSB burst includes all the candidate SSBs) . The value of Xl may be predefined (e.g., Xl = 0 (no switch within an SSB burst) ) , or reported by the UE capability. In some aspects, the SSB burst may refer to the always-on SSB (e.g., SSB with center frequency configured by absoluteFrequencySSB) , on-demand SSB (e.g., SSB configured by od-ssb-config and / or to be activated by a control signalling, e.g., RRC or MAC-CE or DCI) , and / or SSB with adaptation (e.g., SSB configured by addl-ssb-Periodicity and / or with a set of periodicities configured) .
[0052] In some other implementations, the network entity 104 configures up to X2 switches within the transmission of a tracking reference signal (TRS) (e.g., channel state information-reference signal (CSI-RS) resource set with TRS-Info configured) transmission occasion. The value of X2 may be predefined (e.g., X2 = 0 (no switch within a TRS transmission occasion) ) , or reported by the UE capability. In some aspects, the UE 102 may refrain from receiving a transmission occasion of a TRS if it is partially transmitted in one carrier; otherwise, it may receive the transmission occasion.
[0053] In some implementations, the network entity 104 and the UE 102 may determine the random access channel occasion (RO) in the slot configured for the SDL carrier as invalid RO, where the slot may be the UL slot for the FDD carrier. Alternatively or additionally, the network entity 104 and the UE 102 may determine the RO in such slot as valid RO, e.g., network entity 104 and the UE 102 perform the RO validation based on the UL / DL configuration for the FDD carrier, then when the UE 102 determines to transmit the PRACH on such RO, the UE 102 may drop the PRACH transmission, or switch to the FDD carrier to transmit the PRACH, or transmit the PRACH on the next available RO, which may be associated with the same SSB / CSI-RS.This may be applied to the PRACH resources configured by the network entity 104 including or excluding the additional PRACH resources for time-domain adaptation. The RO may refer to the ROs configured by the PRACH resources in RACH-ConfigCommon, the ROs configured by the additional PRACH resources for PRACH adaptation (e.g., addl-RACH-Config-Adaptation) , and / or ROs configured for subband full duplex (SBFD) . The network entity 104 and UE 102 may perform the same operation above for the PUSCH occasion validation or select the PUSCH occasion for the uplink transmission, where the PUSCH occasions may be configured by the network entity 104 for 2-step random access channel (RACH) procedure, or RACH-less handover, or lower layer triggered mobility.
[0054] FIGs. 3A and 3B illustrate example scenarios of a location of a switching gap according to an embodiment. Referring to FIG. 3A, in scenario 300, for example, the network entity 104 configures the location of the switching gap 332A at the end of the duration of the “switching from carrier. ” During the switching gap, the UE 102 calibrates its RF, antenna, and baseband configuration to adapt to the new carrier. During the switching gap, the UE 102 is not expected to receive or transmit data and it is not expected to be scheduled with any UL or DL data in the same serving cell or in another serving cell in a band or band combination or in a serving cell set configured by the network or reported by the UE 102.
[0055] In some embodiments, the network entity 104 configures the location of the switching gap at the start of the duration of the “switching to” carrier. Referring to FIG. 3B, in scenario 350, for example, the network entity 104 configures the location of the switching gap 332B at the start of the duration of the “switching to carrier. ”
[0056] FIG. 4A illustrates an example scenario 400 that supports hybrid automatic repeat request-acknowledgement (HARQ-ACK) transmission according to an embodiment. Referring to FIG. 4A, in a scenario where the UE is operating on the SDL (Rx only) , the UE 102 can receive physical downlink shared channel (PDSCH) data (e.g., 442A, 442B, 442C) on the SDL carrier 222, but the UE 102 cannot transmit HARQ-ACK on a physical uplink control channel (PUCCH) 444 on the SDL carrier 222. In this scenario, the UE 102 may have to wait based on the switching gap 332A before the UE 102 can transmit the HARQ-ACK feedback associated with the PDSCH on the FDD carrier (e.g., 442A, 442B, 442C) .
[0057] After the UE 102 receives PDSCHs (e.g., 442A, 442B, 442C) on the SCell (e.g., in Case 2) and then switches back to PCell (e.g., Case 1) , the configuration may indicate a specific HARQ-ACK window (e.g., a number of symbols / slots) on the PCell immediately after the switch to be prioritized or reserved for HARQ-ACK transmissions associated with the received PDSCHs (e.g., 442A, 442B, 442C) .
[0058] In some embodiments, CSI measurements carried on the SDL SCell are transmitted after the switch to the FDD PCell. A configuration may indicate a specific CSI window (e.g., a number of symbols / slots) on the PCell immediately after the switch to be prioritized or reserved for CSI measurement transmissions associated with the received CSI-RS on the SDL SCell. In another example, the CSI measurements on SDL SCell are dropped. In another example, a specified number of CSI measurements carried on the SDL SCell are transmitted on the PCell (e.g., the last / most-recent N measurements (e.g., N = 1) , ... )
[0059] In some embodiments, the network entity 104 schedules the PDSCH on the SCell such that the corresponding HARQ-ACK feedback timing falls within the HARQ-ACK window.
[0060] In 3GPP TS 38.214 (section 5.3) , the minimum UE PDSCH processing time Tproc, 1 is specified as: Tproc, 1 = (N1 + d1, 1 + d2 + d3) (2048 + 144) ·κ2-μ·TC + Text
[0061] Where N1 is based on μ of table 5.3-1 and table 5.3-2 for UE processing capability 1 and 2 respectively, where μ corresponds to the one of (μphysical downlink control channel (PDCCH) , μPDSCH, μUL) resulting with the largest Tproc, 1, where the μPDCCH corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, the μPDSCH corresponds to the subcarrier spacing of the scheduled PDSCH, and μUL corresponds to the subcarrier spacing of the uplink channel with which the HARQ-ACK is assumed to be transmitted for PDSCH with or without disabled HARQ-ACK feedback, and κ is defined in section 4.1 of 3GPP TS 38.211.
[0062] However, the introduction of carrier switching mechanisms raises a processing timeline issue. When the UE 102 transitions from the operation on the SDL carrier (Case 2, involving PDSCH reception on SDL carrier 2) to the operation on the FDD carrier (Case 1, involving FDD carrier 1) , a particular timing aspect requires some considerations. In this situation, the UE 102 receives the PDSCH on the SDL carrier 2 before the switch occurs, but the corresponding HARQ-ACK feedback must then be transmitted on the uplink of FDD carrier 1 after the switching process is complete.
[0063] In one example implementation, an additional time, A may be included as an additional element when calculating the Tproc, 1 value to ensure the transition is adequately accounted for. For example, the updated minimum UE PDSCH processing time Tproc, 1 is specified as: Tproc, 1 = (N1 + d1, 1 + d2 + d3) (2048 + 144) ·κ2-μ·TC + Text + Δ
[0064] In some embodiments, the additional time A is equal to the duration of the switching gap. In some other embodiments, the additional time Δ is configured / indicated by the network entity 104 (e.g., via RRC, DCI, MAC-CE, ... ) . In some other embodiments, the additional time A is specified and fixed in the specifications. In some other embodiments, the additional time Δ is reported by the UE capability.
[0065] In some aspects, the additional time may be included for the CSI report (e.g., included in the minimum offset between the DCI and the uplink channel for CSI report and / or in the minimum offset between the last channel measurement resource or interference measurement resource and the uplink channel for CSI report) , which may be equal to the duration of the switching gap, or configured / indicated by the network entity 104 (e.g., via RRC, DCI, MAC-CE, ..., etc. ) , or specified and fixed in the specifications, or reported by the UE capability.
[0066] In some implementations, the UE 102 considers the semi-static switching pattern only during the DRX active time.
[0067] In some embodiments, the switching pattern indicates that the UE is not expected to switch carriers during the DRX inactive time.
[0068] In some embodiments, the switching pattern is only applied for slots in the DRX active time (i.e., slots in inactive time are not considered (skipped) in the pattern) .
[0069] In some implementations, the network entity 104 configures up to X4 switches within Y slots during DRX active time. Thus, the switches during DRX inactive time are not counted. The value of X4 and Y may be pre-defined or reported by the UE capability.
[0070] In some implementations, the UE 102 switches from case 1 to case 2 or from case 2 to case 1 only during the DRX active time of the PCell. For example, if switching associated with the switching pattern happens during DRX inactive time then switching is delayed to the start of the next DRX active time.
[0071] In a scenario where the configured duration from the bitmap to stay on Case 2 or Case 1 extends beyond the DRX active time and the switch is supposed to happen during the DRX inactive time, the UE 102 may switch to the other carrier early before the expiry of DRX active time (e.g., before going to sleep) . In some other embodiments, the UE 102 switches to the other carrier late, at the start of the next DRX active time. In some other embodiments, the UE 102 extends the DRX active time to complete the carrier duration from the bitmap and then switch back to the other carrier following the switching pattern and then follow the DRX inactive time.
[0072] FIG. 4B illustrates an example scenario 400 of the overlapping of switching gap and the states of cell discontinuous reception (DRX) according to an embodiment. Referring to FIG. 4B, the switching gap 332A located at the end the Band 1 220 overlaps with the DRX transition 450A from an active state 450 to an inactive state 452. The switching gap 332A overlaps with the moment the drx-OnDurationTimer or the drx-InactivityTimer is expiring.
[0073] In some embodiments, the UE 102 completes the switch from one carrier to the other carrier and then proceeds into the DRX inactive mode, i.e., DRX active is extended to cover the switch (and potentially the start of SDL activity) . The network entity 104 may send a DCI or MAC-CE or schedule a PDSCH to extend the active time to cover the switch.
[0074] In some embodiments, the UE 102 proceeds into the DRX inactive mode following the DRX configuration and postpones the switch from one carrier to the other carrier to the next active DRX time. When the UE 102 wakes up, the UE 102 refers to the state of the semi-static switching pattern to determine which carrier to be on.
[0075] In some embodiments, the UE is specified with different rules based on the “switch-to” carrier. For example, if switching to the PCell (FDD carrier) : the UE 102 completes the switch and then proceeds into the DRX inactive rime. In another example, if switching to the SCell (SDL carrier) , the UE 102 proceeds into the inactive DRX and then switches to the SCell in the next active time.
[0076] In some embodiments, the UE 102 is not expected to be configured with the semi-static switching pattern such that the switching gaps coincides with the expiry points of the DRX active time of the UE 102. The UE 102 is expected to be scheduled with data such that the drx-InactivityTimer expires before or after the switching gap.
[0077] In some implementations, the network entity 104 may configure and / or activate the DRX for the two carriers by a common or separate signaling, e.g., common, or separate RRC parameters, or common or separate DCIs or DCI fields in one DCI.
[0078] In some implementations, the network entity 104 may configure and / or activate the cell discontinuous transmission (DTX) for the two carriers by a common or separate signaling, e.g., common, or separate RRC parameters, or common or separate DCIs or DCI fields in one DCI. In one example, the network entity 104 may provide common configuration for the cell DTX for the two carriers. The UE may report the UE capability indicating whether it supports different configuration of the cell DTX for the two carriers.
[0079] In some implementations, the network entity 104 may configure and / or activate the cell DRX for the two carriers by a common or separate signaling, e.g., common, or separate RRC parameters, or common or separate DCIs or DCI fields in one DCI. In one example, the network entity 104 may provide common configuration for the cell DRX for the two carriers. The UE may report the UE capability indicating whether it supports different configuration of the cell DRX for the two carriers.
[0080] In one example implementation, the network entity 104 configures multiple gap durations. The network entity 104 may configure the UE 102 with multiple possible gap durations (e.g., short, average, long, etc. ) . The network entity 104 may dynamically indicate which gap duration the UE 102 should apply (e.g., via DCI or a MAC-CE) to accommodate variations in a timing advance. Alternatively, the network entity 104 may configure the gap duration via RRC signaling. The UE 102 may report the minimum or preferred gap duration via an RRC message (e.g., UE capability or UE assistance information (UAI) ) , or MAC-CE, or uplink control information (UCI) (e.g., MAC-CE or UCI for timing information report or timing advance (TA) report) .
[0081] In another example implementation, the network entity 104 may configure the switching gap duration according to a timing advance group (TAG) . In this scenario, when the UE 102 is assigned to a particular TAG, the UE 102 would automatically use the switching gap duration that has been preconfigured with that TAG.
[0082] The unit of the duration of the switching gap may be defined in terms of, number of symbols, or slots, milliseconds, etc. The network entity 104 and the UE 102 may determine the duration of the switching gap based on a subcarrier spacing predefined, e.g., 15 kHz, or configured by the network entity 104.
[0083] For the application of the switching gap, ifthe switching gap is applied at the end of the duration of “the switch from” carrier, the end of the switching gap is aligned with the end of the “the switch from” cartier duration as in the switching pattern. If the switching gap is applied at the start of the duration of “the switch to” carrier, the start of the switching gap is aligned with the start of the “the switch to” carrier duration as in the switching pattern.
[0084] In some embodiments, the UE 102 may be configured to perform additional carrier switches outside of those configured by the semi-static switching pattern. This flexibility may be beneficial to support procedures like RACH, where the UE 102 may need to switch carriers in a way that does not align with the predefined schedule. This is important because if a high priority event occurs on the PCell (FDD carrier) while the UE 102 is operating on the SCell (SDL carrier) as per the pattern, the UE 102 might be unable to switch back to the PCell on time. Consequently, there is a risk that the UE 102 could become isolated or unresponsive on the SDL carrier, especially during events such as radio link failure (RLF) .
[0085] In one example implementation, a high priority procedure can be defined where the UE 102 can switch back to PCell, deviating from the configured switching pattern (e.g., RLF) . A DCI bit-field or a MAC-CE field can be used to trigger an additional switching from PCell to SCell or from SCell to PCell for high priority procedure reasons.
[0086] In one example embodiment, if a signal is supposed to be received by the UE on PCell (e.g., handover command, lower layer triggered mobility (LTM) command, beam failure recovery, ..., etc. ) while the UE 102 is scheduled for an SCell duration (based on the carrier switching pattern) , a trigger signal for emergency switch to PCell can be specified (e.g., via DCI or MAC-CE) and can be received on the SCell and will request the UE 102 to switch back to perform the required procedure.
[0087] FIG. 5 is a signaling diagram 500 illustrating communications between a UE 102 and a network entity 104 for switching from one carrier to another carrier. The network entity 104 may correspond to a base station or a unit of a base station, such as the RU 106, the DU 108, the CU 110, etc.
[0088] Referring to FIG. 5, the network entity 104 may transmit 501, to the UE 102, (and the UE 102 may receive 501, from the network entity 104) a UE capability enquiry message.
[0089] The UE 102 may transmit 503, to the network entity 104, (and the network entity 104 may receive 503 from the UE 102) a UE capability information message including a UE capability information element (IE) . In some implementations, the UE capability IE includes a capability indicating support of carrier aggregation (CA) with switching pattern.
[0090] The network entity 104 transmits 505, to the UE 102, (and the UE 102 receives 505, from the network entity 104) an RRC configuration message or an RRC reconfiguration message to configure the UE for carrier aggregation with a switching pattern. The RRC configuration message or the RRC reconfiguration message switching pattern may indicate a switching pattern.
[0091] The UE 102 transmits 507, to the network entity 104, (and the network entity 104 receives 507, from the UE 102) a RRC configuration complete message. The UE 102 may apply the configuration and the switching pattern to communicate with the network entity 104 as described below. For example, the UE 102 applies the location of the switching gap configured in the switching pattern.
[0092] The network entity 104 transmits 509, to the UE 102, (and the UE receives 509, from the network entity 104) a DL control information (DCI) scheduling a DL transmission on the secondary component carrier serving the SCell.
[0093] The network entity 104 transmits 511, to the UE 102, (and the UE receives 511, from the network entity 104) a DL transmission on the SCell in accordance with the DCI. In some implementations, the DL transmission is a PDSCH transmission.
[0094] The network entity 104 detects 513 high priority events (e.g., handover, BFR conditions, etc. ) . The network entity 104 determines 515 to trigger the UE 102 to switch to the PCell.
[0095] The network entity 104 transmits 517, to the UE 102, (and the UE receives 517, from the network entity 104) a trigger on the SCell triggering the UE to switch to the primary component carrier serving the PCell.
[0096] The UE 102 decodes 519 the trigger, aborts SCell activity, and initiates the switch to the PCell. The UE 102 switches 521 to the PCell and monitors the expected signal (e.g., handover command, BFR resources, etc. ) .
[0097] The network entity 104 transmits 523, to the UE 102, (and the UE receives 523, from the network entity 104) a control signal on PDCCH (e.g., HO command, LTM command, RACH trigger for BFR, other DL signaling on the primary PCell, etc. ) . The UE 102 receives 525 the critical signal and performs the required procedure. The UE 102 communicates 527 with the network entity 104.
[0098] In some implementations, the network entity 104 may configure whether the UE autonomous carrier switching is enabled or not. If it is enabled, the UE 102 may switch the carrier if the UE 102 identifies at least one of the followings: UE is to transmit a PRACH triggered by a certain event (e.g., handover command, LTM command, beam failure recovery and so on, or PRACH ordered by the network) ; the UE 102 is to transmit a PUCCH configured for a certain usage (e.g., beam failure recovery, scheduling request, UE initiated CSI / beam report, and so on) ; the UE 102 is to transmit a configured-grant PUSCH (CG-PUSCH) . If it is disabled, the UE 102 shall perform the carrier switching based on the network-configured pattern.
[0099] FIG. 6 illustrates a method 600, which can be implemented by a UE (e.g., the UE 102) , for switching from the secondary cell (SCell) to the primary cell (PCell) according to configurations (e.g., configuration 261A-261B, for example, switching pattern 224) . The method 600 begins at block 605, where the UE is configured in the secondary component cell according to SCell duration (as per the configured carrier switching pattern) . For example, the UE is currently served by the SCell according to the SCell timer (e.g., sCellDeactivationTimer) dictating how long the SCell remains active before it is deactivated ifno data is received, or a timer expires.
[0100] The method continues at block 617, where the UE 102 monitors SCell PDCCH / PDSCH for any trigger of an emergency PCell switch (e.g., DCI, MAC-CE,...) .
[0101] At block 617A, ifthe UE 102 determines that the UE receives a trigger on the SCell ( “Yes” branch of block 617A) , the method proceeds to block 619A; otherwise ( “No” branch of block 617A) , the method proceeds to block 605A. At block 619A, the UE 102 decodes the trigger signal. At block 619B, the UE 102 aborts current SCell activities. At block 619C, the UE calibrates RF, baseband configuration, ... etc. to PCell.
[0102] At block 621, the UE 102 monitors PDCCH on PCell for critical DL signaling (e.g., Handover command, BFR signaling, RRC messaging, ..., etc. ) . At block 625, the UE 102 receives critical PCell signaling and executes required procedure. The method ends at block 629.
[0103] FIG. 7 illustrates a method 700, which can be implemented by a base station (e.g., the network entity 104) and the UE 102, for configuring the UE to switch from the secondary component carrier to the primary component carrier according to configurations (e.g., configuration 261-261 B, for example, switching pattern 224) . The method 700 begins at block 705, where the network entity 104 configures the UE with carrier aggregation (CA) (e.g., PCell and SCell) and with carrier switching pattern.
[0104] The method continues at block 713, where the network entity 104 detects a triggering event requiring the UE 102 action PCell (e.g., handover, PCell BFR, urgent RRC messaging, ..., etc. ) .
[0105] At block 715, ifthe network entity 104 determines that the UE 102 is on a SCell duration ( “Yes” branch of block 715) , the method proceeds to block 717; otherwise ( “No” branch of block 715) , the method proceeds to block 705A, where the UE 102 continues with the PCell operation. At block 717, the network entity 104 transmits an emergency trigger to switch the UE to the PCell (e.g., via DCI, MAC-CE, etc. ) . At block 723, the network entity 104 transmits critical signaling on the PCell. At block 723B, the network entity 104 monitors the UE for response / action. At block 725, the UE executes the PCell procedure. The method 700 ends at block 729.
[0106] In one example implementation, ifBFR is triggered (or handover or LTM or RRC messaging, or any other specified procedure is triggered, etc. ) and the UE is on the PCell duration but the switching to the SCell is imminent according to the carrier switching pattern, the UE 102 stops following the switching pattern (e.g., switching pattern is cancelled or suspended or expected to be reconfigured after the end of the procedure by the same cell or by a new target cell) and stays on PCell for BFR. The network entity 104 can activate the UE 102 again later to follow the switching pattern. In another example, a timer can be specified / configured allowing the UE 102 to follow the pattern again after the end of the BFR procedure. In general, some procedures can be specified to implicitly / explicitly cancel the switching pattern operation (e.g., start of a handover or a BFR or deactivation of the SCell, ... ) . Some explicit signaling can be defined / specified to cancel the switching pattern operation (e.g., DCI signaling or MAC-CE) . New / existing fields / bit-fields in the MAC-CE and / or DCI signaling can be specified for this purpose. Other implicit rules can be specified for the deactivation of the semi-static switching pattern, for example the semi-static switching pattern is only applicable when the SCell is active.
[0107] In one example implementation, for the UL power control for the FDD PCell, when the UE is configured to operate on the SDL SCell, UL transmissions on the FDD PCell are temporarily suspended during the operation on the SDL SCell. After switching back to the FDD PCell, the UE can resume using the same power control parameters (e.g., p0 nominal p0-UE-PUSCH, p0-nominalWithGrant, deltaMCS-Enabled, p0-PUCCH-value, p0_SRS, pathloss loss compensation for SRS, srs-PowerControl Adjustment, pathloss compensation factor, pathloss estimate, preambleReceivedTargetPower, PRACH-PowerRampingStep, etc. ) and the same power control loop. In another example, the power control loop is reset and the same parameters are re-used. In another example, different power control parameters are re-configured and the power control loop is reset. In another example, the UE can re-use the old parameters like pathloss estimates for the initial transmission until the closed loop reconverges with new parameters.
[0108] In another example, the network entity 104 may activate / re-activate the usage of the carriers switching pattern via dynamic signaling (e.g., DCI, MAC-CE, ..., etc. ) .
[0109] In another example, the network entity 104 may cancel a switching from one carrier to another carrier to keep the UE 102 on the same carrier, i.e., cancelling one or multiple bit (s) in the semi-static pattern.
[0110] FIG. 8 illustrates an example scenario 800 of the overlapping between the switching gap and the measurement gap according to an embodiment. Referring to FIG. 8, in some scenarios, measurement gaps 854 (e.g., configured for inter-frequency / inter-radio access technology (inter-RAT) measurements) may overlap with the switching gaps 332A.
[0111] In some embodiments, the UE 102 prioritizes the measurement gap over the switching gap. After the measurement gap, the UE 102 proceeds according to the semi-static switching pattern. Thus, the UE 102 may ignore the carrier configuration from the network entity 104 during the measurement gap, and perform the measurement based on the measurement object during the measurement gap. In this scenario, the switching gap may be cancelled as the UE 102 would have enough time within the measurement gap to tune back to the carrier of semi-static switching pattern.
[0112] In some embodiments, the UE 102 prioritizes the switching gap over the measurement gap. In one example, the UE 102 may perform the measurement on the measurement object when the UE 102 is configured in one carrier (e.g., FDD carrier or SDL carrier) . In another example, the network entity 104 may configure common or separate measurement gaps for different carriers.
[0113] In some embodiments, the UE 102 prioritizes the gap that happens first in time. In some embodiments, a priority per gap may be configured to indicate to the UE 102 whether to prioritize the measurement gap or the switching gap.
[0114] In some embodiments, the network entity 104 may use a dynamic signaling to cancel a measurement gap that overlaps with the switching gap. For example, a DCI bit field “1” may indicate to cancel the measurement gap and prioritize the switching; and DCI bit field “0” may indicate to prioritize the measurement gap (and possibly to cancel switching or postpone switching) .
[0115] In some embodiments, a priority may be configured to determine between performing the measurement on the measurement gap and performing the switching during the switching gap. The priority may be configured depending on the type of the measurement gap. For example, radio resource management (RRM) measurement gap has a higher priority than switching gap, but positioning measurement gap has lower priority than the switching gap.
[0116] In some embodiments, if switching gap is from Band 1 to Band 2 and the measurement gap is to measure Band 2, then the UE 102 switches to Band 2 and performed the measurement first and stays on Band 2 per the switching pattern.
[0117] In some embodiments, if switching gap is from Band 1 to Band 2 and the measurement gap is to measure Band n, then the UE 102 switches to Band n first to perform the measurement and then switches to Band 2 and the switching gap is shifted.
[0118] In scenarios where there is a partial overlapping, in some embodiments, the UE 102 performs the measurements during the initial part of the overlapping if the measurement gap starts first. If the measurement is a high priority, the UE 102 continues the measurement and delays the switching, otherwise the UE 102 cancels the remaining of the measurement gap and performs the switching.
[0119] In some implementations, the network entity 104 configures up to X3 switches within a measurement gap. The value of X3 may be predefined, e.g., X3 = 0 (no switch within a measurement gap) , or reported by the UE capability.
[0120] When the UE 102 switches from one carrier to another carrier or from PCell to SCell or from SCell to PCell, the handling of HARQ buffer, buffer status report (BSR) , timers, may be addressed according to the following embodiments.
[0121] In some embodiments, the UE 102 flushes the buffer, resets the timer, and drops the BSR when the UE 102 switches from one carrier to another carrier.
[0122] In some embodiments, the UE 102 maintains the buffer, maintains the timer (e.g., packet data convergence protocol (PDCP) discard timer) , and maintains the BSR when the UE switches from one carrier to another carrier.
[0123] In some embodiments, HARQ information for SDL PDSCH have to be buffered across the switching since data received on SDL needs its HARQ feedback to be sent on the FDD. In some implementations, the UE 102 flushes the HARQ buffer if the switch is from the FDD to the SDL. In some implementations, the UE 102 maintains the HARQ buffer for the switch from the SDL to the FDD.
[0124] In some other embodiments, a buffer status report (BSR) and / or delay status report (DSR) reflect only UL data buffer.
[0125] Since UL is only for FDD, the UE 102 drops BSR and / or DSR when the UE switches from FDD to SDL.
[0126] The UE 102 flushes UL data buffer when the UE switches from FDD to SDL.
[0127] The network may further configure whether the UE should perform any one of the embodiments, as described above. Alternatively of additionally, the UE 102 may report to the network entity 104 whether the UE performs any one of the embodiments, as described above.
[0128] In some implementation, the timing alignment timer can be specified to continue to run when the UE switches from the PCell (e.g., FDD) to SCell (e.g., SDL) to avoid losing UL sync. In another example embodiment, the timing alignment timer is reset when the UE switches from SCell (e.g., SDL) to PCell (e.g., FDD) .
[0129] In some implementation, for Type 1 or Type 2 CG-PUSCH (on FDD) . If the UE switches to SDL during an active CG, the CG PUSCH occasions on FDD are missed. The timer itself may continue. In another embodiment, the timers can be paused, reset upon return to FDD for that CG or just cancelled.
[0130] In some implementations, the UE may maintain a common HARQ entity for the two carriers. Thus, the HARQ processes in the two carriers are shared. Alternatively, the UE may maintain separate HARQ entities for the two carriers. Thus, the HARQ processes in the two carriers are not shared. The maximum number of HARQ processes across the two carriers may be pre-defined, e.g., the same as the maximum number of HARQ processes for a serving cell, or may be reported by the UE capability. In some other implementations, the network may configure whether the two carrier share a common HARQ entity or not.
[0131] FIG. 9A illustrates a method 900, which can be implemented by a UE (e.g., the UE 102) . The method 900 begins at block 905 where the UE 102 receives a configuration for switching between carriers.
[0132] At block 906A, if the UE 102 determines that the UE switches from a PCell to a SCell ( “Yes” branch of block 906A) , the method proceeds to block 920A; otherwise ( “No” branch of block 906A) , the method proceeds to block 920B.
[0133] At block 920A, the UE 102 may flush a HARQ buffer 920A-1, flush a data buffer 920A-2, drop a BSR 920A-3, drop a DSR 920A-4, or maintain a TAT 920A-5.
[0134] At block 920B, the UE 102 may maintain the HARQ buffer 920B-1, maintain the data buffer 920B-2, maintain the BSR 920B-3, maintain the DSR 920B-4, or stop the TAT 920B-5.
[0135] FIG. 9B illustrates a method 950, which can be implemented by a UE (e.g., the UE 102) . As described above, the method 950 begins at block 905 where the UE 102 receives a configuration for switching between carriers.
[0136] At block 906B, if the UE 102 determines that the UE switches from an FDD carrier to an SDL carrier ( “Yes” branch of block 906B) , the method proceeds to block 920A; otherwise ( “No” branch of block 906B) , the method proceeds to block 920B.
[0137] As described above, at block 920A, the UE 102 may flush a HARQ buffer 920A-1, flush a data buffer 920A-2, drop a BSR 920A-3, drop a DSR 920A-4, or maintain a TAT 920A-5.
[0138] At block 920B, the UE 102 may maintain the HARQ buffer 920B-1, maintain the data buffer 920B-2, maintain the BSR 920B-3, maintain the DSR 920B-4, or stop the TAT 920B-5, as described above.
[0139] FIGs. 10 and 11 show methods for implementing one or more aspects of FIGs. 2A-9B. In particular, FIG. 10 shows an implementation by the UE 102 of the one or more aspects of FIGs. 2A-9B. FIG. 11 shows an implementation by the network entity 104 of the one or more aspects of FIGs. 2A-9B.
[0140] FIG. 10 illustrates a flowchart 1000 of a method of wireless communication at a UE. With reference to FIGs. 1-9B, the method may be performed by the UE 102.
[0141] In embodiments, the UE 102 may transmit 1003, to the network entity 104, UE capability indicating at least one of: a value of X for a number of switches within the time duration, a value of Y for the time duration, a periodicity of the switching pattern, a maximum number of switches within a transmission of an S SB, a maximum number of switches within a TRS, a maximum number of switches within a measurement gap, a maximum number of switches within slots during an active period of a cell DRX, a maximum number of a HARQ feedback associated with the first carrier and the second carrier, a duration of the switching gap, a minimum number of slots between a switch of carriers, or an additional time to process a PDSCH associated with the HARQ feedback. For example, referring to FIG. 5, the UE 102 transmits 503, to the network entity 104, a UE capability information message including a UE capability IE.
[0142] In embodiments, the UE 102 receives 1005, from a network entity 104, a configuration indicating a switching pattern for carrier switching. For example, referring to FIG. 5, the UE 102 receives 505, from the network entity 104, an RRC configuration message or an RRC reconfiguration message to configure the UE for the carrier aggregation with a switching pattern. The RRC configuration message or the RRC reconfiguration message switching pattern may indicate a switching pattern.
[0143] In embodiments, the UE 102 switches 1021, between a first carrier and a second carrier, based on a time window having a limited number of switches associated with the switching pattern. For example, referring to FIG. 5, the UE 102 switches 521 to PCell and monitors the expected signal (e.g., handover command, LTM command, BFR resources, etc. ) .
[0144] In embodiments, the UE 102 communicates 1027, with the network entity 104, and based on the switching, on one of the first carrier or the second carrier. For example, referring to FIG. 5, the UE 102 communicates 527 with the network entity 104.
[0145] FIG. 10 describes a method from a UE-side of a wireless communication link, whereas FIG. 11 describes a method from a network-side of the wireless communication link.
[0146] FIG. 11 is a flowchart 1100 of a method of wireless communication at a network entity. With reference to FIGs. 1-9B, the method may be performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, and / or the CU 110.
[0147] In embodiments, the network entity 104 may receive 1103, from the UE 102, UE capability indicating at least one of: a value of X for a number of switches within the time duration, a value of Y for the time duration, a periodicity of the switching pattern, a maximum number of switches within a transmission of an SSB, a maximum number of switches within a TRS, a maximum number of switches within a measurement gap, a maximum number of switches within slots during an active period of a cell DRX, a maximum number of a HARQ feedback associated with the first carrier and the second carrier, a duration of the switching gap, a minimum number of slots between a switch of carriers, or an additional time to process a PDSCH associated with the HARQ feedback. For example, referring to FIG. 5, the network entity 104, receives 503, from the UE 102, a UE capability information message including a UE capability IE.
[0148] In embodiments, the network entity 104 transmits 1105, to the UE 102, a configuration indicating a switching pattern for switching between a first carrier and a second carrier based on a time window having a limited number of switches associated with the switching pattern. For example, referring to FIG. 5, the network entity 104 transmits 505, to the UE 102, an RRC configuration message or an RRC reconfiguration message to configure the UE for the carrier aggregation with a switching pattern.
[0149] In embodiments, the network entity 104 may transmit 1117, to the UE 102, a trigger to switch from the SCell to the PCell based on an event associated with the PCell. For example, referring to FIG. 5, the network entity 104 transmits 517, to the UE 102a trigger on the SCell triggering the UE to switch to the PCell.
[0150] In embodiments, the network entity 104 communicates 1127, with the UE 102 and based on the switching pattern, on one of the first carrier or the second carrier. For example, referring to FIG. 5, network entity 104 communicates 527 with the UE 102.
[0151] A UE apparatus 1202, as described in FIG. 12, may perform the method of flowchart 1000. The one or more network entities 104, as described in FIG. 13, may perform the method of flowchart 1100.
[0152] FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for a UE apparatus 1202. The UE apparatus 1202 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 1202 may include an application processor 1206, which may have on-chip memory 1206'. In examples, the application processor 1206 may be coupled to a secure digital (SD) card 1208 and / or a display 1210. The application processor 1206 may also be coupled to a sensor (s) module 1212, a power supply 1214, an additional module of memory 1216, a camera 1218, and / or other related components.
[0153] The UE apparatus 1202 may further include a wireless baseband processor 1226, which may be referred to as a modem. The wireless baseband processor 1226 may have on-chip memory 1226'. Along with, and similar to, the application processor 1206, the wireless baseband processor 1226 may also be coupled to the sensor (s) module 1212, the power supply 1214, the additional module of memory 1216, the camera 1218, and / or other related components. The wireless baseband processor 1226 may be additionally coupled to one or more subscriber identity module (SIM) card (s) 1220 and / or one or more transceivers 1230 (e.g., wireless RF transceivers) .
[0154] Within the one or more transceivers 1230, the UE apparatus 1202 may include a Bluetooth module 1232, a WLAN module 1234, an SPS module 1236 (e.g., GNSS module) , and / or a cellular module 1238. The Bluetooth module 1232, the WLAN module 1234, the SPS module 1236, and the cellular module 1238 may each include an on-chip transceiver (TRX) , or in some cases, just a transmitter (TX) or just a receiver (RX) . The Bluetooth module 1232, the WLAN module 1234, the SPS module 1236, and the cellular module 1238 may each include dedicated antennas and / or utilize antennas 1240 for communication with one or more other nodes. For example, the UE apparatus 1202 can communicate through the transceiver (s) 1230 via the antennas 1240 with another UE (e.g., sidelink communication) and / or with a network entity 104 (e.g., uplink / downlink communication) , where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.
[0155] The wireless baseband processor 1226 and the application processor 1206 may each include a computer-readable medium / memory 1226', 1206', respectively. The additional module of memory 1216 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1226', 1206', 1216 may be non-transitory. The wireless baseband processor 1226 and the application processor 1206 may each be responsible for general processing, including execution of software stored on the computer-readable medium / memory 1226', 1206', 1216. The software, when executed by the wireless baseband processor 1226 / application processor 1206, causes the wireless baseband processor 1226 / application processor 1206 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the wireless baseband processor 1226 / application processor 1206 when executing the software. The wireless baseband processor 1226 / application processor 1206 may be a component of the UE 102. The UE apparatus 1202 may be a processor chip (e.g., modem and / or application) and include just the wireless baseband processor 1226 and / or the application processor 1206. In other examples, the UE apparatus 1202 may be the entire UE 102 and include the additional modules of the apparatus 1202.
[0156] As discussed in FIG. 1 and implemented with respect to FIG. 10, the carrier switching component 140 is configured to receive a configuration indicating a switching pattern for carrier switching; switch between a first carrier and a second carrier, based on a time window having a limited number of switches associated with the switching pattern; and communicate, with the network entity and based on the switching, on one of the first carrier or the second cartier.
[0157] The carrier switching component 140 may be within the application processor 1206 (e.g., at 140a) , the wireless baseband processor 1226 (e.g., at 140b) , or both the application processor 1206 and the wireless baseband processor 1226. The carrier switching component 140a-140b may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof. FIG. 13 is a diagram 1300 illustrating an example of a hardware implementation for one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1346, which may have on-chip memory 1346'. In some aspects, the CU 110 may further include an additional module of memory 1356 and / or a communications interface 1348, both of which may be coupled to the CU processor 1346. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an Fl interface between the communications interface 1348 of the CU 110 and a communications interface 1328 of the DU 108.
[0158] The DU 108 may include a DU processor 1326, which may have on-chip memory 1326'. In some aspects, the DU 108 may further include an additional module of memory 1336 and / or the communications interface 1328, both of which may be coupled to the DU processor 1326. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1328 of the DU 108 and a communications interface 1308 of the RU 106.
[0159] The RU 106 may include an RU processor 1306, which may have on-chip memory 1306'. In some aspects, the RU 106 may further include an additional module of memory 1316, the communications interface 1308, and one or more transceivers 1330, all of which may be coupled to the RU processor 1306. The RU 106 may further include antennas 1340, which may be coupled to the one or more transceivers 1330, such that the RU 106 can communicate through the one or more transceivers 1330 via the antennas 1340 with the UE 102.
[0160] The on-chip memory 1306', 1326', 1346' and the additional modules of memory 1316, 1336, 1356 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of the processors 1306, 1326, 1346 is responsible for general processing, including execution of software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor (s) 1306, 1326, 1346 causes the processor (s) 1306, 1326, 1346 to perform the various functions described herein. The computer-readable medium / memory may also be used for storing data that is manipulated by the processor (s) 1306, 1326, 1346 when executing the software. In examples, the carrier switching configuration component 150 may sit at any of the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.
[0161] As discussed in FIG. 1 and implemented with respect to FIG. 11, the carrier switching configuration component 150 is configured to transmit, to a UE 102, a configuration indicating a switching pattern for switching between a first carrier and a second carrier based on a time window having a limited number of switches associated with the switching pattern; and communicate, with the UE 102 and based on the switching pattern, on one of the first carrier or the second carrier.
[0162] The carrier switching configuration component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1306 (e.g., at 150a) , the DU processor 1326 (e.g., at 150b) , and / or the CU processor 1346 (e.g., at 150c) . The carrier switching configuration component 150a-150c may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors 1306, 1326, 1346 configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by the one or more processors 1306, 1326, 1346, or a combination thereof.
[0163] The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.
[0164] The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
[0165] Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0166] An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems-on-chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
[0167] Ifthe functionality described herein is implemented in software, the functions may be stored on, or encoded as, one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media includes computer storage media and can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.
[0168] Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, machine learning (ML) -enabled devices, etc. The aspects, implementations, and / or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.
[0169] Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor (s) , interleavers, adders / summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.
[0170] The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.
[0171] Reference to an element in the singular does not mean “one and only one” unless specifically stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may” , “might” , and “can” , as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of) . The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.
[0172] Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C” or “one or more of A, B, or C” include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiples of A, multiples of B, and / or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more. Terms or articles such as “a” , “an” , and / or “the” may refer to one of an item, feature, element, etc., that the term or article precedes, or may refer to more than one of said item, feature, element, etc. that the term or article precedes. For example, the recitation “awidget” does not preclude reference to multiples of said widget, as “multiple widgets” necessarily includes “awidget” . Hence, the recitation “awidget” may be interpreted as “at least one widget” or, similarly, interpreted as “one or more widgets” .
[0173] Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term.
[0174] Reference numbers, as used in the specification and figures, are sometimes cross-referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings) . Hence, like numbers may refer to like actions.
[0175] Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” , where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.
[0176] The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.
[0177] Example 1 is a method of wireless communication at a user equipment, UE, including receiving, from a network entity, a configuration indicating a switching pattern for carrier switching; switching, between a first carrier and a second carrier, based on a time window having a limited number of switches associated with the switching pattern; and communicating, with the network entity and based on the switching, on one of the first carrier or the second carder.
[0178] Example 2 may be combined with example 1 and further includes that the first carrier includes at least one of: a frequency division duplex, FDD, carrier, a time division duplex, TDD, carrier, a supplementary downlink, SDL, carrier, or a supplementary uplink, SUL, carrier; and further includes that the second carrier includes at least one of: a FDD carrier, a TDD carrier, a SDL carrier, or a SUL carrier; and further includes that the first carrier is different from the second carrier.
[0179] Example 3 may be combined with any examples 1-2 and further includes that the first carrier is associated with a primary cell (PCell) and the second carrier is associated with a secondary cell (SCell) .
[0180] Example 4 may be combined with any examples 1-3 and further includes that the communicating including at least one of: communicating on the first carrier while refraining from communicating on the second carrier; or communicating on the second carrier while refraining from communicating on the first carrier.
[0181] Example 5 may be combined with example 4 and further includes receiving, from the network entity, a trigger to switch from the SCell to the PCell based on an event associated with the PCel1.
[0182] Example 6 may be combined with any examples 1-5 and further includes that the switching pattern includes: a periodicity of the switching pattern, a bitmap including a first bit indicating the first carrier and a second bit indicating the second carrier, and a number of switches within a time duration.
[0183] Example 7 may be combined with any examples 1-6 and further includes that the switching pattern is based on at least one off a sliding window to limit an X number of switches within Y slots and further includes that X and Y are integers, a condition that X is less Y divided by T and further includes that T is a threshold, or a minimum number of slots between a switch of carriers.
[0184] Example 8 may be combined with example 7 and further includes that T is at least one of: a predefined threshold, a configured threshold, or a UE-reported threshold.
[0185] Example 9 may be combined with any examples 1-8 and further includes that the configuration indicates switching gap information including at least one of: a location of a switching gap, a duration of the switching gap, a timing advance group, TAG, or a subcarrier spacing.
[0186] Example 10 may be combined with any examples 1-9 and further includes performing, independent from the switching pattern, an additional switch between the first and second carriers based a priority rule.
[0187] Example 11 may be combined with example 10 and further includes that the priority rule is associated with at least one of: a physical random access channel, PRACH, transmission, a UE-initiated report, a scheduling request, or a configured uplink transmission.
[0188] Example 12 may be combined with any examples 1-5 and further includes ignoring a switch associated with the switching pattern to maintain communication on a current carrier based on a triggering event.
[0189] Example 13 may be combined with example 12 and further includes that the triggering event is associated with at least one of: a beam failure recovery procedure, a handover procedure, a lower-layer triggered mobility procedure, a radio link failure procedure, or a radio resource control, RRC, configuration procedure.
[0190] Example 14 may be combined with any examples 1-13 and further includes that a measurement gap overlaps with a switching gap associated with the switching pattern, the switching between the first carrier and the second carrier being based on at least one of: the measurement gap having a higher priority than the switching gap, the switching gap having a higher priority than the measurement gap, a timing occasion of the measurement gap and the switching gap, a network configured-priority, or a partial overlap between the measurement gap overlaps and the switching gap.
[0191] Example 15 may be combined with example 14 and further includes that the switching between the first carrier and the second carrier is associated with at least one off an active period of a cell discontinuous reception, DRX, slots within the active period of the cell DRX, or an overlap between the switching gap and a transition from the active period to an inactive period of the cell DRX.
[0192] Example 16 may be combined with any examples 1-15 and further includes that a transmission occasion of a hybrid automatic repeat request, HARQ, feedback occurs within a HARQ window; the method and further includes determining an additional time to process a physical downlink shared channel, PDSCH, associated with the HARQ feedback, the additional time being determined based on at least one of: a duration of a switching gap, the configuration, or a UE capability report.
[0193] Example 17 the method any of examples 1-16, the method further comprising at least one of: flushing a data buffer, maintaining the data buffer, flushing a hybrid automatic repeat request, HARQ, buffer, maintaining the HARQ buffer, resetting a timer, continue running the timer, dropping a buffer status report, BSR, maintaining the BSR, dropping a delay status report, DSR, maintaining the DSR, maintaining a timing alignment timer, TAT, stopping the TAT, maintaining a timer associated with configured grant-physical uplink shared channel, CG-PUSCH, occasions, or sharing hybrid automatic repeat request, HARQ, processes across the first carrier and the second carrier.
[0194] Example 18 may be combined with any examples 1-17 and further includes transmitting, to the network entity, UE capability indicating support for at least one of: a value of X for a number of switches within the time duration, a value of Y for the time duration, a periodicity of the switching pattern, a maximum number of switches within a transmission of a synchronization signal block, SSB, a maximum number of switches within a transmission of a tracking reference signal, TRS, a maximum number of switches within a measurement gap, a maximum number of switches within slots during an active period of a cell discontinuous reception, DRX, a maximum number of a hybrid automatic repeat request, HARQ, feedback associated with the first carrier and the second carrier, a duration of the switching gap, a minimum number of slots between a switch of carriers, or an additional time to process a physical downlink shared channel, PDSCH, associated with the HARQ feedback.
[0195] Example 19 is a method of wireless communication at a network entity, including transmitting, to a user equipment, UE, a configuration indicating a switching pattern for switching between a first carrier and a second carrier based on a time window having a limited number of switches associated with the switching pattern; and communicating, with the UE and based on the switching pattern, on one of the first carrier or the second carrier.
[0196] Example 20 may be combined with example 19 and further includes that the first carrier includes at least one of: a frequency division duplex, FDD, carrier, a time division duplex, TDD, carrier, a supplementary downlink, SDL, carrier, or a supplementary uplink, SUL, carrier; and further includes that the second carrier includes at least one of: a FDD carrier, a TDD carrier, a SDL carrier, or a SUL carrier; and further includes that the first carrier is different from the second carrier.
[0197] Example 21 may be combined with any examples 19-20 and further includes that the first carrier is associated with a primary cell (PCell) and the second carrier is associated with a secondary cell (SCell) .
[0198] Example 22 may be combined with any examples 19-21 and further includes that the communicating including at least one of: communicating on the first carrier while refraining from communicating on the second carrier; or communicating on the second carrier while refraining from communicating on the first cartier.
[0199] Example 23 may be combined with example 22 and further includes transmitting, to the UE, a trigger to switch from the SCell to the PCell based on an event associated with the PCell.
[0200] Example 24 may be combined with example 23 and further includes that the event is associated with at least one of: a beam failure recovery procedure, a handover procedure, a lower-layer triggered mobility procedure, a radio link failure procedure, or a radio resource control, RRC, configuration procedure.
[0201] Example 25 may be combined with any examples 19-24 and further includes that the switching pattern includes: a periodicity of the switching pattern, a bitmap including a first bit indicating the first carrier and a second bit indicating the second carrier, and a number of switches within a time duration.
[0202] Example 26 may be combined with any examples 19-25 and further includes that the switching pattern is based on at least one of: a sliding window to limit an X number of switches within Y slots and further includes that X and Y are integers, a condition that X is less Y divided by T and further includes that T is a threshold, or a minimum number of slots between a switch of carriers.
[0203] Example 27 may be combined with example 26 and further includes that T is at least one of: a predefined threshold, a configured threshold, or a UE-reported threshold.
[0204] Example 28 may be combined with any examples 19-27 and further includes that the configuration indicates switching gap information including at least one of: a location of a switching gap, a duration of the switching gap, a timing advance group, TAG, or a subcarrier spacing.
[0205] Example 29 may be combined with any examples 19-28 and further includes that a measurement gap overlaps with a switching gap associated with the switching pattern, the switching between the first carrier and the second carrier being based on at least one of: the measurement gap having a higher priority than the switching gap, the switching gap having a higher priority than the measurement gap, a timing occasion of the measurement gap and the switching gap, a network configured-priority, or a partial overlap between the measurement gap overlaps and the switching gap.
[0206] Example 30 may be combined with example 29 and further includes that the switching between the first carrier and the second carrier is associated with at least one of: an active period of a cell discontinuous reception, DRX, slots within the active period of the cell DRX, or an overlap between the switching gap and a transition from the active period to an inactive period of the cell DRX.
[0207] Example 31 may be combined with any examples 19-30 and further includes that a transmission occasion of a hybrid automatic repeat request, HARQ, feedback occurs within a HARQ window.
[0208] Example 32 may be combined with any examples 19-31 and further includes receiving, from the UE, UE capability indicating support for at least one of: a value of X for a number of switches within the time duration, a value of Y for the time duration, a periodicity of the switching pattern, a maximum number of switches within a transmission of a synchronization signal block, SSB, a maximum number of switches within a transmission of a tracking reference signal, TRS, a maximum number of switches within a measurement gap, a maximum number of switches within slots during an active period of a cell discontinuous reception, DRX, a maximum number of a hybrid automatic repeat request, HARQ, feedback associated with the first carrier and the second carrier, a duration of the switching gap, a minimum number of slots between a switch of carriers, or an additional time to process a physical downlink shared channel, PDSCH, associated with the HARQ feedback.
[0209] Example 33 is an apparatus for wireless communication for implementing a method as in any of Examples 1-32.
[0210] Example 34 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-32.
[0211] Example 35 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-32.
[0212] Example 36 is a computer program product for implementing a method as in any of Examples 1-32.
Claims
1.A method of wireless communication at a user equipment, UE, (102) , comprising:receiving (505) , from a network entity (104) , a configuration indicating a switching pattern for carrier switching;switching (521) , between a first carrier and a second carrier, based on a time window having a limited number of switches associated with the switching pattern; andcommunicating (527) , with the network entity (104) and based on the switching, on one of the first carrier or the second carrier.2.The method of claim 1, wherein the first carrier includes at least one of: a frequency division duplex, FDD, carrier, a time division duplex, TDD, carrier, a supplementary downlink, SDL, carrier, or a supplementary uplink, SUL, carrier; wherein the second carrier includes at least one of: a FDD carrier, a TDD carrier, a SDL carrier, or a SUL carrier; wherein the first carrier is different from the second carrier.3.The method of any of claims 1-2, wherein the first carrier is associated with a primary cell (PCell) and the second carrier is associated with a secondary cell (SCell) .4.The method of claim 3, further comprising:receiving (517) , from the network entity (104) , a trigger to switch from the SCell to the PCell based on an event associated with the PCell.5.The method of any of claims 1-4, wherein the switching pattern includes:a periodicity of the switching pattern,a bitmap including a first bit indicating the first carrier and a second bit indicating the second carrier, anda number of switches within a time duration.6.The method of any of claims 1-5, wherein the switching pattern is based on at least one of:a sliding window to limit an X number of switches within Y slots, wherein X and Y are integers,a condition that X is less Y divided by T, wherein T is a threshold, ora minimum number of slots between a switch of carriers.7.The method of any of claims 1-6, wherein the configuration indicates switching gap information including at least one of:a location of a switching gap,a duration of the switching gap,a timing advance group, TAG, ora subcarrier spacing.8.The method of any of claims 1-7, further comprising:performing, independent from the switching pattern, an additional switch between the first and second carriers based a priority rule.9.The method of claim 8, wherein the priority rule is associated with at least one of:a physical random access channel, PRACH, transmission,a UE-initiated report,a scheduling request, ora configured uplink transmission.10.The method of any of claims 1-9, further comprising:ignoring a switch associated with the switching pattern to maintain communication on a current carrier based on a triggering event.11.The method of any of claims 1-10, wherein a measurement gap overlaps with a switching gap associated with the switching pattern, the switching between the first carrier and the second carrier being based on at least one of:the measurement gap having a higher priority than the switching gap,the switching gap having a higher priority than the measurement gap,a timing occasion of the measurement gap and the switching gap,a network configured-priority, ora partial overlap between the measurement gap overlaps and the switching gap.12.The method of claim 11, wherein the switching between the first carrier and the second carrier is associated with at least one of:an active period of a cell discontinuous reception, DRX,slots within the active period of the cell DRX, oran overlap between the switching gap and a transition from the active period to an inactive period of the cell DRX.13.The method of any of claims 1-12, wherein a transmission occasion of a hybrid automatic repeat request, HARQ, feedback occurs within a HARQ window; the method further comprising:determining an additional time to process a physical downlink shared channel, PDSCH, associated with the HARQ feedback, the additional time being determined based on at least one of:a duration of a switching gap,the configuration, ora UE capability report.14.The method any of claims 1-13, further comprising at least one of:flushing a data buffer,maintaining the data buffer,flushing a hybrid automatic repeat request, HARQ, buffer,maintaining the HARQ buffer,resetting a timer,continue running the timer,dropping a buffer status report, BSR,maintaining the BSR,dropping a delay status report, DSR,maintaining the DSR,maintaining a timing alignment timer, TAT,stopping the TAT,maintaining a timer associated with configured grant-physical uplink shared channel, CG-PUSCH, occasions, orsharing hybrid automatic repeat request, HARQ, processes across the first carrier and the second carrier.15.The method of any of claims 1-14, further comprising:transmitting (503) , to the network entity (104) , UE capability indicating support for at least one of:a value of X for a number of switches within the time duration,a value of Y for the time duration,a periodicity of the switching pattern,a maximum number of switches within a transmission of a synchronization signal block, SSB,a maximum number of switches within a transmission of a tracking reference signal, TRS,a maximum number of switches within a measurement gap,a maximum number of switches within slots during an active period of a cell discontinuous reception, DRX,a maximum number of a hybrid automatic repeat request, HARQ, feedback associated with the first carrier and the second carrier,a duration of the switching gap,a minimum number of slots between a switch of carriers, oran additional time to process a physical downlink shared channel, PDSCH, associated with the HARQ feedback.16.A method of wireless communication at a network entity (104) , comprising:transmitting (505) , to a user equipment, UE, (102) , a configuration indicating a switching pattern for switching between a first carrier and a second carrier based on a time window having a limited number of switches associated with the switching pattern; andcommunicating (527) , with the UE (102) and based on the switching pattern, on one of the first carrier or the second carrier.17.The method of claim 16, wherein the first carrier includes at least one of: a frequency division duplex, FDD, carrier, a time division duplex, TDD, carrier, a supplementary downlink, SDL, carrier, or a supplementary uplink, SUL, carrier; wherein the second carrier includes at least one of: a FDD carrier, a TDD carrier, a SDL carrier, or a SUL carrier; wherein the first carrier is different from the second carrier.18.The method of any of claims 16-17, wherein the switching pattern is based on at least one of:a sliding window to limit an X number of switches within Y slots, wherein X and Y are integers,a condition that X is less Y divided by T, wherein T is a threshold, ora minimum number of slots between a switch of carriers.19.The method of any of claim 16-18, further comprisingreceiving (503) , from the UE (102) , UE capability indicating support for at least one of:a value of X for a number of switches within a time duration,a value of Y for the time duration,a periodicity of the switching pattern,a maximum number of switches within a transmission of a synchronization signal block, SSB,a maximum number of switches within a transmission of a tracking reference signal, TRS,a maximum number of switches within a measurement gap,a maximum number of switches within slots during an active period of a cell discontinuous reception, DRX,a maximum number of a hybrid automatic repeat request, HARQ, feedback associated with the first carriier and the second carrier,a duration of the switching gap,a minimum number of slots between a switch of carriers, oran additional time to process a physical downlink shared channel, PDSCH, associated with the HARQ feedback.20.An apparatus for wireless communication comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-19.
