Interruption of physical uplink shared channel (PUSCH) repetition due to band switching

Abstract

A method of wireless communication by a user equipment (UE) includes receiving a repetition configuration for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band. The method further includes receiving a switching configuration for switching the uplink transmission to an uplink slot in a second frequency band. The method further includes counting available slots for transmitting PUSCH repetitions based on the repetition configuration and the handover configuration.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly to interruption of Physical Uplink Shared Channel (PUSCH) repetitions due to switching of uplink transmissions to a different frequency band. Background Art

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard released by the Third Generation Partnership Project (3GPP). Narrowband (NB) Internet of Things (IoT) and enhanced machine type communications (eMTC) are a set of enhancements to LTE for machine type communications.

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

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global levels. New Radio (NR) (which may also be referred to as 5G) is an enhancement set of the LTE mobile standard released by the Third Generation Partnership Project (3GPP). NR is designed to better support mobile broadband Internet access by using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with a cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation to improve spectrum efficiency, reduce costs, improve services, utilize new spectrum, and better integrate with other open standards. Summary of the Invention

[0005] According to aspects of the present disclosure, a method for wireless communication by a user equipment (UE) includes receiving a repetition configuration for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band. The method also includes receiving a switching configuration for switching the uplink transmission to an uplink timeslot in a second frequency band. The method also includes counting available timeslots for transmitting the PUSCH repetition based on the repetition configuration and the switching configuration.

[0006] According to other aspects of the present disclosure, a method for wireless communication by a network device includes: transmitting a repetition configuration for transmitting physical uplink shared channel (PUSCH) repetitions in a first frequency band. The method also includes: transmitting a switching configuration for switching uplink transmission to an uplink time slot in a second frequency band. The method also includes: communicating with a UE based on counting available time slots for transmitting the PUSCH repetitions based on the repetition configuration and the switching configuration.

[0007] According to other aspects of the present disclosure, an apparatus for wireless communication by a user equipment (UE) includes a memory and at least one processor coupled to the memory. The processor is configured to receive a repetition configuration for transmitting physical uplink shared channel (PUSCH) repetitions in a first frequency band. The processor is further configured to receive a switching configuration for switching uplink transmission to an uplink timeslot in a second frequency band. The processor is further configured to count available timeslots for transmitting the PUSCH repetitions based on the repetition configuration and the switching configuration.

[0008] According to other aspects of the present disclosure, an apparatus for wireless communication by a network device includes: a memory; and at least one processor coupled to the memory. The processor is configured to: send a repetition configuration for transmitting physical uplink shared channel (PUSCH) repetitions in a first frequency band. The processor is further configured to: send a switching configuration for switching uplink transmission to an uplink time slot in a second frequency band. The processor is further configured to: count available time slots for transmitting PUSCH repetitions based on the repetition configuration and the switching configuration.

[0009] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and processing systems substantially as described with reference to and as illustrated in the accompanying drawings and description.

[0010] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description that follows may be better understood. Additional features and advantages will be described. The concepts and specific examples disclosed may be readily used as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the disclosed concepts, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order that the features of the present disclosure may be understood in detail, reference may be made to various aspects of the detailed description, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only certain aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0012] Figure 1 is a block diagram conceptually illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0013] Figure 2 is a block diagram conceptually illustrating an example of a base station communicating with a user equipment (UE) in a wireless communication network according to various aspects of the present disclosure.

[0014] Figure 3 is a block diagram illustrating an example decomposed base station architecture in accordance with various aspects of the present disclosure.

[0015] Figure 4 is a timeline illustrating a time division duplex (TDD) slot pattern according to aspects of the present disclosure.

[0016] Figure 5 is a diagram illustrating switching between frequency bands according to aspects of the present disclosure.

[0017] Figure 6 is a diagram illustrating a timeline of two frequency bands with overlapping downlink and uplink resources in accordance with aspects of the present disclosure.

[0018] Figure 7 is a diagram illustrating a timeline of two frequency bands with overlapping uplink resources according to aspects of the present disclosure.

[0019] Figure 8 is a flow diagram illustrating an example process performed, for example, by a user equipment (UE) according to various aspects of the present disclosure.

[0020] Figure 9 is a flow diagram illustrating an example process, eg, performed by a network device, according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0021] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. Based on the teachings, those skilled in the art should recognize that the scope of the present disclosure is intended to cover any aspect of the present disclosure, whether that aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, any number of aspects set forth can be used to implement an apparatus or practice method. In addition, the scope of the present disclosure is intended to cover such apparatus or methods that are practiced using other structures, functionality, or structure and functionality in addition to or as a supplement to the various aspects of the present disclosure set forth. It should be understood that any aspect of the present disclosure disclosed can be embodied by one or more elements of the claims.

[0022] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0023] It should be noted that although various aspects may be described using terms typically associated with 5G and subsequent wireless technologies, various aspects of the present disclosure may be applied in other generation-based communication systems (such as and including 3G and / or 4G technologies).

[0024] To improve the reliability of a transmission, a transmission may be repeated multiple times to increase the likelihood that the transmission will be correctly received or decoded. The Third Generation Partnership Project (3GPP) defines specifications for repetition of the Physical Uplink Shared Channel (PUSCH). For example, 3GPP Release 17 defines a method for counting the number of slots used for repetition.

