JP2024512486A - Physical uplink shared channel repetition during handover - Google Patents

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) communicates with a source base station associated with a source master cell group (MCG) one or more slots of the source MCG during handover of the UE from the source MCG to the target MCG. Physical Uplink Shared Channel (PUSCH) repetitions may be transmitted. The UE may perform uplink transmissions in one or more slots of the target MCG during handover to a target base station associated with the target MCG, overlapping in time with uplink transmissions to the MCG. The PUSCH repetition associated with the source MCG to cancel is canceled, and the count of PUSCH repetitions is based at least in part on the slot of the source MCG associated with the canceled PUSCH repetition. A number of other aspects are described.

Description

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

TECHNICAL FIELD Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for physical uplink shared channel (PUSCH) repetition during handover.

Wireless communication systems are widely deployed to provide various telecommunications services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access techniques that can support communication with multiple users by sharing available system resources (eg, bandwidth, transmit power, etc.). Examples of such multiple access technologies are 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 Includes division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long-term evolution (LTE). LTE/LTE Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP(R)).

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

The multiple access techniques described above have been adopted in various telecommunication standards to provide a common protocol that allows different user equipment to communicate on a city, national, regional, or even global scale. NR, sometimes referred to as 5G, is a set of extensions to the LTE mobile standard published by 3GPP. NR improves spectral efficiency, lowers cost, improves service, utilizes new spectrum, and orthogonal frequency division with cyclic prefix (CP) on the downlink (DL). multiplexing (OFDM) (CP-OFDM) and on the uplink (UL) using CP-OFDM and/or SC-FDM (e.g. also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM) ) and by better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Designed. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies remain useful.

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

In some aspects, a method of wireless communication performed by a source base station includes transmitting to a UE a configuration associated with an amount of PUSCH repetitions; receiving PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station during base handover, the PUSCH repetitions temporally overlapping with uplink transmissions to the target MCG; and the count of canceled PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions.

In some aspects, a UE for wireless communication includes memory and one or more processors operably coupled to the memory, the one or more processors having a source associated with a source MCG. transmitting a PUSCH repetition in each of the one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG to the base station; and to the target base station associated with the target MCG; performing uplink transmissions in one or more slots of a target MCG during a DAPS-based handover, the PUSCH repetitions associated with the source MCG temporally overlapping with uplink transmissions to the MCG; and a count of the canceled PUSCH repetition is based at least in part on a slot of the source MCG associated with the canceled PUSCH repetition.

In some aspects, a source base station for wireless communication includes memory and one or more processors operably coupled to the memory, the one or more processors transmitting PUSCH repetitions to a UE. and in each of one or more 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. receiving a PUSCH repetition that overlaps in time with an uplink transmission to a target MCG, wherein the PUSCH repetition count is at least equal to the slot of the source MCG associated with the canceled PUSCH repetition; and configured to receive and receive data based in part on the data.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication, when executed by one or more processors of a UE, transmits instructions to a source base station associated with a source MCG; transmitting PUSCH repetitions in each of one or more slots of the source MCG during a DAPS-based handover of a UE from a source MCG to a target MCG; performing uplink transmissions in one or more slots of a target MCG during handover of the PUSCH, wherein PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG are canceled; The count of repetitions includes one or more instructions for causing the UE to perform based at least in part on the slot of the source MCG associated with the canceled PUSCH repetition.

In some aspects, a non-transitory computer-readable medium storing a set of instructions for wireless communication that, when executed by one or more processors of a source base station, is associated with an amount of PUSCH repetitions to a UE. and receiving, from the UE, PUSCH repetitions in each of the one or more 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. PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled, the count of PUSCH repetitions being based at least in part on the slots of the source MCG associated with the canceled PUSCH repetitions; , receiving, and one or more instructions for causing the source base station to perform the following operations.

In some aspects, an apparatus for wireless communication communicates with a source base station associated with a source MCG one or more slots of the source MCG during a DAPS-based handover of the apparatus from the source MCG to the target MCG. means for transmitting PUSCH repetitions in each and means for performing uplink transmission in one or more slots of the target MCG during a DAPS-based handover to a target base station associated with the target MCG; A PUSCH repetition associated with a source MCG that overlaps in time with an uplink transmission to the MCG is canceled, and the count of PUSCH repetitions is at least partially in the slot of the source MCG associated with the canceled PUSCH repetition. based on, including means.

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

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

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

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

In order that the above-listed features of the present disclosure may be understood in detail, a more detailed description, briefly summarized above, may be obtained by reference to the embodiments, some of which are illustrated in the accompanying drawings. There may be cases where However, the accompanying drawings depict only some typical aspects of the disclosure and therefore should not be considered a limitation on its scope, as the description may admit other equally effective aspects. Please note that there is no. The same reference numbers in different drawings may identify the same or similar elements.

1 is a diagram illustrating an example wireless network according to the present disclosure. FIG. FIG. 2 is a diagram illustrating an example of a base station communicating with a UE in a wireless network in accordance with the present disclosure. FIG. 3 is a diagram illustrating an example of a PUSCH repetition type A count in accordance with the present disclosure. FIG. 2 is a diagram illustrating an example of DAPS-based handover according to the present disclosure. FIG. 3 illustrates an example of uplink cancellation in DAPS-based handover according to the present disclosure. FIG. 3 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. FIG. 3 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. FIG. 3 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. FIG. 3 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. FIG. 3 illustrates an example associated with PUSCH repetition during handover in accordance with the present disclosure. FIG. 3 illustrates an example process associated with PUSCH repetition during handover in accordance with this disclosure. FIG. 3 illustrates an example process associated with PUSCH repetition during handover in accordance with this disclosure. 1 is a block diagram of an example apparatus for wireless communication in accordance with the present disclosure. FIG. 1 is a block diagram of an example apparatus for wireless communication in accordance with the present disclosure. FIG.

