Method, apparatus, and computer readable medium for early termination of a PUSCH transmission

Abstract

This provides aspects that allow the UE to prematurely terminate the repetition of an ongoing PUSCH transmission in response to a DCI indication from the base station indicating whether a previous PUSCH transmission or repetition has been successfully decoded. The UE obtains information configuring uplink data transmission and the repetition of uplink data transmission. The UE sends uplink data transmission to the base station. The UE terminates the repetition of uplink data transmission in response to receiving downlink information in the downlink control channel. Therefore, reduced UE power and enhanced resource efficiency can be achieved. Furthermore, the repetition terminates after a time gap following the CORESET in which the downlink control channel is received. Therefore, the start time for terminating PUSCH repetition can be configured to accommodate various timing considerations, such as dynamic TDD, different parameter sets between PDCCH and PUSCH, and the capacity for multiple PUSCH processing.

Description

[0001] This patent application claims priority to U.S. Patent Application No. 17 / 165,860, filed February 2, 2021, entitled “Early Termination of PUSCH Transmission,” which has been assigned to the assignee of this application and is expressly incorporated herein by reference for all purposes. Technical Field

[0002] This disclosure generally relates to communication systems, and more specifically, to a wireless communication system between a user equipment (UE) and a base station. Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies 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 multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with 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 communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0005] The following provides a brief overview of one or more aspects to offer a basic understanding of them. This overview is not a comprehensive summary of all anticipated aspects, nor is it intended to identify key or important elements of all aspects, nor to depict the scope of any or all aspects. Its sole purpose is to present some ideas of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0006] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a UE (User Equipment). The UE obtains information configuring uplink data transmission and the repetition of uplink data transmission. The UE transmits uplink data transmission to a base station, and the UE terminates the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel. The repetition terminates after a time gap following the control resource set (CORESET) after which the downlink control channel is received.

[0007] To achieve the foregoing and related objectives, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth specific illustrative features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of each aspect can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0009] Figure 2A This is an illustration showing an example of the first frame according to various aspects of this disclosure.

[0010] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0011] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0012] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0013] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0014] Figure 4 This is a diagram illustrating an example of uplink data transmission that terminates in response to an explicit indication of successful decoding of downlink information.

[0015] Figure 5 This is a diagram illustrating an example of a first uplink data transmission that terminates in response to downlink information implicitly indicating successful decoding of the first transmission and scheduling of the second uplink data transmission.

[0016] Figure 6 This is a diagram illustrating an example of the time gap following the CORESET in which downlink information is received.

[0017] Figure 7 This is a diagram illustrating another example of the time gap following the CORESET in which downlink information is received.

[0018] Figure 8 This is a diagram illustrating another example of the time gap following the CORESET in which downlink information is received.

[0019] Figure 9 This is a diagram illustrating an example of downlink information used as explicit acknowledgment feedback for uplink data transmission.

[0020] Figure 10 This is a diagram illustrating an example of uplink data transmission that terminates upon successful decoding of a transmission, explicitly indicated by downlink information in CORESET.

[0021] Figure 11 This is a diagram illustrating an example of a first uplink data transmission that terminates in response to downlink information in CORESET that implicitly indicates successful decoding of the first transmission and schedules the second uplink data transmission.

[0022] Figure 12 This is a call flow diagram between the UE and the base station.

[0023] Figure 13 This is a flowchart of the wireless communication method at the UE.

[0024] Figure 14 This is a diagram illustrating an example hardware implementation of the example device.

[0025] Figures 15A-15C This is a flowchart of an example process executed by the UE. Detailed Implementation

[0026] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as representing the only configuration in which the concepts described herein can 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 can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0027] When a base station configures a UE to transmit uplink data on the Physical Uplink Shared Channel (PUSCH), the base station can instruct the UE to transmit repetitions of its uplink data for coverage enhancement and improved data reliability. Typically, a UE can be configured to transmit up to sixteen repetitions of PUSCH transmission in response to dynamic grant, or up to eight repetitions in response to configured grant. However, for example, to further extend PUSCH coverage for enhanced mobile broadband (eMBB) / VoIP, to support low-capability UEs with extended coverage, or in other cases, the number of repetitions can be increased to more than sixteen. Therefore, the UE can transmit several repetitions of its uplink data so that the base station can successfully decode the uplink data.

[0028] While in some cases a base station can successfully decode uplink data after receiving all configured repetitions (e.g., when the UE is located at a considerable distance from the base station, such as at the cell edge), in other cases a base station can successfully decode data after receiving only some configured repetitions. For example, even if the base station configures the UE to send eight PUSCH repetitions, if the UE is not located at the cell edge or otherwise in a geometry with high signal quality, the base station may successfully decode data after receiving only four PUSCH repetitions (or some other number less than eight).

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

[0030] Therefore, even if the base station has already decoded the uplink data in a previous PUSCH transmission or repetition, the UE may not be certain that the base station has successfully decoded the data until the time period for receiving DCI has passed, and thus the UE will continue to send unnecessary PUSCH repetitions in the middle. As a result, the UE wastes transmission power and PUSCH resources on inefficient repetitions. Therefore, allowing the UE to terminate ongoing PUSCH transmissions early (e.g., terminating inefficient repetitions) to save UE power and improve resource efficiency would be helpful.

[0031] Therefore, various aspects for terminating repetitions of PUSCH transmissions are provided. In the first example, the base station may provide a DCI in the PDCCH that explicitly indicates successful decoding of the PUSCH transmission. This indication can be provided using bit values ​​configured with various parameters for the DCI. For example, the DCI may have a DCI format of 0-0 or 0-1, which includes a Frequency Domain Resource Allocation (FDRA) field or an MCS field 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.) set to zero. The UE may receive a 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 slot following the CORESET (e.g., no later than T symbols after the last symbol of the CORESET). In the second example, the base station may provide a DCI in the PDCCH that implicitly indicates successful decoding of the first PUSCH transmission. For example, the base station may provide the DCI to the UE to schedule a second PUSCH transmission in time resources overlapping with the first PUSCH transmission. The UE can receive a PDCCH carrying a DCI in the CORESET, and the DCI can instruct the UE to terminate subsequent repetitions of the first PUSCH transmission after a time slot following the CORESET (e.g., no later than T symbols after the last symbol of the CORESET). The DCI can also instruct the UE to transmit a second PUSCH transmission in an uplink time slot following the time slot following the CORESET. In the first or second example, the time slot (e.g., the value of T) can be a function of the PDCCH subcarrier spacing (SCS) and PUSCH SCS, PUSCH processing capacity, whether the first symbol of the PUSCH resource allocation is reserved for the demodulation reference signal (DMRS), and PUSCH preparation time. Additionally, the time slot (T) can include an additional number of symbols Δ (e.g., T = T + Δ) for UE processing margin, the duration of which can be a function of the PDCCH SCS and the PUSCH SCS. For example, the duration of the additional number of symbols Δ can be a function of the smaller SCS between the PDCCH SCS and the PUSCH SCS.

[0032] Several aspects of a telecommunications system will now be given with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0033] As an example, an element, or any part of an element, or any combination of elements, can 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-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc.

[0034] Accordingly, in one or more example embodiments, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored on or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium may be any available medium accessible by a computer. By way of example, and not limitation, such a computer-readable medium may include 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 computer-readable media of the types described above, or any other medium capable of storing computer-executable code in the form of instructions or data structures accessible by a computer.

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

[0036] Base station 102 configured for 4G Long Term Evolution (LTE) (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G New Radio (NR) (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and device tracking, RAN Information Management (RIM), paging, location, and warning message delivery. Base station 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or core network 190) via third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0037] Base station 102 can wirelessly communicate with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. The heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 may use spectrum allocated per carrier up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc.) of bandwidth in carrier aggregation for a total of up to Y x MHz (x component carriers) for transmission in each direction. Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric relative to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0038] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can 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). D2D communication can be achieved through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR, as examples.

[0039] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 (e.g., in an unlicensed spectrum of 5 GHz). When communicating in an unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0040] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) as the unlicensed spectrum used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can improve access network coverage and / or increase access network capacity.

[0041] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the intermediate frequency band (IF). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes arise with FR2; although different from the extremely high frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the “millimeter wave” band in documents and articles.

[0042] In light of the foregoing, unless otherwise specified, it should be understood that the terms "below 6 GHz," if used herein, can broadly refer to frequencies that are less than 6 GHz, within FR1, or may include intermediate frequency bands. Furthermore, unless otherwise specified, it should be understood that the terms "millimeter wave," if used herein, can broadly refer to frequencies that may include intermediate frequency bands, within FR2, or within the EHF band.