[0025] A user equipment (UE) can be configured to transmit on multiple frequency bands. For example, if two transmit chains are available, the UE can transmit on both frequency bands simultaneously. Alternatively, if only a single transmit chain is available, the UE can switch from a first frequency band to a second frequency band and back to the first frequency band. The 3GPP standard defines techniques for switching between the two frequency bands. If a single transmit chain is available, transmission on the first frequency band will be interrupted when switching to the second frequency band. If PUSCH repetition is configured on the first frequency band, the repetition can be interrupted during the switch.

[0026] According to various aspects of the present disclosure, counting methods are defined for the case where the frequency band used for uplink transmission is switched during PUSCH repetition. Some aspects address the case where an uplink time slot scheduled in one frequency band overlaps a downlink time slot in another frequency band used for PUSCH repetition. In some aspects, a frequency band two scheduling overlaps a frequency band one downlink time slot during a frequency band one PUSCH repetition. In such aspects, if only uplink resources on frequency band two are configured, but no actual uplink transmission occurs on frequency band two, then switching from frequency band one to frequency band two is prevented. In some aspects, uplink transmission occurs on frequency band two. In these aspects, the UE can treat the scheduled uplink time slot as an error case. In other aspects, the network ensures that scheduling or configuration of uplink resources will not occur. In other aspects, the UE transmits on frequency band two and counting of PUSCH repetitions continues.

[0027] Aspects of the present disclosure also address the situation where the uplink time slot scheduled for Band 2 overlaps with the uplink time slot of Band 1 used for PUSCH repetition or the switching period for the uplink time slot in Band 1. Both partial overlap and complete overlap are considered. In some aspects, when the uplink time slot of Band 2 overlaps with the uplink time slot of Band 1 during the PUSCH repetition of Band 1, if only uplink resources on Band 2 are configured but no actual uplink transmission occurs on Band 2, the switching from Band 1 to Band 2 is prevented. In some aspects, the uplink transmission occurs on Band 2. In these aspects, the UE can treat the scheduled uplink time slot as an error case. In other aspects, the network ensures that the scheduling or configuration of uplink resources will not occur.

[0028] Certain aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, the described techniques, such as counting available time slots for transmitting PUSCH repetitions, can improve uplink transmission reliability. When both uplink transmission switching and time slot repetition are configured, these techniques continue counting. By continuing to count, the UE's repetitions are not interrupted by transmission switching and uplink transmission reliability is guaranteed.

[0029] Figure 1 is a diagram illustrating a network 100 in which various aspects of the present disclosure may be practiced. Network 100 may be a 5G or NR network, or some other wireless network (such as an LTE network). Wireless network 100 may include multiple base stations (BSs) 110 (shown as BSs 110a, 110b, 110c, and 110d) and other network entities. A BS is an entity that communicates with user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B, access point, transmit and receive point (TRP), network node, network entity, etc. A base station may be implemented as a converged base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, etc. A base station may be implemented in a converged or monolithic base station architecture, or alternatively, in a decomposed base station architecture, and may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near-RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC.

[0030] Each BS can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0031] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in FIG, BS 110a may be a macro BS for macrocell 102a, BS 110b may be a pico BS for picocell 102b, and BS 110c may be a femto BS for femtocell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB," "base station," "NR BS," "gNB," "AP," "Node B," "5G NB," "TRP," and "cell" may be used interchangeably.

[0032] In some aspects, the cells need not be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (e.g., direct physical connections, virtual networks, etc.) using any suitable transport network.

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

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

[0035] For example, BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and core network 130 may exchange communications via backhaul links 132 (e.g., S1, etc.). Base stations 110 may communicate with each other directly or indirectly (e.g., through core network 130) via other backhaul links (e.g., X2, etc.).

[0036] The core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may be a control node that handles signaling between the UE 120 and the EPC. All user IP packets may be transmitted through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to the network operator's IP services. The operator's IP services may include the Internet, intranet, IP multimedia subsystem (IMS), and packet switched (PS) streaming services.

[0037] The core network 130 may provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. One or more of the base stations 110 or access node controllers (ANCs) may interface with the core network 130 via a backhaul link 132 (e.g., S1, S2, etc.) and may perform radio configuration and scheduling for communications with the UE 120. In some configurations, the various functions of each access network entity or base station 110 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., base station 110).

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

[0039] One or more UEs 120 may establish a protocol data unit (PDU) session for a network slice. In some cases, the UE 120 may select a network slice based on an application or subscription service. By having different network slices serve different applications or subscriptions, the UE 120 may improve its resource utilization in the wireless network 100 while also meeting the performance specifications of the respective applications of the UE 120. In some cases, the AMF (Anti-Sensitive Multicasting Facility) associated with one or both of the base station 110 and the core network 130 may be used to establish a protocol data unit (PDU) session for the network slice ... Figure 1 1) to serve the network slice used by UE 120. In addition, session management of the network slice can be performed by an access and mobility management function (AMF).

[0040] UE 120 may include a physical uplink shared channel (PUSCH) repetition module 140. For simplicity, only one UE 120d is shown as including the PUSCH repetition module 140. The PUSCH repetition module 140 may receive a repetition configuration for transmitting physical uplink shared channel (PUSCH) repetitions in a first frequency band. The PUSCH repetition module 140 may receive a switching configuration for switching uplink transmission to an uplink time slot in a second frequency band. The PUSCH repetition module 140 may count available time slots for transmitting the PUSCH repetitions based on the repetition configuration and the switching configuration.

