Patent Description:
In Long-Term Evolution (LTE), resources for uplink (UL) transmissions are granted by a network node (e.g., a base station, Evolved Node B (eNB), Next Generation Node B (gNB), etc.) This grant scheduling procedure can be done dynamically, such as when a network node schedules the UL transmission per transmission time interval (TTI). Alternatively, a semi-persistent scheduling (SPS) framework can be utilized. When SPS is utilized, uplink grants for multiple TTls are transmitted to the wireless device at some point prior to a data transmission. The configuration of SPS includes an indication regarding the periodicity of the grant, the allocations, and modulation and coding scheme (MCS) for subsequent SPS occasions related to the grant.

Another associated concept in wireless transmission is data retransmission. When the transmission of data fails due to some errors in the channel that cannot be fixed in the decoding, the receiver may request that the transmitter retransmit the data, for instance, using a HARQ process. The retransmission method may simply be transmitting the same data or a better coded data, with lower rate, for example. At the receiver side, the receiver may simply use the new retransmitted data instead of the initially transmitted data or may combine them to make a more reliable detection.

LTE uses a synchronous HARQ concept where an acknowledgement of correctly received data (ACK) or a negative acknowledgement of an erroneous detection (NACK) is sent by the receiver to the transmitter at a certain time over a Physical Hybrid-ARQ Indicator Channel (PHICH). In LTE, a wireless device (also referred to herein as a user equipment (UE)) uses the same HARQ process number every eight TTIs. Correspondingly, retransmission of the data, if needed, occurs every eight TTIs using the same HARQ process number as the original transmission. Since the UE uses a specific HARQ process ID at a specific subframe, the network node (also referred to herein as a base station, eNB, gNB, or the like) is able to identify individual HARQ processes and cross-reference each retransmission with its original transmission through the HARQ ID.

When considering the New Radio (NR) for <NUM>, it has been agreed that similar principles to those of SPS and HARQ should be adopted. Specifically, at least semi-static resource (re-)configuration is supported as a grant-free framework, which is similar to the Semi-Persistent Scheduling (SPS) and fast uplink access in LTE in which the transmission opportunities are pre-configured with a periodicity. The UL HARQ process in <NUM> aims to be asynchronous in design, which means that an ACK or NACK can be transmitted sporadically, thus rendering HARQ feedback timing unpredictable.

In LTE-SPS, network nodes allocate PHICH for each configured SPS UL grant. Since the HARQ is synchronous, only one PHICH is allocated for sending the necessary explicit HARQ feedback signals from a receiver to the transmitter. With asynchronous HARQ, however, many PHICH channels would be required, and NR does not provide these channels or a mechanism for their creation. Thus, because NR is to use UL semi-persistent scheduling without explicit HARQ feedback, a UE implementing NR protocols will not be able to determine whether it should send a new data packet according to the SPS period or it should send a retransmission of the previous packet. Therefore, solutions to solve the problems resulting from this ambiguity are needed, as the resulting uncertainty regarding what is to be transmitted by the UE in NR could cause acute performance and reliability degradation on a per-UE as well as a system-wide scale.

Some background information relating to dynamically adjusting data transmission parameters and controlling H-ARQ processes can be found in <CIT>.

The present disclosure describes example techniques for data retransmission in systems that do not utilize explicit HARQ feedback, such as those implementing SPS or similar scheduling paradigms. For instance, the present disclosure describes an example method performed by a network node for managing wireless data transmissions (e.g., in a transport block (TB) having an associated HARQ process ID) by a wireless device to the network node at periodic transmission occasions.

The present disclosure presents techniques for uplink data transmission and scheduling whereby a timer with a corresponding maximum retransmission time is configured for a wireless device such that when the timer expires, the wireless device can reuse the used HARQ process for transmission of new UL data or for retransmission of all or part of an original transmission. These techniques are based on the reality that there are two possible assumptions if the UE has not received any feedback. First, the wireless device could assume that the original transmission was correctly received (i.e., assumes an ACK) for the TB. Under this first possible assumption, the wireless device could generate and transmit a new TB for the given HARQ process at the next transmission occasion. This scenario would be applicable, for example, where the reliability requirements for receiving the transmission at the network node are not particularly high (e.g., in an enhanced Mobile Broadband (eMBB) use-case).