Various aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure may, however, be embodied in many different forms and should not be construed as limited to any specific structure or functionality presented throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Based on the teachings herein, the scope of this disclosure, whether implemented independently of or in combination with any other aspects of this disclosure, includes: It will be appreciated by those skilled in the art that any aspect of the disclosure disclosed herein is encompassed. For example, an apparatus may be implemented or a method practiced using any number of the aspects described herein. In addition, the scope of the disclosure may be practiced using other structures, features, or structures and features in addition to or in addition to the various aspects of the disclosure described herein. It is intended to include such devices or methods. It is to be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Next, several aspects of telecommunications systems are presented with reference to various devices and techniques. These devices and techniques are illustrated in the detailed description below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). is shown. These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

Although aspects may be described herein using terminology commonly associated with 5G or NR radio access technologies (RATs), aspects of the present disclosure apply to 3G RATs, 4G RATs, and/or NR radio access technologies (RATs). Note that it may also be applied to other RATs, such as post-5G (eg, 6G) RATs.

FIG. 1 is a diagram illustrating an example wireless network 100 according to the present disclosure. Wireless network 100 may be an element of or include a 5G (NR) network and/or an LTE network, among other examples. Wireless network 100 may include several 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 may provide communication coverage for a particular geographic area. In 3GPP®, the term "cell" may refer to the coverage area of a BS and/or the BS subsystem serving this coverage area, depending on the context in which the term is used.

A BS may provide communication coverage to macro cells, pico cells, femto cells, and/or other types of cells. A macro cell may cover a relatively large geographic area (eg, several kilometers radius) and may allow unrestricted access by UEs subscribing to the service. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs subscribing to the service. Femtocells can cover a relatively small geographic area (e.g., your home) and provide limited access by UEs that have an association with the femtocell (e.g., UEs in a restricted subscriber group (CSG)). It can be possible. A BS for a macro cell is sometimes called a macro BS. A BS for pico cells is sometimes called a pico BS. A BS for femto cells may be called femto BS or home BS. In the example shown in FIG. 1, BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. It's okay. A BS may support one or more (eg, three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" are used interchangeably herein. may be used for.

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

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

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

Network controller 130 may couple to a set of BSs and may provide coordination and control for these BSs. Network controller 130 may communicate with the BS via backhaul. BSs may also communicate with each other, directly or indirectly, eg, via wireless or wireline backhaul.

UEs 120 (eg, 120a, 120b, 120c) may be distributed throughout 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. The UE may include cellular phones (e.g., smartphones), personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, tablets, cameras, gaming devices, Netbooks, smartbooks, ultrabooks, medical devices or equipment, biosensors/devices, wearable devices (smartwatches, smart clothing, smart glasses, smart wristbands, smart jewelry (e.g. smart rings, smart bracelets)), entertainment devices (e.g., music or video devices, or satellite radio), vehicle components or sensors, smart meters/sensors, industrial manufacturing equipment, global positioning system devices, or configured to communicate via a wireless or wired medium. or any other suitable device.

Some UEs may be considered machine type communication (MTC) UEs, or evolved or enhanced machine type communication (eMTC) UEs. MTC UE and eMTC UE are, for example, robots, drones, remote devices, sensors, meters, monitors, and/or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. including. A wireless node may provide connectivity for or to a network (eg, the Internet or a wide area network such as a cellular network), eg, via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices and/or may be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs may be considered customer premises equipment (CPE). UE 120 may be included within a housing that houses components of UE 120, such as processor components and/or memory components. In some aspects, processor components and memory components may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., memory) may be operably coupled, communicatively coupled, electronically coupled, and/or electrically coupled. May be combined.

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

