PHYSICAL UPLINK SHARED CHANNEL REPEAT DURING HANDOVER - Patent application

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may transmit, to a source base station associated with a source master cell group (MCG), a physical uplink shared channel (PUSCH) repetition in one or more slots of the source MCG during handover of the UE from the source MCG to a target MCG. The UE may perform uplink transmissions to a target base station associated with the target MCG in one or more slots of the target MCG during handover, where PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmissions to the MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the slots of the source MCG associated with the cancelled PUSCH repetitions. Numerous other aspects are described.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This patent application claims priority to U.S. Non-Provisional Patent Application No. 17 / 219,377, filed March 31, 2021, entitled “PHYSICAL UPLINK SHARED CHANNEL REPETITIONS DURING HANDOVER,” which is expressly incorporated herein by reference.

[0002] Aspects of the present disclosure relate generally to wireless communications and to techniques and apparatus for Physical Uplink Shared Channel (PUSCH) repetition during handover. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP®).

[0004] A wireless network may include a number of base stations (BSs) that can support communication for a number of user equipments (UEs). The UEs may communicate with the BSs via a downlink and an uplink. The "downlink" (or "forward link") refers to the communication link from the BS to the UE, and the "uplink" (or "reverse link") refers to the communication link from the UE to the BS. As described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0005] The above multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that allows different user equipment to communicate on a city, national, regional, or even global scale. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink (UL), as well as better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful. Summary of the Invention [Means for solving the problem]

[0006] In some aspects, a method of wireless communication performed by a UE includes transmitting, to a source base station associated with a source master cell group (MCG), physical uplink shared channel (PUSCH) repetitions in each of one or more slots of a source MCG during a dual active protocol stack (DAPS) based handover of the UE from the source MCG to a target MCG; and performing, to a target base station associated with the target MCG, uplink transmissions in the one or more slots of the target MCG during the DAPS based handover, wherein PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG are canceled, and a count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0007] In some aspects, a method of wireless communication performed by a source base station includes transmitting a configuration associated with an amount of PUSCH repetitions to a UE; and receiving from the UE PUSCH repetitions in each of one or more slots of a source MCG associated with the source base station during a DAPS-based handover of the UE from the source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0008] In some aspects, a UE for wireless communication includes a memory and one or more processors operably coupled to the memory, where the one or more processors are configured to: transmit, to a source base station associated with a source MCG, PUSCH repetitions in each of the one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to a target MCG; and perform, to a target base station associated with the target MCG, uplink transmissions in the one or more slots of the target MCG during the DAPS-based handover, where PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG are canceled and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0009] In some aspects, a source base station for wireless communication includes a memory and one or more processors operably coupled to the memory, where the one or more processors are configured to: send, to a UE, a configuration associated with an amount of PUSCH repetitions; and receive, from the UE, PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station during a DAPS-based handover of the UE from the source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0010] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a UE, cause the UE to: transmit, to a source base station associated with a source MCG, PUSCH repetitions in each of one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to a target MCG; and perform uplink transmissions, to a target base station associated with the target MCG, in one or more slots of the target MCG during the DAPS-based handover, where PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG are canceled and a count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0011] In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a source base station, cause the source base station to: send, to a UE, a configuration associated with an amount of PUSCH repetitions; and receive from the UE PUSCH repetitions in each of one or more slots of a source MCG associated with the source base station during a DAPS-based handover of the UE from the source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and the count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0012] In some aspects, an apparatus for wireless communication includes means for transmitting, to a source base station associated with a source MCG, PUSCH repetitions in each of one or more slots of the source MCG during a DAPS based handover of the apparatus from the source MCG to a target MCG; and means for performing, to a target base station associated with the target MCG, uplink transmissions in the one or more slots of the target MCG during the DAPS based handover, wherein PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG are canceled, and a count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0013] In some aspects, a source device for wireless communication includes means for transmitting, to a UE, a configuration associated with an amount of PUSCH repetitions; and means for receiving, from the UE, PUSCH repetitions in each of one or more slots of a source MCG associated with the source device during a DAPS based handover of the UE from the source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and a count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the drawings and this specification.

[0015] The foregoing has outlined rather broadly the features and technical advantages of examples according to the present disclosure so that the following detailed description may be better understood. Additional features and advantages are described below. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for the purpose of illustration and description, and not as a definition of the limits of the claims.

[0016] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects may be implemented in many different configurations and scenarios. The techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include several components (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers) for analog and digital applications. It is contemplated that the aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, or end-user devices of various sizes, shapes, and configurations.

[0017] So that the above-listed features of the present disclosure may be understood in detail, a more detailed description may be had by referring to embodiments, some of which are shown in the accompanying drawings. However, it should be noted that the accompanying drawings show only some typical embodiments of the present disclosure and therefore should not be considered as limiting its scope, since the present description may admit of other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Brief description of the drawings]

[0018] [Figure 1] FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2] FIG. 2 illustrates an example of a base station in communication with a UE in a wireless network in accordance with the present disclosure. [Diagram 3] FIG. 1 illustrates an example of PUSCH repetition type A counting in accordance with the present disclosure. [Figure 4] FIG. 1 illustrates an example of a DAPS-based handover in accordance with the present disclosure. [Diagram 5] FIG. 1 illustrates an example of uplink cancellation in a DAPS-based handover in accordance with the present disclosure. [Figure 6] FIG. 1 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. [Figure 7] FIG. 1 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. [Figure 8] FIG. 1 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. [Figure 9] FIG. 1 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. [Figure 10] FIG. 1 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. [Figure 11] FIG. 1 illustrates an example process associated with PUSCH repetition during handover, in accordance with the present disclosure. [Figure 12] FIG. 1 illustrates an example process associated with PUSCH repetition during handover, in accordance with the present disclosure. [Figure 13] 1 is a block diagram of an example apparatus for wireless communication according to the present disclosure. [Figure 14] 1 is a block diagram of an example apparatus for wireless communication according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] Various aspects of the present disclosure will be described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that the disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art should appreciate that the scope of the present disclosure encompasses any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. In addition, the scope of the present disclosure is intended to encompass such an apparatus or method practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0020] Several aspects of a telecommunications system are now presented with reference to various apparatus and techniques that are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0021] Although aspects may be described herein using terminology commonly associated with 5G or NR radio access technologies (RATs), it should be noted that aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

[0022] FIG. 1 illustrates an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be or include elements of a 5G (NR) network and / or an LTE network, among other examples. The wireless network 100 may include several base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A base station (BS) is an entity that communicates with user equipment (UE) and may also be referred to as an NR BS, Node B, gNB, 5G Node B (NB), access point, transmit reception point (TRP), etc. Each BS may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving this coverage area, depending on the context in which the term is used.

