CN112400291B - Apparatus and method for scheduling Physical Uplink Shared Channel (PUSCH) - Google Patents

Abstract

An apparatus, comprising: a memory to store Downlink Control Information (DCI) to schedule a second Physical Uplink Shared Channel (PUSCH) transmission overlapping one or more repetitions of the PUSCH transmission for a specified hybrid automatic repeat request (HARQ) process for a User Equipment (UE); and processing circuitry, coupled to the memory, for: retrieving DCI from a memory; generating a message including DCI; and encoding the message for transmission to the UE.

Description

Apparatus and method for scheduling Physical Uplink Shared Channel (PUSCH)

RELATED APPLICATIONS

The present application claims priority from U.S. provisional patent application Ser. No. 62/739,042, entitled "System and method for repeated termination of PUSCH in NR", filed on 28, 9, 2018, and U.S. provisional patent application Ser. No. 62/808,728, entitled "SYSTEM AND METHODS ON PUSCH REPETITION TERMINATION IN NR (System and method for repeated termination of PUSCH in NR)", filed on 21, 2, 2019, the entire disclosures of which are incorporated herein by reference.

Background

Embodiments described herein are directed to termination of Physical Uplink Shared Channel (PUSCH) transmission repetition, and the like. Embodiments of the present disclosure may be used in conjunction with transmissions for New Radios (NRs).

Drawings

The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To aid in this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

Fig. 1, 2, and 3 illustrate examples of operational flow/algorithm structures in accordance with certain embodiments.

Fig. 4 depicts an architecture of a network system in accordance with certain embodiments.

Fig. 5 depicts an example of components of a device in accordance with certain embodiments.

Fig. 6 depicts an example of an interface of baseband circuitry in accordance with some embodiments.

Fig. 7 depicts a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, in accordance with certain embodiments.

Detailed Description

Embodiments discussed herein may relate to termination of Physical Uplink Shared Channel (PUSCH) transmission repetition for a New Radio (NR). Other embodiments may be described and/or claimed.

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular architecture, architectures, interfaces, techniques, etc., in order to provide a thorough understanding of the various aspects of the claimed invention. However, it will be apparent to one having ordinary skill in the art having had the benefit of the present disclosure that the various aspects of the invention claimed may be practiced in other examples that depart from these specific details. In some instances, descriptions of well known devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

Various aspects of the illustrative embodiments will be described using terms commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. However, it will be apparent to those skilled in the art that alternative embodiments may be practiced using only some of the described aspects. For purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the illustrative embodiments. However, it will be apparent to one skilled in the art that the alternative embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrative embodiments.

Further, various operations will be described as multiple discrete operations in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.

The phrases "in various embodiments," "in certain embodiments," and the like may refer to the same or different embodiments. The terms "comprising," "having," and "including" are synonymous, unless the context indicates otherwise. The phrase "a and/or B" means (a), (B) or (a and B). The phrases "a/B" and "a or B" mean (a), (B) or (a and B), similar to the phrase "a and/or B". For the purposes of this disclosure, the phrase "at least one of a and B" means (a), (B), or (a and B). The description may use the phrases "in one embodiment," "in embodiments," "in certain embodiments," and/or "in various embodiments," each of which may refer to one or more of the same or different embodiments. Furthermore, the terms "comprising," "including," "having," and the like, as used with respect to embodiments of the present disclosure, are synonymous.

Examples of embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel, together, or concurrently. In addition, the order of the operations may be rearranged. A process may terminate when its operation is complete, but may also have additional steps not included in the figure(s). A process may correspond to a method, a function, a procedure, a subroutine, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function and/or the main function.

Examples of embodiments may be described in the general context of computer-executable instructions, such as program code, software modules, and/or functional processes, being executed by one or more of the circuits described above. Program code, software modules and/or functional processes may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular data types. The program code, software modules and/or functional processes discussed herein may be implemented using existing hardware in existing communication networks. For example, the program code, software modules and/or functional processes discussed herein may be implemented using existing hardware at existing network elements or control nodes.

Mobile communications have evolved from early voice systems to today's highly complex integrated communication platforms. The next generation wireless communication system 5G or New Radio (NR) will enable various users and applications to access information and share data anytime and anywhere. NR is expected to be a unified network/system that aims to meet distinct and sometimes conflicting performance dimensions and services. Such different multi-dimensional requirements are driven by different services and applications. Typically, NR will evolve based on 3GPP LTE-Advanced and other potential new Radio Access Technologies (RATs), enriching people's lives with better, simple and seamless radio connection solutions. NR will enable everything to be interconnected in a wireless manner and provide fast, rich content and services.

Repetition of scheduling by dynamic grant or configuration grant may be terminated by dynamic grant for the same Transport Block (TB):

some agreements to be considered include:

For a UE configured with K repetitions of TB transmission using grant/no-use grant, the UE can continue the repetition of the TB (FFS may be different RV versions, FFS different MCS) until one of the following conditions is met

If the UL grant is successfully received for a slot/minislot (slot/mini-slot) of the same TB

The number of repetitions of the TB reaches K

Embodiments of the present disclosure are directed to introducing processing time to cancel in-progress repetition (e.g., in accordance with the agreement noted above), and the like. In addition, when applied in a Physical Uplink Shared Channel (PUSCH) carrying a grant confirmation of a Medium Access Control (MAC) Control Element (CE) configuration, consider a cancellation rule in case of a transmission direction conflicting with a dynamic Slot Format Indication (SFI).

In addition, for the case of repeated termination by dynamic grant (with different HARQ process IDs), such behavior is not currently defined in L1 when both the configuration grant and dynamic grant PESCH are generated by the MAC layer. Embodiments of the present disclosure may also address this problem by applying PUSCH termination. Furthermore, in case different HARQ processes are used for the CG PUSCH in progress and the scheduled overlapping dynamic PUSCH, similar repetition termination behavior may be applied.