[0043] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies when communicating with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Both base station 180 and UE 104 may include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.

[0044] Base station 180 may transmit beamforming signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamforming signals from base station 180 in one or more receive directions 182″. UE 104 may also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 may receive beamforming signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

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

[0046] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and core network 190. Typically, AMF 192 provides Quality of Service (QoS) streaming and session management. All user IP packets are transmitted via UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IMS, packet-switched (PS) streaming service, and / or other IP services.

[0047] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmit-Receive Point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 devices may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or any other suitable term.

[0048] Although this disclosure may focus on 5G NR, the concepts and aspects described herein may be applied to other similar fields, such as LTE, LTE-A Advanced, Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM) or other wireless / radio access technologies.

[0049] Refer again Figure 1 In a particular aspect, UE 104 may include a Physical Uplink Shared Channel (PUSCH) termination component 198, which is configured to: obtain information on configuring uplink data transmission and repetition of uplink data transmission; send uplink data transmission to a base station; and terminate the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition is terminated after a time gap following a CORESET in which the downlink control channel is received.

[0050] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2DFigure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL, or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , Figure 2C In the provided example, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 34 (primarily UL). Although subframes 3 and 4 are shown with slot formats 34 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE configures the slot format via a receive slot format indicator (SFI) (dynamically via DL control information (DCI) or semi-statically / statically via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0051] Other wireless communication technologies may have different frame structures and / or different channels. For example, a 10-millisecond (ms) frame may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may include 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL may be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL may be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios, limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set. For slot configuration 0, different parameter sets μ0 to μ4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter sets 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slots and 2... μ Each time slot / subframe. Subcarrier spacing and symbol length / duration are functions of a parameter set. Subcarrier spacing can be equal to 2. μ*15 kHz, where μ is the parameter set from 0 to 4. Therefore, parameter set μ = 0 has a subcarrier spacing of 15 kHz, and parameter set μ = 4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D Examples are provided for slot configuration 0 with 14 symbols per slot and parameter set μ=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 the frame set, one or more distinct bandwidth portions (BWPs) of frequency division multiplexing may exist (see reference). Figure 2B Each BWP can have a specific set of parameters.

[0052] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) that extends 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0053] like Figure 2A As shown, some REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulated RS (DM-RS) (indicated as an RS for a specific configuration). x (where 100x is the port number, but other DM-RS configurations are possible) and the Channel State Information Reference Signal (CSI-RS) for channel estimation at the UE. The RS may also include Beam Measurement RS (BRS), Beam Refinement RS (BRRS), and Phase Tracking RS (PT-RS).

[0054] Figure 2BExamples of various DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising nine RE Groups (REGs), each REG comprising four consecutive REs in an OFDM symbol. The PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). Additional BWPs can be located at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The UE uses the PSS to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE is able to determine the Physical Cell Identifier (PCI). Based on the PCI, the UE is able to determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides multiple RBs and System Frame Numbers (SFNs) within the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Blocks (SIBs)), and paging messages.

[0055] like Figure 2C As shown, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). SRS can be transmitted in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to implement frequency-dependent scheduling on the UL.

[0056] Figure 2DExamples of various UL channels within a subframe of a frame are shown. The PUCCH can be positioned as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) / negation (NACK) feedback. The PUCCH carries data and may also be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCI.

[0057] Figure 3 This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with upper-layer packet data unit (PDU) transmission, 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 functions associated with 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 priority ordering.

[0058] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM streams are spatially precoded to produce multiple spatial streams. The channel estimate from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. The channel estimate can be derived from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0059] At UE 350, each receiver 354RX receives signals through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them 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 consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements Layer 3 and Layer 2 functions.

[0060] The controller / processor 359 can 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 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0061] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, 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 to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0062] The TX processor 368 can use the channel estimate derived by the channel estimator 358 from the reference signal transmitted by the base station 310 or from feedback to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0063] UL transmissions are processed at base station 310 in a manner similar to the receiver function description at UE 350. Each receiver 318RX receives signals via its corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0064] The controller / processor 375 can 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 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 can be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0065] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 The PUSCH termination component 198 is used to perform various aspects.

[0066] When a base station configures a UE to transmit uplink data in the PUSCH, the base station may instruct the UE to transmit repetitions of its uplink data for coverage enhancement and improved data reliability. For example, the base station may send a PUSCH configuration (e.g., pusch-Config or another name) to the UE via dedicated RRC signaling, which indicates the number of repetitions of uplink data the UE may transmit on the PUSCH in response to dynamic granting (e.g., in the parameter pusch-AggregationFactor or another name). In another example, the base station may send a configured grant configuration (e.g., configuredGrantConfig or another name) to the UE, which indicates the number of repetitions of uplink data the UE may transmit on the PUSCH in response to configured granting (e.g., in the parameter repK or another name). Typically, the UE may be configured to transmit up to sixteen repetitions of PUSCH transmissions in response to dynamic granting, or up to eight repetitions in response to configured granting. However, for example, to further extend PUSCH coverage for Enhanced Mobile Broadband (eMBB) / VoIP, to support low-capacity UEs with extended coverage, or in other cases, the number of repetitions can be increased to sixteen or more. For instance, in rural or some urban areas, downlink channels typically include higher signal quality than uplink channels (e.g., approximately 6-12 dB), and therefore PUSCH repetitions can be used to compensate for this degradation in signal quality.

[0067] Therefore, the UE can send multiple repetitions of its uplink data so that the base station can successfully decode the uplink data. While in some cases (e.g., when the UE is at a considerable distance from the base station, such as at the cell edge), the base station can successfully decode the uplink data after receiving all configured repetitions, in other cases, the base station can successfully decode the data after receiving only some configured repetitions. For example, even if the base station configures the UE to send eight PUSCH repetitions, if the UE is not located at the cell edge or otherwise situated in a geometry with high signal quality, the base station can successfully decode the data after receiving only four PUSCH repetitions (or some other number less than eight).

[0068] However, while NR supports asynchronous hybrid automatic repeat request (HARQ) acknowledgments (ACKs) in response to downlink transmissions (e.g., HARQ-ACK from UE to base station), base stations typically do not provide HARQ-ACK feedback in response to PUSCH transmissions (e.g., HARQ-ACK from base station to UE). Instead, depending on whether the base station successfully decodes uplink data or fails to decode it, the base station can provide downlink control information (DCI) to the UE, indicating whether the UE should retransmit the uplink data in subsequent PUSCH transmissions. For example, if the base station fails to decode the uplink data, it can provide the UE with a DCI instructing the UE to retransmit the uplink data; if the base station successfully decodes the uplink data, it does not provide such a DCI, and the UE assumes the data was successfully received after determining that the base station did not provide such a DCI within a specific time period. Therefore, even if the base station has decoded the uplink data in a previous PUSCH transmission or repetition, the UE may not be certain that the base station has successfully decoded the data until the time period for receiving the DCI has passed, and thus the UE may continue to send unnecessary PUSCH repetitions in between. As a result, the UE wastes transmission power and PUSCH resources on inefficient repetitions. Therefore, allowing the UE to terminate ongoing PUSCH transmissions early (e.g., terminating inefficient repetitions) would be helpful in saving UE power and improving resource efficiency.

[0069] In LTE Enhanced Machine-Type Communications (eMTC), a UE can terminate an ongoing uplink transmission in full-duplex (FD) frequency division duplex (FD-FDD) and time division duplex (TDD) deployments in response to a DCI from the base station. For example, the base station can provide the DCI to the UE in the MTC Physical Downlink Control Channel (MPDCCH), and the DCI can explicitly or implicitly indicate that the base station has successfully decoded a previous uplink transmission. The UE can then terminate the ongoing PUSCH transmission in response to the DCI.

[0070] When the DCI includes one of two DCI formats, the indication can be explicit (used as a valid HARQ-ACK), where the DCI format includes a specific configuration specifying the bit values ​​in the DCI parameters. For example, to explicitly confirm that the base station has successfully decoded an uplink transmission from the UE, the base station can provide the UE with a DCI of format 6-0A, which includes a resource block allocation field set to all 1s and all remaining bits set to zero (except for the format 6-0A / format 6-1A distinction and the DCI subframe repetition count). Alternatively, the base station can provide the UE with a DCI of format 6-0B, which includes a modulation and coding scheme (MCS) field set to all 1s and all remaining bits set to zero (except for the format 6-0B / format 6-1B distinction and the DCI subframe repetition count). On the other hand, the indication can be implicit when the base station schedules a PUSCH transmission that overlaps with a previously scheduled PUSCH transmission or repeats a new PUSCH transport block that overlaps in time. For example, in order to implicitly confirm that the base station has successfully decoded the uplink transmission from the UE, the base station can provide the UE with DCI to schedule a new PUSCH transport block in overlapping time resources.

