First radio node, second radio node, and methods therein, in a wireless communications network

Abstract

A method performed by a first radio node for handling feedback for Hybrid Automatic Repeat Request Feedback (HARQ-FB) in a wireless communications network The method comprises determining (501) reception status associated with one or more transmissions scheduled from a second radio node. The method comprises transmitting (504) a HARQ-FB report to the second radio node. The HARQ-FB report is transmitted as encapsulated in a data transport block. The HARQ-FB report is indicative of the determined reception status. The HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

Description

[0001] FIRST RADIO NODE, SECOND RADIO NODE, AND METHODS THEREIN, IN A WIRELESS COMMUNICATIONS NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first radio node, a second radio node, and methods therein. In some aspects they relate to handling feedback for Hybrid Automatic Repeat Request (HARQ) data transmissions in a wireless communications network.

[0004] BACKGROUND

[0005] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0006] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0007] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0008] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0009] Background 5G user-plane protocols

[0010] The 5G user-plane architecture and protocols are illustrated by Error! Reference source not found.. A UE is connected over the air via a Uu protocol with a radio access network (RAN) gNB. The gNB may be separated into distributed unit (DU) and centralized unit (CU), connected via a F1 interface. The gNB is connected to a core network (ON) including the user-plane function (UPF). Typically, Internet Protocol (IP) data is transported via UE-gNB-UPF. The RAN protocol stack between UE and gNB includes the Service Data Adaptation Protocol (SDAP) protocol, for handling mapping of Quality of Service (QoS) flows as established by the UPF to data radio bearers (DRBs) as established by the gNB. The protocol data convergence protocol (PDCP) is among others responsible for encryption / integrity protection and handover forwarding and retransmission. For handovers between gNBs the Xn interface is employed. The radio link control (RLC) is among others responsible for segmentation of higher layer PDCP / IP data to fitting transport blocks (TBs) available for the lower layer over the air transmission. Also, retransmissions are based on automatic repeat request (ARQ) in acknowledged mode of RLC. A Medium Access Control (MAC) protocol supports scheduling of transmissions over the air, and entails a hybrid automated repeat request (HARQ) protocol. A physical layer (PHY) handles e.g. modulation and coding and the actual physical transmission.

[0011] Background on HARQ

[0012] In 3GPP radio access networks, e.g. 5G NR, the HARQ protocol facilitates retransmissions of data in case of transmission errors over the air.

[0013] For downlink HARQ, data transmissions are assigned by downlink control indicators (DCI) carried on the physical downlink control channel (PDCCH) and data is transmitted on the physical downlink shared channel (PDSCH). Different encoding is applied to these channels resulting in different error rates.

[0014] HARQ feedback (HARQ-FB), e.g., positive acknowledgement (ACK) or negative acknowledgement (NACK) of data reception from the UE is transmitted as uplink control information (UCI) either on the physical uplink control channel (PLICCH) or physical uplink shared channel (PLISCH) multiplexed with other uplink data.

[0015] This is since simultaneous transmission of PLICCH and PLISCH imposes challenges on the radio frequency (RF) implementation. Different encoding of these channels may result in different error rates, where transmission on PLICCH is typically more robust.

[0016] However, it is noteworthy that the transmissions on the PLISCH undergo the uplink HARQ protocol, i.e. are also subject to retransmissions to correct any decoding errors. Furthermore, the code rate for UCI on PUSCH can be adjusted by varying the number of resources for the UCI.

[0017] PUCCH

[0018] Besides HARQ-FB, the PUCCH may also carry scheduling requests and / or CSI reports. Due to carrier aggregation scheduling, the use of Code Block Groups (CBGs) and / or MIMO layers, the number of UCI bits and thus, the amount of resources for PUCCH may vary. To be optimized for different PUCCH payload sizes, different PUCCH formats (PF) were specified as summarized in Table 1 below.

[0019] Table 1

[0020] PUCCH format 4 differs from PUCCH format 3 in the use of orthogonal cover codes

[0021] (OCC) and is used for FR2-2. To minimize the UCI bits, a dynamic HARQ codebook is used by default, meaning that HARQ feedback resources are only allocated for Downlink (DL) transmissions that actually take place. If carrier aggregation and CBG transmission is used, the HARQ codebook size may become very large. If there are not enough PLICCH resources for simultaneous HARQ feedback and CSI transmission, the CSI is dropped.

[0022] UCI on PUSCH

[0023] When UCI is transmitted on PUSCH, up to two HARQ feedback bits are always punctured. If more HARQ feedback bits are transmitted on PUSCH, rate matching is used for the uplink data.

[0024] HARQ error cases

[0025] Since there is a probability that a UE misses a DCI / PDCCH carrying DL scheduling assignments, the UE would incorrectly calculate the HARQ codebook size. To solve this, downlink assignment index (DAI) counters are utilized in the DCI. The DAI field in the DCI indicates the amount of resources reserved for DL HARQ feedback. Thus, regardless of whether the device missed any previous scheduling assignments or not, the amount of resources, i.e. , the expected count of HARQ feedback bits to use for the DL HARQ-FB is known.

[0026] The UE sets bit positions to “NACK” which correspond to the missed DCIs such as missing DAI. Nevertheless, there is still an ambiguity as the gNB cannot distinguish whether a UE missed a DCI or a corresponding transport block, and usage of DAI comes with complexities in carrier aggregation scheduling on top of the use of Code Block Groups (CBGs) and MIMO layers, as these resources between individual carriers need to be coordinated.

[0027] Fig. 1 illustrates the use of counter DAI and total DAI. DCI misdetection and codebook size determination may be performed due to keeping track of DAI. The use of the counter DAI (cDAI) and total DAI (tDAI) in the DL DCI is illustrated in

[0028] Fig. 1 and allows the UE to detect missed DCIs and determine the HARQ codebook size for UCI transmission to the network. It should be noted that HARQ IDs in the example used in

[0029] Fig. 1 are used on different carriers for the sake of simplicity only. Each carrier can have its own set of HARQ processes and may thus use the same HARQ ID as another carrier. The top DAI pair in the first row denotes the actual cDAI / tDAI, while the bottom DAI pair assumes only 2 bits for the DAI transmission, and the cDAI / tDAI to be provided in the DCI is the actual cDAI / tDAI mod 4. The DCI further informs the UE about the time offset between DCI reception and HARQ feedback transmission.

[0030] Fig. 3 illustrates HARQ-FB provided in the UCI. The UE can provide the HARQ-FB as a bitmap. Based on the DAIs, the UE can calculate a size of the HARQ-FB bitmap and the bitmap positions for the corresponding HARQ ACK / NACKs. For missed DCIs, the UE sets NACK. Thus, a network cannot distinguish whether the UE had missed the DCI or whether it had been unable to decode the transport block.

[0031] Furthermore, if the gNB does not receive any HARQ-FB I UCI on PUCCH or PUSCH. In such a case, the gNB does not know whether the UE had missed the scheduling DCI or whether the UE transmitted HARQ feedback, which was however not detected by the gNB. Another approach that addresses the ambiguity is the one-time HARQ feedback request, which was introduced in the context of NR Unlicensed (NR-U). It gives the gNB the possibility to request the UE to send HARQ feedback for all HARQ processes. Other common failures of the downlink HARQ protocol are that transmission errors of the PUCCH lead to flipping of the transmitted HARQ feedback, e.g. from NACK to ACK, i.e. a false positive, or from ACK to NACK, i.e. a false negative. False negatives will lead to unnecessary retransmissions and thus, inefficient resource usage, and false positives can be addressed by the acknowledged mode (AM) of the RLC protocol.

[0032] HARQ timing

[0033] The slot timing between DL data transmission and HARQ feedback, denoted as K1, is determined based on the K1 field in DCI. K1=0 means that the HARQ-FB is provided in the same slot, K1=1 means that the HARQ-FB is provided in the next slot, etc.

[0034] For NR-U, a non-numerical K1 value can be used, indicating that the network has not yet decided when the UE shall send the HARQ-FB for a given HARQ process. Instead, the network can, at a later point of time, request a “one-shot” HARQ feedback for all (active / non-active) HARQ processes. When the UE receives such a HARQ-FB request, it sets the HARQ-FB bits to ACK for successfully decoded transport blocks, and all others to NACK. The ACKs are only flushed when the UE receives a toggled New Data Indicator (NDI) for that HARQ process. As in legacy, the NACK may indicate to the network that the UE either missed the DCI or that it unsuccessfully decoded the corresponding TB.

[0035] Radio Link Control

[0036] The RLC protocol, which resides on top of the HARQ protocol, in AM, is able to detect and correct HARQ residual errors. Therefore, RLC maintains its own state of which data packets are already successfully received. This is based on RLC status reporting from the receiver. Counters and timers are employed to poll, trigger and if needed retransmit RLC status reports and retransmit RLC data until reception success is ensured. RLC status reports are considered data in the HARQ protocol, meaning they undergo HARQ retransmissions in case of unsuccessful reception. The drawback of RLC retransmissions is increased latency.

[0037] SUMMARY

[0038] As a part of developing embodiments herein a number of issues with HARQ have been identified:

[0039] 1) Carrier aggregation: PUCCH overhead vs. increased latency for PUCCH allocation due to scheduling dependency for a Primary cell (PCell) and / or for Secondary Cells (SCell) can be inefficient,

[0040] 2) A size of PUCCH allocation may depend on scheduling decisions on PCell and / or SCell(s) may lead to a varying PUCCH allocation size increases decoding error probability,

[0041] 3) Ambiguity may be caused by missed DCI vs. missed Uplink (UL) HARQ,

[0042] 4) RLC retransmissions may happen due to feedback issues which may cause large delays. This may relate to that RLC retransmissions may be based on RLC timers, which are configured with delays allowing a certain number of HARQ retransmissions before triggering RLC retransmissions.

[0043] An object of embodiments herein may be to improve efficiency of HARQ-FB. In particular, the embodiments herein may relate to how a radio node such as a UE handles HARQ-FB to overcome or improve on some of the above-mentioned issues.

[0044] According to a first aspect, a method performed by a first radio node for handling HARQ-FB in a wireless communications network is provided. The first radio node may be a UE or any other suitable device. The method comprises determining reception status associated with one or more transmissions scheduled from a second radio node. The second radio node may be a network node such as a gNB or any other suitable device.

[0045] The method comprises transmitting a HARQ-FB report to the second radio node. The HARQ-FB report is transmitted as encapsulated in a data transport block. “As encapsulated” as used in examples herein may mean encapsulated, and vice versa. The HARQ-FB report is indicative of the determined reception status. The HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

[0046] According to a second aspect, a method performed by a second radio node for handling HARQ-FB in a wireless communications network is provided. The second radio node may be a network node such as a gNB or any other suitable device.

[0047] The method comprises triggering one or more transmissions from the second radio node to a first radio node. The first radio node may be a UE or any other suitable device. The method comprises receiving a HARQ-FB report from the first radio node. The HARQ- FB report is transmitted as encapsulated in a data transport block. The HARQ-FB report is indicative of the determined reception status. The HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information. Indicative as used herein with respect to the HARQ-FB report may mean that the referred to object, information, or feature may be comprised in the HARQ-FB report.

[0048] According to a third aspect, a first radio node configured to handle HARQ-FB in a wireless communications network is provided. The first radio node is configured to determine reception status associated with one or more transmissions scheduled from a second radio node. The first radio node is configured to transmit a HARQ-FB report to the second radio node. The HARQ-FB report is transmitted as encapsulated in a data transport block. The HARQ-FB report is indicative of the determined reception status. The HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ- FB information.

[0049] According to a fourth aspect, a second radio node configured to handle HARQ-FB in a wireless communications network is provided. The second radio node is configured to trigger one or more transmissions from the second radio node to a first radio node. The second radio node is configured to receive a HARQ-FB report from the first radio node. The HARQ-FB report is adapted to be transmitted as encapsulated in a data transport block. The HARQ-FB report is adapted to be indicative of the determined reception status. The HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ-FB information.

[0050] Since the HARQ-FB report is transmitted as encapsulated in a data transport block, this means that the HARQ-FB report is transmitted in a layer above a physical layer over a radio layer or other higher layer, i.e. , the transmission is over a non-physical layer. This means that there is more room to flexibly use and plan resources, and accordingly, this allows for a more dynamic and flexible HARQ-FB report. By using a non-physical layer, the HARQ-FB is more robust, e.g., by use of Cyclic Redundancy Check (CRC) and / or by possibility to perform retransmissions of the HARQ-FB report, which allows for improved performance, and thus, the HARQ-FB report may mitigate residual HARQ errors and the need for outer loop retransmission on RLC. The HARQ-FB report will indicate, e.g., comprise, a HARQ codebook or compressed HARQ-FB information. Due to the usage of the non-physical layer, the HARQ codebook or the compressed HARQ-FB information may be richer and / or of dynamical size as compared to HARQ-FB over a physical layer, which improves efficiency of handling HARQ and HARQ-FB, at least due to more efficient use of resources which will further be discussed below.

