Early termination of PUSCH transmission

Abstract

An aspect is provided that enables a UE to perform early termination of an ongoing repetition of a PUSCH transmission in response to a DCI from a base station indicating whether a previous PUSCH transmission or repetition was successfully decoded. The UE obtains information configuring an UL data transmission and a repetition of the UL data transmission. The UE sends the UL data transmission to the base station. The UE terminates the repetition of the UL data transmission in response to receiving DL information in a DL control channel. Thus, UE power reduction and improved resource efficiency can be achieved. Furthermore, the repetition ends after a time gap following a CORESET in which the DL control channel is received. As a result, the start time for terminating a PUSCH repetition can be configured to accommodate various timing considerations, such as dynamic TDD, different numerologies between PDCCH and PUSCH, and multiple PUSCH processing capabilities.

Description

Technical Field

[0001] This patent application claims priority to U.S. Patent Application No. 17 / 165,860, entitled "EARLY TERMINATION OF PUSCH TRANSMISSION," filed on February 2, 2021, which has been assigned to the assignee of this application and is hereby incorporated by reference in its entirety for all purposes.

[0002] The present disclosure generally relates to communication systems, and more particularly, to wireless communication between a user equipment (UE) and a base station.

Background Art

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. A typical wireless communication system may employ a multiple access technology that is capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multi-connectivity technologies are adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the urban, national, regional, and even global scales. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution published by the 3rd Generation Partnership Project (3GPP™) to meet new requirements related to latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low-latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long-Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology. These improvements may also be applicable to other multi-connectivity technologies and the telecommunications standards that utilize these technologies.

SUMMARY OF THE INVENTION

MEANS FOR SOLVING THE PROBLEM

[0005] The following presents a simplified summary of such aspects in order to provide a basic understanding of one or more aspects. This summary is not an extensive overview of all contemplated aspects, nor does it identify the main or critical elements of all aspects, nor does it delimit the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that follows.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus can be a UE. The UE obtains information that constitutes uplink data transmission and the repetition of uplink data transmission. The UE sends the uplink data transmission to a base station and terminates the repetition of the uplink data transmission in response to receiving downlink information on a downlink control channel. The repetition ends after a time gap following a control resource set (CORESET) on which the downlink control channel is received.

[0007] To achieve the above object and related objects, one or more aspects include features that are fully described below and particularly pointed out in the claims. The following description and the accompanying drawings detail some exemplary features of one or more aspects. However, these features represent only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2A

Figure 2B

Figure 2C

Figure 2D

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15A

Figure 15B

Figure 15C

[0009] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the 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 in order to avoid obscuring such concepts.

[0010] When the base station configures the UE to transmit uplink data on the Physical Uplink Shared Channel (PUSCH), it may send repetitions of that uplink data for coverage enhancement and instruct the UE to improve the reliability of the data. Typically, the UE may be configured to send up to 16 repetitions of PUSCH transmissions in response to dynamic grants, or up to 8 repetitions in response to configured grants. However, for example, to further expand PUSCH coverage for extended mobile broadband (eMBB) / Voice over Internet Protocol (VoIP), to support low-capability UEs with extended coverage, or in other cases, the number of repetitions may be increased beyond 16. Thus, the UE may send multiple repetitions of its uplink data so that the base station can successfully decode the uplink data.

[0011] In some cases, the base station may be able to successfully decode the uplink data after receiving all the configured repetitions (e.g., when the UE is located relatively far from the base station such as at the cell edge), and in other cases, the base station may be able to successfully decode the data after receiving only some of the configured repetitions. For example, even if the base station configures the UE to send 8 PUSCH repetitions, if the UE is not at the cell edge or is otherwise in a geometry with high signal quality, the base station may be able to successfully decode the data after receiving only 4 PUSCH repetitions (or some other number less than 8).

[0012] Furthermore, asynchronous hybrid automatic repeat request (HARQ) positive acknowledgments (ACKs) are supported in NR in response to downlink transmissions (e.g., HARQ-ACK from the UE to the base station), but the base station conventionally does not provide HARQ-ACK feedback in response to PUSCH transmissions (e.g., HARQ-ACK from the base station to the UE). Instead, depending on whether the base station successfully decoded the uplink data or not, the base station may provide the UE with downlink control information (DCI) indicating whether the UE should retransmit the uplink data in a subsequent PUSCH transmission. In particular, if the base station fails to decode the uplink data, the base station can provide the UE with DCI instructing the UE to retransmit the uplink data, while if the base station successfully decodes the uplink data, the base station does not provide such DCI, and the UE assumes that the data was successfully received after determining that the base station has not provided such DCI within a certain time period.

[0013] Accordingly, even if the base station has already decoded the uplink data in a previous PUSCH transmission or iteration, the UE may not determine that the base station has successfully decoded the data until the time period for receiving the DCI has elapsed, and thus the UE may continue to send unnecessary PUSCH iterations in the meantime. As a result, the UE may waste transmission power and PUSCH resources with inefficient iterations. Therefore, it is useful to enable the UE to perform early termination of an ongoing PUSCH transmission (e.g., terminate inefficient iterations) in order to save UE power and improve resource efficiency.

[0014] Therefore, a manner for terminating the repetition of PUSCH transmission is provided. In a first example, the base station may provide, on the PDCCH, a DCI that explicitly indicates the success of decoding of the PUSCH transmission. The indication may be provided using configured bit values for various parameters of the DCI. For example, the DCI may have DCI format 0-0 or 0-1 in which the frequency domain resource allocation (FDRA) field or the MCS field is set to all 1s, and all remaining bits in one or more other parameters of the DCI (such as time domain resource allocation (TDRA), frequency hopping flag, etc.) are set to 0s. The UE receives the PDCCH carrying the DCI in a control resource set (CORESET), and the DCI may instruct the UE to terminate subsequent repetitions of the PUSCH transmission after a time gap following the CORESET (for example, up to T symbols after the last symbol of the CORESET). In a second example, the base station may provide, on the PDCCH, a DCI that implicitly indicates the success of decoding of the first PUSCH transmission. For example, the base station may provide the DCI to a UE that schedules a second PUSCH transmission within time resources overlapping with the first PUSCH transmission. The UE receives the PDCCH carrying the DCI in a CORESET, and the DCI may instruct the UE to terminate subsequent repetitions of the first PUSCH transmission after a time gap following the CORESET (for example, up to T symbols after the last symbol of the CORESET). The DCI may also instruct the UE to transmit the second PUSCH transmission in an uplink slot after the time gap following the CORESET. In either the first example or the second example, the time gap (for example, the value of T) may be a function of the PDCCH subcarrier spacing (SCS) and the PUSCH SCS, the PUSCH processing capability, whether the first symbol of the PUSCH resource allocation is reserved for the demodulation reference signal (DMRS), and the PUSCH preparation time. In addition, the time gap (T) may include an additional number of symbols Δ for the UE processing margin (for example, T = T + Δ), and its duration may be a function of the PDCCH SCS and the PUSCH SCS.For example, the duration of the additional symbol count Δ may be a function of the smaller SCS between the PDCCH SCS and the PUSCH SCS.

[0015] Some aspects of a telecommunication system are presented herein with respect to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or as software depends on the particular application and design constraints imposed on the overall system.

[0016] As an example, an element or any part of an element or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, individual hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more of the processors in the processing system may execute software. Software is to be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., regardless of whether it is called software, firmware, middleware, microcode, hardware description language, or otherwise.

[0017] Thus, in one or more exemplary embodiments, the functions described may be implemented in hardware, software, or any combination thereof. When implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. The computer-readable medium includes computer storage media. The storage media may be any available media that can be accessed by a computer. By way of example and not limitation, such computer-readable media can comprise random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other media that can be used to store computer-executable code in the form of instructions or data structures accessible by a computer.

[0018] FIG. 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). A macrocell includes a base station. Small cells include femtocells, picocells, and microcells.

[0019] The base station 102 configured for 4G Long-Term Evolution (LTE) (collectively referred to as the evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN)) can interface with the EPC 160 through a first backhaul link 132 (e.g., the S1 interface). The base station 102 configured for 5G New Radio (NR) (collectively referred to as the next-generation RAN (NG-RAN)) can interface with the core network 190 through a second backhaul link 184. In addition to other functions, the base station 102 may perform one or more of the following functions, namely, transfer of user data, encryption and decryption of radio channels, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, setup and release of connections, load distribution, delivery for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), tracking of subscribers and devices, radio access network information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 can communicate directly or indirectly with each other (e.g., through the EPC 160 or the core network 190) via a third backhaul link 134 (e.g., the X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 may be wired or wireless.

[0020] The base station 102 may communicate wirelessly with the UE 104. Each of the base stations 102 may provide communication coverage to its respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may sometimes be referred to as a heterogeneous network. The heterogeneous network may also include a home evolved Node B (HeNB) that can provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link 120 between the base station 102 and the UE 104 may include uplink (UL) (also called reverse link) transmission from the UE 104 to the base station 102 and / or downlink (DL) (also called forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technology including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use a spectrum of bandwidth up to Yx megahertz (MHz) (x component carriers) per carrier in carrier aggregation allocated up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) for transmission in each direction. The carriers may or may not be adjacent to each other. The carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may sometimes be called a Primary Cell (PCell), and the secondary component carrier may sometimes be called a Secondary Cell (SCell).

[0021] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use the DL / UL WWAN spectrum. The D2D communication links 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR, for example.

[0022] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152, for example, in the 5 gigahertz (GHz) unlicensed frequency spectrum via a communication link 154. When communicating in the unlicensed frequency spectrum, the STA 152 / AP 150 may perform a Clear Channel Assessment (CCA) before communicating to determine whether the channel is available.

[0023] The small cell 102' may operate in the licensed and / or unlicensed frequency spectrum. When operating in the unlicensed frequency spectrum, the small cell 102' may utilize NR and may use the same unlicensed frequency spectrum (e.g., 5 GHz, etc.) as used by the Wi-Fi AP 150. The small cell 102' utilizing NR in the unlicensed frequency spectrum may enhance the coverage to the access network and / or increase the capacity of the access network.

[0024] The electromagnetic spectrum is often re-divided into various classes, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands are specified as the frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. A part of FR1 is higher than 6 GHz, but FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and papers. Similar nomenclature issues may arise regarding FR2, but this is often (interchangeably) referred to as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified by the International Telecommunication Union (ITU) as the "millimeter wave" band.

[0025] With the above aspects in mind, unless otherwise specified, it should be understood that terms such as "sub-6 GHz", when used in this specification, may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specified, it should be understood that terms such as "millimeter wave", when used in this specification, may broadly represent frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0026] The base station 102 may include, and / or be referred to as, an eNB, a gNodeB (gNB), or another type of base station, whether it is a small cell 102' or a large cell (e.g., a macro base station). Some base stations, such as gNB 180, may communicate with the UE 104 and operate in the conventional sub-6 GHz spectrum, at millimeter wave frequencies, and / or at near millimeter wave frequencies. When the gNB 180 operates in millimeter wave frequencies or near millimeter wave frequencies, the gNB 180 may be referred to as a millimeter wave base station. The millimeter wave base station 180 may use beamforming 182 with the UE 104 to compensate for path loss and short distances. The base station 180 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0027] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmission directions 182'. The UE 104 may receive a beamformed signal from the base station 180 in one or more reception directions 182''. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmission directions. The base station 180 may receive a beamformed signal from the UE 104 in one or more reception directions. The base station 180 / UE 104 may perform beam training to determine the best reception and transmission directions for each of the base station 180 / UE 104. The transmission and reception directions for the base station 180 may or may not be the same. The transmission and reception directions for the UE 104 may or may not be the same.