Terminating repeated application time

As noted above, the repetition scheduled by the dynamic grant or the configuration grant may be terminated by the dynamic grant for the same TB. However, there is still no assumption about the processing time generated. When it is desired to terminate an already planned/prepared PUSCH transmission from a UE, a hypothetical processing time is required.

In one embodiment, after "m" symbols counted from the symbol after the last symbol of CORESET, the UE is not expected to continue repetition of dynamically triggered or configured PUSCH transmissions, wherein the DCI format 0_0 or 0_1 scheduled PUSCH transmissions overlap with ongoing/scheduled repetitions, and wherein the DCI is addressed to the same HARQ process ID as the ongoing/scheduled repetition. The value "m" is N2 symbols, where N2 is the minimum UE processing time for PUSCH preparation corresponding to a specified processing capability, and is further defined based on one or more of: a subcarrier spacing (SCS) of the scheduling PDCCH, and an SCS of the scheduled or planned PUSCH. Furthermore, it is not desirable that the UE continue to repeat from the earliest repetition after "m" symbols, i.e., the UE does not terminate part of PUSCH.

Alternatively, explicit application times may not be introduced. In contrast, the specified PUSCH scheduling has experienced an N2 processing time, where the slot offset K2 and the starting symbol of the PUSCH in the scheduling grant are always such that a minimum PUSCH preparation time (N2 symbols for the specified digital term (numerology) (e.g., subcarrier spacing (SCS)) is guaranteed between the end of the PDCCH carrying the UL grant and the start of the CP of the earliest UL symbol for PUSCH transmission, termination may be done in the MAC layer. The MAC layer currently models the repetition as a separate MAC grant. Thus, in this case, if there is a dynamic grant addressed to the same HARQ process delivered to the MAC layer that overlaps with a bundled transmission other than the first one of the bundled transmissions (bundle), the remaining bundled transmissions are discarded. In other words, the UE should skip the repetition corresponding to the HARQ process starting from the repetition corresponding to the time domain resource indicated for PUSCH transmission via another valid UL grant for the same HARQ process. Here, the concept of "valid UL grant" means that the UL grant indicates a slot offset (offset from a scheduled PDCCH) and a start symbol for PUSCH transmission, thereby ensuring a minimum UE processing time for PUSCH preparation.

Note that although in the above embodiments and examples, the time gap is described in symbol units and with respect to N2 symbols as PUSCH preparation time for simplicity, in detail, this means that the time gap between the end of the last symbol of the PDCCH carrying DCI scheduling PUSCH and the start of the CP of the earliest UL symbol from which PUSCH repetition may be cancelled is at least T _proc,2 (milliseconds) — where T _proc,2 is as defined in section 6.4 of 3GPP Technical Specification (TS) 38.214, v15.2.0, 2018-06-29.

Further, in embodiments, in the case of a dynamically scheduled ("grant-based") PUSCH with multi-slot transmission, the UE may be expected to terminate the remaining repetition after receiving another UL grant for the same HARQ process only when the NDI bit field is switched.

Further, in an embodiment, as part of the capability reporting framework, the UE indicates whether the UE supports a function to cancel one or more repetitions of PUSCH, wherein slot aggregation is configured for dynamically scheduled PUSCH as described above, or repK >1 is configured for CG PUSCH based on subsequent UL grants. In another example, capabilities may be indicated for dynamically scheduled (grant-based) PUSCH and type 1 and 2CG PUSCHs, respectively. The capability may be further reported on a per UE basis or on a per band, per band combination.

Canceling configured licensed PUSCH due to dynamic SFI

Another aspect of embodiments of the present disclosure is UE behavior in handling conflicting transmission directions due to dynamic SFI reception. According to the current agreement, any dynamically scheduled PUSCH transmission is not cancelled since an SFI is received indicating conflicting transmission directions. Dynamically scheduled PUSCH includes dynamic retransmission of grants scheduled, or configured, by DCI formats 0_0 and 0_1 of the dynamic PUSCH, or first configured grant resources after activation by DCI formats 0_0 and 0_1 addressed to CS-RNTI.

However, PUSCH after deactivating DCI may also be regarded as dynamic PUSCH (e.g., without undergoing cancellation by SFI), since it should carry a MAC CE with configured grant confirmation according to the MAC procedure.

In one embodiment, PUSCH resources in BWP (including any repetition when configured with slot aggregation) are treated as dynamically scheduled PUSCH after DCI deactivation of configured grant type 2, and thus do not undergo cancellation due to transmission direction conflicting with SFI. Here, "direction of conflict with SFI" includes the following cases: the dynamic SFI carried by DCI format 2_0 may indicate at least one of symbols overlapping with time domain resources to carry PUSCH with configured grant confirmation MAC CE as DL or flexible symbol. Alternatively, the PUSCH carrying the configured grant confirmation MAC CE triggered by the deactivation DCI is treated as a dynamically scheduled PUSCH and therefore does not experience cancellation due to the transmission direction conflicting with the SFI.

In one embodiment, the UE is not expected to send a MAC CE configured grant confirmation in the configured PUSCH resource before the minimum PUSCH preparation procedure time starting from the last symbol of CORESET, where DCI format 0_0 is validated as configured grant type 2 deactivation. In other words, upon receiving the valid DCI format 0_0 of the bearer type 2CG PUSCH deactivation command, the UE may be expected to transmit the PUSCH of the bearer configured grant confirmation MAC CE using the earliest transmission opportunity of the grant configuration according to the type 2 configuration such that the start of the CP of the first UL symbol for the transmission opportunity occurs at least T _proc,2 (milliseconds) after the end of the last symbol of the PDCCH, which carries the DCI format 0_0, the DCI format 0_0 carrying the type 2CG PUSCH deactivation command.

In another embodiment, upon receiving the valid DCI format 0_0 of the bearer type 2CG PUSCH deactivation command, the UE may be expected to transmit PUSCH of the grant confirmation MAC CE of the bearer configuration using the same frequency domain resources as indicated in the activation grant of the corresponding type 2CG PUSCH configuration and the time domain resources indicated in the time domain allocation bit field in the DCI format 0_0 of the bearer deactivation command.

Termination of CGPUSCH repetition while covered by dynamic PUSCH with different HARQ process IDs

In one embodiment, in the case of a different HARQ process ID, if the initial transmission of the configured grant overlaps with the dynamic PUSCH at the physical layer (where the overlap at the physical layer may occur just before the CG repetition starts at T _proc,2 of the dynamic PUSCH), then the entire repetition sequence of the CG is terminated. In particular, for any RV sequence, the repetition should terminate at the symbol of DCI format 0_0 or 0_1 scheduling another PUSCH with the same HARQ process, or at the symbol of DCI format 0_0 or 0_1 scheduling the initial repetition of another PUSCH with a different HARQ process, whichever comes first.

In another embodiment, in case of a different HARQ process ID, if the transmission of the configured grant overlaps with the dynamic PUSCH at the physical layer, the repetition that falls wholly or partly within the interval of "X" symbols starting from the starting symbol of the dynamic PUSCH is discarded and the remaining repetition is transmitted. Here, "X" may be at least T _proc,2 symbols or a function thereof, e.g., x=a×t _proc,2, where "a" is a scale factor, which may be equal to 1 or greater than 1. Alternatively, x=a+t _proc,2. In another variation of the embodiment, the above interval of length "X" symbols may be defined to start from the last symbol of the dynamic PUSCH. In these embodiments, the CG PUSCH transmission may be an initial transmission alone or any repetition in both the initial transmission and sequence.

Fig. 4 illustrates an architecture of a network system 400 in accordance with certain embodiments. System 400 is shown to include a User Equipment (UE) 401 and a UE 402. UEs 401 and 402 are illustrated as smartphones (e.g., handheld touch screen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a Personal Data Assistant (PDA), pager, portable computer, desktop computer, wireless handset, or any computing device that includes a wireless communication interface.

In some embodiments, either of UEs 401 and 402 can comprise an internet of things (IoT) UE, which can include a network access layer designed for low power IoT applications that utilize short term UE connections. IoT UEs can exchange data with machine-to-machine (M2M) or machine-type communication (MTC) servers or devices via Public Land Mobile Networks (PLMNs), proximity services (ProSe) or device-to-device (D2D) based communications, sensor networks, or IoT networks using technologies such as machine-to-machine (M2M) or machine-type communication (MTC). The M2M or MTC data exchange may be a machine initiated data exchange. IoT networks describe the use of short-term connections to interconnect IoT UEs, which may include uniquely identifiable embedded computing devices (within the internet infrastructure). The IoT UE may execute a background application (e.g., keep-alive message, status update, etc.) to facilitate connection of the IoT network.

UEs 401 and 402 may be configured to connect (e.g., communicatively couple) with a Radio Access Network (RAN) 410—ran 410 may be, for example, an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), a next generation RAN (NG RAN), or some other type of RAN. UEs 401 and 402 utilize connections 403 and 404, respectively, each of which includes a physical communication interface or layer (discussed in further detail below); in this example, connections 403 and 404 are illustrated as implementing a communicatively coupled air interface and are capable of conforming to a cellular communication protocol such as a global system for mobile communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a push-to-talk (PTT) protocol, a push-to-talk (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and so on.

In this embodiment, UEs 401 and 402 may further exchange communication data directly via ProSe interface 405. ProSe interface 405 may alternatively be referred to as a side link interface that includes one or more logical channels including, but not limited to, a physical side link control channel (PSCCH), a physical side link shared channel (PSSCH), a physical side link discovery channel (PSDCH), and a physical side link broadcast channel (PSBCH).

UE 402 is shown configured to access an Access Point (AP) 406 via a connection 407. Connection 407 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 406 would comprise wireless fidelityAnd a router. In this example, the AP 406 is shown connected to the internet without being connected to the core network of the wireless system (described in further detail below).

RAN 410 can include one or more access nodes that enable connections 403 and 404. These Access Nodes (ANs) can be referred to as Base Stations (BS), nodebs, evolved nodebs (enbs), next generation nodebs (gnbs), RAN nodes, etc., and can include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., cell). RAN 410 may include one or more RAN nodes for providing macro cells (e.g., macro RAN node 411) and one or more RAN nodes, such as Low Power (LP) RAN node 412, for providing femto cells or pico cells (e.g., cells with less coverage, less user capacity, or higher bandwidth than macro cells).

Either of RAN nodes 411 and 412 can terminate the air interface protocol and can be the first point of contact for UEs 401 and 402. In some embodiments, any of RAN nodes 411 and 412 are capable of satisfying various logical functions of RAN 410, including but not limited to Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

According to certain embodiments, UEs 401 and 402 may be configured to communicate with each other or any of RAN nodes 411 and 412 over a multicarrier communication channel using Orthogonal Frequency Division Multiplexing (OFDM) communication signals in accordance with various communication techniques such as, but not limited to, orthogonal Frequency Division Multiple Access (OFDMA) communication techniques (e.g., for downlink communications) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or side link communications), although the scope of the embodiments is not limited in this respect. The OFDM signal can include a plurality of orthogonal subcarriers.