[0023] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs that have an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or multiple (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” may be used interchangeably herein.

[0024] In some aspects, the cells may not necessarily be stationary and the geographic area of ​​the cells may move according to the location of the mobile BS. In some aspects, the BSs may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0025] Wireless network 100 may also include relay stations. A relay station is an entity that can receive a transmission of data from an upstream station (e.g., a BS or a UE) and send the transmission of the data to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. In the example shown in FIG. 1, relay BS 110d may communicate with macro BS 110a and UE 120d to facilitate communication between BS 110a and UE 120d. A relay BS may also be referred to as a relay station, a relay base station, a relay, etc.

[0026] The wireless network 100 may be a heterogeneous network including different types of BSs, such as macro BSs, pico BSs, femto BSs, relay BSs, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5-40 watts), while a pico BS, femto BS, and relay BS may have a lower transmit power level (e.g., 0.1-2 watts).

[0027] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, e.g., directly or indirectly via wireless or wireline backhaul.

[0028] The UEs 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium.

[0029] Some UEs may be considered as machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and / or a location tag that may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered as Customer Premises Equipment (CPE). The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some aspects, the processor component and the memory component may be coupled to each other. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0030] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular RAT and may operate on one or more frequencies. The RAT may also be referred to as a radio technology, an air interface, etc. The frequencies may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0031] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using the base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, the UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include, e.g., vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / or mesh networks. In this case, the UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by the base station 110.

[0032] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided into various classes, bands, channels, etc. based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using an operating band having a first frequency range (FR1) that may range from 410 MHz to 7.125 GHz, and / or may communicate using an operating band having a second frequency range (FR2) that may range from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, FR2 is often referred to as the "millimeter wave" band, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunications Union (ITU). Thus, unless otherwise specified, it should be understood that terms such as "sub-6 GHz," as used herein, may broadly refer to frequencies below 6 GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise specified, it should be understood that terms such as "millimeter wave," as used herein, may broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25 GHz). The frequencies included in FR1 and FR2 may be modified, and it is contemplated that the techniques described herein are applicable to those modified frequency ranges.

[0033] As noted above, Figure 1 is provided as an example. Other examples may differ from those described with respect to Figure 1.

[0034] 2 is a diagram illustrating an example base station 110 200 in communication with a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with T antennas 234a through 234t, and the UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0035] At the base station 110, the transmit processor 220 may receive data for one or more UEs from a data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols to all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively.

[0036] At the UE 120, the antennas 252a-252r may receive downlink signals from the base station 110 and / or other base stations and may provide received signals to demodulators (DEMODs) 254a-254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from all R demodulators 254a-254r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate and decode) the detected symbols and provide decoded data for the UE 120 to a data sink 260 and provide decoded control and system information to a controller / processor 280. The term “controller / processor” may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a channel quality indicator (CQI) parameter, among other examples. In some aspects, one or more components of the UE 120 may be included in the housing 284.

[0037] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base stations 110 via the communication unit 294.

[0038] An antenna (e.g., antennas 234a-t and / or antennas 252a-r) may include or be contained within one or more antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include a set of coplanar antenna elements and / or a set of non-coplanar antenna elements. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include antenna elements in a single housing and / or antenna elements in multiple housings. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG. 2.

[0039] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266, if applicable, further processed by the modulators 254a-254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some aspects, the modulators and demodulators (e.g., MOD / DEMOD 254) of the UE 120 may be included in a modem of the UE 120. In some aspects, the UE 120 includes a transceiver. The transceiver may include any combination of antennas 252, modulators and / or demodulators 254, MIMO detectors 256, receive processors 258, transmit processors 264, and / or TX MIMO processors 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., as described with reference to FIGS. 6-12).

[0040] At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule the UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of the base station 110 may be included in a modem of the base station 110. In some aspects, the base station 110 includes a transceiver. The transceiver may include any combination of antennas 234, modulators and / or demodulators 232, MIMO detectors 236, receive processors 238, transmit processors 220, and / or TX MIMO processors 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., as described with reference to FIGS. 6-12).

[0041] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform one or more techniques associated with PUSCH repetition during handover, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other components of FIG. 2 may perform or direct the operation of, for example, process 1100 of FIG. 11, process 1200 of FIG. 12, and / or other processes as described herein. The memories 242 and 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some aspects, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., immediately or after being compiled, converted, and / or interpreted) by one or more processors of the base station 110 and / or the UE 120, may cause the one or more processors, the UE 120, and / or the base station 110 to perform or direct operations of, for example, process 1100 of FIG. 11, process 1200 of FIG. 12, and / or other processes as described herein. In some aspects, executing the instructions may include invoking the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0042] In some aspects, a UE (e.g., UE 120) includes means for transmitting, to a source base station associated with a source MCG, PUSCH repetitions in each of one or more slots of a source MCG during a DAPS-based handover of the UE from the source MCG to a target MCG, and / or means for performing uplink transmissions in one or more slots of a target MCG during a DAPS-based handover to a target base station associated with the target MCG, where PUSCH repetitions associated with a source MCG that overlap in time with an uplink transmission to the MCG are cancelled and the count of PUSCH repetitions is based at least in part on the slots of the source MCG associated with the cancelled PUSCH repetitions. The means for the UE to perform the operations described herein may include, for example, one or more of antenna 252, demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, modulator 254, controller / processor 280, or memory 282.

[0043] In some aspects, the UE includes means for canceling PUSCH repetitions associated with a source MCG that overlap in time with an uplink transmission to the MCG.

[0044] In certain aspects, the UE includes means for canceling PUSCH repetitions associated with a source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during a DAPS based handover.

[0045] In certain aspects, the UE includes means for canceling PUSCH repetitions associated with a source MCG based at least in part on the UE capability to cancel uplink transmissions during a DAPS based handover.

[0046] In certain aspects, the UE includes means for canceling PUSCH repetitions associated with a source MCG based at least in part on the intra-frequency DAPS based handover.

[0047] In some aspects, a source base station (e.g., base station 110a) includes means for transmitting, to the UE, a configuration associated with an amount of PUSCH repetitions, and / or means for receiving, from the UE, PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station during a DAPS-based handover of the UE from the source MCG to the target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are cancelled and the count of PUSCH repetitions is based at least in part on the slots of the source MCG associated with the cancelled PUSCH repetitions. The means for the source base station to perform the operations described herein may include, for example, one or more of the transmit processor 220, the TX MIMO processor 230, the modulator 232, the antennas 234, the demodulator 232, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0048] 2 are shown as separate components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combination component, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0049] As noted above, Figure 2 is provided as an example. Other examples may differ from those described with respect to Figure 2.