The other alternative is to assume that the data was not properly received and that a negative acknowledgement (NACK) should have been sent. In this case, the wireless device would generate and transmit the data of the original TB at the next transmission occasion of the HARQ process. This scenario would be applicable, for example, where the reliability requirements for receiving the data transmission at the network node are relatively high (e.g., in an ultra-reliable low latency communications (URLLC) use-case).

In either of these example scenarios, and following either assumption above, in an aspect of the example embodiments presented herein, transmissions and retransmissions can be governed according to a HARQ policy that defines a timer counting a pre-configured maximum feedback time period (T) and/or a default operation (e.g., according to one of the above-recited scenarios and assumptions). This default operation, which can include whether to transmit new data using a particular HARQ ID or to retransmit data that was previously transmitted using the HARQ ID, can be triggered after the timer expires without the transmitting device receiving HARQ feedback from a receiving device. In some examples, the timer could begin counting down the associated time period T when it transmits the original TB data, while in other examples the countdown could start when the wireless device receives the UL resource grant for the original TB data transmission. In addition, as indicated above, the default operation will be triggered in some embodiments where feedback has not been received by the time the timer has expired. This feedback associated with the timer could include an ACK, a NACK, a new data indicator (e.g., new data exists in a transmission queue), or a new resource grant for one or more uplink transmissions.

In a further aspect of some example embodiments, the maximum feedback time period T <NUM> can be selected or adapted (e.g., by the network node <NUM> or by another network-side device controlled by a network operator, for examples) based on the number of HARQ processes to be utilized for wireless communication between the wireless device <NUM> and the network node <NUM> (or at least for uplink transmissions <NUM>, <NUM>). In some examples, when the number of HARQ processes is relatively small (e.g., based on a threshold number, for instance) the value of the time period for the timer can be set to a relatively low value to allow for reuse of individual HARQ process numbers. Alternatively, where the number of HARQ processes is relatively large, the wireless device <NUM> can wait longer for a feedback before it must reuse the corresponding HARQ process number for new data, and therefore the time period can be set to a relatively higher value.

Furthermore, as multiple HARQ processes are available for use concurrently (i.e. as in LTE, where eight HARQ processes are available as discussed above), any available HARQ process can be used to transmit new data while waiting for maximum feedback time period T <NUM> of a particular HARQ ID. Thus, in a further aspect of the present disclosure, each HARQ process can operate its own timer, optionally with a same maximum feedback time period or with different time periods in other examples.

Aspects of these and other possible implementations will now be described in reference to the accompanying figures. <FIG> illustrates a wireless communication system <NUM> that includes a network node <NUM> and a wireless device <NUM> in wireless communication over one or more communication channels. As shown, the wireless device <NUM> is configured to transmit uplink messages to the network node. In an aspect, these uplink transmissions can include an original (e.g., first or earlier in time) TB transmission <NUM> comprising data and having a HARQ process ID. In addition, the uplink transmissions can include a subsequent TB transmission <NUM>, which, depending on the HARQ policy <NUM> stored at the wireless device <NUM> and the network node <NUM>, can include either new data or all or part of the original data for retransmission using the HARQ process ID of the original TB transmission <NUM>.

In addition, as shown in <FIG>, the network node <NUM> is configured to transmit downlink messages to the wireless device <NUM>. These downlink messages can include one or more uplink scheduling grants <NUM>, which in some instances can implement SPS techniques (i.e., one uplink scheduling grant <NUM> being transmitted for every n transmission occasions where n > <NUM>). In addition, the downlink transmissions can include configuration information <NUM>, which can include information related to the HARQ processes, such as information needed at the wireless device <NUM> to carry out the HARQ policy <NUM>. For instance, the configuration information may include a value for the time period T <NUM> associated with the timer.