[0071] When the UE receives a DCI in the MPDCCH in subframe N (which explicitly indicates that the base station has successfully decoded a previous uplink transmission using DCI format 6-0A or 6-0B as described above), the UE may terminate or stop transmitting data on the PUSCH no later than subframe N+k, where k is the number of subframes. For example, k can be 4 subframes for FDD deployment, or k can be a function of the subframe number (or slot number) and the TDD uplink / downlink configuration for TDD deployment (e.g., k = 4, 5, 6, or 7). In response to early decoding of the DCI in the MPDCCH, the UE may terminate PUSCH transmission earlier than subframe N+k. Similarly, when the UE receives a DCI in the MPDCCH in subframe M (which 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 no later than subframe M+k. The UE may, for example, terminate PUSCH transmission earlier than subframe M+k in response to early decoding of the DCI in the MPDCCH. Additionally, the UE may send a new PUSCH transmission in response to a DCI that begins in subframe M+k.

[0072] Figure 4Example 400 illustrates where the UE terminates PUSCH transmission 402 in response to a DCI explicitly indicating successful decoding of the PUSCH transmission. The base station initially provides DCI 404 to the UE in the MPDCCH to schedule the PUSCH transmission; 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. Furthermore, the base station can determine, for example, in response to a buffer status report from the UE or in some other way, that the UE does not have additional data to transmit in its transmission buffer. Therefore, the base station can provide DCI 406 to the UE to explicitly indicate that the PUSCH transmission has been successfully decoded. For example, DCI 406 can have DCI format 6-0A or 6-0B with bit values ​​configured as described above, which does not schedule new PUSCH transmissions. 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 may terminate the PUSCH transmission no later than subframe N+k. For example, the UE may stop transmitting duplicates of its uplink data that began at subframe N+k, as indicated by the terminated PUSCH transmission 408.

[0073] Similarly, Figure 5Example 500 illustrates where the UE terminates the first PUSCH transmission 502 in response to a DCI implicitly indicating successful decoding of the first PUSCH transmission and scheduling a second PUSCH transmission 504. The base station initially provides the UE with a DCI 506 in the MPDCCH to schedule the first PUSCH transmission; 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. Furthermore, the base station can determine, for example, in response to a buffer status report from the UE or in some other way, that the UE has additional data to transmit in its transmission buffer. Therefore, the UE can provide a DCI 508 to the UE to implicitly indicate that the first PUSCH transmission has been successfully decoded. For example, DCI 508 can schedule the second PUSCH transmission 504 in time resources overlapping with the first PUSCH transmission 502. The UE can then terminate its first PUSCH transmission and transmit its second PUSCH transmission in response to DCI 508. For example, assuming the UE receives DCI 508 in subframe M, the UE can terminate the first PUSCH transmission no later than subframe M+k and begin transmitting the second PUSCH transmission that begins in subframe M+k. For example, the UE can stop transmitting repetitions of its first uplink data that begins at subframe M+k (as indicated by the terminated PUSCH transmission 510) and begin transmitting its second uplink data that begins at subframe M+k.

[0074] However, while LTE eMTC can support early termination of PUSCH transmissions based on explicit or implicit feedback as described above, the timelines (subframes N+k and M+k) associated with such terminated PUSCH transmissions may not be maintainable in NR. For example, in contrast to the static TDD configurations supported in LTE (e.g., seven TDD UL / DL configurations 0-6), NR supports dynamic TDD configurations, where the base station can dynamically change the symbol or slot format (e.g., the arrangement of downlink (DL) and uplink (UL) symbols or slots in a subframe). Therefore, an attempt to terminate PUSCH transmissions k subframes after receiving the DCI may fail due to conflicts with the dynamic UL / DL configuration. Furthermore, in contrast to LTE, NR supports different parameter sets between PDCCH and PUSCH (e.g., PDCCH and PUSCH may include different subcarrier spacings (SCS)), and thus different symbol durations between PDCCH and PUSCH. Therefore, if the DCI and terminated PUSCH transmissions are associated with different SCS or symbol durations, the dynamic value of k based on the slot number in TDD deployments or TDDUL / DL configurations, and the fixed value of k in FDD deployments, may be inappropriate. Furthermore, in contrast to LTE, NR supports multiple PUSCH processing capabilities for UEs. For example, after receiving a PDCCH transmission, a UE with PUSCH processing capability 2 can begin transmitting PUSCH in approximately half the time compared to a UE with PUSCH processing capability 1 (e.g., 5 symbols after receiving a DCI for capability 2, assuming a 15kHz SCS, instead of 10 symbols after receiving a DCI for capability 1). Therefore, if the UE has advanced PUSCH processing capabilities, terminating PUSCH transmission k subframes after receiving the DCI would be inefficient.

[0075] Therefore, aspects of this disclosure provide a timeline for terminating PUSCH transmissions, taking into account this timing consideration between NR and LTE. In a first example, the base station may provide a DCI in the PDCCH that explicitly indicates successful decoding of the PUSCH transmission. For example, the DCI may have a DCI format of 0-0 or 0-1, including a Frequency Domain Resource Allocation (FDRA) field or an MCS field 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.) set to zero. The UE may receive 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., no later than T symbols after the last symbol of the CORESET). In a second example, the base station may provide a DCI in the PDCCH that implicitly indicates successful decoding of the first PUSCH transmission. For example, the base station may provide the DCI to the UE to schedule a second PUSCH transmission in time resources overlapping with the first PUSCH transmission. The UE can receive a PDCCH carrying a DCI in the CORESET, and the DCI can instruct the UE to terminate subsequent repetitions of the first PUSCH transmission after a time slot following the CORESET (e.g., no later than T symbols after the last symbol of the CORESET). The DCI can also instruct the UE to transmit a second PUSCH transmission in an uplink time slot following the time slot following the CORESET. In the first or second example, the time slot (e.g., the value of T) can be a function of the PDCCH SCS and PUSCH SCS, PUSCH processing capacity, whether the first symbol of the PUSCH resource allocation is reserved for the demodulation reference signal (DMRS), and the PUSCH preparation time. Additionally, the time slot (T) can include an additional number of symbols Δ for UE processing margin (e.g., T = T + Δ), the duration of which can be a function of the PDCCH SCS and PUSCH SCS. For example, the duration of the additional number of symbols Δ can be a function of the smaller SCS between the PDCCH SCS and PUSCH SCS.

[0076] Therefore, it is possible to terminate PUSCH transmission based on timelines that take into account different timing considerations for NR. For example, here, the termination of PUSCH repetition is based on the CORESET symbol timing reference (including the last symbol of the DCI CORESET), rather than the LTE DCI subframe timing reference (including the end of the DCI subframe). Since the CORESET symbol timing reference is more configurable than the DCI subframe timing reference (in contrast to the fixed end of the subframe, the base station can configure the last symbol of the CORESET to be any symbol of the time slot), greater flexibility in the PUSCH termination start time is achieved. Furthermore, since the base station can configure different SCs, the dynamic CORESET symbol timing reference better accounts for different symbol or time slot durations due to different SCSs compared to the fixed DCI subframe timing reference. Moreover, since the time slot (T) can also be a function of the SCS, PUSCH processing capacity, or other timing configurations (e.g., DMRS), various PUSCH termination start times can be obtained.