[0051] BRIEF DESCRIPTION OF DRAWINGS

[0052] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0053] Fig. 1 illustrates an architecture according to prior art.

[0054] Fig. 2 illustrates DAI counter usage according to prior art.

[0055] Fig. 3 illustrates HARQ usage according to prior art.

[0056] Fig. 4 illustrates a schematic block diagram illustrating embodiments of a wireless communications network.

[0057] Fig. 5 is a flowchart depicting embodiments of a method.

[0058] Fig. 6 is a flowchart depicting embodiments of a method.

[0059] Figs. 7a-b illustrates example scenarios of HARQ transmissions.

[0060] Fig. 8 illustrates an example scenario of an example embodiment.

[0061] Figs. 9a-b illustrates example scenarios of embodiments herein.

[0062] Fig. 10 illustrates an example scenario of an example embodiment.

[0063] Fig. 11 illustrates an example scenario of an example embodiment.

[0064] Fig. 12 illustrates an example scenario of an example embodiment.

[0065] Fig. 13 illustrates an example scenario of an example embodiment.

[0066] Fig. 14 illustrates an example scenario of an example embodiment.

[0067] Fig. 15 illustrates an example scenario of an example embodiment.

[0068] Fig. 16 illustrates an example scenario of an example embodiment.

[0069] Fig. 17 illustrates an example scenario of an example embodiment.

[0070] Fig. 18 illustrates an example scenario of an example embodiment.

[0071] Fig. 19 is a schematic block diagram illustrating embodiments of a first radio node.

[0072] Fig. 20 is a schematic block diagram illustrating embodiments of a second radio node.

[0073] Fig. 21 is a schematic block diagram illustrating embodiments of a communication system.

[0074] Fig. 22 is a schematic block diagram illustrating embodiments of a UE.

[0075] Fig. 23 is a schematic block diagram illustrating embodiments of a Network node.

[0076] Fig. 24 is a schematic block diagram illustrating embodiments of a Host.

[0077] Fig. 25 is a schematic block diagram illustrating embodiments of a Virtualization environment.

[0078] Fig. 26 is a schematic block diagram illustrates communications with a host in an example scenario.

[0079] DETAILED DESCRIPTION

[0080] As summarized above a number of issues associated with HARQ have been identified which will further be explained below.

[0081] One issue relates to carrier aggregation, e.g., PLICCH overhead vs. increased latency for PLICCH allocation due to scheduling dependency for PCell / SCell(s).

[0082] One issue relates to a size of resource allocation, e.g., PLICCH allocation depending on scheduling decisions on PCell / SCell(s). It follows that varying allocation size such as PLICCH allocation size increases a decoding error probability.

[0083] One issue relates to when a radio node such as a gNB receives NACK for a HARQ process as there is ambiguity whether the UE missed the DCI or whether it could not decode the data, e.g., DL data on PDSCH.

[0084] One issue relates to that if a radio node such as a gNB does not detect HARQ feedback for a transmission, e.g., downlink transmission, the radio node does not know whether it had missed the HARQ-FB, e.g., due to poor connection such as poor UL, or whether a corresponding radio node such as a UE did not send any feedback due to a misdetection of DCI

[0085] One issue relates to RLC retransmissions due to feedback issues that cause large delays.

[0086] Embodiments herein may relate to handling at least some of the above issues by transmitting a HARQ-FB report encapsulated in a data transport block. Encapsulated in a data transport block may mean that the HARQ-FB report is transmitted in a Medium Access Control Control Element (MAC-CE) or as part of a Radio Resource Control (RRC) message. In other words, the HARQ-FBreport may be transported in a radio layer such as Layer 2 (L2), or higher layers. This means that the HARQ-FB report may be mapped on resources / channels, e.g., PUSCH, with higher priority than if transmitted over a physical layer. This further means that in embodiments herein, the size of the HARQ-FB report may be dynamic as the size of the HARQ-FB may be dynamic when encapsulated in a data transport block being transmitted over L2. In embodiments herein, the size of the HARQ-FB may be indicated by any suitable header such as a MAC-CE header.

[0087] Transmission of HARQ-FB encapsulated in a data transport block e.g., on L2 allows for a flexible message size and content and thus allows for compressed HARQ-FB indicating e.g. {all ACK, all NACK, missed all DL assignments, MIX}. Additionally or alternatively all a pending decoding state (PENDING) or a mix including at least one PENDING state may also apply. The first three states may exploit characteristics of coherent channels in combination with continuous interference levels, and the last state (“MIX”) may cover spiky interference where interference may occur e.g. on orthogonal frequency-division multiplexing (OFDM) symbol level. The format for the extended HARQ- FB information may be dynamically chosen e.g., by any radio node such as a UE or may be pre-configured e.g., by the network.

[0088] Embodiments herein may provide a number of advantages as will be explained below. Some advantages will further be understood by the skilled person by the description.

[0089] HARQ-FB encapsulated in a data transport block, e.g., an L2 feedback message, is more robust than transmitting over a physical layer, e.g., as in prior art. This achieves better system performance: mitigates residual HARQ errors and the need for outer loop retransmission on RLC which would create higher layer packet delay

[0090] Using a higher level communication layer enables richer more detailed feedback information, i.e., as the size and content of the HARQ-FB and report thereof may be dynamic and set in a more flexible manner. In addition to retransmissions triggered by HARQ ACK / NACK, radio nodes may adapt missed control messages, e.g., where the network may adapt PDCCH in case of a missed DCI.

[0091] The HARQ-FB report may have variable size, meaning that it may be dynamically determined by radio nodes such as a UE, depending on the decoding outcome, and thereby the HARQ-FB report of embodiments herein may be more flexible and efficient with respect to the application usage.

[0092] Channel coherence, e.g., coherence of ACK / NACK / missed control messages such as DCI, may be exploited by embodiments herein to minimize the size of the FB message.

[0093] A further advantage may relate to that scheduling of the HARQ-FB may be made more flexible by using more flexible timing of when HARQ-FB shall be transmitted, such as by using a reverse time slot offset, the HARQ-FB can take place at any suitable time. With regards to embodiments herein, naming and / or some technological entities mentioned may be with reference to 5G standardization. However, the embodiments herein have been developed with the intention for being deployed in any future standardization, in particular with reference to the Sixth Generation telecommunications (6G) which may be seen as a suitable technology for embodiments herein. Hence, any naming or specific technology mentioned with reference to 5G or earlier generations of telecommunications may further also mean any corresponding name or technology applicable for future standards such as for 6G.

[0094] Fig. 4 is a schematic overview depicting a wireless communications network 100, wherein embodiments herein may be implemented. The wireless communications network 100 comprises one or more RANs and one or more CNs. The wireless communications network 100 may use 5G NR or may use a number of other different technologies, such as, 6G, Wi-Fi, (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0095] Network nodes operate in the wireless communications network 100. Each of the network nodes e.g. provides a number of cells and may use these cells for communicating with other network nodes. Each of the network nodes may be a transmission and reception point e.g. a network node, a radio access network node such as a base station, a radio base station, a NodeB, an evolved Node B (eNB, eNodeB, eNode B), an NR / g Node B (gNB), 6G radio access network function (RANF), a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a transmission arrangement of a radio base station, a stand-alone access point, a Wireless Local Area Network (WLAN) access point, an Access Point Station (AP STA), an access controller, a UE acting as an access point or a peer in a Device to Device (D2D) communication, or any other network unit capable of communicating with a UE served by the network node depending e.g. on the radio access technology and terminology used.

[0096] UEs operate in the wireless communications network 100. The UEs may respectively e.g. be an NR device, a mobile station, a wireless terminal, an internet of things (loT) device, an enhanced Machine Type Communication (eMTC) device, an NR RedCap device, a CAT-M device, a Vehicle-to-everything (V2X) device, Vehicle-to- Vehicle (V2V) device, a Vehicle-to-Pedestrian (V2P) device, a Vehicle-to-lnfrastructure (V2I) device, a Vehicle-to-Network (V2N) device, a Wi-Fi device, an LTE device, a non- access point (non-AP) STA, a STA, that communicates via a base station, and one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by the skilled in the art that the term UE relates to a non-limiting term which means any UE, terminal, wireless communication terminal, user equipment, (D2D) terminal, or node e.g. smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station communicating within a cell.

[0097] Radio nodes operate in the wireless communications network 100 such as a first radio node 1 and a second radio node 2. The first radio node 1 may be any suitable radio device, e.g., a UE or a network node as described above. The second radio node 2 may be any suitable radio device, e.g., a UE or a network node as described above. In other words, communications or transmissions herein may relate to Sidelink (SL), DL, and / or UL, associated with the first radio node 1 and the second radio node 2, in any suitable manner.

[0098] Methods herein may in one aspect be performed by the first radio node 1 and / or the second radio node 2. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in a cloud 190 as shown in Fig. 4, may be used for performing or partly performing the methods of embodiments herein. The cloud 190 may comprise a cloud network infrastructure. A cloud network infrastructure may e.g. be a collection of hardware and software elements such as computing power, networking, storage, and virtualization resources needed to enable cloud computing in a wireless communications network such as e.g. a communications network.

[0099] Transmission of HARQ-FB encapsulated in a data transport block, e.g., transmitted over L2, allows for flexible message size and content and may further allow for compressed HARQ-FB indicating e.g. {all ACK, all NACK, missed all scheduling assignments such as DL assignments, MIX}. Additionally or alternatively all PENDING may also apply or a mix including at least one PENDING state may also apply. The first three states may exploit characteristics of coherent channels in combination with continuous interference levels, and the last state (“MIX”) may relate to spiky interference where interference may occur e.g. on OFDM symbol level. The format for HARQ-FB information may be dynamically chosen or pre-configured, e.g., by the network.

[0100] Example and embodiments herein may typically relate to transmissions from a network node, e.g., the second radio node 2, to a UE, e.g., the first radio node 1. Hence, many example and embodiments may discuss communication in only a single direction, e.g., UL / DL, or associated channels or control information, e.g., DCI, or assignments, e.g., DAI. However, communication in any direction, e.g., using DL,SL or UL, is possible using HARQ and embodiments herein, and the specific directions of communication is only describes as a non-limiting example.

[0101] Using a data transport block, e.g., L2 communication, may allow for adding more information at lower cost, and / or may allow for mitigation of ambiguities due to missed Control Information (Cl), e.g., missed DCIs vs. missed UL feedback. As used herein, Cl may be DCI and / or UCI.

[0102] If a radio node, such as the first or second radio node 1 , 2, obtains information about missed control information, e.g., DCI, it may e.g. choose a larger transmission format, e.g., PDCCH format or DCI format 1_0, for better transmission robustness. In order for the first or second radio node 1 , 2, e.g., a UE, to detect missed control information such as DCI, the corresponding radio node 1,2, such as a network node, needs to transmit an assignment index, e.g., downlink assignment index (DAI) in the DL assignment.

[0103] An explicit indication in the HARQ-FB about missing control information such as DCIs is not needed if counters such as DAI counters are used and the number of HARQ- FB entries is indicated, e.g., by the network.

[0104] Additionally, or alternatively to implicit or explicit control information indication e.g., about a missed DCI, the first radio node 1 , such as a UE may indicate to the second radio node 2, such as a network node, that it is in the decoding process of a transport block for a certain HARQ ID. Thus, the second radio node 2, may obtain information that the control information, e.g., DCI, was received by the first radio node 1 , but the processing time for the decoding of the TB may last a bit longer. In other words, control information such as DCI for a HARQ process may have been correctly decoded and thus, the second network node 2 may not need to initiate any retransmission for that HARQ process until a corresponding ACK / NACK has been received. Also, the second radio node 2 may as a result determine that it cannot free up that HARQ process. The status bit to indicate that a decoding process is ongoing may further work without the use of assignment indices and their associated counters, e.g., DAI.

[0105] A number of embodiments will now be described, some of which may be seen as alternatives, while some may be used in combination.

[0106] A method according to embodiments will now be described from the view of the first radio node 1 together with Fig. 5. Fig. 5 depicts example embodiments of a method performed by the first radio node 1 for handling feedback for HARQ data transmissions, i.e. , HARQ-FB, in the wireless communications network 100. Any one or more actions below may be performed in response to receiving a HARQ-FB request from the second radio node 2. The first radio node 1 may also autonomously perform the below actions.

[0107] The method comprises any one or more of the following actions, which actions may be taken in any suitable order.

[0108] Action 501

[0109] In some embodiments, the method comprises determining reception status associated with one or more transmissions scheduled from a second radio node 2. The one or more transmissions may be any suitable data or control messages. The one or more transmissions may be the HARQ data transmissions as discussed above, or a subset thereof. The one or more transmissions may be managed by one or more corresponding HARQ processes.