Additionally, in some examples, the configuration information can include control or characteristic data gathered by the network node <NUM> to aid the wireless device <NUM> in determining the HARQ policy <NUM> and/or the time period associated with the timer. Such information may include a number of HARQ processes to be utilized by the wireless device <NUM> in its transmissions to the network node <NUM>, a periodicity of periodic transmission occasions (i.e., how frequently uplink transmission occasions or opportunities are available), a delay tolerance of a service corresponding to data that may be carried by a TB transmitted by the wireless device <NUM>, network load information, a processing time required for the network node to process received uplink transmissions from the wireless device <NUM>, among other factors that may be needed to ensure proper transmission timing and/or HARQ policy selection by the wireless device <NUM>. In an aspect, the selection of the HARQ policy (by wireless device <NUM>, for instance) includes determining whether the wireless device <NUM> is to retransmit all or part of the TB data transmitted in the original transmission <NUM> or is to use the HARQ process ID of that original transmission <NUM> to transmit new data in a TB at a next transmission occasion for that HARQ process if the timer expires without the wireless device <NUM> having received HARQ feedback for the original TB transmission <NUM>.

<FIG> illustrates an example of uplink transmission timing in the wireless communication system <NUM> of <FIG>, which allows for functional retransmission operations without using explicit HARQ feedback. In the simplified use-case illustrated in the figure, there is only a single HARQ process used in semi-persistent scheduling. As shown, the wireless device <NUM> can initially send an original TB transmission <NUM> at a periodic transmission occasion <NUM> defined by the corresponding uplink grant (e.g., in an earlier SPS message from the network node <NUM>). In the example shown, the timer <NUM> is started by the wireless device <NUM> contemporaneous with the original TB transmission <NUM> (though in other examples, the timer <NUM> could be started when the uplink grant for periodic transmission occasion <NUM> is received by the wireless device <NUM>). After transmitting the original TB and stating the timer <NUM>, the wireless device <NUM> then waits for a time period T <NUM> This time period T <NUM> may be selected by the wireless device <NUM>, preconfigured by a network operator, or assigned by the network node <NUM>.

If the wireless device <NUM> determines that no HARQ feedback has been received for the original TB transmission <NUM>, the wireless device <NUM> is configured to, at the next periodic transmission occasion <NUM> following expiration of the timer, either (a) reuse the HARQ process ID of the original TB transmission <NUM> to transmit new data in a new TB or (b) retransmit all or part of the original TB transmission <NUM> using the same HARQ process ID. In an aspect of the present disclosure, this determination regarding whether to transmit new data or retransmit the original data is governed by the HARQ policy <NUM>. Therefore, upon determining that the timer has expired and no HARQ feedback was received, the wireless device <NUM> takes the action mandated by the HARQ policy <NUM> in effect at the time. Thus, in some instances, depending on the HARQ policy <NUM>, the TB sent by the wireless device <NUM> at a next transmission occasion for the relevant HARQ process ID (i.e., the first occasion available for the HARQ process after the timer expires) could be either a retransmission of the original data or a new TB containing new data.

Furthermore, in example embodiments of the present disclosure, the HARQ policy <NUM> can be determined by the wireless device <NUM> (and optionally relayed to the network node <NUM>). In some examples, the HARQ policy <NUM> can be set by the wireless device <NUM> based on network-side factors such as observed or estimated latency, network load, Quality of Service (QoS) requirements of the service to which the transmitted data pertains or to which the data is to likely pertain, reliability requirements of the underlying service (e.g., eMBB vs. URLCC), and the like.

Moving on, <FIG> shows another example implementation where the number of HARQ processes is four. In this example, the timer time period T <NUM> is relatively long compared to the time period T <NUM> of <FIG>, and as a result, multiple transmission occasions for other HARQ process IDs occur during the time period T <NUM> - namely, TB transmissions 300B, 300C, and 300D at periodic transmission occasions 301B, 301C, and 301D, respectively. For purposes of the present disclosure, although the timer is described as having an associated time period T, the terms meant to be read as interchangeable such that when a timer is referred to, so is a time period T, and vice versa. Returning to the operation of the present solutions, again, as in <FIG>, upon expiration of the timer after time period T <NUM> elapses in <FIG>, the wireless device <NUM> either retransmits all or part of the data transmitted in the TB of 300A or transmits new data in a TB at the next periodic transmission occasion by reusing the HARQ process ID of the original TB transmission 300A.