In some embodiments, the downlink resource grid can be used for downlink transmissions from either of RAN nodes 411 and 412 to UEs 401 and 402, while the uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, this time-frequency plane representation is common practice, which makes radio resource allocation intuitive. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in the radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid comprises a plurality of resource blocks describing the mapping of some physical channels to resource elements. Each resource block includes a set of resource elements. In the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit a number of different physical downlink channels.

A Physical Downlink Shared Channel (PDSCH) may carry user data and higher layer signaling to UEs 401 and 402. The Physical Downlink Control Channel (PDCCH) may carry information on a transport format and resource allocation related to the PDSCH channel, etc. It may also inform UEs 401 and 402 of transport format, resource allocation and H-ARQ (hybrid automatic repeat request) information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UEs 402 within a cell) may be performed on either of RAN nodes 411 and 412 based on channel quality information fed back from either of UEs 401 and 402. The downlink resource allocation information may be transmitted on a PDCCH for (e.g., allocated to) each of UEs 401 and 402.

The PDCCH may use Control Channel Elements (CCEs) to convey control information. The PDCCH complex-valued symbols may first be organized into quadruples before being mapped to resource elements, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine four physical resource elements referred to as Resource Element Groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. Depending on the size of Downlink Control Information (DCI) and channel conditions, a PDCCH can be transmitted using one or more CCEs. Four or more different PDCCH formats with different numbers of CCEs (e.g., aggregation levels l=1, 2, 4, or 8) can be defined in LTE.

Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above-described concept. For example, some embodiments may utilize an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar to above, each ECCE may correspond to nine groups of four physical resource elements referred to as Enhanced Resource Element Groups (EREGs). In some cases, ECCEs may have other amounts of EREGs.

