Systems and methods for physical uplink shared channel repeated adaptation

Abstract

A wireless communication system and method are provided that relate to a physical uplink shared channel (PUSCH) repetition adaptation scheme when one or more PUSCH repetitions are discarded due to a conflict. Specifically, a user equipment (UE) may obtain data for uplink transmission on multiple repeated PUSCH instances. In response to determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions, the UE may discard the at least one repeated PUSCH instance. The UE may then use a configured grant to retransmit the data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission.

Description

[0001] M. Tahzadeh Boroujeni, Tao Luo, and S. Akalakaran

[0002] Cross - References

[0003] This application claims priority to U.S. Non - Provisional Application No. 17 / 124,392, filed on December 16, 2020, which is a non - provisional application of and claims priority to co - owned and co - pending U.S. Provisional Application No. 62 / 951,910, filed on December 20, 2019, and the entire contents of both applications are hereby expressly incorporated by reference. Technical Field

[0004] The technology of the present application discussed below relates to wireless communication systems, and more particularly to physical uplink shared channel (PUSCH) repetition adaptation when PUSCH repetition conflicts with one or more downlink symbols.

[0005] Introduction

[0006] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcasting, etc. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multi - access communication system may include several base stations (BSs), each of which simultaneously supports the communication of multiple communication devices, which may also be referred to as user equipment (UE).

[0007] In a wireless system, uplink transmissions from one or more UEs to a BS may include configured grants for transmission and / or dynamic grants. For example, multiple UEs are given periodic resources for data transmission using configured grants. The BS allocates configured grant instances to multiple UEs, and when each UE has data to transmit, the UE can randomly utilize these instances. Specifically, in the next - generation new radio (NR) network, PUSCH repetition (e.g., a series of repeated PUSCH instances) is adopted as a method to increase the coverage of the PUSCH carrying uplink data. However, the extended coverage of the PUSCH may sometimes cause a conflict between the time resources assigned for PUSCH repetition and the time resources assigned for one or more downlink symbols. When a conflict occurs, the particular PUSCH repetition is usually discarded, which may result in a performance loss in coverage. Some existing systems can configure another PUSCH repetition to compensate for the discarded PUSCH, but usually with significant latency.

[0008] Therefore, there is a need for an efficient PUSCH repetition adaptation scheme when PUSCH repetition conflicts with one or more downlink symbols.

[0009] Brief overview of some examples

[0010] The following provides an overview of some aspects of the present disclosure to provide a basic understanding of the technologies discussed. This overview is not an exhaustive survey of all contemplated features of the present disclosure, and is neither intended to identify key or critical elements of all aspects of the present disclosure, nor to attempt to define the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in an overview form as a prelude to the more detailed description that follows.

[0011] For example, in one aspect of the present disclosure, a method of wireless communication includes obtaining, at a user equipment (UE), data for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances. The method further includes determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions and discarding the at least one repeated PUSCH instance. The method further includes retransmitting, using a configured grant, data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission.

[0012] In another aspect of the present disclosure, a user equipment (UE) for wireless communication is provided. The UE includes a memory configured to obtain data for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances. The UE further includes a processor configured to: determine that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions and discard the at least one repeated PUSCH instance. The UE further includes a transceiver configured to retransmit, using a configured grant, data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission.

[0013] In another aspect of the present disclosure, a non-transitory processor-readable storage medium storing processor-executable instructions for wireless communication is disclosed. The instructions are executed by a processor to perform operations including obtaining, at a user equipment (UE), data for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances. The operations further include determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions. The operations further include discarding the at least one repeated PUSCH instance and retransmitting, using a configured grant, data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission.

[0014] In another aspect of the present disclosure, a wireless communication system is disclosed. The system includes means for obtaining data at a user equipment (UE) for uplink transmission on multiple repeated physical uplink shared channel (PUSCH) instances. The system further includes means for determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions and means for discarding the at least one repeated PUSCH instance. The system further includes means for retransmitting data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission using a configured grant.

[0015] After reading the following description of specific exemplary aspects of the invention in conjunction with the accompanying drawings, other aspects, features, and aspects of the invention will be apparent to those of ordinary skill in the art. Although the features of the invention may be discussed below with respect to certain aspects and drawings, all aspects of the invention may include one or more of the advantageous features discussed herein. In other words, although one or more aspects may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various aspects of the invention discussed herein. In a similar manner, although the exemplary aspects may be discussed below as device, system, or method aspects, it should be understood that such exemplary aspects may be implemented in various devices, systems, and methods. Brief Description of the Drawings

[0017] Figure 1 Illustrates a wireless communication network in accordance with some aspects of the present disclosure.

[0018] Figure 2 Illustrates a scheduling / configuration timeline in accordance with one or more aspects of the present disclosure.

[0019] Figure 3A Illustrates configured grant resources in accordance with one or more aspects of the present disclosure.

[0020] Figure 3B Illustrates a PUSCH repetition adaptation scheme in the case of discarded PUSCH repetitions due to conflicts in accordance with one or more aspects of the present disclosure.

[0021] Figure 4 Is a block diagram of a user equipment (UE) in accordance with some aspects of the present disclosure.

[0022] Figure 5 Is a block diagram of an exemplary base station (BS) in accordance with some aspects of the present disclosure.

[0023] Figure 6 Illustrates operations performed by a UE in accordance with aspects of the present disclosure and Figure 3BThe logic flow diagram corresponding to the PUSCH repetition adaptation scheme shown in [].

[0024] Figure 7 Illustrates the interaction transmission timeline between a UE and a BS for implementing the PUSCH repetition adaptation scheme shown in []. Figure 6 The PUSCH repetition adaptation scheme shown in [].

[0025] Figure 8 Illustrates the logic flow diagram executed by a UE corresponding to an embodiment of determining configured resources for retransmission after discarding PUSCH repetitions according to aspects of the present disclosure.

[0026] Detailed description

[0027] The detailed description set forth below in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0028] The present disclosure generally relates to wireless communication systems (also referred to as wireless communication networks). In various aspects, techniques and devices may be used in wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, global system for mobile communications (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0029] OFDMA networks enable radio technologies such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long-Term Evolution (LTE) is a UMTS version that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in literature provided by an organization named "3rd Generation Partnership Project" (3GPP), while cdma2000 is described in literature from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a cooperation among groups of telecommunications associations that aims to define globally applicable third-generation (3G) mobile phone specifications. 3GPP Long-Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP can define specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure focuses on the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond, which have shared access to the wireless spectrum among networks using a collection of new and different radio access technologies or radio air interfaces.

[0030] Specifically, 5G networks envision diverse deployments, diverse spectrums, and diverse services and devices that can be achieved using an OFDM-based unified air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to: (1) provide coverage for massive Internet of Things (IoT) with ultra-high density (e.g., about 1M nodes / km 2 ), ultra-low complexity (e.g., about dozens of bits per second), ultra-low energy (e.g., about 10+ years of battery life), and deep coverage capable of reaching challenging locations; (2) provide coverage including critical mission control for users with strong security (to protect sensitive personal, financial, or confidential information), ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 ms), and with a wide range of mobility or lack of wide range of mobility; and (3) provide coverage with enhanced mobile broadband, which includes extremely high capacity (e.g., about 10 Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rate), and deep awareness with advanced discovery and optimization.