[0050] FR1 and FR2 may be associated with potential bottleneck channels. For example, in FR1, the potential bottleneck channel may be a PUSCH for enhanced mobile broadband (eMBB). The PUSCH for eMBB may be associated with frequency division duplexing (FDD) or time division duplexing (TDD) with a certain slot configuration (e.g., DDDSU, DDDSUDDSUU, or DDDDDDDSUU, where "D" represents a downlink slot, "S" represents a special slot, and "U" represents an uplink slot). In FR1, another potential bottleneck channel may be a PUSCH for voice over Internet protocol (VoIP). The PUSCH for VoIP may be associated with FDD or TDD with a certain slot configuration (e.g., DDDSU or DDDSUDDSUU). In FR2, the potential bottleneck channel may be a PUSCH for eMBB, which may be associated with a certain slot configuration (e.g., DDDSU or DDSU). In FR2, another potential bottleneck channel may be PUSCH for VoIP with a fixed slot configuration (eg, DDDSU or DDSU).

[0051] For PUSCH repetition type A, the UE may repeat a transport block over consecutive slots applying the same symbol allocation in each slot. However, for PUSCH repetition type A, the number of PUSCH repetitions may be based at least in part on the amount of available uplink / special slots, since counting PUSCH repetitions based at least in part on consecutive slots may limit the number of actual PUSCH repetitions.

[0052] FIG. 3 is a diagram illustrating an example PUSCH repetition type A count 300 in accordance with the present disclosure.

[0053] As indicated by reference numeral 302, a PUSCH repetition count for TDD (unpaired spectrum) may provide multiple downlink, uplink, and / or special slots based at least in part on a slot configuration. The first PUSCH repetition is associated with the first slot (uplink or special slot) and may have a count value of 0, and the count value for each subsequent slot (e.g., uplink, downlink, or special slot) may be incremented by 1.

[0054] In this example, since the first slot and the second slot may be separated by a non-uplink slot (e.g., a downlink slot), a first PUSCH repetition associated with the first slot may correspond to a count value of 0 and a second PUSCH repetition associated with the second slot may correspond to a count value of 5. Furthermore, the first slot and the second slot may be associated with the same symbol allocation. For example, when symbols 2-10 are used in the first slot for the first PUSCH repetition, symbols 2-10 may also be used in the second slot for the second PUSCH repetition.

[0055] As indicated by reference numeral 304, the PUSCH repetition count for FDD (paired spectrum) may include multiple PUSCH repetitions based at least in part on the slot configuration. The first PUSCH repetition is associated with the first slot and may have a count value of 0, and the count value for each subsequent slot may be incremented by 1.

[0056] As indicated by reference numeral 306, the PUSCH repetition count for TDD (paired spectrum) may include multiple PUSCH repetitions based at least in part on the slot configuration. The first PUSCH repetition may be associated with the first slot and may have a count value of 0. In this example, the count value may not increment by 1 for each successive slot, regardless of whether the next slot is an uplink, downlink, or special slot. Rather, the count value may only be incremented for the subsequent uplink / special slot.

[0057] In this example, even though the first and second slots may be separated by a non-uplink slot (e.g., a downlink slot), a first PUSCH repetition associated with a first slot may correspond to a count value of 0 and a second PUSCH repetition associated with a second slot may correspond to a count value of 1. Thus, in this example, the amount of PUSCH repetitions may be counted based on available uplink / special slots and may not be counted based on consecutive slots, which may limit the number of actual PUSCH repetitions.

[0058] As noted above, Figure 3 is provided as an example. Other examples may differ from those described with respect to Figure 3.

[0059] 4 illustrates an example 400 of a DAPS-based handover in accordance with the present disclosure. A DAPS-based handover may involve a UE, a source MCG (or source base station), a target MCG (or target base station), and a user plane function.

[0060] DAPS-based handover may reduce handover interruption time by allowing the UE to connect to both source and target MCGs simultaneously during DAPS-based handover. DAPS-based handover may be applicable to intra-frequency handover, intra-band inter-frequency handover, and / or inter-band inter-frequency handover.

[0061] As shown in FIG. 4, in a first action, the UE may perform radio resource management (RRM) reference signal measurement, where the RRM reference signal may be a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS). In a second action, an event trigger may occur in the UE, and in a third action, the UE may send a measurement report to the source MCG. The measurement report may indicate the RRM reference signal measurement value. In a fourth action, the source MCG may perform a DAPS-based handover decision based at least in part on the measurement report. In a fifth action, the source MCG may prepare the target MCG for the DAPS-based handover.

[0062] In a sixth action, the source MCG may send a radio resource control (RRC) reconfiguration message to the UE. The RRC reconfiguration message may indicate a handover command. In a seventh action, the UE may connect to the target MCG, and in an eighth action, the UE may send an RRC reconfiguration complete message to the target MCG. In a ninth action, the target MCG may perform a source MCG connection release decision, and in a tenth action, the source MCG and the target MCG may communicate a handover connection setup complete indication. In an eleventh action, the target MCG may send an instruction to the UE to release the source MCG, and in a twelfth action, the UE may release the source MCG based at least in part on the indication received from the target MCG. In a thirteenth action, the UE may send an RRC reconfiguration complete message to the target MCG. In a fourteenth action, the UE context information with the source MCG may be released. In a fifteenth action, the UE may communicate data on the target MCG.

[0063] In this example of a DAPS-based handover, the UE may be connected to both the source MCG and the target MCG during handover of the UE from the source MCG to the target MCG, e.g., during action 7 to action 11, the UE may continue transmitting and receiving data on the source MCG even though the UE may also be connected to the target MCG.

[0064] As noted above, Figure 4 is provided as an example. Other examples may differ from those described with respect to Figure 4.

[0065] For a non-intra-frequency DAPS based handover, the UE may transmit on a target cell (e.g., a target cell associated with a target MCG) and the UE may cancel transmissions to a source cell (e.g., a source cell associated with a source MCG). In other words, the UE may transmit only on the target cell and cancel transmissions to the source cell. The UE may transmit on the target cell and cancel transmissions to the source cell based at least in part on the UE transmissions on the target cell and source cell being in overlapping time resources, the UE not indicating capability for power sharing between the source MCG and the target MCG in the DAPS based handover, and the UE indicating support for uplink transmission cancellation associated with the DAPS based handover.