[0110] The one or more transmissions may have been transmitted by the second radio node 2 and each transmission, respectively, may or may not have been received by the first radio node 1.

[0111] The one or more transmissions may be in DL, UL, or SL. Embodiments herein may typically refer to DL or UL, but any direction and corresponding resources or channels are applicable.

[0112] The reception status may relate to, for each of the one or more transmissions, an ACK, a NACK. In some embodiments herein, the status may also relate to any or both of: a missed scheduling assignment denoted in some embodiments as MISSED, and / or a pending decoding state, denoted in some embodiments as PENDING.

[0113] Action 502

[0114] In some embodiments, a HARQ codebook is used. In some of these embodiments, the method comprises obtaining an indication of a codebook size for the one or more transmissions.

[0115] The codebook size may be obtained in any suitable manner, e.g., the codebook size may be determined, e.g., based on any one or more out of:

[0116] DAI and / or tDAI counters,

[0117] Number of transmissions, e.g., out of the one or more transmissions detected by the first radio node 1 , identifiers of one or more transport blocks, e.g., bundles, transmitted from the second radio node 2, e.g., wherein the identifiers are received from the second radio node 2, and based on an indication received from the second radio node 2. The codebook size may in some embodiments be of a predetermined size, e.g., when being configured as a semi-static codebook it may be determined by number of HARQ processes configured in RRC or it may always have a set size of entries.

[0118] In some embodiments, the codebook size is dynamically determined by above determinations or based on explicit signalling, e.g., from the second radio node 2.

[0119] The codebook size may be entries in the HARQ codebook.

[0120] Action 503

[0121] In some embodiments, the method comprises obtaining control information from the second radio node 2.

[0122] The control information may be a HARQ-FB request from the second radio node 2 to the first radio node 1. Alternatively, such a request may be received separately.

[0123] Typically, HARQ-FB is requested together with a provided UL grant for UL resources and / or HARQ-FB is requested in a set slot n, and the first radio node 1 may use any suitable radio resources, e.g., contention-based access, or using a configured grant that occurs in slot n or later.

[0124] The control information may be associated with, e.g., it may indicate, how and / or when to transmit a HARQ-FB report to the second radio node 2. For example, the control information may indicate for which of the one or more data transmissions to provide HARQ-FB. The control information may in some scenarios be DCI but for other communication directions other control information apply. The control information may comprise timing information of when to transmit the HARQ-FB, e.g., which symbol or slot.

[0125] In some embodiments, the control information indicates a request of HARQ-FB from the second radio node 2. The HARQ-FB report may indicate reception status of one or more transmissions occurred in one or more prior slots to a current slot. The current slot may be indicated by the control information or the slot where the control information is received. The one or more prior slots may be indicated by a reverse time slot offset, e.g., transmitted by the second radio node 2 or otherwise obtained. In other words, the reverse time slot offset points to or indicates the first HARQ transmission of a HARQ transmission set. The reporting for HARQ transmissions may be omitted, e.g., if it is determined that the first radio node 1 would not be able to decode it by the time of transmitting the HARQ- FB. In these situations, the one prior slot before the current slot, would not be included in the HARQ-FB, e.g., saving one or potentially more entries. If the processing takes e.g. 3 slots, the 3 prior slots may not be included in the HARQ-FB message. Obtaining control information may comprise receiving an indication of the reverse time slot offset as transmitted from the second radio node 2. The reverse time slot may be indicated by an offset KT.

[0126] The control information may further comprise any other suitable control information, e.g., DCI or UCI.

[0127] Action 504

[0128] In some embodiments, the method comprises transmitting a HARQ-FB report to the second radio node 2. The HARQ-FB report is transmitted as encapsulated in a data transport block, e.g., in a non-physical communication layer, e.g., a radio layer such as layer 2. The term “as encapsulated in a data transport block” may mean that the HARQ- FB is transmitted in any suitable data transport block or other messaged for transmitting data which is not directly relating to signalling on a lowest layer of communication. Using a data transport block for transmitting the HARQ-FB report ensures flexibility and more efficient use of resources.

[0129] The HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

[0130] The HARQ-FB report may be transmitted using MAC or RRC.

[0131] The HARQ-FB report is indicative of the determined reception status.

[0132] In some examples,, the size of the HARQ-FB report is dynamic. However, the HARQ-FB report may also be fixed in size, e.g., by a predefined size.

[0133] Dynamic may mean that the size of the HARQ-FB report is dependent of several factors, among which the reception status of the received HARQ data is considered. For example, only 2 bits may indicating all ACK, all NACK, all MISSED, MIX, rather than the reception status for each transmitted HARQ process. Additionally or alternatively all PENDING may also apply or a mix including at least one PENDING state may also apply.

[0134] Since the HARQ-FB report is transmitted over a non-physical layer, e.g., using MAC or RRC, the HARQ-FB report can be transmitted in a more flexible manner. This is since using layers higher up in the abstraction than the physical layer, it is possible to more dynamically determine size of payloads and / or when to transmit. Hence, the HARQ-FB report can be more dynamic and flexible in its transmission.

[0135] The compressed HARQ-FB information may be indicative of a HARQ codebook or compressed and / or otherwise encoded HARQ-FB information. The compression may be performed in any suitable manner. E.g., if 30% are ACK or mostly ACK this may be indicated by a few selected bits instead of bits per HARQ process. The compression may for example indicate the number of ACKs, e.g. 5 ACKs, e.g., out of 16, using x bits e.g., 4 bits.

[0136] When the HARQ-FB report is indicative of the HARQ codebook, the HARQ-FB report may further indicate: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, e.g., a number of HARQ codebook entries, and an indication of HARQ-FB information indicated, e.g., conveyed, by the HARQ codebook.

[0137] In some embodiments, the HARQ codebook indicates for each of the one or more transmissions, ACK, or NACK, e.g., using 1 bit. In some embodiments, the HARQ codebook indicates, e.g., using 2 bits, for each of the one or more transmissions, an ACK, a NACK, or any or both of: a missed scheduling assignment, and / or a pending decoding state. In other words, the codebook may be used in many different manners, and indicate different reception status.

[0138] In some embodiments, the HARQ codebook further indicates a HARQ-ID for each of the one or more transmissions.

[0139] In some embodiments, the HARQ codebook indicates for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0140] In some embodiments, the HARQ-FB information indicates at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers, e.g., by indicating the at least one corresponding reception status of the respective multiple carriers in a single HARQ codebook entry of the HARQ codebook. The respective reception status may be for the respective HARQ processes / transmissions on the respective multiple carriers.

[0141] For example, there could be one HARQ codebook per carrier, a common HARQ codebook across multiple carriers, e.g., using a (carrier) pool ID, or it could be as used in legacy implementations. One single HARQ codebook for all carriers may also be used, e.g., all carriers in one pool so that no pool ID is needed.

[0142] In some embodiments, the HARQ codebook is a dynamic HARQ codebook.

[0143] In some embodiments, the HARQ-FB report comprises a dynamic HARQ codebook which size is determined based on the obtained codebook size. Transmitting the HARQ codebook may therefore comprise transmitting the HARQ codebook with a size based on the obtained codebook size. In some embodiments, transmitting the HARQ-FB report is based on the control information.

[0144] In some embodiments, the HARQ-FB report is indicative of reception status of one or more transmissions for each code block group and / or code block bundle associated with the one or more transmissions.

[0145] In some embodiments, when the HARQ-FB report is indicative of the compressed HARQ-FB, wherein the reception status indicates any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, all PENDING for the one or more transmissions, that all scheduling assignments for the one or more transmissions were missed, or a mix of any one or more out of:

[0146] - one or more ACKs for the one or more transmissions,

[0147] - one or more NACKs for the one or more transmissions,

[0148] - one or more PENDING states for the one or more transmissions, and

[0149] - one or more missed scheduling assignment for the one or more transmissions.

[0150] A method according to embodiments will now be described from the view of the second radio node 2 together with Fig. 6. Fig. 6 depicts example embodiments of a method performed by the second radio node 2 for handling feedback for HARQ data transmissions, i.e., HARQ-FB in the wireless communications network 100.

[0151] The method comprises any one or more of the following actions, which actions may be taken in any suitable order. All features of actions 501-504 may also apply to below actions in a corresponding manner.

[0152] Action 601

[0153] In some embodiments, the method comprises triggering one or more transmissions, e.g., SL, DL, or UL from the second radio node 2 to a first radio node 1. Triggering the one or more transmissions may comprise scheduling or transmitting the one or more transmissions, or may comprise trigger another radio node or scheduler to do so. The one or more transmissions corresponds to the one or more transmission of actions 501-502 above.

[0154] Action 602

[0155] In some embodiments, the method comprises transmitting control information to the first radio node 1 , e.g., as in actions 502-503. The control information may be associated with or indicate how and / or when to transmit a HARQ-FB report. The control information may indicate for which one or more data transmissions to provide HARQ-FB.

[0156] The control information may be a HARQ-FB request from the second radio node 2 to the first radio node 1. Alternatively, such a request may be transmitted separately.

[0157] In some embodiments, the control information indicates a request of HARQ-FB from the second radio node 2. The request may indicate that a transmitted HARQ-FB report shall be indicative of reception status of one or more transmissions occurred in one or more prior slots of a current slot. The second radio node 2 may indicate the one or more prior slots by a reverse time slot offset KT. Optionally, transmitting the control information further may comprises transmitting an indication of the reverse time slot offset to the first radio node 1. I.e., the reverse time slot offset may be transmitted with the control information or as a separate request.

[0158] While the reverse time slot offset indicates a slot offset, it also applies to any granularity, e.g., it may be a symbol offset or an offset of any unit that may apply for future standards.

[0159] The control information may further comprise any other suitable control information, e.g., DCI or UCI.

[0160] Action 603

[0161] In some embodiments, the method comprises receiving a HARQ-FB report from the first radio node 1 , e.g., as transmitted in action 504.

[0162] Features describing the HARQ-FB and associated report as in Action 504 may apply to action 603.

[0163] The HARQ-FB report may be transmitted as encapsulated in a data transport block. The HARQ-FB report may be indicative of the determined reception status. The size of the HARQ-FB report may be dynamic. The HARQ-FB report may also be fixed in size.

[0164] The HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

[0165] When the HARQ-FB report is indicative of the HARQ codebook, the HARQ-FB report may further indicate: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, e.g., a number of HARQ codebook entries, and an indication of HARQ-FB information indicated by the HARQ codebook. In some embodiments, the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0166] In some embodiments, the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0167] In some embodiments, when the HARQ codebook further indicates a HARQ-ID for each of the one or more transmissions.

[0168] In some embodiments, the HARQ codebook indicates for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0169] In some embodiments, the HARQ-FB information indicates at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers, e.g., by indicating the at least one corresponding reception status of the respective multiple carriers in a single HARQ codebook entry of the HARQ codebook.

[0170] In some embodiments, the received HARQ-FB is based on the control information, e.g., received as triggered or requested by the control information.

[0171] In some embodiments, the HARQ-FB report is indicative of reception status of one or more transmissions for each code block group and / or code block bundle e.g., as part of a HARQ process, associated with the one or more transmissions.

[0172] In some embodiments, when the HARQ-FB report is indicative of the compressed HARQ-FB, wherein the reception status indicates any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, all PENDING for the one or more transmissions, that all scheduling assignments for the one or more data transmissions were missed, or a mix of any one or more out of:

[0173] - one or more ACKs for the one or more transmissions,

[0174] - one or more NACKs for the one or more transmissions,

[0175] - one or more PENDING states for the one or more transmissions, and

[0176] - one or more missed scheduling assignment for the one or more transmissions. Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0177] In examples below, when discussing HARQ-FB may refer to any feedback information as part of the HARQ-FB report as discusses in actions above.

[0178] HARQ-FB report contents and structure

[0179] A HARQ-FB report of examples herein may be sent on L2 or in a data transport block, e.g., as in action 204, as a MAC control element (CE) and thus mapped on PLISCH with higher priority.

[0180] Transmission of HARQ-FB on L2 or in a data transport block may allow for flexible message size and content and thus allows for compressed HARQ-FB indicating e.g. {all ACK, all NACK, missed all DL assignments, MIX}. Additionally or alternatively all PENDING may also apply or a mix including at least one PENDING state may also apply.

[0181] The first three states may exploit characteristics of coherent channels in combination with continuous interference levels, and the last state (“MIX”) covers spiky interference where interference may occur e.g. on OFDM symbol level. The format for the extended HARQ-FB information may be dynamically chosen by the first radio node 1 , e.g., a UE, or pre-configured, e.g., by the second radio node 2.

[0182] Content of the HARQ-FB report, e.g., as in action 504 and 603 may be described as option 1 or 2 below.

[0183] Option 1 : HARQ codebook as part of the HARQ-FB report may comprise any one or more out of the following:

[0184] 1. Time reference: a. (Transmission / HARQ bundle) ID and / or SN of when the HARQ transmission was performed (may contain more) - and / or b. how a receiver interprets the time when the report was sent