[0041] Core network 130 or base station 110 or any other network device (e.g. Figure 3The UE may include a PUSCH repetition module 138 configured to transmit a repetition configuration for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band. The PUSCH repetition module 138 may transmit a switching configuration for switching uplink transmission to an uplink time slot in a second frequency band. The PUSCH repetition module 138 may communicate to the UE based on a count of available time slots for transmitting the PUSCH repetition based on the repetition configuration and the switching configuration.

[0042] Some UEs may be considered machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. For example, MTC and eMTC UEs include robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that can communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity to or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered 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 in a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).

[0043] Generally speaking, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific radio access technology (RAT) and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. In a given geographic area, each frequency can support a single RAT to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0044] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary) using one or more sidelink channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, etc.), mesh networks, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein that are performed by base station 110. For example, base station 110 may configure UE 120 via downlink control information (DCI), radio resource control (RRC) signaling, medium access control-control element (MAC-CE), or via system information (e.g., system information block (SIB)).

[0045] As indicated above, Figure 1 It is provided as an example only. Other examples can be found in the reference Figure 1 The examples described are different.

[0046] Figure 2 A block diagram shows a design 200 of a base station 110 and a UE 120, which may be Figure 1 One of the base stations in Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general T≧1 and R≧1.

[0047] At the base station 110, the transmit processor 220 may receive data for one or more UEs from a data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for each UE based at least in part on the MCS selected for the UE, and provide data symbols for all UEs. Reducing the MCS reduces throughput but increases transmission reliability. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI) and control information (e.g., CQI requests, grants, upper layer signaling, etc.) and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, as applicable, and may provide T output symbol streams to T modulators (MODs) 232a through 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM) or the like) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a through 232t may be transmitted via T antennas 234a through 234t, respectively. According to various aspects described in greater detail below, position coding may be utilized to generate synchronization signals to convey additional information.

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

[0049] On the uplink, at UE 120, a transmit processor 264 may receive data from a data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.) from a controller / processor 280 and process the data and control information. The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266, if applicable, further processed by modulators 254a through 254r (e.g., for discrete Fourier transform spread OFDM (DFT-s-OFDM), CP-OFDM, etc.), and transmitted to the base station 110. At the base station 110, uplink signals from UE 120 and other UEs may be received by antennas 234, processed by demodulators 254, detected by MIMO detector 236 (if applicable), and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and may provide the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the core network 130 via the communication unit 244. The core network 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0050] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other components of the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or the like may perform one or more techniques associated with PUSCH repetition interruption, as described in greater detail elsewhere. Figure 2 Any other component of may perform or direct e.g. Figure 8 and Figure 9 1 and / or other processes as described. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. Scheduler 246 may schedule UEs for data transmission on the downlink and / or uplink.

[0051] In some aspects, the UE 120 and / or base station 110 may include means for receiving, means for receiving, means for counting, means for preventing, means for discarding, means for undesired, means for sending, means for scheduling or configuring, and means for communicating. Such means may include means for combining Figure 2 One or more components of a UE 120 or base station 110 are depicted.

[0052] As indicated above, Figure 2 It is provided as an example only. Other examples can be found in the reference Figure 2 The examples described are different.

[0053] The deployment of a communication system (such as a 5G New Radio (NR) system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)) or one or more units (or one or more components) that perform base station functionality can be implemented in a converged or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit and receive point (TRP) or a cell, etc.) can be implemented as a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0054] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

[0055] Base station type operation or network design can take into account the aggregated nature of base station functionality. For example, a disaggregated base station can be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition can include distributing functionality across two or more units at various physical locations, as well as virtually distributing the functionality of at least one unit, which can enable flexibility in network design. The various units of the disaggregated base station or disaggregated RAN architecture can be configured for wired or wireless communication with at least one other unit.

[0056] In some cases, different types of devices supporting different types of applications and / or services may coexist in a cell. Examples of different types of devices include UE phones, customer premises equipment (CPE), vehicles, and Internet of Things (IoT) devices. Examples of different types of applications include ultra-reliable low-latency communications (URLLC) applications, massive machine-type communications (mMTC) applications, enhanced mobile broadband (eMBB) applications, and vehicle-to-everything (V2X) applications. In addition, in some cases, a single device may support different applications or services simultaneously.

[0057] Figure 3A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CUs 310 can communicate with one or more distributed units (DUs) 330 via corresponding midhaul links, such as an F1 interface. The DUs 330 can communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. The RUs 340 can communicate with corresponding UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 can be served simultaneously by multiple RUs 340.

[0058] Each of these units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include one or more interfaces, or may be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of these units, or an associated processor or controller that provides instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive signals or transmit signals to one or more of the other units, or both, via a wireless transmission medium.

[0059] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0060] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on a functional split, such as that defined by the Third Generation Partnership Project (3GPP). In some aspects, the DU 330 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0061] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, both real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0062] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 311, via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0063] The non-RT RIC 315 may be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB 311 with the near-RT RIC 325.