[0066] In the case of an intra-frequency DAPS based handover, the UE may transmit on the target cell and cancel transmission to the source cell based at least in part on the UE transmissions on the target cell and source cell being in overlapping time resources.

[0067] FIG. 5 illustrates an example 500 of uplink cancellation in a DAPS-based handover in accordance with the present disclosure.

[0068] As shown in FIG. 5, a UE may be connected to a source MCG and a target MCG during a DAPS-based handover. The UE may communicate with the source MCG based at least in part on a first slot configuration, and the UE may communicate with the target MCG based at least in part on a second slot configuration. In this example, the first slot configuration may be associated with a first slot corresponding to an uplink transmission, a second slot corresponding to an uplink transmission, a third slot corresponding to a non-uplink transmission (e.g., a downlink transmission), and a fourth slot corresponding to an uplink transmission. The second slot configuration may be associated with a first slot corresponding to a non-uplink transmission, a second slot corresponding to an uplink transmission, a third slot corresponding to an uplink transmission, and a fourth slot corresponding to a non-uplink transmission. In this example, the UE may cancel the second slot having an uplink transmission for the source MCG because the second transmission associated with both the first slot configuration and the second slot configuration is an uplink transmission. In other words, during the second slot associated with the first slot configuration and the second slot configuration, the UE may perform an uplink transmission to the target MCG and may cancel the uplink transmission to the source MCG.

[0069] As noted above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0070] The UE may be handed over from a source MCG to a target MCG based at least in part on a DAPS-based handover. During the DAPS-based handover, the UE may communicate with both a source base station associated with the source MCG and a target base station associated with the target MCG. Regardless of whether the DAPS-based handover is an intra-frequency DAPS-based handover, the UE may perform transmissions on the target MCG and may cancel transmissions on the source MCG based at least in part on the transmissions on the source MCG overlapping in time with the transmissions on the target MCG. However, the UE behavior may not be defined for a situation in which a PUSCH transmission with repetition on the source MCG is canceled based at least in part on an uplink transmission on the target MCG when a DAPS-based handover is enabled for the UE.

[0071] In various aspects of the techniques and apparatus described herein, the UE may transmit to a source base station associated with the source MCG a PUSCH repetition in each of one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG. The UE may perform uplink transmissions to a target base station associated with the target MCG in one or more slots of the target MCG during a DAPS-based handover. In some aspects, the UE may cancel a PUSCH repetition associated with the source MCG that overlaps in time with an uplink transmission to the MCG. In some aspects, the UE may count PUSCH repetitions based at least in part on slots of the source MCG associated with the cancelled PUSCH repetitions. In some aspects, the UE may count PUSCH repetitions based at least in part on counting slots of the source MCG associated with the cancelled PUSCH repetitions. In some aspects, the UE may count PUSCH repetitions based at least in part on not counting slots of the source MCG associated with the cancelled PUSCH repetitions.

[0072] 6 is a diagram illustrating an example 600 of PUSCH repetition during handover in accordance with the present disclosure. As shown in FIG. 6, the example 600 includes communication between a UE (e.g., UE 120), a source base station UE (e.g., base station 110a), and a target base station (e.g., base station 110b). In some aspects, the UE, the source base station, and the target base station may be included in a wireless network, such as wireless network 100.

[0073] As indicated by reference numeral 602, the UE may transmit PUSCH repetitions in each of one or more slots of the source MCG to a source base station associated with the source MCG. The one or more slots may be uplink slots and / or special slots. The UE may transmit PUSCH repetitions in one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG. In some aspects, the PUSCH repetitions may be associated with PUSCH repetition type A in which the same symbol allocation is applied in each of the one or more slots of the source MCG.

[0074] In some aspects, the UE may receive a configuration associated with an amount of PUSCH repetitions from a source base station, and the UE may transmit PUSCH repetitions in one or more slots of the source MCG to the source base station based at least in part on the configuration.

[0075] In some aspects, the DAPS based handover may be associated with an FDD-FDD handover. In some aspects, the DAPS based handover may be associated with a TDD-TDD handover. In some aspects, the DAPS based handover may be associated with a TDD-FDD handover. In some aspects, the DAPS based handover may be associated with an FDD-TDD handover. Furthermore, FDD may be associated with a paired spectrum and TDD may be associated with an unpaired spectrum.

[0076] The UE may perform an uplink transmission in one or more slots of the target MCG during the DAPS-based handover to a target base station associated with the target MCG, as indicated by reference numeral 604. The uplink transmission may be a Physical Uplink Control Channel (PUCCH) transmission, a PUSCH transmission, a Sounding Reference Signal (SRS), a Physical Random Access Channel (PRACH) transmission, or a Message 3 (Msg3) PUSCH transmission.

[0077] In some aspects, the UE may cancel PUSCH repetitions associated with a source MCG that overlap in time with an uplink transmission to the MCG, where one or more slots of the target MCG may be associated with the uplink transmission from the UE. In some aspects, the UE may cancel PUSCH repetitions associated with a source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during a DAPS-based handover. In some aspects, the UE may cancel PUSCH repetitions associated with a source MCG based at least in part on a UE capability to cancel uplink transmissions during a DAPS-based handover.

[0078] In some aspects, the UE may count PUSCH repetitions based at least in part on slots of a source MCG associated with a cancelled PUSCH repetition. In one example, the UE may count PUSCH repetitions based at least in part on counting slots of a source MCG associated with a cancelled PUSCH repetition. In another example, the UE may count PUSCH repetitions based at least in part on not counting slots of a source MCG associated with a cancelled PUSCH repetition.

[0079] In some aspects, the PUSCH repetitions associated with the source MCG may fully overlap in time with the uplink transmissions to the MCG, hi some aspects, the PUSCH repetitions associated with the source MCG may partially overlap in time with the uplink transmissions to the MCG.

[0080] In some aspects, the UE may use the available PUSCH repetition transmission in the source MCG.

[0081]

number

[0082] , the UE may transmit PUSCH repetitions over an amount of slots, due to the slots overlapping in time with uplink transmissions to the target MCG.

[0083]

number

[0084] When the UE does not transmit PUSCH repetitions in the slots included in the amount of slots,

[0085]

number

[0086] Slots included in the amount of slots may or may not be counted.

[0087]

number

[0088] The slots in the amount of slots may be slots associated with cancelled PUSCH repetitions due to slots that overlap in time with uplink transmissions to the target MCG. In this example,

[0089]

number