RAN 410 is shown communicatively coupled to a Core Network (CN) 420 via an S1 interface 413. In an embodiment, the CN 420 may be an Evolved Packet Core (EPC) network, a next generation packet core (NPC) network, or some other type of CN. In this embodiment, the S1 interface 413 is divided into two parts: S1-U interface 414 and S1 Mobility Management Entity (MME) interface 415, S1-U interface 414 carries traffic data between RAN nodes 411 and 412 and serving gateway (S-GW) 422, S1 MME interface 415 is a signaling interface between RAN nodes 411 and 412 and MME 421.

In this embodiment, CN 420 includes MME 421, S-GW 422, packet Data Network (PDN) gateway (P-GW) 423, and Home Subscriber Server (HSS) 424. The MME 421 may be similar in function to the control plane of a legacy serving General Packet Radio Service (GPRS) support node (SGSN). The MME 421 may manage mobility aspects in access such as gateway selection and tracking area list management. HSS 424 may include a database for network users that includes subscription-related information to support the processing of communication sessions by network entities. Depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc., the CN 420 may include one or several HSS 424. For example, HSS 424 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, and the like.

The S-GW 422 may terminate the S1 interface 413 towards the RAN 410 and route data packets between the RAN 410 and the CN 420. In addition, the S-GW 422 may be a local mobility anchor for inter-RAN node handover and may also provide an anchor for mobility between 3 GPP. Other functions may include lawful interception, billing, and some policy enforcement.

The P-GW 423 may terminate the SGi interface towards the PDN. P-GW 423 may route data packets between the EPC network and external networks, such as networks that include application server 430 (alternatively referred to as an Application Function (AF)), via Internet Protocol (IP) interface 425. In general, the application server 430 may be an element that provides a core network (e.g., UMTS Packet Service (PS) domain, LTE PS data traffic, etc.) to applications that use IP bearer resources. In this embodiment, P-GW 423 is shown communicatively coupled to application server 430 via IP communication interface 425. Application server 430 can also be configured to support one or more communication services (e.g., voice over internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social network services, etc.) for UEs 401 and 402 via CN 420.

P-GW 423 may further be a node for policy enforcement and charging data collection. Policy and charging enforcement function (PCRF) 426 is a policy and charging control element of CN 420. In a non-roaming scenario, there may be one PCRF in a local public land mobile network (HPLMN) associated with an internet protocol connectivity access network (IP-CAN) session of the UE. In a roaming scenario with local traffic bursts, there may be two PCRFs associated with the IP-CAN session of the UE: a home PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 426 may be communicatively coupled to application server 430 via P-GW 423. Application server 430 may signal PCRF 426 to indicate the new traffic flow and select the appropriate quality of service (QoS) and charging parameters. PCRF 426 may provide this rule to a Policy and Charging Enforcement Function (PCEF) (not shown) using an appropriate Traffic Flow Template (TFT) and QoS Class (QCI) identifier, which begins QoS and charging specified by application server 430.

Fig. 5 illustrates example components of a device 500 in accordance with certain embodiments. In some embodiments, device 500 may include application circuitry 502, baseband circuitry 504, radio Frequency (RF) circuitry 506, front End Module (FEM) circuitry 508, one or more antennas 510, and Power Management Circuitry (PMC) 512 coupled together at least as shown. The illustrated components of the apparatus 500 may be included in a UE or RAN node. In some embodiments, the device 500 may include fewer elements (e.g., the RAN node may not utilize the application circuitry 502, but instead include a processor/controller to process IP data received from the EPC). In some embodiments, device 500 may include additional elements, such as memory/storage, a display, a camera, a sensor, or an input/output (I/O) interface. In other embodiments, the components described below may be included in multiple devices (e.g., for a cloud-RAN (C-RAN) implementation, the circuitry may be included in multiple devices, respectively).

The application circuitry 502 may include one or more application processors. For example, application circuitry 502 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. A processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled to or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 500. In some embodiments, the processor of application circuitry 502 may process IP data packets received from the EPC.