[0031] 5G NR can be implemented to: use an optimized OFDM-based waveform with scalable parameter design and transmission time interval (TTI); have a common, flexible framework to efficiently multiplex services and features using dynamic, low-latency time-division duplex (TDD) / frequency-division duplex (FDD) designs; and have advanced radio technologies such as massive multiple-input multiple-output (MIMO), robust millimeter-wave (mmWave) transmission, advanced channel decoding, and device-centric mobility. The scalability of the parameter design in 5G NR (and the scaling of subcarrier spacing) can efficiently address operating diverse services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments with less than 3 GHz FDD / TDD implementation, the subcarrier spacing can occur at 15 kHz, e.g., on bandwidths (BW) of 5, 10, 20 MHz, etc. For other various outdoor and small cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing can occur at 30 kHz on 80 / 100 MHz BW. For other various indoor broadband implementations, by using TDD on the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz on 160 MHz BW. Finally, for various deployments transmitting with mmWave components using TDD at 28 GHz, the subcarrier spacing can occur at 120 kHz on 500 MHz BW.

[0032] The scalable parameter design of 5G NR enables scalable TTI to meet diverse latency and quality of service (QoS) requirements. For example, shorter TTI can be used for low latency and high reliability, while longer TTI can be used for higher spectral efficiency. The efficient multiplexing of long TTI and short TTI allows transmissions to start at symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with uplink / downlink scheduling information, data, and acknowledgments in the same subframe. The self-contained integrated subframe supports communication in unlicensed or contention-based shared spectrums, supports adaptive uplink / downlink that can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0033] Various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are merely representative and not limiting. Based on the teachings herein, one of ordinary skill in the art should appreciate that the aspects disclosed herein can be implemented independently of any other aspect and two or more of these aspects can be combined in various ways. For example, any number of the aspects set forth herein can be used to implement an apparatus or practice a method. Additionally, other structures, functionality, or both, which supplement or differ from one or more of the aspects set forth herein, can be used to implement such an apparatus or practice such a method. For example, a method can be implemented as part of a system, device, apparatus, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. Moreover, one aspect can include at least one element of a claim.

[0034] Figure 1 A wireless communication network 100 in accordance with some aspects of the present disclosure is illustrated. Network 100 can be a 5G network. Network 100 includes several base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. BS 105 can be a station that communicates with UE 115 and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, and so on. Each BS 105 can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the specific geographical coverage area of BS 105 and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0035] BS 105 can provide communication coverage for macro cells or small cells (such as pico cells or femto cells), and / or other types of cells. Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and can allow unrestricted access by UEs having a service subscription with the network provider. Small cells (such as pico cells) generally cover a relatively small geographical area and can allow unrestricted access by UEs having a service subscription with the network provider. Small cells (such as femto cells) generally also cover a relatively small geographical area (e.g., a residence), and in addition to unrestricted access, can be accessed by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in the residence, etc.) in a restricted manner. The BS for a macro cell can be referred to as a macro BS. The BS for a small cell can be referred to as a small cell BS, pico BS, femto BS, or home BS. In Figure 1In the example shown, BS105d and 105e can be conventional macro BSs, while BS105a - 105c can be macro BSs enabled with one of three - dimensional (3D), full - dimensional (FD), or massive MIMO. BS105a - 105c can utilize their higher - dimensional MIMO capabilities to increase coverage and capacity by using 3D beamforming in both elevation and azimuth beamforming. BS105f can be a small cell BS, which can be a home node or a portable access point. BS105 can support one or more (e.g., two, three, four, etc.) cells.

[0036] Network 100 can support synchronous or asynchronous operation. For synchronous operation, each BS can have similar frame timing, and transmissions from different BSs can be approximately aligned in time. For asynchronous operation, each BS can have different frame timing, and transmissions from different BSs may not be aligned in time.

[0037] Each UE 115 is dispersed throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a terminal, mobile station, subscriber unit, station, etc. UE 115 can be a cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, tablet computer, laptop computer, cordless phone, wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). In another aspect, the UE can be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC can also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a - 115d are examples of mobile smart - phone - type devices accessing the network 100. UE 115 can also be a machine specifically configured for connected communication, including machine - type communication (MTC), enhanced MTC (eMTC), narrow - band IoT (NB - IoT), etc. UE 115e - 115k are examples of various machines configured for communication accessing the network 100. UE 115 can be capable of communicating with any type of BS, whether it is a macro BS or a small cell, etc. In Figure 1 In, lightning bolts (e.g., communication links) indicate wireless transmissions between UE 115 and serving BS105, desired transmissions between BSs, and backhaul transmissions between BSs, where serving BS105 is the BS designated to serve UE 115 on the downlink and / or uplink.

[0038] In operation, BS105a - 105c may use 3D beamforming and coordinated spatial techniques (such as coordinated multi - point (CoMP) or multi - connectivity) to serve UEs 115a and 115b. Macro BS105d may perform backhaul communication with BS105a - 105c, as well as small cell BS105f. Macro BS105d may also transmit multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information (such as weather emergencies or alerts, such as Amber alerts or Gray alerts).

[0039] BS105 may also communicate with the core network. The core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some BS105s (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG - C, NG - U, etc.), and may perform radio configuration and scheduling for communication with UEs 115. In various examples, BS105s may communicate with each other directly or indirectly (e.g., via the core network) over a backhaul link (e.g., X1, X2, etc.), which may be a wired or wireless communication link.

[0040] Network 100 may also support mission - critical communication with ultra - reliable and redundant links for mission - critical devices (such as UE 115e, which may be a drone). The redundant communication links with UE 115e may include links from macro BSs 105d and 105e, as well as from small cell BS105f. Other machine - type devices (such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device)) may communicate directly with BSs (such as small cell BS105f and macro BS105e) via Network 100, or may be in a multi - hop configuration by communicating with another user equipment that relays their information to the network (such as UE 115f communicating temperature measurement information to smart meter UE115g, which is then reported to the network via small cell BS105f). Network 100 may also provide additional network efficiency via dynamic, low - latency TDD / FDD communication (such as in vehicle - to - vehicle (V2V)).

[0041] In some implementations, network 100 utilizes an OFDM-based waveform for communication. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are typically also referred to as subcarriers, frequency tones, frequency bins, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0042] BS105 can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS105 to UE 115, and UL refers to the transmission direction from UE115 to BS105. This communication can take the form of radio frames. A radio frame can be divided into multiple subframes or time slots, e.g., approximately 10. Each time slot can be further divided into sub-slots. In the FDD mode, simultaneous UL and DL transmissions can occur in different frequency bands. For example, each subframe includes a UL subframe in the UL frequency band and a DL subframe in the DL frequency band. In the TDD mode, UL and DL transmissions occur in the same frequency band at different time periods. For example, a subset of subframes in the radio frame (e.g., DL subframes) can be used for DL transmissions, and another subset of subframes in the radio frame (e.g., UL subframes) can be used for UL transmissions.

[0043] DL subframes and UL subframes can be further divided into several regions. For example, each DL or UL subframe may have predefined regions for the transmission of reference signals, control information, and data. A reference signal is a predefined signal that facilitates communication between BS105 and UE 115. For example, a reference signal may have a specific pilot pattern or structure, where the pilot frequency tones may span the operating BW or frequency band, and each pilot frequency tone is positioned at a predefined time and a predefined frequency. For example, BS105 may transmit cell-specific reference signals (CRS) and / or channel state information reference signals (CSI-RS) so that UE 115 can estimate the DL channel. Similarly, UE 115 may transmit sounding reference signals (SRS) so that BS105 can estimate the UL channel. Control information may include resource assignment and protocol control. Data may include protocol data and / or operation data. In some aspects, BS105 and UE 115 may use self-contained subframes to communicate. A self-contained subframe may include a portion for DL communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL communication than for UL communication. A UL-centric subframe may include a longer duration for UL communication than for DL communication.