[0064] In some implementations, the non-RT RIC 315 can receive parameters or external enrichment information from an external server in order to generate an AI / ML model to be deployed in the near-RT RIC 325. Such information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or from network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0065] To improve the reliability of a transmission, a transmission may be repeated multiple times to increase the likelihood of receiving the transmission correctly. The Third Generation Partnership Project (3GPP) defines specifications for Physical Uplink Shared Channel (PUSCH) repetition. For example, 3GPP Release 17 defines a method for counting the time slots used for PUSCH repetition.

[0066] First, the UE determines K available time slots for K repetitions. A time slot is available if all symbols contained in the time domain resource allocation (TDRA) are uplink symbols or flexible symbols. Symbols may be indicated as uplink symbols or flexible symbols by radio resource control (RRC) signaling (e.g., tdd-UL-DL-ConfigurationCommon message and / or tdd-UL-DL-ConfigurationDedicated message). In order to be available, the time slot may not be configured for synchronization signal block (SSB) transmission, for example, as configured by the SSBPositionsInBurst message. Next, the UE determines whether to discard PUSCH repetitions according to the version 15, 16, and 17 PUSCH discard rules. Regardless of whether the UE discards repetitions, PUSCH repetitions are still counted in the K repetitions.

[0067] Figure 4 is a timeline illustrating a time division duplex (TDD) time slot pattern according to aspects of the present disclosure. Figure 4 In the example of , every three downlink time slots (D) are followed by an uplink time slot (U). In this example, three uplink time slots 1, 2, and 3 can be used for PUSCH repetition.

[0068] A UE can be configured to transmit on multiple frequency bands. For example, if two transmit chains are available, the UE can transmit on both frequency bands simultaneously. Alternatively, if only a single transmit chain is available, the UE can switch from the first frequency band to the second frequency band and back to the first frequency band. The 3GPP standard defines techniques for switching between the two frequency bands. If a single transmit chain is available, transmission on the first frequency band will be interrupted when switching to the second frequency band. If PUSCH repetition is configured, repetition can be interrupted during switching.

[0069] Figure 5 is a diagram illustrating switching between frequency bands according to aspects of the present disclosure. Figure 5 In the example of , the first frequency band 502 has 10 time slots (time slots 0-9) and the second frequency band 504 has five time slots (time slots 0-4). The first frequency band 502 is called component carrier (CC) 2 (or simply carrier 2) and is a TDD carrier in this example. The second frequency band 504 is called component carrier (CC) 1 (or simply carrier 1) and is a frequency division duplex (FDD) carrier in this example. For the first frequency band 502, time slots 4, 8, and 9 are configured as uplink time slots (U), time slots 0, 1, 2, 5, and 6 are configured as downlink time slots (D), and time slots 3 and 7 are configured as special time slots (S). For the second frequency band 504, all time slots are configured as uplink time slots.

[0070] In this example, the uplink time slots in the first frequency band 502 are available time slots for PUSCH repetition. However, in the second frequency band 504, transmissions occur in time slots 0, 1, 2, and 3. A conflict exists between time slot 2 in the second frequency band 504 and time slot 4 in the first frequency band 502. It is desirable to have a solution to resolve conflicts caused by switching during PUSCH repetition. According to aspects of the present disclosure, a counting method is defined for the case where uplink transmission switching is combined with PUSCH repetition.

[0071] Some aspects address the case where a Band 2 scheduling of an uplink timeslot overlaps a Band 1 downlink timeslot during a Band 1 PUSCH repetition. In the following description, Band 1 is assumed to be TDD with PUSCH repetition.

[0072] Figure 6 is a diagram illustrating a timeline of two frequency bands with overlapping downlink and uplink resources according to aspects of the present disclosure. Figure 6In the example of FIG, a first frequency band 602 has a plurality of downlink time slots (one labeled D) and four uplink time slots (labeled U) corresponding to four PUSCH repetitions. The first frequency band 602 is referred to as component carrier (CC) 2 and is a TDD carrier in this example. The second frequency band 604 has an uplink time slot 606 configured and scheduled for uplink transmission. The second frequency band 604 is referred to as component carrier (CC) 1 and is an FDD carrier in this example. The uplink time slot 606 overlaps with the downlink time slot 608 in the first frequency band 602.

[0073] In some examples, such as Figure 6 In the example of , the uplink time slot 606 scheduled on frequency band 2 604 overlaps with the downlink time slot of frequency band 1 during the PUSCH repetition of frequency band 1. In such an example, if only the uplink time slot 606 on frequency band 2 604 is configured, but no actual uplink transmission occurs on frequency band 2 604, then switching from frequency band 1 602 to frequency band 2 604 is prevented. The actual uplink transmission may not occur because the uplink time slot 606 is not scheduled for UE uplink transmission or the UE does not actually transmit on the uplink time slot 606. As discussed, Figure 6 The scheduled and configured uplink time slots 606 in frequency band two 604 are shown. These aspects do not apply to Figure 6 In the example shown, unless an uplink timeslot 606 in frequency band two 604 is configured but not scheduled or the UE is not transmitting on the uplink timeslot 606 .

[0074] In some aspects, the uplink transmission occurs on frequency band two 604. For example, a scheduling request may initiate scheduling of an uplink time slot 606, or the UE may need to transmit. In these aspects, the UE may treat the scheduled uplink time slot 606 as an error condition. For example, the UE may discard the uplink transmission on frequency band two 604 by ignoring the handover request. In other examples, the UE performs a frequency band handover. In other aspects, the network ensures that scheduling or configuration of the uplink time slot 606 will not occur. Therefore, the UE does not expect to be scheduled or configured with uplink resources 606 in the second frequency band 604 and transmit during the PUSCH repetition in the first frequency band 602. In other aspects, the UE transmits on frequency band two 604, and the counting of repetitions continues. An example of a transmission on the second frequency band 604 may be a physical random access channel (PRACH) message.