[0028] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, an MBMS Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may communicate with a Home Subscriber Server (HSS) 174. The MME 162 is a control node that processes signaling between the UE 104 and the EPC 160. Generally, the MME 162 performs bearer and connection management. All user Internet Protocol (IP) packets are transferred through the Serving Gateway 166, and the Serving Gateway 166 itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to an IP service 176. The IP service 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 can provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may act as an entry point for content provider MBMS transmissions, may be used to permit and activate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to deliver MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related charging information.

[0029] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with an integrated data management (UDM) 196. The AMF 192 is a control node that processes signaling between the UE 104 and the core network 190. Generally, the AMF 192 provides service quality (QoS) flow and session management. All user IP packets are forwarded through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, IMS, a packet switched (PS) streaming service, and / or other IP services.

[0030] The base station may include a gNB, Node B, eNB, access point, transceiver base station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmission and reception point (TRP), or some other suitable term, and / or may be referred to as such. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of the UE 104 include a cellular phone, smartphone, session initiation protocol (SIP) phone, laptop, personal digital assistant (PDA), satellite radio, global positioning system, multimedia device, video device, digital audio player (e.g., MP3 player), camera, game console, tablet, smart device, wearable device, vehicle, electric meter, gas pump, large or small cooking appliance, health management device, implant, sensor / actuator, display, or any other similar functional device. Some of the UE 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicle, heart monitor, etc.). The UE 104 may also be called a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0031] Although the present disclosure may focus on 5G NR, the concepts and various aspects described herein may be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A), code division multiple access (CDMA), Global System for Mobile communications (GSM), or other wireless / wireless access technologies.

[0032] Referring back to FIG. 1, in some aspects, the UE 104 may include a physical uplink shared channel (PUSCH) termination component 198 configured to obtain information that constitutes uplink data transmission and repetitions of the uplink data transmission, send the uplink data transmission to the base station, and terminate the repetitions of the uplink data transmission in response to receiving downlink information on the downlink control channel, where the repetitions terminate after a time gap following the CORESET in which the downlink control channel is received.

[0033] FIG. 2A is a diagram 200 showing an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 showing an example of a DL channel within a 5G NR subframe. FIG. 2C is a diagram 250 showing an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 showing an example of a UL channel within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexing (FDD) in which subframes within a set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL for a particular set of subcarriers, or may be time division duplexing (TDD) in which subframes within a set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. In the examples provided by FIGS. 2A and 2C, the 5G / NR frame structure is assumed to be TDD, and subframe 4 is configured using slot format 28 (which mostly has DL), where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 is configured using slot format 34 (which mostly has UL). Subframes 3 and 4 are shown using slot formats 34 and 28 respectively, but any particular subframe may be configured using any of the various available slot formats 0 - 61. Slot formats 0 and 1 are all DL and UL respectively. The other slot formats 2 - 61 include a mixture of DL, UL, and flexible symbols. The UE is configured using the slot format (dynamically through DL control information (DCI) or semi-statically / statically through radio resource control (RRC) signaling) through the received slot format indicator (SFI). Note that the following description also applies to a 5G NR frame structure that is TDD.

[0034] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10 millisecond (ms) frame can be divided into 10 sub-frames (1 ms) of equal size. Each sub-frame may include one or more time slots. The sub-frame may also include mini-slots that can include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols depending on the slot configuration. In the case of slot configuration 0, each slot may include 14 symbols, and in the case of slot configuration 1, each slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also called single carrier frequency division multiple access (SC-FDMA) symbols) (for power limited scenarios and limited to single stream transmission). The number of slots in a sub-frame is based on the slot configuration and numerology. In slot configuration 0, different numerologies μ0 to 4 allow 1, 2, 4, 8, and 16 slots per sub-frame respectively. In slot configuration 1, different numerologies 0 to 2 allow 2, 4, and 8 slots per sub-frame respectively. Thus, for slot configuration 0 and numerology μ, there are 14 symbols / slot and 2 μ slots / sub-frame. The sub-carrier spacing and symbol length / duration are functions of the numerology. The sub-carrier spacing is 2 μ*It may be equal to 15 kilohertz (kHz), provided that μ is numerology 0 to 4. Thus, numerology μ = 0 has a subcarrier spacing of 15 kHz, and numerology μ = 4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. FIGS. 2A to 2D give an example of slot configuration 0 with 14 symbols per slot and numerology μ = 2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a specific numerology.

[0035] A resource grid may be used to represent the frame structure. Each time slot contains resource blocks (RBs) (also called physical RBs (PRBs)) spanning 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0036] As shown in FIG. 2A, some of the REs carry reference (pilot) signals (RSs) for the UE. The RSs may include demodulation RSs (DM-RSs) (where 100x is the port number and is shown as such for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). The RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs). x as shown, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RSs). The RSs may also include beam measurement RSs (BRSs), beam refinement RSs (BRRSs), and phase tracking RSs (PT-RSs).

[0037] Figure 2B shows an example of various DL channels within a subframe of a frame. The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), where each CCE contains nine Resource Element Groups (REGs), and each REG contains four consecutive Resource Elements (REs) within an OFDM symbol. The PDCCH within one Bandwidth Part (BWP) can be referred to as a Control Resource Set (CORESET). Additional BWPs may be at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) may be in symbol 2 of a specific subframe of a frame. The PSS is used by UE104 to determine subframe / symbol timing and physical layer identification information. The Secondary Synchronization Signal (SSS) may be in symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification information group number and radio frame timing. Based on the physical layer identification information and the physical layer cell identification information group number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the above-mentioned DM-RS. The Physical Broadcast Channel (PBCH) that carries the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH Block (also called an SS Block (SSB)). The MIB provides the number of Resource Blocks (RBs) within the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as System Information Blocks (SIBs), and paging messages.

[0038] As shown in FIG. 2C, some of the REs carry DM-RS for channel estimation at the base station (shown as R for one particular configuration, although other DM-RS configurations are possible). The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS may be transmitted within the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether a short PUCCH or a long PUCCH is transmitted and on the particular PUCCH format used. The UE may transmit a sounding reference signal (SRS). The SRS may be transmitted in the last symbol of the subframe. The SRS may have a comb structure and the UE may transmit the SRS on one of the combs. The SRS may be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0039] FIG. 2D shows an example of the various UL channels within a subframe of a frame. The PUCCH may be positioned as shown in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) / negative acknowledgement (NACK) feedback. The PUSCH carries data and may also be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0040] FIG. 3 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 can be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer. The controller / processor 375 is related to RRC layer functionality for system information (e.g., MIB, SIB) broadcasting, RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), mobility between radio access technologies (RATs), and measurement configuration for UE measurement reports, PDCP layer functionality related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions, RLC layer functionality related to transfer of upper layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs, and MAC layer functionality related to mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0041] The transmitting (TX) processor 316 and the receiving (RX) processor 370 perform layer 1 functions related to various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping onto the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes mapping to signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream is then mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate a plurality of spatial streams. Channel estimates from the channel estimator 374 may be used to determine the coding and modulation scheme and for spatial processing. The channel estimates may be derived from reference signals transmitted by the UE 350 and / or channel state feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier using its respective spatial stream for transmission.

[0042] In UE350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX recovers the information modulated on the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions related to various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams directed to UE350. Multiple spatial streams, if addressed to UE350, may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal comprises separate OFDM symbol streams for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on the channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359 that implements layer 3 and layer 2 functions.

[0043] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 performs demultiplexing, packet reassembly, decoding, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the EPC160. The controller / processor 359 is also involved in error detection using the ACK and / or NACK protocols to support HARQ operations.

[0044] Similar to the functions described for DL transmission by the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) collection, RRC connection, and measurement reporting, PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification), RLC layer functions associated with transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs, and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, reporting of scheduling information, error correction through HARQ, prioritization, and logical channel prioritization.

[0045] Channel estimates derived by the channel estimator 358 from reference signals or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with its respective spatial stream for transmission.

[0046] UL transmission is processed at the base station 310 in a manner similar to that described for the receiver function in the UE 350. Each receiver 318RX receives signals through its respective antenna 320. Each receiver 318RX recovers the information modulated on the RF carrier and provides that information to the RX processor 370.

[0047] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 performs demultiplexing, packet reassembly, decoding, header decompression, and control signal processing between the transport channel and the logical channel to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also involved in error detection using the ACK and / or NACK protocols to support HARQ operations.

[0048] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects associated with the PUSCH end component 198 of FIG. 1.