[0044] In some aspects, network 100 may be an NR network deployed on licensed spectrum. BS105 may transmit synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in network 100 to facilitate synchronization. BS105 may broadcast system information associated with network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, BS105 may broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on the physical broadcast channel (PBCH), and may broadcast the RMSI and / or OSI on the physical downlink shared channel (PDSCH).

[0045] In some aspects, UE 115 attempting to access network 100 may perform an initial cell search by detecting the PSS from BS105. The PSS may achieve time slot timing synchronization and may indicate a physical layer identity value. UE 115 may then receive the SSS. The SSS may achieve radio frame synchronization and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell. The PSS and SSS may be located in the central portion of the carrier or at any suitable frequency within the carrier.

[0046] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for the RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to the random access channel (RACH) procedure, paging, control resource sets (CORESETs) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.

[0047] After obtaining the MIB, RMSI, and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may transmit a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include the detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or backoff indicator. Upon receiving the random access response, the UE 115 may transmit a connection request to the BS 105 and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG 1), message 2 (MSG 2), message 3 (MSG 3), and message 4 (MSG 4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may transmit the random access preamble and the connection request in a single transmission, and the BS 105 may respond by transmitting the random access response and the connection response in a single transmission.

[0048] After establishing the connection, the UE 115 and the BS 105 can enter the normal operation phase, where operation data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL communication. The BS 105 may transmit UL and / or DL scheduling grants to the UE 115 via the PDCCH. The BS 105 may transmit DL communication signals to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may transmit UL communication signals to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.

[0049] In some examples, BS105 may use Hybrid Automatic Repeat reQuest (HARQ) to communicate data with UE 115 to improve communication reliability. BS105 may schedule UE 115 for PDSCH communication by transmitting a DL grant in the PDCCH. BS105 may transmit a DL data packet to UE 115 according to the scheduling in the PDSCH. The DL data packet may be transmitted in the form of a Transport Block (TB). If UE 115 successfully receives the DL data packet, UE 115 may transmit a HARQ ACK to BS105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 may transmit a HARQ NACK to BS105. Once receiving the HARQ NACK from UE 115, BS105 retransmits the DL data packet to UE 115. The retransmission may include the same encoded version of the DL data as the initial transmission. Alternatively, the retransmission may include a different encoded version of the DL data from the initial transmission. UE 115 may apply soft combining to combine the encoded data received from the initial transmission and the retransmission for decoding. BS105 and UE 115 may also apply HARQ to UL communication using a mechanism that is substantially similar to DL HARQ.

[0050] In some aspects, network 100 may operate on the system BW or component carrier BW. Network 100 may divide the system BW into multiple BWPs (e.g., multiple parts). BS105 may dynamically assign UE 115 to operate on a certain BWP (e.g., a certain part of the system BW). The assigned BWP may be referred to as the active BWP. UE 115 may monitor the active BWP for signaling information from BS105. BS105 may schedule UE 115 for UL or DL communication in the active BWP. In some aspects, BS105 may assign a pair of BWPs within a component carrier to UE 115 for UL and DL communication. For example, the BWP pair may include one BWP for UL communication and one BWP for DL communication. BS105 may additionally configure UE 115 to have one or more CORESETs in the BWP. The CORESET may include a set of frequency resources that span several symbols in time. BS105 may configure UE 115 to have one or more search spaces for PDCCH monitoring based on the CORESET. UE 115 may perform blind decoding in the search space to search for DL control information (e.g., UL and / or DL scheduling grants) from the BS. In one example, BS105 may configure UE 115 to have a BWP, a CORESET, and / or a PDCCH search space via RRC configuration.

[0051] In some aspects, network 100 may operate on a shared band or unlicensed band (e.g., at about 3.5 gigahertz (GHz) in the millimeter wave band, sub-6 GHz, or higher frequencies). Network 100 may divide the band into multiple channels, e.g., each channel occupying about 20 megahertz (MHz). BS105 and UE 115 may be operated by multiple network operating entities sharing resources in the shared communication medium and may utilize the LBT procedure to capture the channel occupancy time (COT) in the shared medium for communication. The COT may be non-consecutive in time and may refer to the amount of time when a wireless node can transmit a frame when the wireless node wins contention for the wireless medium. Each COT may include multiple transmission time slots. The COT may be referred to as a transmission opportunity (TXOP). Before transmitting in the band, BS105 or UE 115 may perform LBT in the band. LBT may be based on energy detection or signal detection. For energy detection, when the signal energy measured from the channel is greater than a specific signal energy threshold, BS105 or UE 115 may determine that the channel is busy or occupied. For signal detection, when a specific reservation signal (e.g., a preamble signal sequence) is detected in the channel, BS105 or UE 115 may determine that the channel is busy or occupied.

[0052] Figure 2 Illustrated is a scheduling / configuration timeline 200 according to one or more aspects of the present disclosure. The scheduling / configuration timeline 200 may correspond to a scheduling / configuration timeline for communication between BS105 and UE 115 in network 100. In Figure 2 it, the x-axis represents time in some constant units. Figure 2 A frame structure 201 is shown that includes multiple time slots 204 over time. The indices of the time slots 204 are S0 to S9. For example, the BS may communicate with the UE in units of time slots 204. The time slot 204 may also be referred to as a transmission time interval (TTI). Each time slot 204 or TTI carries a media access control (MAC) layer transport block. Each time slot 204 may include several symbols in time and several frequency tones in frequency. Each time slot 204 may include a DL control portion followed by at least one of a subsequent DL data portion, UL data portion, and / or UL control portion. In the context of LTE, the DL control portion, DL data portion, UL data portion, and UL control portion may be referred to as a physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), physical uplink shared channel (PUSCH), and physical uplink control channel (PUCCH), respectively.

[0053] The patterned boxes indicate the transmission of DL control information (DCI), DL data, UL control information (UCI), UL data, ACK, and / or NACK in respective corresponding time slots 204. Although the entire time slot 204 is patterned, the transmission may occur only in the corresponding portion of the time slot 204. As shown, the BS transmits DCI 220 in the time slot 204 with index S0 (e.g., in the DL control portion of the time slot 204). DCI 220 may indicate a UL grant for the UE. The UE transmits UCI 221 to the BS in the time slot 204 with index S6 (e.g., in the UL control portion of the time slot 204) based on the UL assignment. The time slot 204 with index S4 is the fourth time slot starting from the time slot 204 with index S0. UCI 221 is the scheduled UL, which is granted by the UL grant indicated in DCI 220.

[0054] Additionally, the BS transmits DCI 224 in the time slot 204 with index S3 (e.g., in the DL control portion of the time slot 204). DCI 224 may indicate a DL grant for the UE in the same time slot 204 with index S3. Accordingly, the BS transmits a DL data signal 226 to the UE in the time slot 204 with index S3 (e.g., in the DL data portion of the time slot 204). The UE may receive DCI 224 and receive the DL data signal 226 based on the DL grant. The DL data signal 226 is the scheduled DL, which is granted by the DL grant indicated in DCI 224.

[0055] After receiving the DL data signal 226, UE 115 may report the reception status of the DL data signal 226 to the BS by transmitting an acknowledgement (ACK) / negative acknowledgement (NACK) signal 228. The ACK / NACK signal 228 refers to a feedback signal carrying an ACK or a NACK. The feedback may be an acknowledgement (ACK) indicating that the UE has successfully received the DL data or may be a negative acknowledgement (NACK) indicating that the UE has not successfully received the DL data (e.g., including errors or error correction failures). The UCI may include CSI - part 1, CSI - part 2, and / or the ACK / NACK signal 228. For example, the ACK / NACK signal 228 may be part of the UCI.