In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) use one or more sidelink channels (e.g., using base station 110 as a medium to communicate with each other). may also be used for direct communication (without using For example, the UE 120 communicates peer-to-peer (P2P) communications, device-to-device (D2D) communications, vehicle-to-everything (V2X) protocols (which may include, for example, vehicle-to-vehicle (V2V) protocols or vehicle-to-infrastructure (V2I) protocols), and / Or may communicate using a mesh network. 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.

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

As mentioned above, FIG. 1 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 2 is a diagram illustrating an example 200 of base station 110 in communication with UE 120 in wireless network 100, in accordance with this disclosure. Base station 110 may be equipped with T antennas 234a-234t, and UE 120 may be equipped with R antennas 252a-252r, where generally T≧1 and R≧1.

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

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

Network controller 130 may include a communications unit 294, a controller/processor 290, and memory 292. Network controller 130 may include, for example, one or more devices in a core network. Network controller 130 may communicate with base station 110 via communication unit 294.

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

On the uplink, at UE 120, transmit processor 264 receives data from data source 262 and control information (e.g., for reporting including RSRP, RSSI, RSRQ, and/or CQI) from controller/processor 280. , may be processed. Transmit processor 264 may also generate reference symbols for one or more reference signals. Symbols from transmit processor 264 are precoded by TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to base station 110. May be sent. In some aspects, a modulator and demodulator (eg, MOD/DEMOD 254) for UE 120 may be included in a modem for UE 120. In some aspects, UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modulator and/or demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and/or a TX MIMO processor 266. The transceiver may be coupled to a processor (e.g., controller/processor 280) to perform any aspect of the methods described herein (e.g., as described with reference to FIGS. 6-12). and memory 282.

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

The base station 110 controller/processor 240, the UE 120 controller/processor 280, and/or any other components of FIG. One or more techniques associated with PUSCH repetition may be performed. For example, controller/processor 240 of base station 110, controller/processor 280 of UE 120, and/or any other component of FIG. It may also perform or direct the operations of other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and/or memory 282 may include non-transitory computer readable media that stores one or more instructions (eg, code and/or program code) for wireless communication. For example, when the one or more instructions are executed (e.g., immediately or after being compiled, converted, and/or interpreted) by one or more processors of base station 110 and/or UE 120, one or more causing the plurality of processors, UE 120, and/or base station 110 to perform or direct operations of, for example, process 1100 of FIG. 11, process 1200 of FIG. 12, and/or other processes as described herein; be able to. In some aspects, executing the instructions may include invoking the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a UE (e.g., UE 120) informs a source base station associated with the source MCG of one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG. means for transmitting PUSCH repetitions in each and/or uplink transmission in one or more slots of the target MCG during a DAPS-based handover to a target base station associated with the target MCG; means for canceling a PUSCH repetition associated with a source MCG that overlaps in time with an uplink transmission to the MCG, and wherein the count of PUSCH repetitions is equal to or less than the slot of the source MCG associated with the canceled PUSCH repetition; and means based at least in part on. The means for the UE to perform the operations described herein include, for example, an antenna 252, a demodulator 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a modulator 254, a controller /processor 280, or memory 282.

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

In some aspects, the UE reduces PUSCH repetitions associated with the source MCG based at least in part on the UE's lack of capability for power sharing between the source MCG and the target MCG during a DAPS-based handover. Includes means for cancellation.

In some aspects, the UE includes means for canceling PUSCH repetitions associated with the source MCG based at least in part on the UE's ability to cancel uplink transmissions during a DAPS-based handover.

In some aspects, the UE includes means for canceling PUSCH repetitions associated with the source MCG based at least in part on intra-frequency DAPS-based handovers.

In some aspects, the source base station (e.g., base station 110a) includes means for transmitting to the UE a configuration associated with an amount of PUSCH repetitions, and/or a configuration associated with the amount of PUSCH repetitions from the UE from the source MCG to the target MCG. means for receiving PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station during a DAPS-based handover of a UE, the means for receiving PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station, the method comprising: PUSCH repetitions that overlap the PUSCH repetitions are canceled, and the count of PUSCH repetitions is based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions. The means for the source base station to perform the operations described herein include, 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.

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

As mentioned above, FIG. 2 is provided as an example. Other examples may differ from those described with respect to FIG.

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

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

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

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

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

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

As indicated by reference numeral 306, the PUSCH repetition count for TDD (versus spectrum) may include multiple PUSCH repetitions based at least in part on the slot configuration. The first PUSCH repetition is associated with the first slot and may have a count value of zero. In this example, the count value does not need to be incremented by 1 for each consecutive slot, regardless of whether the next slot is an uplink slot, a downlink slot, or a special slot. good. Rather, the count value need only be incremented for subsequent uplink/special slots.

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

As mentioned above, FIG. 3 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 4 is a diagram illustrating an example 400 of DAPS-based handover in accordance with the present disclosure. A DAPS-based handover may require a UE, a source MCG (or source base station), a target MCG (or target base station), and user plane functionality.

DAPS-based handover may reduce handover interruption time by allowing a UE to connect to both a source MCG and a target MCG simultaneously during a DAPS-based handover. DAPS-based handovers may be applicable to intra-frequency handovers, intra-band inter-frequency handovers, and/or inter-band inter-frequency handovers.

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

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

In this example of DAPS-based handover, the UE may be connected to both the source MCG and the target MCG during handover of the UE from the source MCG to the target MCG. For example, between actions 7 and 11, the UE may continue transmitting and receiving data on the source MCG even though the UE may also be connected to the target MCG.

As mentioned above, FIG. 4 is provided as an example. Other examples may differ from those described with respect to FIG.

For non-intra-frequency DAPS-based handovers, the UE may transmit on the target cell (e.g., the target cell associated with the target MCG) and the UE may transmit on the source cell (e.g., the source cell associated with the source MCG). ) can be canceled. In other words, the UE may transmit only on the target cell or cancel transmission to the source cell. The UE transmits on the target cell, and the UE transmits on the target cell and the source cell are during overlapping time resources, and the UE transmits on the target cell in a DAPS-based handover. and the UE indicates support for uplink transmission cancellation associated with DAPS-based handover.

For DAPS-based handovers that are intra-frequency, the UE transmits on the target cell and transmits to the source cell based at least in part on the UE transmissions on the target cell and the source cell being during overlapping time resources. You may cancel the transmission.

FIG. 5 is a diagram illustrating an example 500 of uplink cancellation in a DAPS-based handover in accordance with the present disclosure.

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

As mentioned above, FIG. 5 is provided as an example. Other examples may differ from those described with respect to FIG.

A UE may be handed over from a source MCG to a target MCG based at least in part on a DAPS-based handover. During a DAPS-based handover, a UE may communicate with both a source base station associated with a source MCG and a target base station associated with a target MCG. Regardless of whether the DAPS-based handover is an intra-frequency DAPS-based handover, the UE may perform a transmission on the target MCG, and the transmission on the source MCG is temporally similar to the transmission on the target MCG. The transmission on the source MCG may be canceled based at least in part on the overlap. However, the UE behavior is such that PUSCH transmissions with repetition on the source MCG are canceled based at least in part on uplink transmissions on the target MCG when DAPS-based handover is enabled for the UE. The situation may not be defined.