Baseband circuitry 504 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. Baseband circuitry 504 may include one or more baseband processors or control logic to process baseband signals received from the receive signal path of RF circuitry 506 and to generate baseband signals for the transmit signal path of RF circuitry 506. Baseband processing circuit 504 may interface with application circuit 502 to generate and process baseband signals and control the operation of RF circuit 506. For example, in some embodiments, the baseband circuitry 504 may include a third generation (3G) baseband processor 504A, a fourth generation (4G) baseband processor 504B, a fifth generation (5G) baseband processor 504C, or other baseband processor 504D of an existing generation, a generation under development, or a generation to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 504 (e.g., one or more baseband processors 504A-D) may handle various wireless control functions that enable communication with one or more radio networks via the RF circuitry 506. In other embodiments, some or all of the functionality of baseband processors 504A-D may be included in modules stored in memory 504G and executed via Central Processing Unit (CPU) 504E. The wireless control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 504 may include Fast Fourier Transform (FFT), precoding, or constellation mapping/demapping functions. In some embodiments, the encoding/decoding circuitry of baseband circuitry 504 may include convolution, tail-biting convolution, turbo, viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of the modem and encoder/decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

In some embodiments, baseband circuitry 504 may include one or more audio Digital Signal Processors (DSPs) 504F. The audio DSP 504F may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments. In some embodiments, components of the baseband circuitry may be suitably combined on a single chip, a single chipset, or disposed on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuitry 504 and application circuitry 502 may be implemented together, such as on a system on a chip (SOC).

In some embodiments, baseband circuitry 504 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 504 may support communication with an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or other Wireless Metropolitan Area Network (WMAN), wireless Local Area Network (WLAN), wireless Personal Area Network (WPAN). In embodiments where the baseband circuitry 504 is configured to support radio communications for multiple wireless protocols, it may be referred to as a multimode baseband circuitry.

RF circuitry 506 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, RF circuitry 506 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuitry 506 may include a receive signal path that may include circuitry to down-convert RF signals received from FEM circuitry 508 and provide baseband signals to baseband circuitry 504. RF circuitry 506 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by baseband circuitry 504 and provide RF output signals to FEM circuitry 508 for transmission.

In some embodiments, the receive signal path of RF circuit 506 may include a mixing circuit 506a, an amplifying circuit 506b, and a filtering circuit 506c. In some embodiments, the transmit signal path of RF circuit 506 may include filter circuit 506c and mixer circuit 506a. The RF circuit 506 may also include a combining circuit 506d for combining frequencies used by the mixing circuit 506a of the receive signal path and the transmit signal path. In some embodiments, the mixing circuit 506a of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 508 based on the synthesized frequency provided by the synthesizing circuit 506 d. The amplification circuit 506b may be configured to amplify the down-converted signal and the filtering circuit 506c may be a Low Pass Filter (LPF) or a Band Pass Filter (BPF) configured to remove unwanted signals from the down-converted signal to produce an output baseband signal. The output baseband signal may be provided to baseband circuitry 504 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, but this is not required. In some embodiments, mixing circuit 506a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixing circuit 506a of the transmit signal path may be configured to upconvert the input baseband signal based on the synthesized frequency provided by the synthesizing circuit 506d to generate an RF output signal for the FEM circuit 508. The baseband signal may be provided by baseband circuitry 504 and may be filtered by filter circuitry 506 c.

In some embodiments, the mixing circuit 506a of the receive signal path and the mixing circuit 506a of the transmit signal path may include two or more mixers and may be configured for quadrature down-conversion and/or up-conversion, respectively. In some embodiments, the mixing circuit 506a of the receive signal path and the mixing circuit 506a of the transmit signal path may include two or more mixers and may be configured for image rejection (e.g., hartley image rejection). In some embodiments, the mixing circuit 506a of the receive signal path and the mixing circuit 506a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixing circuit 506a of the receive signal path and the mixing circuit 506a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 506 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 504 may include a digital baseband interface to communicate with RF circuitry 506.

In some dual mode embodiments, a separate radio IC circuit may be provided for each spectrum to process the signal, although the scope of the embodiments is not limited in this respect.

In some embodiments, combining circuit 506d may be a fractional-N combiner or a fractional-N/n+1 combiner, although the scope of the embodiments is not limited in this respect as other types of frequency combiners may be suitable. For example, the combining circuit 506d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

The combining circuit 506d may be configured to combine the output frequencies used by the mixing circuit 506a of the RF circuit 506 based on the frequency input and the divider control input. In some embodiments, the combining circuit 506d may be a fractional N/n+1 synthesizer.

In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), but this is not required. The divider control input may be provided by the baseband circuitry 504 or the application processor 502 depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor 502.

The combining circuit 506d of the RF circuit 506 may include a frequency divider, a Delay Locked Loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD) and the phase accumulator may be a Digital Phase Accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or n+1 (e.g., based on a carry) to provide a fractional divide ratio. In some example embodiments, the DLL may include a set of cascaded adjustable delay units, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to divide the VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO period.

In some embodiments, the combining circuit 506d may be configured to generate the carrier frequency as the output frequency, while in other embodiments the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used with the quadrature generator and the divide circuit to generate a plurality of signals having different phases from each other at the carrier frequency. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, RF circuit 506 may include an IQ/polarity converter.

FEM circuitry 508 may include a receive signal path, which may include circuitry configured to operate on RF signals received from one or more antennas 510, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 506 for further processing. FEM circuitry 508 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 506 for transmission through one or more of the one or more antennas 510. In various embodiments, amplification through the transmit or receive signal paths may be accomplished in RF circuit 506 alone, FEM 508 alone, or both RF circuit 506 and FEM 508.

In some embodiments, FEM circuitry 508 may include TX/RX switches to switch between transmit mode operation and receive mode operation. FEM circuitry 508 may include a receive signal path and a transmit signal path. The receive signal path of FEM circuitry 508 may include a Low Noise Amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to RF circuitry 506). The transmit signal path of FEM circuitry 508 may include: a Power Amplifier (PA) for amplifying an input RF signal (e.g., provided by RF circuit 506); and one or more filters for generating RF signals for subsequent transmission (e.g., via one or more of the one or more antennas 510).