[0056] The ACK / NACK signal 228 may be associated with a Hybrid Automatic Repeat reQuest (HARQ) process. In the HARQ process, a transmitting node may transmit various encoded versions of information data to a receiving node. For example, the transmitting node may transmit a first encoded version of the information data to the receiving node. Upon receiving a NACK signal from the receiving node, the transmitting node may transmit a second encoded version of the information data to the receiving node. When both the received first encoded version and the received second encoded version have errors, the receiving node may combine the received first encoded version and the received second encoded version for error correction.

[0057] The transmission of data may be a self-scheduled (i.e., unscheduled) transmission or a scheduled transmission. As discussed above, the UE transmits the UCI 221 via a scheduled UL grant (e.g., transmission in the PDCCH via DCI 220). In addition, the UE receives the DL data signal 226 via a scheduled grant (e.g., transmission of DCI in the PDCCH indicated in DCI 224). A configured UL transmission is an unscheduled transmission that is performed on a channel without a UL grant. A configured UL transmission may also be referred to as grant-free, grant-less, or self-scheduled transmission. In some examples, the UE may transmit UL control information and / or UL data based on a configured grant. In addition, the configured UL data may also be referred to as grant-free UL data, grant-less UL data, unscheduled UL data, or autonomous UL (AUL) data. In addition, the configured grant may also be referred to as grant-free grant, unscheduled grant, or self-scheduled grant. The resources and other parameters used by the UE for configured grant transmission may be provided by the BS in one or more of an RRC configuration or an active DCI, without an explicit grant for each UE transmission.

[0058] To avoid collisions when communicating in a shared or unlicensed spectrum, the UE may perform LBT to ensure that the shared channel is clear before transmitting a signal on the shared channel. In one example, if the channel is available (the result of the LBT execution is LBT passed), the UE may perform a UL transmission. If the channel is not available (the result of the LBT execution is LBT failed), the UE may back off and perform the LBT procedure again at a later time point. Thus, based on LBT, the UE may not be able to obtain the COT because other nodes are operating on the shared channel. The ability of the UE 115 to transmit on a UL transmission depends on whether the UE can obtain access to the medium for data transmission and / or reception. The UE may wish to transmit a UL communication signal in the configured grant resources rather than waiting for a UL grant.

[0059] In addition, to support more resource allocation in the network, transmissions can be scheduled based on semi-persistent scheduling (SPS). The BS can allocate one or more configured grant resources 234 in a frequency band (e.g., an unlicensed band or a shared band) for UL or DL transmissions. In some examples, the configured grant resources 234 are based on SPS. After the LBT result is LBT passed, the BS can perform LBT and obtain the COT during which the BS transmits SPS to the UE group. The BS can transmit the configuration of the configured grant resources (e.g., the configured grant resources 234) to the UE. The BS can transmit SPS, for example, via an RRC configuration message. The RRC configuration message can configure semi-persistent resources for AUL transmissions for the UE. In some examples, UE-specific RRC signaling configures and / or reconfigures the location of the PUSCH for UCI transmissions. SPS includes a plurality of resource allocations spaced apart in time. The plurality of resource allocations can be spaced apart in time according to a time interval of, for example, approximately 40 ms. In this example, the plurality of resources are allocated to each UE in the UE group every 40 ms. The resources can be shared with the UE group, and the UE can contend for the resources. SPS can use relative timing (e.g., an offset time period relative to the current time period for conveying scheduling information) to indicate the scheduling information.

[0060] In some examples, the UE transmits the UL communication signal 230 in the configured grant resources 234 using the resource allocation specified in the SPS. The BS can receive the UL communication signal 230 in the configured grant resources 234. The UL communication signal 230 can include UL control information (UCI), a demodulation reference signal (DMRS), a phase-tracking reference signal (PTRS) (not shown), and UL data (which can also be referred to as configured UL data). The UCI can include, for example, normal UCI and / or configured grant UCI (CG-UCI) 232. Although in Figure 2 FIG., the ACK / NACK signal 228 and the CG-UCI 232 are shown separate from the UL communication signal 230, it should be understood that the ACK / NACK signal 228 and / or the CG-UCI 232 can be included in the UL communication signal 230.

[0061] Normal UCI may include HARQ ACK / NACK signals, channel state information (CSI), and / or scheduling requests (SR). HARQ ACK / NACK may also be referred to as HARQ-ACK or ACK / NACK (e.g., ACK / NACK signal 228). Additionally, CSI may include CSI-Part1 and CSI-Part2. CSI-Part1 may include information related to broadband channel quality indicator (CQI), subband differential CQI, and / or precoding matrix indicator (PMI) determined based on reference signals in DL communication (e.g., CSI-RS). CSI-Part2 may include information related to CSI-RS resource indicator (CRI), rank indicator (RI), layer indicator (LI) determined based on reference signals in DL communication (e.g., RSI-RS). Each normal UCI (e.g., ACK / NACK, CSI-Part1, CSI-Part2) may be encoded independently. CG-UCI 232 is associated with a configured grant and indicates information associated with normal UCI (e.g., ACK / NACK, CSI, and SR) and / or configured UL data (e.g., UL data signal 222).

[0062] DMRS may include pilot symbols distributed across frequency channels to enable a UE or a BS to perform channel estimation and demodulation for decoding. The pilot symbols may be generated from a predetermined sequence with a specific pattern, and the remaining symbols may carry UL data. The system may beamform the DMRS, keep it within the scheduled resources, and / or transmit the DMRS in DL or UL channels only when necessary. For example, DMRS allows a receiver to determine the channel estimation of a frequency channel, where the channel estimation may be used to recover UL data. Additionally, PTRS tracks the phases of local oscillators at the transmitter and the receiver and accordingly minimizes the impact of oscillator phase noise on system performance.

[0063] Figure 3A A configured grant resource 300 in accordance with one or more aspects of the present disclosure is illustrated. The configured grant resource 300 may be communicated between BS105 and UE 115 of network 100 and may correspond to Figure 2 the configured grant resource 234 in Figure 3B . The configured grant resource 300 includes a configured grant UCI (CG-UCI) resource 302 and a configured grant PUSCH (CG-PUSCH) resource 304. In some embodiments, as further illustrated in

[0064] Reference is made to Figure 2In related discussions, the UE may transmit at least some portions of the normal UCI in the CG-UCI resource 302, and the CG-UCI 232 may transmit the configured UL data in the CG-PUSCH resource 304. For example, the UE may transmit a UL communication signal that includes the CG-UCI 232 multiplexed with at least some portions of the normal UCI and the configured UL data.

[0065] The configured grant resource may be referred to as a time-frequency resource. If the PUCCH transmission does not overlap with the configured grant resource 234 during a time period, the UE may transmit the UCI 221 and the ACK / NACK 228 in the PUCCH. However, if the PUCCH transmission overlaps with the configured grant resource 234 during a time period, the UE may determine whether to transmit the UL communication signal (e.g., CSI-Part 1, CSI-Part 2, ACK / NACK) in the PUCCH or the PUSCH and further determine the components to be included in the UL communication signal. In Figure 2 the PUCCH transmission overlaps with the configured grant resource 234 during a time period.

[0066] As discussed, the UCI 221 may include three UCI parts (e.g., CSI-Part 1, CSI-Part 2, and ACK / NACK). For the CG-UCI 232, the number of UCI parts may be four. It may be difficult for the UE to multiplex more than three UCI parts. Additionally, in the case of more UCI parts, the total number of REs occupied by the UCI may increase. Therefore, if the number of UCI parts for transmission exceeds a first threshold (e.g., three parts) or the total number of REs occupied by the UCI exceeds a second threshold, the UE may determine which UCI part(s) to remove and / or which UCI part(s) to include in the UL transmission based on a set of priority rules. The UE may determine whether to transmit the UL communication signal 230 in the PUCCH or the PUSCH based on the set of priority rules.