In various aspects of the techniques and apparatus described herein, a UE communicates with a source base station associated with the source MCG one of the source MCGs during a DAPS-based handover of the UE from the source MCG to the target MCG. Alternatively, PUSCH repetitions may be transmitted in each of multiple slots. The UE may perform uplink transmissions in one or more slots of the target MCG during a DAPS-based handover to a target base station associated with the target MCG. In some aspects, the UE may cancel PUSCH repetitions associated with a source MCG that overlap in time with uplink transmissions to the MCG. In some aspects, the UE may count PUSCH repetitions based at least in part on the slot of the source MCG associated with the canceled PUSCH repetition. In some aspects, the UE may count PUSCH repetitions based at least in part on counting slots of the source MCG associated with canceled PUSCH repetitions. In some aspects, the UE may count PUSCH repetitions based at least in part on not counting slots of the source MCG associated with canceled PUSCH repetitions.

FIG. 6 is a diagram illustrating an example 600 of PUSCH repetition during handover in accordance with this disclosure. As shown in FIG. 6, 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, a UE, a source base station, and a target base station may be included in a wireless network, such as wireless network 100.

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

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

In some aspects, DAPS-based handover may be associated with FDD-FDD handover. In some aspects, DAPS-based handover may be associated with TDD-TDD handover. In some aspects, DAPS-based handover may be associated with TDD-FDD handover. In some aspects, DAPS-based handover may be associated with FDD-TDD handover. Furthermore, FDD may be associated with paired spectra and TDD may be associated with unpaired spectra.

As indicated by reference numeral 604, the UE may perform uplink transmissions in one or more slots of the target MCG during the DAPS-based handover to a target base station associated with the target MCG. . The uplink transmissions may 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.

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

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

In some aspects, PUSCH repetitions associated with a source MCG may completely overlap in time with uplink transmissions to the MCG. In some aspects, PUSCH repetitions associated with a source MCG may partially overlap in time with uplink transmissions to the MCG.

In some aspects, the UE determines whether the PUSCH is available for repeat transmission at the source MCG.

Due to the slots overlapping in time with the uplink transmission to the target MCG, the UE may transmit PUSCH repetitions over an amount of

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

The slots included in the amount of slots may or may not be counted.

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

may represent a slot (eg, an uplink slot or a special slot) associated with a PUSCH repetition. Uplink transmissions to the target MCG may be associated with PUCCH, PUSCH, SRS, PRACH, or Msg3 PUSCH.

As mentioned above, FIG. 6 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 7 is a diagram illustrating an example 700 of PUSCH repetition during handover in accordance with this disclosure.

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

A slot format configuration (eg, a configuration of uplink slots, downlink slots, and special slots) may be defined for the source MCG, and a slot format configuration may be defined for the target MCG. In the first counting scheme, in FDD-FDD handover, in which the UE counts the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE: The first slot may be associated with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot may be associated with a canceled PUSCH repeat transmission of only 1. It may be associated with a count value that is incremented. In the second counting scheme, where the UE does not count the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE counts the first slot as 0. may be associated with the first PUSCH repetition transmission having a count value of May be associated.

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

As mentioned above, FIG. 7 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 8 is a diagram illustrating an example 800 of PUSCH repetition during handover in accordance with this disclosure.

As shown in FIG. 8, a slot format configuration (e.g., a configuration of uplink slots, downlink slots, and special slots) may be defined for the source MCG, and a slot format configuration for the target MCG may be defined. Good too. In the first counting scheme, in TDD-TDD handover, the UE counts the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE: The first slot may be associated with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot may be associated with a canceled PUSCH repeat transmission of only 1. It may be associated with a count value that is incremented. In the second counting scheme, in which the UE does not count the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE counts the first slot as 0. may be associated with the first PUSCH repetition transmission having a count value of May be associated.

As mentioned above, FIG. 8 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 9 is a diagram illustrating an example 900 of PUSCH repetition during handover in accordance with this disclosure.

As shown in FIG. 9, a slot format configuration (e.g., a configuration of uplink slots, downlink slots, and special slots) may be defined for the source MCG, and a slot format configuration for the target MCG may be defined. Good too. In the first counting scheme, in TDD-TDD handover, the UE counts the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE: The first slot may be associated with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot may be associated with a canceled PUSCH repeat transmission of only 1. It may be associated with a count value that is incremented. In the second counting scheme, where the UE does not count the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE counts the first slot as 0. may be associated with the first PUSCH repetition transmission having a count value of May be associated.

As mentioned above, FIG. 9 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 10 is a diagram illustrating an example 1000 of PUSCH repetition during handover in accordance with this disclosure.

As shown in FIG. 10, a slot format configuration (e.g., a configuration of uplink slots, downlink slots, and special slots) may be defined for the source MCG, and a slot format configuration for the target MCG may be defined. Good too. In the first counting scheme, in TDD-TDD handover, the UE counts the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE: The first slot may be associated with the first PUSCH repeat transmission with a count value of 0, and each subsequent slot may be associated with a canceled PUSCH repeat transmission of only 1. It may be associated with a count value that is incremented. In the second counting scheme, in which the UE does not count the slots of the source MCG associated with canceled PUSCH repeat transmissions due to uplink transmissions to the target MCG that overlap in time resources, the UE counts the first slot as 0. may be associated with the first PUSCH repetition transmission having a count value of May be associated.