[0075] Aspects of the present disclosure also address the situation where Band 2 scheduling overlaps with Band 1 uplink slots or switching periods for uplink slots in Band 1 during Band 1 PUSCH repetitions. Both partial and full overlaps are contemplated. In the following description, Band 1 is assumed to be TDD with PUSCH repetitions.

[0076] Figure 7 is a diagram illustrating a timeline of two frequency bands with overlapping downlink and uplink resources according to aspects of the present disclosure. Figure 7 In the example of FIG. 7 , a first frequency band 702 has a plurality of downlink time slots (one labeled D) and four uplink time slots (labeled U) corresponding to four repetitions. First frequency band 702 is referred to as component carrier (CC) 2 and, in this example, is a TDD carrier. Second frequency band 704 has uplink time slots 706 configured and scheduled for uplink transmissions. Second frequency band 704 is referred to as component carrier (CC) 1 and, in this example, is an FDD carrier. Uplink time slots 706 overlap with uplink time slots 708 in first frequency band 702.

[0077] In some examples, such as Figure 7 In the example of FIG1 , an uplink time slot 706 scheduled on frequency band two 704 overlaps with a frequency band one uplink time slot during a frequency band one PUSCH repetition. In such an example, if only the uplink time slot 706 on frequency band two 704 is configured, but no actual uplink transmission occurs on frequency band two 704, then switching from frequency band one 702 to frequency band two 704 is prevented. No actual uplink transmission occurs because the uplink time slot 706 is not scheduled for a UE uplink transmission or the UE does not actually transmit on the uplink time slot 706. Figure 7 The scheduled and configured uplink time slots 706 are shown. These aspects do not apply to Figure 7 The example shown, unless the uplink timeslot 706 is configured but not scheduled or the UE does not transmit on the uplink timeslot 706.

[0078] In some aspects, the uplink transmission occurs on frequency band two 704. For example, a scheduling request may initiate scheduling of an uplink time slot 706, or the UE may need to transmit. In these aspects, the UE may treat the scheduled uplink time slot 706 as an error condition. For example, the UE may discard the uplink transmission on frequency band two 704 by ignoring the handover request. In other examples, the UE performs a frequency band handover. In other aspects, the network guarantees that scheduling or configuration of the uplink time slot 706 will not occur. Therefore, the UE does not expect to be scheduled or configured with an uplink time slot 706 in the second frequency band 704 and transmit during the PUSCH repetition in the first frequency band 702.

[0079] As indicated above, Figures 4 to 7 are provided as examples. Other examples can be compared with Figures 4 to 7 The examples described are different.

[0080] Figure 8 is a flow diagram illustrating an example process 800 performed, for example, by a user equipment (UE) in accordance with various aspects of the present disclosure. The example process 800 is an example of counting available time slots for sending PUSCH repetitions.

[0081] At block 802, a UE receives a repetition configuration for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive the repetition configuration. The first frequency band may be TDD.

[0082] At block 804, the UE receives a switching configuration for switching uplink transmissions to an uplink timeslot in the second frequency band. For example, the UE (e.g., using antenna 252, DEMOD / MOD 254, MIMO detector 256, receive processor 258, controller / processor 280, memory 282, etc.) may receive the switching configuration. In some aspects, in response to an uplink timeslot in the second frequency band overlapping with a downlink timeslot in the first frequency band during a PUSCH repetition period and the uplink timeslot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink timeslot, the UE may prevent switching to the uplink timeslot in the second frequency band according to the switching configuration. In other aspects, in response to an uplink timeslot in the second frequency band overlapping with a downlink timeslot in the first frequency band during a PUSCH repetition period and the uplink timeslot is scheduled for UE transmission, the UE may discard the uplink transmission on the uplink timeslot in the second frequency band.

[0083] At block 806, the UE counts available time slots for sending PUSCH repetitions based on the repetition configuration and the switching configuration. For example, the UE (e.g., using the controller / processor 280, the memory 282, etc.) may count time slots. In some aspects, in response to an uplink time slot in the second frequency band overlapping a downlink time slot in the first frequency band during a PUSCH repetition, the UE may send an uplink message on the uplink time slot in the second frequency band and continue to count PUSCH repetitions.

[0084] Figure 99 is a flow chart illustrating an example process 900 performed, for example, by a network device according to various aspects of the present disclosure. Example process 900 is an example of communicating based on counting available time slots for sending PUSCH repetitions. In some implementations, the network device may be a base station.

[0085] At block 902, a base station transmits a repetition configuration to a user equipment (UE) for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may transmit the repetition configuration. The first frequency band may be TDD.

[0086] At block 904, the base station sends a switching configuration to the UE for switching uplink transmissions to an uplink timeslot in the second frequency band. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, controller / processor 240, memory 242, etc.) may send the switching configuration. In some aspects, in response to an uplink timeslot in the second frequency band overlapping a downlink timeslot in the first frequency band during a PUSCH repetition, the base station schedules or configures the UE to not have an uplink timeslot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