[0067] In some aspects, the UE may determine that PUCCH transmissions overlap with configured grant resources during a time period. The UE may desire to transmit a CG-PUSCH and associated CG-UCI. The PUCCH transmission may include a first UCI that includes a first number of parts based on a set of priority rules. The UE may determine whether to transmit only the first UCI in the PUCCH resources associated with the PUCCH transmission or to remove at least one of the parts included in the first number of parts and transmit the remaining part of the first UCI multiplexed with the CG-PUSCH and associated CG-UCI in the configured grant resources. The UE may transmit the UL communication signal based on the determination of whether to transmit the first UCI in the PUCCH resources or to remove at least one of the parts included in the first number of parts and transmit the remaining part along with the CG-PUSCH and associated CG-UCI in the configured grant resources.

[0068] Figure 3B Illustrated is a PUSCH repetition adaptation scheme in the case of discarded PUSCH repetitions due to conflicts, according to one or more aspects of the present disclosure. As discussed with respect to Figure 2 and Figure 3A uplink data may be transmitted on CG-PUSCH resource instances configured by the system, which may be reflected in system information, RRC signaling, etc., sent to the BS. In one embodiment, the CG-PUSCH 306 may be assigned for normal coverage of the PUSCH carrying uplink data.

[0069] In some embodiments, a series of repeated PUSCH instances 306a, 306b,... 306n may be used to extend the coverage of the PUSCH. For example, under normal coverage, the CG-PUSCH 306 may be a time-frequency resource block (e.g., which covers 1 ms in time). Under extended coverage, the PUSCH repetitions 306a-n may be a series of temporally consecutive time-frequency resource blocks that cover N ms in time.

[0070] In some embodiments, in the case of extended coverage in time, the PUSCH repetitions 306a-n are more likely to conflict with one or more downlink symbol transmissions. For example, the PUSCH repetition 306b may conflict with the time resources assigned to downlink symbols, and the PUSCH repetition 306b may be discarded (as shown by the shaded box 306b), resulting in a performance loss in coverage.

[0071] In view of the performance loss problem caused by PUSCH repetitions discarded due to downlink symbol collisions, the embodiments described herein provide a PUSCH repetition adaptation scheme that allows the use of configured resources to retransmit uplink data that would otherwise have been carried by the discarded PUSCH repetitions. Specifically, in an NR network, some uplink data transmissions using configured grants may be allowed to perform uplink transmissions without a dynamic grant (e.g., without DCI) at some configured times with configured resources and transmission parameters. Such configured resources can be used to compensate for discarded PUSCH repetitions.

[0072] For example, such configured resources may include a series of periodic configured grants 308a, 308b, 308c, etc. for uplink transmission, which may be assigned for every four time slots. When a PUSCH repetition 306b is discarded due to a collision, based on the timing of the PUSCH repetition 306b, the first available uplink configured grant (e.g., configured grant 308b) after the discard time can be used to retransmit the discarded PUSCH repetition 306b. In this case, the uplink data that would otherwise have been carried by the PUSCH repetition 306b can be retransmitted on the configured grant 308b.

[0073] Figure 4 is a block diagram of an exemplary UE 400 in accordance with some aspects of the present disclosure. For example, the UE 400 may be the UE 115 discussed above in Figure 1 or the UE 202 shown in other figures. As shown, the UE 400 may include a processor 402, a memory 404, a PUSCH repetition adaptation module 408, a communication interface 409, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416. These elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0074] The processor 402 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 402 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0075] Memory 404 may include cache memory (e.g., the cache memory of processor 402), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard disk drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, memory 404 includes non-transitory computer-readable media. Memory 404 may store or have recorded thereon instructions 406. The instructions 406 may include instructions that, when executed by processor 402, cause processor 402 to perform the operations described herein with reference to UE 115 in connection with aspects of the present disclosure (e.g., Figures 3A - 3B and Figures 6 - 8 of the aspects). The instructions 406 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform these operations, such as by causing one or more processors (such as processor 402) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be construed broadly to include any type of computer-readable statement. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or many computer-readable statements.

[0076] The PUSCH repetition adaptation module 408 may communicate with the communication interface 409 to receive messages from or transmit messages to another device. Each of the PUSCH repetition adaptation module 408 and the communication interface 409 may be implemented via hardware, software, or a combination thereof. For example, each of the PUSCH repetition adaptation module 408 and the communication interface 409 may be implemented as a processor, circuitry, and / or instructions 406 stored in memory 404 and executed by processor 402. In some examples, the PUSCH repetition adaptation module 408 and the communication interface 409 may be integrated within the modem subsystem 412. For example, the PUSCH repetition adaptation module 408 and the communication interface 409 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 412. In some examples, the UE may include one of the PUSCH repetition adaptation module 408 and the communication interface 409. In other examples, the UE may include both the PUSCH repetition adaptation module 408 and the communication interface 409.

[0077] The PUSCH repetition adaptation module 408 and the communication interface 409 may be used for various aspects of the present disclosure, such as, Figures 3A - 3B and Figures 6 - 8Aspects of the PUSCH repetition adaptation module 408 are configured to receive configured grants (including CG-PUSCH, PUSCH repetition, etc.) and / or dynamic grants from a BS (e.g., 105). The PUSCH repetition adaptation module 408 is further configured to transmit uplink data to the BS via the configured grant and / or dynamic grant. The PUSCH repetition adaptation module 408 is further configured to detect conflicts between PUSCH repetitions and downlink symbols, and then discard the conflicting PUSCH repetitions. The PUSCH repetition adaptation module 408 is further configured to determine available preconfigured uplink resources, and then retransmit the uplink data that should have been transmitted on the discarded PUSCH repetitions on the available preconfigured uplink resources.

[0078] The communication interface 409 is configured to coordinate with the PUSCH repetition adaptation module 408 to receive uplink or downlink scheduling grants from the BS, and / or communicate with the BS according to the uplink or downlink scheduling grants. The communication interface 409 is further configured to transmit uplink data to the BS.

[0079] As shown, the transceiver 410 may include a modem subsystem 412 and an RF unit 414. The transceiver 410 may be configured to communicate bidirectionally with other devices (such as the BS 105). The modem subsystem 412 may be configured to modulate and / or encode data from the memory 404, the PUSCH repetition adaptation module 408, and / or the communication interface 409 according to a modulation and coding scheme (MCS) (e.g., low density parity check (LDPC) coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). The RF unit 414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data from the modem subsystem 412 (for outbound transmissions) or the modulated / encoded data of transmissions from another source such as the UE 115 or the BS 105 (e.g., PUCCH, PUSCH, channel reports, ACK / NACK). The RF unit 414 may be further configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in the transceiver 410, the modem subsystem 412 and the RF unit 414 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0080] The RF unit 414 may provide the modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 416 for transmission to one or more other devices. The antenna 416 may further receive data messages transmitted from other devices. The antenna 416 may provide the received data messages for processing and / or demodulation at the transceiver 410. The transceiver 410 may provide the demodulated and decoded data (e.g., DL data blocks, PDSCH, PUSCH, BWP hopping configurations, and / or instructions) to the PUSCH repetition adaptation module 408 and / or the communication interface 409 for processing. The antenna 416 may include multiple antennas of similar or different designs to maintain multiple transmission links. The RF unit 414 may configure the antenna 416.

[0081] In one aspect, the UE 400 may include multiple transceivers 410 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 400 may include a single transceiver 410 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 410 may include various components, and different combinations of the components may implement different RATs.