In some embodiments, PMC 512 may manage the power provided to baseband circuitry 504. In particular, the PMC 512 may control power supply selection, voltage scaling, battery charging, or DC-DC conversion. PMC 512 may often be included when device 500 is capable of being powered by a battery, for example, when the device is included in a UE. PMC 512 may improve power conversion efficiency while providing desired implementation size and heat dissipation characteristics.

Fig. 5 shows PMC 512 coupled only to baseband circuitry 504. However, in other embodiments, PMC 512 may additionally or alternatively be coupled to and perform similar power management operations on other components, such as, but not limited to, application circuitry 502, RF circuitry 506, or FEM 508.

In some embodiments, PMC 512 may control or otherwise be part of various power saving mechanisms of device 500. For example, if the device 500 is in an RRC Connected (rrc_connected) state in which it is still Connected to the RAN node because it expects to receive traffic briefly, after a period of inactivity it may enter a state called discontinuous reception mode (DRX). During this state, the device 500 may be powered down for a short time interval, thereby conserving power.

If there is no data traffic active for an extended period of time, the device 500 may transition to an RRC Idle (rrc_idle) state in which it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 500 enters a very low power state and performs paging where it wakes up again periodically to listen to the network and then powers down again. The device 500 may not receive data in this state and must transfer back to the RRC connected state in order to receive data.

The additional power saving mode may cause the device to fail to use the network for longer than the paging interval (ranging from seconds to hours). During this time, the device is completely inaccessible to the network and may be completely powered down. Any data transmitted during this period will create a large delay and this delay is assumed to be acceptable.

The processor of the application circuitry 502 and the processor of the baseband circuitry 504 may be used to execute elements of one or more instances of a protocol stack. For example, the processor of baseband circuitry 504 may be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processor of application circuitry 502 may utilize data (e.g., packet data) received from these layers and further perform layer 4 functions (e.g., transmission Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, layer 3 may include a Radio Resource Control (RRC) layer, which will be described in further detail below. As mentioned herein, layer 2 may include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which will be described in further detail below. As mentioned herein, layer 1 may include a Physical (PHY) layer of the UE/RAN node, as will be described in further detail below.

Fig. 6 illustrates an example interface of baseband circuitry in accordance with certain embodiments. As discussed above, the baseband circuitry 504 of fig. 5 may include processors 504A-504E and memory 504G used by the processors. Each of the processors 504A-504E may include a memory interface 604A-604E, respectively, to transmit and receive data to and from the memory 504G.

Baseband circuitry 504 may further include one or more interfaces to communicatively couple to other circuits/devices, such as a memory interface 612 (e.g., an interface for transmitting/receiving data to/from memory external to baseband circuitry 504), an application circuit interface 614 (e.g., an interface for transmitting/receiving data to/from application circuitry 502 of figure 5), an RF circuit interface 616 (e.g., an interface for transmitting/receiving data to/from RF circuitry 506 of fig. 5), a wireless hardware connection interface 618 (e.g., for transmitting data to/from a Near Field Communication (NFC) component,Components (e.g./>)Low energy),/>The interfaces that the components and other communication components transmit/receive data), and a power management interface 620 (e.g., an interface for transmitting/receiving power or control signals to/from the PMC 512).

Fig. 7 is a block diagram illustrating components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to certain example embodiments. In particular, FIG. 7 shows a diagrammatic representation of a hardware resource 700, the hardware resource 700 including one or more processors (or processor cores) 710, one or more memory/storage devices 720, and one or more communication resources 730, each of which may be communicatively coupled via a bus 740. For embodiments in which node virtualization (e.g., NFV) is utilized, the manager 702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 700.

Processor 710 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 712 and processor 714.

Memory/storage 720 may include main memory, disk storage, or any suitable combination thereof. Memory/storage 720 may include, but is not limited to, any type of volatile or non-volatile memory such as Dynamic Random Access Memory (DRAM), static Random Access Memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid state memory, and the like.

Communication resources 730 may include interconnections or network interface components or other suitable devices to communicate with one or more peripheral devices 704 or one or more databases 706 via network 708. For example, communication resources 730 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, and so forth,Components (e.g./>)Low energy),/>Components and other communication components.

The instructions 750 may include software, programs, applications, applets, APPs, or other executable code for causing at least any one of the processors 710 to perform any one or more of the methods discussed herein. The instructions 750 may reside, completely or partially, within at least one of the processors 710 (e.g., within a cache memory of the processor), within the memory/storage device 720, or any suitable combination thereof. Further, any portion of the instructions 750 may be transferred from any combination of the peripheral 704 or the database 706 to the hardware resource 700. Accordingly, the memory of processor 710, memory/storage 720, peripheral 704, and database 706 are examples of computer-readable and machine-readable media.

In various embodiments, the devices/components of fig. 4-7 (particularly the baseband circuitry of fig. 6) may be used to practice, in whole or in part, any of the operational flows/algorithm structures depicted in fig. 1-3.

An example of an operational flow/algorithm structure is depicted in fig. 1, which may be performed by a next generation NodeB (gNB) in accordance with certain embodiments. In this example, the operational flow/algorithm structure 100 may include: at 105, downlink Control Information (DCI) is retrieved from a memory, the DCI for scheduling a Physical Uplink Shared Channel (PUSCH) transmission overlapping with a repetition of a hybrid automatic repeat request (HARQ) process for a User Equipment (UE). The operational flow/algorithm structure 100 may further comprise: at 110, a message including DCI is generated. The operational flow/algorithm structure 100 may further comprise: at 115, the message is encoded for transmission to the UE.

Another example of an operational flow/algorithm structure is depicted in fig. 2, which may be performed by a UE in accordance with certain embodiments. In this example, the operational flow/algorithm structure 200 may include: at 205, a message including Downlink Control Information (DCI) is detected, wherein the UE is to schedule a Physical Uplink Shared Channel (PUSCH) transmission overlapping with a repetition of a hybrid automatic repeat request (HARQ) process for the UE. The operational flow/algorithm structure 200 may further comprise: at 210, PUSCH repetition is stopped based on the detection of DCI. The operational flow/algorithm structure 200 may further comprise: at 215, a PUSCH message is encoded, the PUSCH message including a grant confirmation of a Media Access Control (MAC) Control Element (CE) configuration for transmission.

