Physical uplink shared channel repetition during handover

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can transmit, to a source base station associated with a source master cell group (MCG), physical uplink shared channel (PUSCH) repetitions in one or more slots of the source MCG during a handover of the UE from the source MCG to a target MCG. The UE performs, during the handover, uplink transmissions to the target MCG in the one or more slots to a target base station associated with the target MCG, wherein PUSCH repetitions associated with the source MCG that overlap in time with the 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. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. nonprovisional patent application No. 17 / 219,377, filed on March 31, 2021, entitled “PHYSICAL UPLINK SHAREDCHANNEL REPETITIONSDURING HANDOVER”, which is expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to wireless communications, and to techniques and apparatus for repeating the Physical Uplink Shared Channel (PUSCH) during handover. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communications employ multiple access technologies that support 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) systems. LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include multiple base stations (BSs), each capable of supporting communication between multiple user equipment (UEs). UEs can communicate with the BS via downlinks and uplinks. A "downlink" (or "forward link") refers to the communication link from the BS to the UE, while an "uplink" (or "backward link") refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), New Radio (NR) BS, 5G Node B, etc.

[0006] The aforementioned multiple access technologies have been adopted by various telecommunications standards to provide a common protocol, enabling different user equipment to communicate at the municipal, national, regional, and even global levels. NR (also known as 5G) is a set of enhancements to the LTE mobile standard issued by 3GPP. NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards by using Orthogonal Frequency Division Multiplexing (PFDM) with a Cyclic Prefix (CP) (CP-OFDMA) on the downlink (DL) and CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended PFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation. Further improvements to LTE, NR, and other wireless access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] In some aspects, a wireless communication method performed by a UE includes: during a dual-active protocol stack (DAPS)-based handover of the UE from a source primary cell group (MCG) to a target MCG, transmitting a Physical Uplink Shared Channel (PUSCH) repetition to a source base station associated with the source MCG in each of one or more time slots of the source MCG; and during the DAPS-based handover, performing an uplink transmission to the target MCG in one or more time slots to the target base station associated with the target MCG, wherein PUSCH repetitions associated with the source MCG that time overlap with the uplink transmission to the MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repetitions.

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

[0009] In some aspects, a UE for wireless communication includes: a memory; and one or more processors operatively coupled to the memory and configured to: during a DAPS-based handover of the UE from a source MCG to a target MCG, transmit a PUSCH repeat to a source base station associated with the source MCG in each of one or more time slots of the source MCG; and during the DAPS-based handover, perform an uplink transmission to the target MCG in one or more time slots to the target base station associated with the target MCG, wherein PUSCH repeats associated with the source MCG that time overlap with the uplink transmission to the MCG are cancelled, and the count of PUSCH repeats is at least partially based on the time slot of the source MCG associated with the cancelled PUSCH repeats.

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

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

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

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

[0014] In some aspects, a source device for wireless communication includes: a unit for transmitting to a UE a configuration associated with the number of PUSCH repetitions; and a unit for receiving PUSCH repetitions from the UE in each of one or more time slots of the source MCG associated with the source base station during a DAPS-based handover of the UE from a source MCG to a target MCG, wherein PUSCH repetitions that overlap temporally with uplink transmissions to the target MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repetitions.

[0015] The terms generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment and / or processing systems as substantially described herein with reference to the accompanying drawings and description.

[0016] The features and technical advantages of the examples according to this disclosure have been outlined quite extensively above to facilitate a better understanding of the following detailed description. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures to achieve the same purpose of this disclosure. Such equivalent structures do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and operation, and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0017] While aspects are described herein by way of example, those skilled in the art will understand that these aspects can be implemented in many different arrangements and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or package arrangements. For example, some aspects can be implemented via integrated chip embodiments or other devices based on non-modular components (e.g., end-user equipment, vehicles, communication equipment, computing devices, industrial equipment, retail / procurement equipment, medical devices, or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, or system-level components. Devices combining the described aspects and features may include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals may include multiple components (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders, or summers) for analog and digital purposes. The aspects described herein are intended to be practiced in devices, components, systems, distributed arrangements, or end-user equipment of various sizes, shapes, and configurations. Attached Figure Description

[0018] To gain a more detailed understanding of the foregoing features of this disclosure, a more specific description, briefly summarized above, can be obtained by referring to various aspects, some of which are illustrated in the accompanying drawings. However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should not be considered as limiting its scope, as the description may acknowledge other equally valid aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0019] Figure 1 This is a diagram illustrating an example of a wireless network according to this disclosure.

[0020] Figure 2 This is a diagram illustrating an example of a base station communicating with a UE in a wireless network according to the present disclosure.

[0021] Figure 3This is a diagram illustrating an example of PUSCH repeat type A counting according to this disclosure.

[0022] Figure 4 This is a diagram illustrating an example of DAPS-based switching according to this disclosure.

[0023] Figure 5 This is a diagram illustrating an example of uplink cancellation during a DAPS-based handover according to this disclosure.

[0024] Figure 6-10 This is a diagram illustrating an example of PUSCH repetition during switching according to this disclosure.

[0025] Figure 11-12 This is a diagram illustrating an exemplary process associated with PUSCH repetition during switching according to this disclosure.

[0026] Figure 13-14 This is a block diagram of an exemplary apparatus for wireless communication according to the present disclosure. Detailed Implementation

[0027] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be embodied in many different forms and should not be construed as limited to any particular structure or function presented throughout this disclosure. Rather, these aspects are provided to make this disclosure thorough and complete, and to fully communicate the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of the aspects set forth herein may be used to implement an apparatus or practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods that are practiced using other structures, functions, or structures and functions other than or different from the aspects of this disclosure set forth herein. It should be understood that any aspect of the disclosure herein may be embodied by one or more elements of the claims.

[0028] Several aspects of a telecommunications system will now be presented with reference to various devices and techniques. These devices and techniques will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system.

[0029] It should be noted that although the terms commonly associated with 5G or NR radio access technology (RAT) may be used to describe the aspects, the aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT, and / or RATs after 5G (e.g., 6G).

[0030] Figure 1 This is a diagram illustrating an example of a wireless network 100 according to this disclosure. The wireless network 100 may be or may include 5G (NR).