[0090] may represent a slot associated with the PUSCH repetition (e.g., an uplink slot or a special slot). An uplink transmission to a target MCG may be associated with a PUCCH, a PUSCH, an SRS, a PRACH, or an Msg3 PUSCH.

[0091] As noted above, Figure 6 is provided as an example. Other examples may differ from those described with respect to Figure 6.

[0092] FIG. 7 is a diagram illustrating an example 700 of PUSCH repetition during handover in accordance with the present disclosure.

[0093] As shown in FIG. 7, multiple slots may be configured for PUSCH repeat transmission to the source MCG, and multiple slots may be configured for uplink transmission (e.g., PUCCH transmission, PUSCH transmission, SRS transmission, PRACH transmission, and / or Msg3 PUSCH transmission) to the target MCG. The UE may perform PUSCH repeat transmission to the source MCG on one or more slots associated with the source MCG, and the UE may perform uplink transmission to the target MCG on one or more slots associated with the target MCG. However, for slots associated with the source MCG that overlap in time with uplink transmission in slots associated with the target MCG, the UE may cancel PUSCH repeat transmission in those slots associated with the source MCG. In other words, the UE may cancel PUSCH repeat transmission in those slots and instead perform uplink transmission to the target MCG.

[0094] A slot format configuration (e.g., a configuration of uplink, downlink, and special slots) for the source MCG may be defined, and a slot format configuration for the target MCG may be defined. In a first counting scheme in which a UE counts slots of a source MCG associated with a cancelled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources in an FDD-FDD handover, the UE may associate a first slot with a first PUSCH repeat transmission having a count value of 0, and each subsequent slot may be associated with a count value that is incremented by 1, regardless of whether the subsequent slot is associated with a cancelled PUSCH repeat transmission. In a second counting scheme in which the UE does not count slots of a source MCG associated with a canceled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources, the UE may associate a first slot with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot associated with a PUSCH repeat transmission (e.g., that is not a canceled PUSCH repeat transmission) may be associated with a count value that is incremented by 1.

[0095] As an example, in the second counting scheme, slots 5 and 6 may not be counted because the PUSCH repeat transmissions to the source MCG are cancelled based at least in part on the uplink transmissions to the target MCG.

[0096] As noted above, Figure 7 is provided as an example. Other examples may differ from those described with respect to Figure 7.

[0097] FIG. 8 is a diagram illustrating an example 800 of PUSCH repetition during handover in accordance with the present disclosure.

[0098] A slot format configuration (e.g., a configuration of uplink slots, downlink slots, and special slots) for the source MCG may be defined, and a slot format configuration for the target MCG may be defined, as shown in Figure 8. In a first counting scheme in which a UE counts slots of a source MCG associated with a cancelled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources in a TDD-TDD handover, the UE may associate a first slot with a first PUSCH repeat transmission having a count value of 0, and each subsequent slot may be associated with a count value that is incremented by 1, regardless of whether the subsequent slot is associated with a cancelled PUSCH repeat transmission. In a second counting scheme in which the UE does not count slots of a source MCG associated with a canceled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources, the UE may associate a first slot with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot associated with a PUSCH repeat transmission (e.g., that is not a canceled PUSCH repeat transmission) may be associated with a count value that is incremented by 1.

[0099] As noted above, Figure 8 is provided as an example. Other examples may differ from those described with respect to Figure 8.

[0100] FIG. 9 is a diagram illustrating an example 900 of PUSCH repetition during handover in accordance with the present disclosure.

[0101] A slot format configuration (e.g., a configuration of uplink slots, downlink slots, and special slots) for the source MCG may be defined, and a slot format configuration for the target MCG may be defined, as shown in Figure 9. In a first counting scheme in which a UE counts slots of a source MCG associated with a cancelled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources in a TDD-TDD handover, the UE may associate a first slot with a first PUSCH repeat transmission having a count value of 0, and each subsequent slot may be associated with a count value that is incremented by 1, regardless of whether the subsequent slot is associated with a cancelled PUSCH repeat transmission. In a second counting scheme in which the UE does not count slots of a source MCG associated with a canceled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources, the UE may associate a first slot with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot associated with a PUSCH repeat transmission (e.g., that is not a canceled PUSCH repeat transmission) may be associated with a count value that is incremented by 1.

[0102] As noted above, Figure 9 is provided as an example. Other examples may differ from those described with respect to Figure 9.

[0103] FIG. 10 is a diagram illustrating an example 1000 of PUSCH repetition during handover in accordance with the present disclosure.

[0104] A slot format configuration (e.g., a configuration of uplink slots, downlink slots, and special slots) for the source MCG may be defined, and a slot format configuration for the target MCG may be defined, as shown in Figure 10. In a first counting scheme in which a UE counts slots of a source MCG associated with a cancelled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources in a TDD-TDD handover, the UE may associate a first slot with a first PUSCH repeat transmission with a count value of 0, and each subsequent slot may be associated with a count value that is incremented by 1, regardless of whether the subsequent slot is associated with a cancelled PUSCH repeat transmission. In a second counting scheme in which the UE does not count slots of a source MCG associated with a canceled PUSCH repeat transmission due to an uplink transmission to a target MCG that overlaps in time resources, the UE may associate a first slot with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot associated with a PUSCH repeat transmission (e.g., that is not a canceled PUSCH repeat transmission) may be associated with a count value that is incremented by 1.

[0105] As noted above, Figure 10 is provided as an example. Other examples may differ from those described with respect to Figure 10.

[0106] 11 illustrates an example process 1100 performed, for example, by a UE, in accordance with the present disclosure. The example process 1100 is an example in which a UE (for example, UE 120) performs operations associated with PUSCH repetition during handover.

[0107] 11, in some aspects, process 1100 may include transmitting, to a source base station associated with the source MCG, PUSCH repetitions in each of one or more slots of the source MCG during DAPS-based handover of the UE from the source MCG to the target MCG (block 1110). For example, the UE (e.g., using the transmitting component 1304 shown in FIG. 13) may transmit, to a source base station associated with the source MCG, PUSCH repetitions in each of one or more slots of the source MCG during DAPS-based handover of the UE from the source MCG to the target MCG, as described above.

[0108] 11, in some aspects, the process 1100 may include performing, to a target base station associated with the target MCG, uplink transmissions in one or more slots of the target MCG during the DAPS-based handover, where PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmissions to the MCG are cancelled, and the count of the PUSCH repetitions is based at least in part on the slots of the source MCG associated with the cancelled PUSCH repetitions (block 1120). For example, the UE (e.g., using the transmitting component 1304 shown in FIG. 13) may perform, to a target base station associated with the target MCG, uplink transmissions in one or more slots of the target MCG during the DAPS-based handover, where PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmissions to the MCG are cancelled, and the count of the PUSCH repetitions is based at least in part on the slots of the source MCG associated with the cancelled PUSCH repetitions, as described above.