[0049] When the base station configures the UE to transmit uplink data in PUSCH, it may send repetitions of the uplink data for coverage enhancement and instruct the UE to improve the reliability of the data. For example, the base station may send a PUSCH configuration (e.g., pusch-Config or another name) indicating the number of repetitions of the uplink data that the UE can transmit on the PUSCH in response to a dynamic grant (e.g., the parameter pusch-AggregationFactor or another name) to the UE via dedicated RRC signaling. In another example, the base station may send a configured grant configuration (e.g., configuredGrantConfig or another name) indicating the number of repetitions of the uplink data that the UE can transmit on the PUSCH in response to a configured grant (e.g., the parameter repK or another name) to the UE. Typically, the UE may be configured to send up to 16 repetitions of PUSCH transmissions in response to a dynamic grant, or up to 8 repetitions in response to a configured grant. However, the number of repetitions can be increased beyond 16, for example, to further extend the PUSCH coverage for enhanced mobile broadband (eMBB) / voice over Internet protocol (VoIP), to support low-capability UEs in extended coverage, or in other cases. For example, in rural or some urban areas, the downlink channel usually includes a higher signal quality (e.g., about 6 - 12 dB) than the uplink channel, and thus, the repetitions of the PUSCH can serve to compensate for this degradation in signal quality.

[0050] Therefore, the UE may send multiple repetitions of its uplink data so that the base station can correctly decode the uplink data. In some cases, the base station may correctly decode the uplink data after receiving all the configured repetitions (for example, when the UE is located relatively far from the base station such as at the cell edge), and in other cases, the base station may correctly decode the data only after receiving some of the configured repetitions. For example, even if the base station configures the UE to transmit 8 PUSCH repetitions, if the UE is not at the cell edge or is otherwise in a geometry with high signal quality, the base station may correctly decode the data after receiving only 4 PUSCH repetitions (or some other number less than 8).

[0051] However, asynchronous hybrid automatic repeat request (HARQ) positive acknowledgments (ACKs) are supported in NR in response to downlink transmissions (e.g., HARQ-ACK from the UE to the base station), but the base station conventionally does not provide HARQ-ACK feedback in response to PUSCH transmissions (e.g., HARQ-ACK from the base station to the UE). Instead, depending on whether the base station successfully decodes the uplink data or fails to decode it, the base station may provide the UE with downlink control information (DCI) indicating whether the UE should retransmit the uplink data in a subsequent PUSCH transmission. For example, if the base station fails to decode the uplink data, the base station can provide the UE with DCI instructing the UE to retransmit the uplink data, while if the base station successfully decodes the uplink data, the base station does not provide such DCI, and the UE assumes that the data was successfully received after determining that the base station has not provided such DCI within a certain time period. Thus, even if the base station has already decoded the uplink data in a previous PUSCH transmission or iteration, the UE may not determine that the base station has successfully decoded the data until the time period for receiving the DCI has elapsed, and thus the UE may continue to send unnecessary PUSCH iterations in the meantime. As a result, the UE may waste transmission power and PUSCH resources with inefficient iterations. Therefore, to save UE power and improve resource efficiency, it is useful to enable the UE to perform an early termination of an ongoing PUSCH transmission (e.g., terminate inefficient iterations).

[0052] In Long-Term Evolution (LTE) Extended Machine-Type Communication (eMTC), a User Equipment (UE) may terminate an ongoing uplink transmission in full-duplex (FD) frequency-division duplexing (FD-FDD) and time-division duplexing (TDD) deployments in response to Downlink Control Information (DCI) from a base station. For example, the base station may provide DCI to the UE on the Machine-Type Communication Physical Downlink Control Channel (MPDCCH), and the DCI may explicitly or implicitly indicate that the base station has successfully decoded the previous uplink transmission. The UE may then terminate the ongoing Physical Uplink Shared Channel (PUSCH) transmission in response to the DCI.

[0053] The indication may be explicit when the DCI includes one of two DCI formats that contain a certain configuration of bit values in the specified DCI parameters (acting as a valid Hybrid Automatic Repeat reQuest - Acknowledgement (HARQ-ACK)). For example, to explicitly approve that the base station has successfully decoded an uplink transmission from the UE, the base station may provide the UE with DCI having DCI format 6-0A, where the resource block allocation field is set to all 1s and all remaining bits are set to 0s (excluding the flag format 6-0A / format 6-1A distinction and the DCI subframe repetition count). Alternatively, the base station may provide the UE with DCI having DCI format 6-0B, where the modulation and coding scheme (MCS) field is set to all 1s and all remaining bits are set to 0s (excluding the flag format 6-0B / format 6-1B distinction and the DCI subframe repetition count). On the other hand, the indication may be implicit when the base station schedules a new PUSCH transport block that temporally overlaps with a previously scheduled PUSCH transmission or repetition. For example, to implicitly approve that the base station has successfully decoded an uplink transmission from the UE, the base station may provide DCI to the UE that schedules a new PUSCH transport block with overlapping time resources.

[0054] When the UE receives, in subframe N, a DCI in an MPDCCH that explicitly indicates that the base station has successfully decoded a previous uplink transmission using DCI format 6-0A or 6-0B, if k is the number of subframes, the UE may terminate or stop transmitting data on the PUSCH by subframe N + k. For example, in an FDD deployment, k may be 4 subframes, and in a TDD deployment, k may be a function of the subframe number (or slot number) and the TDD uplink / downlink configuration (e.g., k = 4, 5, 6, or 7). The UE may terminate PUSCH transmission earlier than subframe N + k in response to early decoding of the DCI in the MPDCCH. Similarly, when the UE receives, in subframe M, a DCI in an MPDCCH that implicitly indicates that the base station has successfully decoded a previous uplink transmission by scheduling a new PUSCH transmission in overlapping resources, the UE may terminate or stop transmitting data on the PUSCH by subframe M + k. The UE may terminate PUSCH transmission earlier than subframe M + k, for example, in response to early decoding of the DCI in the MPDCCH. In addition, the UE may transmit a new PUSCH transmission in response to a DCI starting in subframe M + k.

[0055] FIG. 4 shows an example 400 in which a UE terminates PUSCH transmission 402 in response to DCI that explicitly indicates successful decoding of the PUSCH transmission. The base station first provides DCI 404 in the MPDCCH to the UE that schedules the PUSCH transmission, and in response, the UE begins transmitting its uplink data to the base station in PUSCH transmission 402. While the UE is transmitting its uplink data in one or more repetitions, the base station can successfully decode the PUSCH transmission. Further, the base station can determine that the UE has no additional data to send in its transmission buffer, for example, in response to a buffer status report from the UE or by some other means. Thus, the base station can provide the UE with DCI 406 that explicitly indicates that the PUSCH transmission has been successfully decoded. For example, DCI 406 can have DCI format 6-0A or 6-0B with configured bit values as described above that do not schedule a new PUSCH transmission. The UE can then terminate its PUSCH transmission in response to DCI 406. For example, assuming the UE receives DCI 406 in subframe N, the UE can terminate the PUSCH transmission by subframe N+k. For example, the UE can stop transmitting the repetition of its uplink data starting at subframe N+k, as represented by the terminated PUSCH transmission 408.

[0056] Similarly, FIG. 5 shows an example 500 in which the UE terminates a first PUSCH transmission 502 in response to DCI that schedules a second PUSCH transmission 504 and implicitly indicates successful decoding of the first PUSCH transmission. The base station first provides DCI 506 in the MPDCCH to the UE that schedules the first PUSCH transmission, and in response, the UE begins transmitting its uplink data to the base station in the first PUSCH transmission 502. While the UE is transmitting its uplink data in one or more repetitions, the base station can successfully decode the first PUSCH transmission. Further, the base station can determine, for example, in response to a buffer status report from the UE or some other means, that the UE has additional data to send in its transmission buffer. Accordingly, the base station can provide the UE with DCI 508 that implicitly indicates that the first PUSCH transmission has been successfully decoded. For example, DCI 508 can schedule the second PUSCH transmission 504 in time resources that overlap with the first PUSCH transmission 502. The UE then terminates its first PUSCH transmission in response to DCI 508 and can transmit its second PUSCH transmission. For example, assuming the UE receives DCI 508 in subframe M, the UE can terminate the first PUSCH transmission by subframe M + k and begin transmitting the second PUSCH transmission that starts in subframe M + k. For example, the UE can stop transmitting the repetition of its first uplink data that starts in subframe M + k and begin transmitting its second uplink data that starts in subframe M + k, as represented by the terminated PUSCH transmission 510.

[0057] However, although LTE eMTC may support early termination of PUSCH transmissions based on explicit or implicit feedback as described above, the timeline associated with such terminated PUSCH transmissions (subframes N + k and M + k) may not be sustainable in NR. For example, NR supports a dynamic TDD configuration where the base station can dynamically change the symbol or slot format (e.g., the arrangement of downlink (DL) symbols and uplink (UL) symbols or slots within a subframe), in contrast to the static TDD configurations supported in LTE (e.g., the seven TDD UL / DL configurations 0 - 6). Thus, an attempt to terminate a PUSCH transmission after k subframes upon receiving DCI may fail due to a conflict with the dynamic UL / DL configuration. Further, NR supports different numerologies between the PDCCH and the PUSCH compared to LTE (e.g., the PDCCH and the PUSCH may include different subcarrier spacings (SCS)), and thus different symbol durations between the PDCCH and the PUSCH. Therefore, if the DCI and the terminated PUSCH transmission are associated with different SCS or symbol durations, the dynamic value of k based on the slot number or the TDD UL / DL configuration in a TDD deployment, and the fixed value of k in an FDD deployment, may not be appropriate. Additionally, NR supports multiple PUSCH processing capabilities of the UE compared to LTE. For example, after receiving a PDCCH transmission, a UE with PUSCH processing capability 2 may be able to start a PUSCH transmission in approximately half the amount of time compared to a UE with PUSCH processing capability 1 (e.g., assuming a 15 kHz SCS, 5 symbols after receiving DCI for capability 2 as opposed to 10 symbols after receiving DCI for capability 1). Thus, if the UE has a high PUSCH processing capability, terminating a PUSCH transmission k subframes after receiving DCI may be inefficient.