[0077] The time slot (T) can be a function of one or more of the following example parameters. In one example, T can be a function of the subcarrier spacing of the PDCCH carrying the DCI and the subcarrier spacing of the PUSCH. For example, if the SCS of both the DCI and PUSCH transmissions is 15 kHz, then T can be one value; if the SCS of both the DCI and PUSCH transmissions is 30 kHz, then T can be another value; if the SCS of the DCI is 15 kHz and the SCS of the PUSCH transmission is 30 kHz, then T can be another value, and so on. Similarly, T can be a function of the subcarrier spacing of the active DL BWP on which the PDCCH is monitored and the subcarrier spacing of the active ULBWP on which the PUSCH is transmitted. For example, if the SCS of both the DL BWP carrying DCI and the UL BWP carrying PUSCH transmission is 15kHz, then T can be one value; if the SCS of both the DL BWP and the UL BWP is 30kHz, then T can be another value; if the SCS of the DL BWP is 15kHz and the SCS of the UL BWP is 30kHz, then T can be another value, and so on. In another example, T can be a function of the UE's PUSCH processing capability. For example, T can be one value for UE PUSCH processing capability 1 and another value for UE PUSCH processing capability 2. In another example, T can be a function indicating whether the first symbol of the PUSCH allocation consists only of DMRS. For example, if the base station configures the first symbol of the PUSCH transmission slot to include only DMRS, then T can be one value; while if the base station configures the first symbol of the PUSCH transmission slot to include only PUSCH data or PUSCH data and DMRS, then T can be another value. In an additional example, T can be the UE PUSCH preparation time T0. proc,2 The function, where T proc,2 It is a function of the PUSCH preparation time N2, where N2 is based on a parameter set μ for UE processing capability 1, where μ corresponds to the parameter that causes the maximum T. proc,2 of (μ) DL μ UL One of (μ) DL μ UL The smaller value between (or SCS), where μ DL The subcarrier interval corresponding to the DCI carrying the scheduling PUSCH that is transmitted, and where μ UL This corresponds to the subcarrier spacing in which the PUSCH is transmitted. For example, the value of T can be different for different values ​​of N2.

