Cell switching for measurement gap activation
Cell switching during measurement gaps in wireless communication systems addresses inefficiencies and latency by allowing uplink and downlink transmissions on a secondary cell, improving data communication efficiency.
Patent Information
- Application Number
- PCT/CN2024/075198
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-02-01
- Publication Date
- 2025-08-07
AI Technical Summary
Wireless communication systems face inefficiencies and latency due to measurement gaps that prevent uplink and downlink transmissions during feedback message exchanges, particularly in scenarios where uplink or downlink transmissions overlap with measurement gaps, leading to delayed feedback and retransmissions.
A user equipment (UE) is triggered to perform a cell switch from a first cell to a second cell during measurement gap occasions, allowing uplink or downlink transmissions to occur on the second cell, facilitated by control messages indicating measurement gap activation and cell switch instructions, which may include power or pathloss offsets.
This approach reduces latency and enhances communication efficiency by enabling uplink and downlink signaling during measurement gaps, thereby meeting latency and performance metrics.
Smart Images

Figure CN2024075198_07082025_PF_FP_ABST
Abstract
Description
CELL SWITCHING FOR MEASUREMENT GAP ACTIVATION
[0001] FIELD OF TECHNOLOGY
[0002] The following relates to wireless communications, including cell switching for measurement gap activation.BACKGROUND
[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM) . A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE) .SUMMARY
[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support cell switching for measurement gap activation. A user equipment (UE) may be triggered to perform a cell switch from a first cell to a second cell based on an activation of one or more measurement gap occasions associated with the first cell. For example, when an uplink or a downlink transmission at least partially overlaps (e.g., collides) with a measurement gap, the UE may switch cells to communicate the uplink or downlink transmission on another cell during the measurement gap occasions. Here, the UE may communicate with the network entity (e.g., transmit uplink signaling, receive downlink signaling) during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. In some examples, the UE may receive a downlink control message indicating both an activation of measurement gap occasions on a first cell (e.g., a serving cell, a primary cell (PCell) ) and an indication of the cell switch to switch from the first cell to the second cell (e.g., a target cell, a secondary cell (SCell) ) for communicating the uplink message. In other examples, the measurement gap activation and the cell switch indication may be received by the UE via different control messages.
[0005] In some examples, the indication for the cell switch may be included in a UE-specific downlink control information (DCI) or group common DCI for a group of UEs including the UE. In some examples, the UE may be configured by the network entity to select the second cell for performing the cell switch in accordance with a rule, where the rule indicates an order of one or more respective cell indices (e.g., a priority) to use for performing the cell switch. In some examples, the UE may receive a control message indicating a target cell (e.g., a cell index) to use for the second cell. In some examples, the UE may receive a control message indicating a power control offset, a pathloss offset, or both, to apply to the uplink message for the cell switch. The UE performing the cell switch in order to communicate the uplink message via the second cell during the measurement gap of the first cell may reduce latencies otherwise associated with waiting for the measurement gap to finish before communicating the uplink message via the first cell.
[0006] A method for wireless communications by a UE is described. The method may include receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell, performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions, and communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0007] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell, perform a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions, and communicate with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0008] Another UE for wireless communications is described. The UE may include means for receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell, means for performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions, and means for communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0009] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell, perform a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions, and communicate with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0010] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the cell switching indication via the first control message, where the cell switch may be based on receiving the first control message.
[0011] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, one or more bit fields of the first control message includes the cell switching indication and an indication of a cell index corresponding to the second cell.
[0012] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the one or more bit fields include one or more reserved bits.
[0013] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first control message includes a group-common DCI or a UE-specific DCI.
[0014] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a second control message different from the first control message, the second control message including the cell switching indication, where the cell switch may be based on receiving the second control message.
[0015] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for selecting the second cell for performing the cell switch in accordance with a rule, the rule indicating an order of one or more respective cell indices to use for performing the cell switch.
[0016] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a third control message indicating an updated rule that may be different from the rule and selecting the second cell for performing the cell switch in accordance with the updated rule.
[0017] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the third control message includes a medium access control-control element or DCI.
[0018] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a fourth control message indicating a cell index to use for the second cell and selecting, in response to the activation of the one or more measurement gap occasions, the second cell for performing the cell switch based on the cell index.
[0019] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, communicating with the network entity may include operations, features, means, or instructions for transmitting one or more uplink messages to the network entity via the second cell during at least the portion of the one or more measurement gap occasions associated with the first cell, where a power control offset or a pathloss offset, or both, applied to the one or more uplink messages may be based on performing the cell switch from the first cell to the second cell.
[0020] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first control message indicates the power control offset, the pathloss offset, or both.
[0021] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving a fifth control message indicating the power control offset, the pathloss offset, or both.BRIEF DESCRIPTION OF THE DRAWINGS
[0022] FIG. 1 shows an example of a wireless communications system that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.
[0023] FIG. 2 shows an example of a wireless communications system that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.
[0024] FIG. 3 shows an example of a process flow that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.
[0025] FIGs. 4 and 5 show block diagrams of devices that support cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.
[0026] FIG. 6 shows a block diagram of a communications manager that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.
[0027] FIG. 7 shows a diagram of a system including a device that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.
[0028] FIGs. 8 through 10 show flowcharts illustrating methods that support cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION
[0029] In some wireless communications systems, a user equipment (UE) may suspend communication with a network entity during a measurement gap occasion. For example, measurement gap occasions may prevent the UE may from communicate uplink messages to the network entity or receive downlink messages from the network entity during each of the measurement gap occasion. Similarly, feedback messages (e.g., including hybrid automatic repeat request (HARQ) , acknowledgment (ACK) / negative acknowledgment (NACK) messages) and retransmissions may be limited due to measurement gaps. For instance, the UE may receive data, such as extended reality (XR) data, in a downlink message from the network entity via a first cell. After receiving the data, the UE may communicate feedback data in an uplink message to the network entity via the first cell. However, the UE may not communicate the feedback data to the network entity during a measurement gap occasion, and the UE may wait for the measurement gap occasion to complete before communicating the feedback data, resulting in latency and inefficiencies. The feedback latencies associated with the delayed uplink message may further result in transmission (e.g., retransmission) latencies of a downlink message (e.g., a retransmission) that is sent to the UE in response to the feedback from the UE.
[0030] As described herein, techniques may be used to reduce latency and enable efficient communication of uplink and downlink signaling for the UE. For example, the UE may be triggered to perform a cell switch from a first cell to a second cell based on an activation of one or more measurement gap occasions associated with the first cell. For example, when an uplink or a downlink transmission at least partially overlaps (e.g., collides) with a measurement gap, the UE may switch cells to communicate the uplink or downlink transmission on another cell during the measurement gap occasions. In such examples, the UE may communicate with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. In some examples, the UE may receive a downlink control message (e.g., downlink control information (DCI) indicating both an activation of measurement gap occasions on a first cell (e.g., a serving cell, primary cell (PCell) ) along with an indication of the cell switch to switch from the first cell to the second cell (e.g., a target cell, secondary (SCell) ) for communicating the uplink message. In other examples, the measurement gap activation and the cell switch indication may each be received by the UE via different control messages.
[0031] In some examples, the indication for the cell switch may be included in a UE-specific DCI or group common DCI for a group of UEs including the UE. In some examples, the UE may be configured by the network entity to select the second cell for performing the cell switch in accordance with a rule, where the rule indicates an order of one or more respective cell indices (e.g., a priority) to use for performing the cell switch. In some examples, the UE may receive a control message indicating an explicit indication of a target cell (e.g., identified by a cell index) to use for the second cell when switching cells. In some examples, the UE may receive a control message indicating a power control offset, a pathloss offset, or both, to apply to the uplink message for the cell switch. The techniques for performing the cell switch to communicate the uplink message via the second cell during the measurement gap of the first cell may reduce latencies otherwise associated with waiting for the measurement gap to finish before communicating the messages via the first cell, thereby enabling data communications to meet some latency and performance metrics, among other advantages.
[0032] Aspects of the disclosure are initially described in the context of wireless communications systems. Aspects of the disclosure are further illustrated by and described with reference to process flows, apparatus diagrams, system diagrams, and flowcharts that relate to cell switching for measurement gap activation.
[0033] FIG. 1 shows an example of a wireless communications system 100 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105) , one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.
[0034] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link (s) 125 (e.g., a radio frequency (RF) access link) . For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link (s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs) .
[0035] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some examples of UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105) , as shown in FIG. 1.
[0036] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein) , a UE 115 (e.g., any UE described herein) , a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.
[0037] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link (s) 120 (e.g., in accordance with an S1, N2, N3, or other interface protocol) . In some examples, network entities 105 may communicate with one another via backhaul communication link (s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130) . In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol) , or any combination thereof. The backhaul communication link (s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link) , among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.
[0038] One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB) , a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB) , a 5G NB, a next-generation eNB (ng-eNB) , a Home NodeB, a Home eNodeB, or other suitable terminology) . In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140) .
[0039] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) , which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105) , such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) . For example, a network entity 105 may include one or more of a central unit (CU) , such as a CU 160, a distributed unit (DU) , such as a DU 165, a radio unit (RU) , such as an RU 170, a RAN Intelligent Controller (RIC) , such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) . One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations) . In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
[0040] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3) , layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) . The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs) , or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (L1) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170) . In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170) . A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., F1, F1-c, F1-u) , and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface) . In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.
[0041] In some wireless communications systems (e.g., the wireless communications system 100) , infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130) . In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node (s) 104) may be partially controlled by each other. The IAB node (s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station) . The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node (s) 104) via supported access and backhaul links (e.g., backhaul communication link (s) 120) . IAB node (s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node (s) 104 used for access via the DU 165 of the IAB node (s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT) ) . In some examples, the IAB node (s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node (s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream) . In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node (s) 104 or components of the IAB node (s) 104) may be configured to operate according to the techniques described herein.
[0042] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180) .
[0043] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA) , a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.
[0044] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.
[0045] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link (s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link (s) 125. For example, a carrier used for the communication link (s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP) ) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR) . Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information) , control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting, ” “receiving, ” or “communicating, ” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105) .
[0046] In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN) ) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non-standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT) .
[0047] The communication link (s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode) .
[0048] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz) ) . Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.
[0049] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM) ) . In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both) , such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam) , and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.
[0050] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.
[0051] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts=1 / (Δfmax·Nf) seconds, for which Δfmax may represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms) ) . Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023) .
[0052] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period) . In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Nf) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.
[0053] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI) . In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs) ) .
[0054] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET) ) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs) ) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE) .
[0055] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID) , a virtual cell identifier (VCID) ) . In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.
[0056] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG) , the UEs 115 associated with users in a home or office) . A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.
[0057] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT) , enhanced mobile broadband (eMBB) ) that may provide access for different types of devices.
[0058] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105) . In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105) . The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.
[0059] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.
[0060] Some UEs 115, such as MTC or IoT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication) . M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.
[0061] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently) . In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications) , or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs) ) within a carrier, within a guard-band of a carrier, or outside of a carrier.
[0062] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC) . The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.
[0063] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P) , D2D, or sidelink protocol) . In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170) , which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1: M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.
[0064] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC) , which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management function (AMF) ) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a Packet Data Network (PDN) gateway (P-GW) , or a user plane function (UPF) ) . The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet, Intranet (s) , an IP Multimedia Subsystem (IMS) , or a Packet-Switched Streaming Service.
[0065] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz) . Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.
[0066] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) , also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170) , and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.
[0067] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA) , LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA) . Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.
[0068] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.
[0069] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation) .
[0070] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A medium access control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.
[0071] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link (s) 125, a D2D communication link 135) . HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC) ) , forward error correction (FEC) , and retransmission (e.g., automatic repeat request (ARQ) ) . HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal-to-noise conditions) . In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.
[0072] In some examples, the UE 115 may suspend communication with the network entity 105 during a measurement gap occasion. For example, the UE 115 may receive data in a downlink message from the network entity 105 via a first cell and after receiving the data, the UE 115 may communicate feedback data in an uplink message to the network entity 105 via the first cell. However, the UE 115 may not communicate the feedback data to the network entity 105 during a measurement gap occasion and the UE 115 may wait for the measurement gap occasion to complete before communicating the feedback data, resulting in latencies.
[0073] The wireless communications system 100 may support one or more techniques for cell switching based on a dynamic activation of measurement gaps. For example, to reduce or minimize system latency, as discussed herein, the UE 115 may be triggered to perform a cell switch from a first cell to a second cell based on an activation of one or more measurement gap occasions associated with the first cell. For example, when an uplink or a downlink transmission at least partially overlaps (e.g., collides) with a measurement gap, the UE 115 may switch cells to communicate the uplink or downlink transmission on another cell, such as the second cell, during the measurement gap occasions. By switching to the second cell, the UE 115 may communicate with the network entity 105 during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. In some examples, the UE 115 may receive a downlink control message indicating both an activation of measurement gap occasions on a first cell (e.g., a serving cell / PCell) along with an indication of the cell switch to switch from the first cell to the second cell (e.g., a target cell / SCell) for communicating the uplink message. In other examples, the measurement gap activation and the cell switch indication may be received by the UE 115 via different control messages.
[0074] In some examples, the indication for the cell switch may be included in a UE-specific DCI or group common DCI for a group of UEs 115 including the UE 115. In some examples, the UE 115 may be configured by the network entity 105 to select the second cell for performing the cell switch in accordance with a rule, where the rule indicates an order of one or more respective cell indices (e.g., a priority) to use for performing the cell switch. In some examples, the UE 115 may receive a control message indicating a target cell (e.g., a cell index) to use for the second cell. In some examples, the UE 115 may receive a control message indicating a power control offset, a pathloss offset, or both, to apply to the uplink message for the cell switch. The UE 115 performing the cell switch in order to communicate the uplink message via the second cell during the measurement gap of the first cell may reduce latencies otherwise associated with waiting for the measurement gap to finish before communicating the uplink message via the first cell.
[0075] FIG. 2 shows an example of a wireless communications system 200 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement aspects of or may be implemented by aspects of the wireless communications system 100. For example, the wireless communications system 200 includes a UE 115-a and a network entity 105-a, which may be examples of a UE 115 and a network entity 105 described with respect to FIG. 1.
[0076] In some examples, the UE 115-a may suspend communication with the network entity 105 during a measurement gap occasion. In some cases, the measurement gap occasion may have a relatively higher priority than other data traffic in the wireless communications system 200. A measurement gap periodicity of the measurement occasion, which may include a period of 20 milliseconds (ms) , 40 ms, 80 ms, 160 ms, and so forth, may not be aligned with data periodicity (e.g., in frames per second (fps) or hertz (Hz) ) of a data traffic occasion, such as for communicating XR data. In some cases, overlapping (e.g., confliction, collision) of a measurement gap occasion and a data traffic occasion (e.g., data traffic transmission period) may not be avoided by adjusting offset values (e.g., start and end times of the measurement gap occasions and data traffic occasions) .
[0077] In some examples, the collision of the measurement gap occasion and data traffic occasion may cause a relatively frequent (and significant) and increasing occurrences of packet delay in wireless communications, resulting in inability to meet a packet delay budget (PDB) condition, such as a PDB condition of 99%packets for an XR application. In some cases, when a measurement gap occasion is configured with discontinuous reception (DRX) , a DRX inactivity timer or an on-duration timer may expire during a measurement gap occasion, causing the UE 115-a to enter the inactivity state during data traffic occasion. The UE 115-a may not receive data while in the inactivity state.
[0078] To reduce the collision of a measurement gap occasion and a data traffic occasion, dynamic activation and / or deactivation of measurement gap occasions, configuring a priority between the data traffic occasion and the measurement gap occasion, and / or a periodic, semi-persistent, or aperiodic measurement gap occasions may be implemented. Activating and / or deactivating the measurement gap occasion may involve the network entity 105-a outputting a dynamic indication (e.g., via MAC control element (MAC-CE) or DCI) with bitmap to the UE 115-a, to cause the UE 115-ato skip the measurement gap occasion. The configurable priority between the data traffic occasion and the measurement gap occasion may include the use of a RRC information element (IE) for configuring a priority between a data traffic occasion and the measurement gap occasion. The network entity 105-a may determine the priority of measurement gap occasion over the data traffic occasion based on a 5G quality of service (QoS) Identifier (5QI) as indicated from the core network. The periodic, semi-persistent, or aperiodic measurement gap occasion configuration may involve irregular gap occasions configured in accordance with (e.g., based on or around) bursts of the data traffic occasions (e.g., XR bursts) .
[0079] In some examples, in a physical uplink control channel (PUCCH) cell switch, the PUCCH may be transmitted on a PCell (e.g., first cell or serving cell) in a PUCCH cell group. For uplink carrier aggregation with time division duplex including an uplink and downlink pattern (e.g., dividing and alternating time for uplink and downlink) , using an earlier uplink slot (e.g., U / S slot) on a SCell (e.g., second cell) to transmit the PUCCH may significantly reduce PUCCH feedback latency. For example, the feedback message may include a HARQ acknowledgment (HARQ-ACK) or a negative acknowledgment (HARQ-NACK) that may be transmitted by the UE 115-aand received by the network entity 105-a earlier with respect than without using the second cell. Accordingly, in some examples, a PUCCH cell switch to transmit PUCCH on either PCell or (one additional) SCell may be implemented to reduce feedback latency. However, in some examples, the simultaneous use of both PCell and SCell may not be supported.
[0080] Such TDD patterns may lead to extra or additional delays, thereby affecting both latency and reliability, which may be key performance indicators (KPIs) for data traffic (e.g., for XR data) . To reduce the retransmission time and delays in TDD, transmissions (e.g., uplink and / or downlink) may occur on different component carriers (e.g., different frequencies) . For example, the nearest uplink slot on any carrier for an uplink transmission and the nearest downlink slot on any carrier for a downlink transmission may be used to reduce latency. An initial HARQ transmission may be sent on one component carrier and an associated HARQ retransmission may be sent on another component carrier. In other words, if a first physical downlink shared channel (PDSCH) or a physical uplink shared channel (PUSCH) transmission is transmitted on a first component carrier (e.g., CC1) , the retransmission of the PDSCH or the PUSCH may be transmitted on a second component carrier (e.g., CC2) .
[0081] Measurement gap occasions may collide with a downlink and / or uplink transmission occasion. In some examples, the collision between the measurement gap occasions and the downlink and / or uplink transmission occasions involve control signaling, PUSCH, or the PDSCH in the uplink and / or downlink transmission occasions. The collision may result in failed PDB conditions, for example, for an XR service. Accordingly, for XR traffic data or other data, different component carriers or a second cell group for transmission and retransmissions may be used to reduce unsuccessful PDB conditions when measurement gap occasions are activated for the PCell or master cell group (MCG) .
[0082] In some examples, when the network entity 105-a activates a measurement gap occasion for the UE 115-a, the UE 115-a may not transmit the PUSCH, PUCCH, or sounding reference signal (SRS) during the measurement gap occasion and / or may not receive the PDSCH, PDCCH, or channel state information reference signal (CSI-RS) during the measurement gap occasion, resulting in relatively increased latency for XR applications.
[0083] In some examples, the network entity 105-a may enable dynamic measurement gap occasion activation in carrier aggregation schemes. For example, when one or more measurement gap occasions are dynamically activated in one component carrier, such that the UE 115-a may not transmit the PUSCH, PUCCH, or the SRS in the component carrier, the network entity 105-a may indicate to the UE 115-a to switch to another component carrier to transmit the PUSCH, PUCCH, or the SRS. In some examples, UE 115-a may be configured via RRC signaling to indicate which component carriers are candidates for transmitting uplink messages and which component carriers are not candidates, for example, to transmit uplink control information (UCI) .
[0084] As discussed herein, the UE 115-a may be triggered to perform a cell switch from a first cell to a second cell based on an activation of one or more measurement gap occasions associated with the first cell so that the UE 115-a may communicate with the network entity 105-a during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. For example, the network entity 105-a may communicate with the UE 115-a using a communication link 125. In some examples, the communication link 125 may include a first channel 225-a for transmitting data from the UE 115-a to the network entity 105-a and a second channel 225-b for transmitting data from the network entity 105-a to the UE 115-a. The communication link 125 may be an example of an NR or LTE link between the UE 115-a and the network entity 105-a. The communication link 125 may include a bi-directional link that enables both uplink and downlink communications, for example, via the channels 225.
[0085] For example, the UE 115-a may transmit uplink messages 245 (e.g., uplink transmissions) , such as uplink control signals or uplink data signals, to the network entity 105-a using the first channel 225-a (e.g., of the communication link 125) and the network entity 105-a may transmit downlink messages 250 (e.g., downlink transmissions) , such as downlink control signals or downlink data signals, to the UE 115-a using the second channel 225-b (e.g., of the communication link 125) . In some examples, the downlink messages 250 may be part of control signaling transmitted from the network entity 105-a. Using a cell switch, the UE 115-a may communicate an uplink message 245 to the network entity 105-a via a second cell during at least a portion of a measurement gap on the first cell. In some examples, the multiple messages outputted via multiple downlink messages 250, respectively, may be outputted in a single downlink message 250.
[0086] In an example, the network entity 105-a may output a first downlink message 250-a, which includes a DCI 255 indicating a measurement gap occasion 260 activation (e.g., activating one or more measurement gaps occasions) on a serving cell, such as a PCell associated with a primary component carrier (PCC) 270. In the first downlink message 250-a, the network entity 105-a may explicitly indicate to the UE 115-a to cell switch PUCCH or schedule a cross carrier HARQ retransmission (e.g., downlink or uplink) during the measurement gap occasion 260 to reduce latency. That is, the same DCI 255 that activates the measurement gap occasion 260 also indicates the cell switch for cross carrier for cross-carrier scheduling. For example, when the measurement gap occasion 260 is scheduled using the PCC 270 based on the DCI 255, data traffic transmission 265 (e.g., PUCCH or HARQ retransmission) is scheduled using a second component carrier 275 (SCC) (e.g., component carrier that is different from the PCC 270) based on the same DCI 255. Accordingly, the first downlink message 250-amay include a cell switching indication within the same dynamic measurement gap occasion 260 activation via DCI 255. In some examples, one or more new bit fields may be defined in the DCI 255 to indicate the cell switch and a particular cell. The fields may include PDSCH reception (k0) , PUSCH transmission (k2) , HARQ feedback transmission over PUCCH (k1) , PUCCH resource indicator (PRI) field, redundancy version (RV) , and cell switching-related parameter fields. In some examples, the DCI 255 may include reserved bits to indicate cell switching and a particular cell. In some examples, the DCI 255 may use existing bits field otherwise used for other functions, to indicate the cell switching and particular cell.
[0087] The DCI 255 may be used to activate the measurement gap occasion 260 in the PCC 270, as well as to indicate a cell switch and a specific component carrier (e.g., the second component carrier 275, an SCC) for uplink transmissions, for example, to reduce the chance of or avoid a collision between the measurement gap occasion 260 in the PCC 270 and an uplink transmission in the PCC 270 that may otherwise occur without the cell switch.
[0088] In some examples, the network entity 105-a may transmit a second downlink message 250-b, which may be a UE-specific DCI or a group-common DCI. The UE-specific DCI or the group-common DCI of the second downlink message 250-b may indicate the cell switch. For example, in this example, the indication of the measurement gap occasion may be transmitted to the UE 115-a in the first downlink message 250-awhile the indication of the cell switch is transmitted to the UE 115-a in the second downlink message 250-b. In such examples, the corresponding fields, such as k2, may be based on the target cell (e.g., the SCell) and not on the serving cell (e.g., the PCell) . As such, the UE 115-a may transmit feedback and / or other messages in accordance with the parameters signaled in the DCI while communicating on multiple component carriers.
[0089] In some examples, the network entity 105-a may transmit a third downlink message 250-c, which may include an indication of a rule (e.g., an implicit rule) . The network entity 105-a may configure the UE 115-a with the rule to enable the UE 115-ato determine the target cell for the cell switch. In such examples, the network entity 105-a may configure a default order of component carriers for the UE 115-a via RRC signaling (e.g., RRCReconfigurations in the third downlink message 250-c) , where the default order may be used by the UE 115-a when selecting which cell to switch to as part of the cell switching procedure. The rule may be based on cell indices, where the rule, for example, may include a correlation between decreasing index of a component carrier to increasing priority for using in the cell switch (e.g., the lower the index of component carrier is, then the higher the priority for the component carrier to be used for cell switching) . Accordingly, the UE 115-a may be configured to perform cell switching using the component carrier having the relatively lowest index since the lowest index component carrier may have the relatively greatest priority. The UE 115-amay switch to other target cells (e.g., other SCells) according to the rule, for example, when the PCell is dynamically indicated to activate measurement gap occasions. In some examples, the network entity 105-a may update the rule (e.g., update one or more parameters associated with the rule) via MAC-CE or DCI signaling.
[0090] In some examples, the network entity 105-a may configure the UE 115-awith one component carrier candidate (e.g., via the third downlink message 250-c) , such as component carrier Y, for example, using RRC signaling. The network entity 105-amay configure the UE 115-a to use the component carrier Y along with configuring the UE 115-a with the measurement gap occasions. In such examples, when the network entity 105-a dynamically activates the measurement gap occasion in the PCC or the SCC, the UE 115-a may autonomously switch to the configured component carrier Y to transmit overlapping stringent data or the controlling signaling. The dynamic indication (e.g., the third downlink message 250-c) to activate the measurement gap occasion may also indicate the cell switching.
[0091] In some examples, the path loss might be different (e.g., very different) on a target component carrier than the serving component carrier. As such, link adaptation for the network entity 105-a may be difficult, for example, to control the block error rate (BLER) for PUSCH across an initial transmission (e.g., using the serving component carrier) and the retransmission (e.g., using the target component carrier) . To reduce the BLER between the component carriers, the network entity 105-a may indicate a pathloss or power control offset between the two component carriers where the UE 115-a applies the offset when switching component carriers for PUSCH retransmission. In some examples, the power control offset between the component carriers may be different than the original power configuration for component carriers (e.g., for the initial PUSCH transmission) . For example, the offset may be applied to the retransmission on different component carriers. In some examples, the offset may be configured by the network entity 105-a along with the dynamic indication DCI for measurement gap occasions. In some examples, a specific DCI may indicate the offset to the UE 115-a for component carrier switching (e.g., cell switching) . Using the cell switching techniques described herein, the UE 115-a may communicate with the network entity 105-a during at least a portion of the measurement gap occasions via the second cell or SCC based on the cell switch, reducing latencies otherwise associated with providing uplink messages (e.g., HARQ feedback) to the network entity 105-a via the first cell or PCC (e.g., that includes the measurement gap occasions) .
[0092] FIG. 3 shows an example of a process flow 300 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The process flow 300 may implement aspects of or may be implemented by aspects of the wireless communications systems 100 and 200. For example, the process flow 300 may include a UE 115-c, which may be an example of a UE 115 as described herein. The process flow 300 may include a network entity 105-c, which may be an example of a network entity 105 as described herein. In the following description of the process flow 300, the operations performed by the UE 115-c and the network entity 105-c may be performed in different orders or at different times than the exemplary order shown. Some operations may also be omitted from the process flow 300, or other operations may be added to the process flow 300. Further, while operations in the process flow 300 are illustrated as being performed by the UE 115-c and the network entity 105-c, the examples herein are not to be construed as limiting, as the described features may be associated with any quantity of different devices.
[0093] At 305, the UE 115-c may receive a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. In some examples, the UE 115-c may receive the cell switching indication via the first control message. The cell switch may be based at least in part on receiving the first control message. One or more bit fields of the first control message may include the cell switching indication and an indication of a cell index corresponding to the second cell. The one or more bit fields may include one or more reserved bits. In some examples, the first control message may include a group-common DCI or a UE-specific DCI.
[0094] In some examples, the UE 115-a may receive a second control message different from the first control message. At 310, the second control message may include the cell switching indication, where the cell switch is based on receiving the second control message. In some examples, the UE 115-a may select the second cell for performing the cell switch in accordance with a rule. The rule may indicate an order of one or more respective cell indices to use for performing the cell switch. In some examples, the UE 115-a may receive a third control message indicating an updated rule that is different from the rule. The UE 115-a may select the second cell for performing the cell switch in accordance with the updated rule. The third control message may include a MAC-CE or DCI.
[0095] In some examples, the UE 115-a may receive a fourth control message indicating a cell index to use for the second cell. The UE 115-a may select, in response to the activation of the one or more measurement gap occasions, the second cell for performing the cell switch based on the cell index. In some examples, the UE 115-amay receive a fifth control message indicating a power control offset, the pathloss offset, or both.
[0096] At 315, the UE 115-a may perform a cell switch from the first cell to a second cell that is different from the first cell. The cell switch may be triggered via a cell switching indication from the network entity 105-a and may be associated with the activation of the one or more measurement gap occasions.
[0097] At 320, the UE 115-a may communicate with the network entity 105-aduring at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. In some examples, the UE 115-a may transmit one or more uplink messages to the network entity 105-a via the second cell during at least the portion of the one or more measurement gap occasions associated with the first cell. A power control offset or a pathloss offset, or both, may be applied to the one or more uplink messages based on performing the cell switch from the first cell to the second cell. In such examples, the first control message may indicate the power control offset, the pathloss offset, or both.
[0098] FIG. 4 shows a block diagram 400 of a device 405 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The device 405 may be an example of aspects of a UE 115 as described herein. The device 405 may include a receiver 410, a transmitter 415, and a communications manager 420. The device 405, or one or more components of the device 405 (e.g., the receiver 410, the transmitter 415, the communications manager 420) , may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
[0099] The receiver 410 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cell switching for measurement gap activation) . Information may be passed on to other components of the device 405. The receiver 410 may utilize a single antenna or a set of multiple antennas.
[0100] The transmitter 415 may provide a means for transmitting signals generated by other components of the device 405. For example, the transmitter 415 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cell switching for measurement gap activation) . In some examples, the transmitter 415 may be co-located with a receiver 410 in a transceiver module. The transmitter 415 may utilize a single antenna or a set of multiple antennas.
[0101] The communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be examples of means for performing various aspects of cell switching for measurement gap activation as described herein. For example, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be capable of performing one or more of the functions described herein.
[0102] In some examples, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) . The hardware may include at least one of a processor, a digital signal processor (DSP) , a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory) .
[0103] Additionally, or alternatively, the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code) . If implemented in code executed by at least one processor, the functions of the communications manager 420, the receiver 410, the transmitter 415, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure) .
[0104] In some examples, the communications manager 420 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 410, the transmitter 415, or both. For example, the communications manager 420 may receive information from the receiver 410, send information to the transmitter 415, or be integrated in combination with the receiver 410, the transmitter 415, or both to obtain information, output information, or perform various other operations as described herein.
[0105] The communications manager 420 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 420 is capable of, configured to, or operable to support a means for receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The communications manager 420 is capable of, configured to, or operable to support a means for performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions. The communications manager 420 is capable of, configured to, or operable to support a means for communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0106] By including or configuring the communications manager 420 in accordance with examples as described herein, the device 405 (e.g., at least one processor controlling or otherwise coupled with the receiver 410, the transmitter 415, the communications manager 420, or a combination thereof) may support techniques for reducing latencies associated with uplink or downlink messages communicated via a cell or a component carrier during a measurement occasion on the cell or component carrier.
[0107] FIG. 5 shows a block diagram 500 of a device 505 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a device 405 or a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520) , may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses) .
[0108] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cell switching for measurement gap activation) . Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.
[0109] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to cell switching for measurement gap activation) . In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.
[0110] The device 505, or various components thereof, may be an example of means for performing various aspects of cell switching for measurement gap activation as described herein. For example, the communications manager 520 may include a message communication manager 525, a cell switch manager 530, or any combination thereof. The communications manager 520 may be an example of aspects of a communications manager 420 as described herein. In some examples, the communications manager 520, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitter 515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.
[0111] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. The message communication manager 525 is capable of, configured to, or operable to support a means for receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The cell switch manager 530 is capable of, configured to, or operable to support a means for performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions. The message communication manager 525 is capable of, configured to, or operable to support a means for communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0112] FIG. 6 shows a block diagram 600 of a communications manager 620 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The communications manager 620 may be an example of aspects of a communications manager 420, a communications manager 520, or both, as described herein. The communications manager 620, or various components thereof, may be an example of means for performing various aspects of cell switching for measurement gap activation as described herein. For example, the communications manager 620 may include a message communication manager 625 a cell switch manager 630, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories) , may communicate, directly or indirectly, with one another (e.g., via one or more buses) .
[0113] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The message communication manager 625 is capable of, configured to, or operable to support a means for receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The cell switch manager 630 is capable of, configured to, or operable to support a means for performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions. In some examples, the message communication manager 625 is capable of, configured to, or operable to support a means for communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0114] In some examples, the message communication manager 625 is capable of, configured to, or operable to support a means for receiving the cell switching indication via the first control message, where the cell switch is based on receiving the first control message.
[0115] In some examples, one or more bit fields of the first control message includes the cell switching indication and an indication of a cell index corresponding to the second cell.
[0116] In some examples, the one or more bit fields include one or more reserved bits.
[0117] In some examples, the first control message includes a group-common DCI or a UE-specific DCI.
[0118] In some examples, the message communication manager 625 is capable of, configured to, or operable to support a means for receiving a second control message different from the first control message, the second control message including the cell switching indication, where the cell switch is based on receiving the second control message.
[0119] In some examples, the cell switch manager 630 is capable of, configured to, or operable to support a means for selecting the second cell for performing the cell switch in accordance with a rule, the rule indicating an order of one or more respective cell indices to use for performing the cell switch.
[0120] In some examples, the message communication manager 625 is capable of, configured to, or operable to support a means for receiving a third control message indicating an updated rule that is different from the rule. In some examples, the cell switch manager 630 is capable of, configured to, or operable to support a means for selecting the second cell for performing the cell switch in accordance with the updated rule. In some examples, the third control message includes a MAC-CE or DCI.
[0121] In some examples, the message communication manager 625 is capable of, configured to, or operable to support a means for receiving a fourth control message indicating a cell index to use for the second cell. In some examples, the cell switch manager 630 is capable of, configured to, or operable to support a means for selecting, in response to the activation of the one or more measurement gap occasions, the second cell for performing the cell switch based on the cell index.
[0122] In some examples, to support communicating with the network entity, the message communication manager 625 is capable of, configured to, or operable to support a means for transmitting one or more uplink messages to the network entity via the second cell during at least the portion of the one or more measurement gap occasions associated with the first cell, where a power control offset or a pathloss offset, or both, applied to the one or more uplink messages is based on performing the cell switch from the first cell to the second cell. In some examples, the first control message indicates the power control offset, the pathloss offset, or both.
[0123] In some examples, the message communication manager 625 is capable of, configured to, or operable to support a means for receiving a fifth control message indicating the power control offset, the pathloss offset, or both.
[0124] FIG. 7 shows a diagram of a system 700 including a device 705 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The device 705 may be an example of or include components of a device 405, a device 505, or a UE 115 as described herein. The device 705 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof) . The device 705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 720, an input / output (I / O) controller, such as an I / O controller 710, a transceiver 715, one or more antennas 725, at least one memory 730, code 735, and at least one processor 740. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 745) .
[0125] The I / O controller 710 may manage input and output signals for the device 705. The I / O controller 710 may also manage peripherals not integrated into the device 705. In some cases, the I / O controller 710 may represent a physical connection or port to an external peripheral. In some cases, the I / O controller 710 may utilize an operating system such as or another known operating system. Additionally, or alternatively, the I / O controller 710 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I / O controller 710 may be implemented as part of one or more processors, such as the at least one processor 740. In some cases, a user may interact with the device 705 via the I / O controller 710 or via hardware components controlled by the I / O controller 710.
[0126] In some cases, the device 705 may include a single antenna. However, in some other cases, the device 705 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 715 may communicate bi-directionally via the one or more antennas 725 using wired or wireless links as described herein. For example, the transceiver 715 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 715 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 725 for transmission, and to demodulate packets received from the one or more antennas 725. The transceiver 715, or the transceiver 715 and one or more antennas 725, may be an example of a transmitter 415, a transmitter 515, a receiver 410, a receiver 510, or any combination thereof or component thereof, as described herein.
[0127] The at least one memory 730 may include random access memory (RAM) and read-only memory (ROM) . The at least one memory 730 may store computer-readable, computer-executable, or processor-executable code, such as the code 735. The code 735 may include instructions that, when executed by the at least one processor 740, cause the device 705 to perform various functions described herein. The code 735 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 735 may not be directly executable by the at least one processor 740 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 730 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
[0128] The at least one processor 740 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs) , one or more graphics processing units (GPUs) , one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs) ) , one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof) . In some cases, the at least one processor 740 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 740. The at least one processor 740 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 730) to cause the device 705 to perform various functions (e.g., functions or tasks supporting cell switching for measurement gap activation) . For example, the device 705 or a component of the device 705 may include at least one processor 740 and at least one memory 730 coupled with or to the at least one processor 740, the at least one processor 740 and the at least one memory 730 configured to perform various functions described herein. In some examples, the at least one processor 740 may include multiple processors and the at least one memory 730 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 740 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 740) and memory circuitry (which may include the at least one memory 730) ) , or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 740 or a processing system including the at least one processor 740 may be configured to, configurable to, or operable to cause the device 705 to perform one or more of the functions described herein. Further, as described herein, being “configured to, ” being “configurable to, ” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 735 (e.g., processor-executable code) stored in the at least one memory 730 or otherwise, to perform one or more of the functions described herein.
[0129] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 720 is capable of, configured to, or operable to support a means for receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The communications manager 720 is capable of, configured to, or operable to support a means for performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions. The communications manager 720 is capable of, configured to, or operable to support a means for communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch.
[0130] By including or configuring the communications manager 720 in accordance with examples as described herein, the device 705 may support techniques for reducing latencies associated with uplink or downlink messages communicated via a cell or a component carrier during a measurement occasion on the cell or component carrier.
[0131] In some examples, the communications manager 720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 715, the one or more antennas 725, or any combination thereof. Although the communications manager 720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 720 may be supported by or performed by the at least one processor 740, the at least one memory 730, the code 735, or any combination thereof. For example, the code 735 may include instructions executable by the at least one processor 740 to cause the device 705 to perform various aspects of cell switching for measurement gap activation as described herein, or the at least one processor 740 and the at least one memory 730 may be otherwise configured to, individually or collectively, perform or support such operations.
[0132] FIG. 8 shows a flowchart illustrating a method 800 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The operations of the method 800 may be implemented by a UE or its components as described herein. For example, the operations of the method 800 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
[0133] At 805, the method may include receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The operations of 805 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 805 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0134] At 810, the method may include performing a cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions. The operations of 810 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 810 may be performed by a cell switch manager 630 as described with reference to FIG. 6.
[0135] At 815, the method may include communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. The operations of 815 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 815 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0136] FIG. 9 shows a flowchart illustrating a method 900 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The operations of the method 900 may be implemented by a UE or its components as described herein. For example, the operations of the method 900 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
[0137] At 905, the method may include receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The operations of 905 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 905 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0138] At 910, the method may include receiving a cell switching indication via the first control message. The operations of 910 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 910 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0139] At 915, the method may include performing the cell switch from the first cell to a second cell that is different from the first cell, where the cell switch is triggered via the cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions, where the cell switch is based on receiving the first control message. The operations of 915 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 915 may be performed by a cell switch manager 630 as described with reference to FIG. 6.
[0140] At 920, the method may include communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. The operations of 920 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 920 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0141] FIG. 10 shows a flowchart illustrating a method 1000 that supports cell switching for measurement gap activation in accordance with one or more aspects of the present disclosure. The operations of the method 1000 may be implemented by a UE or its components as described herein. For example, the operations of the method 1000 may be performed by a UE 115 as described with reference to FIGs. 1 through 7. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.
[0142] At 1005, the method may include receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell. The operations of 1005 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0143] At 1010, the method may include selecting a second cell for performing a cell switch in accordance with a rule, the rule indicating an order of one or more respective cell indices to use for performing the cell switch. The operations of 1010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed by a cell switch manager 630 as described with reference to FIG. 6.
[0144] At 1015, the method may include performing the cell switch from the first cell to the second cell that is different from the first cell, where the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions. The operations of 1015 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed by a cell switch manager 630 as described with reference to FIG. 6.
[0145] At 1020, the method may include communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based on the cell switch. The operations of 1020 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1020 may be performed by a message communication manager 625 as described with reference to FIG. 6.
[0146] The following provides an overview of aspects of the present disclosure:
[0147] Aspect 1: A method for wireless communications at a UE, comprising: receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell; performing a cell switch from the first cell to a second cell that is different from the first cell, wherein the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions; and communicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based at least in part on the cell switch.
[0148] Aspect 2: The method of aspect 1, further comprising: receiving the cell switching indication via the first control message, wherein the cell switch is based at least in part on receiving the first control message.
[0149] Aspect 3: The method of aspect 2, wherein one or more bit fields of the first control message comprises the cell switching indication and an indication of a cell index corresponding to the second cell.
[0150] Aspect 4: The method of aspect 3, wherein the one or more bit fields comprise one or more reserved bits.
[0151] Aspect 5: The method of any of aspects 2 through 4, wherein the first control message comprises a group-common DCI or a UE-specific DCI.
[0152] Aspect 6: The method of any of aspects 1 through 5, further comprising: receiving a second control message different from the first control message, the second control message comprising the cell switching indication, wherein the cell switch is based at least in part on receiving the second control message.
[0153] Aspect 7: The method of any of aspects 1 through 6, further comprising: selecting the second cell for performing the cell switch in accordance with a rule, the rule indicating an order of one or more respective cell indices to use for performing the cell switch.
[0154] Aspect 8: The method of aspect 7, further comprising: receiving a third control message indicating an updated rule that is different from the rule; and selecting the second cell for performing the cell switch in accordance with the updated rule.
[0155] Aspect 9: The method of aspect 8, wherein the third control message comprises a MAC-CE or DCI.
[0156] Aspect 10: The method of any of aspects 1 through 9, further comprising: receiving a fourth control message indicating a cell index to use for the second cell; and selecting, in response to the activation of the one or more measurement gap occasions, the second cell for performing the cell switch based at least in part on the cell index.
[0157] Aspect 11: The method of any of aspects 1 through 10, wherein communicating with the network entity comprises: transmitting one or more uplink messages to the network entity via the second cell during at least the portion of the one or more measurement gap occasions associated with the first cell, wherein a power control offset or a pathloss offset, or both, applied to the one or more uplink messages is based at least in part on performing the cell switch from the first cell to the second cell.
[0158] Aspect 12: The method of aspect 11, wherein the first control message indicates the power control offset, the pathloss offset, or both.
[0159] Aspect 13: The method of any of aspects 11 through 12, further comprising: receiving a fifth control message indicating the power control offset, the pathloss offset, or both.
[0160] Aspect 14: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 13.
[0161] Aspect 15: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 13.
[0162] Aspect 16: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 13.
[0163] It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.
[0164] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.
[0165] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0166] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU) , a neural processing unit (NPU) , an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) . Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.
[0167] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
[0168] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.
[0169] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”
[0170] As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components, ” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components. ”
[0171] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure) , ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information) , accessing (e.g., accessing data stored in memory) , and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.
[0172] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.
[0173] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.
[0174] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1.A user equipment (UE) , comprising:one or more memories storing processor-executable code; andone or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:receive a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell;perform a cell switch from the first cell to a second cell that is different from the first cell, wherein the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions; andcommunicate with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based at least in part on the cell switch.2.The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive the cell switching indication via the first control message, wherein the cell switch is based at least in part on receiving the first control message.3.The UE of claim 2, wherein one or more bit fields of the first control message comprises the cell switching indication and an indication of a cell index corresponding to the second cell.4.The UE of claim 3, wherein:the one or more bit fields comprise one or more reserved bits.5.The UE of claim 2, wherein the first control message comprises a group-common downlink control information (DCI) or a UE-specific DCI.6.The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive a second control message different from the first control message, the second control message comprising the cell switching indication, wherein the cell switch is based at least in part on receiving the second control message.7.The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:select the second cell for performing the cell switch in accordance with a rule, the rule indicating an order of one or more respective cell indices to use for performing the cell switch.8.The UE of claim 7, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive a third control message indicating an updated rule that is different from the rule; andselect the second cell for performing the cell switch in accordance with the updated rule.9.The UE of claim 8, wherein the third control message comprises a medium access control-control element or downlink control information.10.The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive a fourth control message indicating a cell index to use for the second cell; andselect, in response to the activation of the one or more measurement gap occasions, the second cell for performing the cell switch based at least in part on the cell index.11.The UE of claim 1, wherein, to communicate with the network entity, the one or more processors are individually or collectively operable to execute the code to cause the UE to:transmit one or more uplink messages to the network entity via the second cell during at least the portion of the one or more measurement gap occasions associated with the first cell, wherein a power control offset or a pathloss offset, or both, applied to the one or more uplink messages is based at least in part on performing the cell switch from the first cell to the second cell.12.The UE of claim 11, wherein the first control message indicates the power control offset, the pathloss offset, or both.13.The UE of claim 11, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive a fifth control message indicating the power control offset, the pathloss offset, or both.14.A method for wireless communications at a user equipment (UE) , comprising:receiving a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell;performing a cell switch from the first cell to a second cell that is different from the first cell, wherein the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions; andcommunicating with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based at least in part on the cell switch.15.The method of claim 14, further comprising:receiving the cell switching indication via the first control message, wherein the cell switch is based at least in part on receiving the first control message.16.The method of claim 15, wherein one or more bit fields of the first control message comprises the cell switching indication and an indication of a cell index corresponding to the second cell.17.The method of claim 15, wherein the first control message comprises a group-common downlink control information (DCI) or a UE-specific DCI.18.The method of claim 14, further comprising:receiving a second control message different from the first control message, the second control message comprising the cell switching indication, wherein the cell switch is based at least in part on receiving the second control message.19.The method of claim 14, further comprising:selecting the second cell for performing the cell switch in accordance with a rule, the rule indicating an order of one or more respective cell indices to use for performing the cell switch.20.A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to:receive a first control message via a first cell, the first control message indicating an activation of one or more measurement gap occasions associated with the first cell;perform a cell switch from the first cell to a second cell that is different from the first cell, wherein the cell switch is triggered via a cell switching indication from a network entity and is associated with the activation of the one or more measurement gap occasions; andcommunicate with the network entity during at least a portion of the one or more measurement gap occasions via the second cell based at least in part on the cell switch.
Citation Information
Patent Citations
Measurement gap scheduling method and device, communication equipment and storage medium
CN115039433A
Measurement interval configuration method and device
CN116017491A
Gap information transmission method and device and network side equipment
CN116471671A
Measurement gap scheduling method and apparatus therefor
WO2023044628A1