Another example of an operational flow/algorithm structure is depicted in fig. 3, which may be performed by the gNB in accordance with certain embodiments. In this example, the operational flow/algorithm structure 300 may include: at 305, a message is generated that includes Downlink Control Information (DCI) for scheduling a Physical Uplink Shared Channel (PUSCH) transmission overlapping with a hybrid automatic repeat request (HARQ) repetition for a User Equipment (UE). The operational flow/algorithm structure 300 may further comprise: at 310, a configuration message is encoded for transmission to a UE.

Example

Some non-limiting examples are provided below.

Example 1 includes an apparatus comprising: a memory to store Downlink Control Information (DCI) to schedule a second Physical Uplink Shared Channel (PUSCH) transmission overlapping one or more repetitions of the PUSCH transmission for a specified hybrid automatic repeat request (HARQ) process for a User Equipment (UE); and processing circuitry, coupled to the memory, for: retrieving DCI from a memory; generating a message including DCI; and encoding the message for transmission to the UE.

Example 2 includes the apparatus of example 1 or some other example herein, wherein the DCI is format 0_0 or 0_1.

Example 3 includes the apparatus of example 1 or some other example herein, wherein the DCI scheduling the second PUSCH is addressed to a HARQ process identifier having a common identifier with the ongoing or licensed first PUSCH.

Example 4 includes the apparatus of example 1 or some other example herein, wherein the DCI includes an indication of a time-domain resource allocation (TDRA) for the second PUSCH.

Example 5 includes the apparatus of example 4 or some other example herein, wherein the second PUSCH does not overlap with the repetition of the first PUSCH if the repetition of the first PUSCH begins a plurality of symbols ("m") before a last symbol of a PDCCH carrying DCI scheduling the second PUSCH.

Example 6 includes the apparatus of example 5 or some other example herein, wherein the value of m is an N2 symbol, wherein N2 is a minimum UE processing time for PUSCH preparation corresponding to the specified processing capability.

Example 7 includes the apparatus of example 6 or some other example herein, wherein N2 is based on one or more of: a subcarrier spacing of the scheduling PDCCH, and a subcarrier spacing of the first or second PUSCH.

Example 8 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a User Equipment (UE) to: detecting a message including Downlink Control Information (DCI) that is used by a UE to schedule a second Physical Uplink Shared Channel (PUSCH) transmission overlapping one or more repetitions of the PUSCH transmission for a specified hybrid automatic repeat request (HARQ) process for the UE; stopping PUSCH repetition based on detection of DCI; and encoding the second PUSCH message for transmission on the time domain resource as indicated in the DCI scheduling the second PUSCH.

Example 9 includes the one or more computer-readable media of example 8 or some other example herein, wherein the DCI scheduling the second PUSCH is addressed to a HARQ process identifier having a common identifier with the ongoing or licensed first PUSCH.

Example 10 includes the one or more computer-readable media of example 8 or some other example herein, wherein the UE stops repetition of the first PUSCH starting with repetition corresponding to time domain resources that overlap with the indicated time domain resource allocation for the second PUSCH transmission.

Example 11 includes the one or more computer-readable media of example 8 or some other example herein, wherein the DCI is a format 0_0 or 0_1.

Example 12 includes the one or more computer-readable media of example 8 or some other example herein, wherein the DCI includes an indication of a time-domain resource allocation (TDRA) for the second PUSCH.

Example 13 includes the one or more computer-readable media of example 12 or some other example herein, wherein the second PUSCH does not overlap with the repetition of the first PUSCH if the repetition of the first PUSCH begins before a number of symbols ("m") after a last symbol of a PDCCH carrying DCI scheduling the second PUSCH.

Example 14 includes the one or more computer-readable media of example 13 or some other example herein, wherein the value of m is an N2 symbol, where N2 is a minimum UE processing time for PUSCH preparation corresponding to a specified processing capability.

Example 15 includes the one or more computer-readable media of example 14 or some other example herein, wherein N2 is based on one or more of: a subcarrier spacing of the scheduling PDCCH, and a subcarrier spacing of the first or second PUSCH.

Example 16 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a next generation NodeB (gNB): generating a message comprising Downlink Control Information (DCI) for scheduling a second Physical Uplink Shared Channel (PUSCH) transmission overlapping one or more repetitions of the PUSCH transmission for a specified hybrid automatic repeat request (HARQ) for a User Equipment (UE); and encoding the message for transmission to the UE.

Example 17 includes the one or more computer-readable media of example 16 or some other example herein, wherein the DCI is a format 0_0 or 0_1.

Example 18 includes the one or more computer-readable media of example 16 or some other example herein, wherein the DCI scheduling the second PUSCH is addressed to a HARQ process identifier having a common identifier with the ongoing or licensed first PUSCH.

Example 19 includes the one or more computer-readable media of example 16 or some other example herein, wherein the DCI includes an indication of a time-domain resource allocation (TDRA) of the second PUSCH such that the second PUSCH does not overlap with the repetition of the first PUSCH if the repetition of the first PUSCH begins before a number of symbols ("m") after a last symbol of a PDCCH carrying DCI scheduling the second PUSCH.

Example 20 includes the one or more computer-readable media of example 18 or some other example herein, wherein the value of m is an N2 symbol, wherein N2 is a minimum UE processing time for PUSCH preparation time corresponding to a specified processing capability, N2 being defined based on one or more of: a subcarrier spacing of the scheduling PDCCH, and a subcarrier spacing of the first or second PUSCH.