[0082] Figure 5 is a block diagram of an exemplary BS 500 according to some aspects of the present disclosure. For example, the BS 500 may be the BS105 discussed above in Figure 1 and the BS204 described in other figures. As shown, the BS 500 may include a processor 502, a memory 504, an RRC configuration module 508, a communication interface 509, a transceiver 510 that includes a modem subsystem 512 and an RF unit 514, and one or more antennas 516. These elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0083] The processor 502 may have various features as a dedicated type of processor. For example, these features may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0084] Memory 504 may include cache memory (e.g., the cache memory of processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, a memristor-based array, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, memory 504 may include non-transitory computer-readable media. Memory 504 may store instructions 506. Instructions 506 may include instructions that, when executed by processor 502, cause processor 502 to perform the operations described herein (e.g., Figure 2 , Figures 3A - 3B and Figures 6 - 8 aspects). Instructions 506 may also be referred to as code, which may be broadly interpreted to include any type of computer-readable statement as discussed above with reference to Figure 4 .

[0085] The RRC configuration module 508 may communicate with the communication interface 509 to receive messages from or transmit messages to another device. Each of the RRC configuration module 508 and the communication interface 509 may be implemented via hardware, software, or a combination thereof. For example, each of the RRC configuration module 508 and the communication interface 509 may be implemented as a processor, circuitry, and / or instructions 506 stored in memory 504 and executed by processor 502. In some examples, the RRC configuration module 508 and the communication interface 509 may be integrated within the modem subsystem 512. For example, the RRC configuration module 508 and the communication interface 509 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 512. In some examples, the UE may include one of the RRC configuration module 508 and the communication interface 509. In other examples, the UE may include both the RRC configuration module 508 and the communication interface 509.

[0086] The RRC configuration module 508 and the communication interface 509 may be used in various aspects of the present disclosure, such as, Figures 3A - 3B and Figures 6 - 8 aspects. The RRC configuration module 508 is configured to allocate and send uplink and / or downlink scheduling grants to the UE, for example, via an RRC configuration message. For example, the RRC configuration module 508 may configure DCI information to indicate whether the option to retransmit PUSCH repetitions on the configured resources can be activated.

[0087] The communication interface 509 is configured to coordinate with the RRC configuration module 508 to transmit a scheduling grant to the UE. The communication interface 509 is further configured to receive uplink data from the UE.

[0088] As shown, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices such as UE 115 and / or 400 and / or another core network element. The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS (e.g., LDPC coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (e.g., BWP frequency modulation configuration and instructions, PDCCH, PDSCH) from the modem subsystem 512 (for outbound transmissions) or the modulated / encoded data of a transmission from another source such as UE 115 and UE 400. The RF unit 514 may be further configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in the transceiver 510, the modem subsystem 512 and / or the RF unit 514 may be separate devices that are coupled together at the BS105 to enable the BS105 to communicate with other devices.

[0089] The RF unit 514 may provide the modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 516 for transmission to one or more other devices. This may include, for example, the transmission of information for completing attachment to the network and communication with the occupied UE 115 or 400 according to aspects of the present disclosure. The antenna 516 may further receive data messages transmitted from other devices and provide the received data messages for processing and / or demodulation at the transceiver 510. The transceiver 510 may provide the demodulated and decoded data (e.g., channel reports, PUSCH, PUCCH, HARQ ACK / NACK) to the RRC configuration module 508 and / or the communication interface 509 for processing. The antenna 516 may include multiple antennas of similar or different designs to maintain multiple transmission links.

[0090] In one aspect, the BS 500 may include multiple transceivers 510 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 500 may include a single transceiver 510 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 510 may include various components, and different combinations of the components may implement different RATs.

[0091] Figure 6 Illustrated is performed by a UE according to aspects of the present disclosure related to Figure 3BThe logic flow diagram corresponding to the PUSCH repetition adaptation scheme shown in. Method 600 describes the UE behavior of retransmitting a PUSCH repetition (e.g., 306b in ) on a configured resource (e.g., 308b in ) in response to discarding a PUSCH repetition due to a conflict with a downlink symbol. Figure 3B in. Figure 3B 306b in.

[0092] Each step of method 600 can be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or by other appropriate means for performing each step. For example, a wireless communication device (such as UE 115 or UE 400) can utilize one or more components (such as processor 402, memory 404, PUSCH repetition adaptation module 408, communication interface 409, transceiver 410, modem 412, and one or more antennas 416) to perform each step of method 600. Method 600 can be used in conjunction with the PUSCH repetition adaptation scheme described above with respect to. As illustrated, method 600 includes several enumerated steps, but aspects of method 600 include additional steps before, after, and between these enumerated steps. In some aspects, one or more of the enumerated steps can be omitted or performed in a different order. Figure 3B in.

[0093] In step 602, the UE can obtain data for uplink transmission on multiple repeated PUSCH instances. For example, the multiple repeated PUSCH instances can be a series of consecutive configured grant PUSCH instances 306a - n shown in. Figure 3B in.

[0094] In step 604, the UE can determine that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions. For example, the UE can obtain the time - frequency resources allocated for the transmission of the one or more downlink symbols from the slot format information and determine whether the time - frequency resources allocated for the downlink transmission overlap with any of the PUSCH repetitions 306a - n.

[0095] In step 606, the UE can discard the at least one repeated PUSCH instance (e.g., in response to determining that the at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions).

[0096] At step 608, the UE may use the configured grant to retransmit the data scheduled to be transmitted on the at least one repeated PUSCH instance (e.g., the discarded repeated PUSCH instance) on the configured resources configured for uplink transmission. For example, the uplink data initially carried by CG-PUSCH 306b may be retransmitted on the next available configured resource 308b. The timing of the retransmission will be described in conjunction with Figure 7 further described.

[0097] Figure 7 illustrates the transmission timeline of the interaction between the UE and the BS for implementing the Figure 6 PUSCH repetition adaptation scheme shown in. Diagram 700 depicts Figure 6 The method 600 in can be implemented by the interaction timeline between UE 115 and BS106.

[0098] For example, diagram 700 shows that BS105 may determine DCI, configured grants, etc. at 701 for allocating time resources to UE 115. For example, the DCI may include scheduling information for the PUSCH and an indication of the option to retransmit PUSCH repetitions on the configured resources. Such information may be transmitted from BS 105 to UE 115 via RRC signaling 702 via an RRC configuration message.

[0099] UE 115 may then identify from the received DCI one or more preconfigured grants that can be used to retransmit the PUSCH repetitions at 703. For example, the configured resources for every four time slots may be used for PUSCH repetition adaptation. If UE 115 detects at 704 that the PUSCH repetition conflicts with one or more downlink symbols from the SFI, UE 115 may discard the PUSCH repetition 706 at 704.

[0100] In this case, UE 115 may determine the retransmission time at 709 based on any combination of the timing of the discarded PUSCH repetition, the timing of the configured resources, and / or the preconfigured time offset. For example, UE 115 may grab the next available configured resource (e.g., Figure 3B 308b in ) after the conflicting PUSCH repetition (e.g., Figure 3B 306b in ) has been discarded. For another example, UE 115 may optionally want a preconfigured time offset 708 at the time when the conflicting PUSCH repetition is discarded or between the start times of the discarded PUSCH repetitions, and then look for the next available configured resource for retransmission.

[0101] In some embodiments, the determined retransmission time may be further subject to a time constraint. For example, UE 115 may determine whether a retransmission is valid depending on whether the retransmission time is within a limit to avoid significant waiting times. The limit may be determined based on the timing of the original PUSCH scheduling, the timing of the discarded PUSCH repetition, and / or preconfigured parameters. For example, the limit may be the end time of the original PUSCH plus a preconfigured parameter, e.g., requiring any retransmission to be completed within a specific waiting time after the original PUSCH scheduling. For another example, the limit may be the end time of the discarded PUSCH repetition plus a preconfigured parameter, e.g., requiring any retransmission to be completed within a specific waiting time after the discarded PUSCH repetition is discarded. In this way, the delay caused by adapting the PUSCH repetition via retransmission can be limited.

[0102] UE 115 may then perform an uplink retransmission on the determined preconfigured grant at 710 to compensate for the discarded PUSCH repetition. In some embodiments, the transmission may be performed using the transmission parameters configured for the discarded PUSCH repetition, which overwrite the transmission parameters of the preconfigured grant for the retransmission. In this way, BS105 may be able to combine the received uplink data transmitted on the preconfigured grant with the data transmitted on other PUSCH repetitions.

[0103] Figure 8 A logic flow diagram performed by a UE corresponding to an embodiment of determining configured resources for retransmission after discarding a PUSCH repetition in accordance with aspects of the present disclosure is illustrated. Method 800 describes UE behavior for determining a configured grant for retransmission in response to a discarded PUSCH repetition when multiple uplink configured grants are available.

[0104] The steps of method 800 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other suitable components) of a wireless communication device or other suitable means for performing the steps. For example, a wireless communication device (such as UE 115 or UE 400) may utilize one or more components (such as processor 402, memory 404, PUSCH repetition adaptation module 408, communication interface 409, transceiver 410, modem 412, and one or more antennas 416) to perform the steps of method 600. Method 800 may be used in conjunction with the PUSCH repetition adaptation scheme described above with respect to Figure 3B As shown, method 800 includes a plurality of enumerated steps, but aspects of method 800 include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0105] Method 800 may start fromFigure 6 It is carried out in step 604 in [reference]. At step 802, the UE may discard duplicate PUSCH instances and record the timing of the discarded PUSCH duplicates. For example, the UE may record the original start and end times of the discarded PUSCH duplicates, and / or the time at which the PUSCH duplicate was discarded.