As a comparison of <FIG> and <FIG> shows, the timer can be set (for instance, by the network node <NUM> or another network-side device) to have an associated time period T <NUM>, <NUM> that differs based on one or more parameters. For instance, the time period T <NUM>, <NUM> of the timer can be set based on one or more of the number of HARQ processes to be used by the wireless device <NUM>, a periodicity of the SPS transmission, or a degree of delay-tolerance associated with the service or application corresponding to the data contained in one or more of the uplink TB transmissions 300A-D and <NUM>. The timer could further be configured based on a processing time required by the network node <NUM> to decode and process received data of a given TB and perform a reliability check on the received data (e.g., cyclic redundancy check (CRC) or the like).

In some instances, the time period T <NUM>, <NUM> of the timer may additionally or alternatively be set based on the load in the network or network node <NUM> and/or throughput or QoS metrics mandated by an underlying service. For instance, in an example aspect, If the load is higher in the cell or cells operating on the same network node <NUM>, the network node <NUM> can configure (or reconfigure) the time period T <NUM>, <NUM> based on a present (or time-averaged) processing load present at the network node <NUM>, and may further set the time period T such that the network node <NUM> is able to respond to the wireless device <NUM> with HARQ feedback within the configured time period T at a rate that is greater than or equal to a threshold value (or is projected to meet the threshold value through extrapolation or similar predictive methods).

Turning to <FIG>, the figure depicts an example method <NUM> for managing TB transmissions by the wireless device <NUM> to a network node <NUM> at periodic transmission occasions, which can be performed by a wireless device <NUM> (e.g., a UE) according to some implementations. The method <NUM> can include, for instance, starting a timer for a HARQ process associated with a transport block transmission by the wireless device <NUM> to the network node <NUM> (i.e., original TB data transmissions <NUM> and 300A of <FIG> and <FIG>, respectively) at block <NUM>. In addition, the example method <NUM> can include, at block <NUM>, identifying a HARQ policy for the HARQ process, where the HARQ policy governs whether the wireless device <NUM> is to retransmit the TB or the original transmission <NUM> or transmit a new TB where no HARQ feedback responsive to the original TB transmission is received from the network nod e106 before the timer expires. In addition, the method <NUM> can include, at block <NUM>, retransmitting the TB or transmitting the new TB according to the HARQ policy at a next periodic transmission occasion for the HARQ process after the timer expires.

Furthermore, although not explicitly shown in <FIG>, additional or alternative aspects of the present disclosure could be included in method <NUM> in some embodiments. For instance, as shown in <FIG>, in some examples of method <NUM>, at least one additional HARQ process (see e.g., items 300B, 300C, 300D) is executed after starting the timer and before the timer expires. In an additional optional aspect of method <NUM>, the time period T associated with the timer can be set (e.g., by the network node <NUM>) according to one or more of: a number of HARQ processes utilized by the wireless device <NUM>, a periodicity of periodic transmission occasions, a delay tolerance of a service corresponding to data carried by the TB and/or the new TB, a processing time of the network node <NUM>, and a network load. In addition, as mentioned above, the timer for a relevant HARQ process can be started upon transmission of the original TB or upon the wireless device <NUM> receiving an uplink grant from the network node <NUM> for transmission of the TB. Also, as introduced above, the method <NUM> can include the wireless device <NUM> generating the HARQ policy.