As mentioned above, FIG. 10 is provided as an example. Other examples may differ from those described with respect to FIG.

FIG. 11 is a diagram illustrating an example process 1100 performed, for example, by a UE, in accordance with this disclosure. Example process 1100 is an example of a UE (eg, UE 120) performing operations associated with PUSCH repetition during handover.

As shown in FIG. 11, in some aspects, the process 1100 includes a source base station associated with the source MCG, one or more of the source MCGs during a DAPS-based handover of the UE from the source MCG to the target MCG. The method may include transmitting a PUSCH repetition in each of a plurality of slots (block 1110). For example, the UE (e.g., using the transmitting component 1304 shown in FIG. 13) may transmit the UE's DAPS from the source MCG to the target MCG to the source base station associated with the source MCG, as described above. A PUSCH repetition in each of one or more slots of the source MCG during base handover may be transmitted.

As further shown in FIG. 11, in some aspects, the process 1100 includes an uplink in one or more slots of the target MCG during a DAPS-based handover to a target base station associated with the target MCG. A PUSCH repetition associated with a source MCG performing a transmission that overlaps in time with an uplink transmission to the MCG is canceled, and the count of PUSCH repetitions is increased to the source MCG associated with the canceled PUSCH repetition. (block 1120). For example, the UE (e.g., using the transmitting component 1304 shown in FIG. 13) transmits the target MCG during a DAPS-based handover to a target base station associated with the target MCG, as described above. performing an uplink transmission in one or more slots of the PUSCH repetition associated with the source MCG that overlaps in time with an uplink transmission to the MCG, the count of PUSCH repetitions being canceled; Performing may be performed based at least in part on a slot of the source MCG associated with the PUSCH repetition that was issued.

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

In a first aspect, counting PUSCH repetitions includes counting slots of the source MCG associated with canceled PUSCH repetitions.

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

In a third aspect, alone or in combination with one or more of the first and second aspects, the PUSCH repetitions associated with the source MCG completely overlap in time with uplink transmissions to the MCG. do.

In a fourth aspect, alone or in combination with one or more of the first to third aspects, the PUSCH repetition associated with the source MCG is partially in time with the uplink transmission to the MCG. Duplicate.

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

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

In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the PUSCH repetition applies the same symbol allocation in each of the one or more slots of the source MCG. Associated with PUSCH repetition type A.

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

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

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the process 1100 at least partially affects the UE's ability to cancel uplink transmissions during a DAPS-based handover. based on the PUSCH repetition associated with the source MCG.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the process 1100 is associated with a source MCG based at least in part on intra-frequency DAPS-based handover. This includes canceling the PUSCH iterations that were created.

In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the one or more slots of the source MCG are one or more of the uplink slots or the special slots. The one or more slots of the target MCG include one or more of an uplink slot or a special slot.

Although FIG. 11 shows example blocks of process 1100, in some aspects, process 1100 includes additional blocks, fewer blocks, different blocks, or different blocks than the blocks shown in FIG. It may also include placed blocks. Additionally or alternatively, two or more of the blocks of process 1100 may be executed in parallel.

FIG. 12 is a diagram illustrating an example process 1200 performed, for example, by a source base station, in accordance with this disclosure. Exemplary process 1200 is an example of a source base station (eg, source base station 110) performing operations associated with PUSCH repetition during handover.

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

As further shown in FIG. 12, in some aspects, the process 1200 includes a process from the UE to one or more of the source MCGs associated with the source base station during a DAPS-based handover of the UE from the source MCG to the target MCG. receiving PUSCH repetitions in each of the plurality of slots, wherein the PUSCH repetitions that overlap in time with an uplink transmission to the target MCG are canceled, and a count of PUSCH repetitions is associated with the canceled PUSCH repetitions; The receiving may include receiving (block 1220) based at least in part on a slot of the source MCG. For example, the source base station (e.g., using the receiving component 1402 shown in FIG. 14) may receive the source base station from the UE during a DAPS-based handover of the UE from the source MCG to the target MCG, as described above. receiving PUSCH repetitions in each of one or more slots of a source MCG associated with a base station, wherein a PUSCH repetition that overlaps in time with an uplink transmission to a target MCG is canceled; The receiving count may be based at least in part on a slot of the source MCG associated with the canceled PUSCH repetition.

Process 1200 includes additional features, such as any single aspect or any combination of aspects, described in relation to one or more other processes described below and/or elsewhere herein. It may also include aspects.

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

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

Although FIG. 12 shows example blocks of process 1200, in some aspects, process 1200 includes additional blocks, fewer blocks, different blocks, or different blocks than the blocks shown in FIG. 12. It may also include arranged blocks. Additionally or alternatively, two or more of the blocks of process 1200 may be executed in parallel.

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

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

Receiving component 1302 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from device 1306. Receiving component 1302 may provide received communications to one or more other components of apparatus 1300. In some aspects, the receiving component 1302 performs signal processing (filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, among other examples) on received communications. interference cancellation, decoding, etc.) and the processed signal may be provided to one or more other components of apparatus 1306. In some aspects, the receiving component 1302 comprises one or more of the UE's antennas, demodulators, MIMO detectors, receiving processors, controllers/processors, memory, or combinations thereof, as described above with respect to FIG. May include.

Transmission component 1304 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to device 1306. In some aspects, one or more other components of device 1306 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1306. good. In some aspects, the transmitting component 1304 performs signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications. and the processed signal may be sent to device 1306. In some aspects, the transmit component 1304 comprises one or more of the UE's antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or combinations thereof as described above with respect to FIG. May include. In some aspects, transmitting component 1304 may be colocated with receiving component 1302 in a transceiver.