[0185] 2. Length indicator for the HARQ-FB information (list size) a. The size comprises all HARQ processes for which the UE has not yet provided HARQ-FB b. The size is indirectly provided by the network by using a i. HARQ process bundle ID or ii. Reverse time offset K1’: if the first radio node 1 receives a HARQ- FB request in slot n, the first transmission slot for which to provide HARQ-FB is slot n-K1’-1

[0186] 3. List of HARQ feedback information a. If DAI is used (list size derived from cDAI / tDAI): i. HARQ FB (1 or 2 bits)

[0187] • 1 bit: ACK / NACK

[0188] • 2 bits: ACK / NACK / PENDING / reserved /

[0189] • MISSED indicates that the first radio node 1 missed the Control information, e.g., DCI carrying the DL scheduling assignment from the second radio node 2. b. If no DAI is used (,e.g., first radio node 1 not aware of missed control information, e.g., DCIs): i. HARQ ID (number of bits depends on the number of HARQ processes) ii. HARQ FB (1 or 2 bits)

[0190] • 1 bit: ACK / NACK

[0191] • 2 bits: ACK / NACK / PENDING / reserved

[0192] PENDING: if “early reporting” supported and if the first radio node 1 indicates that it has received the control information, e.g., DCI (opposite of DCI misdetection that the first radio node 1 is not aware of without DAI usage).

[0193] Option 2: compressed HARQ- as part of the HARQ-FB report may comprise any one or more out of the following:

[0194] Instead of sending a list of HARQ-FB information (step 3 of option 1), the HARQ feedback may can be compressed and comprised in the HARQ-FG report as follows:

[0195] • 2 bits indicating: {all ACK, all NACK, no control information received, DCIs received, MIX}

[0196] • If all ACK, All NACK, no DCIs received: no additional information

[0197] • Else if MIX: add extended information (HARQ-FB list, i.e. HARQ codebook, see step 3 in option 1)

[0198] Use of shorter TTIs, e.g. HARQ transmissions on OFDM symbol level

[0199] With regards to option 1 or 2 above, the same content in the HARQ-FB report as previously described applies, However, in some embodiments, the time reference may have a different granularity, e.g. symbol level time offsets instead of time offsets on slot level.

[0200] Use of Code Block Groups or Code Block Bundles

[0201] In some embodiments, HARQ-FB may further be provided in the HARQ-FB report for each code block group I code block bundle of a HARQ process. The HARQ process may be associated with the one or more transmissions as discussed with regards to the actions above. This scheme may benefit more from compression schemes due to higher level of coherence between OFDM symbols and thus, there is increased probability for “all ACK” or “all NACK”. In some embodiments, “all MISSED” may also be applicable if a connection robustness is poor, e.g., if PDCCH robustness is detected to have a quality below a threshold.

[0202] Use of HARQ codebooks

[0203] Embodiments herein may relate to transmitting HARQ-FB over non-physical layers. Hence, any suitable HARQ codebook may be used.

[0204] Any one of the following may be used:

[0205] Semi-static HARQ codebook. As a baseline, a semi-static HARQ codebook may be used, i.e. the size is dependent on the number of configured HARQ processes. The number of HARQ processes may be independent of the number of transmissions of actions 501 or 601.

[0206] Dynamic HARQ codebook. In order to reduce the reporting overhead of the HARQ-FB report, the second radio node 2 may request HARQ-FB for a subset of the HARQ processes using different possibilities.

[0207] Autonomous mode

[0208] The first radio node 1, optionally being a UE, may transmit HARQ-FB, e.g., as part of action 504, at pre-configured times or at the first possible occasion. The first radio node 1 may provide ACK / NACK or optionally MISSED / PENDING for all HARQ processes that it has attempted to decode. When it sends PENDING, the first radio node 1 may still be the process of decoding the one or more transmission, or when it sends MISSED, the first radio node 1 may not have received any related control information, e.g., no missed DCI detected by DAI usage. If the status changes from PENDING to ACK / NACK, the first radio node 1 may include the updated FB in the next HARQ-FB transmission occasion, e.g., as in a subsequent HARQ-FB report according to action 504.

[0209] HARQ-FB timing and HARQ processes to report

[0210] For HARQ-FB provisioning in autonomous mode: The first radio node 1 may autonomously indicate the HARQ-FB report to the second radio node 2, either using a dynamic FB grant from the second radio node 2 without any restriction on the HARQ codebook size, a configured grant, or when the first radio node 1 receives a grant for data, e.g., an UL grant for data. The first radio node 1 keeps track of the HARQ processes, i.e., transmissions, for which it has already provided a FB report.

[0211] Using a reverse time offset KT: The second radio node 2 may indicates in control information, e.g., DCI, together with a HARQ-FB request, the first slot for which it wants to receive HARQ-FB(s) from the first radio node 1.

[0212] Using HARQ process bundle ID: The second radio node 2 may bundle a set of HARQ processes, e.g., associated with a number of transmissions of the one or more transmissions, and associate them in the control information, e.g., as in actions 503 and 602, such as DCI with an associated bundle ID. The second radio node 2 may further request HARQ-FB for a certain bundle ID. Alternatively, the first radio node 1 may send, at a pre-configured grant, HARQ-FB for a certain bundlelD indicating that bundlelD in the HARQ-FB report, e.g., in an associated MAC-CE.

[0213] In some embodiments herein, the HARQ transmissions, e.g., the one or more transmissions or HARQ transmissions related to the one or more transmissions, will be similar to the 5G specification, i.e. the second radio node 2 may provide HARQ IDs and DAI counters, e.g., counter DAI and optionally, total DAI, with each scheduling assignment such as DL scheduling assignment. The first radio node may build a MAC-CE containing a HARQ codebook or use any other data transport block. In this variation, the first radio node 1 may only send the HARQ-FB, but it does not explicitly send the corresponding HARQ IDs. Those may be implicitly conveyed by the position of each HARQ-FB entry within the HARQ codebook.

[0214] New aspects if the HARQ-FB is provided in a data transport block, e.g., on L2, rather than on the physical layer, e.g., Layer 1 (L1), such as PUCCH or UCI on PUSCH, is that more information, i.e., more HARQ-FB states, may be provided. UCI may need to be pre-determined based on tDAI. Furthermore, UCI needs to be as small as possible to minimize a number of resources to be blocked for PUCCH. For example, the transmission in a data transport block such as on L2 allows the transmission of one additional bit per HARQ process or transmission to provide richer information to the second radio node 2, such that control information, e.g., DCI carrying DL scheduling assignment(s), was missed for a certain HARQ process rather than simply sending a NACK for missed DCIs. Another aspect is that using a data transport block, e.g., L2, for the HARQ-FB report may allow more flexible timing for the HARQ-FB transmission by using dynamic grants, e.g., similar as non-numerical K1 introduced for NR-ll, to request HARQ-FB.

[0215] Fig. 7a illustrates an example scenario where the second radio node 2 performs HARQ transmissions, e.g., the one or more transmissions, to the first radio node 1 using HARQ processes. HARQ-FB for the HARQ transmissions is encapsulated in a data transport block and carried on a data channel towards the second radio node 2, e.g., as in action 504. The HARQ-FB may be transmitted autonomously by the first radio node 1 , e.g., as part of the HARQ-FB report in action 504, using pre-configured or contentionbased radio resources. The first radio node 1 may need to include sufficient information in the HARQ-FB report so that the second radio node 2 may associate the communicated HARQ-FB with the corresponding transmissions. Alternatively, a control message from the second radio node 2 to the first radio node 1 may be transmitted, e.g., as part of action 601 or 602. The control message may schedules data resources carrying data and / or the HARQ-FB. The control message includes timing information and / or a bundle ID to define the HARQ transmissions to be associated with the HARQ-FB. The first radio node 1 may transmit the HARQ-FB in accordance with the control message from the second radio node 2.

[0216] Fig. 7b illustrates example communication between the first radio node 1 and the second radio node 2. The communication may be in UL, SL, or DL. The second radio node 2 may perform / transmit / schedule HARQ transmissions, e.g., the one or more transmissions, to the first radio node 1 using HARQ processes. HARQ-FB for the HARQ transmissions is encapsulated in a data transport block and may be carried on a data channel towards the second radio node 2, e.g., as part of action 504 / 603. A control message from the second radio node 2 may be transmitted to the first radio node 1 , e.g., as part of any of actions 601-602. The control message may schedule data resources carrying data and / or the HARQ-FB. The control message may include timing information and / or a bundle ID to define the HARQ transmissions, e.g., the one or more transmissions, to be associated with the HARQ-FB. The first radio node 1 may transmit the HARQ-FB in accordance with the control message from the second radio node 2, e.g., as part of action 504 / 603.

[0217] Fig. 7c illustrates example communication between the first radio node 1 and the second radio node 2. The communication may be in UL, SL, or DL. The second radio node may schedule / transmit / perform HARQ transmissions, e.g., the one or more transmissions, to the first radio node 1 using HARQ processes. Control Information (Cl) may optionally contain further information, e.g. bundle ID to determine the set of HARQ transmissions / processes. The Cl may comprise UCI or DCI. HARQ-FB for the HARQ transmissions is encapsulated in a data transport block and may be carried on a data channel towards the second radio node 2, e.g., as part of action 504 / 603. The HARQ-FB may be transmitted autonomously by the first radio node 1 using pre-configured or contention-based radio resources. If no Cl is provided, i.e., transmitted or otherwise indicated, from the second radio node 2 during the HARQ transmissions, then the first radio node 1 may need to include sufficient information, e.g., a HARQ ID or bundle ID, so that the second radio node may associate the HARQ-FB with the corresponding transmissions or, there need to be pre-configured or specified association rules e.g., for pre-configured or specified rules for associating the HARQ-FB with the HARQ transmissions. For example, if a HARQ-FB message is transmitted, it may include HARQ- FB for a latest (fully) received bundle ID, e.g., assuming e.g. always 4 HARQ transmissions or slots within a bundle. As a second example, if a HARQ-FB message is transmitted, it may use a pre-configured, e.g., RRC, or pre-defined KT value to determine a first HARQ transmission.

[0218] HARQ codebook variations

[0219] As in 5G, it is possible to use a semi-static HARQ codebook with a semi-static list size or a dynamic HARQ codebook with a dynamic list size, which varies depending on actual HARQ transmissions.

[0220] Semi-static HARQ codebook

[0221] The first radio node 1 may build or establish a MAC-CE or other data transport block containing one HARQ-FB list for all configured carriers. The list size for each carrier is determined by the number of HARQ processes configured for the corresponding carrier. For each entry, which corresponds to one HARQ process, the first radio node 1 provides HARQ-FB may provide described below.

[0222] Dynamic HARQ codebook

[0223] In order to avoid transmitting redundant HARQ-FB for inactive HARQ processes, a dynamic HARQ codebook was already introduced for 5G. If the parameter K1 is transmitted for each scheduling assignment, e.g., DL assignment, the first radio node 1 can use K1 and the DAI counters to derive the number of HARQ-FB entries in the HARQ codebook.

[0224] In the HARQ-FB of embodiments herein, the first radio node 1 may include a size / length indicator, e.g., depends on #HARQ processes, to indicate a number of HARQ- FB entries in the HARQ codebook. In some embodiments, if the second radio node 2 provides a dynamic grant, e.g., UL grant, for the HARQ-FB, the second radio node 2 may additionally indicate the HARQ codebook size, which would correspond to the tDAI and thus, add extra redundancy to avoid any ambiguity. This may mainly protect the case where all control information such as DCIs are missed in all slots or at least in the last slot.

[0225] For example, if 4 transmissions in a row are missed, e.g. slot n-1 , with 2-bit DAI in DL DCI, the first radio node 1 may create a HARQ codebook with size 7 instead of size 11.

[0226] In another embodiment, illustrated in Fig. 8, the second radio node 2 may only provide the HARQ codebook size in a dynamic grant such as a dynamic UL grant. The tDAI does not need to be sent in every scheduling assignment, e.g., every DL scheduling assignment, and thus, the Cl overhead, e.g., for DCI, may be reduced. Even though the first radio node 1 may not notice quickly that it had missed a Cl, e.g., DCI, it may not be important for the first radio node 1 as HARQ-FB information may still be useful for the second radio node 2. Fig. 8 illustrates a codebookSize provided in the HARQ-FB request instead of tDAI in DL assignments.

[0227] Feedback content of the HARQ-FB report

[0228] The following may be comprised in the HARQ-FB report, e.g., as part of action 504 / 603, e.g., as transmitted over L2 and / or in a data transport block.

[0229] • Carrier ID, e.g., if multiple carriers are activated, or pool ID, described further below,

[0230] • HARQ-FB information, e.g., any ACK / NACK / MISSED / PENDING or other HARQ-FB information, e.g., as in action 504, such as:

[0231] - HARQ codebook as described above or below, or