<FIG> illustrates an example method <NUM> performed by a network node for managing TB transmissions by a wireless device <NUM> to the network node <NUM> at periodic transmission occasions. In an aspect, method <NUM> may include, at block <NUM>, configuring a timer for a HARQ process associated with a TB transmission by the wireless device to the network node. In addition, method <NUM> may include, at block <NUM>, identifying a HARQ policy for the HARQ process, where the HARQ policy governs whether the wireless device <NUM> is to retransmit the TB or transmit a new TB to the network node <NUM> in scenarios where the wireless device <NUM> receives no HARQ feedback from the network node <NUM> responsive to the TB transmission before the timer expires. Furthermore, at block <NUM>, method <NUM> may include receiving a retransmitted TB or a new TB according to the HARQ policy at a next periodic transmission occasion for the HARQ process after the timer expires.

Furthermore, although not explicitly shown in <FIG>, additional or alternative aspects of the present disclosure could be included in method <NUM> in some embodiments. For instance, in some examples, identifying the HARQ policy at block <NUM> may also include obtaining the HARQ policy from the wireless device <NUM>, for instance, via control signaling in a stand-alone uplink transmission or via a signal transmitted by the wireless device <NUM> of any other sort (e.g., higher-level signaling, trailing bits of control or data transmissions by the wireless device, etc.) where the HARQ policy can optionally be indicated in one or more piggybacked bits.

In an additional aspect of some embodiments, identifying the HARQ policy can include setting the HARQ policy at the network node <NUM>, which can be based on one or more of the following non-limiting list of factors: a number of HARQ processes utilized by the wireless device <NUM>, a periodicity of periodic transmission occasions, a delay tolerance and/or a reliability requirement of a service corresponding to data carried by the TB and/or the new TB, a processing time of the network node <NUM>, and a network load. In addition, in some examples, the time period T of the timer can be set by the network node <NUM> based on one or more of these factors. The method <NUM> can also include the network node <NUM> determining that the network load has reached a threshold value and, based on this determination, increasing the time period of the timer.

In a further aspect of the method <NUM>, and the functionality of the network node <NUM> generally, the network node <NUM> may be configured to perform error detection on one or more TBs received from the wireless device <NUM>. This can involve, for instance, performing CRC operations or otherwise processing received data using other error detection mechanisms known in the art. Based on the results of these error detection operations, the network node <NUM> can optionally transmit HARQ feedback to the wireless device assuming the configured HARQ policy allows for such transmissions to the wireless device <NUM>. Leveraging the unique features of the techniques presented herein, the network node <NUM> can then determine a TB and/or HARQ process that is to be transmitted or retransmitted during a next periodic transmission occasion based on a result of the error detection, the configured HARQ policy, and/or a time at which the HARQ feedback is transmitted to the wireless device <NUM> or is to be received by the wireless device <NUM>.

Moreover, though not explicitly shown in methods <NUM> or <NUM> of <FIG> or <FIG>, respectively, these methods may exhibit further optional aspects in some embodiments. For instance, in method <NUM> or method <NUM>, the periodic transmission occasions (e.g. <NUM>, <NUM> of <FIG>, 300A-300D, <NUM> of <FIG>) are defined according to an SPS scheme, which may also be referred to as "UL transmission without dynamic scheduling", "configured grant scheduling," or "configured scheduling.

In a further optional aspect, although the HARQ policy can be selected by the wireless device <NUM>, in some instances, it can alternatively be preconfigured, for instance, by a manufacturer, network operator, a particular radio access technology utilized by the wireless device <NUM> and the network node <NUM>, or the like. In the same vein, in some instances the HARQ policy may be static, where in other instances it may be dynamic in that it can change over time based on one or more factors, including those discussed above.

In addition, for purposes of the present disclosure, the wireless device <NUM> can be considered to be a user equipment, though, again, this is not a limiting aspect. Furthermore, in any of the example embodiments of the present disclosure, though not limiting, the network node <NUM> can be a gNB, eNB, Base Station, <NUM> Access Point, or any other radio access network device in communication with one or more wireless devices <NUM>. In other words, the network node <NUM>, as that term is used herein, is a general term and can correspond to any type of radio network node or any network node which communicates with a wireless device and/or with another network node. Examples of network nodes include, but are not limited to NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, evolved node B (eNodeB), new generation (<NUM>) node B (gNodeB), macro evolved Node B (MeNB), small evolved Node B (SeNB), network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, remote radio unit (RRU), remote radio head (RRH), nodes in distributed antenna system (DAS), core network node (e.g., mobile switching center (MSC), MME, etc.), operations & maintenance (O&M), open storage service (OSS), self-organizing network (SON), positioning node (e.g., evolved serving location center (E-SMLC)), minimizing of driving test (MDT), etc..