[0087] At block 906, the base station communicates with the UE based on the count of available time slots for transmitting PUSCH repetitions based on the repetition configuration and the switching configuration. For example, the base station (e.g., using antenna 234, MOD / DEMOD 232, TX MIMO processor 230, transmit processor 220, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, etc.) can communicate with the UE. In some aspects, in response to an uplink time slot in the second frequency band overlapping a downlink time slot in the first frequency band during a PUSCH repetition, the base station receives an uplink message on the uplink time slot in the second frequency band while continuing to count the PUSCH repetitions.

[0088] Example aspects

[0089] Aspect 1: A method for wireless communication by a user equipment (UE), the method comprising: receiving a repetition configuration for sending a physical uplink shared channel (PUSCH) repetition in a first frequency band; receiving a switching configuration for switching the uplink transmission to an uplink time slot in a second frequency band; and counting available time slots for sending the PUSCH repetition based on the repetition configuration and the switching configuration.

[0090] Aspect 2: The method according to aspect 1, wherein the first frequency band is time division duplex (TDD).

[0091] Aspect 3: The method according to Aspect 1 or 2 further includes: preventing switching to the uplink time slot in the second frequency band according to the switching configuration in response to the following items: the uplink time slot in the second frequency band overlaps with the downlink time slot in the first frequency band during PUSCH repetition, and the uplink time slot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink time slot.

[0092] Aspect 4: The method according to Aspect 1 or 2 further includes: discarding the uplink transmission on the uplink time slot in the second frequency band in response to the following items: the uplink time slot in the second frequency band overlaps with the downlink time slot in the first frequency band during PUSCH repetition, and the uplink time slot is scheduled for UE transmission.

[0093] Aspect 5: The method according to Aspect 1 or 2 further includes: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, it is not expected that the UE is scheduled or configured to have the uplink time slot in the second frequency band and send during the PUSCH repetition in the first frequency band.

[0094] Aspect 6: The method according to Aspect 1 or 2 further includes: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during PUSCH repetition, sending an uplink message on the uplink time slot in the second frequency band, and continuing to count the PUSCH repetition.

[0095] Aspect 7: The method according to Aspect 1 or 2 further includes: preventing switching to the uplink time slot in the second frequency band according to the switching configuration in response to the following items: the uplink time slot in the second frequency band overlaps with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, and the uplink time slot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink time slot.

[0096] Aspect 8: The method according to Aspect 1 or 2 further includes: discarding the uplink transmission on the uplink time slot in the second frequency band in response to the following items: the uplink time slot in the second frequency band overlaps with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during PUSCH repetition, and the uplink time slot is scheduled for UE transmission.

[0097] Aspect 9: The method according to Aspect 1 or 2 further includes: in response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, it is not expected that the UE is scheduled or configured to have the uplink time slot in the second frequency band and send during the PUSCH repetition in the first frequency band.

[0098] Aspect 10: A method for wireless communication by a network device, the method comprising: sending a repetition configuration for sending physical uplink shared channel (PUSCH) repetitions in a first frequency band to a user equipment (UE); sending a switching configuration to the UE for switching uplink transmission to an uplink time slot in a second frequency band; and communicating with the UE based on a count of available time slots for sending PUSCH repetitions based on the repetition configuration and the switching configuration.

[0099] Aspect 11: The method according to aspect 10, wherein the first frequency band is time division duplex (TDD).

[0100] Aspect 12: The method according to Aspect 10 or 11 further includes: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, scheduling the UE as or configuring the UE not to have an uplink time slot in the second frequency band and sending during the PUSCH repetition in the first frequency band.

[0101] Aspect 13: The method according to Aspect 10 or 11 further includes: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, receiving an uplink message on the uplink time slot in the second frequency band while continuing to count the PUSCH repetition.

[0102] Aspect 14: The method according to Aspect 10 or 11 further includes: in response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, scheduling the UE as or configuring the UE to not have an uplink time slot in the second frequency band and sending during the PUSCH repetition in the first frequency band.

[0103] Aspect 15: An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: a memory; and at least one processor coupled to the memory, the at least one processor being configured to: receive a repetition configuration for sending a physical uplink shared channel (PUSCH) repetition in a first frequency band; receive a switching configuration for switching the uplink transmission to an uplink time slot in a second frequency band; and count available time slots for sending PUSCH repetitions based on the repetition configuration and the switching configuration.

[0104] Aspect 16: The apparatus of aspect 15, wherein the first frequency band is time division duplex (TDD).

[0105] Aspect 17: The apparatus according to Aspect 15 or 16 further includes: preventing switching to the uplink time slot in the second frequency band according to the switching configuration in response to the following items: the uplink time slot in the second frequency band overlaps with the downlink time slot in the first frequency band during PUSCH repetition, and the uplink time slot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink time slot.

[0106] Aspect 18: The apparatus according to Aspect 15 or 16 further includes: discarding the uplink transmission on the uplink time slot in the second frequency band in response to the following items: the uplink time slot in the second frequency band overlaps with the downlink time slot in the first frequency band during the PUSCH repetition, and the uplink time slot is scheduled for UE transmission.

[0107] Aspect 19: The apparatus according to Aspect 15 or 16 further includes: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, the UE is not expected to be scheduled or configured to have the uplink time slot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

[0108] Aspect 20: The apparatus according to Aspect 15 or 16 further includes: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, sending an uplink message on the uplink time slot in the second frequency band, and continuing to count the PUSCH repetition.