[0058] Accordingly, aspects of the present disclosure provide a timeline for terminating PUSCH transmission that takes into account such timing considerations between NR and LTE. In a first example, the base station may provide DCI that explicitly indicates the success of decoding of the PUSCH transmission on the PDCCH. For example, the DCI may have DCI format 0-0 or 0-1 in which the frequency domain resource allocation (FDRA) field or MCS field is set to all 1s and all remaining bits in one or more other parameters of the DCI (e.g., time domain resource allocation (TDRA), frequency hopping flag, etc.) are set to zero. The UE receives the PDCCH carrying the DCI in a control resource set (CORESET), and the DCI may instruct the UE to terminate subsequent repetitions of the PUSCH transmission after a time gap following the CORESET (e.g., up to T symbols after the last symbol of the CORESET). In a second example, the base station may provide DCI on the PDCCH that implicitly indicates the success of decoding of the first PUSCH transmission. For example, the base station may provide DCI to a UE that schedules a second PUSCH transmission within time resources overlapping with the first PUSCH transmission. The UE receives the PDCCH carrying the DCI in a CORESET, and the DCI may instruct the UE to terminate subsequent repetitions of the first PUSCH transmission after a time gap following the CORESET (e.g., up to T symbols after the last symbol of the CORESET). The DCI may also instruct the UE to transmit a second PUSCH transmission in an uplink slot after the time gap following the CORESET. In either the first example or the second example, the time gap (e.g., the value of T) may be a function of the PDCCH SCS and PUSCH SCS, PUSCH processing capabilities, whether the first symbol of the PUSCH resource allocation is reserved for a demodulation reference signal (DMRS), and the PUSCH preparation time. Additionally, the time gap (T) may include an additional number of symbols Δ for UE processing margin (e.g., T = T + Δ), and its duration may be a function of the PDCCH SCS and PUSCH SCS.For example, the duration of the additional symbol count Δ can be a function of the smaller SCS between the PDCCH SCS and the PUSCH SCS.

[0059] Accordingly, the end of PUSCH transmission based on a timeline that takes into account different timing considerations in NR can be achieved. For example, here, the end of PUSCH repetition is with respect to the CORESET symbol timing reference (the last symbol of the CORESET containing the DCI), rather than the LTE DCI subframe timing reference (the end of the subframe containing the DCI). Since the CORESET symbol timing reference is more configurable than the DCI subframe timing reference (the base station can configure the last symbol of the CORESET to be any symbol of the slot, as opposed to the end of a fixed subframe), more flexibility can be achieved in the PUSCH end start time. Furthermore, since the base station can configure different SCS, dynamic CORESET symbol timing references as opposed to a fixed DCI subframe timing reference, different symbol or slot durations resulting from different SCS can be better taken into account. Additionally, the time gap (T) can also be a function of the SCS, PUSCH processing capabilities, or other timing configurations (e.g., DMRS), so that various PUSCH end start times can be obtained.