With these devices in mind, let us turn to <FIG>, <FIG>, which present example aspects of a wireless device <NUM> and network node <NUM> that are configured to carry out the techniques and methods presented above. <FIG> illustrates additional details of an example wireless device <NUM> of a wireless communication system <NUM> according to one or more embodiments. The wireless device <NUM> is configured, e.g., via functional means or units (also may be referred to as modules or components herein), to implement processing to perform certain aspects described above in reference to at least the aspects of <FIG> and <FIG> the related methods presented in <FIG> and <FIG>. As shown in <FIG>, the wireless device <NUM> in some embodiments for example includes means, modules, components, or units <NUM>, <NUM>, and <NUM> (among other possible means, modules, components, or units not shown explicitly in <FIG>) for performing aspects of these methods. In some examples, these means, modules, components, or units can be realized in processing circuitry <NUM>. Specifically, the functional means or units of the wireless device <NUM> may include a timing unit/module <NUM> configured to start and manage a timer for one or more HARQ processes, such as in block <NUM> of <FIG>. In addition, the wireless device <NUM> can include a HARQ policy unit/module <NUM> to identify a HARQ policy for one or more HARQ processes governing whether the wireless device <NUM> is to retransmit a TB or portion thereof, or transmit a new TB where no HARQ feedback responsive to the TB transmission is received from the network node before the timer expires, for example, as performed in block <NUM> of <FIG>, above. In addition, wireless device <NUM> may include a transmitting/retransmitting unit/module for retransmitting a TB or a portion thereof, or transmitting a new TB according to the HARQ policy at a next periodic transmission occasion for the HARQ process after the timer expires, for instance, as performed at block <NUM> in <FIG>.

In at least some embodiments, the wireless device <NUM> comprises one or more processing circuitry/circuits <NUM> configured to implement processing of the methods presented in <FIG> and <FIG> and certain associated processing of the features described in relation to other figures, such as by implementing functional means or units above. In one embodiment, for example, the processing circuit(s) <NUM> implements functional means or units as respective circuits. The circuits in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory <NUM>. In embodiments that employ memory <NUM>, which may comprise one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc., the memory <NUM> stores program code that, when executed by the one or more for carrying out one or more microprocessors, carries out the techniques described herein.

In one or more embodiments, the wireless device <NUM> also comprises communication circuitry <NUM>. The communication circuitry <NUM> includes various components (e.g., antennas) for sending and receiving data and control signals. More particularly, the circuitry <NUM> includes a transmitter that is configured to use known signal processing techniques, typically according to one or more standards, and is configured to condition a signal for transmission (e.g., over the air via one or more antennas). Similarly, the communication circuitry includes a receiver that is configured to convert signals received (e.g., via the antenna(s)) into digital samples for processing by the one or more processing circuits.