[0109] Aspect 21: The apparatus according to Aspect 15 or 16 further includes: preventing switching to the uplink time slot in the second frequency band according to the switching configuration in response to the following items: the uplink time slot in the second frequency band overlaps with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, and the uplink time slot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink time slot.

[0110] Aspect 22: The apparatus according to Aspect 15 or 16 further includes: discarding the uplink transmission on the uplink time slot in the second frequency band in response to the following items: the uplink time slot in the second frequency band overlaps with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, and the uplink time slot is scheduled for UE transmission.

[0111] Aspect 23: The apparatus according to Aspect 15 or 16 further includes: in response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, the UE is not expected to be scheduled or configured to have the uplink time slot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

[0112] Aspect 24: An apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor coupled to the memory, the at least one processor being configured to: send a repetition configuration for sending a physical uplink shared channel (PUSCH) repetition in a first frequency band to a user equipment (UE); send a switching configuration to the UE for switching the uplink transmission to an uplink time slot in a second frequency band; and communicate with the UE based on a count of available time slots for sending PUSCH repetitions based on the repetition configuration and the switching configuration.

[0113] Aspect 25: The apparatus of aspect 24, wherein the first frequency band is time division duplex (TDD).

[0114] Aspect 26: An apparatus according to Aspect 24 or 25, wherein the at least one processor is further configured to: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, schedule the UE as or configure the UE to not have an uplink time slot in the second frequency band and to send during the PUSCH repetition in the first frequency band.

[0115] Aspect 27: An apparatus according to Aspect 24 or 25, wherein the at least one processor is further configured to: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during the PUSCH repetition, receive an uplink message on the uplink time slot in the second frequency band while continuing to count the PUSCH repetition.

[0116] Aspect 28: An apparatus according to aspect 24 or 25, wherein the at least one processor is further configured to: in response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, schedule the UE or configure the UE to not have an uplink time slot in the second frequency band and send during the PUSCH repetition in the first frequency band.

[0117] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the foregoing disclosure or may be acquired from practice of the various aspects.

[0118] As used, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used, a processor is implemented in hardware, firmware, and / or a combination of hardware and software.

[0119] Some aspects are described in conjunction with thresholds. As used, satisfying a threshold can refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0120] It will be apparent that the described systems and / or methods can be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the aspects. Thus, the operation and performance of these systems and / or methods are described without reference to specific software code, and it should be understood that software and hardware used to implement these systems and / or methods can be designed based at least in part on this description.

[0121] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various aspects. In fact, many of these features can be combined in a manner that is not specifically set forth in the claims and / or not disclosed in the specification. Although each dependent claim listed below may only directly depend on one claim, the disclosure of the various aspects includes each dependent claim in combination with each other claim in the claim set. A phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other arrangement of a, b, and c).

[0122] The elements, actions or instructions used should not be interpreted as critical or necessary unless expressly described as such. In addition, as used, the articles "a" and "an" are intended to include one or more items and can be used interchangeably with "one or more". In addition, as used, the terms "set" and "group" are intended to include one or more items (e.g., related items, unrelated items, a combination of related items and unrelated items, etc.) and can be used interchangeably with "one or more". If you only want to refer to one item, use the phrase "only one" or similar terms. In addition, as used, the terms "have", "have", "have" etc. are intended to be open terms. In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise expressly stated.

Claims

1. A method for wireless communication by a user equipment (UE), the method comprising: receiving a repetition configuration for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band; receiving a switching configuration for switching uplink transmissions to an uplink timeslot in a second frequency band; and Available time slots for sending PUSCH repetitions are counted based on the repetition configuration and the switching configuration. The method of claim 1 , wherein the first frequency band is time division duplex (TDD).

3. The method according to claim 2, further comprising: preventing switching to the uplink timeslot in the second frequency band according to the switching configuration in response to: The uplink timeslot in the second frequency band overlaps with a downlink timeslot in the first frequency band during a PUSCH repetition, and The uplink timeslot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink timeslot.

4. The method according to claim 2, further comprising: dropping uplink transmissions on the uplink timeslot in the second frequency band in response to: The uplink timeslot in the second frequency band overlaps with a downlink timeslot in the first frequency band during a PUSCH repetition, and The uplink time slot is scheduled for UE transmission.

5. The method according to claim 2, further comprising: In response to the uplink timeslot in the second frequency band overlapping with the downlink timeslot in the first frequency band during a PUSCH repetition, the UE is not expected to be scheduled or configured with the uplink timeslot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

6. The method according to claim 2, further comprising: In response to the uplink timeslot in the second frequency band overlapping with a downlink timeslot in the first frequency band during a PUSCH repetition, an uplink message is sent on the uplink timeslot in the second frequency band and PUSCH repetitions are continued to be counted.

7. The method according to claim 2, further comprising: preventing switching to the uplink timeslot in the second frequency band according to the switching configuration in response to: The uplink timeslot in the second frequency band overlaps with an uplink timeslot in the first frequency band or a switching period for the uplink timeslot in the first frequency band during a PUSCH repetition, and The uplink timeslot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink timeslot.

8. The method according to claim 2, further comprising: dropping uplink transmissions on the uplink timeslot in the second frequency band in response to: The uplink timeslot in the second frequency band overlaps with an uplink timeslot in the first frequency band or a switching period for the uplink timeslot in the first frequency band during a PUSCH repetition, and The uplink time slot is scheduled for UE transmission.