[0060] The time gap (T) can be a function of one or more of the following exemplary parameters. In one example, T can be a function of the subcarrier spacing of the PDCCH that carries the DCI and the subcarrier spacing of the PUSCH. For example, if the SCS of both the DCI and PUSCH transmissions is 15 kHz, T can be a certain value; if the SCS of both the DCI and PUSCH transmissions is 30 kHz, T can be another value; if the SCS of the DCI is 15 kHz and the SCS of the PUSCH transmission is 30 kHz, T can be another value, and so on. Similarly, T can be a function of the subcarrier spacing of the active DL BWP in which the PDCCH is monitored and the subcarrier spacing of the active UL BWP in which the PUSCH is transmitted. For example, if the SCS of both the DL BWP that carries the DCI and the UL BWP that carries the PUSCH transmission is 15 kHz, T can be a certain value; if the SCS of both the DL BWP and UL BWP is 30 kHz, T can be another value; if the SCS of the DL ZWP is 15 kHz and the SCS of the UL BWP is 30 kHz, T can be another value, and so on. In another example, T can be a function of the PUSCH processing capability of the UE. For example, T can be one value for UE PUSCH processing capability 1 and another value for UE PUSCH processing capability 2. In a further example, T can be a function of a configuration indicating whether the first symbol of the PUSCH allocation consists of only DMRS. For example, if the base station configures the first symbol of the PUSCH transmission slot to consist of only DMRS, T can be a certain value; if the base station configures the first symbol of the PUSCH transmission slot to consist of only PUSCH data or PUSCH data and DMRS, T can be another value. In an additional example, T can be a function of the UE PUSCH preparation time T proc,2 and T proc,2 is a function of the PUSCH preparation time N 2 and N 2 is based on the numerology μ at the UE processing capability 1, where μ results in the smaller value or SCS between the maximum T proc,2 (μ DL and μ UL ), or SCS) (μ DL, μ UL corresponds to one of them, and μ DL corresponds to the subcarrier spacing when the PDCCH that carries the DCI for scheduling the PUSCH is transmitted, and μ UL corresponds to the subcarrier spacing at which the PUSCH should be transmitted. For example, the value of T can be different for different values of N2.

[0061] In addition to being a function of one or more of the above exemplary parameters, the time gap (T) can be increased for additional UE processing margin. For example, for a low-capability UE with a large PUSCH preparation time, or for a UE that transmits simultaneously to multiple base stations (e.g., the source base station and the target base station during handover), an additional number of symbols (Δ) can be added to T. In one example, the value of Δ can be fixed. For example, Δ can be preconfigured to a value of 0, 1, 2, or some other number. In another example, the value of Δ can be indicated to the UE, for example, within the PUSCH configuration. For example, when the base station provides the PUSCH configuration to the UE (e.g., pusch-Config), the PUSCH configuration can indicate the configured value of Δ (e.g., 0, 1, 2, or some other number of symbols). In a further example, the value of Δ can depend on the UE capability. For example, if the UE can support a PUSCH processing capability of 2, Δ can be one value, and if the UE can only support a PUSCH processing capability of 1, Δ can be another value. In any example, the duration of Δ can be a function of the SCS of the PDCCH that carries the DCI and the SCS of the PUSCH that carries the uplink transmission (e.g., the smaller SCS between the PDCCH SCS and the PUSCH SCS). For example, if the smaller SCS is 15 kHz, the total temporal length of Δ can be one value, and if the smaller SCS is 30 kHz, the total temporal length of Δ can be another value, and so on.

[0062] FIG. 6 shows an example 600 of a time gap 602 following a CORESET 604 in which a PDCCH carrying DCI is received. A UE may receive the CORESET 604 in slot 606 (slot N). In the illustrated example, the time gap 602 is T = 12 symbols, but in other examples, the time gap may be a different number of symbols depending on the SCS, UE capabilities, or other parameters described above. Further, in this example, the last symbol 608 of the CORESET 604 is the second symbol (symbol 1) of the slot 606, but in other examples, the last symbol 608 of the CORESET 604 may be a different symbol within the slot 606. Thus, in the illustrated example, the UE may complete a subsequent PUSCH repetition after the previous PUSCH transmission by up to 12 symbols after the second symbol of the slot 606. That is, the UE may stop transmitting the repetition of the PUSCH transmission starting from at least symbol 0 of the subsequent slot 610 (slot N + 1). Similarly, when the DCI schedules a second PUSCH transmission, the UE may start transmitting the second PUSCH transmission after the time gap 602. For example, the UE may start transmitting a second PUSCH transmission starting from symbol 0 of the subsequent slot 610 in response to the DCI.

[0063] FIG. 7 shows another example 700 of time gap 702 following CORESET 704 in which PDCCH carrying DCI is received. Similar to the example of FIG. 6, the UE may receive CORESET 704 in slot 706 (slot N). In the illustrated example, the time gap 702 is T = 13 symbols, but in other examples, the time gap may be a different number of symbols depending on the SCS, UE capabilities, or other parameters described above. Further, similar to the example of FIG. 6, here, the last symbol 708 of CORESET 704 is the second symbol (symbol 1) of slot 706, but in other examples, the last symbol 708 of CORESET 704 may be a different symbol within slot 706. However, different from the example of FIG. 6, here, the time gap 702 ends in the middle of a slot, in this case, the next slot 710 (slot N + 1). Thus, if the UE is to end a subsequent PUSCH repetition after the time gap following the CORESET, the end will start in the middle of a slot. To prevent such partial slot ends, the UE may delay the end until the start of the subsequent slot 712 (slot N + 2) as shown in FIG. 7. As a result, the UE may stop transmitting the repetition of the PUSCH transmission that starts from symbol 0 of the subsequent slot 712 (slot N + 2) instead of starting from symbol 1 of the next slot 710 (slot N + 1). Similarly, when the DCI schedules a second PUSCH transmission, the UE may start transmitting the second PUSCH transmission after the time gap 702 and an additional time delay. For example, the UE may start transmitting a second PUSCH transmission starting from symbol 0 of the subsequent slot 712 in response to the DCI.

[0064] FIG. 8 shows a further example 800 of time gap 802 following CORESET 804 in which a PDCCH carrying DCI is received. Similar to the examples of FIGS. 6 and 7, the UE may receive CORESET 804 in slot 806 (slot N). Also, similar to the example of FIG. 6, here, the last symbol 808 of CORESET 804 is the second symbol (symbol 1) of slot 806, but in other examples, the last symbol 808 of CORESET 804 may be a different symbol within slot 806. However, unlike the examples of FIGS. 6 and 7, here, time gap 802 may include multiple parts, a first time gap part 810 (T symbols) and a second time gap part 812 (Δ symbols) that the base station can configure separately. The first time gap part 810 may correspond to time gaps 602, 702 of FIGS. 6 and 7. For example, in the illustrated example, the first time gap part 810 is T = 12 symbols, but in other examples, the first time gap part may be a different number of symbols depending on the SCS, UE capabilities, or other exemplary parameters described above. The second time gap part 812 may be the number of additional symbols for additional UE processing margin. For example, in the illustrated example, the second time gap part 812 is Δ = 2 symbols, but in other examples, the second time gap part may be a different number of symbols depending on the PDCCH SCS and PUSCH SCS as described above. In addition, similar to the example of FIG. 7, here, time gap 802 (including the first time gap part 810 and the second time gap part 812) ends in the middle of a slot, in this case, the next slot 814 (slot N + 1). Thus, if the UE is to end a subsequent PUSCH repetition after the time gap following the CORESET, the end will start in the middle of a slot. To prevent such a partial slot end, the UE may delay the end until the start of subsequent slot 816 (slot N + 2) as shown in FIG. 8.As a result, the UE may stop transmitting the repetition of the PUSCH transmission that starts from symbol 0 of the subsequent slot 816 (slot N+2), instead of starting from symbol 1 of the next slot 814 (slot N+1). Similarly, when the DCI schedules a second PUSCH transmission, the UE may start transmitting the second PUSCH transmission after the time gap 802 and an additional time delay. For example, the UE may start transmitting a second PUSCH transmission starting from symbol 0 of the subsequent slot 816 in response to the DCI.

[0065] Therefore, the UE may terminate subsequent repetitions of the PUSCH transmission in response to DCI that implicitly or explicitly indicates that the base station has successfully decoded the previous PUSCH transmission. When the DCI schedules a subsequent uplink transmission in the overlapping resources of the repetition of the previous uplink transmission, the DCI may implicitly indicate the success of decoding. When the DCI contains pre-configured bit values for its various DCI format parameters (e.g., DCI format 0_0 or 0_1), the DCI may explicitly indicate the success of decoding (functioning effectively as HARQ-ACK). Such DCI that functions as explicit HARQ-ACK does not schedule subsequent uplink transmissions.

[0066] FIG. 9 shows an example 900 of DCI that functions as an explicit HARQ-ACK. The illustrated example refers to DCI format 0_0, but the DCI format may be different in other examples (e.g., DCI format 0_1). The DCI can be various parameters including FDRA 902, MCS 904, and other parameters 906 such as TDRA, frequency hopping flag, new data indicator, redundancy version, HARQ process number, etc. To explicitly indicate that the base station has successfully decoded the PUSCH transmission, the base station can configure the bits of one or more DCI parameters according to one preconfigured bit value (e.g., a bit sequence), and configure the bits of one or more other DCI parameters according to a different preconfigured bit value (e.g., a different bit sequence). For example, as shown in the example of FIG. 9, the base station can configure FDRA 902 or MCS 904 (or both) to all contain 1 bit, and configure one or more of the other parameters 906 to all contain 0 bits. Alternatively, the base station can configure FDRA or MCS (or both) to all contain 0 bits, and configure one or more of the other parameters to all contain 1 bit. In other examples, the base station can configure the FDRA, MCS, or other parameters of the DCI with other bit sequences to indicate an explicit HARQ-ACK. Thus, when the UE receives the DCI, the UE can determine that the DCI serves to approve the previous PUSCH transmission, and thus the UE can determine that it can terminate the subsequent repetition of the previous PUSCH transmission.

[0067] FIG. 10 shows an example 1000 in which a UE terminates PUSCH transmission 1002 in response to DCI in CORESET 1004 (e.g., CORESETs 604, 704, 804 in FIGS. 6-8) that explicitly indicates successful decoding of the PUSCH transmission. The base station first provides DCI 1006 in the PDCCH to the UE that schedules the PUSCH transmission, and in response, the UE begins transmitting its uplink data to the base station in PUSCH transmission 1002. While the UE transmits its uplink data in one or more repetitions, the base station can successfully decode the PUSCH transmission. Further, the base station can determine, for example, in response to a buffer status report from the UE or by some other means, that the UE has no additional data to send in its transmission buffer. Thus, the base station can provide the UE in CORESET 1004 with DCI 1008 that explicitly indicates that the PUSCH transmission has been successfully decoded. For example, DCI 1008 can have DCI format 0-0 or 0-1 in which the FDRA field or the MCS field is set to all 1s and all remaining bits in one or more other parameters of the DCI (e.g., TDRA, frequency hopping flag, etc.) are set to 0s, as described above with respect to FIG. 9. In response to receiving DCI 1008, the UE can terminate its PUSCH transmission as represented by terminated PUSCH transmission 1010 after time gap 1012 (e.g., time gaps 602, 702, 802) following CORESET 1004 that contains DCI 1008.

[0068] Figure 11 shows an example 1100 in which the UE implicitly indicates successful decoding of the first PUSCH transmission and terminates the first PUSCH transmission 1102 in response to DCI in CORESET 1104 (e.g., CORESET 604, 704, 804 in FIGS. 6-8) that schedules the second PUSCH transmission 1106. The base station first provides DCI 1108 in the PDCCH to the UE that schedules the first PUSCH transmission, and in response, the UE begins transmitting its uplink data to the base station in the first PUSCH transmission 1102. While the UE is transmitting its uplink data in one or more repetitions, the base station can successfully decode the first PUSCH transmission. Further, the base station can determine that the UE has additional data to send in its transmission buffer, for example, in response to a buffer status report from the UE or by some other means. Accordingly, the base station can provide the UE with DCI 1110 that implicitly indicates that the first PUSCH transmission has been successfully decoded. For example, DCI 1110 can schedule the second PUSCH transmission 1106 in time resources that overlap with the repetitions of the first PUSCH transmission 1102. In response to receiving DCI 1110, the UE can terminate its PUSCH transmission as represented by the terminated PUSCH transmission 1112 and begin transmitting its second PUSCH transmission after a time gap 1114 (e.g., time gaps 602, 702, 802) following CORESET 1104 that contains DCI 1110.

[0069] FIG. 12 is an example 1200 of a call flow between UE 1202 and base station 1204. The UE can transmit a capability information message 1206 to the base station. For example, in response to receiving a capability query from the base station, the UE may provide a capability information message indicating whether the UE supports advanced PUSCH processing capabilities (e.g., PUSCH processing capability 2). The base station may provide a configuration 1208 to the UE. For example, the configuration may be a PUSCH configuration indicating the number of repetitions of uplink data that the UE can transmit on the PUSCH in response to a dynamic grant. Alternatively, the configuration may be a configured grant configuration indicating the number of repetitions of uplink data that the UE can transmit on the PUSCH in response to a configured grant.

[0070] Thereafter, UE 1202 may receive DCI 1210 from base station 1204 that schedules uplink data transmission 1212. For example, DCI 1210 may correspond to DCI 1006 or DCI 1108 in FIGS. 10 or 11, respectively. Similarly, uplink data transmission 1212 may correspond to PUSCH transmission 1002 or first PUSCH transmission 1102 in FIGS. 10 or 11, respectively. The UE may then transmit uplink data transmission 1212, including one or more repetitions 1214 of the uplink data transmission configured by configuration 1208, to the base station.

[0071] In this example, after receiving one or more repetitions 1214, the base station 1204 successfully decodes the uplink data transmission 1212. Thus, the base station may provide the UE 1202 with DCI 1216 that explicitly or implicitly indicates that the uplink data transmission has been successfully decoded. For example, DCI 1216 may correspond to DCI 1008 within CORESET 1004 in FIG. 10 if the UE does not have additional data to send in its transmission buffer. In such a case, DCI 1216 may have DCI format 0-0 or 0-1 that includes one or more of its parameters configured with bit values to effectively indicate HARQ-ACK, as described above with respect to FIG. 9. Alternatively, DCI 1216 may correspond to DCI 1110 within CORESET 1104 in FIG. 11 if the UE has additional data to send in its transmission buffer. In such a case, DCI 1216 may schedule a subsequent uplink data transmission 1218 within a time resource that overlaps with one or more repetitions 1214.

[0072] At 1220, in response to receiving DCI 1216, UE 1202 may terminate subsequent repetitions of uplink data transmission 1212. For example, if the base station 1204 configures the UE to transmit 8 repetitions of uplink data transmission 1212, the base station may successfully decode the data after 4 repetitions (repetition 1214) and provide DCI 1216 to the UE before the next scheduled repetition. As a result, the UE may refrain from transmitting the remaining 4 repetitions to the base station, as represented by the terminated uplink data repetitions 1222 (e.g., the terminated PUSCH transmissions 1010, 1112 in FIGS. 10 or 11, respectively). In another example, even if the base station successfully decodes uplink data transmission 1212 even before the first configured repetition, the UE may refrain from transmitting 8 repetitions to the base station. The UE may terminate the repetition after a time gap following the CORESET containing DCI 1216 (e.g., time gaps 602, 702, 802, 1012, 1114 in FIGS. 6-8 and FIGS. 10-11). The time gap may be a function of, for example, the SCS of the PDCCH carrying DCI 1210, the SCS of the PUSCH carrying uplink data transmission 1212 or repetition 1214, the UE's PUSCH processing capability reported in the capability information message 1206, or other factors. Further, if DCI 1216 schedules a subsequent uplink data transmission 1218 in resources overlapping with the terminated uplink data repetitions 1222, the UE may transmit the subsequent uplink data transmission in the overlapping resources.

[0073] FIG. 13 is a flowchart 1300 of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, 350, 1202, device 1402). Optional aspects are indicated by dashed lines. By this method, in order to account for different timing considerations between NR and LTE, the UE can terminate PUSCH transmission after a time gap following the CORESET.

[0074] At 1302, the UE obtains information that constitutes uplink data transmission and repetitions of the uplink data transmission. For example, 1302 can be performed by the obtaining component 1440. For example, referring to FIG. 12, the UE 1202 can obtain from the base station 1204 a configuration 1208 that constitutes the uplink data transmission 1212 and the repetition 1214 of the uplink data transmission 1212. For example, the configuration can be a PUSCH configuration indicating the number of repetitions of the uplink data that the UE can transmit on the PUSCH in response to a dynamic grant. In another example, the configuration can be a configured grant configuration indicating the number of repetitions of the uplink data that the UE can transmit on the PUSCH in response to a configured grant. Thus, the obtained information can be a PUSCH configuration, a configured grant configuration, or other configuration for uplink data transmission including uplink data repetitions. The information constituting the uplink data transmission and the repetitions of the uplink data transmission can be the same information (e.g., a single configuration) or different information (e.g., different configurations).

[0075] At 1304, the UE sends the uplink data transmission to the base station. For example, 1304 can be performed by the transmitting component 1442. For example, referring to FIG. 12, the UE 1202 can send the uplink data transmission 1212 to the base station 1204. The UE 1202 can also send one or more repetitions 1214 of the uplink data transmission. The uplink data transmission and the repetitions can be scheduled by DCI 1210.

[0076] Finally, at 1306, in response to receiving downlink information on the downlink control channel, the UE terminates the repetition of uplink data transmission. For example, 1306 can be implemented by the termination component 1444. For example, referring to FIG. 12, at 1220, the UE 1202 terminates or refrains from sending one or more subsequent repetitions of the uplink data transmission 1212, as represented by the terminated uplink data repetition 1222. The UE may refrain from sending the repetition in response to receiving DCI 1216 on the PDCCH.