[0031] Elements of a network and / or an LTE network, and other examples. A wireless network 100 may include multiple base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d) 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 / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0032] A BS can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access for UEs associated with the femtocell (e.g., UEs in a Closed User Group (CSG)). A BS used for macrocells can be referred to as a macro BS. A BS used for picocells can be referred to as a pico BS. A BS used for femtocells can be referred to as a femtocell BS or a home BS. Figure 1 In the example shown, BS110a can be a macro BS of macro cell 102a, BS110b can be a pico BS of pico cell 102b, and BS110c can be a femto BS of femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “NR BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0033] In some respects, the cell is not necessarily stationary, and the geographical area of ​​the cell can move depending on the location of the mobile BS. In some respects, BSs can interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (e.g., direct physical connections or virtual networks).

[0034] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and transmit the data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1 In the example shown, relay BS110d can communicate with macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay BS can also be referred to as a relay station, relay base station, relay, etc.

[0035] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs), such as macro BSs, pico BSs, femto BSs, and relay BSs. These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs may have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs may have lower transmit power levels (e.g., 0.1 to 2 watts).

[0036] Network controller 130 can be coupled to a group of base stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0037] 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biometric sensor / device, a wearable device (smartwatch, 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 a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0038] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that can communicate with base stations, another device (e.g., a remote device), or some other entity. For example, a wireless node can provide connectivity to or to a network via a wired or wireless communication link (e.g., a wide area network such as the Internet or a cellular network). Some UEs can be considered Internet of Things (IoT) devices and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be contained within a housing that houses the components of UE 120 (e.g., processor components and / or memory components). In some aspects, the processor components and memory components can be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) can be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0039] Typically, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a wireless technology, air interface, etc. A frequency can also be referred to as a carrier, channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks may be deployed.

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

[0041] Devices in the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices in the wireless network 100 can communicate using an operating band with a first frequency range (FR1), which spans from 410 MHz to 7.125 GHz, and / or can communicate using an operating band with a second frequency range (FR2), which spans from 24.25 GHz to 52.6 GHz. Frequencies between FR1 and FR2 are sometimes referred to as intermediate frequency (IF) bands. 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, although it is different from the extremely high frequency (EHF) band (30 GHz–300 GHz) recognized as a “millimeter wave” band by the International Telecommunication Union (ITU). Therefore, unless otherwise explicitly stated, the terms "sub-6GHz" and the like, as used herein, can broadly refer to frequencies less than 6 GHz, frequencies within FR1, and / or intermediate frequency band frequencies (e.g., greater than 7.125 GHz). Similarly, unless otherwise explicitly stated, the terms "millimeter wave" and the like, as used herein, can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or intermediate frequency band frequencies (e.g., less than 24.25 GHz). It is anticipated that the frequencies included in FR1 and FR2 can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0042] As mentioned above, providing Figure 1 As an example. Other examples may be related to... Figure 1 The descriptions are different.

[0043] Figure 2This is a diagram illustrating an example 200 of a base station 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The base station 110 may be equipped with T antennas 234a to 234t, and the UE 120 may be equipped with R antennas 252a to 252r, wherein typically T ≥ 1 and R ≥ 1.

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

[0045] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, down-convert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can also process the input sample (e.g., for OFDM, etc.) to obtain the received symbols. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receive processor 258 can process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine parameters such as the Received Reference Signal Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Signal Quality (RSRQ), and Channel Quality Indicator (CQI). In some respects, one or more components of the UE 120 may be contained within housing 284.

[0046] Network controller 130 may include communication unit 294, controller / processor 290, and memory 292. Network controller 130 may include one or more devices, such as those in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

[0047] Antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may be included or contained in one or more antenna panels, antenna groups, antenna element sets, and / or antenna arrays. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include coplanar antenna element sets and / or non-coplanar antenna element sets. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include antenna elements within a single housing and / or antenna elements within multiple housings. Antenna panels, antenna groups, antenna element sets, and / or antenna arrays may include one or more antenna elements coupled to one or more transmitting and / or receiving components, such as... Figure 2 One or more components.

[0048] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., for reporting RSRP, RSSI, RSRQ, and / or CQI). The transmitting processor 264 can also generate reference symbols for one or more reference signals. Symbols from the transmitting processor 264 can be pre-encoded (if applicable) by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. In some aspects, the modulator and demodulator of UE 120 (e.g., MOD / DEMOD 254) can be included in the modem of UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of antenna 252, modulator and / or demodulator 254, MIMO detector 256, receive processor 258, transmit processor 264 and / or TX MIMO processor 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 referenced). Figure 6-12 (As described).

[0049] At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if used), and further processed by receiver processor 238 to obtain decoded data and control information transmitted by UE 120. Receiver processor 238 can provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Base station 110 may include communication unit 244 and communicate with network controller 130 via communication unit 244. Base station 110 may include scheduler 246 for scheduling UE 120 for downlink and / or uplink communications. In some aspects, the modulator and demodulator (e.g., MOD / DEMOD 232) of base station 110 may be included in the modem of base station 110. In some aspects, base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modulator and / or demodulator 232, MIMO detector 236, receiver processor 238, transmitter processor 220, and / or TXMIMO processor 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 referenced). Figure 6-12 (as described)

[0050] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2 Any other components may perform one or more techniques associated with PUSCH repetition during handover, as described in more detail elsewhere below. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component can perform or direct, for example Figure 11 Process 1100 Figure 12 The operation of process 1200 and / or other processes described herein. Memory 242 and 282 may store data and program code of base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120 (e.g., directly or after compilation, translation, and / or interpretation), may cause one or more processors, UE 120, and / or base station 110 to perform or direct, for example... Figure 11 Process 1100 Figure 12 The operation of process 1200 and / or other processes described herein. In some aspects, execution instructions may include run instructions, translation instructions, compilation instructions and / or interpretation instructions, as well as other examples.

[0051] In some aspects, the UE (e.g., UE 120) includes elements for transmitting PUSCH repetitions to a source base station associated with the source MCG in each of one or more time slots of the source MCG during a DAPS-based handover from the source MCG to the target MCG; and / or elements for performing uplink transmissions to the target MCG in one or more time slots to the target MCG to the target base station associated with the target MCG during a DAPS-based handover, wherein PUSCH repetitions associated with the source MCG that time overlap with the uplink transmissions to the MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the time slots of the source MCG associated with the cancelled PUSCH repetitions. Elements for the UE to perform the operations described herein may include one or more of, for example, 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.

[0052] In some respects, the UE includes a unit for canceling PUSCH duplication associated with the source MCG that overlaps in time with uplink transmissions to the MCG.

[0053] In some respects, the UE includes a unit for canceling PUSCH duplication associated with the source MCG, based at least in part on the lack of UE capability to perform power sharing between the source MCG and the target MCG during DAPS-based handover.