[0232] - compressed HARQ-FB, e.g., {all ACK, all NACK, all DCIs missed, mix} and if MIX, extended HARQ-FB such comprising a HARQ codebook, as described above or below,

[0233] The HARQ codebook may comprise entries as described below. The entries may be for the one or more transmissions, e.g., as in action 501. Which HARQ codebook format to use may be fixed as per specification, partially, pre-configured or dynamically configured by the second radio node 2, or dynamically chosen by the first radio node 1. The first radio node 1 may select the smallest possible format, e.g. the first radio node 1 may prioritize the compressed HARQ-FB whenever possible. For the extended report, the format may be pre-configured or dynamically configured by the second radio node 2, or a suitable format may be dynamically chosen by the first radio node 1 and may be indicated to the second radio node 2 using a format field for the HARQ codebook. Which HARQ codebook format to use may be based on whether the second radio node 2 is configured to use DAI counters or not.

[0234] Below follows Variations 1-7 defining HARQ-FB information as part of the HARQ codebook, e.g., per entry of said codebook. The Variations 1-7 may be different embodiment which are combinable with each other and other embodiments when suitable.

[0235] Variation 1 : a 1-bit HARQ-FB conveys {ACK, NACK} and may be a legacy scheme. For missed Cis such as DCIs, the first radio node 1 may set the HARQ-FB to NACK, and thus, the second radio node 2 cannot distinguish between NACK and missed Cis. Fig. 9a illustrates variation 1 where HARQ ID is implicitly derived, e.g., by being mapped to an entry or entry position, and 1-bit HARQ-FB entries indicates ACK or NACK.

[0236] Variation 2: a 2-bit HARQ-FB conveys {ACK, NACK, MISSED, reserved}. The first radio node 1 may detect missed Cis, e.g., DCIs, by evaluating received counter / total DAI values, e.g., as part of action 501. The HARQ state “missed” allows the second network node 2 to distinguish between missed Cis and unsuccessfully decoded TBs and thus, the second radio node 2 may take corresponding measures, e.g. more robust DCI transmission in case of a missed DCI. Fig. 9b illustrates variation 2 where HARQ ID is implicitly derived and 2-bit HARQ-FB entries indicates: ACK, NACK, MISSED, or reserved.

[0237] Variation 3: a 2-bit HARQ-FB conveys {ACK, NACK, PENDING, reserved}. The HARQ-FB “PENDING” indicates to the second radio node 2 that the first radio node 1 has successfully decoded Cl, e.g., DCI carrying the DL assignment, but is still in the decoding procedure of a TB, e.g., of the one or more transmissions e.g., as in action 501. Such information may help a scheduler, e.g., of the second radio node 2, to plan resources such as downlink resources accordingly. For unused HARQ processes, the first radio node 1 may set the HARQ-FB to NACK. Fig. 10 illustrates variation 3 where HARQ ID is implicitly derived and 2-bit HARQ-FB entries indicates: ACK, NACK, PENDING, or reserved.

[0238] Variation 4: a 2-bit HARQ-FB conveys {ACK, NACK, MISSED, PENDING}. This variation may provide extra redundancy in the HARQ-FB information of the HARQ-FB report. This may be useful if the first radio node 1 is requested to send the HARQ-FB, while the second radio node 2 does not know how long the first radio node 1 needs for decoding the one or more transmissions. Variation 5: Some or each entry of the HARQ code book may comprises a HARQ ID + a 2-bit HARQ-FB for each entry {ACK, NACK, MISSED, reserved}. In this variant, the codebook size may be determined using the tDAI. In addition to the HARQ-FB, the first radio node 1 also provides the HARQ ID in each entry. For missed Cis such as DCIs, the HARQ ID remains unknown to the first radio node 1 , so in these cases it may need to include a dummy HARQ ID with the MISSED indication. Fig. 11 illustrates variation 5 where HARQ ID is explicitly indicated and 2-bit HARQ-FB entries indicates, ACK, NACK, MISSED, or reserved.

[0239] Variation 6: A codebook size may be determined by the first radio node 1, e.g., based on a HARQ ID + 1 -bit HARQ-FB indicating ACK or NACK. Using this variation 6, the codebook size may depend on the number of transmissions, e.g., out of the one or more transmissions, the first radio node 1 has detected, e.g., detection may be part of action 501. Any missed Cis such as DCIs may not be included in the HARQ codebook. This variation 6 does not require the use of any DAI counters. In the assumption that the HARQ-FB is requested e.g., after the first radio node 1 decoding times out, or after some set time period or after a set number of slots, the second radio node 2 may derive from missing HARQ IDs that the first radio node 1 did not detect corresponding scheduling assignments such as DL scheduling assignments. Each entry of the HARQ codebook may also comprise HARQ-ID in addition to the HARQ state, e.g., ACK or NACK, this variation 6 may require more overhead than other variations, but as the HARQ-FB report is transmitted encapsulated in a data transport block, e.g., as an L2 feedback message, the message size and content may be flexible, i.e. doesn’t need to be limited to a fixed set of defined options as in L1 physical layer message. Furthermore, the L2 message content may be encoded thus redundancy may be reduced. Fig. 12 illustrates variation 6 where HARQ ID is explicitly indicated and 1 -bit HARQ-FB entries indicates, ACK, or NACK.

[0240] Variation 7: Multiple carriers may use a common set of HARQ processes. The HARQ-FB report may then comprise any one or more out of the following:

[0241] • A carrier pool ID, e.g., if multiple carriers are activated,

[0242] • A list containing following content per entry:

[0243] HARQ ID

[0244] - HARQ-FB, e.g., ACK, NACK and / or any other suitable reception status.

[0245] HARQ-FB timing and HARQ group determination In order to allow the second radio node 2 to grant HARQ-FB transmission more flexibly, the second radio node 2 may optionally use a non-numerical K1 similar as in NR- II. In order to avoid a semi-static codebook, a time reference may need to be provided, e.g., by the reverse slot time offset, e.g. KTto identify the HARQ processes, i.e. , which of the one or more transmissions, for which the second radio node 2 requests HARQ-FB.

[0246] Option 1 : The autonomous HARQ-FB reporting of the first radio node 1, e.g., being a UE. The first radio node 1 autonomously indicates the HARQ-FB report to the second radio node 2, e.g., as part of action 504, either using a dynamic FB grant from the second radio node 2 without any restriction on the HARQ codebook size, a configured grant, or when the first radio node 1 receives a grant for data, e.g., a UL grant. The first radio node 1 may be configured to track the HARQ processes, e.g., which transmissions of the one or more transmissions, for which it has already provided a FB report to the second radio node 2. If no timing relation is provided, e.g., by the second radio node such as in the control information of action 602, the first radio node 1 may need to send HARQ IDs together with the HARQ-FB.

[0247] In some embodiments, there is a specified timing relation, e.g. depending on the first radio node 1 category such as a UE category, or a pre-configured timing relation between the time where the HARQ-FB report is sent and to which HARQ processes, e.g., which one or more transmissions, it is associated. For example, if the first radio node 1 establishes and sends a HARQ-FB report in a slot n, it may include all HARQ processes for which it has received an assignment, e.g., DL assignment, starting from slot (n-8) to slot (n-1). If no HARQ IDs are included in the report, a DAI mechanism may need to be sent in Cis such as DCIs, which are arranged to schedule data, e.g., DL data, and / or grants, e.g., UL grant, for the HARQ-FB report. However, such a free / dynamic timing relation may be error-prone whenever a messages cannot be correctly decoded by the second radio node 2.

[0248] Option 2: Using a “reverse” slot timing KT, e.g., as indicated in actions above. The reverse slot timing, denoted as KT, may be arranged to point to a first HARQ transmission for which to provide HARQ-FB. The last HARQ to report for is 1 slot before the reception of the HARQ-FB request. If the first radio node 1 receives HARQ-FB request in slot n, then the first radio node 1 may transmit HARQ-FB in the HARQ-FB report for all scheduled data it received from slot n-K1’-1 to slot n-1.

[0249] Fig. 13 illustrates reverse slot timing KT to indicate the HARQ transmissions for which to provide HARQ-FB according to some embodiments herein. While a standard K1 parameter may count forward to the future from the Cl, e.g., DCI, where the HARQ transmission is performed, KT may count backwards to the past from the Cl where the Cl contains a HARQ-FB request. Since the first radio node 1 may be capable of obtaining or determining its processing time, the first radio node 1 may alternatively skip all slots for which it had not been able to finalize the decoding, e.g., as illustrated in Fig. 14. Fig. 14 illustrates a reverse slot timing KT and end of a HARQ bundle of transmissions.

[0250] Another option to predetermine the HARQ-FB report size is that the number of slots for which to provide a HARQ-FB report is always fixed, configured in RRC, or dynamically indicated to the first radio node, e.g., in Cl such as DCI and / or together with the HARQ-FB request e.g., as transmitted from the second radio node 2 to the first radio node 1.

[0251] Option 3: “bundlelD” to identify the HARQ transmissions, e.g., the one or more transmissions. The bundlelD indicates a bundle of transport blocks transmitted, e.g., in consecutive or even non-consecutive slots, so that the first radio node 1 may have to provide HARQ-FB for N slots carrying transport blocks. This may incur a limit to a maximum list size for the HARQ-FB report.

[0252] The number of slots may vary for each bundle as depicted in Figure15, e.g. HARQ process bundle #4 spans 3 slots, while bundle #5 spans 4 slots. In a grant such as a UL grant, the second radio node 2 may indicate for which bundlelD it wants to receive HARQ- FB. The first radio node 1 may establish a HARQ-FB report that includes all transport blocks belonging to the given bundlelD.

[0253] Fig. 15 illustrates an example where DAI is used and the HARQ ID is implicit and derived from DAI. Fig. 15 further illustrates that data is grouped and identified using a bundlelD, e.g., using a codebook which uses implicit HARQ ID.

[0254] Fig. 16 illustrates an example where HARQ ID is explicitly provided in a HARQ-FB codebook of the HARQ-FB report, and no DAI is used / needed. Fig. 16 further illustrates the use of bundle IDs where the HARQ codebook includes an explicit HARQ ID.

[0255] Fixed vs. variable processing times for decoding of HARQ transmissions

[0256] Radio nodes, in particular UEs, may have different processing capabilities or the processing time for the decoding may be different for each TB. This may result in that different embodiments herein may be more suitable for some radio nodes. In some embodiments, the first radio node 1 may transmit HARQ-FB for all TBs it has processed for decoding, e.g., as in Variation 6 discussed above. In another embodiment, e.g., as part of Variation 3, the first radio node 1 transmits HARQ-FB for all HARQ processes, e.g., transmissions of the one or more transmissions, for which it has finalized a respective decoding process, or for which it has received an assignment such as a DL assignment. Fig. 17 illustrates HARQ-FB transmitted for all HARQ processes as part of the HARQ-FB report with available decoding results vs. pending processes.

[0257] Compression schemes

[0258] A compression scheme, e.g., when not using a HARQ codebook in the HARQ-FB report, may be referred to as Variation 8.

[0259] Variation 8: Instead of providing HARQ-FB for all HARQ processes separately in a list, e.g., in the HARQ codebook, a special encoding may be used. The special encoding may be predefined or otherwise configured to try to communicate the reception status of the one or more transmissions using significantly less bits than when using a HARQ codebook or other approaches. The idea is that if all transmissions may often have the same reception status, or there may be a pattern in the reception status that can be encoded with fewer bits than if using a HARQ codebook.

[0260] The encoding may comprise 2 bits compressed FB comprising: all ACK, all NACK, all Cis such as DCIs missed, or a mix thereof. If mix, more details may be needed to be transmitted, e.g., as part of an extended report described above or below. It may be encoded to save overhead: e.g. HARQ IDs 8-12 -> ACK, and e.g., the rest is NACK. In these cases, fewer bits would be needed for the encoding than using the full HARQ codebook. The encoding may comprise a feedback ordering, e.g., using lowest carrier ID first.

[0261] In case of the extended report when indicating a mix, a list of one or more HARQ FB IDs with their corresponding feedback flags may be included in the encoding. The list may be encoded by any suitable source coding techniques, leading to variable message sizes. As one example, a run-length encoding may be employed of this data, or run-length encoding may be employed based on the difference between the to be transmitted list and a previously transmitted list, a list transmitted on another carrier, a list indicated by an identifier, a default list or a default list specific for this set of HARQ IDs or number of HARQ IDs for which feedback is provided.

[0262] In other words, the extended information attached when the encoding indicates a mix may be encoded using any suitable compression encoding, e.g., by compressing bits indicative of its reception status and / or by compressing bits indicative of a difference in a previous or default reception status, e.g., as transmitted in a HARQ-FB.

[0263] Use of consecutive HARQ IDs