9. The method according to claim 2, further comprising: In response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, it is not expected that the UE is scheduled or configured to have the uplink time slot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

10. A method for wireless communication by a network device, the method comprising: sending a repetition configuration to a user equipment (UE) for sending a physical uplink shared channel (PUSCH) repetition in a first frequency band; sending a switching configuration to the UE for switching uplink transmission to an uplink timeslot in a second frequency band; and Communicating with the UE is performed based on counting available time slots for sending PUSCH repetitions based on the repetition configuration and the switching configuration. The method of claim 10 , wherein the first frequency band is time division duplex (TDD).

12. The method according to claim 10, further comprising: In response to the uplink timeslot in the second frequency band overlapping with the downlink timeslot in the first frequency band during a PUSCH repetition, the UE is scheduled or configured to not have an uplink timeslot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

13. The method according to claim 10, further comprising: In response to the uplink timeslot in the second frequency band overlapping with a downlink timeslot in the first frequency band during a PUSCH repetition, an uplink message is received on the uplink timeslot in the second frequency band while continuing to count PUSCH repetitions.

14. The method according to claim 10, further comprising: In response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, the UE is scheduled or configured to not have an uplink time slot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

15. An apparatus for wireless communication by a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: receiving a repetition configuration for transmitting a physical uplink shared channel (PUSCH) repetition in a first frequency band; receiving a switching configuration for switching uplink transmissions to an uplink timeslot in a second frequency band; and Available time slots for sending PUSCH repetitions are counted based on the repetition configuration and the switching configuration. The apparatus of claim 15 , wherein the first frequency band is time division duplex (TDD).

17. The apparatus according to claim 16, further comprising: preventing switching to the uplink timeslot in the second frequency band according to the switching configuration in response to: The uplink timeslot in the second frequency band overlaps with a downlink timeslot in the first frequency band during a PUSCH repetition, and The uplink timeslot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink timeslot.

18. The apparatus according to claim 16, further comprising: dropping uplink transmissions on the uplink timeslot in the second frequency band in response to: The uplink timeslot in the second frequency band overlaps with a downlink timeslot in the first frequency band during a PUSCH repetition, and The uplink time slot is scheduled for UE transmission.

19. The apparatus according to claim 16, further comprising: In response to the uplink timeslot in the second frequency band overlapping with the downlink timeslot in the first frequency band during a PUSCH repetition, the UE is not expected to be scheduled or configured with the uplink timeslot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

20. The apparatus according to claim 16, further comprising: In response to the uplink timeslot in the second frequency band overlapping with a downlink timeslot in the first frequency band during a PUSCH repetition, an uplink message is sent on the uplink timeslot in the second frequency band and PUSCH repetitions are continued to be counted.

21. The apparatus according to claim 16, further comprising: preventing switching to the uplink timeslot in the second frequency band according to the switching configuration in response to: The uplink timeslot in the second frequency band overlaps with an uplink timeslot in the first frequency band or a switching period for the uplink timeslot in the first frequency band during a PUSCH repetition, and The uplink timeslot is not scheduled for UE uplink transmission or the UE does not transmit on the uplink timeslot.

22. The apparatus according to claim 16, further comprising: dropping uplink transmissions on the uplink timeslot in the second frequency band in response to: The uplink timeslot in the second frequency band overlaps with an uplink timeslot in the first frequency band or a switching period for the uplink timeslot in the first frequency band during a PUSCH repetition, and The uplink time slot is scheduled for UE transmission.

23. The apparatus of claim 16, further comprising: In response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or the switching period for the uplink time slot in the first frequency band during the PUSCH repetition, it is not expected that the UE is scheduled or configured to have the uplink time slot in the second frequency band and to transmit during the PUSCH repetition in the first frequency band.

24. An apparatus for wireless communication, the apparatus comprising: Memory; and at least one processor coupled to the memory, the at least one processor configured to: sending a repetition configuration to a user equipment (UE) for sending a physical uplink shared channel (PUSCH) repetition in a first frequency band; sending a switching configuration to the UE for switching uplink transmission to an uplink timeslot in a second frequency band; and Communicating with the UE is performed based on counting available time slots for sending PUSCH repetitions based on the repetition configuration and the switching configuration.

25. The apparatus of claim 24, wherein the first frequency band is time division duplex (TDD).

26. The apparatus of claim 24, wherein the at least one processor is further configured to, in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during a PUSCH repetition, schedule or configure the UE to not have an uplink time slot in the second frequency band and to transmit during a PUSCH repetition in the first frequency band.

27. The apparatus of claim 24, wherein the at least one processor is further configured to: in response to the uplink time slot in the second frequency band overlapping with the downlink time slot in the first frequency band during a PUSCH repetition, receive an uplink message on the uplink time slot in the second frequency band while continuing to count PUSCH repetitions.

28. The apparatus of claim 24, wherein the at least one processor is further configured to, in response to the uplink time slot in the second frequency band overlapping with the uplink time slot in the first frequency band or a switching period for the uplink time slot in the first frequency band during a PUSCH repetition, schedule the UE or configure the UE to not have an uplink time slot in the second frequency band and to transmit during a PUSCH repetition in the first frequency band.

Images