[0054] In some respects, the UE includes a unit for canceling PUSCH duplication associated with the source MCG, based at least in part on the UE capability to cancel uplink transmissions during DAPS-based handover.

[0055] In some respects, the UE includes a unit for canceling PUSCH duplication associated with the source MCG, at least in part based on intra-frequency DAPS-based handover.

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

[0057] Although Figure 2 The boxes in the diagram are shown as different components, but the functions described above with respect to these boxes can be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by or under the control of controller / processor 280.

[0058] As mentioned above, providing Figure 2 As an example. Other examples may be related to... Figure 2 The descriptions are different.

[0059] FR1 and FR2 can be associated with potential bottleneck channels. For example, in FR1, a potential bottleneck channel might be the PUSCH for Enhanced Mobile Broadband (eMBB). The eMBB PUSCH can be associated with Frequency Division Duplex (FDD) or Time Division Duplex (TDD) with a specific timeslot configuration (e.g., DDDSU, DDDSUDSUU, or DDDDUDDSUU, where "D" represents a downlink timeslot, "S" represents a special timeslot, and "U" represents an uplink timeslot). Another potential bottleneck channel in FR1 could be the PUSCH for Voice over Internet Protocol (VoIP). The VoIP PUSCH can be associated with FDD or TDD with a specific timeslot configuration (e.g., DDDSU or DDDSUDSUU). In FR2, a potential bottleneck channel might be the eMBB PUSCH, which may be associated with a specific timeslot configuration (e.g., DDDSU or DDSU). In FR2, another potential bottleneck channel could be the PUSCH of VoIP with a specific timeslot configuration (e.g., DDDSU or DDSU).

[0060] For PUSCH repetition type A, the UE can repeat transmission blocks across consecutive time slots, applying the same symbol allocation in each time slot. However, for PUSCH repetition type A, the number of PUSCH repetitions can be based at least in part on the number of available uplink / special time slots, because counting PUSCH repetitions at least in part on consecutive time slots may limit the actual number of PUSCH repetitions.

[0061] Figure 3 This is a diagram illustrating example 300 of the PUSCH repeat type A counting according to this disclosure.

[0062] As shown by reference numeral 302 in the attached figure, in PUSCH repetition counting for TDD (unpaired spectrum), multiple downlink slots, uplink slots, and / or special slots can be provided, at least in part, based on slot configuration. A first PUSCH repetition can be associated with a first slot (uplink slot or special slot) and have a count value of 0, and the count value for each subsequent slot (e.g., uplink slot, downlink slot, or special slot) can be incremented by one.

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

[0064] As shown by reference numeral 304 in the attached figure, in the PUSCH repetition count for FDD (paired spectrum), multiple PUSCH repetitions can occur at least partially based on the slot configuration. The first PUSCH repetition can be associated with a first slot and have a count value of 0, and the count value for each subsequent slot can be incremented by one.

[0065] As shown by reference numeral 306 in the attached figure, in PUSCH repetition counting for TDD (Paired Spectrum), multiple PUSCH repetitions can occur at least partially based on slot configuration. The first PUSCH repetition can be associated with the first slot and have a count value of 0. In this example, the count value does not increment by one for each consecutive slot, regardless of whether the next slot is an uplink slot, a downlink slot, or a special slot. Instead, the count value can increment only for subsequent uplink / special slots.

[0066] In this example, the first PUSCH repeat associated with the first time slot can correspond to a count value of 0, and the second PUSCH repeat associated with the second time slot can correspond to a count value of 1, even if the first and second time slots can be separated by non-uplink time slots (e.g., downlink time slots). Therefore, in this example, the number of PUSCH repeats can be counted based on available uplink / specific time slots, and the number of PUSCH repeats may not be counted based on consecutive time slots, which may limit the actual number of PUSCH repeats.

[0067] As mentioned above, it provides Figure 3 As an example. Other examples may be related to... Figure 3 The descriptions are different.

[0068] Figure 4 This is a diagram illustrating an example 400 of a DAPS-based handover according to this disclosure. DAPS-based handover may involve the UE, the source MCG (or source base station), the target MCG (or target base station), and user plane functions.

[0069] DAPS-based handover can reduce handover downtime by enabling the UE to connect to both the source MCG and the target MCG simultaneously during DAPS-based handover. DAPS-based handover can be applied to intra-band handover, intra-band inter-band handover, and / or inter-band inter-band handover.

[0070] like Figure 4As shown, in the first action, the UE can perform Radio Resource Management (RRM) reference signal measurements, where the RRM reference signal can be a Synchronization Signal Block (SSB) or a Channel State Information Reference Signal (CSI-RS). In the second action, an event trigger can occur at the UE, and in the third action, the UE can send a measurement report to the source MCG. The measurement report can indicate the RRM reference signal measurement. In the fourth action, the source MCG can perform a DAPS-based handover decision, at least in part, based on the measurement report. In the fifth action, the source MCG can prepare a target MCG for the DAPS-based handover.

[0071] In the sixth action, the source MCG can send a Radio Resource Control (RRC) reconfiguration message to the UE. The RRC reconfiguration message can indicate a handover command. In the seventh action, the UE can connect to the target MCG; and in the eighth action, the UE can send an RRC reconfiguration complete message to the target MCG. In the ninth action, the target MCG can execute a connection release decision for the source MCG; and in the tenth action, the source MCG and the target MCG can communicate a handover connection establishment completion indication. In the eleventh action, the target MCG can send a command to the UE to release the source MCG; and in the twelfth action, the UE can release the source MCG, at least in part, based on an indication received from the target MCG. In the thirteenth action, the UE can send an RRC reconfiguration complete message to the target MCG. In the fourteenth action, UE context information can be released along with the source MCG. In the fifteenth action, the UE can transmit data on the target MCG.

[0072] In this example of DAPS-based handover, during the handover of the UE from the source MCG to the target MCG, the UE can connect to both the source MCG and the target MCG. For example, between actions seven and eleven, the UE can continue to send and receive data on the source MCG, even while the UE can connect to the target MCG.

[0073] As mentioned above, providing Figure 4 As an example. Other examples may be related to... Figure 4 The descriptions are different.

[0074] For non-frequency DAPS-based handovers, the UE can transmit on the target cell (e.g., the target cell associated with the target MCG) and can cancel transmissions to the source cell (e.g., the source cell associated with the source MCG). In other words, the UE can transmit only on the target cell and can cancel transmissions to the source cell. If, at least in part, UE transmissions on the target and source cells are within overlapping time resources, the UE has not indicated power sharing capability between the source and target MCGs during a DAPS-based handover, and the UE indicates support for uplink transmission cancellation associated with the DAPS-based handover, the UE can transmit on the target cell and cancel transmissions to the source cell.