[0109] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein.

[0110] In a first aspect, counting the PUSCH repetitions includes counting slots of the source MCG associated with the cancelled PUSCH repetitions.

[0111] In a second aspect, alone or in combination with the first aspect, counting the PUSCH repetitions includes not counting slots of the source MCG associated with the cancelled PUSCH repetitions.

[0112] In a third aspect, alone or in combination with one or more of the first and second aspects, the PUSCH repetitions associated with the source MCG fully overlap in time with the uplink transmission to the MCG.

[0113] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the PUSCH repetitions associated with the source MCG partially overlap in time with the uplink transmissions to the MCG.

[0114] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the uplink transmission in one or more slots of the target MCG during DAPS based handover is one of a physical uplink control channel transmission, a PUSCH transmission, a sounding reference signal, a physical random access channel transmission, or an Msg3 PUSCH transmission.

[0115] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the DAPS based handover is associated with an FDD-FDD handover, a TDD-TDD handover, a TDD-FDD handover, or an FDD-TDD handover, wherein FDD is associated with a paired spectrum and TDD is associated with an unpaired spectrum.

[0116] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the PUSCH repetition is associated with a PUSCH repetition type A in which the same symbol allocation is applied in each of one or more slots of the source MCG.

[0117] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the process 1100 includes canceling a PUSCH repetition associated with a source MCG that overlaps in time with an uplink transmission to the MCG.

[0118] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the process 1100 includes canceling a PUSCH repetition associated with a source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during a DAPS based handover.

[0119] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the process 1100 includes canceling PUSCH repetitions associated with the source MCG based at least in part on a UE capability to cancel uplink transmissions during a DAPS based handover.

[0120] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the process 1100 includes canceling a PUSCH repetition associated with a source MCG based at least in part on an intra-frequency DAPS based handover.

[0121] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, one or more slots of the source MCG include one or more of uplink slots or special slots, and one or more slots of the target MCG include one or more of uplink slots or special slots.

[0122] 11 illustrates example blocks of process 1100, in some aspects process 1100 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 11. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0123] 12 illustrates an example process 1200 performed, for example, by a source base station, in accordance with the present disclosure. The example process 1200 is an example of a source base station (e.g., source base station 110) performing operations associated with PUSCH repetition during handover.

[0124] 12, in some aspects, the process 1200 may include transmitting a configuration associated with an amount of PUSCH repetition to the UE (block 1210). For example, the source base station (e.g., using the transmitting component 1404 shown in FIG. 14) may transmit the configuration associated with the amount of PUSCH repetition to the UE, as described above.

[0125] 12, in some aspects, the process 1200 may include receiving, from the UE, a PUSCH repetition in each of one or more slots of a source MCG associated with a source base station during a DAPS-based handover of the UE from the source MCG to the target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and the count of the PUSCH repetitions is based at least in part on the slots of the source MCG associated with the canceled PUSCH repetitions (block 1220). For example, the source base station (e.g., using the receiving component 1402 illustrated in FIG. 14) may receive, as described above, a PUSCH repetition in each of one or more slots of a source MCG associated with a source base station during a DAPS-based handover of the UE from the source MCG to the target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and the count of the PUSCH repetitions is based at least in part on the slots of the source MCG associated with the canceled PUSCH repetitions.

[0126] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or with respect to one or more other processes described elsewhere herein.

[0127] In a first aspect, the counting of PUSCH repetitions is based at least in part on counting slots of a source MCG associated with cancelled PUSCH repetitions.

[0128] In a second aspect, alone or in combination with the first aspect, the counting of PUSCH repetitions is based at least in part on not counting slots of the source MCG associated with cancelled PUSCH repetitions.

[0129] 12 illustrates example blocks of process 1200, in some aspects process 1200 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 12. Additionally or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0130] 13 is a block diagram of an example apparatus 1300 for wireless communication. The apparatus 1300 may be a UE, or a UE may include the apparatus 1300. In some aspects, the apparatus 1300 includes a receiving component 1302 and a transmitting component 1304, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a base station, or another wireless communication device) using the receiving component 1302 and the transmitting component 1304. As further shown, the apparatus 1300 may include a cancellation component 1308, among other examples.

[0131] In some aspects, the apparatus 1300 may be configured to perform one or more operations described herein with respect to FIGS. 6-10. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as the process 1100 of FIG. 11. In some aspects, the apparatus 1300 and / or one or more components illustrated in FIG. 13 may include one or more components of a UE described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 13 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0132] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1306. The receiving component 1302 may provide the received communications to one or more other components of the apparatus 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the apparatus 1306. In some aspects, the receiving component 1302 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE as described above with respect to FIG. 2.

[0133] The transmitting component 1304 may transmit a communication to the device 1306, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 1306 may generate a communication and provide the generated communication to the transmitting component 1304 for transmission to the device 1306. In some aspects, the transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 1306. In some aspects, the transmitting component 1304 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof of a UE as described above with respect to FIG. 2. In some aspects, the transmitting component 1304 may be co-located with the receiving component 1302 in a transceiver.

[0134] The transmitting component 1304 may transmit, to a source base station associated with the source MCG, PUSCH repetitions in each of the one or more slots of the source MCG during DAPS-based handover of the UE from the source MCG to the target MCG. The transmitting component 1304 may perform, to a target base station associated with the target MCG, uplink transmissions in the one or more slots of the target MCG during DAPS-based handover, where PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG are cancelled and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with the cancelled PUSCH repetitions.

[0135] The cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG. The cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during a DAPS based handover. The cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG based at least in part on a UE capability to cancel uplink transmissions during a DAPS based handover. The cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG based at least in part on an intra-frequency DAPS based handover.

[0136] The number and arrangement of components shown in Figure 13 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components compared to those shown in Figure 13. Furthermore, two or more components shown in Figure 13 may be implemented within a single component, or a single component shown in Figure 13 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 13 may perform one or more functions described as being performed by another set of components shown in Figure 13.

[0137] 14 is a block diagram of an example apparatus 1400 for wireless communication. The apparatus 1400 may be a source base station, or the source base station may include the apparatus 1400. In some aspects, the apparatus 1400 includes a receiving component 1402 and a transmitting component 1404, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using the receiving component 1402 and the transmitting component 1404.