[0264] In order to minimize the HARQ-FB overhead, the second radio node 2 may enforce the use of consecutive HARQ IDs whenever possible, e.g. from 8-11 , instead of e.g. 3+6+8+9. This may mostly be relevant for embodiments where the HARQ-FB report comprises explicit HARQ IDs. In these embodiments, it may not be possible to use entry positions of the HARQ codebook to derive the used HARQ process, e.g., as identified by the ID. If 8 bits are used for identifying 32 HARQ processes, the scheme would require 4x8 bits = 32 bits to indicate procs 3+6+8+9. However, if it is defined that the first ACKed HARQ process ID is process #8, and also all 3 subsequent HARQ processes are defined then it is possible to use 4 bits to indicate proc #8, and 8 bits to indicate a total length, or indicate "3" subsequent procs, 16 bits instead of 32 bits.

[0265] Symbol-based HARQ or code block bundle transmissions

[0266] In 6G, transmissions, e.g., the one or more transmissions may be shorter than in 3G, 4G, and 5G, and may be performed in any suitable granularity e.g. on OFDM Symbol (OS) level.

[0267] Symbol-based HARQ transmissions. As a first option, each HARQ transmission may be performed within an OS, such that one TB is transmitted per OS and one HARQ process is used per OS.

[0268] The HARQ-FB report format may then look similar as before and comprise any one or more out of:

[0269] • one or more Carrier IDs, e.g., if multiple carriers are activated,

[0270] • a HARQ codebook corresponds to the following:

[0271] - Alternative 1: a HARQ-FB list wherein

[0272] • HARQ ID may be implicitly indicated

[0273] • HARQ-FB e.g., as in Variations 1-4, such as using ACK / NACK + extra state(s) PENDING and / or MISSED

[0274] - Alternative 2, e.g., as in variations 5 + 6 above with a HARQ codebook comprising

[0275] • HARQ ID

[0276] • HARQ-FB (ACK / NACK)

[0277] Code block bundles per OS. As a second option, a TB of embodiments herein may be divided into code blocks and bundled as Code Block Groups (CBG) as in 5G. In some embodiments, the code blocks are bundled into code block bundles (CBB) in exactly one OS and may not span multiple symbols as illustrated in Fig. 18. Fig. 18 illustrates that TBs are divided into code block bundles, each carried in one OS. For code block bundles (CBB) within one OS, the HARQ-FB report may comprise any one or more out of:

[0278] • one or more carrier IDs, e.g., if multiple carriers are activated,

[0279] • HARQ ID, e.g., per entry in the codebook, • a HARQ codebook indicating

[0280] - FB for all CBBs: All ACK, all NACK, ENC

[0281] - If Enconding(ENC): bitmap or other encoding of HARQ-FB for the CBBs.

[0282] ENC as used herein may mean an encrypted encoding, which is why a bitmap may be needed to map the encoding.

[0283] As an alternative, HARQ ID does not need to be signaled explicitly e.g., as described in Variations 1-4 above.

[0284] Fig. 19 shows an example of arrangement in the first radio node 1.

[0285] The first radio node 1 may comprise an input and output interface 1900 configured to communicate with the second radio node 2. The input and output interface 1900 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0286] The first radio node 1 is configured to handle feedback for HARQ, data transmissions, i.e., HARQ-FB, in the wireless communications network 100. The first radio node 1 is configured to determine reception status associated with one or more transmissions scheduled from a second radio node 2. The first radio node 1 is configured to transmit a HARQ-FB report to the second radio node 2. The HARQ-FB report is transmitted as encapsulated in a data transport block. The HARQ-FB report is indicative of the determined reception status. The HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ-FB information.

[0287] In some embodiments, wherein the HARQ-FB report is transmitted in a MAC-CE, or as part of a RRC message.

[0288] In some embodiments, the size of the HARQ-FB report is dynamic.

[0289] In some embodiments, when the HARQ-FB report is adapted to be indicative of the HARQ codebook, the HARQ-FB report may further be adapted to indicate:

[0290] - a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission,

[0291] -a length indicator of the HARQ codebook, and

[0292] -an indication of HARQ-FB information indicated by the HARQ codebook.

[0293] In some embodiments, the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0294] In some embodiments, the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0295] In some embodiments, the HARQ codebook further is adapted to indicate a HARQ- ID for each of the one or more transmissions.

[0296] In some embodiments, the HARQ codebook is adapted to indicate for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0297] In some embodiments, the HARQ-FB information is adapted to indicate at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers,.

[0298] In some embodiments, the HARQ codebook is adapted to be a dynamic HARQ codebook and wherein the first radio node further is configured to:

[0299] -obtain an indication of a codebook size for the one or more transmissions, and

[0300] -transmit the HARQ-FB report comprising a dynamic HARQ codebook based on the obtained codebook size.

[0301] In some embodiments, the first radio node 1 is further configured to obtain control information from the second radio node 2, the control information being is adapted to be associated with how and / or when to transmit the HARQ-FB report. In these embodiments the control information may be adapted to indicate which one or more data transmissions to provide HARQ-FB. In these embodiments the first radio node may be configured to transmit the HARQ-FB report based on the control information.

[0302] In some embodiments, the control information is adapted to indicate a request of HARQ-FB from the second radio node 2. In some of these embodiments, the HARQ-FB report is adapted to indicate reception status of one or more transmissions occurred in one or more prior slots of a current slot.

[0303] In some embodiments, the HARQ-FB report is adapted to be indicative of reception status of one or more transmissions for each code block group and / or code block bundle associated with the one or more transmissions.

[0304] In some embodiments, when the HARQ-FB report is indicative of the compressed HARQ-FB, the reception status is adapted to indicate any of:

[0305] - all ACK for the one or more transmissions,

[0306] - all PENDING for the one or more transmissions,

[0307] - all NACK for the one or more transmissions,

[0308] - that all scheduling assignments for the one or more transmissions were missed, or

[0309] - a mix of any one or more out of:

[0310] - one or more ACKs for the one or more transmissions, - one or more NACKs for the one or more transmissions,

[0311] - one or more PENDING states for the one or more transmissions, and

[0312] - one or more missed scheduling assignment for the one or more transmissions.

[0313] In some embodiments, the first radio node 1 is a UE and / or the second radio node 2 is a gNB.

[0314] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 1910 of a processing circuitry in the first radio node 1 depicted in Fig. 19, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first radio node 1. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first radio node 1.

[0315] The first radio node 1 and / or the processor 1910 is e.g., configured to perform actions of the method of the first radio node 1 as described above, e.g., using the processors or memories of the first radio node 1 to perform the actions.

[0316] The first radio node 1 may further comprise respective a memory 1919 comprising one or more memory units. The memory 1919 comprises instructions executable by the processor 1910 in the first radio node 1.

[0317] The memory 1910 is arranged to be used to store instructions, data, configurations, identifiers, indications, parameters, timing or control information, HARQ-FB, HARQ information, HARQ codebook, reports, and applications to perform the methods herein when being executed in the first radio node 1.

[0318] In some embodiments, a computer program 1930 comprises instructions, which when executed by the at least one processor 1910, cause the at least one processor 1910 of the first radio node 1 to perform the actions above.

[0319] In some embodiments, a respective carrier 1940 comprises the respective computer program 1930, wherein the carrier 1940 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0320] Those skilled in the art will also appreciate that the functional modules in the first radio node 1 , described below may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the first radio node 1 , that when executed by the respective one or more processors such as the at least one processor 1910 described above cause the respective at least one processor 1910 to perform actions according to any of the actions above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0321] Fig. 20 shows an example of arrangement in the second radio node 2.

[0322] The second radio node 2 may comprise an input and output interface 2000 configured to communicate with the first radio node 1. The input and output interface 2000 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0323] The second radio node 2 configured to handle feedback for HARQ data transmissions, i.e. , HARQ-FB. The second radio node being configured to trigger one or more transmissions from the second radio node 2 to a first radio node 1. The second radio node being configured to receive a HARQ-FB report from the first radio node 1. The HARQ-FB report is adapted to be transmitted as encapsulated in a data transport block. The HARQ-FB report is adapted to be indicative of the determined reception status. The HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ- FB information.

[0324] In some embodiments, the HARQ-FB report is transmitted in a MAC-CE, or as part of an RRC message.

[0325] In some embodiments, the size of the HARQ-FB report is dynamic.

[0326] In some embodiments, when the HARQ-FB report is adapted to be indicative of the HARQ codebook, the HARQ-FB report may further be adapted to indicate:

[0327] - a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission,

[0328] -a length indicator of the HARQ codebook, and

[0329] -an indication of HARQ-FB information indicated by the HARQ codebook.

[0330] In some embodiments, the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0331] In some embodiments, the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0332] In some embodiments, the HARQ codebook further is adapted to indicate a HARQ- ID for each of the one or more transmissions.

[0333] In some embodiments, the HARQ codebook is adapted to indicate for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0334] In some embodiments, the HARQ-FB information is adapted to indicate at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers.

[0335] In some embodiments, the second radio node 2 is configured to: transmit control information to the first radio node 1 , the control information being is adapted to be associated with how and / or when to transmit the HARQ-FB report. In some of these embodiments, the control information is adapted to indicate for which one or more data transmissions to provide HARQ-FB. In some embodiments, the second radio node 2 is configured to receive the HARQ-FB report based on the control information.

[0336] In some embodiments, the control information is adapted to indicate a request of HARQ-FB to the first radio node 1. In some of these embodiments, the HARQ-FB report is adapted to indicate reception status of one or more transmissions occurred in one or more prior slots of a current slot.

[0337] In some embodiments, the HARQ-FB report is adapted to indicate reception status of one or more transmissions for each code block group and / or code block bundle.

[0338] In some embodiments, when the HARQ-FB report is adapted to indicate the compressed HARQ-FB, and wherein the reception status is adapted to indicate any of: -all ACK for the one or more transmissions, -all PENDING for the one or more transmissions, -all NACK for the one or more transmissions,

[0339] -that all scheduling assignments for the one or more data transmissions were missed, or -a mix of any one or more out of:

[0340] -one or more ACKs for the one or more transmissions,

[0341] -one or more NACKs for the one or more transmissions,

[0342] -one or more PENDING states for the one or more transmissions, and

[0343] -one or more missed scheduling assignment for the one or more transmissions.

[0344] In some embodiments, the first radio node 1 is a UE and / or wherein the second radio node 2 is a gNB. The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2010 of a processing circuitry in the second radio node 2 depicted in Fig. 20, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the second radio node 2. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second radio node 2.

[0345] The second radio node 2 and / or the processor 2010 is e.g., configured to perform actions of the method of the second radio node 2 as described above, e.g., using the processors or memories of the second radio node 2 to perform the actions.

[0346] The second radio node 2 may further comprise respective a memory 2020 comprising one or more memory units. The memory 2020 comprises instructions executable by the processor 2010 in the second radio node 2.

[0347] The memory 2010 is arranged to be used to store instructions, data, configurations, identifiers, indications, parameters, timing or control information, HARQ-FB, HARQ information, HARQ codebook, reports, and applications to perform the methods herein when being executed in the second radio node 2.

[0348] In some embodiments, a computer program 2030 comprises instructions, which when executed by the at least one processor 2010, cause the at least one processor 2010 of the second radio node 2 to perform the actions above.

[0349] In some embodiments, a respective carrier 2040 comprises the respective computer program 2030, wherein the carrier 2040 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0350] Those skilled in the art will also appreciate that the functional modules in the second radio node 2, described below may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g. stored in the second radio node 2, that when executed by the respective one or more processors such as the at least one processor 2010 described above cause the respective at least one processor 2010 to perform actions according to any of the actions above. One or more of these processors, as well as the other digital hardware, may be included in a single Application-Specific Integrated Circuitry (ASIC), or several processors and various digital hardware may be distributed among several separate components, whether individually packaged or assembled into a system-on-a-chip (SoC).

[0351] Embodiments

[0352] Below, some example Embodiments 1-54 are shortly described. See e.g., Figures 5-20. The Embodiments 1-54 may be combined with any of the other embodiments herein in any suitable manner.

[0353] Embodiment 1. A method performed by a first radio node 1, e.g., a User Equipment, UE, for handling feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, in a wireless communications network, the method comprising any one or more out of: determining 501 reception status associated with one or more transmissions scheduled from a second radio node 2, e.g., a network node such as a gNB, transmitting 504 a HARQ Feedback, HARQ-FB, report to the second radio node 2, the HARQ-FB report being transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is indicative of the determined reception status, and optionally wherein the size of the HARQ- FB report is dynamic.

[0354] Embodiment 2. The method according to Embodiment 1 , wherein the HARQ- FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

[0355] Embodiment 3. The method according to Embodiment 2, when the HARQ-FB report is indicative of the HARQ codebook, the HARQ-FB report further indicates: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, e.g., a number of HARQ codebook entries, and an indication of HARQ-FB information indicated by the HARQ codebook. Embodiment 4. The method according to Embodiment 2 or 3, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0356] Embodiment 5. The method according to any one of Embodiments 2-4, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0357] Embodiment 6. The method according to Embodiment 5, wherein when the HARQ codebook further indicates a HARQ-ID for each of the one or more transmissions.