[0106] At step 805, the UE may retrieve the next available uplink configured grant for retransmission, for example, after an optional preconfigured time offset. For example, the UE may optionally want an optional preconfigured time offset after the PUSCH duplicate is discarded, and then set the retransmission timeline after that optional preconfigured time offset.

[0107] In some embodiments, the UE may identify multiple configured grants (CG) ULs, and the UE may determine the configured grant to be used for retransmitting the discarded PUSCH based on the scheduling DCI and / or the timing of the discarded duplicates and / or some RRC configuration or a combination thereof. For example, at step 806, the UE may check whether a flag is included in the configuration of any available uplink configured grant, which may indicate that the corresponding uplink configured grant can be used for the transmission of the discarded PUSCH duplicate. If a flag is identified for the next available uplink configured grant, then at step 808, the UE may retransmit the PUSCH duplicate on that particular configured grant.

[0108] If the next available uplink configured grant does not contain such a flag, the UE may optionally look for more configured grants, for example, subsequent uplink configured grants, to see if the flag is indicated. For example, at step 810, if the UE determines that there are more configured grants available, method 800 may repeat at step 805. If no more configured grants are available, the UE may record the PUSCH duplicate loss at step 812.

[0109] In some embodiments, referring to step 810, the UE may further determine whether the next available configured grant complies with the retransmission limit as described above with respect to Figure 7 the description. The UE may only select to retransmit data on a preconfigured grant that starts before the retransmission limit to control the retransmission waiting time of the uplink data.

[0110] Information and signals may be represented using any of a variety of different arts and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0111] The various illustrative blocks and modules described in this disclosure can be implemented or performed with a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0112] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer readable medium as one or more instructions or code. Other examples and implementations fall within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the above functions can be implemented using software, hardware, firmware, hardwired, or any combination thereof executed by a processor. The features implementing the functions can also be physically located in various positions, including being distributed such that portions of the functions are implemented at different physical locations. Additionally, as used herein (including in the claims), the "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0113] As will be appreciated by one of ordinary skill in the art hereto and depending on the particular application at hand, many modifications, substitutions, and variations can be made to the materials, devices, configurations, and methods of use of the devices of the present disclosure without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the specific aspects described and illustrated herein (since they are only some examples of the present disclosure), but should be commensurate with the appended claims and their functional equivalents in their entirety.

Claims

1. A method for wireless communication, comprising: Obtaining, at a user equipment (UE), data for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances; Determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions; Discarding the at least one repeated PUSCH instance; And Retransmitting, using a configured grant, the data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission.

2. The method according to claim 1, wherein determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions comprises: Determining, according to slot format information, that a first time resource assigned to the at least one repeated PUSCH instance overlaps with a second time resource assigned to the one or more downlink symbol transmissions.

3. The method according to claim 1, further comprising: Determining a time instance for retransmitting the data on the configured resources based on any combination of the following: The time when the at least one repeated PUSCH instance is discarded; The time resources defined for the configured resources; and A preconfigured time offset.

4. The method according to claim 3, wherein determining a time instance for retransmitting the data on the configured resources further comprises: Identifying a next available configured resource after the preconfigured time offset has elapsed since the time when the at least one repeated PUSCH instance is discarded.

5. The method according to claim 3, further comprising: Determining whether the retransmission is valid depending on whether the determined time instance for retransmitting the data on the configured resources satisfies a time constraint, the time constraint being based on any combination of the following: Original PUSCH scheduling; The timing of the at least one repeated PUSCH instance that is discarded; and Preconfigured parameters.

6. The method according to claim 5, wherein the retransmission is valid when the determined time instance is not later than the PUSCH time of the original scheduling plus the preconfigured parameter or the timing of the at least one repeated PUSCH instance that is discarded plus the preconfigured parameter.

7. The method according to claim 1, wherein the data is retransmitted on the configured resources configured for uplink transmission using a configured grant with transmission parameters associated with the at least one repeated PUSCH instance, and the transmission parameters associated with the at least one repeated PUSCH instance overwrite the transmission parameters associated with the configured resources.

8. The method according to claim 1, further comprising: Receiving, via a radio resource control (RRC) configuration message, downlink control information (DCI) from a base station (BS), wherein the DCI indicates an option for retransmitting PUSCH repetitions on the configured resources.

9. The method according to claim 1, further comprising: In response to determining that more than one uplink configured grant can be used for retransmitting data scheduled to be transmitted on the at least one repeated PUSCH instance: Determine a configured grant for use in the retransmission from the more than one uplink configured grants based on any combination of the following: The scheduling DCI; The timing of the at least one repeated PUSCH instance that was discarded; and The RRC configuration.

10. The method according to claim 9, wherein the configured grant includes a flag indicating the availability of the retransmission of the discarded PUSCH repetition.

11. A user equipment (UE) for wireless communication, comprising: A memory configured to obtain data for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances; A processor configured to: Determine that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions, and Discard the at least one repeated PUSCH instance; and A transceiver configured to retransmit, using a configured grant, data scheduled to be transmitted on the at least one repeated PUSCH instance on configured resources configured for uplink transmission.

12. The UE according to claim 11, wherein the processor is further configured to determine that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions by: Determine that a first time resource assigned to the at least one repeated PUSCH instance overlaps with a second time resource assigned to the one or more downlink symbol transmissions according to the slot format information.

13. The UE according to claim 11, wherein the processor is further configured to: Determine a time instance for retransmitting the data on the configured resources based on any combination of the following: The time when the at least one repeated PUSCH instance was discarded; The time resources defined for the configured resources; and A preconfigured time offset.