<FIG> illustrates additional details of an example network node <NUM> of a wireless communication system <NUM> according to one or more embodiments. The network node <NUM> is configured, e.g., via functional means or units (also may be referred to as modules or components herein), to implement processing to perform certain aspects described above in reference to at least the aspects of <FIG> and <FIG> the related methods presented in <FIG> and <FIG>. As shown in <FIG>, the network node <NUM> in some embodiments for example includes means, modules, components, or units <NUM>, <NUM>, and <NUM> (among other possible means, modules, components, or units not shown explicitly in <FIG>) for performing aspects of these methods. In some examples, these means, modules, components, or units can be realized in processing circuitry <NUM>. Specifically, the functional means or units of the network node <NUM> may include a timing unit/module <NUM> configured to configure a timer and/or a time period associated with the timer for a HARQ process associated with a TB transmission by a wireless device <NUM> to the network node <NUM>, such as in block <NUM> of <FIG>. In addition, the network node <NUM> can include a HARQ policy unit/module <NUM> to identify a HARQ policy for one or more HARQ processes governing whether the network node <NUM> is to retransmit a TB or portion thereof, or transmit a new TB where no HARQ feedback responsive to the TB transmission is received from the network node before the timer expires, for example, as performed in block <NUM> of <FIG>, above. In addition, network node <NUM> may include a receiving unit/module for receiving a retransmitted TB or a portion thereof, or receiving a new TB according to the HARQ policy at a next periodic transmission occasion for the HARQ process after the timer expires, for instance, as performed at block <NUM> in <FIG>.

In at least some embodiments, the network node <NUM> comprises one or more processing circuitry/circuits <NUM> configured to implement processing of the methods presented in <FIG> and <FIG> and certain associated processing of the features described in relation to other figures, such as by implementing functional means or units above. In one embodiment, for example, the processing circuit(s) <NUM> implements functional means or units as respective circuits. The circuits in this regard may comprise circuits dedicated to performing certain functional processing and/or one or more microprocessors in conjunction with memory <NUM>. In embodiments that employ memory <NUM>, which may comprise one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc., the memory <NUM> stores program code that, when executed by the one or more for carrying out one or more microprocessors, carries out the techniques described herein.

In one or more embodiments, the network node <NUM> also comprises communication circuitry <NUM>. The communication circuitry <NUM> includes various components (e.g., antennas) for sending and receiving data and control signals. More particularly, the circuitry <NUM> includes a transmitter that is configured to use known signal processing techniques, typically according to one or more standards, and is configured to condition a signal for transmission (e.g., over the air via one or more antennas). Similarly, the communication circuitry includes a receiver that is configured to convert signals received (e.g., via the antenna(s)) into digital samples for processing by the one or more processing circuits.

A computer program comprises instructions which, when executed on at least one processor of the network node <NUM> or wireless device <NUM>, cause these devices to carry out any of the respective processing described above. Furthermore, the processing or functionality of network node <NUM> or wireless device <NUM> may be considered as being performed by a single instance or device or may be divided across a plurality of instances of network node <NUM> or wireless device <NUM> that may be present in a given system such that together the device instances perform all disclosed functionality.

In an aspect, the wireless device <NUM> may correspond to any mobile (or even stationary) device that is configured to receive/consume user data from a network-side infrastructure, including laptops, phones, tablets, loT devices, etc. As recited above, the network node <NUM> may be any network device, such as a base station, eNB, gNB, access point, or any other similar device.

A computer program in this regard may comprise one or more code modules corresponding to the means or units described above.

Claim 1:
A method (<NUM>) performed by a wireless device (<NUM>) for managing transport block, TB, transmissions (<NUM>) by the wireless device (<NUM>) to a network node (<NUM>) at periodic transmission occasions (<NUM>), the periodic transmission occasions having a periodicity configured by the network node (<NUM>), the method comprising:
performing a transport block, TB, transmission (<NUM>) to the network node (<NUM>) in a first transmission occasion of the periodic transmission occasions;
starting (<NUM>) a timer for a hybrid automatic repeat request, HARQ, process associated with the TB transmission (<NUM>), the timer being started at the transmission of the TB;
identifying (<NUM>) a HARQ policy (<NUM>) for the HARQ process, wherein the HARQ policy (<NUM>) governs whether the wireless device (<NUM>) is to retransmit the TB or transmit a new TB where no HARQ feedback responsive to the TB transmission (<NUM>) is received from the network node (<NUM>) before the timer expires; and
responsive to determining that the timer has expired without receiving from the network node (<NUM>) HARQ feedback responsive to the TB transmission (<NUM>), retransmitting (<NUM>) the TB or transmitting the new TB according to the HARQ policy (<NUM>) at a next transmission occasion of the periodic transmission occasions (<NUM>) for the HARQ process.