[0077] The repetition ends after a time gap following the CORESET in which the downlink control channel is received. For example, referring to FIGS. 6 to 8 and FIGS. 10 to 12, the UE 1202 may end the repetition at 1220 after a time gap (e.g., time gaps 602, 702, 802, 1012, 1114) following the CORESET (e.g., CORESETs 604, 704, 804, 1004, 1104) in which the PDCCH carrying DCI 1216 (e.g., DCI 1008, 1110) is received.

[0078] The time gap can be equal to the length of one or more symbols following the last symbol of the CORESET. For example, referring to FIG. 6, the time gap 602 can be equal to the length of 12 symbols (T = 12 symbols) following the last symbol 608 of the CORESET 604. In another example, referring to FIG. 7, the time gap 702 can be equal to the length of 13 symbols (T = 13 symbols) following the last symbol 708 of the CORESET 704. The time gap can have different symbol lengths in other examples. Additionally, the time gap can end within a slot, and the end at 1306 can start with the initial symbol of a subsequent slot. For example, referring to FIGS. 7 and 8, the time gaps 702, 802 can end within the next slots 710, 814 (slot N + 1), and the completed PUSCH transmission (e.g., the completed uplink data repetition 1222 in FIG. 12) can start with symbol 0 of the subsequent slots 712, 816 (slot N + 2).

[0079] The downlink information can indicate HARQ-ACK. In this example, the downlink information can include FDRA, MCS, and other parameters, and the HARQ-ACK can be indicated by a first pre-configured bit value of FDRA or MCS and a second pre-configured bit value of other parameters. The second pre-configured bit value can be different from the first pre-configured bit value. For example, referring to FIGS. 10 and 12, the DCI 1008, 1216 can explicitly indicate that the uplink data transmission 1212 or repetition 1214 has been successfully decoded. For example, the DCI 1008, 1216 can have DCI format 0-0 or 0-1 that includes one or more of its parameters configured with bit values to effectively indicate HARQ-ACK as described above with respect to FIG. 9. As an example, the FDRA 902 or MCS 904 of the DCI can be set all to 1, and the other parameters 906 of the DCI can be set all to 0. The base station 1204 can provide this DCI, for example, when the UE does not have additional data to send in its transmission buffer.

[0080] Downlink information may schedule subsequent uplink data transmission after a time gap. For example, referring to FIGS. 11 and 12, DCI 1110, 1216 may implicitly indicate that uplink data transmission 1212 or iteration 1214 has been successfully decoded. For example, DCI 1216 may schedule subsequent uplink data transmission 1218 within a time resource that overlaps with one or more iterations 1214 after time gaps 602, 702, 802, 1114. Further, the time gap may end within a slot, and subsequent uplink data transmission may start at the initial symbol of a subsequent slot. For example, referring to FIG. 8, time gap 802 may end within the next slot 814 (slot N + 1), and subsequent PUSCH transmission (e.g., subsequent uplink data transmission 1218 in FIG. 12) may start at symbol 0 of subsequent slot 816 (slot N + 2).

[0081] The time gap may be a function of a first SCS of a PDCCH that carries downlink information and a second SCS of a PUSCH that carries uplink data transmission. For example, referring to FIGS. 6 - 8 and FIGS. 10 - 12, time gaps 602, 702, 802, 1012, 1114 (T) may be a function of the sub - carrier spacing of the PDCCH that carries DCI 1008, 1110, 1216 and the sub - carrier spacing of the PUSCH that carries uplink data transmission 1212 or iteration 1214. For example, if the SCS of both the DCI and PUSCH transmissions is 15 kHz, T may be one value; if the SCS of both the DCI and PUSCH transmissions is 30 kHz, T may be another value; if the SCS of the DCI is 15 kHz and the SCS of the PUSCH transmission is 30 kHz, T may be another value, and so on.

[0082] The time gap can be a function of the first SCS of the downlink BWP including the PDCCH and the second SCS of the uplink BWP including the PUSCH. For example, referring to FIGS. 6 to 8 and FIGS. 10 to 12, the time gaps 602, 702, 802, 1012, 1114(T) can be a function of the subcarrier spacing of the active DL BWP in which the PDCCH carrying DCI1008, 1110, 1216 is monitored and the subcarrier spacing of the active UL BWP in which the PUSCH carrying uplink data transmission 1212 or repetition 1214 is transmitted. For example, when the SCSs of both the DL BWP carrying the DCI and the UL BWP carrying the PUSCH transmission are 15 kHz, T can be a certain value, when the SCSs of both the DL BWP and the UL BWP are 30 kHz, T can be another value, when the SCS of the DL ZWP is 15 kHz and the SCS of the UL BWP is 30 kHz, T can be another value, and so on.

[0083] The time gap can be a function of the UE PUSCH processing capability. For example, referring to FIGS. 6 to 8 and FIGS. 10 to 12, the time gaps 602, 702, 802, 1012, 1114(T) can be a function of the UE PUSCH processing capability. For example, T can be a certain value for the UE PUSCH processing capability 1 and another value for the UE PUSCH processing capability 2. The UE PUSCH processing capability can be indicated, for example, by the capability information message 1206 in FIG. 12.

[0084] The time gap can be a function of a configuration indicating whether the first symbol of the uplink data transmission is reserved for DMRS. For example, referring to FIGS. 6 to 8 and FIGS. 10 to 12, the time gaps 602, 702, 802, 1012, 1114(T) can be a function of a configuration (e.g., configuration 1208 or a different configuration) indicating whether the first symbol of the PUSCH allocation for the uplink data transmission 1212 or the repetition 1214 is composed of only DMRS. For example, when the base station configures the first symbol of the slot for PUSCH transmission to include only DMRS, T can be a certain value, and when the base station configures the first symbol of the slot for PUSCH transmission to include only PUSCH data or both PUSCH data and DMRS, T can be another value.

[0085] The time gap can be a function of the PUSCH preparation time. For example, referring to FIGS. 6 to 8 and FIGS. 10 to 12, the time gaps 602, 702, 802, 1012, 1114(T) can be a function of the UE PUSCH preparation time T proc,2 and T proc,2 is a function of the PUSCH preparation time N 2 and N 2 is based on the numerology μ at the UE processing capability 1, where μ results in the smaller value or SCS between the maximum T proc,2 (μ DL , μ UL ) and corresponds to one of them, and μ DL , μ UL corresponds to the subcarrier spacing when the PDCCH carrying the DCI for scheduling the PUSCH is transmitted, and μ DL corresponds to the subcarrier spacing at which the PUSCH is to be transmitted. For example, the value of T can be different for different values of N UL . 2

[0086] The time gap may include a plurality of separately configurable parts. For example, referring to FIG. 8, the time gap 802 may include a plurality of parts, such as a first time gap part 810 (T symbols) and a second time gap part 812 (Δ symbols) that can be separately configured by the base station. One of the separately configurable parts (for example, the second time gap part 812) may be pre-configured (for example, fixed), indicated by a PUSCH configuration (for example, configuration 1208 or a different configuration), or dependent on the UE capabilities. For example, in one example, the value of Δ may be fixed to 0, 1, 2, or some other number value. In another example, the base station may dynamically indicate the value of Δ to the UE within a PUSCH configuration (for example, 0, 1, 2, or some other number of symbols). In a further example, the value of Δ may be dependent on the UE capabilities. For example, if the UE can support PUSCH processing capability 2, Δ may be one value, and if the UE can only support PUSCH processing capability 1, Δ may be another value.

[0087] In addition, one of the separately configurable parts (for example, the second time gap part 812) may be a function of the first SCS of the PDCCH that carries downlink information and the second SCS of the PUSCH that carries uplink data transmission. For example, the duration of Δ may be a function of the SCS of the PDCCH that carries DCI1216 and the SCS of the PUSCH that carries uplink transmission 1212 or repetition 1214 (for example, the smaller SCS between the PDCCH SCS and the PUSCH SCS). For example, if the smaller SCS is 15 kHz, the total temporal length of Δ may be one value, and if the smaller SCS is 30 kHz, the total temporal length of Δ may be another value, and so on.

[0088] FIG. 14 is a diagram 1400 showing an example of a hardware implementation form of the apparatus 1402. The apparatus 1402 is a UE and includes a cellular baseband processor 1404 (also called a modem) coupled to cellular RF transceivers 1422 and one or more subscriber identity module (SIM) cards 1420, an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410, a Bluetooth module 1412, a wireless local area network (WLAN) module 1414, a global positioning system (GPS) module 1416, and a power supply 1418. The cellular baseband processor 1404 communicates with the UE 104 and / or the BS 102 / 180 through the cellular RF transceiver 1422. The cellular baseband processor 1404 may include a computer-readable medium / memory. The computer-readable medium / memory may be non-transitory. The cellular baseband processor 1404 is responsible for general processing including the execution of software stored on the computer-readable medium / memory. When the software is executed by the cellular baseband processor 1404, it causes the cellular baseband processor 1404 to perform the various functions described above. The computer-readable medium / memory may be used to store data operated on by the cellular baseband processor 1404 when the software is executed. The cellular baseband processor 1404 further includes a receiving component 1430, a communication manager 1432, and a transmitting component 1434. The communication manager 1432 includes one or more of the illustrated components. The components within the communication manager 1432 may be stored in the computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1404. The cellular baseband processor 1404 may be a component of the UE 350 and may include at least one of the memory 360 and / or the TX processor 368, the RX processor 356, and the controller / processor 359.In one configuration, device 1402 may be a modem chip and may include only baseband processor 1404. In another configuration, device 1402 may be the entire UE (see, e.g., reference 350 in FIG. 3) and may include the aforementioned additional modules of device 1402.

[0089] Communication manager 1432 includes, for example, an acquisition component 1440 configured to acquire information that configures uplink data transmission and the repetition of uplink data transmission, as described in connection with 1302. FIG. 15A shows an example 1500 of a process or algorithm executed by acquisition component 1440. The acquisition component may be implemented, for example, in RX processor 356. At 1502, acquisition component 1440 receives information. For example, referring to FIG. 3, acquisition component 1440 may receive a signal carrying information from base station 310 via one or more respective antennas 352. Next, at 1504, acquisition component 1440 decodes the received information. For example, referring to FIG. 3, the acquisition component may demodulate the received information based on a modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.).