14. The UE according to claim 13, wherein the processor is further configured to determine a time instance for retransmitting the data on the configured resources by: Identify the next available configured resource after the preconfigured time offset has elapsed since the time when the at least one repeated PUSCH instance was discarded.

15. The UE according to claim 13, wherein the processor is further configured to: Determine whether the retransmission is valid depending on whether the determined time instance for retransmitting the data on the configured resources satisfies a time constraint, the time constraint being based on any combination of the following: The original PUSCH scheduling; The timing of the at least one repeated PUSCH instance that was discarded; and Preconfigured parameters.

16. The UE according to claim 15, wherein the retransmission is valid when the determined time instance is not later than the PUSCH time of the original scheduling plus the preconfigured parameter or the timing of the at least one repeated PUSCH instance that was discarded plus the preconfigured parameter.

17. The UE according to claim 11, wherein the data is retransmitted on the configured resources configured for uplink transmission using transmission parameters associated with the at least one repeated PUSCH instance, and the transmission parameters associated with the at least one repeated PUSCH instance overwrite the transmission parameters associated with the configured resources.

18. The UE according to claim 11, wherein the transceiver is further configured to: receive downlink control information (DCI) from a base station (BS) via a radio resource control (RRC) configuration message, wherein the DCI indicates an option to retransmit PUSCH repetitions on the configured resources.

19. The UE according to claim 11, wherein the processor is further configured to: in response to determining that more than one uplink configured grant can be used to retransmit data scheduled to be transmitted on the at least one repeated PUSCH instance: determine a configured grant for the retransmission from the more than one uplink configured grants based on any combination of: scheduling DCI; the timing of the at least one repeated PUSCH instance that was discarded; and RRC configuration.

20. The UE according to claim 19, wherein the configured grant includes a flag indicating the availability of retransmitting discarded PUSCH repetitions.

21. A non-transitory processor-readable storage medium storing processor-executable instructions for wireless communication, the processor-executable instructions being executable by a processor to perform operations, the operations including: obtaining, at a user equipment (UE), data for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances; determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions; discarding the at least one repeated PUSCH instance; and retransmitting, using a configured grant, the data scheduled to be transmitted on the at least one repeated PUSCH instance on the configured resources configured for uplink transmission.

22. The non-transitory processor-readable storage medium according to claim 21, wherein the operation of determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions further includes: determining that a first time resource assigned to the at least one repeated PUSCH instance overlaps with a second time resource assigned to the one or more downlink symbol transmissions according to slot format information.

23. The non-transitory processor-readable storage medium according to claim 21, wherein the operations further include: determining a time instance for retransmitting the data on the configured resources based on any combination of: the time when the at least one repeated PUSCH instance was discarded; the time resources defined for the configured resources; and a preconfigured time offset.

24. The non-transitory processor-readable storage medium according to claim 23, wherein the operation of determining a time instance for retransmitting the data on the configured resources further includes: Identify the next available configured resource after the preconfigured time offset has elapsed since the time when the at least one repeated PUSCH instance was discarded.

25. The non-transitory processor-readable storage medium of claim 23, wherein the operation further comprises: Determining whether the retransmission is valid depending on whether a determined time instance for retransmitting the data on the configured resource satisfies a time constraint, the time constraint being based on any combination of: Original PUSCH scheduling; The timing of the at least one repeated PUSCH instance that was discarded; and Preconfigured parameters.

26. The non-transitory processor-readable storage medium of claim 25, wherein the retransmission is valid when the determined time instance is no later than the PUSCH time of the original scheduling plus the preconfigured parameter or the timing of the at least one repeated PUSCH instance that was discarded plus the preconfigured parameter.

27. The non-transitory processor-readable storage medium of claim 21, wherein the data is retransmitted on the configured resource configured for uplink transmission using configured grants with transmission parameters associated with the at least one repeated PUSCH instance, and the transmission parameters associated with the at least one repeated PUSCH instance overwrite the transmission parameters associated with the configured resource.

28. The non-transitory processor-readable storage medium of claim 21, wherein the operation further comprises: Receiving downlink control information (DCI) from a base station (BS) via a radio resource control (RRC) configuration message, wherein the DCI indicates an option to retransmit PUSCH repetitions on the configured resource.

29. The non-transitory processor-readable storage medium of claim 21, wherein the operation further comprises: In response to determining that more than one uplink configured grant can be used to retransmit data scheduled to be transmitted on the at least one repeated PUSCH instance: Determining a configured grant from the more than one uplink configured grants for the retransmission based on any combination of: Scheduling DCI; The timing of the at least one repeated PUSCH instance that was discarded; and RRC configuration.

30. The non-transitory processor-readable storage medium of claim 29, wherein the configured grant includes a flag indicating the availability of retransmitting discarded PUSCH repetitions.

31. A wireless communication system, comprising: Means for obtaining data at a user equipment (UE) for uplink transmission on a plurality of repeated physical uplink shared channel (PUSCH) instances; Means for determining that at least one repeated PUSCH instance conflicts with one or more downlink symbol transmissions; Means for discarding the at least one repeated PUSCH instance; And Means for retransmitting data scheduled to be transmitted on the at least one repeated PUSCH instance on a configured resource configured for uplink transmission using a configured grant.

32. The system according to claim 31, wherein the means for determining a conflict between at least one repeated PUSCH instance and one or more downlink symbol transmissions comprises: means for determining, based on slot format information, that a first time resource assigned to the at least one repeated PUSCH instance overlaps with a second time resource assigned to the one or more downlink symbol transmissions.

33. The system according to claim 31, further comprising: means for determining a time instance for retransmitting the data on the configured resource based on any combination of: the time at which the at least one repeated PUSCH instance is discarded; the time resources defined for the configured resource; and a preconfigured time offset.

34. The system according to claim 33, wherein the means for determining a time instance for retransmitting the data on the configured resource further comprises: means for identifying the next available configured resource after the preconfigured time offset has elapsed since the time at which the at least one repeated PUSCH instance was discarded.

35. The system according to claim 33, further comprising: means for determining whether the retransmission is valid depending on whether the determined time instance for retransmitting the data on the configured resource satisfies a time constraint, the time constraint being based on any combination of: the original PUSCH scheduling; the timing of the at least one repeated PUSCH instance that was discarded; and preconfigured parameters.

36. The system according to claim 35, wherein the retransmission is valid when the determined time instance is no later than the PUSCH time of the original scheduling plus the preconfigured parameter or the timing of the at least one repeated PUSCH instance that was discarded plus the preconfigured parameter.

37. The system according to claim 31, wherein the data is retransmitted on the configured resource configured for uplink transmission using a configured grant with transmission parameters associated with the at least one repeated PUSCH instance, and the transmission parameters associated with the at least one repeated PUSCH instance overwrite the transmission parameters associated with the configured resource.

38. The system according to claim 31, further comprising: means for receiving downlink control information (DCI) from a base station (BS) via a radio resource control (RRC) configuration message, wherein the DCI indicates an option to retransmit a PUSCH repetition on the configured resource.

39. The system according to claim 31, further comprising: means for determining, in response to determining that more than one uplink configured grant can be used to retransmit data scheduled to be transmitted on the at least one repeated PUSCH instance, a configured grant for use in the retransmission from the more than one uplink configured grants based on any combination of: scheduling DCI; the timing of the at least one repeated PUSCH instance that was discarded; and RRC configuration.

40. The system according to claim 39, wherein the configured grant includes a flag indicating the availability of a repetition of a retransmission-discarded PUSCH.

Images