[0078] In addition to being a function of one or more of the example parameters mentioned above, a time gap (T) can be added to provide additional UE processing margin. For example, for a low-capacity UE with a large PUSCH preparation time, or for a UE that transmits to multiple base stations simultaneously (e.g., a source base station and a 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 pre-configured as 0, 1, 2, or some other numerical value. In another example, the value of Δ can be indicated to the UE, for example, within the PUSCH configuration. For example, when a base station provides a PUSCH configuration (e.g., pusch-Config) to the UE, the PUSCH configuration can indicate a configured value for Δ (e.g., 0, 1, 2, or some other number of symbols). In yet another example, the value of Δ can depend on the UE's capabilities. For example, if the UE is capable of PUSCH processing capability 2, Δ can be one value, while if the UE is only capable of PUSCH processing capability 1, Δ can be another value. In any example, the duration of Δ can be a function of the SCS of the PDCCH carrying DCI and the SCS of the PUSCH carrying 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 duration of Δ can be one value; if the smaller SCS is 30 kHz, the total duration of Δ can be another value, and so on.

[0079] Figure 6 Example 600 shows a time slot 602 following CORESET 604 in which a PDCCH carrying DCI is received. The UE can receive CORESET 604 in time slot 606 (time slot N). In the example shown, time slot 602 is T = 12 symbols, but in other examples, the time slot can be a different number of symbols depending on the SCS, UE capabilities, or other parameters as described above. Furthermore, in this example, the last symbol 608 of CORESET 604 is the second symbol (symbol 1) of time slot 606, but in other examples, the last symbol 608 of CORESET 604 can be a different symbol in time slot 606. Thus, in the example shown, the UE can terminate subsequent PUSCH repetitions of the previous PUSCH transmission no later than 12 symbols after the second symbol of time slot 606. That is, the UE can stop sending PUSCH transmission repetitions no later than symbol 0 of the subsequent time slot 610 (time slot N+1). Similarly, if the DCI schedules a second PUSCH transmission, the UE can begin transmitting the second PUSCH transmission after time slot 602. For example, the UE can respond to the DCI by starting the second PUSCH transmission from symbol 0 of the subsequent time slot 610.

[0080] Figure 7 Another example 700 is shown, following the time gap 702 after CORESET 704 in which the PDCCH carrying DCI is received. Similar to... Figure 6 For example, the UE can receive CORESET 704 in time slot 706 (time slot N). In the example shown, time slot 702 is T = 13 symbols, but in other examples, depending on the SCS, UE capabilities, or other parameters as described above, the time slot can be of a different number of symbols. Furthermore, similar to... Figure 6 In the example, the last symbol 708 of CORESET 704 is the second symbol (symbol 1) of time slot 706, but in other examples, the last symbol 708 of CORESET 704 can be a different symbol in time slot 706. However, with Figure 6 Unlike the previous example, here time slot 702 ends in the middle of time slot (in this case, the next time slot 710 (time slot N+1)). Therefore, if the UE terminates subsequent PUSCH repetitions after the time slot following CORESET, the termination will begin in the middle of the time slot. To prevent such partial time slot termination, such as... Figure 7 As shown, the UE can delay the termination until the beginning of the subsequent time slot 712 (time slot N+2). As a result, the UE can stop transmitting repeated PUSCH transmissions starting from symbol 0 of the subsequent time slot 712 (time slot N+2) instead of starting from symbol 1 of the next time slot 710 (time slot N+1). Similarly, if the DCI schedules a second PUSCH transmission, the UE can begin transmitting the second PUSCH transmission after time slot 702 and an additional time delay. For example, the UE can respond to the DCI by starting the second PUSCH transmission from symbol 0 of the subsequent time slot 712.

[0081] Figure 8 Another example 800 is shown, following the time gap 802 after CORESET 804 in which the PDCCH carrying DCI is received. Similar to Figure 6 and 7 For example, the UE can receive CORESET 804 in time slot 806 (time slot N). Similarly, Figure 6 In the example, the last symbol 808 of CORESET 804 is the second symbol (symbol 1) of time slot 806, but in other examples, the last symbol 808 of CORESET 804 can be a different symbol in time slot 806. However, with Figure 6 and Figure 7Unlike previous examples, time slot 802 here can include multiple parts, including a first time slot portion 810 (T symbols) and a second time slot portion 812 (Δ symbols), which can be configured separately by the base station. The first time slot portion 810 can correspond to... Figure 6 and 7 Time slots 602 and 702. For example, in the example shown, the first time slot portion 810 is T = 12 symbols, but in other examples, depending on the SCS, UE capabilities, or other example parameters as described above, the first time slot portion can be a different number of symbols. The second time slot portion 812 can be an additional number of symbols used to add UE processing margin. For example, in the example shown, the second time slot portion 812 is Δ = 2 symbols, but in other examples, depending on the PDCCH SCS and PUSCH SCS as described above, the second time slot portion can be a different number of symbols. Additionally, similar to... Figure 7 For example, time slot 802 (including the first time slot portion 810 and the second time slot portion 812) ends in the middle of the time slot (in this case, the next time slot 814 (time slot N+1)). Therefore, if the UE terminates subsequent PUSCH repetitions after a time slot following CORESET, the termination will begin in the middle of the time slot. To prevent such partial time slot termination, such as... Figure 8 As shown, the UE can delay the termination to the beginning of the subsequent time slot 816 (time slot N+2). As a result, the UE can stop transmitting the repetitive PUSCH transmission from symbol 0 of the subsequent time slot 816 (time slot N+2) instead of from symbol 1 of the next time slot 814 (time slot N+1). Similarly, if the DCI schedules a second PUSCH transmission, the UE can begin transmitting the second PUSCH transmission after time slot 802 and the additional time delay. For example, the UE can respond to the DCI by starting the second PUSCH transmission from symbol 0 of the subsequent time slot 816.

[0082] Therefore, the UE can terminate subsequent repetitions of a PUSCH transmission in response to implicitly or explicitly instructing the base station to successfully decode the DCI of a previous PUSCH transmission. A DCI can implicitly indicate successful decoding when it schedules a subsequent uplink transmission within overlapping resources of a previous uplink transmission repetition. A DCI can explicitly indicate successful decoding (effectively used as a HARQ-ACK) when it includes pre-configured bit values ​​in its various DCI format parameters (e.g., DCI format 0_0 or 0_1). Such a DCI used as an explicit HARQ-ACK does not schedule subsequent uplink transmissions.

[0083] Figure 9Example 900 of a DCI used for explicit HARQ-ACK is shown. While the example shown pertains to DCI format 0_0, the DCI format may be different in other examples (e.g., DCI format 0_1). A DCI may include 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 bits of one or more DCI parameters based on a pre-configured bit value (e.g., bit sequence), and configure bits of one or more other DCI parameters based on different pre-configured bit values ​​(e.g., different bit sequences). For example, as... Figure 9 As shown in the example, the base station can configure FDRA 902 or MCS 904 (or both) to include all 1 bits, and configure one or more of the other parameters 906 to include all 0 bits. Alternatively, the base station can configure FDRA or MCS (or both) to include all 0 bits, and configure one or more of the other parameters to include all 1 bits. In other examples, the base station can utilize other bit sequences to configure the FDRA, MCS, or other parameters of the DCI to indicate explicit HARQ-ACK. Therefore, when the UE receives the DCI, the UE can determine that the DCI is used to acknowledge a previous PUSCH transmission, and thus the UE can terminate subsequent repetitions of its previous PUSCH transmission.

[0084] Figure 10 This shows the UE response to CORESET 1004 (e.g., Figure 6-8 Example 1000 shows a DCI (Device Context 604, 704, 804) in CORESET 1004 that explicitly indicates successful decoding of a PUSCH transmission and terminates PUSCH transmission 1002. The base station initially provides DCI 1006 to the UE in the PDCCH to schedule the PUSCH transmission; in response, the UE begins transmitting its uplink data to the base station in PUSCH transmission 1002. While the UE is transmitting its uplink data in one or more repetitions, the base station can successfully decode the PUSCH transmission. Furthermore, the base station can determine, for example, in response to a buffer status report from the UE or in some other way, that the UE does not have additional data to transmit in its transmission buffer. Therefore, the base station can provide DCI 1008 to the UE in CORESET 1004, which explicitly indicates that the PUSCH transmission has been successfully decoded. For example, as mentioned above regarding... Figure 9As described, DCI 1008 may have a DCI format of 0-0 or 0-1, which includes an FDRA field or MCS field set to all 1s, and all remaining bits in one or more other parameters of the DCI (e.g., TDRA, frequency hopping flag, etc.) set to 0. In response to receiving DCI 1008, the UE may terminate its PUSCH transmission after a time gap 1012 (e.g., time gaps 602, 702, 802) following CORESET 1004, which includes DCI 1008, as indicated by terminated PUSCH transmission 1010.

[0085] Figure 11 This shows the UE response to CORESET 1104 (e.g., Figure 6-8 Example 1100 uses the DCI in CORESET 604, 704, 804 to implicitly indicate successful decoding of the first PUSCH transmission and schedule the second PUSCH transmission 1106 to terminate the first PUSCH transmission 1102. The base station initially provides the UE with DCI 1108 in the PDCCH to schedule the first PUSCH transmission, in response to which the UE begins transmitting its uplink data to the base station in the first PUSCH transmission 1102. The base station can successfully decode the first PUSCH transmission while the UE is transmitting its uplink data in one or more repetitions. Furthermore, the base station can determine, for example, in response to a buffer status report from the UE or in some other way, that the UE has additional data to transmit in its transmission buffer. Therefore, the UE can provide DCI 1110 to implicitly indicate that the first PUSCH transmission has been successfully decoded. For example, DCI 1110 can schedule the second PUSCH transmission 1106 in time resources overlapping with the repetition of the first PUSCH transmission 1102. In response to receiving DCI 1110, the UE may terminate its PUSCH transmission (as indicated 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, which includes DCI 1110.

[0086] Figure 12This is example 1200 of a call flow between UE 1202 and base station 1204. The UE may send 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 is capable of having advanced PUSCH processing capabilities (e.g., PUSCH processing capability 2). The base station may provide the UE with a configuration 1208. For example, this configuration may be a PUSCH configuration indicating the number of repetitions of uplink data that the UE may send on the PUSCH in response to dynamic authorization. Alternatively, the configuration may be a configured authorization configuration indicating the number of repetitions of uplink data that the UE may send on the PUSCH in response to configured authorization.

[0087] Subsequently, UE 1202 can receive DCI 1210 for scheduling uplink data transmission 1212 from base station 1204. For example, DCI 1210 can correspond to... Figure 10 or Figure 11 DCI 1006 or DCI 1108 in the above. Similarly, uplink data transmission 1212 can correspond to DCI 1006 or DCI 1108 respectively. Figure 10 or Figure 11 The UE may then transmit uplink data 1212 to the base station, which includes one or more repetitions 1214 of the uplink data transmission as configured by configuration 1208.

[0088] In this example, base station 1204 successfully decodes uplink data transmission 1212 after receiving one or more repetitions of 1214. Therefore, the base station provides UE 1202 with DCI 1216, which explicitly or implicitly indicates that the uplink data transmission was successfully decoded. For example, if the UE does not have additional data to send in its transmission buffer, DCI 1216 could correspond to... Figure 10 DCI 1008 in CORESET 1004. In this case, as mentioned above... Figure 9 The DCI 1216 can have a DCI format of 0-0 or 0-1, which includes one or more bit values ​​configured in its parameters to effectively indicate HARQ-ACK. Alternatively, if the UE has additional data to be transmitted in its transmission buffer, the DCI 1216 can correspond to... Figure 11 DCI 1110 in CORESET 1104. In this case, DCI 1216 can schedule subsequent uplink data transmissions 1218 in time resources that overlap with one or more repetitions 1214.

[0089] At 1220, in response to receiving DCI 1216, UE 1202 can terminate subsequent repetitions of uplink data transmission 1212. For example, if base station 1204 configures the UE to send eight repetitions of uplink data transmission 1212, the base station can successfully decode the data after four repetitions (repetition 1214) and provide DCI 1216 to the UE before the next scheduled repetition. As a result, the UE can suppress the transmission of the remaining four repetitions to the base station, such as those terminated by uplink data repetition 1222 (e.g., respectively). Figure 10 or Figure 11 The termination of PUSCH transmissions 1010 and 1112 is indicated by this. In another example, if the base station successfully decodes uplink data transmission 1212 even before the first configured repetition, the UE can suppress sending eight repetitions to the base station. The UE can do this in a time gap following the CORESET of DCI 1216 (e.g., Figure 6-8 The repetition terminates after time slots 602, 702, 802, 1012, and 1114 (10-11). For example, the time slot can be a function of 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 capability information message 1206, or other factors. Furthermore, if DCI 1216 schedules subsequent uplink data transmission 1218 in overlapping resources with the terminated uplink data repetition 1222, the UE can transmit subsequent uplink data transmissions in the overlapping resources.

[0090] Figure 13 This is a flowchart 1300 of a wireless communication method. This method can be performed by a UE (e.g., UE 104, 350, 1202; device 1402). Optional aspects are shown in dashed lines. This method allows the UE to terminate PUSCH transmission after a time gap following CORESET to account for different timing considerations between NR and LTE.

[0091] At 1302, the UE obtains duplicate information regarding the configuration of uplink data transmission and uplink data transmission. For example, 1302 can be performed by obtaining component 1440. For example, refer to... Figure 12UE 1202 can obtain configuration 1208 from base station 1204, which configures uplink data transmission 1212 and the repetition 1214 of uplink data transmission 1212. For example, this configuration could be a PUSCH configuration indicating the number of repetitions of uplink data that the UE can transmit on the PUSCH in response to dynamic granting. In another example, the configuration could be a granting configuration indicating the number of repetitions of uplink data that the UE can transmit on the PUSCH in response to the granted granting. Therefore, the information obtained could be a PUSCH configuration, a granting configuration, or multiple other configurations for uplink data transmission including uplink data repetition. The information configuring uplink data transmission and the repetition of uplink data transmission could be the same information (e.g., a single configuration) or different information (e.g., different configurations).

[0092] At point 1304, the UE transmits uplink data to the base station. For example, point 1304 can be performed by the transmitting component 1442. For example, refer to... Figure 12 UE 1202 can send uplink data transmission 1212 to base station 1204. UE 1202 can also send one or more repetitions 1214 of uplink data transmission. Uplink data transmission and repetition can be scheduled by DCI 1210.

[0093] Finally, at 1306, the UE terminates the repetition of uplink data transmission in response to receiving downlink information in the downlink control channel. For example, 1306 can be performed by termination component 1444. For example, refer to... Figure 12 At 1220, UE 1202 terminates or suppresses one or more subsequent repetitions of uplink data transmission 1212, as indicated by the terminated uplink data repetition(s)1222. UE may suppress transmission repetitions in response to receiving DCI 1216 in the PDCCH.

[0094] The repetition terminates after the time interval following the CORESET when the downlink control channel is received. For example, refer to Figure 6-8 And 10-12, UE 1202 may terminate its repetition at 1220 after a time gap (e.g. time gap 602, 702, 802, 1012, 1114) following the reception of a PDCCH carrying DCI 1216 (e.g., DCI 1008, 1110) by a CORESET (e.g., CORESET 604, 704, 804, 1004, 1104).

[0095] This time gap can be equal to the length of one or more symbols following the last symbol of the CORESET. For example, refer to... Figure 6The time gap 602 can be equal to the length of 12 symbols (T = 12 symbols) following the last symbol 608 of CORESET 604. In another example, refer to... Figure 7 Time slot 702 can be equal to the length of 13 symbols (T = 13 symbols) following the last symbol 708 of CORESET 704. In other examples, time slots can have different symbol lengths. Additionally, a time slot can end during the slot, and the termination at 1306 can begin in the initial symbol of a subsequent time slot. For example, see Reference... Figure 7 and Figure 8 Time slots 702 and 802 may end during the next time slots 710 and 814 (time slot N+1), and the terminated PUSCH transmission (e.g., Figure 12 The termination of (multiple) uplink data repeats (1222) can begin in symbol 0 of subsequent time slots 712, 816 (time slot N+2).

[0096] Downlink information can indicate HARQ-ACK. In this example, downlink information may include FDRA, MCS, and other parameters, and HARQ-ACK can be indicated by a first pre-configured bit value for FDRA or MCS and a second pre-configured bit value for other parameters. The second pre-configured bit value may differ from the first pre-configured bit value. For example, refer to... Figure 10 and 12 DCI 1008 and 1216 can explicitly indicate that uplink data transmission 1212 or (multiple) repeating 1214 has been successfully decoded. For example, as mentioned above... Figure 9 As described, DCIs 1008 and 1216 can have a DCI format of 0-0 or 0-1, which includes one or more bit values ​​configured in their parameters to effectively indicate HARQ-ACK. As an example, FDRA 902 or MCS 904 of the DCI can be set to all 1s, while other parameters 906 of the DCI can be set to all 0s. For example, if the UE does not have additional data to send in its transmission buffer, base station 1204 can provide this DCI.

[0097] Downlink information can be used to schedule subsequent uplink data transmissions after a time gap. For example, refer to... Figure 11 and 12DCI 1110, 1216 can implicitly indicate that uplink data transmission 1212 or (multiple) repetitions 1214 has been successfully decoded. For example, DCI 1216 can schedule subsequent uplink data transmission 1218 in time resources overlapping with one or more repetitions 1214 after time slots 602, 702, 802, 1114. Furthermore, time slots can end during a time slot, and subsequent uplink data transmission can begin in the initial symbol of a subsequent time slot. For example, refer to... Figure 8 Time slot 802 can end during the next time slot 814 (time slot N+1), and subsequent PUSCH transmissions (e.g., Figure 12 Subsequent uplink data transmission (1218) can begin in symbol 0 of subsequent time slot 816 (time slot N+2).

[0098] The time slot can be a function of the first SCS of the PDCCH carrying downlink information and the second SCS of the PUSCH carrying uplink data transmission. For example, refer to Figure 6-8 The time intervals 602, 702, 802, 1012, and 1114(T) can be functions of the subcarrier spacing of the PDCCH carrying DCI 1008, 1110, and 1216, and the subcarrier spacing of the PUSCH carrying uplink data transmission 1212 or (multiple) repeats of 1214. For example, if the SCS of both the DCI and PUSCH transmissions is 15 kHz, then T can be one value; if the SCS of both the DCI and PUSCH transmissions is 30 kHz, then T can be another value; if the SCS of the DCI is 15 kHz and the SCS of the PUSCH transmission is 30 kHz, then T can be another value, and so on.

[0099] The time slot 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, refer to Figure 6-8 The time intervals 602, 702, 802, 1012, and 1114(T) can be functions of the subcarrier spacing of the active DL BWP monitored carrying DCI 1008, 1110, and 1216 on it, and the subcarrier spacing of the active UL BWP carrying uplink data transmission 1212 or (multiple) repeats 1214 on it. For example, if the SCS of both the DL BWP carrying DCI and the UL BWP carrying PUSCH transmission is 15 kHz, then T can be one value; if the SCS of both the DL BWP and the UL BWP is 30 kHz, then T can be another value; if the SCS of the DL BWP is 15 kHz and the SCS of the UL BWP is 30 kHz, then T can be another value, and so on.

[0100] The time slot can be a function of the UE's PUSCH processing capability. For example, refer to... Figure 6-8 And 10-12, time intervals 602, 702, 802, 1012, 1114(T) can be functions of the UE's PUSCH processing capability. For example, T can be one value for UE PUSCH processing capability 1 and another value for UE PUSCH processing capability 2. The UE's PUSCH processing capability can be, for example, in Figure 12 The capability information message 1206 indicates this.

[0101] This time interval is a function that indicates whether the first symbol of uplink data transmission is reserved for DMRS configuration. For example, refer to... Figure 6-8 And 10-12, time slots 602, 702, 802, 1012, 1114(T) can be functions indicating whether the first symbol of the PUSCH allocation for uplink data transmission 1212 or (multiple) repetitions 1214 consists only of DMRS (e.g., configuration 1208 or a different configuration). For example, if the base station configures the first symbol of the PUSCH transmission time slot to include only DMRS, then T can be one value, while if the base station configures the first symbol of the PUSCH transmission time slot to include only PUSCH data or includes both PUSCH data and DMRS, then T can be another value.

[0102] The time gap can be a function of the PUSCH preparation time. For example, refer to... Figure 6-8 And 10-12, time intervals 602, 702, 802, 1012, 1114(T) can be the UE PUSCH preparation time T. proc,2 The function, where T proc,2 It is a function of the PUSCH preparation time N2, where N2 is based on the parameter set μ for UE processing capability 1, where μ corresponds to the parameter that causes the maximum T. proc,2 of (μ) DL μ UL One of (μ) DL μ UL The smaller value between (or SCS), where μ DL The subcarrier interval corresponding to the DCI carrying the scheduling PUSCH that is transmitted, and where μ UL This corresponds to the subcarrier interval to which its PUSCH will be transmitted. For example, the value of T can be different for different values ​​of N2.

[0103] The time interval can include multiple individual configurable parts. For example, reference Figure 8Time slot 802 may include multiple parts, including a first time slot portion 810 (T symbols) and a second time slot portion 812 (Δ symbols), which can be configured separately by the base station. One of the separately configurable portions (e.g., the second time slot portion 812) may be pre-configured (e.g., fixed), indicated in the PUSCH configuration (e.g., configuration 1208 or a different configuration), or dependent on the UE capability. For example, in one example, the value of Δ may be fixed as 0, 1, 2, or some other numerical value. In another example, the base station may dynamically indicate the value of Δ to the UE within the PUSCH configuration (e.g., 0, 1, 2, or some other number of symbols). In yet another example, the value of Δ may depend on the UE capability. For example, if the UE is capable of having PUSCH processing capability 2, then Δ may be one value, while if the UE is only capable of having PUSCH processing capability 1, then Δ may be another value.

[0104] Additionally, one of the individually configurable portions (e.g., the second time gap portion 812) can be a function of the first SCS of the PDCCH carrying downlink information and the second SCS of the PUSCH carrying uplink data transmission. For example, the duration of Δ can be a function of the SCS of the PDCCH carrying DCI 1216 and the SCS of the PUSCH carrying uplink data transmission 1212 or (multiple) repetitions 1214 (e.g., the smaller SCS between the PDCCH SCS and the PUSCH SCS). For example, if the smaller SCS is 15 kHz, the total duration of Δ can be one value; if the smaller SCS is 30 kHz, the total duration of Δ can be another value, and so on.

[0105] Figure 14Figure 1400 illustrates an example of a hardware implementation of device 1402. Device 1402 is a UE and includes a cellular baseband processor 1404 (also referred to as a modem) coupled to a cellular RF transceiver 1422 and one or more Subscriber Identity Module (SIM) cards 1420, an application processor 1406 coupled to a Secure Digital Card (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 BS 102 / 180 via the cellular RF transceiver 1422. The cellular baseband processor 1404 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 1404 is responsible for general processing, including executing software stored on the computer-readable media / memory. The software, when executed by the cellular baseband processor 1404, causes the cellular baseband processor 1404 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1404 during software execution. The cellular baseband processor 1404 also includes a receiving component 1430, a communication manager 1432, and a transmitting component 1434. The communication manager 1432 includes one or more of the components shown. The components within the communication manager 1432 may be stored in a 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 TX processor 368, the RX processor 356, and the controller / processor 359 and / or memory 360. In one configuration, the device 1402 may be a modem chip and include only the baseband processor 1404, while in another configuration, the device 1402 may be the entire UE (e.g., see...). Figure 3 (350) and includes the aforementioned additional module of device 1402.

[0106] The communication manager 1432 includes an acquisition component 1440, which is configured to acquire repeated information configuring uplink data transmission and uplink data transmission, such as as described in conjunction with 1302. Figure 15A Example 1500 illustrates a process or algorithm executed by the acquisition component 1440. The acquisition component may be implemented in, for example, an RX processor 356. At 1502, the acquisition component 1440 receives information. For example, refer to... Figure 3 The receiving component 1440 can receive signals carrying information from the base station 310 via one or more corresponding antennas 352. Then, at 1504, the receiving component 1440 decodes the received information. For example, refer to... Figure 3The receiving component can demodulate the received information based on the modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.).

[0107] The communication manager 1432 also includes a transmitting component 1442, which, for example, as described in conjunction with 1304, receives input in the form of information from the receiving component 1440 and is configured to transmit uplink data to the base station. Figure 15B Example 1520 illustrates a process or algorithm executed by transmitting component 1442. The transmitting component may be implemented in, for example, a TX processor 368. At 1522, transmitting component 1442 encodes uplink data. For example, refer to... Figure 3 The transmitting component 1442 can modulate the uplink data based on a modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.). Then, at 1524, the transmitting component 1442 transmits the encoded uplink data. For example, refer to... Figure 3 The transmitting component can transmit encoded uplink data to the base station 310 through one or more corresponding antennas 352.

[0108] The communication manager 1432 also includes a termination component 1444, which, for example, as described in conjunction with 1306, receives input in the form of information from the acquisition component 1440 and is configured to terminate the repetition of uplink data transmission in response to receiving downlink information in the downlink control channel. Figure 15C Example 1540 illustrates a process or algorithm executed by termination component 1444. The termination component may be implemented in, for example, a controller / processor 359. At 1542, termination component 1444 receives downlink information. For example, refer to... Figure 3 Termination component 1444 can receive DCI from RX processor 356 (or acquisition component 1440 of RX processor 356). For example, acquisition component 1440 in RX processor 356 can receive a signal carrying a PDCCH payload including DCI from base station 310 via one or more corresponding antennas 352, demodulate the PDCCH payload based on a modulation scheme (e.g., BPSK, QPSK, M-PSK, M-QAM, etc.), and provide the demodulated PDCCH payload including DCI to termination component 1444 in controller / processor 359. Termination component 1444 can then decode the demodulated PDCCH payload to receive DCI. Subsequently, at 1544, termination component 1444 suppresses transmission duplication in response to received downlink information. For example, refer to Figure 3 Termination component 1444 can stop the delivery of uplink data duplicates to TX processor 368 (or TX processor's transmission component 1442).

[0109] The apparatus may include the ability to perform Figure 13 and Figure 15A -C is an additional component of each block of the algorithm in the aforementioned flowchart. Thus, Figure 13 and Figure 15A Each block in the aforementioned flowchart of -C can be executed by a component, and the apparatus can include one or more of those components. A component can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0110] In one configuration, apparatus 1402, particularly cellular baseband processor 1404, includes: components for obtaining information configuring uplink data transmission and repetition of uplink data transmission; components for transmitting uplink data transmission to a base station; and components for terminating the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel. The repetition terminates after a time gap following a CORESET in which the downlink control channel is received.

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

[0112] In one configuration, a time slot can end during the time slot, and termination can begin in the initial symbol of a subsequent time slot.

[0113] In one configuration, downlink information can indicate HARQ-ACK. In another configuration, downlink information may include FDRA, MCS, and other parameters, and HARQ-ACK may 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 being different from the first pre-configured bit value.

[0114] In one configuration, downlink information can be scheduled for subsequent uplink data transmission after the time slot. In another configuration, the time slot can end during the slot, and subsequent uplink data transmission can begin in the initial symbol of the subsequent time slot.

[0115] In one configuration, the time slot can be a function of the first SCS of the PDCCH carrying downlink information and the second SCS of the PUSCH carrying uplink data transmission.

[0116] In one configuration, the time slot can be a function of the first SCS of the downlink BWP that includes the PDCCH and the second SCS of the uplink BWP that includes the PUSCH.

[0117] In one configuration, the time interval can be a function of the UE's PUSCH processing capability.

[0118] In one configuration, the time slot can be a function that indicates whether the first symbol of uplink data transmission is reserved for the configuration of DMRS.

[0119] In one configuration, the time interval can be a function of the PUSCH preparation time.

[0120] In one configuration, the time slot may include multiple individually configurable portions. In one configuration, one of the individually configurable portions is pre-configured, indicated in the PUSCH configuration, or depends on UE capabilities. In one configuration, one of the individually configurable portions may be a function of a first SCS of the PDCCH carrying downlink information and a second SCS of the PUSCH carrying uplink data transmission.

[0121] The aforementioned components may be one or more of the aforementioned components of device 1402 configured to perform the functions described by the aforementioned device. As described above, device 1402 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned device may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described by the aforementioned components.

[0122] If the base station has already decoded uplink data in a previous PUSCH transmission or repetition, the UE may continue to transmit unnecessary PUSCH repetitions due to the general lack of HARQ feedback for PUSCH in the NR. As a result, the UE may waste transmission power and PUSCH resources on inefficient repetitions. To address this power waste and inefficiency, the base station can provide the UE with a DCI that explicitly or implicitly indicates whether a previous PUSCH transmission was successfully decoded, and the UE can terminate ongoing PUSCH transmissions early (e.g., terminate inefficient repetitions). Thus, reduced UE power and enhanced resource efficiency can be achieved. Furthermore, the UE can terminate PUSCH transmissions after a time gap (T symbols) following the CORESET of the PDCCH carrying the DCI, instead of several subframes (k subframes) after the subframe containing the DCI. The time gap can be a function of various parameters, such as the PDCCH SCS (or DL ​​BWP SCS), PUSCH SCS (or UL BWP SCS), UE PUSCH processing capacity, DMRS configuration, or PUSCH preparation time. Such configurable timing can accommodate and minimize conflicts with various timing configurations existing in NR (e.g., dynamic TDD, different parameter sets (numerology) between PDCCH and PUSCH, and multiple PUSCH processing capabilities). Furthermore, time slots can be divided into separately configurable portions, one of which can also be a function of the PDCCH SCS and PUSCH SCS. Such configured portions can provide additional UE processing headroom for low-capacity UEs, while similarly considering the various timing configurations existing in NR as described above.

[0123] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowchart is illustrative of the exemplary method. Based on design preferences, it should be understood that the specific order or hierarchy of the boxes in the process / flowchart can be rearranged. Furthermore, some boxes can be combined or omitted. The appended method claims present the elements of the boxes in a sample order and are not intended to limit one to the specific order or hierarchy presented.

[0124] The preceding 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 apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to limit them to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, references to singular elements are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “while,” should be interpreted as indicating “under this condition,” rather than implying an immediate temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to or during the occurrence of an action, but simply imply that an action will occur if a condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless otherwise specifically stated, the term “some” means 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", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. 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", and "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 and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms "module", "mechanism", "element", "device", etc., may not be a substitute for the term "part". Therefore, no claim element should be interpreted as a device plus a function unless the element is explicitly stated using the phrase "a device for...".

[0125] The following examples are merely illustrative and may be combined with other examples or aspects of the teachings described herein, and are not limited thereto.

[0126] Example 1 is a method for wireless communication at a user equipment (UE), comprising: obtaining information configuring uplink data transmission and repetition of uplink data transmission; sending uplink data transmission to a base station; and terminating the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition terminates after a time gap following the receipt of the control resource set (CORESET) of the downlink control channel.

[0127] Example 2 is the method as described in Example 1, wherein the time gap is equal to the length of one or more symbols following the last symbol of CORESET.

[0128] Example 3 is a method as described in any one of Examples 1 and 2, wherein the time gap ends during the time gap and the termination begins in the initial symbol of the subsequent time gap.

[0129] Example 4 is a method as described in any one of Examples 1 to 3, wherein the downlink information indicates a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK).

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

[0131] Example 6 is a method as described in any one of Examples 1 to 3, wherein the downlink information is scheduled for subsequent uplink data transmission after a time gap.

[0132] Example 7 is the method as described in Example 6, wherein the time slot ends during the time slot and subsequent uplink data transmission begins in the initial symbol of the subsequent time slot.

[0133] Example 8 is a method as described in any one of Examples 1 to 7, wherein the time slot is a function of the first subcarrier spacing (SCS) of the physical downlink control channel (PDCCH) carrying downlink information and the second SCS of the physical uplink shared channel (PUSCH) carrying uplink data transmission.

[0134] Example 9 is a method as described in any one of Examples 1 to 8, wherein the time slot is a function of a first subcarrier spacing (SCS) of the downlink bandwidth portion (BWP) including the physical downlink control channel (PDCCH) and a second SCS of the uplink BWP including the physical uplink shared channel (PUSCH).

[0135] Example 10 is a method as described in any one of Examples 1 to 9, wherein the time slot is a function of the UE's Physical Uplink Shared Channel (PUSCH) processing capability.

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

[0137] Example 12 is a method as described in any one of Examples 1 to 11, wherein the time gap is a function of the Physical Uplink Shared Channel (PUSCH) preparation time.

[0138] Example 13 is a method as described in any one of Examples 1 to 12, wherein the time interval comprises a plurality of individually configurable portions.

[0139] Example 14 is a method as described in Example 13, wherein one of the individual configurable parts is pre-configured, indicated in the Physical Uplink Shared Channel (PUSCH) configuration, or depends on the UE capability.

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

[0141] Example 16 is an apparatus for wireless communication, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory, the instructions being operable, when executed by the processor, to cause the apparatus to: obtain information configuring uplink data transmission and repetition of uplink data transmission; transmit uplink data transmission to a base station; and terminate the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition terminates after a time gap following the receipt of the control resource set (CORESET) of the downlink control channel.

[0142] Example 17 is an apparatus as described in Example 16, wherein the time gap is equal to the length of one or more symbols following the last symbol of CORESET.

[0143] Example 18 is an apparatus as described in any one of Examples 16 and 17, wherein the downlink information indicates a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK).

[0144] Example 19 is an apparatus as described in any one of Examples 16 and 17, wherein the downlink information is scheduled for subsequent uplink data transmission after a time gap.

[0145] Example 20 is an apparatus as described in any one of Examples 16 to 19, wherein the time slot is a function of a first subcarrier spacing (SCS) of the physical downlink control channel (PDCCH) carrying downlink information and a second SCS of the physical uplink shared channel (PUSCH) carrying uplink data transmission.

[0146] Example 21 is an apparatus as described in any one of Examples 16 to 20, wherein the time slot is a function of a first subcarrier spacing (SCS) of the downlink bandwidth portion (BWP) including the physical downlink control channel (PDCCH) and a second SCS of the uplink BWP including the physical uplink shared channel (PUSCH).

[0147] Example 22 is an apparatus as described in any one of Examples 16 to 21, wherein the time slot is a function of the UE's Physical Uplink Shared Channel (PUSCH) processing capability.

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

[0149] Example 24 is an apparatus as described in any one of Examples 16 to 23, wherein the time gap is a function of the Physical Uplink Shared Channel (PUSCH) preparation time.

[0150] Example 25 is an apparatus as described in any one of Examples 16 to 24, wherein the time interval comprises a plurality of individually configurable portions.

[0151] Example 26 is an apparatus as described in Example 25, wherein one of the separately configurable parts is a function of a first subcarrier spacing (SCS) of the physical downlink control channel (PDCCH) carrying downlink information and a second SCS of the physical uplink shared channel (PUSCH) carrying uplink data transmission.

[0152] Example 27 is an apparatus for wireless communication, comprising: components for obtaining information configuring uplink data transmission and repetition of uplink data transmission; components for transmitting uplink data transmission to a base station; and components for terminating the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition terminates after a time gap following the receipt of the control resource set (CORESET) of the downlink control channel.

[0153] Example 28 is an apparatus as described in Example 27, wherein the downlink information indicates a Hybrid Automatic Repeat Request (HARQ) Acknowledgment (HARQ-ACK).

[0154] Example 29 is an apparatus as described in Example 27, wherein the downlink information is scheduled for subsequent uplink data transmission after a time gap.

[0155] Example 30 is a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to: obtain information configuring uplink data transmission and repetition of uplink data transmission; send uplink data transmission to a base station; and terminate the repetition of uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition terminates after a time gap following the receipt of the control resource set (CORESET) of the downlink control channel.

Claims

1. A method of wireless communication at a user equipment (UE), comprising: obtaining information configuring an uplink data transmission and a repetition of the uplink data transmission; transmitting the uplink data transmission to a base station; and terminating the repetition of the uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition is terminated after a time gap after a control resource set (CORESET) in which the downlink control channel is received, wherein the downlink information indicates a hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK), and wherein 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. the time gap is equal to a length of one or more symbols after a last symbol of the CORESET.

2. The method of claim 1, wherein, the time gap ends during a slot and the terminating begins in an initial symbol of a subsequent slot.

3. The method of claim 1, wherein, the downlink information schedules a subsequent uplink data transmission after the time gap.

4. The method of claim 1, wherein, the time gap ends during a slot and the subsequent uplink data transmission begins in an initial symbol of a subsequent slot.

5. The method of claim 4, wherein, the time gap is a function of a first sub-carrier 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.

6. The method of claim 1, wherein, the time gap is a function of a first sub-carrier 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).

7. The method of claim 1, wherein, the time gap is a function of a UE physical uplink shared channel (PUSCH) processing capability.

8. 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).

9. The method of claim 1, wherein, the time gap is a function of a physical uplink shared channel (PUSCH) preparation time.

10. The method of claim 1, wherein, the time gap includes a plurality of individually configurable portions.

11. The method of claim 1, wherein, one of the individually configurable portions is preconfigured, indicated in a physical uplink shared channel (PUSCH) configuration, or dependent on a UE capability.

12. The method of claim 11, wherein, one of the individually configurable portions is a function of a first sub-carrier 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.

13. The method of claim 11, wherein, 14. An apparatus for wireless communication, comprising: a processor; a memory coupled with the processor; and instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to: obtain information configuring an uplink data transmission and a repetition of the uplink data transmission; transmit the uplink data transmission to a base station; and ​ terminating the repetition of the uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition is terminated after a time gap after a control resource set, CORESET, in which the downlink control channel is received, wherein the downlink information indicates a hybrid automatic repeat request, HARQ, acknowledgement, HARQ-ACK, and wherein the downlink information comprises 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.

15. The apparatus of claim 14, wherein, the time gap is equal to a length of one or more symbols after a last symbol of the CORESET.

16. The apparatus of claim 14, wherein, the downlink information schedules a subsequent uplink data transmission after the time gap.

17. The apparatus of claim 14, wherein, the time gap is a function of a first sub-carrier 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.

18. The apparatus of claim 14, wherein, the time gap is a function of a first sub-carrier 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.

19. The apparatus of claim 14, wherein, the time gap is a function of a UE physical uplink shared channel, PUSCH, processing capability.

20. The apparatus of claim 14, 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.

21. The apparatus of claim 14, wherein, the time gap is a function of a physical uplink shared channel, PUSCH, preparation time.

22. The apparatus of claim 14, wherein, the time gap comprises a plurality of individually configurable parts.

23. The apparatus of claim 22, wherein, one of the individually configurable parts is a function of a first sub-carrier 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.

24. An apparatus for wireless communication, comprising: means for obtaining information configuring an uplink data transmission and a repetition of the uplink data transmission; means for transmitting the uplink data transmission to a base station; and means for terminating the repetition of the uplink data transmission in response to receiving downlink information in a downlink control channel, wherein the repetition is terminated after a time gap after a control resource set, CORESET, in which the downlink control channel is received, wherein the downlink information indicates a hybrid automatic repeat request, HARQ, acknowledgement, HARQ-ACK, and wherein the downlink information comprises 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. the time gap is equal to a length of one or more symbols after a last symbol of the CORESET. the downlink information schedules a subsequent uplink data transmission after the time gap. the time gap is a function of a first sub-carrier 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. the time gap is a function of a first sub-carrier 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. the time gap is a function of a UE physical uplink shared channel, PUSCH, processing capability. 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. the time gap is a function of a physical uplink shared channel, PUSCH, preparation time. the time gap comprises a plurality of individually configurable parts. one of the individually configurable parts is a function of a first sub-carrier 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.

25. The apparatus of claim 24, wherein, The downlink information schedules a subsequent uplink data transmission after a time gap.

26. A computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to: obtain information configuring an uplink data transmission and repetitions of the uplink data transmission; transmit the uplink data transmission to a base station; and terminate the repetitions of the uplink data transmission in response to receiving downlink information in a downlink control channel, wherein terminate after a time gap after a control resource set (CORESET) in which the downlink control channel is received, wherein the downlink information indicates a hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK), and wherein 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.

Images