Example 21 may include an apparatus comprising: a module for performing one or more elements of any one of examples 1-20 or the method described with respect to any one of examples 1-20, or any other method or process described herein.

Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, when executed by one or more processors of the electronic device, to perform one or more elements of the methods described in any of examples 1-20 or with respect to any of examples 1-20, or any other method or process described herein.

Example 23 may include an apparatus comprising: logic, modules, and/or circuitry to perform one or more elements of any of examples 1-20 or the methods described with respect to any of examples 1-20, or any other method or process described herein.

Example 24 may include a method, technique, or process as any of examples 1-20 or described with respect to any of examples 1-20, or a portion thereof.

Example 25 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform any one of examples 1-20 or the method, technique, or process described with respect to any one of examples 1-20, or a portion thereof.

Example 26 may include a method of communicating in a wireless network as shown and described herein.

Example 27 may include a system for providing wireless communications as shown and described herein.

Example 28 may include a device for providing wireless communication as shown and described herein.

The description of illustrated implementations herein includes what is described in the abstract and is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Although specific implementations and examples have been described herein for illustrative purposes, various alternative or equivalent embodiments or implementations calculated to achieve the same purposes may be made from the foregoing detailed description without departing from the scope of the disclosure.

Claims (17)

1. An apparatus for scheduling Physical Uplink Shared Channel (PUSCH) transmissions, the apparatus comprising:

A memory to store Downlink Control Information (DCI) to schedule a second PUSCH transmission overlapping one or more repetitions of a first PUSCH transmission for a specified hybrid automatic repeat request (HARQ) process for a User Equipment (UE); and

Processing circuitry, coupled with the memory, for:

Retrieving DCI from the memory;

Generating a message including DCI; and

The message is encoded for transmission to the UE,

Wherein, the DCI is in the format 0_0 or 0_1.

2. The apparatus of claim 1, wherein DCI scheduling the second PUSCH is addressed to a HARQ process identifier having a common identifier with an ongoing or licensed first PUSCH.

3. The apparatus of claim 1, wherein the DCI includes an indication of a time-domain resource allocation (TDRA) for the second PUSCH.

4. The apparatus of claim 3, wherein the second PUSCH does not overlap with the repetition of the first PUSCH if the repetition of the first PUSCH starts before a plurality of symbols, i.e., m symbols, after a last symbol of a PDCCH carrying DCI scheduling the second PUSCH.

5. The apparatus of claim 4, wherein the value of m is N2 symbols, where N2 is a minimum UE processing time for PUSCH preparation corresponding to a specified processing capability.

6. The apparatus of claim 5, wherein N2 is based on one or more of: a subcarrier spacing of the scheduling PDCCH, and a subcarrier spacing of the first or second PUSCH.

7. One or more computer-readable media for scheduling Physical Uplink Shared Channel (PUSCH) transmissions, wherein the media stores instructions that, when executed by one or more processors, cause a User Equipment (UE) to:

detecting a message including Downlink Control Information (DCI) that is used by a UE to schedule a second PUSCH transmission overlapping with one or more repetitions of a first PUSCH transmission for a specified hybrid automatic repeat request (HARQ) process for the UE;

stopping PUSCH repetition based on detection of DCI; and

Encoding the second PUSCH message for transmission on time domain resources indicated in the DCI scheduling the second PUSCH,

Wherein, the DCI is in the format 0_0 or 0_1.

8. The one or more computer-readable media of claim 7, wherein the DCI scheduling the second PUSCH is addressed to a HARQ process identifier having a common identifier with the first PUSCH that is ongoing or licensed.

9. The one or more computer-readable media of claim 7, wherein the UE stops repetition of the first PUSCH starting from a repetition corresponding to a time domain resource that overlaps with the indicated time domain resource allocation for the second PUSCH transmission.

10. The one or more computer-readable media of claim 7, wherein the DCI includes an indication of a time-domain resource allocation (TDRA) for the second PUSCH.

11. The one or more computer-readable media of claim 10, wherein the second PUSCH does not overlap with the repetition of the first PUSCH if the repetition of the first PUSCH begins before a plurality of symbols, i.e., m symbols, after a last symbol of the PDCCH carrying the DCI scheduling the second PUSCH.

12. The one or more computer-readable media of claim 11, wherein the value of m is N2 symbols, where N2 is a minimum UE processing time for PUSCH preparation corresponding to a specified processing capability.

13. The one or more computer-readable media of claim 12, wherein N2 is based on one or more of: a subcarrier spacing of the scheduling PDCCH, and a subcarrier spacing of the first or second PUSCH.

14. One or more computer-readable media for scheduling Physical Uplink Shared Channel (PUSCH) transmissions, wherein the media stores instructions that, when executed by one or more processors, cause a next generation NodeB (gNB):

generating a message including Downlink Control Information (DCI) for scheduling a second PUSCH transmission overlapping with one or more repetitions of the first PUSCH transmission for a specified hybrid automatic repeat request (HARQ) for a User Equipment (UE); and

The message is encoded for transmission to the UE,

Wherein, the DCI is in the format 0_0 or 0_1.

15. The one or more computer-readable media of claim 14, wherein the DCI scheduling the second PUSCH is addressed to a HARQ process identifier having a common identifier with the first PUSCH that is ongoing or licensed.

16. The one or more computer-readable media of claim 14, wherein the DCI includes an indication of a time-domain resource allocation (TDRA) for the second PUSCH such that the second PUSCH does not overlap with the repetition of the first PUSCH if the repetition of the first PUSCH begins before a number of symbols, i.e., m symbols, after a last symbol of the PDCCH carrying the DCI scheduling the second PUSCH.

17. The one or more computer-readable media of claim 15, wherein the value of m is N2 symbols, where N2 is a minimum UE processing time for PUSCH preparation time corresponding to a specified processing capability, N2 being defined based on one or more of: a subcarrier spacing of the scheduling PDCCH, and a subcarrier spacing of the first or second PUSCH.