[0075] For intra-frequency DAPS-based handover, at least in part based on the fact that UE transmissions on the target cell and the source cell are in overlapping time resources, the UE can transmit on the target cell and cancel the transmission to the source cell.

[0076] Figure 5 This is a diagram illustrating example 500 of uplink cancellation during DAPS-based handover according to this disclosure.

[0077] like Figure 5 As shown, during DAPS-based handover, the UE can connect to both the source MCG and the target MCG. The UE can communicate with the source MCG at least partially based on a first timeslot configuration, and the UE can communicate with the target MCG at least partially based on a second timeslot configuration. In this example, the first timeslot configuration can be associated with: a first timeslot corresponding to an uplink transmission, a second timeslot corresponding to an uplink transmission, a third timeslot corresponding to a non-uplink transmission (e.g., a downlink transmission), and a fourth timeslot corresponding to an uplink transmission. The second timeslot configuration can be associated with: a first timeslot corresponding to a non-uplink transmission, a second timeslot corresponding to an uplink transmission, a third timeslot corresponding to an uplink transmission, and a fourth timeslot corresponding to a non-uplink transmission. In this example, since the second transmission associated with both the first and second timeslot configurations is an uplink transmission, the UE can cancel the second timeslot having an uplink transmission relative to the source MCG. In other words, during the second time slot associated with the first time slot configuration and the second time slot configuration, the UE can perform uplink transmission to the target MCG and can cancel uplink transmission to the source MCG.

[0078] As mentioned above, providing Figure 5 As an example. Other examples may be related to... Figure 5 The descriptions are different.

[0079] A UE can be handed over from a source MCG to a target MCG, at least in part, based on DAPS-based handover. During DAPS-based handover, the UE can communicate with both the source base station associated with the source MCG and the target base station associated with the target MCG. Regardless of whether the DAPS-based handover is intra-band DAPS-based, the UE can perform transmissions on the target MCG and cancel transmissions on the source MCG, at least in part, based on transmissions on the source MCG that overlap temporally with transmissions on the target MCG. However, when DAPS-based handover is enabled for a UE, UE behavior may be undefined for cases where cancellation of duplicate PUSCH transmissions on the source MCG is based at least in part on uplink transmissions on the target MCG.

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

[0081] Figure 6 This is a diagram illustrating example 600 of PUSCH repeating during switching according to this disclosure. Figure 6 As shown, 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, source base station, and target base station may be included in a wireless network such as wireless network 100.

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

[0083] In some respects, the UE can receive a configuration associated with the number of PUSCH repetitions from the source base station. The UE can send PUSCH repetitions to the source base station in one or more time slots of the source MCG, at least in part, based on the configuration.

[0084] In some respects, DAPS-based handover can be associated with FDD-to-FDD handover. In some respects, DAPS-based handover can be associated with TDD-to-TDD handover. In some respects, DAPS-based handover can be associated with TDD-to-FDD handover. In some respects, DAPS-based handover can be associated with FDD-to-TDD handover. Furthermore, FDD can be associated with paired spectrum, while TDD can be associated with unpaired spectrum.

[0085] As indicated by reference numeral 604, the UE can perform uplink transmissions to the target MCG in one or more time slots during DAPS-based handover to the target base station associated with the target MCG. The uplink transmissions can be Physical Uplink Control Channel (PUCCH) transmissions, PUSCH transmissions, Sounding Reference Signals (SRS), Physical Random Access Channel (PRACH) transmissions, or Message 3 (Msg3) PUSCH transmissions.

[0086] In some aspects, the UE can cancel PUSCH duplication associated with the source MCG that overlaps temporally with uplink transmissions to the MCG, wherein one or more time slots of the target MCG can be associated with uplink transmissions from the UE. In some aspects, the UE can cancel PUSCH duplication associated with the source MCG at least in part based on the lack of UE capability for power sharing between the source and target MCGs during DAPS-based handover. In some aspects, the UE can cancel PUSCH duplication associated with the source MCG at least in part based on the UE capability to cancel uplink transmissions during DAPS-based handover.

[0087] In some aspects, the UE may count PUSCH repetitions at least partially based on the time slots associated with canceled PUSCH repetitions in the source MCG. In one example, the UE may count PUSCH repetitions at least partially based on counting the time slots associated with canceled PUSCH repetitions in the source MCG. In another example, the UE may count PUSCH repetitions at least partially based on not counting the time slots associated with canceled PUSCH repetitions in the source MCG.

[0088] In some respects, PUSCH repetitions associated with the source MCG can completely overlap in time with uplink transmissions to the MCG. In other respects, PUSCH repetitions associated with the source MCG can partially overlap in time with uplink transmissions to the MCG.

[0089] In some respects, the number of PUSCH retransmissions available to the UE in the source MCG The PUSCH is transmitted repeatedly in each time slot, and because the time slot overlaps with the uplink transmission to the target MCG in time, the UE is not included in the number. PUSCH is sent repeatedly in a time slot within a time slot. The UE can select the number of times it contains the PUSCH repeats. The time slots within each time slot are counted or not. In terms of quantity... A time slot within a time slot can be a time slot associated with a canceled PUSCH repetition, because that time slot overlaps in time with the uplink transmission to the target MCG. In this example, This can represent a time slot repeatedly associated with PUSCH (e.g., an uplink time slot or a special time slot). Uplink transmissions to the target MCG can be associated with PUCCH, PUSCH, SRS, PRACH, or Msg3 PUSCH.

[0090] As mentioned above, providing Figure 6 As an example. Other examples may be related to... Figure 6 The descriptions are different.

[0091] Figure 7 This is a diagram illustrating example 700 of PUSCH repeating during switching according to this disclosure.

[0092] like Figure 7As shown, multiple time slots can be configured for repeated PUSCH transmissions to the source MCG, and multiple time slots can be configured for uplink transmissions to the target MCG (e.g., PUCCH transmissions, PUSCH transmissions, SRS transmissions, PRACH transmissions, and / or Msg3 PUSCH transmissions). The UE can perform repeated PUSCH transmissions to the source MCG on one or more time slots associated with it, and the UE can perform uplink transmissions to the target MCG on one or more time slots associated with it. However, for time slots associated with the source MCG that time-overlap with uplink transmissions in time slots associated with the target MCG, the UE can cancel repeated PUSCH transmissions in those time slots associated with the source MCG. In other words, the UE can cancel repeated PUSCH transmissions in those time slots and instead perform uplink transmissions to the target MCG.