The transmitting component 1304 transmits, to a source base station associated with the source MCG, PUSCH repetitions in each of the one or more slots of the source MCG during a DAPS-based handover of the UE from the source MCG to the target MCG. Good too. The transmission component 1304 is configured to perform uplink transmission in one or more slots of the target MCG during a DAPS-based handover to a target base station associated with the target MCG, the transmission component 1304 comprising: A PUSCH repetition associated with a source MCG that overlaps in time with a link transmission is canceled, and a count of PUSCH repetitions is based at least in part on the slots of the source MCG associated with the canceled PUSCH repetition. You may go.

Cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG that overlap in time with uplink transmissions to the MCG. Cancellation component 1308 cancels the PUSCH repetition associated with the source MCG based at least in part on the lack of UE capability for power sharing between the source MCG and the target MCG during the DAPS-based handover. Good too. Cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG based at least in part on the UE's ability to cancel uplink transmissions during a DAPS-based handover. Cancellation component 1308 may cancel PUSCH repetitions associated with the source MCG based at least in part on intra-frequency DAPS-based handovers.

The number and arrangement of components shown in FIG. 13 is provided as an example. In fact, there may be additional, fewer, different, or differently arranged components compared to the components shown in FIG. 13. Additionally, two or more of the components shown in FIG. 13 may be implemented within a single component, or the single component shown in FIG. 13 may be implemented as multiple distributed components. Good too. Additionally or alternatively, the set(s) of components shown in FIG. 13 may perform one or more functions described as being performed by another set of components shown in FIG. May be executed.

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

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

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

Transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to device 1406. In some aspects, one or more other components of device 1406 may generate communications and provide the generated communications to transmitting component 1404 for transmission to device 1406. good. In some aspects, the transmitting component 1404 performs signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communications. and the processed signal may be sent to device 1406. In some aspects, the transmit component 1404 includes one or more antennas, modulators, transmit MIMO processors, transmit processors, controllers/processors, memory, or the like of the source base station described above with respect to FIG. May include combinations. In some aspects, transmitting component 1404 may be colocated with receiving component 1402 in a transceiver.

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

The number and arrangement of components shown in FIG. 14 is provided as an example. In fact, there may be additional, fewer, different, or differently arranged components compared to the components shown in FIG. 14. Additionally, two or more of the components shown in FIG. 14 may be implemented within a single component, or the single component shown in FIG. 14 may be implemented as multiple distributed components. Good too. Additionally or alternatively, the set(s) of components shown in FIG. 14 may perform one or more functions described as being performed by another set of components shown in FIG. May be executed.

The following provides a summary of some aspects of the disclosure.

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

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

Aspect 3: The method of any of aspects 1-2, wherein counting PUSCH repetitions does not count slots of the source MCG associated with canceled PUSCH repetitions.

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

Aspect 5: The method of any of aspects 1-4, wherein the PUSCH repetitions associated with the source MCG partially overlap in time with uplink transmissions to the MCG.

Aspect 6: Uplink transmissions in one or more slots of the target MCG during DAPS-based handover are physical uplink control channel transmissions, PUSCH transmissions, sounding reference signals, physical random access channel transmissions, or message 3 (Msg3) A method according to any one of aspects 1 to 5, which is one of PUSCH transmissions.

Aspect 7: The DAPS-based handover is associated with a frequency division duplex (FDD)-to-FDD handover, a time-division duplex (TDD)-to-TDD handover, a TDD-to-FDD handover, or an FDD-to-TDD handover, and the FDD is 7. The method of any of embodiments 1-6, wherein the TDD is associated with an unpaired spectrum.

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

Aspect 9: The method of any of aspects 1-8, further comprising canceling PUSCH repetitions associated with a source MCG that overlap in time with uplink transmissions to the MCG.

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

Aspect 11: Any of Aspects 1-10, further comprising canceling PUSCH repetitions associated with the source MCG based at least in part on the UE's ability to cancel uplink transmissions during a DAPS-based handover. the method of.

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

Aspect 13: The one or more slots of the source MCG include one or more of the uplink slots or special slots, and the one or more slots of the target MCG include one or more of the uplink slots or special slots. The method of any of embodiments 1-12, comprising one or more.

Aspect 14: A method of wireless communication performed by a source base station, the method comprising: transmitting to a user equipment (UE) a configuration associated with an amount of physical uplink shared channel (PUSCH) repetitions; receiving PUSCH repetitions in each of one or more slots of a source MCG associated with a source base station during a Dual Active Protocol Stack (DAPS) based handover of a UE from a source master cell group (MCG) to a target MCG; PUSCH repetitions that overlap in time with uplink transmissions to the target MCG are canceled, the count of PUSCH repetitions being based at least in part on slots of the source MCG associated with the canceled PUSCH repetitions; A method, including steps.

Aspect 15: The method of aspect 14, wherein counting PUSCH repetitions is based at least in part on counting slots of the source MCG associated with canceled PUSCH repetitions.

Aspect 16: The method of any of aspects 14-15, wherein counting PUSCH repetitions is based at least in part on not counting slots of the source MCG associated with canceled PUSCH repetitions.

Aspect 17: An apparatus for wireless communication in a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions executable by a processor to cause the process to occur.

Aspect 18: A device for wireless communication comprising a memory and one or more processors coupled to the memory, the memory and one or more processors according to one of Aspects 1-13. or a device configured to perform the method of multiple aspects.

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

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