[0138] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein with respect to FIGS. 6-10. Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as the process 1200 of FIG. 12. In some aspects, the apparatus 1400 and / or one or more components illustrated in FIG. 14 may include one or more components of a source base station described above with respect to FIG. 2. Additionally or alternatively, one or more components illustrated in FIG. 14 may be implemented within one or more components described above with respect to FIG. 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0139] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the apparatus 1406. The receiving component 1402 may provide the received communications to one or more other components of the apparatus 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the apparatus 1406. In some aspects, the receiving component 1402 may include one or more antennas, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a source base station as described above with respect to FIG.

[0140] The transmitting component 1404 may transmit communications to the device 1406, such as a reference signal, control information, a data communication, or a combination thereof. In some aspects, one or more other components of the device 1406 may generate a communication and provide the generated communication to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 1406. In some aspects, the transmitting component 1404 may include one or more antennas, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a source base station as described above with respect to FIG. 2. In some aspects, the transmitting component 1404 may be co-located with the receiving component 1402 in a transceiver.

[0141] The transmitting component 1404 may transmit a configuration associated with an amount of PUSCH repetitions to the UE. The receiving component 1402 may receive from the UE PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station during a DAPS-based handover of the UE from the source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled and the count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0142] The number and arrangement of components shown in Figure 14 are provided as an example. In practice, there may be additional, fewer, different, or differently arranged components compared to those shown in Figure 14. Furthermore, two or more components shown in Figure 14 may be implemented within a single component, or a single component shown in Figure 14 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 14 may perform one or more functions described as being performed by another set of components shown in Figure 14.

[0143] The following provides a summary of several aspects of the disclosure.

[0144] Aspect 1: A method of wireless communications performed by a user equipment (UE), comprising: transmitting, to a source base station associated with a source master cell group (MCG), a physical uplink shared channel (PUSCH) repetition in each of one or more slots of a source MCG during a dual active protocol stack (DAPS) based handover of the UE from the source MCG to a target MCG; and performing, to a target base station associated with the target MCG, an uplink transmission in one or more slots of the target MCG during the DAPS based handover, wherein PUSCH repetitions associated with the source MCG that overlap in time with an uplink transmission to the MCG are canceled, and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0145] Aspect 2: The method of aspect 1, wherein counting the PUSCH repetitions includes counting slots of the source MCG associated with the cancelled PUSCH repetitions.

[0146] Aspect 3: The method of any of aspects 1 to 2, wherein counting the PUSCH repetitions includes not counting slots of a source MCG associated with a cancelled PUSCH repetition.

[0147] Aspect 4: The method of any of aspects 1-3, wherein the PUSCH repetitions associated with the source MCG fully overlap in time with the uplink transmissions to the MCG.

[0148] Example 5: The method of any of Examples 1-4, wherein the PUSCH repetitions associated with the source MCG overlap in time with the uplink transmissions to the MCG.

[0149] Aspect 6: The method of any of aspects 1-5, wherein the uplink transmission in one or more slots of the target MCG during DAPS-based handover is one of a physical uplink control channel transmission, a PUSCH transmission, a sounding reference signal, a physical random access channel transmission, or a message 3 (Msg3) PUSCH transmission.

[0150] Aspect 7: The method of any of aspects 1-6, wherein the DAPS based handover is associated with a Frequency Division Duplex (FDD)-FDD handover, a Time Division Duplex (TDD)-TDD handover, a TDD-FDD handover, or an FDD-TDD handover, wherein FDD is associated with a paired spectrum and TDD is associated with an unpaired spectrum.

[0151] Example 8: The method of any of Examples 1-7, wherein the PUSCH repetition is associated with a PUSCH repetition type A in which the same symbol allocation is applied in each of one or more slots of a source MCG.

[0152] Aspect 9: The method of any of aspects 1-8, further comprising canceling a PUSCH repetition associated with a source MCG that overlaps in time with an uplink transmission to the MCG.

[0153] Aspect 10: The method of any of aspects 1-9, further comprising canceling PUSCH repetitions associated with a source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during a DAPS based handover.

[0154] Aspect 11: The method of any of aspects 1-10, further comprising canceling PUSCH repetitions associated with the source MCG based at least in part on a UE capability to cancel uplink transmissions during DAPS based handover.

[0155] Aspect 12: The method of any of aspects 1-11, further comprising canceling PUSCH repetitions associated with the source MCG based at least in part on an intra-frequency DAPS based handover.

[0156] Aspect 13: Any of the methods of aspects 1 to 12, wherein one or more slots of the source MCG include one or more of an uplink slot or a special slot, and one or more slots of the target MCG include one or more of an uplink slot or a special slot.

[0157] Aspect 14: A method of wireless communication performed by a source base station, comprising: transmitting a configuration associated with an amount of physical uplink shared channel (PUSCH) repetitions to a user equipment (UE); and receiving from the UE PUSCH repetitions in each of one or more slots of a source master cell group (MCG) associated with a source base station during a dual active protocol stack (DAPS) based handover of the UE from a source MCG to a target MCG, wherein PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled, and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

[0158]

[0041] Aspect 15: The method of aspect 14, wherein the counting of PUSCH repetitions is based at least in part on counting slots of a source MCG associated with a cancelled PUSCH repetition.

[0159] Example 16: The method of any of Examples 14-15, wherein the counting of PUSCH repetitions is based at least in part on not counting slots of a source MCG associated with a cancelled PUSCH repetition.

[0160] Aspect 17: An apparatus for wireless communication in a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 1-13.

[0161] Aspect 18: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to perform the method of one or more of aspects 1-13.

[0162] Aspect 19: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 1-13.

[0163] Aspect 20: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method of one or more of aspects 1-13.

[0164] Aspect 21: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 1-13.

[0165] Aspect 22: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of one or more of aspects 14-16.

[0166] Aspect 23: A device for wireless communication, comprising: a memory; and one or more processors coupled to the memory, wherein the memory and the one or more processors are configured to perform the method of one or more of aspects 14-16.

[0167] Aspect 24: An apparatus for wireless communication, comprising at least one means for performing the method of one or more of aspects 14-16.

[0168] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method of one or more of aspects 14-16.

[0169] Aspect 26: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method of one or more of aspects 14-16.

[0170] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0171] The term "component" as used herein shall be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. A processor as used herein is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not intended to limit the aspects. Thus, the operation and behavior of the systems and / or methods have been described herein without reference to any specific software code. It should be understood that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0172] As used herein, "meeting a threshold" can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc., depending on the context.