[0093] A timeslot format configuration (e.g., configuration of uplink timeslots, downlink timeslots, and special timeslots) can be defined for the source MCG, and a timeslot format configuration can be defined for the target MCG. In an FDD-to-FDD handover, in a first counting scheme where the UE counts timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot can be associated with an incrementing count value, regardless of whether the subsequent timeslot is associated with a cancelled PUSCH retransmission. In a second counting scheme where the UE does not count timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot associated with a PUSCH retransmission (e.g., not a cancelled PUSCH retransmission) can be associated with an incrementing count value.

[0094] As an example, in the second counting scheme, slots 5 and 6 may not be counted because the duplicate transmission of PUSCH to the source MCG is canceled at least in part based on the uplink transmission to the target MCG.

[0095] As mentioned above, providing Figure 7 As an example. Other examples may be related to... Figure 7 The descriptions are different.

[0096] Figure 8 This is a diagram illustrating example 800 of PUSCH repeating during switching according to this disclosure.

[0097] like Figure 8As shown, a timeslot format configuration (e.g., configuration of uplink timeslots, downlink timeslots, and special timeslots) can be defined for the source MCG, and a timeslot format configuration can be defined for the target MCG. In a TDD-to-TDD handover, in a first counting scheme where the UE counts timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot can be associated with an incrementing count value, regardless of whether the subsequent timeslot is associated with a cancelled PUSCH retransmission. In a second counting scheme where the UE does not count timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot associated with a PUSCH retransmission (e.g., not a cancelled PUSCH retransmission) can be associated with an incrementing count value.

[0098] As mentioned above, providing Figure 8 As an example. Other examples may be related to... Figure 8 The descriptions are different.

[0099] Figure 9 This is a diagram illustrating example 900 of PUSCH repeating during switching according to this disclosure.

[0100] like Figure 9 As shown, a timeslot format configuration (e.g., configuration of uplink timeslots, downlink timeslots, and special timeslots) can be defined for the source MCG, and a timeslot format configuration can be defined for the target MCG. In a TDD-to-TDD handover, in a first counting scheme where the UE counts timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot can be associated with an incrementing count value, regardless of whether the subsequent timeslot is associated with a cancelled PUSCH retransmission. In a second counting scheme where the UE does not count timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot associated with a PUSCH retransmission (e.g., not a cancelled PUSCH retransmission) can be associated with an incrementing count value.

[0101] As mentioned above, providing Figure 9As an example. Other examples may be related to... Figure 9 The descriptions are different.

[0102] Figure 10 This is a diagram illustrating example 1000 of PUSCH repeating during switching according to this disclosure.

[0103] like Figure 10 As shown, a timeslot format configuration (e.g., configuration of uplink timeslots, downlink timeslots, and special timeslots) can be defined for the source MCG, and a timeslot format configuration can be defined for the target MCG. In a TDD-to-TDD handover, in a first counting scheme where the UE counts timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot can be associated with an incrementing count value, regardless of whether the subsequent timeslot is associated with a cancelled PUSCH retransmission. In a second counting scheme where the UE does not count timeslots of the source MCG associated with PUSCH retransmissions cancelled due to overlapping uplink transmissions to the target MCG in terms of time resources, the UE can associate the first timeslot with the first PUSCH retransmission with a count value of 0, and each subsequent timeslot associated with a PUSCH retransmission (e.g., not a cancelled PUSCH retransmission) can be associated with an incrementing count value.

[0104] As mentioned above, providing Figure 10 As an example. Other examples may be related to... Figure 10 The descriptions are different.

[0105] Figure 11 This is a diagram illustrating an exemplary process 1100 performed, for example, by a UE according to this disclosure. Exemplary process 1100 is an example in which a UE (e.g., UE 120) performs operations associated with PUSCH repetition during handover.

[0106] like Figure 11 As shown, in some aspects, process 1100 may include sending a PUSCH repetition to the source base station associated with the source MCG in each of one or more time slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG (box 1110). For example, the UE (e.g., using...) Figure 13 The transmission component 1304 described herein may send PUSCH repetitions to the source base station associated with the source MCG in each of one or more time slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG, as described above.

[0107] like Figure 11 As further shown, in some aspects, process 1100 may include performing uplink transmissions to the target MCG in one or more time slots to the target MCG during DAPS-based handover, wherein PUSCH repetitions associated with the source MCG that time overlap with the uplink transmissions to the MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the time slots of the source MCG associated with the cancelled PUSCH repetitions (box 1120). For example, the UE (e.g., using...) Figure 13 The transmission component 1304 described herein can perform uplink transmissions to the target MCG in one or more time slots to the target base station associated with the target MCG during DAPS-based handover, wherein PUSCH repetitions associated with the source MCG that overlap with the uplink transmissions to the MCG in time are cancelled, and the count of PUSCH repetitions is based at least in part on the time slots of the source MCG associated with the cancelled PUSCH repetitions, as described above.

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

[0109] In the first aspect, the counting of PUSCH repetitions includes counting the time slots associated with canceled PUSCH repetitions of the source MCG.

[0110] In the second aspect, either alone or in combination with the first aspect, the counting of PUSCH repetitions includes not counting the time slots associated with canceled PUSCH repetitions of the source MCG.

[0111] In the third aspect, either alone or in combination with one or more of the first and second aspects, the PUSCH repeat associated with the source MCG completely overlaps in time with the uplink transmission to the MCG.

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

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

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

[0115] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, PUSCH repetition is associated with PUSCH repetition type A, wherein the same symbol assignment is applied in each of one or more time slots of the source MCG.

[0116] In the eighth aspect, either alone or in combination with one or more of the first to seventh aspects, process 1100 includes canceling PUSCH duplications associated with the source MCG that overlap temporally with uplink transmissions to the MCG.

[0117] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1100 includes canceling PUSCH duplication associated with the source MCG based at least in part on the lack of UE capability to share power between the source MCG and the target MCG during DAPS-based handover.

[0118] In the tenth aspect, either alone or in combination with one or more of the first to ninth aspects, process 1100 includes canceling PUSCH duplication associated with the source MCG based at least in part on the UE's ability to cancel uplink transmissions during DAPS-based handover.

[0119] In the eleventh aspect, either alone or in combination with one or more of the first to tenth aspects, process 1100 includes canceling PUSCH repetition associated with the source MCG by at least partly based on intra-frequency DAPS-based switching.

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