[0090] The communication manager 1432 receives an input of the form of information from the acquisition component 1440 and further includes a transmission component 1442 configured to send uplink data transmission to a base station, as described, for example, in connection with 1304. FIG. 15B shows an example 1520 of a process or algorithm executed by the transmission component 1442. The transmission component may be implemented, for example, in the TX processor 368. At 1522, the transmission component 1442 encodes the uplink data. For example, referring to FIG. 3, the transmission component 1442 may modulate the uplink data based on a modulation scheme (such as BPSK, QPSK, M-PSK, M-QAM, etc.). Next, at 1524, the transmission component 1442 transmits the encoded uplink data. For example, referring to FIG. 3, the transmission component may transmit the encoded uplink data to the base station 310 via one or more respective antennas 352.

[0091] Communication manager 1432 receives the input of the information form from acquisition component 1440, and further includes an end component 1444 configured to end the iteration of uplink data transmission in response to the reception of downlink information in the downlink control channel, as described in relation to 1306. FIG. 15C shows an example 1540 of a process or algorithm executed by end component 1444. The end component may be implemented, for example, in controller / processor 359. At 1542, end component 1444 receives downlink information. For example, referring to FIG. 3, end component 1444 may receive DCI from RX processor 356 (or acquisition component 1440 of RX processor 356). For example, acquisition component 1440 within RX processor 356 receives a signal carrying a PDCCH payload including DCI from base station 310 via one or more respective antennas 352, demodulates the PDCCH payload based on a modulation scheme (such as BPSK, QPSK, M-PSK, M-QAM, etc.), and may provide the demodulated PDCCH payload including DCI to end component 1444 in controller / processor 359. Next, end component 1444 may decode the demodulated PDCCH payload to receive DCI. Then, at 1544, end component 1444 refrains from transmitting the iteration in response to the received downlink information. For example, referring to FIG. 3, end component 1444 may stop the delivery of uplink data iteration to TX processor 368 (or transmission component 1442 of the TX processor).

[0092] The apparatus may include additional components that execute each of the blocks of the algorithms in the aforementioned flowcharts of FIGS. 13 and 15A - 15C. Thus, each block in the aforementioned flowcharts of FIGS. 13 and 15A - 15C may be executed by a component, and the apparatus may include one or more of those components. The components may be one or more hardware components specifically configured to perform the described process / algorithm, implemented by a processor configured to perform the described process / algorithm, stored in a computer - readable medium for implementation by a processor, or some combination thereof.

[0093] In one configuration, the apparatus 1402, and in particular the cellular baseband processor 1404, includes means for obtaining information that constitutes uplink data transmission and repetitions of uplink data transmission, means for sending the uplink data transmission to a base station, and means for ending the repetitions of the uplink data transmission in response to receiving downlink information in a downlink control channel. The repetition ends after a time gap following the CORESET in which the downlink control channel is received.

[0094] In one configuration, the time gap may be equal to the length of one or more symbols following the last symbol of the CORESET.

[0095] In one configuration, the time gap may end within a slot, and the end may start with the initial symbol of a subsequent slot.

[0096] In one configuration, the downlink information may indicate a HARQ - ACK. In one configuration, the downlink information may include FDRA, MCS, and other parameters, and the HARQ - ACK may be indicated by a first pre - configured bit value of the FDRA or MCS and a second pre - configured bit value of the other parameters, and the second pre - configured bit value is different from the first pre - configured bit value.

[0097] In one configuration, the downlink information may schedule subsequent uplink data transmission after the time gap. In one configuration, the time gap may end within a slot, and subsequent uplink data transmission may start at the initial symbol of a subsequent slot.

[0098] In one configuration, the time gap may be a function of the first SCS of the PDCCH that carries downlink information and the second SCS of the PUSCH that carries uplink data transmission.

[0099] In one configuration, the time gap may be a function of the first SCS of the downlink BWP including the PDCCH and the second SCS of the uplink BWP including the PUSCH.

[0100] In one configuration, the time gap may be a function of the UE PUSCH processing capability.

[0101] In one configuration, the time gap may be a function of a configuration indicating whether the first symbol of the uplink data transmission is reserved for the DMRS.

[0102] In one configuration, the time gap may be a function of the PUSCH preparation time.

[0103] In one configuration, the time gap may include a plurality of separately configurable parts. In one configuration, one of the separately configurable parts is pre-configured, indicated in the PUSCH configuration, or dependent on the UE capabilities. In one configuration, one of the separately configurable parts may be a function of the first SCS of the PDCCH that carries downlink information and the second SCS of the PUSCH that carries uplink data transmission.

[0104] The above means may be one or more of the above components of apparatus 1402 configured to perform the functions enumerated by the above means. As described above, apparatus 1402 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the above means may be a TX processor 368, an RX processor 356, and a controller / processor 359 configured to perform the functions enumerated by the above means.

[0105] If the base station has already decoded the uplink data in the previous PUSCH transmission or iteration, due to the conventional lack of HARQ feedback for PUSCH in NR, the UE may continue to send unnecessary PUSCH iterations. As a result, the UE may waste transmission power and PUSCH resources with inefficient iterations. To address this power waste and inefficiency, the base station may provide the UE with DCI that explicitly or implicitly indicates whether the previous PUSCH transmission was successfully decoded, and the UE may perform an early termination of the ongoing PUSCH transmission (e.g., terminate inefficient iterations). Thus, UE power reduction and resource efficiency improvement can be achieved. Further, the UE may terminate the PUSCH transmission not after several subframes (k subframes) following the subframe containing the DCI, but after a time gap (T symbols) following the CORESET containing the PDCCH that carries the DCI. The time gap may be a function of various parameters such as the PDCCH SCS (or DL BWP SCS), the PUSCH SCS (or UL BWP SCS), the UE PUSCH processing capability, the DMRS configuration, or the PUSCH preparation time. Such configurable timing can adapt to the various timing configurations present in NR (e.g., dynamic TDD, different numerologies between the PDCCH and the PUSCH, and multiple PUSCH processing capabilities) and minimize contention. Further, the time gap may be divided into separately configurable parts, one of which may also be a function of the PDCCH SCS and the PUSCH SCS. Such configured parts may provide additional UE processing margin for low-capability UEs while also considering the various timing configurations present in NR as described above.

[0106] It is understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is an illustration of an exemplary approach. Based on design preferences, it is understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged. Additionally, some blocks may be combined or omitted. The appended method claims present the elements of the various blocks in an exemplary order and are not limited to the specific order or hierarchy presented.

[0107] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Accordingly, the claims are not intended to be limited to the aspects shown herein but are to be accorded the widest scope consistent with the claim language and not inconsistent with the disclosed technology. References to elements in the singular are not intended to mean "sole and exclusive" unless explicitly so stated but rather "one or more." Terms such as "if," "when," and "while" are not intended to imply an immediate temporal relationship or reaction but should be construed to mean "under the condition that." That is, these phrases, for example, "when," do not imply an immediate action in response to an action or during the occurrence of an action but rather simply imply that the action occurs when the condition is met, without requiring a specific or immediate time constraint for the action to occur. The term "exemplary" as used herein means "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," "A, B, C, or any combination thereof" include any combination of A, B, and / or C and may include multiple A's, multiple B's, or multiple C's.Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A, B, and C, and any such combination may include one or more members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure, whether known or later to become known to those skilled in the art, are expressly incorporated herein by reference and are intended to be encompassed by the claims. Further, what is disclosed herein is not dedicated to the public regardless of whether such disclosure is expressly recited in the claims. The terms "module", "mechanism", "element", "device", etc. may not be substitutes for the term "means". Accordingly, no claim element should be construed as a means-plus-function unless the element is expressly recited using the phrase "means for".

[0108] The following examples are illustrative only and, without limitation, may be combined with other embodiments or aspects of the teachings described herein.

[0109] Example 1 is a method of wireless communication in a user equipment (UE), including the steps of obtaining information constituting uplink data transmission and iterations of uplink data transmission, sending the uplink data transmission to a base station, and ending the iterations of the uplink data transmission in response to receiving downlink information on a downlink control channel, where the iterations end after a time gap following a control resource set (CORESET) on which the downlink control channel is received.

[0110] Example 2 is the method according to Example 1, where the time gap is equal to the length of one or more symbols following the last symbol of the CORESET.

[0111] Example 3 is the method according to any one of Examples 1 and 2, where the time gap ends during the slot and the end starts with the first symbol of the subsequent slot.

[0112] Example 4 is the method according to any one of Examples 1 to 3, where the downlink information indicates a hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK).

[0113] Example 5 is the method according to Example 4, where the downlink information includes frequency domain resource allocation (FDRA), modulation and coding scheme (MCS), and other parameters, and the HARQ-ACK is indicated by a first pre-configured bit value of the FDRA or MCS and a second pre-configured bit value of the other parameters, and the second pre-configured bit value is different from the first pre-configured bit value.

[0114] Example 6 is the method according to any one of Examples 1 to 3, where the downlink information schedules a subsequent uplink data transmission after the time gap.

[0115] Example 7 is the method according to Example 6, where the time gap ends during the slot and the subsequent uplink data transmission starts with the initial symbol of the subsequent slot.

[0116] Example 8 is the method according to any one of Examples 1 to 7, where the time gap is a function of a first subcarrier spacing (SCS) of a physical downlink control channel (PDCCH) carrying the downlink information and a second SCS of a physical uplink shared channel (PUSCH) carrying the uplink data transmission.

[0117] Example 9 is the method according to any one of Examples 1 to 8, wherein the time gap is a function of a first subcarrier spacing (SCS) of a downlink bandwidth part (BWP) including a physical downlink control channel (PDCCH) and a second SCS of an uplink BWP including a physical uplink shared channel (PUSCH).

[0118] Example 10 is the method according to any one of Examples 1 to 9, wherein the time gap is a function of the UE physical uplink shared channel (PUSCH) processing capability.

[0119] Example 11 is the method according to any one of Examples 1 to 10, wherein the time gap is a function of a configuration indicating whether a first symbol of uplink data transmission is reserved for a demodulation reference signal (DMRS).

[0120] Example 12 is the method according to any one of Examples 1 to 11, wherein the time gap is a function of the physical uplink shared channel (PUSCH) preparation time.

[0121] Example 13 is the method according to any one of Examples 1 to 12, wherein the time gap includes a plurality of separately configurable parts.