[0173] Although certain combinations of features are recited in the claims and / or disclosed herein, these combinations do not limit the disclosure of the various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim described below may depend directly on only one claim, the disclosure of the various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. As an example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0174] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, the articles "a" and "an" as used herein shall include one or more items and may be used interchangeably with "one or more". Furthermore, the article "the" as used herein shall include one or more items referred to with the article "the" and may be used interchangeably with "one or more". Furthermore, the terms "set" and "group" as used herein shall include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with "one or more". When only one item is intended, the phrase "only one" or similar language is used. Also, terms such as "has", "have", "having", etc. as used herein shall be open-ended terms. Furthermore, the phrase "based on" shall mean "based at least in part on" unless otherwise specified. Also, as used herein, the term "or" is intended to be inclusive when used in a consecutive manner, and may be used interchangeably with "and / or" unless otherwise noted (e.g., when used in combination with "either" or "only one of"). [Explanation of symbols]

[0175] 100 Wireless Network 102a Macro Cell 102b Picocell 102c Femtocell 110 Base station, source base station 110a BS, Macro BS 110b BS 110c BS 110d BS, live BS 120UE 120a UE 120b UE 120c UE 120d UE 120e UE 130 Network Controller 200 Examples 212 Data Source 220 Transmit Processor 230 Transmit (TX) Multiple Input Multiple Output (MIMO) Processor, TX MIMO Processor 232 Modulator (MOD), Modulator, Demodulator, MOD / DEMOD 234 Antenna 236 MIMO Detector 238 Receive Processor 239 Data Sink 240 Controllers / Processors 242 Memory 244 Communication Unit 246 Scheduler 252 Antenna 254 Demodulator (DEMOD), Demodulator, Modulator, MOD / DEMOD 256 MIMO detector 258 Receive Processor 260 Data Sink 262 Data Sources 264 Transmit Processor 266 TX MIMO Processor 280 Controller / Processor 282 Memory 284 Housing 290 Controller / Processor 292 Memory 294 Communication Unit 300 Examples 400 Examples 500 Examples 600 Examples 700 Examples 800 Examples 900 Examples 1000 Examples 1100 Process 1200 processes 1300 equipment 1302 Receiving Component 1304 Transmission Component 1306 Equipment 1308 Cancellation Component 1400 equipment 1402 Receiving Component 1404 Transmission Component 1406 Equipment

Claims

1. 1. A method of wireless communication performed by a user equipment (UE), comprising: transmitting, to a source base station associated with a source master cell group (MCG), a physical uplink shared channel (PUSCH) repetition in each of one or more slots of the source MCG during a dual active protocol stack (DAPS) based handover of the UE from the source MCG to a target MCG; performing an uplink transmission in one or more slots of the target MCG during the DAPS based handover to a target base station associated with the target MCG, where PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmission to the target MCG are cancelled, and the counting of the PUSCH repetitions is based at least in part on slots of the source MCG associated with cancelled PUSCH repetitions; A method comprising:

2. 2. The method of claim 1, wherein the counting of the PUSCH repetitions comprises counting the slots of the source MCG associated with the cancelled PUSCH repetition.

3. The method of claim 1, wherein the counting of the PUSCH repetitions includes not counting the slots of the source MCG associated with the canceled PUSCH repetition.

4. The method of claim 1 , wherein the PUSCH repetitions associated with the source MCG fully overlap in time with the uplink transmissions to the target MCG.

5. The method of claim 1 , wherein the PUSCH repetitions associated with the source MCG partially overlap in time with the uplink transmissions to the target MCG.

6. 2. The method of claim 1, wherein the uplink transmission in the one or more slots of the target MCG during the DAPS-based handover is one of a physical uplink control channel transmission, a PUSCH transmission, a sounding reference signal, a physical random access channel transmission, or a message 3 (Msg3) PUSCH transmission.

7. 2. The method of claim 1, wherein the DAPS based handover is associated with a Frequency Division Duplex (FDD)-FDD handover, a Time Division Duplex (TDD)-TDD handover, a TDD-FDD handover, or an FDD-TDD handover, wherein FDD is associated with a paired spectrum and TDD is associated with an unpaired spectrum.

8. The method of claim 1, wherein the PUSCH repetition is associated with a PUSCH repetition type A in which the same symbol allocation is applied in each of the one or more slots of the source MCG.

9. The method of claim 8, further comprising canceling the PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmissions to the target MCG. The method of claim 1, further comprising:

10. canceling the PUSCH repetitions associated with the source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during the DAPS based handover; or canceling the PUSCH repetitions associated with the source MCG based at least in part on a UE capability to cancel uplink transmissions during the DAPS based handover. The method of claim 1, further comprising:

11. The method of claim 10, further comprising canceling the PUSCH repetitions associated with the source MCG based at least in part on an intra-frequency DAPS based handover. The method of claim 1, further comprising:

12. the one or more slots of the source MCG include one or more of an uplink slot or a special slot; the one or more slots of the target MCG include one or more of an uplink slot or a special slot; The method of claim 1.

13. 1. A method of wireless communication performed by a source base station, comprising: transmitting, to a user equipment (UE), a configuration associated with an amount of physical uplink shared channel (PUSCH) repetition; receiving, from the UE, PUSCH repetitions in each of one or more slots of a source master cell group (MCG) associated with the source base station during a dual active protocol stack (DAPS) based handover of the UE from the source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are cancelled, and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with cancelled PUSCH repetitions; A method comprising:

14. A user equipment (UE) for wireless communications, comprising: Memory, and one or more processors configured to be coupled to the memory, the one or more processors further comprising: transmitting, to a source base station associated with a source master cell group (MCG), a physical uplink shared channel (PUSCH) repetition in each of one or more slots of the source MCG during a dual active protocol stack (DAPS) based handover of the UE from the source MCG to a target MCG; performing an uplink transmission in one or more slots of the target MCG during the DAPS based handover to a target base station associated with the target MCG, where PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmission to the target MCG are cancelled, and counting of the PUSCH repetitions is based at least in part on slots of the source MCG associated with cancelled PUSCH repetitions; The UE is configured to:

15. A source base station for wireless communications, comprising: Memory, and one or more processors configured to be coupled to the memory, the one or more processors further comprising: transmitting, to a user equipment (UE), a configuration associated with an amount of physical uplink shared channel (PUSCH) repetition; receiving, from the UE, PUSCH repetitions in each of one or more slots of a source master cell group (MCG) associated with the source base station during a dual active protocol stack (DAPS) based handover of the UE from a source MCG to a target MCG, where PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are cancelled, and a count of the PUSCH repetitions is based at least in part on slots of the source MCG associated with cancelled PUSCH repetitions; A source base station configured to perform the above.

Images