[0121] Although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted in the diagram are those that are additional, fewer, different, or arranged differently. Alternatively, two or more boxes of process 1100 may be executed in parallel.

[0122] Figure 12This is a diagram illustrating an exemplary process 1200 performed, for example, by a source base station according to this disclosure. Exemplary process 1200 is an example in which a source base station (e.g., source base station 110) performs operations associated with PUSCH repetition during handover.

[0123] like Figure 12 As shown, in some aspects, process 1200 may include sending a configuration associated with the number of PUSCH repetitions to the UE (block 1210). For example, the source base station (e.g., using...) Figure 14 The transmission component 1404 described herein can send a configuration associated with the number of PUSCH repetitions to the UE, as described above.

[0124] like Figure 12 As further shown, in some aspects, process 1200 may include receiving PUSCH repeats from the UE in each of one or more time slots of the source MCG associated with the source base station during a DAPS-based handover of the UE from the source MCG to the target MCG, wherein PUSCH repeats that temporally overlap with uplink transmissions to the target MCG are cancelled, and the count of PUSCH repeats is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repeats (box 1220). For example, the source base station (e.g., using...) Figure 14 The receiving component 1402 described herein may receive PUSCH repeats from the UE in each of one or more time slots of the source MCG associated with the source base station during a DAPS-based handover of the UE from the source MCG to the target MCG, wherein PUSCH repeats that overlap temporally with uplink transmissions to the target MCG are cancelled, and the count of PUSCH repeats is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repeats, as described above.

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

[0126] In the first aspect, the count of PUSCH repetitions is based at least in part on the count of time slots associated with canceled PUSCH repetitions of the source MCG.

[0127] In the second aspect, either alone or in combination with the first aspect, the counting of PUSCH repetitions is based at least in part on the fact that time slots associated with canceled PUSCH repetitions of the source MCG are not counted.

[0128] Although Figure 12 An example box of process 1200 is shown, but in some respects, process 1200 may include... Figure 12The boxes depicted in the diagram are those that are additional, fewer, different, or arranged differently. Alternatively, two or more boxes in process 1200 may be executed in parallel.

[0129] Figure 13 This is a block diagram of an exemplary device 1300 for wireless communication. Device 1300 may be a UE, or a UE may include device 1300. In some aspects, device 1300 includes a receiving component 1302 and a transmitting component 1304, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1300 can use the receiving component 1302 and the transmitting component 1304 to communicate with another device 1306 (e.g., a UE, a base station, or another wireless communication device). Further shown, device 1300 may include a cancellation component 1308, and other examples.

[0130] In some respects, device 1300 can be configured to perform the functions described herein. Figure 6-10 One or more operations described herein. Alternatively or concurrently, the device 1300 may be configured to perform one or more processes described herein, such as... Figure 11 The process 1100. In some respects, Figure 13 The device 1300 and / or one or more components shown may include the above-described combination. Figure 2 One or more components of the UE as described. Alternatively or in addition, Figure 13 One or more components shown can be combined above. Figure 2 The description is implemented within one or more components. Alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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.

[0131] Receiver 1302 may receive communications from device 1306, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other components of device 1306. In some aspects, receiver 1302 may include combinations of... Figure 2 One or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memories, or combinations thereof in the UE described above.

[0132] Transmitting component 1304 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1306 can generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1306. In some aspects, transmitting component 1304 can perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signal to device 1306. In some aspects, transmitting component 1304 may include combinations of... Figure 2 The UE described above includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1304 may be co-located with the receive component 1302 in a transceiver.

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

[0134] Cancellation component 1308 can cancel PUSCH duplication associated with the source MCG that overlaps in time with uplink transmissions to the MCG. Cancellation component 1308 can cancel PUSCH duplication associated with the source MCG at least in part based on the lack of UE capability to perform power sharing between the source and target MCGs during DAPS-based handover. Cancellation component 1308 can cancel PUSCH duplication associated with the source MCG at least in part based on the UE capability to cancel uplink transmissions during DAPS-based handover. Cancellation component 1308 can cancel PUSCH duplication associated with the source MCG at least in part based on intra-frequency DAPS-based handover.

[0135] supply Figure 13 The number and arrangement of components shown are for illustrative purposes only. In practice, with... Figure 13 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 13 The two or more components shown can be implemented in a single component, or Figure 13The single component shown can be implemented as multiple distributed components. Alternatively, Figure 13 The set (one or more) components shown can perform one or more functions, which are described as being performed by... Figure 13 Another set of components is executed as shown.

[0136] Figure 14 This is a block diagram of an exemplary device 1400 for wireless communication. Device 1400 may be a source base station, or a source base station may include device 1400. In some aspects, device 1400 includes a receiving component 1402 and a transmitting component 1404, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1400 can use the receiving component 1402 and the transmitting component 1404 to communicate with another device 1406 (e.g., a UE, a base station, or another wireless communication device).

[0137] In some respects, device 1400 can be configured to perform the functions described herein. Figure 6-10 One or more operations described herein. Alternatively or concurrently, the device 1400 may be configured to perform one or more processes described herein, such as... Figure 12 The process is 1200. In some respects, Figure 14 The device 1400 and / or one or more components shown may include the above-described combination. Figure 2 One or more components of the described base station. Alternatively, Figure 14 One or more components shown can be combined above. Figure 2 The description is implemented within one or more components. Alternatively, one or more components in the set of components may be implemented at least partially as software stored in 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.