Aspect 21: A non-transitory computer-readable medium storing a set of instructions for wireless communication, wherein the set of instructions, when executed by one or more processors of the device, causes the device to perform the steps of aspects 1-13. A non-transitory computer-readable medium containing one or more instructions for performing the method of one or more of the aspects.

Aspect 22: An apparatus for wireless communication in a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions executable by a processor to cause the process to occur.

Aspect 23: A device for wireless communication comprising a memory and one or more processors coupled to the memory, the memory and one or more processors according to one of Aspects 14-16. or a device configured to perform the method of multiple aspects.

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

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

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

The above disclosure provides examples and explanations, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

The term "component" as used herein shall be broadly interpreted as hardware and/or a combination of hardware and software. "Software" means, among other things, instructions, instruction sets, code, code segments, program code, program software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. , shall be broadly construed to mean a subprogram, software module, application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, and/or function. Processors as used herein are implemented in hardware and/or a combination of hardware and software. It will be apparent that the systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and/or methods is not a limiting aspect. Accordingly, the operation and behavior of systems and/or methods have been described herein without reference to specific software code. It should be appreciated that software and hardware may be designed to implement systems and/or methods based at least in part on the description herein.

As used herein, "meeting a threshold" means that a value is greater than, greater than or equal to, or less than a threshold, depending on the context. It can also refer to things such as being less than or equal to a threshold value, being equal to a threshold value, and not being equal to a threshold value.

Even though particular combinations of features are recited in the claims and/or disclosed herein, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features may be combined in ways not specifically recited in the claims and/or in ways not disclosed herein. Although each dependent claim set forth below may be directly dependent on only one claim, the disclosure of various aspects includes each dependent claim in combination with any other claims in the claim set. As used herein, the phrase referring to "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of a, b, or c" includes a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination having two or more of the same elements (e.g., a-a, a-a-a , a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c, or any other order of a, b, and c).

No element, act, or instruction used herein should be construed as critical or required unless explicitly described as such. Additionally, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the article "the" is intended to include one or more items mentioned with the article "the" and may be used interchangeably with "one or more." Additionally, the terms "set" and "group" as used herein include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items). may be used interchangeably with "one or more". If only one item is intended, the phrase "only one" or similar language is used. Additionally, as used herein, terms such as "has," "have," and "having" are open-ended terms. Further, the phrase "based on" shall mean "based at least in part on" unless specified otherwise. Additionally, as used herein, the term "or" is inclusive when used consecutively, and unless expressly stated otherwise (e.g., "either") or "only one of"), and may be used interchangeably with "and/or".

100 wireless networks
102a macrocell
102b Picocell
102c femtocell
110 base station, source base station
110a BS, macro BS
110bBS
110cBS
110d BS, relay BS
120UE
120aUE
120bUE
120cUE
120d UE
120eUE
130 Network Controller
200 cases
212 Data Source
220 transmit processor
230 Transmission (TX) Multiple Input Multiple Output (MIMO) Processor, TX MIMO Processor
232 Modulator (MOD), modulator, demodulator, MOD/DEMOD
234 Antenna
236 MIMO detector
238 Receive Processor
239 Data Sink
240 controller/processor
242 memory
244 Communication unit
246 Scheduler
252 Antenna
254 demodulator (DEMOD), demodulator, modulator, MOD/DEMOD
256 MIMO detector
258 Receive Processor
260 data sink
262 data source
264 Transmit Processor
266TX MIMO processor
280 controller/processor
282 Memory
284 Housing
290 Controller/Processor
292 Memory
294 Communication unit
300 cases
400 cases
500 cases
600 cases
700 cases
800 cases
900 cases
1000 examples
1100 processes
1200 processes
1300 equipment
1302 Receiving Component
1304 Send Component
1306 Equipment
1308 Cancellation Component
1400 equipment
1402 Receiving Component
1404 Send Component
1406 Equipment

Claims (30)