[0358] Embodiment 7. The method according to any one of Embodiments 2-6, wherein the HARQ codebook indicates for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0359] Embodiment 8. The method according to any one of Embodiments 2-7, wherein the HARQ-FB information indicates at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers, e.g., by indicating the at least one corresponding reception status of the respective multiple carriers in a single HARQ codebook entry of the HARQ codebook.

[0360] Embodiment 9. The method according to any one of Embodiments 2-8, wherein the HARQ codebook is a dynamic HARQ codebook and wherein the method comprises obtaining 502 an indication of a codebook size for the one or more transmissions, and transmitting 504 the HARQ-FB report comprising a dynamic HARQ codebook based on the obtained codebook size.

[0361] Embodiment 10. The method according to any one of Embodiments 2-9, wherein the method comprises obtaining 503 control information from the second radio node 2, the control information being associated with how and / or when to transmit the HARQ- FB report, and wherein the control information indicates for which one or more data transmissions to provide HARQ-FB, and transmitting 504 the HARQ-FB report based on the control information.

[0362] Embodiment 11. The method according to Embodiment 10, wherein the control information indicates a request of HARQ-FB from the second radio node 2, and wherein the HARQ-FB report is indicative of reception status of one or more transmissions occurred in one or more prior slots of a current slot, e.g., wherein the one or more prior slots is indicated by a reverse time slot offset, and optionally wherein obtaining control information further comprises receiving an indication of the reverse time slot offset as transmitted from the second radio node 2.

[0363] Embodiment 12. The method according to any one of Embodiments 2-11 , wherein the HARQ-FB report is indicative of reception status of one or more transmissions for each code block group and / or code block bundle associated with the one or more transmissions.

[0364] Embodiment 13. The method according to any one of Embodiments 2-12, wherein when the HARQ-FB report is indicative of the compressed HARQ-FB, wherein the reception status indicates any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, that all scheduling assignments for the one or more transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions.

[0365] Embodiment 14. A method performed by a second radio node 2 for handling feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, the method comprising any one or more out of: triggering 601 one or more transmissions, e.g., Sidelink, SL, Downlink, DL, or Uplink, UL, from the second radio node 2 to a first radio node 1 , receiving 603 a HARQ-FB report from the first radio node 1 , the HARQ-FB report being transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is indicative of the determined reception status, and preferably wherein the size of the HARQ-FB report is dynamic.

[0366] Embodiment 15. The method according to Embodiment 14, wherein the HARQ- FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

[0367] Embodiment 16. The method according to Embodiment 15, when the HARQ-FB report is indicative of the HARQ codebook, the HARQ-FB report further indicates: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, e.g., a number of HARQ codebook entries, and an indication of HARQ-FB information indicated by the HARQ codebook.

[0368] Embodiment 17. The method according to Embodiment 14 or 15, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0369] Embodiment 18. The method according to any one of Embodiments 15-17, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0370] Embodiment 19. The method according to Embodiment 18, wherein when the HARQ codebook further indicates a HARQ-ID for each of the one or more transmissions.

[0371] Embodiment 20. The method according to any one of Embodiments 15-19, wherein the HARQ codebook indicates for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0372] Embodiment 21. The method according to any one of Embodiments 15-20, wherein the HARQ-FB information indicates at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers, e.g., by indicating the at least one corresponding reception status of the respective multiple carriers in a single HARQ codebook entry of the HARQ codebook.

[0373] Embodiment 22. The method according to any one of Embodiments 15-22, wherein the method comprises transmitting 602 control information to the first radio node 1 , the control information being associated with how and / or when to transmit the HARQ- FB report, and wherein the control information indicates for which one or more data transmissions to provide HARQ-FB receiving 603 the HARQ-FB report based on the control information.

[0374] Embodiment 23. The method according to Embodiment 23, wherein the control information indicates a request of HARQ-FB from the second radio node 2 to the first radio node 1 , and wherein the HARQ-FB report is indicative of reception status of one or more transmissions occurred in one or more prior slots of a current slot, e.g., wherein the one or more prior slots is indicated by a reverse time slot offset, and optionally wherein transmitting the control information further comprises transmitting an indication of the reverse time slot offset to the first radio node 1.

[0375] Embodiment 24. The method according to any one of Embodiments 15-24, wherein the HARQ-FB report is indicative of reception status of one or more transmissions for each code block group and / or code block bundle e.g., as part of a HARQ process, associated with the one or more transmissions.

[0376] Embodiment 25. The method according to any one of Embodiments 15-25, wherein when the HARQ-FB report is indicative of the compressed HARQ-FB, wherein the reception status indicates any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, that all scheduling assignments for the one or more data transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions.

[0377] Embodiment 26. A first radio node 1 , e.g., a User Equipment, UE, configured to handle feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, in a wireless communications network, the first radio node 1 further being configured to any one or more out of: determine reception status associated with one or more transmissions scheduled from a second radio node 2, e.g., a network node such as a gNB, transmit a HARQ Feedback, HARQ-FB, report to the second radio node 2, the HARQ-FB report being transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is indicative of the determined reception status, and optionally wherein the size of the HARQ-FB report is dynamic.

[0378] Embodiment 27. The first radio node 1 according to Embodiment 26, wherein the HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ-FB information. Embodiment 28. The first radio node 1 according to Embodiment 27, when the HARQ-FB report is adapted to be indicative of the HARQ codebook, the HARQ- FB report further is adapted to indicate: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, e.g., a number of HARQ codebook entries, and an indication of HARQ-FB information indicated by the HARQ codebook.

[0379] Embodiment 29. The first radio node 1 according to Embodiment 27 or 28, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0380] Embodiment 30. The first radio node 1 according to any one of Embodiments 27-30, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0381] Embodiment 31. The first radio node 1 according to Embodiment 30, wherein when the HARQ codebook further is adapted to indicate a HARQ-ID for each of the one or more transmissions.

[0382] Embodiment 32. The first radio node 1 according to any one of Embodiments 27-31 , wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0383] Embodiment 33. The first radio node 1 according to any one of Embodiments 27-32, wherein the HARQ-FB information is adapted to indicate at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers, e.g., by indicating the at least one corresponding reception status of the respective multiple carriers in a single HARQ codebook entry of the HARQ codebook.

[0384] Embodiment 34. The first radio node 1 according to any one of Embodiments 27-33, wherein the HARQ codebook is adapted to be a dynamic HARQ codebook and wherein the first radio node further is configured to: obtain an indication of a codebook size for the one or more transmissions, and transmit the HARQ-FB report comprising a dynamic HARQ codebook based on the obtained codebook size.

[0385] Embodiment 35. The first radio node 1 according to any one of Embodiments 27-34, further configured to: obtain control information from the second radio node 2, the control information being is adapted to be associated with how and / or when to transmit the HARQ-FB report, and wherein the control information is adapted to indicate which one or more data transmissions to provide HARQ-FB, and transmit the HARQ-FB report based on the control information.

[0386] Embodiment 36. The first radio node 1 according to Embodiment 35, wherein the control information is adapted to indicate a request of HARQ-FB from the second radio node 2, and wherein the HARQ-FB report is adapted to indicate reception status of one or more transmissions occurred in one or more prior slots of a current slot, e.g., wherein the one or more prior slots is indicated by a reverse time slot offset, and optionally wherein obtaining control information further comprises receiving an indication of the reverse time slot offset as transmitted from the second radio node 2.

[0387] Embodiment 37. The first radio node 1 according to any one of Embodiments 27-36, wherein the HARQ-FB report is adapted to be indicative of reception status of one or more transmissions for each code block group and / or code block bundle associated with the one or more transmissions.

[0388] Embodiment 38. The first radio node 1 according to any one of Embodiments 27-37, wherein when the HARQ-FB report is indicative of the compressed HARQ-FB, the reception status is adapted to indicate any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, that all scheduling assignments for the one or more transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions. Embodiment 39. A second radio node 2 e.g., configured to handle feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, the second radio node being configured to any one or more out of: trigger one or more transmissions, e.g., Sidelink, SL, Downlink, DL, or Uplink, UL, from the second radio node 2 to a first radio node 1, receive a HARQ-FB report from the first radio node 1, the HARQ-FB report being adapted to be transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is adapted to be indicative of the determined reception status, and preferably wherein the size of the HARQ- FB report is dynamic.

[0389] Embodiment 40. The second radio node 2 according to Embodiment 39, wherein the HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ-FB information.

[0390] Embodiment 41. The second radio node 2 according to Embodiment 40, when the HARQ-FB report is adapted to be indicative of the HARQ codebook, the HARQ-FB report further is adapted to indicate: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, e.g., a number of HARQ codebook entries, and an indication of HARQ-FB information indicated by the HARQ codebook.

[0391] Embodiment 42. The second radio node 2 according to Embodiment 40 or 41 , wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

[0392] Embodiment 43. The second radio node 2 according to any one of Embodiments 40-42, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

[0393] Embodiment 44. The second radio node 2 according to Embodiment 43, wherein the HARQ codebook further is adapted to indicate a HARQ-ID for each of the one or more transmissions.

[0394] Embodiment 45. The second radio node 2 according to any one of Embodiments 40-44, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

[0395] Embodiment 46. . The second radio node 2 according to any one of

[0396] Embodiments 40-45, wherein the HARQ-FB information is adapted to indicate at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers, e.g., by indicating the at least one corresponding reception status of the respective multiple carriers in a single HARQ codebook entry of the HARQ codebook.

[0397] Embodiment 47. The second radio node 2 according to any one of Embodiments 40-46, wherein the second radio node 2 is configured to: transmit control information to the first radio node 1 , the control information being is adapted to be associated with how and / or when to transmit the HARQ-FB report, and wherein the control information is adapted to indicate for which one or more data transmissions to provide HARQ-FB receive the HARQ-FB report based on the control information.

[0398] Embodiment 48. The second radio node 2 according to Embodiment 47, wherein the control information is adapted to indicate a request of HARQ-FB to the first radio node 1 , and wherein the HARQ-FB report is adapted to indicate reception status of one or more transmissions occurred in one or more prior slots of a current slot, e.g., wherein the one or more prior slots is adapted to be indicated by a reverse time slot offset, and optionally wherein transmitting the control information further comprises transmitting an indication of the reverse time slot offset to the first radio node 1.

[0399] Embodiment 49. The second radio node 2 according to any one of Embodiments 40-48, wherein the HARQ-FB report is adapted to indicate reception status of one or more transmissions for each code block group and / or code block bundle e.g., as part of a HARQ process, associated with the one or more transmissions.

[0400] Embodiment 50. The second radio node 2 according to any one of Embodiments 40-49, wherein when the HARQ-FB report is adapted to indicate the compressed HARQ-FB, and wherein the reception status is adapted to indicate any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, that all scheduling assignments for the one or more data transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions.

[0401] Embodiment 51. A computer program 1930 comprising instructions, which when executed by a processor 1910, causes the processor 1910 to perform actions according to any of the Embodiments 1-13.

[0402] Embodiment 52. A carrier 1940 comprising the computer program 1930 of Embodiment 51 , wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0403] Embodiment 53. A computer program 2030 comprising instructions, which when executed by a processor 2010, causes the processor 2010 to perform actions according to any of the Embodiments 14-25.

[0404] Embodiment 54. A carrier 2040 comprising the computer program 2030 of Embodiment 53, wherein the carrier 2040 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0405] ADDITIONAL EXPLANATION

[0406] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0407] Fig. 21 shows an example of a communication system QQ100 in accordance with some embodiments.

[0408] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108 (e.g., the first or second radio node 1 , 2). The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110 e.g., the first or second radio node 1 , 2), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0409] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (0-Dll), an open central unit (O-CU), including an O-CU control plane (O- CLI-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1, E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112 e.g., the first or second radio node 1 , 2) to the core network QQ106 over one or more wireless connections.

[0410] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system QQ100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0411] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0412] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0413] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server. As a whole, the communication system QQ100 of Fig. 21 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G, 6G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0414] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0415] In some examples, the UEs QQ112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi- RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0416] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0417] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0418] Fig. 22 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop- embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0419] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0420] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 22. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0421] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0422] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0423] In some embodiments, the power source QQ208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0424] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0425] The memory QQ210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (IIICC) including one or more subscriber identity modules (SIMs), such as a IISIM and / or ISIM, other memory, or any combination thereof. The IIICC may for example be an embedded IIICC (elllCC), integrated IIICC (illlCC) or a removable IIICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory QQ210, which may be or comprise a device-readable storage medium.

[0426] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0427] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QIIIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0428] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0429] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0430] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Fig. 22. As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0431] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0432] Fig. 23 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0433] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi- cel l / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0434] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