[0138] Receiver 1402 may receive communications from device 1406, such as reference signals, control information, data communications, or combinations thereof. Receiver 1402 may provide the received communications to one or more other components of device 1406. In some aspects, receiver 1402 may perform signal processing on the received communications (e.g., filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signal to one or more other components of device 1406. In some aspects, receiver 1402 may include combinations of... Figure 2 One or more antennas, demodulators, MIMO detectors, receiver processors, controllers / processors, memories, or combinations thereof in the base station described above.

[0139] Transmitting component 1404 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1406. In some aspects, one or more other components of device 1406 can generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1406. In some aspects, transmitting component 1404 can perform signal processing (e.g., filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding) on ​​the generated communications and can transmit the processed signal to device 1406. In some aspects, transmitting component 1404 may include combinations of... Figure 2 The base station described above includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers / processors, memory, or combinations thereof. In some aspects, the transmit component 1404 may be co-located with the receive component 1402 in a transceiver.

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

[0141] supply Figure 14 The number and arrangement of components shown are for illustrative purposes only. In practice, with... Figure 14 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged differently. Furthermore, Figure 14 The two or more components shown can be implemented in a single component, or Figure 14 The single component shown can be implemented as multiple distributed components. Alternatively, Figure 14 The set (one or more) components shown can perform one or more functions, which are described as being performed by... Figure 14 Another set of components is executed as shown.

[0142] The following provides an overview of some aspects of this disclosure:

[0143] Aspect 1: A wireless communication method performed by a user equipment (UE) comprising: during a dual-active protocol stack (DAPS)-based handover of the UE from a source primary cell group (MCG) to a target MCG, transmitting a Physical Uplink Shared Channel (PUSCH) repetition to a source base station associated with the source MCG in each of one or more time slots of the source MCG; and performing an uplink transmission to the target MCG in one or more time slots to the target MCG to the target base station associated with the target MCG during the DAPS-based handover, wherein PUSCH repetitions associated with the source MCG that time overlap with the uplink transmission to the MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repetitions.

[0144] Aspect 2: According to the method of Aspect 1, the counting of PUSCH repetitions includes counting the time slots of the source MCG associated with the canceled PUSCH repetitions.

[0145] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the counting of PUSCH repetitions includes not counting the time slots of the source MCG associated with the canceled PUSCH repetitions.

[0146] Aspect 4: According to the method of any one of Aspects 1 to 3, wherein the PUSCH repetition associated with the source MCG and the uplink transmission to the MCG completely overlap in time.

[0147] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the PUSCH repetition associated with the source MCG partially overlaps in time with the uplink transmission to the MCG.

[0148] Aspect 6: According to any one of Aspects 1 to 5, wherein during DAPS-based handover, the uplink transmission in one or more time slots of the target MCG is one of the following: physical uplink control channel transmission, PUSCH transmission, sounding reference signal, physical random access channel transmission, or message 3 (Msg3) PUSCH transmission.

[0149] Aspect 7: According to the method of any one of Aspects 1 to 6, wherein the DAPS-based handover is associated with frequency division duplex (FDD) to FDD handover, time division duplex (TDD) to TDD handover, TDD to FDD handover, or FDD to TDD handover, wherein FDD is associated with paired spectrum and TDD is associated with unpaired spectrum.

[0150] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the PUSCH repetition is associated with PUSCH repetition type A, wherein the same symbol assignment is applied in each slot of one or more slots of the source MCG.

[0151] Aspect 9: The method according to any one of Aspects 1 to 8 further includes: canceling PUSCH duplication associated with the source MCG that overlaps in time with the uplink transmission to the MCG.

[0152] Aspect 10: The method according to any one of Aspects 1 to 9 further includes: canceling PUSCH duplication associated with the source MCG based at least in part on the lack of UE capability to share power between the source MCG and the target MCG during DAPS-based handover.

[0153] Aspect 11: The method according to any one of Aspects 1 to 10 further includes: canceling PUSCH duplication associated with the source MCG based at least in part on the UE's ability to cancel uplink transmissions during DAPS-based handover.

[0154] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: canceling PUSCH repetition associated with the source MCG based at least in part on intra-frequency DAPS-based switching.

[0155] Aspect 13: The method according to any one of Aspects 1 to 12, wherein: one or more time slots of the source MCG include one or more uplink time slots or special time slots; and one or more time slots of the target MCG include one or more uplink time slots or special time slots.

[0156] Aspect 14. A wireless communication method performed by a source base station, comprising: transmitting to a user equipment (UE) a configuration associated with the number of Physical Uplink Shared Channel (PUSCH) repetitions; and during a handover of the UE from a source primary cell group (MCG) to a target MCG based on a dual-active protocol stack (DAPS), receiving PUSCH repetitions from the UE in each of one or more time slots of the source MCG associated with the source base station, wherein PUSCH repetitions that temporally overlap with uplink transmissions to the target MCG are cancelled, and the count of PUSCH repetitions is based at least in part on the time slots of the source MCG associated with the cancelled PUSCH repetitions.

[0157] Aspect 15: According to the method of aspect 14, wherein the count of PUSCH repetitions is based at least in part on the count of time slots associated with canceled PUSCH repetitions of the source MCG.

[0158] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the counting of PUSCH repetitions is based at least in part on the fact that the time slots associated with the canceled PUSCH repetitions of the source MCG are not counted.

[0159] Aspect 17: An apparatus for wireless communication in a storage area, 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 the methods of one or more aspects of aspects 1-13.

[0160] Aspect 18: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 1-13.

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

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

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

[0164] Aspect 22: An apparatus for wireless communication at 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 one or more aspects of aspects 14-16.

[0165] Aspect 23: An apparatus for wireless communication, comprising a memory and one or more processors coupled to the memory, the memory and the one or more processors being configured to perform the methods of one or more aspects of aspects 14-16.

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

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

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

[0169] The foregoing disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or may be derived from practice in these aspects.

[0170] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. "Software" should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, programs and / or functions, and other examples, whether referred to as software, firmware, middleware, microcode, hardware description languages, or otherwise. As used herein, processors are implemented in hardware and / or a combination of hardware and software. It is evident that the systems and / or methods described herein can be implemented in various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these aspects. Therefore, while this document describes the operation and behavior of systems and / or methods without reference to specific software code, it should be understood that software and hardware can be designed to implement systems and / or methods, at least in part, based on the descriptions herein.

[0171] As used in this article, depending on the context, a threshold means a value that is 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.

[0172] Even if a specific combination of features is recited in the claims and / or disclosed in the specification, such combinations are not intended to limit the disclosure of aspects. In fact, many of these features can be combined in ways not specifically recited in the claims and / or disclosed in the specification. While each dependent claim listed below may depend directly on only one claim, the disclosure of aspects includes combinations of each dependent claim with every other claim in the claim set. As used herein, the phrase “at least one” in the list of items refers to any combination of these items, including single members. For 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).

[0173] Unless explicitly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items combined with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and are interchangeable with “one or more.” If only one item is intended to be used, the phrase “only one item” or similar language is used. Furthermore, as used herein, the terms “has,” “have,” “having,” etc., are intended to be open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and may be used interchangeably with “and / or” unless otherwise expressly stated (e.g., if used in combination with “any one” or “only one”).

Claims

1. A wireless communication method performed by a user equipment (UE), comprising: During the handover of the UE from the source primary cell group (MCG) to the target MCG based on the dual active protocol stack (DAPS), in each of one or more time slots of the source MCG, the Physical Uplink Shared Channel (PUSCH) is repeatedly sent to the source base station associated with the source MCG. as well as During the DAPS-based handover, uplink transmissions to the target MCG are performed in one or more time slots to the target MCG, wherein PUSCH repetitions associated with the source MCG that time overlap with the uplink transmissions to the MCG are cancelled, and the count of the PUSCH repetitions is based at least in part on the time slots of the source MCG associated with the cancelled PUSCH repetitions.