A method of wireless communication performed by user equipment (UE), the method comprising:
a source base station associated with a source master cell group (MCG) of one or more slots of said source MCG during a Dual Active Protocol Stack (DAPS)-based handover of said UE from said source MCG to a target MCG; transmitting a Physical Uplink Shared Channel (PUSCH) repetition in each;
performing uplink transmissions in one or more slots of the target MCG during the DAPS-based handover to a target base station associated with the target MCG, the uplink transmissions to the MCG; a PUSCH repetition associated with said source MCG that overlaps in time with said PUSCH repetition is canceled, the count of said PUSCH repetition being based at least in part on slots of said source MCG associated with the canceled PUSCH repetition; Including, methods. 2. The method of claim 1, wherein the counting of the PUSCH repetitions includes counting the slots of the source MCG associated with the canceled PUSCH repetitions. 2. The method of claim 1, wherein the counting of the PUSCH repetitions includes not counting the slots of the source MCG associated with the canceled PUSCH repetitions. 2. The method of claim 1, wherein the PUSCH repetitions associated with the source MCG completely overlap in time with the uplink transmissions to the MCG. 2. The method of claim 1, wherein the PUSCH repetitions associated with the source MCG partially overlap in time with the uplink transmissions to the MCG. The uplink transmission in the one or more slots of the target MCG during the DAPS-based handover may be a physical uplink control channel transmission, a PUSCH transmission, a sounding reference signal, a physical random access channel transmission, or a message 3 (Msg3 ) PUSCH transmission. The DAPS-based handover is associated with a frequency division duplex (FDD)-to-FDD handover, a time-division duplex (TDD)-to-TDD handover, a TDD-to-FDD handover, or an FDD-to-TDD handover, wherein FDD is associated with a spectrum. , TDD is associated with an unpaired spectrum. 2. The method of claim 1, wherein the PUSCH repetition is associated with a PUSCH repetition type A in which the same symbol allocation is applied in each of the one or more slots of the source MCG. 2. The method of claim 1, further comprising canceling the PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmissions to an MCG. canceling the PUSCH repetition associated with the source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during the DAPS-based handover; 2. The method of claim 1, further comprising: 2. The method of claim 1, further comprising canceling the PUSCH repetition associated with the source MCG based at least in part on a UE's ability to cancel uplink transmissions during the DAPS-based handover. 2. The method of claim 1, further comprising canceling the PUSCH repetition associated with the source MCG based at least in part on intra-frequency DAPS-based handover. the one or more slots of the source MCG include one or more of uplink slots or special slots;
the one or more slots of the target MCG include one or more of uplink slots or special slots;
The method according to claim 1. A method of wireless communication performed by a source base station, the method comprising:
transmitting to a user equipment (UE) a configuration associated with an amount of physical uplink shared channel (PUSCH) repetitions;
of one or more slots of the source MCG associated with the source base station during a Dual Active Protocol Stack (DAPS) based handover of the UE from a source master cell group (MCG) to a target MCG. receiving PUSCH repetitions in each of the PUSCH repetitions that overlap in time with an uplink transmission to the target MCG is canceled, and a count of the PUSCH repetitions is determined from the source associated with the canceled PUSCH repetition; A method based at least in part on slots of an MCG. 15. The method of claim 14, wherein the counting of the PUSCH repetitions is based at least in part on counting the slots of the source MCG associated with the canceled PUSCH repetitions. 15. The method of claim 14, wherein the count of the PUSCH repetitions is based at least in part on not counting the slots of the source MCG associated with the canceled PUSCH repetitions. A user equipment (UE) for wireless communication, the user equipment (UE) comprising:
memory and
one or more processors operably coupled to the memory, the one or more processors comprising:
a source base station associated with a source master cell group (MCG) of one or more slots of said source MCG during a Dual Active Protocol Stack (DAPS)-based handover of said UE from said source MCG to a target MCG; transmitting a Physical Uplink Shared Channel (PUSCH) repetition in each;
performing an uplink transmission in one or more slots of the target MCG during the DAPS-based handover to a target base station associated with the target MCG, the uplink transmission to the MCG; PUSCH repetitions associated with said source MCG that overlap in time with are canceled, and a count of said PUSCH repetitions is based at least in part on slots of said source MCG associated with canceled PUSCH repetitions; A UE configured to: 18. The UE of claim 17, wherein the counting of the PUSCH repetitions includes counting the slots of the source MCG associated with the canceled PUSCH repetitions. 18. The UE of claim 17, wherein the counting of the PUSCH repetitions includes not counting the slots of the source MCG associated with the canceled PUSCH repetitions. The uplink transmission in the one or more slots of the target MCG during the DAPS-based handover may be a physical uplink control channel transmission, a PUSCH transmission, a sounding reference signal, a physical random access channel transmission, or a message 3 (Msg3 ) PUSCH transmission. The DAPS-based handover is associated with a frequency division duplex (FDD)-to-FDD handover, a time-division duplex (TDD)-to-TDD handover, a TDD-to-FDD handover, or an FDD-to-TDD handover, wherein FDD is associated with a spectrum. , TDD is associated with unpaired spectrum. 18. The UE of claim 17, wherein the PUSCH repetition is associated with PUSCH repetition type A in which the same symbol allocation is applied in each of the one or more slots of the source MCG. said one or more processors,
18. The UE of claim 17, further configured to cancel the PUSCH repetitions associated with the source MCG that overlap in time with the uplink transmissions to an MCG. said one or more processors,
canceling the PUSCH repetition associated with the source MCG based at least in part on a lack of UE capability for power sharing between the source MCG and the target MCG during the DAPS-based handover; 18. The UE of claim 17, further configured. said one or more processors,
18. The UE of claim 17, further configured to cancel the PUSCH repetition associated with the source MCG based at least in part on the UE's ability to cancel uplink transmissions during the DAPS-based handover. . said one or more processors,
18. The UE of claim 17, further configured to cancel the PUSCH repetition associated with the source MCG based at least in part on intra-frequency DAPS-based handover. the one or more slots of the source MCG include one or more of uplink slots or special slots;
the one or more slots of the target MCG include one or more of uplink slots or special slots;
UE according to claim 17. A source base station for wireless communications, the source base station comprising:
memory and
one or more processors operably coupled to the memory, the one or more processors comprising:
transmitting to a user equipment (UE) a configuration associated with an amount of physical uplink shared channel (PUSCH) repetitions;
of one or more slots of the source MCG associated with the source base station during a Dual Active Protocol Stack (DAPS) based handover of the UE from a source master cell group (MCG) to a target MCG. receiving PUSCH repetitions in each of the PUSCH repetitions that overlap in time with an uplink transmission to said target MCG is canceled, and a count of said PUSCH repetitions is determined by said source associated with said canceled PUSCH repetition; a source base station configured to receive and receive based at least in part on a slot of an MCG; 29. The source base station of claim 28, wherein the counting of the PUSCH repetitions is based at least in part on counting the slots of the source MCG associated with the canceled PUSCH repetitions. 29. The source base station of claim 28, wherein the count of the PUSCH repetitions is based at least in part on not counting the slots of the source MCG associated with the canceled PUSCH repetitions.