[0435] The processing circuitry QQ302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality. In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0436] The memory QQ304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device- readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0437] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0438] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0439] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0440] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0441] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source QQ308. As a further example, the power source QQ308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0442] Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 23 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0443] Fig. 24 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 21, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0444] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 21-23, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0445] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0446] Fig. 25 is a block diagram illustrating a virtualization environment QQ500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0447] Applications QQ502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0448] Hardware QQ504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0449] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0450] In the context of NFV, a VM QQ508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ508, and that part of hardware QQ504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0451] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0452] Fig. 26 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Fig. 21 and / or UE QQ200 of Fig. 22), network node (such as network node QQ110a of Fig. 21 and / or network node QQ300 of Fig. 23), and host (such as host QQ116 of Fig. 21 and / or host QQ400 of Fig. 24) discussed in the preceding paragraphs will now be described with reference to Fig. 26.

[0453] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0454] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Fig. 21) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0455] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0456] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0457] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0458] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0459] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment.

[0460] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0461] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0462] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0463] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of".

[0464] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

Claims

CLAIMS1 . A method performed by a first radio node (1) for handling feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, in a wireless communications network (100), the method comprising: determining (501) reception status associated with one or more transmissions scheduled from a second radio node (2), transmitting (504) a HARQ-FB report to the second radio node (2), the HARQ-FB report being transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is indicative of the determined reception status, and- wherein the HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

2. The method according to claim 1 , wherein the HARQ-FB report is transmitted in a Medium Access Control Control Element, MAC-CE, or as part of a Radio Resource Control, RRC, message.

3. The method according to claim 1 or 2, wherein the size of the HARQ-FB report is dynamic.

4. The method according to any of claims 1-3, when the HARQ-FB report is indicative of the HARQ codebook, the HARQ-FB report further indicates: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, and an indication of HARQ-FB information indicated by the HARQ codebook.

5. The method according to any of claims 1-4, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

6. The method according to any of claims 1-5, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

7. The method according to claim 6, wherein the HARQ codebook further indicates a HARQ-ID for each of the one or more transmissions.

8. The method according to any one of claims 1-7, wherein the HARQ codebook indicates for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

9. The method according to any one of claims 1-8, wherein the HARQ-FB information indicates at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers.

10. The method according to any one of claims 1-9, wherein the HARQ codebook is a dynamic HARQ codebook and wherein the method comprises obtaining (502) an indication of a codebook size for the one or more transmissions, and transmitting (504) the HARQ-FB report comprising a dynamic HARQ codebook based on the obtained codebook size.

11. The method according to any one of claims 1-10, wherein the method comprises obtaining (503) control information from the second radio node (2), the control information being associated with how and / or when to transmit the HARQ-FB report, and wherein the control information indicates for which one or more data transmissions to provide HARQ-FB, and transmitting (504) the HARQ-FB report based on the control information.

12. The method according to claim 11 , wherein the control information indicates a request of HARQ-FB from the second radio node (2), and wherein the HARQ-FB report is indicative of reception status of one or more transmissions occurred in one or more prior slots of a current slot.

13. The method according to any one of claims 1-12, wherein the HARQ-FB report is indicative of reception status of one or more transmissions for each code block group and / or code block bundle associated with the one or more transmissions.

14. The method according to any one of claims 1-13, wherein when the HARQ-FB report is indicative of the compressed HARQ-FB, the reception status indicates any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, all PENDING for the one or more transmissions, that all scheduling assignments for the one or more transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, o one or more PENDING states for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions.

15. The method of any of claims 1-14, wherein the first radio node (1) is a User Equipment, UE, and / or wherein the second radio node (2) is a network node or network function arranged for sixth generation telecommunications, 6G.

16. A method performed by a second radio node (2) for handling feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, the method comprising: triggering (601) one or more transmissions from the second radio node (2) to a first radio node (1), receiving (603) a HARQ-FB report from the first radio node (1), the HARQ- FB report being transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is indicative of the determined reception status, and- wherein the HARQ-FB report is indicative of a HARQ codebook or compressed HARQ-FB information.

17. The method according to claim 16, wherein the HARQ-FB report is transmitted in a Medium Access Control Control Element, MAC-CE, or as part of a Radio Resource Control, RRC, message.

18. The method according to claim 16 or 17, wherein the size of the HARQ-FB report is dynamic.

19. The method according to any of claims 16-18, when the HARQ-FB report is indicative of the HARQ codebook, the HARQ-FB report further indicates: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, and an indication of HARQ-FB information indicated by the HARQ codebook.

20. The method according to any of claims 16-19, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

21. The method according to any of claims 16-20, wherein the HARQ codebook indicates for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

22. The method according to claim 21 , wherein when the HARQ codebook further indicates a HARQ-ID for each of the one or more transmissions.

23. The method according to any of claims 16-22, wherein the HARQ codebook indicates for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

24. The method according to any of claims 16-23, wherein the HARQ-FB information indicates at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers.

25. The method according to any of claims 16-24, wherein the method comprises transmitting (602) control information to the first radio node (1), the control information being associated with how and / or when to transmit the HARQ-FB report, and wherein the control information indicates for which one or more data transmissions to provide HARQ-FB receiving (603) the HARQ-FB report based on the control information.

26. The method according to claim 25, wherein the control information indicates a request of HARQ-FB from the second radio node (2) to the first radio node (1), and wherein the HARQ-FB report is indicative of reception status of one or more transmissions occurred in one or more prior slots of a current slot.

27. The method according to any one of claims any of claims 16-26, wherein the HARQ-FB report is indicative of reception status of one or more transmissions for each code block group and / or code block bundle.

28. The method according to any one of claims any of claims 16-27, wherein when the HARQ-FB report is indicative of the compressed HARQ-FB, the reception status indicates any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, all PENDING for the one or more transmissions, that all scheduling assignments for the one or more data transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, o one or more PENDING states for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions.

29. The method of any of claims 16-28, wherein the first radio node (1) is a User Equipment, UE, and / or wherein the second radio node (2) is a network node or network function arranged for sixth generation telecommunications, 6G.

30. A first radio node (1), configured to handle feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, in a wirelesscommunications network (100), the first radio node (1) further being configured to: determine reception status associated with one or more transmissions scheduled from a second radio node (2), transmit a HARQ-FB report to the second radio node (2), the HARQ-FB report being transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is indicative of the determined reception status, and- wherein the HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ-FB information.

31. The first radio node (1) according to claim 30, wherein the HARQ-FB report is transmitted in a Medium Access Control Control Element, MAC-CE, or as part of a Radio Resource Control, RRC, message.

32. The first radio node (1) according to claim 30 or 31 , wherein the size of the HARQ-FB report is dynamic.

33. The first radio node (1) according to any of claims 30-32, when the HARQ-FB report is adapted to be indicative of the HARQ codebook, the HARQ-FB report further is adapted to indicate: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, and an indication of HARQ-FB information indicated by the HARQ codebook.

34. The first radio node (1) according to any of claims 30-33, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

35. The first radio node (1) according to any of claims 30-34, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

36. The first radio node (1) according to claim 35, wherein the HARQ codebook further is adapted to indicate a HARQ-ID for each of the one or more transmissions.

37. The first radio node (1) according to any of claims 30-36, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

38. The first radio node (1) according to any of claims 30-37, wherein the HARQ-FB information is adapted to indicate at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers,.

39. The first radio node (1) according to any of claims 30-38, wherein the HARQ codebook is adapted to be a dynamic HARQ codebook and wherein the first radio node further is configured to: obtain an indication of a codebook size for the one or more transmissions, and transmit the HARQ-FB report comprising a dynamic HARQ codebook based on the obtained codebook size.

40. The first radio node (1) according to any of claims 30-39, further configured to: obtain control information from the second radio node (2), the control information being is adapted to be associated with how and / or when to transmit the HARQ-FB report, and wherein the control information is adapted to indicate which one or more data transmissions to provide HARQ-FB, and transmit the HARQ-FB report based on the control information.

41. The first radio node (1) according to claim 40, wherein the control information is adapted to indicate a request of HARQ-FB from the second radio node (2), and wherein the HARQ-FB report is adapted to indicate reception status of one or more transmissions occurred in one or more prior slots of a current slot.

42. The first radio node (1) according to any of claims 30-41 , wherein the HARQ-FB report is adapted to be indicative of reception status of one or more transmissions for each code block group and / or code block bundle associated with the one or more transmissions.

43. The first radio node (1) according to any of claims 30-42, wherein when the HARQ-FB report is indicative of the compressed HARQ-FB, the reception status is adapted to indicate any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, all PENDING for the one or more transmissions, that all scheduling assignments for the one or more transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, o one or more PENDING states for the one or more transmissions, and o one or more missed scheduling assignment for the one or more transmissions.

44. The first radio node (1) of any of claims 30-43, wherein the first radio node (1) is a User Equipment, UE, and / or wherein the second radio node (2) is a network node or network function arranged for sixth generation telecommunications, 6G.

45. A second radio node (2) configured to handle feedback for Hybrid Automatic Repeat Request, HARQ, data transmissions, HARQ-FB, the second radio node being configured to: trigger one or more transmissions from the second radio node (2) to a first radio node (1), receive a HARQ-FB report from the first radio node (1), the HARQ-FB report being adapted to be transmitted as encapsulated in a data transport block, and wherein the HARQ-FB report is adapted to be indicative of the determined reception status, and- wherein the HARQ-FB report is adapted to be indicative of a HARQ codebook or compressed HARQ-FB information.

46. The second radio node (2) according to claim 45, wherein the HARQ-FB report is transmitted in a Medium Access Control Control Element, MAC-CE, or as part of a Radio Resource Control, RRC, message.

47. The second radio node (2) according to claim 45 or 56, wherein the size of the HARQ-FB report is dynamic.

48. The second radio node (2) according to any of claims 45-47, when the HARQ- FB report is adapted to be indicative of the HARQ codebook, the HARQ-FB report further is adapted to indicate: a time reference associated with the one or more transmissions and / or a time reference of the HARQ-FB report transmission, a length indicator of the HARQ codebook, and an indication of HARQ-FB information indicated by the HARQ codebook.

49. The second radio node (2) according to any of claims 45-48, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, or a negative acknowledgement, NACK.

50. The second radio node (2) according to any of claims 45-49, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, an acknowledgement, ACK, a negative acknowledgement, NACK, or any or both of: a missed scheduling assignment, MISSED, and / or a pending decoding state, PENDING.

51. The second radio node (2) according to claim 50, wherein the HARQ codebook further is adapted to indicate a HARQ-ID for each of the one or more transmissions.

52. The second radio node (2) according to any of claims 45-51 -, wherein the HARQ codebook is adapted to indicate for each of the one or more transmissions, a HARQ ID, and 1 bit indicative of an ACK or NACK.

53. The second radio node (2) according to any of claims 45-52, wherein the HARQ- FB information is adapted to indicate at least one identifier of respective multiple carriers and at least one corresponding reception status of the respective multiple carriers.

54. The second radio node (2) according to any of claims 45-53, wherein the second radio node (2) is configured to: transmit control information to the first radio node (1), the control information being is adapted to be associated with how and / or when to transmit the HARQ-FB report, and wherein the control information is adapted to indicate for which one or more data transmissions to provide HARQ-FB receive the HARQ-FB report based on the control information.

55. The second radio node (2) according to claim 54, wherein the control information is adapted to indicate a request of HARQ-FB to the first radio node (1), and wherein the HARQ-FB report is adapted to indicate reception status of one or more transmissions occurred in one or more prior slots of a current slot.

56. The second radio node (2) according to any of claims 45-55, wherein the HARQ- FB report is adapted to indicate reception status of one or more transmissions for each code block group and / or code block bundle.

57. The second radio node (2) according to any of claims 45-56, wherein when the HARQ-FB report is adapted to indicate the compressed HARQ-FB, and wherein the reception status is adapted to indicate any of: all ACK for the one or more transmissions, all NACK for the one or more transmissions, all PENDING for the one or more transmissions, that all scheduling assignments for the one or more data transmissions were missed, or a mix of any one or more out of: o one or more ACKs for the one or more transmissions, o one or more NACKs for the one or more transmissions, o one or more PENDING states for the one or more transmissions, ando one or more missed scheduling assignment for the one or more transmissions.

58. The second radio node (2) of any of claims 45-57, wherein the first radio node (1) is a User Equipment, UE, and / or wherein the second radio node (2) is a network node or network function arranged for sixth generation telecommunications, 6G.

59. A computer program (1930) comprising instructions, which when executed by a processor (1910), causes the processor (1910) to perform actions according to any of the claims 1-15.

60. A carrier (1940) comprising the computer program (1930) of claim 59, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

61. A computer program (2030) comprising instructions, which when executed by a processor (2010), causes the processor (2010) to perform actions according to any of the claims 16-29.

62. A carrier (2040) comprising the computer program (2030) of claim 61, wherein the carrier (2040) is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Images