2. The method according to claim 1, wherein, The counting of PUSCH repetitions includes counting the time slots of the source MCG associated with the cancelled PUSCH repetitions.

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

4. The method according to claim 1, wherein, The PUSCH repeat associated with the source MCG completely overlaps in time with the uplink transmission to the MCG.

5. The method according to claim 1, wherein, The PUSCH repeat associated with the source MCG partially overlaps in time with the uplink transmission to the MCG.

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

7. The method according to claim 1, wherein, The DAPS-based handover is associated with frequency division duplex (FDD) to FDD handover, time division duplex (TDD) to TDD handover, TDD to FDD handover, or FDD to TDD handover, wherein FDD is associated with paired spectrum and TDD is associated with unpaired spectrum.

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

9. The method according to claim 1, further comprising: Cancel the PUSCH duplication associated with the source MCG that overlaps in time with the uplink transmission to the MCG.

10. The method according to claim 1, further comprising: The PUSCH duplication associated with the source MCG is cancelled, at least in part, due to the lack of UE capability for power sharing between the source MCG and the target MCG during the DAPS-based handover.

11. The method according to claim 1, further comprising: The PUSCH duplication associated with the source MCG is cancelled at least in part based on the UE's ability to cancel uplink transmissions during the DAPS-based handover.

12. The method according to claim 1, further comprising: The PUSCH repetition associated with the source MCG is canceled, at least in part, based on intra-frequency DAPS-based switching.

13. The method according to claim 1, wherein: One or more time slots of the source MCG include one or more time slots from the uplink time slots or special time slots; and One or more time slots of the target MCG include one or more time slots from the uplink time slots or special time slots.

14. A wireless communication method performed by a source base station, comprising: Send a configuration associated with the number of Physical Uplink Shared Channel (PUSCH) repetitions to the User Equipment (UE); as well as During a handover of the UE from a source primary cell group (MCG) associated with the source base station to a target MCG based on a dual-active protocol stack (DAPS), a PUSCH repeat is received from the UE in each of one or more time slots of the source MCG, wherein PUSCH repeats that time overlap with uplink transmissions to the target MCG are cancelled, and the count of the PUSCH repeats is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repeats.

15. The method according to claim 14, wherein, The count of PUSCH repetitions is based at least in part on the count of the time slots associated with the canceled PUSCH repetitions of the source MCG.

16. The method of claim 14, wherein, The count of PUSCH repetitions is based at least in part on the fact that the time slots associated with the canceled PUSCH repetitions of the source MCG are not counted.

17. A user equipment (UE) for wireless communication, comprising: Memory; as well as One or more processors, operatively coupled to the memory, and configured to: During the handover of the UE from the source primary cell group (MCG) to the target MCG based on the dual active protocol stack (DAPS), in each of one or more time slots of the source MCG, the Physical Uplink Shared Channel (PUSCH) is repeatedly sent to the source base station associated with the source MCG. as well as During the DAPS-based handover, uplink transmissions to the target MCG are performed in one or more time slots to the target MCG, wherein PUSCH repetitions associated with the source MCG that time overlap with the uplink transmissions to the MCG are cancelled, and the count of the PUSCH repetitions is based at least in part on the time slots of the source MCG associated with the cancelled PUSCH repetitions.

18. The UE according to claim 17, wherein, The counting of PUSCH repetitions includes counting the time slots of the source MCG associated with the cancelled PUSCH repetitions.

19. The UE according to claim 17, wherein, The counting of PUSCH repetitions includes not counting the time slots associated with the canceled PUSCH repetitions of the source MCG.

20. The UE according to claim 17, wherein, During the DAPS-based handover, the uplink transmission in one or more time slots of the target MCG is one of the following: physical uplink control channel transmission, PUSCH transmission, sounding reference signal, physical random access channel transmission, or message 3 (Msg3) PUSCH transmission.

21. The UE according to claim 17, wherein, The DAPS-based handover is associated with frequency division duplex (FDD) to FDD handover, time division duplex (TDD) to TDD handover, TDD to FDD handover, or FDD to TDD handover, wherein FDD is associated with paired spectrum and TDD is associated with unpaired spectrum.

22. The UE according to claim 17, wherein, The PUSCH repeat is associated with PUSCH repeat type A, in which the same symbol allocation is applied in each of the one or more time slots of the source MCG.

23. The UE according to claim 17, wherein, The one or more processors are further configured to: Cancel the PUSCH duplication associated with the source MCG that overlaps in time with the uplink transmission to the MCG.

24. The UE according to claim 17, wherein, The one or more processors are further configured to: The PUSCH duplication associated with the source MCG is cancelled, at least in part, due to the lack of UE capability for power sharing between the source MCG and the target MCG during the DAPS-based handover.

25. The UE according to claim 17, wherein, The one or more processors are further configured to: The PUSCH duplication associated with the source MCG is cancelled at least in part based on the UE's ability to cancel uplink transmissions during the DAPS-based handover.

26. The UE according to claim 17, wherein, The one or more processors are further configured to: The PUSCH repetition associated with the source MCG is canceled, at least in part, based on intra-frequency DAPS-based switching.

27. The UE according to claim 17, wherein: One or more time slots of the source MCG include one or more time slots from the uplink time slots or special time slots; and One or more time slots of the target MCG include one or more time slots from the uplink time slots or special time slots.

28. A source base station for wireless communication, comprising: Memory; as well as One or more processors, operatively coupled to the memory, and configured to: Send a configuration associated with the number of Physical Uplink Shared Channel (PUSCH) repetitions to the User Equipment (UE); and During a handover of the UE from a source primary cell group (MCG) associated with the source base station to a target MCG based on a dual-active protocol stack (DAPS), a PUSCH repeat is received from the UE in each of one or more time slots of the source MCG, wherein PUSCH repeats that time overlap with uplink transmissions to the target MCG are cancelled, and the count of the PUSCH repeats is based at least in part on the time slot of the source MCG associated with the cancelled PUSCH repeats.

29. The source base station according to claim 28, wherein, The count of PUSCH repetitions is based at least in part on the count of the time slots associated with the canceled PUSCH repetitions of the source MCG.

30. The source base station according to claim 28, wherein, The count of PUSCH repetitions is based at least in part on the fact that the time slots associated with the canceled PUSCH repetitions of the source MCG are not counted.

Images