[0122] Example 14 is the method according to Example 13, wherein one of the separately configurable parts is preconfigured, indicated in a physical uplink shared channel (PUSCH) configuration, or depends on UE capabilities.

[0123] Example 15 is the method according to Example 13 or 14, wherein one of the separately configurable parts is a function of a first subcarrier spacing (SCS) of a physical downlink control channel (PDCCH) carrying downlink information and a second SCS of a physical uplink shared channel (PUSCH) carrying uplink data transmission.

[0124] Example 16 is a device for wireless communication, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, which, when executed by the processor, cause the device to obtain information constituting uplink data transmission and repetition of uplink data transmission, send the uplink data transmission to a base station, and terminate the repetition of the uplink data transmission in response to reception of downlink information in a downlink control channel, where the repetition ends after a time gap following a control resource set (CORESET) in which the downlink control channel is received.

[0125] Example 17 is the device according to Example 16, wherein the time gap is equal to the length of one or more symbols following the last symbol of the CORESET.

[0126] Example 18 is the device according to any one of Examples 16 and 17, wherein the downlink information indicates a hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK).

[0127] Example 19 is the device according to any one of Examples 16 and 17, wherein the downlink information schedules a subsequent uplink data transmission after the time gap.

[0128] Example 20 is the device according to any one of Examples 16 to 19, wherein the time gap is a function of a first subcarrier spacing (SCS) of a physical downlink control channel (PDCCH) carrying the downlink information and a second SCS of a physical uplink shared channel (PUSCH) carrying the uplink data transmission.

[0129] Example 21 is the device according to any one of Examples 16 to 20, wherein the time gap is a function of a first subcarrier spacing (SCS) of a downlink bandwidth part (BWP) including a physical downlink control channel (PDCCH) and a second SCS of an uplink BWP including a physical uplink shared channel (PUSCH).

[0130] Example 22 is the apparatus according to any one of Examples 16 to 21, wherein the time gap is a function of the UE physical uplink shared channel (PUSCH) processing capability.

[0131] Example 23 is the apparatus according to any one of Examples 16 to 22, wherein the time gap is a function of a configuration indicating whether a first symbol of uplink data transmission is reserved for a demodulation reference signal (DMRS).

[0132] Example 24 is the apparatus according to any one of Examples 16 to 23, wherein the time gap is a function of the physical uplink shared channel (PUSCH) preparation time.

[0133] Example 25 is the apparatus according to any one of Examples 16 to 24, wherein the time gap includes a plurality of separately configurable parts.

[0134] Example 26 is the apparatus according to Example 25, wherein one of the separately configurable parts is a function of a first subcarrier spacing (SCS) of a physical downlink control channel (PDCCH) that carries downlink information and a second SCS of a physical uplink shared channel (PUSCH) that carries uplink data transmission.

[0135] Example 27 is an apparatus for wireless communication, comprising means for obtaining information constituting uplink data transmission and repetitions of uplink data transmission, means for sending uplink data transmission to a base station, and means for ending repetitions of uplink data transmission in response to reception of downlink information in a downlink control channel, wherein the repetitions end after a time gap following a control resource set (CORESET) in which the downlink control channel is received.

[0136] Example 28 is the apparatus according to Example 27, wherein the downlink information indicates a hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK).

[0137] Example 29 is the apparatus according to Example 27, in which downlink information schedules subsequent uplink data transmission after a time gap.

[0138] Example 30 is a computer-readable medium storing computer-executable code, which, when executed by a processor, causes the processor to obtain information constituting uplink data transmission and iterations of uplink data transmission, send the uplink data transmission to a base station, and terminate the iterations of uplink data transmission in response to receiving downlink information on a downlink control channel, and the iterations terminate after a time gap following a control resource set (CORESET) on which the downlink control channel is received.

Explanation of Signs

[0139] 100 Access network 102 Base station 102' Small cell 104 User equipment (UE) 110 Geographic coverage area 110' Coverage area 120 Communication link 132 First backhaul link 134 Third backhaul link 150 Wi-Fi access point (AP) 152 Wi-Fi station (STA) 154 Communication link 158 Device-to-device (D2D) communication link 160 Evolved packet core (EPC) 162 Mobility management entity (MME) 164 Other MME 166 Serving gateway 168 MBMS gateway 170 Broadcast multicast service center (BM-SC) 172 Packet data network (PDN) gateway 174 Home Subscriber Server (HSS) 176 IP Services 180 Base Station 182 Beamforming 182' Transmission Direction 182'' Reception Direction 184 Second Backhaul Link 190 Core Network 192 Access and Mobility Management Function (AMF) 193 Other AMF 194 Session Management Function (SMF) 195 User Plane Function (UPF) 196 Unified Data Management (UDM) 197 IP Services 198 PUSCH Termination Component 310 Base Station 316 Transmission (TX) Processor 318 Transmitter 318 Receiver 320 Antenna 350 UE 352 Antenna 354 Receiver 354 Transmitter 354 Transmitter 356 Reception (RX) Processor 358 Channel Estimator 359 Controller / Processor 360 Memory 368 TX Processor 370 Reception (RX) Processor 374 Channel Estimator 375 Controller / Processor 376 Memory 402 PUSCH Transmission 404 DCI 406 DCI 408 PUSCH Transmission 502 First PUSCH Transmission 504 Second PUSCH Transmission 506 DCI 508 DCI 510 PUSCH Transmission 602 Time Gap 604 CORESET 606 Slot 608 Last Symbol 610 Subsequent Slot 702 Time Gap 704 CORESET 706 Slot 708 Last Symbol 710 Next Slot 712 Subsequent Slots 802 Time Gap 804 CORESET 806 Slot 808 Last Symbol 810 First Time Gap Portion 812 Second Time Gap Portion 814 Next Slot 902 FDRA 904 MCS 906 Other Parameters 1002 PUSCH Transmission 1004 CORESET 1006 DCI 1008 DCI 1010 PUSCH Transmission 1012 Time Gap 1102 First PUSCH Transmission 1104 CORESET 1106 Second PUSCH Transmission 1108 DCI 1110 DCI 1202 UE 1204 Base Station 1206 Capability Information Message 1208 Configuration 1210 DCI 1212 Uplink Data Transmission 1214 Iteration 1216 DCI 1218 Uplink Data Transmission 1222 Uplink Data Iteration 1402 Device 1404 Cellular Baseband Processor 1406 Application Processor 1408 Secure Digital (SD) Card 1410 Screen 1412 Bluetooth Module 1414 Wireless Local Area Network (WLAN) Module 1416 Global Positioning System (GPS) Module 1418 Power Supply 1420 Subscriber Identity Module (SIM) Card 1422 Cellular RF Transceiver 1430 Receiver Component 1432 Communication Manager 1434 Transmitter Component 1440 Acquisition Component 1442 Transmitter Component 1444 Termination Component

Claims

1. 1. A method of wireless communication in a user equipment (UE), comprising: obtaining information for configuring an uplink data transmission and a repetition of said uplink data transmission; sending the uplink data transmission to a base station; and terminating the repetition of the uplink data transmission in response to receiving downlink information on a downlink control channel. the iteration ends after a time gap following a control resource set (CORESET) on which the downlink control channel is received; the downlink information indicating a Hybrid Automatic Repeat Request (HARQ) Acknowledgement (HARQ-ACK); The downlink information includes a Frequency Domain Resource Allocation (FDRA), a Modulation and Coding Scheme (MCS), and other parameters, and the HARQ-ACK is indicated by a first preconfigured bit value of the FDRA or the MCS and a second preconfigured bit value of the other parameters, the second preconfigured bit value being different from the first preconfigured bit value. method.

2. The method of claim 1 , wherein the time gap is equal to a length of one or more symbols following the last symbol of the CORESET.

3. The method of claim 1 , wherein the time gap ends during a slot and the end begins with a first symbol of a subsequent slot.

4. 2. The method of claim 1, wherein the time gap is a function of a first subcarrier spacing (SCS) of a physical downlink control channel (PDCCH) that carries the downlink information and a second SCS of a physical uplink shared channel (PUSCH) that carries the uplink data transmission.

5. 2. The method of claim 1, wherein the time gap is a function of a first subcarrier spacing (SCS) of a downlink bandwidth portion (BWP) that includes a physical downlink control channel (PDCCH) and a second SCS of an uplink BWP that includes a physical uplink shared channel (PUSCH).

6. 2. The method of claim 1, wherein the time gap is a function of a UE Physical Uplink Shared Channel (PUSCH) processing capability.

7. 2. The method of claim 1, wherein the time gap is a function of a configuration indicating whether a first symbol of the uplink data transmission is reserved for a demodulation reference signal (DMRS).

8. The method of claim 1 , wherein the time gap is a function of a Physical Uplink Shared Channel (PUSCH) preparation time.

9. The method of claim 1 , wherein the time gap comprises multiple, separately configurable portions.

10. 10. The method of claim 9, wherein one of the separately configurable parts is pre-configured, indicated in a Physical Uplink Shared Channel (PUSCH) configuration, or dependent on UE capabilities.

11. 10. The method of claim 9, wherein one of the separately configurable portions is a function of a first subcarrier spacing (SCS) of a physical downlink control channel (PDCCH) that carries the downlink information and a second SCS of a physical uplink shared channel (PUSCH) that carries the uplink data transmission.

12. 1. An apparatus for wireless communication, comprising: means for obtaining information configuring an uplink data transmission and a repetition of said uplink data transmission; means for sending the uplink data transmission to a base station; means for terminating the repetition of the uplink data transmission in response to receiving downlink information on a downlink control channel; the iteration ends after a time gap following a control resource set (CORESET) on which the downlink control channel is received; the downlink information indicating a Hybrid Automatic Repeat Request (HARQ) Acknowledgement (HARQ-ACK); The downlink information includes a Frequency Domain Resource Allocation (FDRA), a Modulation and Coding Scheme (MCS), and other parameters, and the HARQ-ACK is indicated by a first preconfigured bit value of the FDRA or the MCS and a second preconfigured bit value of the other parameters, the second preconfigured bit value being different from the first preconfigured bit value. Device.

13. A computer program comprising instructions which, when executed by a computer, cause the computer to carry out a method according to any one of claims 1 to 11. Computer program.

Images