Transmission Parameter Configuration

Abstract

Embodiments include methods for a wireless device. Such methods may include receiving, from a network node in a wireless network, control signaling indicating a parameter configuration for data transmission to be performed by the network node or by the wireless device, the data transmission being associated with a subset of a plurality of hybrid automatic repeat request (HARQ) processes. The indicated parameter configuration may be one of a plurality of parameter configurations corresponding to respective different subsets of HARQ processes. The different subsets may include a first subset of one or more HARQ processes for which HARQ feedback is disabled, and a second subset of one or more HARQ processes for which HARQ feedback is enabled. Other embodiments include complementary methods for a network node in a wireless network, as well as a wireless device and a network node configured to perform the respective methods.

Description

Technical Field

[0001] This application generally relates to the field of wireless networks, and more specifically, to techniques for improving error control processes (such as hybrid ARQ) for data transmission (such as in non-terrestrial networks where such transmission may experience relatively long propagation delays). Background Art

[0002] Some types of error control processes (such as those based on hybrid automatic repeat request (HARQ) at the PHY / MAC layer) require the transmitter to wait for an acknowledgement feedback from the receiver before performing a (re)transmission of data. This stop-and-wait mechanism coupled with the propagation delay introduces an inherent latency into the communication protocol, which threatens to reduce the link throughput. To mitigate this problem, some methods allow multiple error control processes (e.g., HARQ processes) to be activated simultaneously, such that the transmitter can initiate multiple transmissions in parallel according to different error control processes. In this way, the transmission of one error control process does not require the transmitter to wait for the acknowledgement feedback of another error control process.

[0003] In theory, the number of error control processes that can be active simultaneously can be increased to allow the error control mechanism to cope with larger propagation delays, such as those that may exist in non-terrestrial networks. However, increasing the number of error control processes requires large memories at the transmitter and receiver, requires reducing the maximum supported transmission block size, and increases the signaling overhead. Therefore, error control processes may not be suitable for wireless communication networks with large propagation delays, such as non-terrestrial networks. Disabling the error control process in non-terrestrial networks would avoid these effects, but would result in packet loss. This packet loss in turn would trigger a higher layer retransmission protocol. And the higher layer retransmission protocol would introduce additional latency, thus disrupting the true purpose of disabling the error control process. Summary of the Invention

[0004] Embodiments of the present disclosure provide specific improvements to wireless communication between a wireless device and a wireless network, such as by facilitating solutions to overcome the exemplary problems outlined above and described in more detail below.

[0005] Embodiments include exemplary methods (e.g., procedures) for a wireless device. These embodiments may include receiving control signaling from a network node in a wireless network, the control signaling indicating a parameter configuration for data transmission to be performed by the network node or by the wireless device, the data transmission being associated with a subset of a plurality of hybrid automatic repeat request (HARQ) procedures. The indicated parameter configuration may be one of a plurality of parameter configurations corresponding to respective different subsets of the HARQ procedures. The different subsets may include a first subset of one or more HARQ procedures for which HARQ feedback is disabled, and a second subset of one or more HARQ procedures for which HARQ feedback is enabled.

[0006] In some embodiments, these exemplary methods may further include transmitting or receiving the data transmission associated with the subset of the HARQ procedures according to the indicated parameter configuration.

[0007] In some embodiments, the indicated parameter configuration is for a single HARQ procedure or for all HARQ procedures of a single type. In other embodiments, the indicated parameter configuration is for all HARQ procedures for which HARQ feedback is enabled, or for all HARQ procedures for which HARQ feedback is disabled.

[0008] In some embodiments, the parameter configuration corresponding to the first subset may differ from the parameter configuration corresponding to the second subset in one or more of the following parameters:

[0009] · Aggregation factor, which indicates a plurality of consecutive time slots scheduled by downlink control information;

[0010] · Transmission waveform type;

[0011] · Modulation and coding scheme table;

[0012] · Time domain resource allocation table;

[0013] · Type of frequency resource allocation;

[0014] · Block error rate target;

[0015] · Physical resource block bundling configuration;

[0016] · Type of physical downlink shared channel mapping; or

[0017] · Physical uplink shared channel transmission scheme.

[0018] Other embodiments include other exemplary methods (e.g., procedures) for a wireless device. These exemplary methods may include transmitting, to a network node in a wireless network, hybrid automatic repeat request (HARQ) feedback for a set of downlink (DL) transmissions to be performed by the network node. The HARQ feedback may be based on an HARQ feedback codebook that includes:

[0019] · A first entry corresponding to a first HARQ process for which HARQ feedback is disabled, the first entry indicating that HARQ feedback for the DL transmission is encoded as a negative acknowledgment; and

[0020] · A second entry corresponding to a second HARQ process for which HARQ feedback is enabled, the second entry indicating that HARQ feedback for the DL transmission is encoded based on a decoding result of the DL transmission.

[0021] In some embodiments, the HARQ feedback codebook may be a type 1 HARQ-ACK codebook as described elsewhere herein.

[0022] In some embodiments, the exemplary method may further include receiving, from the network node, a set of downlink control information (DCI) via a physical DL control channel (PDCCH), the set of downlink control information (DCI) indicating respective scheduling for the set of DL transmissions; and receiving the set of DL transmissions from the network node via a physical DL shared channel (PDSCH) according to the respective scheduling.

[0023] In some of these embodiments, the position of the first entry in the HARQ feedback codebook may be based on a slot timing offset included in the DCI that schedules the DL transmission associated with the first HARQ process. Similarly, the position of the second entry in the HARQ feedback codebook may be based on a slot timing offset included in the DCI that schedules the DL transmission associated with the second HARQ process.

[0024] Other embodiments include exemplary methods (e.g., procedures) for a network node in a wireless network. These exemplary methods may include transmitting control signaling to a wireless device, the control signaling indicating a parameter configuration for data transmission to be performed by the network node or by the wireless device, the data transmission being associated with a subset of a plurality of hybrid automatic repeat request (HARQ) processes. The indicated parameter configuration may be one parameter configuration among a plurality of parameter configurations corresponding to respective different subsets of the HARQ processes. The different subsets may include a first subset of one or more HARQ processes for which HARQ feedback is disabled, and a second subset of one or more HARQ processes for which HARQ feedback is enabled.

[0025] In some embodiments, these exemplary methods may further include transmitting or receiving the data transmission associated with the subset of the HARQ processes according to the indicated parameter configuration.

[0026] In some embodiments, the indicated parameter configuration may be used for a single HARQ process or for all HARQ processes of a single type. In other embodiments, the indicated parameter configuration may be used for all HARQ processes that enable HARQ feedback, or for all HARQ processes that disable HARQ feedback.

[0027] In some embodiments, the parameter configuration corresponding to the first subset may be different from the parameter configuration corresponding to the second subset in one or more of the following parameters:

[0028] · Aggregation factor, which indicates a plurality of consecutive time slots scheduled by downlink control information;

[0029] · Transmission waveform type;

[0030] · Modulation and coding scheme table;

[0031] · Time domain resource allocation table;

[0032] · Type of frequency resource allocation;

[0033] · Block error rate target;

[0034] · Physical resource block bundling configuration;

[0035] · Type of physical downlink shared channel mapping; or

[0036] Other embodiments include other exemplary methods (e.g., processes) for network nodes in a wireless network. These exemplary methods may include receiving, from a wireless device, hybrid ARQ (HARQ) feedback for a set of downlink (DL) transmissions to be performed by the network node. The HARQ feedback may be based on a HARQ feedback codebook, which includes:

[0037] · A first entry corresponding to a first HARQ process that disables HARQ feedback, the first entry indicating that the HARQ feedback for the DL transmission is encoded as a negative acknowledgment; and

[0038] · A second entry corresponding to a second HARQ process that enables HARQ feedback, the second entry indicating that the HARQ feedback for the DL transmission is encoded based on the decoding result of the DL transmission.

[0039] In some embodiments, the HARQ feedback codebook can be a type 1 HARQ-ACK codebook, as described elsewhere herein.

[0040] In some embodiments, these exemplary methods may further include transmitting a set of downlink control information (DCI) to the wireless device via a physical downlink control channel (PDCCH), the set of downlink control information (DCI) indicating corresponding scheduling for the set of DL transmissions; and transmitting the set of DL transmissions to the wireless device via a physical downlink shared channel (PDSCH) according to the corresponding scheduling.

[0041] In some of these embodiments, the position of the first entry in the HARQ feedback codebook can be based on a slot timing offset included in the DCI that schedules a DL transmission associated with the first HARQ process. Similarly, the position of the second entry in the HARQ feedback codebook can be based on a slot timing offset included in the DCI that schedules a DL transmission associated with a second HARQ process.

[0042] Other embodiments include network nodes (e.g., base stations, eNBs, gNBs, etc., or components thereof) and wireless devices (e.g., user equipment) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory computer-readable media storing program instructions that, when executed by a processing circuit of such a network node or UE, configure it to perform operations corresponding to any of the exemplary methods described herein.

[0043] These and other objects, features, and advantages of the embodiments of the present disclosure will become apparent upon reading the following detailed description in view of the accompanying drawings, which are briefly summarized below. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 A communication network is shown in accordance with some embodiments.

[0045] INCLUDING Figure 2A -D, FIG. 2 depicts various methods performed by a wireless device in accordance with some embodiments.

[0046] INCLUDING Figure 3A -D, FIG. 3 depicts various methods performed by a network node in accordance with some embodiments.

[0047] Figure 4 An exemplary wireless device is shown in accordance with some embodiments.

[0048] Figure 5 An exemplary network node is shown in accordance with some embodiments.

[0049] Figure 6 Shows an exemplary architecture of a satellite (or non-terrestrial) network with a bent-pipe transponder.

[0050] Figure 7 Shows various delays associated with a Hybrid Automatic Repeat reQuest (HARQ) process.

[0051] Figure 8 Shows an exemplary Time Division Duplex (TDD) mode for codebook-based Downlink (DL) data transmission and corresponding HARQ Uplink (UL) transmission according to some embodiments.

[0052] Figure 9 Shows an example according to some embodiments, where a User Equipment (UE) is configured with two serving cells and three Physical Downlink Control Channel (PDCCH) monitoring occasions.

[0053] Figure 10 Shows another exemplary TDD mode for codebook-based DL data transmission and corresponding HARQ UL transmission according to some embodiments.

[0054] Figure 11 Shows an example of identifying a HARQ process number using a combination of a HARQ process number field and a Redundancy Version (RV) field according to some embodiments.

[0055] Figure 12 Is a block diagram of a User Equipment according to some embodiments.

[0056] Figure 13 Is a block diagram of a virtualized environment according to some embodiments.

[0057] Figure 14 Is a block diagram of a communication network with a host computer according to some embodiments.

[0058] Figure 15 Is a block diagram of a host computer according to some embodiments.

[0059] Figure 16 Is a flowchart showing a method implemented in a communication system according to one embodiment.

[0060] Figures 17 - 20 Is a flowchart showing various methods implemented in a communication system according to various embodiments. Detailed Description

[0061] Some embodiments of what is contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0062] In general, all terms used herein will be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning has been clearly given and / or implied from the context (in which they are used). All references to an element, apparatus, component, part, step, etc. will be construed openly as referring to at least one instance of the element, apparatus, component, part, step, etc., unless otherwise clearly stated. The steps of any method and / or process disclosed herein need not be performed in the exact order disclosed, unless the step is clearly described as after or before another step and / or in circumstances that imply that the step must be after or before another step. In any appropriate case, any feature of any one of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any one of the embodiments may be applied to any other embodiment, and vice versa. Other objectives, features, and advantages of the appended embodiments will be apparent from the following description.

[0063] Furthermore, the following terms are used throughout the specification as given below:

[0064] · Radio node: As used herein, a "radio node" can be a "radio access node" or a "wireless device".

[0065] · Radio access node: As used herein, a "radio access node" (or equivalently a "radio network node", "radio access network node", or "RAN node") can be any node operating in a radio access network (RAN) of a cellular communication network to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, base stations (e.g., a new radio (NR) base station (gNB) in a 3GPP fifth generation (5G) NR network or an enhanced or evolved node B (eNB) in a 3GPP LTE network), base station distributed components (e.g., CU and DU), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, femto base stations, home base stations, etc.), integrated access backhaul (IAB) nodes, transmission points, remote radio units (RRU or RRH), and relay nodes.

[0066] · Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Serving Gateway (SGW), a PDN Gateway (P-GW), a Policy and Charging Rules Function (PCRF), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), a Charging Function (CHF), a Policy Control Function (PCF), an Authentication Server Function (AUSF), etc.

[0067] · Wireless device: As used herein, a "wireless device" (or simply "WD") is any type of device that accesses a cellular communication network (i.e., is served by a cellular communication network) by wirelessly communicating with network nodes and / or other wireless devices. Wireless communication can involve using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through the air to transmit and / or receive wireless signals. Unless otherwise noted, the term "wireless device" is used interchangeably herein with "user equipment" (or simply "UE"). Some examples of wireless devices include, but are not limited to, smart phones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEE), laptop mounted devices (LME), smart devices, wireless customer premise equipment (CPE), Machine-Type Communication (MTC) devices, Internet of Things (IoT) devices, vehicle-mounted wireless terminal devices, etc.

[0068] · Network node: As used herein, a "network node" is any node that is part of the core network of a cellular communication network (e.g., the core network nodes discussed above) or part of a radio access network (e.g., the radio access nodes or equivalent names discussed above). Functionally, a network node is a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a cellular communication network to enable and / or provide wireless access to wireless devices and / or to perform other functions in a cellular communication network (e.g., management).

[0069] Note that the description given herein focuses on 3GPP cellular communication systems, and as such, 3GPP terms or terms similar to 3GPP terms are often used. However, the concepts disclosed herein are not limited to 3GPP systems. Additionally, although the term "cell" is used herein, it should be understood that (especially with respect to 5G NR) beams may be used instead of cells, and as such, the concepts described herein apply equally to both cells and beams.

[0070] Figure 1 A communication network 10 is shown according to some embodiments. The network 10 can be, for example, a non-terrestrial network (NTN), also referred to as a satellite-based radio access network. In some embodiments, the network 10 is a radio access network of a cellular communication network such as a Long-Term Evolution (LTE) or New Radio (NR) network.

[0071] As shown, the network 10 includes, for example, a network node 12 in a core network (CN) or a radio access network (RAN) of a wireless communication network. The network node 12 can be, for example, a radio network node (e.g., a base station). In any case, the network node 12 shown is connected to a ground-based base station antenna 14, which in this example is remote from the network node 12 (i.e., not collocated with the network node 12). The network 10 also includes a satellite 16 as a non-loaded platform, which is connected to the ground-based base station antenna 14 via a feeder link 15. This provides a satellite-based service link 17 to a wireless device 18, which is located, for example, in a corresponding point beam or cell.

[0072] Depending on the functionality of the satellite 406 in the satellite-based radio access network 400, two transponder options can be considered. With a bent pipe transponder, the satellite 16 simply forwards the received signal back to Earth by amplifying and shifting the frequency from the uplink frequency to the downlink frequency. With a regenerative transponder, the satellite 16 includes on-board processing to demodulate and decode the received signal and regenerate the signal before transmitting the signal back to Earth.

[0073] In this context, the wireless device 18 supports multiple error control processes 20-1... 20-N that are simultaneously active. The error control processes 20-1... 20-N can, for example, take the form of multiple HARQ processes controlled by the MAC layer, for example. This means that the wireless device 18 is capable of transmitting or receiving multiple transmissions in parallel according to different error control processes among the error control processes 20-1... 20-N. For example, the wireless device 18 is capable of transmitting or receiving transmission 22-1 according to error control process 20-1 in parallel with transmitting or receiving transmission 22-N according to error control process 20-N. If transmissions 22-1, 22-N are uplink transmissions, the wireless device 18 can transmit transmission 22-1 according to error control process 20-1 without having to wait for an acknowledgment feedback for transmission 22-N that is performed according to error control process 20-N.

[0074] It is noted that some embodiments herein enable the configuration of transmission parameters on a per-error control process basis, on a per-error control process type basis, or on any other basis that enables different subsets of the error control processes 20-1... 20-N to have corresponding transmission parameter configurations. Thus, some embodiments enable the transmission parameters to be configured differently for the different error control processes 20-1... 20-N. That is, the parameters of transmissions 22-1... 22-N for the different error control processes 20-1... 20-N can (but do not necessarily have to) be configured differently. For example, as Figure 1 shown, the wireless device can transmit or receive transmission 22-1 of error control process 20-1 according to parameter configuration 24-1 and transmit or receive transmission 22-N of error control process 20-N according to parameter configuration 24-N.

[0075] In some embodiments, for example, any one of the parameter configurations 24-1... 24-N can include the configuration of one or more power control parameters. The one or more power control parameters can include, for example, one or more of the following: a nominal target received power, a path loss compensation factor, an incremental modulation and coding scheme, a transmit power control accumulation, a plurality of power control adjustment states maintained by the wireless device, or a parameter that maps a transmit power control command field in downlink control information to an absolute or cumulative closed-loop power control value. Here, the nominal target received power can be the sum of a cell-specific component and a device-specific component, the path loss compensation factor can determine how much of the estimated path loss needs to be compensated by the transmit power for the transmission, the incremental modulation and coding scheme parameter can determine whether a factor as a function of the modulation and coding scheme is added to calculate the transmit power for the transmission, and / or the transmit power control accumulation can determine whether the power control command is applied cumulatively.

[0076] Alternatively or additionally, any one of parameter configurations 24-1…24-N may include a configuration of an actual transmission power level. For example, such a configuration may be a configuration regarding whether to perform transmission at a maximum transmission power.

[0077] Alternatively or additionally, any one of parameter configurations 24-1…24-N may include a configuration of one or more of the following: an aggregation factor indicating the number of consecutive downlink time slots scheduled by downlink control information; a transmission waveform type; a modulation and coding scheme table; a time domain resource allocation table; a type of frequency resource allocation; a block error rate target; a physical resource block bundling configuration; a type of physical downlink shared channel mapping; or a physical uplink shared channel transmission scheme.

[0078] Regardless of the specific parameters configured by parameter configurations 24-1…24-N, according to some embodiments, network node 12 may signal one or more of parameter configurations 24-1…24-N. That is, in some embodiments as shown in the figure, network node 12 transmits control signaling 26 to wireless device 18 for transmission parameter configuration. In this regard, control signaling 26 indicates parameter configuration 28, and a transmission of a specific subset of one or more error control processes will be performed according to parameter configuration 28 (wherein, the subset herein refers to a proper subset in mathematical terms, i.e., a part of a larger set). For example, in a case where the specific subset only includes error control process 20-1, the control signaling may indicate parameter configuration 28 (e.g., indicating parameter configuration 24-1), and a transmission of error control process 20-1 will be performed according to parameter configuration 28.

[0079] In some embodiments, one or more error control processes in a specific subset may include one or more error control processes identified by one or more corresponding error control process identifiers. In such a case, control signaling 26 may indicate one or more corresponding error control process identifiers. Thus, control signaling 26 may include parameter configuration 28 and an identifier of an error control process, and a transmission of the error control process will be performed according to parameter configuration 28.

[0080] In another example, one or more error control processes in a specific subset include any error control process of a specific type. In these and other embodiments, for example, one or more error control processes in a specific subset include any error control process for which error control feedback is disabled, or any error control process for which error control feedback is enabled.

[0081] More specifically, in this regard, transmission parameters according to some embodiments may be configured differently for different error control processes 20-1…20-N, depending on whether error control feedback is enabled or disabled for those respective error control processes. That is, in some embodiments, error control feedback for any given error control process may be selectively enabled or disabled, for example, on a dynamic or semi-static basis, such as via a MAC control element (CE) or via RRC signaling. For example, error control feedback may be enabled for error control processes associated with delay-tolerant applications or for which transmission reliability is a primary consideration, but may be disabled for error control processes associated with delay-intolerant applications or for which transmission latency or throughput is a primary consideration. In this context, the transmission parameters may be configured such that transmission is more reliable for error control processes with feedback disabled compared to those with feedback enabled. Configuring the transmission to be more reliable for error control processes with feedback disabled may advantageously mitigate packet loss and trigger of the higher layer retransmission protocol, thereby correspondingly improving transmission latency.

[0082] Then, in this case, in some embodiments, the control signaling 26 may indicate a parameter configuration 28 according to which transmission will be performed for any error control process for which feedback is disabled. Alternatively, the control signaling 26 may indicate a parameter configuration 28 according to which transmission will be performed for any error control process for which feedback is enabled.

[0083] Although the control signaling 26 is shown with respect to one particular subset, the control signaling 26 may generally indicate different parameter configurations according to which transmissions of different subsets of one or more error control processes will be performed. For example, different subsets may include a subset of one or more error control processes for which error control feedback is disabled and a subset of one or more error control processes for which error control feedback is enabled.

[0084] Note that in some embodiments, when error control feedback is disabled for an error control process, transmission is still scheduled, for example, in a downlink control information (DCI) message, with the error control process ID / number. However, the transmitting node does not expect to receive (explicitly or implicitly) an acknowledgment feedback or a scheduled retransmission.

[0085] In view of the above modifications and variations, Figures 2A - 2D depicts various exemplary methods (e.g., processes) for a wireless device 18 (as shown in Figure 1 ), according to various exemplary embodiments. Similarly, Figures 3A - 3D depicts various exemplary methods (e.g., processes) for a network node 12 (as shown in Figure 1 ), according to various exemplary embodiments. Although inFigures 2A - 2D and Figures 3A - 3D exemplary methods are shown by specific boxes in a particular order, but the operations corresponding to the boxes can be performed in an order different from that shown, and can be combined and / or divided into boxes with functionality different from that shown. Further, Figures 2A - 2D and Figures 3A - 3D the various exemplary methods shown in can be complementary to each other such that they can be used in concert to provide various benefits, advantages, and / or solutions to problems, including those described herein. Optional boxes and / or operations are indicated by dashed lines.

[0086] In Figure 2A the exemplary method shown in, a wireless device may receive (e.g., in box 200) control signaling from a network node in a wireless network, the control signaling indicating a parameter configuration for data transmission to be performed by the network node or by the wireless device (e.g., Figure 1 28 shown in), the data transmission being associated with a subset of a plurality of hybrid automatic repeat request (HARQ) processes. The indicated parameter configuration may be one of a plurality of parameter configurations corresponding to respective different subsets of the HARQ processes. The different subsets may include a first subset of one or more HARQ processes that disable HARQ feedback, and a second subset of one or more HARQ processes that enable HARQ feedback.

[0087] In some embodiments, the wireless device may also transmit or receive (e.g., in box 210) the data transmission associated with the subset of the HARQ processes according to the indicated parameter configuration.

[0088] In some embodiments, the indicated parameter configuration is for a single HARQ process or for all HARQ processes of a single type. In other embodiments, the indicated parameter configuration is for all HARQ processes that enable HARQ feedback, or for all HARQ processes that disable HARQ feedback.

[0089] In some embodiments, the parameter configuration corresponding to the first subset may differ from the parameter configuration corresponding to the second subset in one or more of the following parameters:

[0090] · Aggregation factor, which indicates a plurality of consecutive time slots scheduled by downlink control information;

[0091] · Transmission waveform type;

[0092] · Modulation and coding scheme table;

[0093] · Time domain resource allocation table;

[0094] · Type of frequency resource allocation;

[0095] · Block error rate target;

[0096] · Physical resource block bundling configuration;

[0097] · Type of physical downlink shared channel mapping; or

[0098] · Physical uplink shared channel transmission scheme.

[0099] Figure 2B Depicts another exemplary method for a wireless device according to other exemplary embodiments. The method may include transmitting or receiving transmissions of different subsets of one or more error control procedures according to different parameter configurations (block 230). The method may alternatively or additionally include receiving control signaling 26 from network node 12, the control signaling 26 indicating different parameter configurations according to which different subsets of one or more error control procedures will be transmitted (block 220).

[0100] Figure 2C Depicts another exemplary method for a wireless device according to other exemplary embodiments. In Figure 2C the exemplary method shown, the wireless device may transmit (e.g., in block 250) hybrid automatic repeat request (HARQ) feedback for a set of downlink (DL) transmissions to be performed by the network node in the wireless network. The HARQ feedback may be based on a HARQ feedback codebook that includes:

[0101] · A first entry corresponding to a first HARQ process for which HARQ feedback is disabled, the first entry indicating that the HARQ feedback for the DL transmission is encoded as a negative acknowledgment; and

[0102] · A second entry corresponding to a second HARQ process for which HARQ feedback is enabled, the second entry indicating that the HARQ feedback for the DL transmission is encoded based on the decoding result of the DL transmission.

[0103] In some embodiments, the HARQ feedback codebook may be a type 1 HARQ-ACK codebook as described elsewhere herein.

[0104] In some embodiments, the exemplary method may further include operations of blocks 235-240. In block 235, the wireless device may receive a set of downlink control information (DCI) from the network node via a physical downlink control channel (PDCCH), the set of downlink control information (DCI) indicating corresponding scheduling for the set of DL transmissions. In block 240, the wireless device may receive the set of DL transmissions from the network node via a physical downlink shared channel (PDSCH) according to the corresponding scheduling.

[0105] In some of these embodiments, the position of the first entry in the HARQ feedback codebook may be based on a slot timing offset included in the DCI that schedules a DL transmission associated with the first HARQ process. Similarly, the position of the second entry in the HARQ feedback codebook may be based on a slot timing offset included in the DCI that schedules a DL transmission associated with a second HARQ process.

[0106] Figure 2D Another exemplary method for a wireless device according to other exemplary embodiments is depicted. The method includes receiving a downlink control information message that schedules a downlink transmission for a particular error control process and includes a set of one or more fields, the interpretation of the set of one or more fields depending on whether error control feedback is enabled or disabled for the particular error control process (block 260). In some embodiments, the method further includes interpreting the set of one or more fields depending on whether error control feedback is enabled or disabled for the particular error control process (block 270). The method may further include receiving the downlink transmission according to the received downlink control information message (block 280).

[0107] In some embodiments, one or more fields in the set include one or more of the following: a downlink assignment indicator field, a redundancy version field, a feedback timing field, or a physical uplink control channel resource indicator field. In some embodiments, the downlink assignment indicator field indicates the size of a type 2 HARQ codebook. In some embodiments, the redundancy version field indicates the redundancy version of a transport block transmitted to the wireless device. In cases where feedback is enabled for an error control process, the wireless device may receive the same transport block with different redundancy versions, and the wireless device may soft combine the different redundancy versions to improve the reliability of the transmission received via the physical downlink shared channel (PDSCH). In some embodiments, the feedback timing field indicates the time offset from the time of receiving the PDSCH corresponding to a particular error control process to the time of transmitting feedback corresponding to the particular error control process. In some embodiments, the physical uplink control channel resource indicator field indicates which resource among a plurality of resources will be used for feedback corresponding to an error control process in the physical uplink control channel.

[0108] In some embodiments, when error control feedback is disabled, the set of one or more fields indicates an aggregation factor that indicates a plurality of consecutive downlink time slots associated with the scheduled downlink transmission.

[0109] Alternatively or additionally, in some embodiments, when error control feedback is disabled, the set of one or more fields together with the error control process number field in the downlink control information message indicates an error control process number that identifies the particular error control process.

[0110] Figure 3A An exemplary method for a network node in a wireless network according to other exemplary embodiments is depicted. In Figure 3A the exemplary method shown, the network node may transmit (e.g., in block 300) control signaling to the wireless device, the control signaling indicating a parameter configuration for data transmission (e.g., Figure 1 28 shown in

[0111] In some embodiments, the network node may also transmit or receive (e.g., at block 310) the data transmission associated with the subset of the HARQ processes according to the indicated parameter configuration.

[0112] In some embodiments, the indicated parameter configuration is for a single HARQ process or for all HARQ processes of a single type. In other embodiments, the indicated parameter configuration is for all HARQ processes that enable HARQ feedback or for all HARQ processes that disable HARQ feedback.

[0113] In some embodiments, the parameter configuration corresponding to the first subset may be different from the parameter configuration corresponding to the second subset in one or more of the following parameters:

[0114] · Aggregation factor, which indicates a plurality of consecutive time slots scheduled by downlink control information;

[0115] · Transmission waveform type;

[0116] · Modulation and coding scheme table;

[0117] · Time domain resource allocation table;

[0118] · Type of frequency resource allocation;

[0119] · Block error rate target;

[0120] · Physical resource block bundling configuration;

[0121] · Type of physical downlink shared channel mapping; or

[0122] · Physical uplink shared channel transmission scheme.

[0123] Figure 3B Depicts another exemplary method for a network node according to other exemplary embodiments. In some embodiments, the method includes transmitting or receiving transmissions of different subsets of one or more error control processes according to different parameter configurations (block 330). The method may alternatively or additionally include transmitting control signaling 26 from network node 12 to the wireless device, the control signaling 26 indicating different parameter configurations according to which transmissions of different subsets of one or more error control processes will be performed (block 320).

[0124] Figure 3C Depicts another exemplary method for a network node according to other exemplary embodiments. In Figure 3CIn the exemplary method shown, a network node may receive (e.g., in block 350) hybrid automatic repeat request (HARQ) feedback from a wireless device for a set of downlink (DL) transmissions to be performed by the network node. The HARQ feedback may be based on a HARQ feedback codebook that includes:

[0125] · A first entry corresponding to a first HARQ process that disables HARQ feedback, the first entry indicating that HARQ feedback for the DL transmission is encoded as a negative acknowledgment; and

[0126] · A second entry corresponding to a second HARQ process that enables HARQ feedback, the second entry indicating that HARQ feedback for the DL transmission is encoded based on the decoding result of the DL transmission.

[0127] In some embodiments, the HARQ feedback codebook may be a type 1 HARQ-ACK codebook as described elsewhere herein.

[0128] In some embodiments, the exemplary method may further include the operations of blocks 335-340. In block 335, the network node may transmit a set of downlink control information (DCI) to the wireless device via a physical downlink control channel (PDCCH), the set of downlink control information (DCI) indicating respective scheduling for the set of DL transmissions. In block 340, the network node may transmit the set of DL transmissions to the wireless device via a physical downlink shared channel (PDSCH) according to the respective scheduling.

[0129] In some of these embodiments, the position of the first entry in the HARQ feedback codebook may be based on a slot timing offset included in the DCI that schedules the DL transmission associated with the first HARQ process. Similarly, the position of the second entry in the HARQ feedback codebook may be based on a slot timing offset included in the DCI that schedules the DL transmission associated with the second HARQ process.

[0130] Figure 3DAnother exemplary method for a network node according to other exemplary embodiments is depicted. The method includes transmitting a downlink control information message to a wireless device, the downlink control information message scheduling a downlink transmission for a specific error control process and including a set of one or more fields, the interpretation of which depends on whether error control feedback is enabled or disabled for the specific error control process (block 360). In some embodiments, the method may also include encoding the set of one or more fields depending on whether error control feedback is enabled or disabled for the specific error control process (block 370). The method may alternatively or additionally include transmitting the downlink transmission in accordance with the transmitted downlink control information message (block 380).

[0131] In some embodiments, the one or more fields in the set include one or more of the following: a downlink assignment indicator field, a redundant version field, a feedback timing field, or a physical uplink control channel resource indicator field. In some embodiments, the downlink assignment indicator field indicates the size of the type 2 HARQ codebook. In some embodiments, the redundant version field indicates the redundant version of the transport block transmitted to the wireless device. In the case where feedback is enabled for an error control process, the wireless device can receive the same transport block with different redundant versions, and the wireless device can soft combine the different redundant versions to improve the reliability of the PDSCH. In some embodiments, the feedback timing field indicates a time offset from the time when the PDSCH corresponding to a specific error control process is received to the time when feedback corresponding to the specific error control process is sent. In some embodiments, the physical uplink control channel resource indicator field indicates which of a plurality of resources will be used for feedback corresponding to an error control process in a physical uplink control channel.

[0132] In some embodiments, when error control feedback is disabled, the set of one or more fields indicates an aggregation factor indicating a number of consecutive downlink time slots associated with the scheduled downlink transmission.

[0133] Alternatively or additionally, in some embodiments, when error control feedback is disabled, the set of one or more fields, in combination with the error control process number field in the downlink control information message, indicates an error control process number identifying the specific error control process.

[0134] Embodiments herein also include corresponding devices, computer-readable media, and computer program products. Examples of such embodiments include a wireless device arranged to communicate with a network node in a wireless network via HARQ feedback and data transmission associated with multiple HARQ processes, wherein the wireless device is further arranged to perform the above-mentioned Figures 2A - 2DOperations corresponding to any of the described exemplary methods.

[0135] Other examples include a wireless device comprising communication circuitry configured to communicate with a network node in a wireless network and processing circuitry operatively coupled to the communication circuitry, whereby the processing circuitry and the communication circuitry are configured to perform operations corresponding to any of the exemplary methods described above with respect to Figures 2A - 2D Operations corresponding to any of the described exemplary methods.

[0136] Other examples include a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the processing circuitry of a wireless device, configure the wireless device to perform operations corresponding to any of the exemplary methods described above with respect to Figures 2A - 2D Operations corresponding to any of the described exemplary methods.

[0137] Other examples include a computer program product comprising computer-executable instructions that, when executed by the processing circuitry of a wireless device, configure the wireless device to perform operations corresponding to any of the exemplary methods described above with respect to Figures 2A - 2D Operations corresponding to any of the described exemplary methods.

[0138] Other examples include a network node in a wireless network, the network node being arranged to communicate with one or more wireless devices via HARQ feedback and data transmission associated with a plurality of HARQ processes, wherein the network node is further arranged to perform operations corresponding to any of the exemplary methods described above with respect to Figures 3A - 3D Operations corresponding to any of the described exemplary methods.

[0139] Other examples include a network node comprising communication circuitry configured to communicate with a wireless device in a wireless network and processing circuitry operatively coupled to the communication circuitry, whereby the processing circuitry and the communication circuitry are configured to perform operations corresponding to any of the exemplary methods described above with respect to Figures 3A - 3D Operations corresponding to any of the described exemplary methods.

[0140] Other examples include a non-transitory computer-readable medium storing computer-executable instructions that, when executed by the processing circuitry of a network node in a wireless network, configure the network node to perform operations corresponding to any of the exemplary methods described above with respect to Figures 3A - 3D Operations corresponding to any of the described exemplary methods.

[0141] Other examples include a computer program product comprising computer-executable instructions that, when executed by the processing circuitry of a network node in a wireless network, configure the network node to perform operations corresponding to any of the exemplary methods described above with respect to Figures 3A - 3D Operations corresponding to any of the described exemplary methods.

[0142] The embodiment also includes a wireless device, which includes a processing circuit and a power supply circuit. The processing circuit is configured to perform any steps of any of the embodiments described above for the wireless device. The power supply circuit is configured to supply power to the wireless device.

[0143] The embodiment also includes a wireless device, which includes a processing circuit. The processing circuit is configured to perform any steps of any of the embodiments described above for the wireless device. In some embodiments, the wireless device further includes a communication circuit.

[0144] The embodiment also includes a wireless device, which includes a processing circuit and a memory. The memory contains instructions executable by the processing circuit, whereby the wireless device is configured to perform any steps of any of the embodiments described above for the wireless device.

[0145] The embodiment also includes a user equipment (UE). The UE includes an antenna configured to transmit and receive wireless signals. The UE further includes a radio front-end circuit, which is connected to the antenna and the processing circuit and is configured to condition signals transmitted between the antenna and the processing circuit. The processing circuit is configured to perform any steps of any of the embodiments described above for the wireless device. In some embodiments, the UE further includes an input interface, which is connected to the processing circuit and is configured to allow information to be input into the UE for processing by the processing circuit. The UE may include an output interface, which is connected to the processing circuit and is configured to output information that has been processed by the processing circuit from the UE. The UE may also include a battery, which is connected to the processing circuit and is configured to supply power to the UE.

[0146] The embodiments herein also include a radio network node, which is configured to perform any steps of any of the embodiments described above for the radio network node.

[0147] The embodiment also includes a radio network node, which includes a processing circuit and a power supply circuit. The processing circuit is configured to perform any steps of any of the embodiments described above for the radio network node. The power supply circuit is configured to supply power to the radio network node.

[0148] The embodiment also includes a radio network node, which includes a processing circuit. The processing circuit is configured to perform any steps of any of the embodiments described above for the radio network node. In some embodiments, the radio network node further includes a communication circuit.

[0149] The embodiment also includes a radio network node, which includes a processing circuit and a memory. The memory contains instructions executable by the processing circuit, whereby the radio network node is configured to perform any steps of any of the embodiments described above for the radio network node.

[0150] More specifically, the above-described device may perform the methods and any other processes herein by implementing any functional components, modules, units, or circuits. In one embodiment, for example, the device includes corresponding circuitry or circuit systems configured to perform the steps shown in the method drawings. In this regard, the circuitry or circuit systems may include circuitry dedicated to performing a certain functional process and / or one or more microprocessors in combination with a memory. For example, the circuitry may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include a digital signal processor (DSP), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in the memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in the memory may include program instructions for performing one or more telecommunication and / or data communication protocols and instructions for performing one or more of the techniques described herein. In embodiments employing a memory, the memory stores program code that, when executed by one or more processors, performs the techniques described herein.

[0151] Figure 4 An exemplary wireless device 700 (e.g., wireless device 18) according to one or more embodiments is illustrated. As shown, wireless device 400 includes processing circuitry 410 and communication circuitry 420. Communication circuitry 420 (e.g., radio circuitry) is configured to transmit information to and / or receive information from one or more other nodes via any communication technology, for example. Such communication may occur via one or more antennas internal or external to wireless device 400. Processing circuitry 410 is configured to perform processing such as that described above in Figure 2A , Figure 2B , Figure 2C , and / or Figure 2D by executing instructions stored in memory 430. In this regard, processing circuitry 410 may implement certain functional components, units, or modules.

[0152] Figure 5 An exemplary network node 500 (e.g., network node 12) according to one or more embodiments is illustrated. As shown, network node 500 includes processing circuitry 510 and communication circuitry 520. Communication circuitry 520 is configured to transmit information to and / or receive information from one or more other nodes via any communication technology, for example. Processing circuitry 510 is configured to perform processing such as that described above in Figure 3A , Figure 3B ,Figure 3C and / or Figure 3D The processing described in. In this regard, the processing circuit 510 may implement certain functional components, units, or modules.

[0153] Those skilled in the art will also understand that the embodiments herein also include corresponding computer programs.

[0154] The computer program includes instructions that, when executed on at least one processor of the device, cause the device to perform any one of the above corresponding processes. In this regard, the computer program may include one or more code modules corresponding to the above components or units.

[0155] The embodiments also include a carrier containing such a computer program. The carrier may include one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0156] In this regard, the embodiments herein also include a computer program product that is stored on a non-transitory computer-readable (storage or recording) medium and includes instructions that, when executed by a processor of the device, cause the device to perform as described above.

[0157] The embodiments also include a computer program product that includes a program code portion for performing the steps of any one of the embodiments herein when the computer program product is executed by a computing device. The computer program product may be stored on a computer-readable recording medium.

[0158] Additional embodiments will now be described, for example, with respect to the HARQ process in NTN. For illustrative purposes, at least some of these embodiments may be described as applicable in certain contexts and / or wireless network types, but the embodiments are similarly applicable in other contexts and / or wireless network types not explicitly described.

[0159] In 3GPP Release 8, the Evolved Packet System (EPS) was specified. EPS is based on the Long-Term Evolution (LTE) radio network and the Evolved Packet Core (EPC). It was initially intended to provide voice and mobile broadband (MBB) services, but has continued to evolve to broaden its functionality. Since Release 13, Narrowband Internet of Things (NB-IoT) and LTE for Machines (LTE-M) have been part of the LTE specification and provide connectivity for massive machine type communication (mMTC) services.

[0160] In 3GPP Release 15, the first version of the 5G System (5GS) was developed. This is a new generation of radio access technology, which aims to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and mMTC. 5G includes the new radio (NR) access stratum interfaces and the 5G core network (5GC). The NR physical layer and higher layers are reusing parts of the LTE specifications and adding the required components when motivated by new use cases.

[0161] In Release 15, 3GPP started the work of preparing NR for operation in non-terrestrial networks (NTN). This work was carried out in the research project "NR to support Non-Terrestrial Networks" and resulted in TR38.811. In Release 16, the work of preparing NR for operation in NTN continued in the research project RP-181370 "Solutions for NR to support Non-Terrestrial Network".

[0162] A satellite radio access network typically includes the following components: (i) a satellite, which refers to a spaceborne platform; (ii) an earth-based gateway, which connects the satellite to a base station or the core network depending on the architecture choice; (iii) a feeder link, which refers to the link between the gateway and the satellite; (iv) a service link, which refers to the link between the satellite and the UE.

[0163] Two popular architectures are the bent pipe transponder and the regenerative transponder architectures. In the first case, the base station is located on the earth behind the gateway, and the satellite operates as a repeater to forward the feeder link signal to the service link and vice versa. In the second case, the satellite is in the base station, and the service link connects it to the earth-based core network.

[0164] Depending on the orbital altitude, satellites can be classified as low earth orbit (LEO), medium earth orbit (MEO), or geostationary earth orbit (GEO) satellites. LEO has a typical altitude ranging from 250 - 1500 km, where the orbital period ranges from 90 - 120 minutes. MEO has a typical altitude ranging from 5000 - 25000 km, where the orbital period ranges from 3 - 15 hours. And GEO has an altitude of approximately 35786 km, where the orbital period is 24 hours.

[0165] Communication satellites typically generate several beams over a given area. The coverage area of a beam is usually elliptical and is traditionally considered a cell. The coverage area of a beam is also commonly referred to as a spot beam. The spot beam can move over the Earth's surface as the satellite moves or can be fixed on the Earth using a certain beam pointing mechanism employed by the satellite to compensate for the satellite's motion. The size of the spot beam depends on the system design and can range from dozens of kilometers to thousands of kilometers.

[0166] Figure 6 An exemplary architecture of a satellite (or non-terrestrial) network with a bent pipe transponder is shown. Two main physical phenomena that affect satellite communication system design are long propagation delay and Doppler effect.

[0167] The Doppler effect is particularly significant for LEO satellites.

[0168] Propagation delay is a major physical phenomenon in satellite communication systems, which makes the design different from that of terrestrial mobile systems. For a bent pipe satellite network, the following delays are relevant.

[0169] · One-way delay: from the base station (BS) via the satellite to the UE, or vice versa

[0170] · Round-trip delay: from the BS via the satellite to the UE and from the UE via the satellite back to the BS

[0171] · Differential delay: the difference in delay between two selected points in the same spot beam

[0172] Note that there may be an additional delay between the ground BS antenna and the BS, which may or may not be collocated. This delay depends on the deployment. If this delay cannot be ignored, it should be considered in the communication system design.

[0173] Propagation delay depends on the length of the signal path, which further depends on the elevation angle of the satellite as seen by the BS and the UE on the ground. For the UE, the minimum elevation angle is usually greater than 10°, and for the ground BS, the minimum elevation angle is usually greater than 5°.

[0174] The hybrid automatic repeat request (HARQ) protocol is one of the most important features in NR / LTE. Together with link adaptation via channel state information (CSI) feedback and HARQ ACK / NACK, HARQ enables efficient, reliable, and low-latency data transmission in NR / LTE.

[0175] The existing Hybrid Automatic Repeat reQuest (HARQ) processes at the PHY / MAC layer have been designed for terrestrial networks where the Round-Trip Time (RTT) propagation delay is limited to within 1 ms. Using the HARQ protocol, the transmitter needs to wait for feedback from the receiver before sending new data. In the case of a Negative Acknowledgement (NACK), the transmitter may need to retransmit the data packet. Otherwise, it can send new data. This Stop-And-Wait (SAW) process introduces an inherent latency to the communication protocol, which may reduce the link throughput. To mitigate this problem, the existing HARQ processes allow multiple HARQ processes to be active at the transmitter. That is, the transmitter can initiate multiple transmissions in parallel without waiting for the HARQ to complete. For example, in the case of 16 (8) HARQ processes in NR (LTE) DL, the gNB (eNB) can initiate up to 16 (8) new data transmissions without waiting for the ACK of the first packet transmission. Note that for terrestrial networks where the propagation delay is typically less than 1 ms, there are a sufficient number of HARQ processes.

[0176] Figure 7 The following shows the various delays associated with the HARQ process:

[0177] 1. The packet first arrives at the receiver after the propagation delay Tp.

[0178] 2. The receiver sends feedback after the processing / slot delay T1.

[0179] 3. The feedback arrives at the data transmitter after the propagation delay Tp.

[0180] 4. The transmitter may send a retransmission or new data after the processing / slot delay T2.

[0181] 5. To avoid HARQ stall, the minimum required number of HARQ processes is ceil((2Tp + T1 + T2) / Ts), where Ts refers to the slot duration in NR and the subframe duration in LTE.

[0182] The existing HARQ processes in LTE / NR are mainly designed for terrestrial networks where the propagation delay is typically limited to 1 ms. However, there are problems with using the existing HARQ protocol in large propagation delays.

[0183] More specifically, when the propagation delay is much larger than the propagation delay supported by the allowed number of HARQ processes, existing HARQ mechanisms may not be feasible. For example, consider the case where LTE DL is used for satellite communication. For the GEO case, the RTT propagation delay can be approximately 500 ms. In the case of 8 HARQ processes, the eNB needs to wait approximately 500 ms before sending new data. This translates to benefiting only from a low fractional multiple (8 / 500) of the available peak throughput. Even in the case where 16 HARQ processes are supported in NR and the slot duration is 1 ms, the available peak throughput as a percentage of the total channel capacity is very low. Table 1 outlines the available peak throughput for UEs for LEO, MEO, and GEO satellites. Therefore, in the absence of a sufficient number of HARQ processes, the absolute magnitude of the propagation delay may make closed-loop HARQ communication impractical.

[0184] The number of HARQ processes supported by existing HARQ protocols is insufficient to absorb potentially large propagation delays in non-terrestrial networks. For example, Table 1 shows that operating HARQ in large propagation delays requires a significant increase in the existing number of HARQ processes. Unfortunately, for the following reasons, supporting many HARQ processes (especially at the UE) is challenging: (i) large memory is required at both the transmitter and the receiver; (ii) it may be necessary to reduce the HARQ buffer size (and thus reduce the maximum supported transport block size TBS); (iii) a large number of HARQ buffers imply a large number of HARQ receivers; (iv) it may increase the signaling overhead of the HARQ ID. In fact, in NR, the HARQ process ID is indicated in the downlink control information (DCI), and currently there are 4 bits in the HARQ process number field to indicate this. Increasing the number of HARQ processes to 500 would require approximately 9 bits (more than twice the current 4 bits in the HARQ process number field).

[0185] Table 1 Required number of HARQ processes in satellite networks. Also listed is the peak throughput with 16 HARQ processes and Ts = 1 ms.

[0186]

[0187] Note that Rel-15 NR supports up to 16 HARQ processes in UL / DL. LTE typically supports 8 processes in UL / DL.

[0188] In short, existing (PHY / MAC) HARQ mechanisms are not suitable for non-terrestrial networks with large propagation delays. Moreover, there is no existing signaling mechanism for disabling HARQ at the PHY / MAC layer.

[0189] One solution is to make the use of HARQ network-configurable [3]. In other words, the network should be able to configure the UE to turn off HARQ. If HARQ is turned off, there is no feedback for the transmission.

[0190] Now consider the NR HARQ ACK / NACK feedback on the PUCCH. In NR, when receiving the Physical Downlink Shared Channel (PDSCH) in the downlink from the serving gNB in slot n, if the PDSCH is successfully decoded, the UE feeds back a HARQ ACK to the gNB via a PUCCH (Physical Uplink Control Channel) resource in the uplink in slot n + k. Otherwise, the UE sends a HARQ NACK to the gNB in slot n + k to indicate that the PDSCH was not successfully decoded. If the PDSCH carries two Transport Blocks (TBs), a HARQ ACK / NACK is reported for each TB, such that if one TB is not successfully decoded, only that TB needs to be retransmitted by the gNB. Spatial bundling can be configured, in which case the logical "AND" of the decoding states of TB1 and TB2 is fed back to the gNB.

[0191] For DCI format 1-0, k is indicated by the 3-bit PDSCH-to-HARQ timing indicator field. For DCI format 1-1, k is indicated by the 3-bit PDSCH-to-HARQ timing indicator field (if present) or by a higher layer via Radio Resource Control (RRC) signaling.

[0192] If Code Block Group (CBG) transmission is configured, instead, a HARQ ACK / NACK for each CBG in the TB is reported.

[0193] In the case of Carrier Aggregation (CA) with multiple carriers and / or TDD operation, multiple aggregated HARQ ACK / NACK bits need to be sent in a single PUCCH.

[0194] In NR, up to four PUCCH resource sets can be configured for the UE. The PUCCH resource set with pucch-ResourceSetId = 0 can have up to 32 PUCCH resources, while for the PUCCH resource sets with pucch-ResourceSetId = 1 to 3, each set can have up to 8 PUCCH resources. The UE determines the PUCCH resource set in a slot based on the number of aggregated UCI (Uplink Control Information) bits to be sent in that slot. The UCI bits consist of HARQ ACK / NACK, Scheduling Request (SR), and Channel State Information (CSI) bits.

[0195] If the UE transmits O UCIFor UCI information bits, the UE determines the PUCCH resource set as

[0196] · If O UCI ≤ 2 includes 1 or 2 HARQ-ACK information bits and a positive or negative SR on one SR transmission occasion (if the transmission of HARQ-ACK information and SR occurs simultaneously), then it is the first set of PUCCH resources with pucch-ResourceSetId = 0, or

[0197] · If 2 < O UCI ≤ N 2 (if provided by the higher layer), then it is the second set of PUCCH resources with pucch-ResourceSetId = 1, or

[0198] · If N 2 < O UCI ≤ N 3 (if provided by the higher layer), then it is the third set of PUCCH resources with pucch-ResourceSetId = 2, or

[0199] · If N 3 < O UCI ≤ 1706 (if provided by the higher layer), then it is the fourth set of PUCCH resources with pucch-ResourceSetId = 3,

[0200] where N 1 < N 2 < N 3 is provided by the higher layer.

[0201] For PUCCH transmission with HARQ-ACK information, the UE determines the PUCCH resource after determining the PUCCH resource set. The PUCCH resource determination is based on the 3-bit PUCCH Resource Indicator (PRI) field in DCI format 1_0 or DCI format 1_1.

[0202] If more than one DCI format 1_0 or 1_1 is received in the case of CA and / or TDD, the PUCCH resource determination is based on the PUCCH Resource Indicator (PRI) field in the last DCI format 1_0 or DCI format 1_1 among the multiple received DCI format 1_0 or DCI format 1_1 detected by the UE.

[0203] NR Rel-15 supports two types of HARQ codebooks (i.e., semi-static (type 1) and dynamic (type 2) codebooks) for HARQ Ack / Nack multiplexing of multiple PDSCHs on one or more component carriers (CCs). The UE can be configured to use either of the codebooks for HARQ Ack / Nack feedback.

[0204] Now consider NR type 1 HARQ-ACK codebook determination. The HARQ codebook (CB) size (DL association set) in time is determined based on a configured set of HARQ-ACK timings K1 and, in the case of TDD, based on a semi-statically configured TDD mode. For a PDCCH received in slot n of a PDSCH, K1 is signaled in the PDCCH, and K1 indicates that the HARQ A / N feedback for the PDSCH occurs in slot n + K1.

[0205] Figure 8 An example of a TDD mode with a set of K1 from 1 to 5 and a configured time-domain resource allocation table or pdsch-TimeDomainAllocationList without non-overlapping PDSCH TDRA allocations (i.e., only one PDSCH can be scheduled in a slot) is shown. In this case, there are 5 entries in the HARQ codebook, one entry for each K1 value. For a slot without PDSCH transmission or for a slot in which no PDSCH is detected, the corresponding entry in the codebook is filled with NACK.

[0206] If the UE supports receiving more than one unicast PDSCH per slot, one HARQ codebook entry is reserved for each non-overlapping time-domain resource allocation in the pdsch-symbolAllocation table per slot; otherwise, one HARQ entry is reserved per slot.

[0207] Now consider NR type 2 HARQ-ACK codebook determination. Different from the type 1 HARQ codebook, the size of the type 2 HARQ codebook changes dynamically based on the number of DCIs associated with the same PUCCH resource used for HARQ Ack / NACK feedback for scheduled PDSCH reception or SPS PDSCH release. The number of DCIs can be derived based on the counter DAI (downlink assignment indicator) field in the DCI, and in the case of DCI format 1-1, if more than one serving cell is configured, it can also be derived based on the total DAI field.

[0208] The value of the counter DAI field in DCI format 1_0 or DCI format 1_1 represents the cumulative number of {serving cell, PDCCH monitoring occasion} pairs up to the current serving cell and the current PDCCH monitoring occasion, in which there is (are) (one or more) PDSCH reception(s) or (one or more) SPS PDSCH release(s) associated with DCI format 1_0 or DCI format 1_1.

[0209] When present, the value of the total DAI in DCI format 1_1 represents the total number of {serving cell, PDCCH monitoring occasion} pairs up to the current PDCCH monitoring occasion m, in which there is (are) (one or more) PDSCH reception(s) or SPS PDSCH release(s) associated with DCI format 1_0 or DCI format 1_1, and the value is updated with the PDCCH monitoring occasion.

[0210] Figure 9 An example is shown where the UE is configured with 2 serving cells and 3 PDCCH monitoring occasions. The corresponding counter DAI and total DAI values after each scheduled DCI are shown. The counter DAI is updated after each scheduled DCI, while the total DAI is updated only at each monitoring occasion. Since only 2 bits are allocated to the counter DAI or total DAI in the DCI, the actual DAI value is wrapped around using modulo 4 arithmetic. If the number of consecutive DCIs not detected is less than 4, the UE can calculate the actual number of DCIs transmitted even if some DCIs are not detected.

[0211] For DCI format 1-1, the DAI field is present only when using type 2 HARQ-ACK, and bit widths of 0, 2, or 4 bits are possible. For DCI format 1-0, the DAI field is composed of 2 bits.

[0212] There are currently some challenges. HARQ activation can be used to address the large latency in the NTN scenario. However, in the absence of a HARQ mechanism at the PHY / MAC layer, the transmission reliability will be significantly reduced. In the case of packet loss, the receiver will rely on higher layers (such as RLC) retransmission and error control protocols to recover the lost packets. However, this may lead to additional latency due to the large propagation delay (i.e., for exactly the same reason, HARQ is considered unsuitable and deactivated in the first place).

[0213] Certain aspects of the present disclosure and its embodiments may provide solutions to these or other challenges. Some embodiments herein include methods for improving (e.g., at the PHY / MAC layer) transmission reliability in situations where the HARQ feedback / retransmission protocol / mechanism is disabled for some HARQ processes and enabled for the remaining HARQ processes.

[0214] More specifically, the HARQ protocol / mechanism as used herein refers to the HARQ process at the PHY / MAC layer. The term "feedback-less HARQ process" as used herein refers to a HARQ process for which HARQ feedback is disabled. A feedback-less HARQ process is Figure 1 an example of an error control process 20-1…20-N in which feedback is disabled. In the case where HARQ feedback is disabled, retransmission can be effectively disabled for such a HARQ process. Similarly, the term "feedback-based HARQ process" as used herein refers to a HARQ process for which HARQ feedback is enabled. In the case where HARQ feedback is enabled, retransmission can be effectively enabled for such a HARQ process. A feedback-based HARQ process is Figure 1 an example of an error control process 20-1…20-N in which feedback is enabled. In this context, some embodiments herein use different transmission configurations for feedback-based and feedback-less HARQ processes. Using this approach, PHY layer transmissions can be made more reliable for feedback-less HARQ processes without compromising the performance of feedback-based HARQ processes. This avoids unnecessarily invoking higher layer retransmission / error control protocols in feedback-less HARQ processes, where unnecessary invocation of higher layer retransmission / error control protocols may increase further latency and reduce throughput due to large propagation delays in non-terrestrial networks.

[0215] Some embodiments generally adapt HARQ to non-terrestrial networks.

[0216] Some embodiments introduce a method of prescribing different parameter configurations for HARQ processes with disabled HARQ feedback and HARQ processes with enabled HARQ feedback. This enables the network to configure (e.g., via Figure 1control signaling 26) parameters related to power control, modulation and coding scheme (MCS), waveform, etc., making the transmission of the non-feedback HARQ process more reliable. By improving the reliability of the non-feedback HARQ process, some embodiments can help reduce the total latency by avoiding the need to invoke higher layer error control / retransmission processes when HARQ is disabled at the PHY / MAC layer. Additionally, this additional reliability can be obtained without interfering with the operation of the feedback-based HARQ process. Some embodiments alternatively or additionally provide the necessary UE processes for determining the NR type 1 HARQ codebook entries when the UE is configured with both a "non-feedback HARQ process" and a "feedback-based HARQ process".

[0217] Certain embodiments may provide one or more of the following technical advantages. Some embodiments introduce a method for differently configuring the transmission parameters of HARQ processes in the case of enabling or disabling HARQ. Without such a distinction, the same parameter configuration would apply to all HARQ processes regardless of whether the HARQ mechanism is disabled. By the ability to signal different parameter configurations for different HARQ processes, there are several potential advantages: (i) it helps improve the transmission reliability of the non-feedback HARQ process; (ii) a more reliable non-feedback HARQ process means that the error control process / retransmission is conservatively triggered, which can help reduce latency compared to the case where RLC retransmissions are overused due to decoding errors at the PHY / MAC layer; and / or (iii) it helps avoid performance degradation of the feedback-based HARQ process because the network does not need to change the parameter configuration of the feedback-based HARQ process to accommodate the non-feedback HARQ process.

[0218] Some embodiments separate the transmission configurations of the feedback-based and non-feedback HARQ processes. So far, the transmission parameter configurations signaled by the gNB to the UE have been applied to all HARQ processes. In contrast, some embodiments herein separate the transmission parameter configuration of the non-feedback HARQ process from the transmission parameter configuration of the feedback-based HARQ process.

[0219] Consider an example where HARQ feedback is enabled for HARQ process ID 0 and disabled for the remaining HARQ processes. Then, according to some embodiments herein, the gNB can configure (e.g., via Figure 1 control signaling 26) two sets of transmission parameter configurations: one set for the feedback-based HARQ process with ID 0 and another set for the non-feedback HARQ process. Then, the UE applies the corresponding configuration to the HARQ process depending on whether the HARQ process is a feedback-based HARQ process or a non-feedback HARQ process.

[0220] Some embodiments specifically relate to power control configurations. For example, one or more embodiments introduce new Radio Resource Control (RRC) signaling to allow the gNB to independently set power control parameters for both non-feedback and feedback-based Hybrid Automatic Repeat reQuest (HARQ) processes.

[0221] In one example, the power control profile can be set more aggressively for HARQ processes where HARQ feedback is disabled. For example, the target received power can be set to a higher value to encourage the UE to transmit at a higher power when using non-feedback HARQ processes. However, for feedback-based HARQ processes, normal power control configurations can be used.

[0222] The following are example power control parameters that can be set differently for non-feedback and feedback-based HARQ processes: (i) nominal UE-specific P0; (ii) path loss compensation factor alpha; (iii) deltaMCS; (iv) tpc-accumulation; (v) twoPUSCH-PC-AdjustmentStates; and / or (vi) the mapping of the Transmit Power Control (TPC) command field in the Downlink Control Information (DCI) to absolute or cumulative closed-loop power control values.

[0223] Other embodiments herein relate to transmit power selection. For example, one embodiment introduces new signaling to allow the gNB to directly set the transmit power for non-feedback HARQ processes. That is, this embodiment allows the gNB to directly set the UE transmit power for a specific HARQ process, rather than setting power control parameters differently for non-feedback and feedback-based HARQ processes.

[0224] Consider an example. Instead of relying on existing power control processes, the gNB can directly set the transmit power for Physical Uplink Shared Channel (PUSCH) transmissions on non-feedback HARQ processes. For example, it may be that the power control process recommends a transmit power below the maximum transmit power. To increase the received Signal-to-Noise Ratio (SNR) at the gNB, some embodiments allow the UE to completely bypass the power control process and transmit at the maximum power. With a higher signal-to-noise ratio (SNR), the transmission is more likely to be successfully decoded.

[0225] In another embodiment, 1 bit is used to signal to the UE whether to transmit at the maximum power.

[0226] In yet another embodiment, if the gNB wants to select a transmit power level from a set with up to 2 N possible values, N bits can be reserved for this purpose. For example, in the case of N = 2 bits, the gNB can indicate four possibilities:

[0227] Bit value Meaning 00 Transmission at existing power 01 Transmission at X dB lower than maximum power 10 Transmission at Y dB lower than maximum power 11 Transmission at maximum power

[0228] The values “X” and “Y” can be fixed in the 3GPP specifications or can be configured in RRC signaling.

[0229] Typically, then, some embodiments introduce new signaling to allow the gNB to set different transmission configurations for feedback-based and non-feedback HARQ processes.

[0230] Consider another example. An aggregation factor greater than 1 can be configured and applied to non-feedback HARQ processes to improve reliability, while an aggregation factor equal to 1 can be configured and applied to feedback-based HARQ processes. As another example, to improve reliability, a more robust waveform can be configured for HARQ processes that disable HARQ feedback. For example, the DFT-S-OFDM waveform can be used for non-feedback HARQ processes, while CP-OFDM is used for feedback-based HARQ processes.

[0231] Other example transmission parameters that can be set differently for non-feedback HARQ processes and feedback-based HARQ processes include one or more of the following: MCS table, time-domain resource allocation table, frequency resource allocation types 0 and 1, block error rate target, physical resource block (PRB) bundling configuration, PDSCH mapping types A and B, and / or PUSCH transmission scheme (codebook-based transmission and non-codebook-based transmission).

[0232] Still other embodiments herein consider the impact of the NR type 1 HARQ-ACK codebook. In cases where the UE is configured with both “non-feedback HARQ processes” and “feedback-based HARQ processes”, some embodiments define UE procedures on how to determine the entries in the NR type 1 HARQ codebook. In one embodiment, when the UE is configured with both “non-feedback HARQ processes” and “feedback-based HARQ processes”, a UE procedure is defined for determining the NR type 1 HARQ codebook entries. In one embodiment, the UE inserts a NACK in the position in the NR type 1 HARQ-ACK codebook corresponding to the PDSCH associated with the non-feedback HARQ process. For the PDSCH associated with the feedback-based HARQ process, the UE inserts an ACK or a NACK depending on the decoding result of the PDSCH.

[0233] Figure 10An example of a type 1 HARQ codebook is shown, where K1 = {1, 2, 3, 4, 5} and where NACK is inserted in the positions corresponding to the PDSCH associated with the non-feedback HARQ process. In the DL association setting for the HARQ CB in slot n, the UE receives the PDSCH associated with the non-feedback HARQ process in slot n-3 (corresponding to K1 = 3), and receives the PDSCH associated with the feedback-based HARQ process in slot n-1 (corresponding to K1 = 1). Since there is no ACK-NACK feedback for the PDSCH associated with the non-feedback HARQ process, the UE will insert NACK (N) in position K1 = 3 corresponding to the PDSCH received in slot n-3. For the PDSCH received in slot n-1 associated with the feedback-based HARQ process, the UE inserts the ACK-NACK bit X, which depends on the result of the PDSCH associated with the feedback-based HARQ process.

[0234] Similarly, in the DL association setting for the HARQ CB in slot n+5, the UE inserts NACK in position K1 = 2 corresponding to the PDSCH associated with the non-feedback HARQ process. For the PDSCH received in slot n+1 associated with the feedback-based HARQ process, the UE inserts the ACK-NACK bit X, which depends on the result of the PDSCH associated with the feedback-based HARQ process.

[0235] Other embodiments herein relate to the efficient use of unused DCI fields. When the PDSCH corresponding to the non-feedback HARQ process is scheduled by DCI, one or more DCI fields may be unused. For example, since there is no ACK / NACK feedback for the PDSCH corresponding to the non-feedback HARQ process, DCI fields such as DAI, RV (redundancy version), PDSCH to HARQ feedback timing, and PRI are unused. In one embodiment, one or a combination of these fields can be used to dynamically indicate other information related to the PDSCH corresponding to the non-feedback HARQ process.

[0236] In a variant of this embodiment, the aggregation factor list may be configured for a non-feedback HARQ process, and one of the aggregation factor values may be dynamically indicated by one or a combination of DCI fields such as DAI, RV (Redundancy Version), PDSCH-to-HARQ feedback timing, and PRI. For example, when the UE receives a PDSCH corresponding to a non-feedback HARQ process (as indicated by the HARQ process number field in the DCI), the UE decodes one or a combination of the DA, RV, PDSCH-to-HARQ feedback timing, and PRI fields to infer the aggregation factor value associated with the PDSCH. If the UE receives a PDSCH corresponding to a feedback-based HARQ process, the DAI, RV, PDSCH-to-HARQ feedback timing, and PRI fields are decoded in a conventional manner as specified in NR Rel-15.

[0237] In this regard, note that different types of data traffic may have different reliability requirements. Therefore, dynamically indicating the aggregation factor is beneficial. For example, for data that requires higher reliability, a larger aggregation factor may be dynamically indicated, while for data that requires lower reliability, a smaller aggregation factor may be dynamically indicated. This becomes particularly important when there is no HARQ Ack / Nack feedback.

[0238] In another variant of this embodiment, one or more of the DCI fields such as DAI, RV, PDSCH-to-HARQ feedback timing, and PRI may be used together with the HARQ process number field to indicate the HARQ process number. This is useful in cases where the number of HARQ processes in the NTN scenario increases to more than 16 processes, in which case the 4 bits in the HARQ process number field in the DCI are not sufficient. Figure 11 An example is shown of using the RV field and the HARQ process number field to identify the HARQ process number when more than 16 HARQ processes are configured. In this example, 19 HARQ processes are configured, where 4 of the 19 HARQ processes (processes 16 - 19) are non-feedback HARQ processes, and 15 of the 19 HARQ processes (processes 1 - 15) are feedback-based HARQ processes. The feedback-based HARQ processes are directly indicated by the corresponding values indicated by the HARQ process number field. To indicate one of the non-feedback HARQ processes, the HARQ process number field indicates a specific value (value 0 in this example), and the value indicated by the RV field indicates one of the configured non-feedback HARQ processes. Thus, Figure 11 The example of... shows the use of the HARQ process number field in combination with one or more of the DAI, RV, PDSCH-to-HARQ feedback timing, and PRI fields to identify the HARQ process number.

[0239] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network shown in Figure 12 . For simplicity, the wireless network of Figure 12 only depicts network 1206, network nodes 1260 and 1260b, and WDs 1210, 1210b, and 1210c. In reality, a wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device. Among the components shown, network node 1260 and wireless device (WD) 1210 are depicted in additional detail. A wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0240] A wireless network may include any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system and / or be interfaced with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, a particular embodiment of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards such as the IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0241] Network 1206 may include one or more backhaul networks, core networks, IP networks, Public Switched Telephone Network (PSTN), packet data networks, optical networks, Wide Area Networks (WAN), Local Area Networks (LAN), Wireless Local Area Networks (WLAN), wired networks, wireless networks, Metropolitan Area Networks, and other networks that enable communication between devices.

[0242] Network nodes 1260 and WD 1210 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals (either via wired or wireless connections).

[0243] 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 B, evolved Node B (eNB), and NR Node B (gNB)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmission power levels) and can thus also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a repeater. A network node can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), which is sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna into an antenna integrated radio device. The parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

[0244] Additional examples of network nodes include multi-standard radio (MSR) devices (such as MSR BS), network controllers (such as radio network controllers (RNC) or base station controllers (BSC)), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLC), and / or MDT. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable and / or provide access to a wireless network for a wireless device or to provide some service to a wireless device that is already connected to the wireless network.

[0245] In Figure 12 it, network node 1260 includes a processing circuit 1270, a device-readable medium 1280, an interface 1290, auxiliary equipment 1284, a power supply 1286, a power supply circuit 1287, and an antenna 1262. Although Figure 12The network node 1260 shown in the example wireless network can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It is to be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods and / or processes disclosed herein. Additionally, although the components of network node 1260 are depicted as nested within multiple boxes or as a single box within a larger box, in reality, a network node can include multiple different physical components that make up a single shown component (e.g., the device-readable medium 1280 can include multiple individual hard disk drives as well as multiple RAM modules).

[0246] Similarly, network node 1260 can be composed of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), and these components can each have their own corresponding components. In certain scenarios where network node 1260 includes multiple individual components (e.g., BTS and BSC components), one or more of the individual components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such a scenario, each unique NodeB and BSC pair can be considered as a single individual network node in some instances. In some embodiments, network node 1260 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device-readable media 1280 for different RATs) and some components can be reused (e.g., the same antenna 1262 can be shared by RATs). Network node 1260 can also include multiple sets of the various shown components for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into network node 1260. These wireless technologies can be integrated into the same or different chips or chip sets and other components within network node 1260.

[0247] The processing circuit 1270 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 1270 can include processing the information obtained by the processing circuit 1270 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of such processing.

[0248] The processing circuitry 1270 may include one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or coded logic operable to provide the functionality of the network node 1260 alone or in conjunction with other components of the network node 1260 (such as the device readable medium 1280). Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.

[0249] For example, the processing circuitry 1270 may execute instructions stored in the device readable medium 1280 or in a memory within the processing circuitry 1270. In some embodiments, the processing circuitry 1270 may include a system on a chip (SOC). As a more specific example, the instructions stored in the medium 1280 (also referred to as a computer program product) may include instructions that, when executed by the processing circuitry 1270, may configure the network node 1260 to perform operations corresponding to the various exemplary methods (e.g., procedures) described herein.

[0250] In some embodiments, the processing circuitry 1270 may include one or more of radio frequency (RF) transceiver circuitry 1272 and baseband processing circuitry 1274. In some embodiments, the radio frequency (RF) transceiver circuitry 1272 and the baseband processing circuitry 1274 may be on separate chips (or chip sets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, some or all of the RF transceiver circuitry 1272 and the baseband processing circuitry 1274 may be on the same chip or chip set, board, or unit.

[0251] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 1270 executing instructions stored on the device readable medium 1280 or in a memory within the processing circuitry 1270. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1270 without executing instructions stored on a separate or discrete device readable medium (such as in a hardwired manner). In any of those embodiments, whether or not instructions are executed on a device readable storage medium, the processing circuitry 1270 may be configured to perform the described functionality. The benefits provided by such functionality are not limited to only the processing circuitry 1270 or other components of the network node 1260, but are enjoyed by the network node 1260 as a whole and / or by the end user and the wireless network generally.

[0252] The apparatus-readable medium 1280 can include any form of volatile or non-volatile computer-readable memory, including without limitation: permanent storage devices, solid-state memories, remotely mounted memories, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, compact discs (CDs) or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory apparatus-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuitry 1270. The apparatus-readable medium 1280 can store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that can be executed by the processing circuitry 1270 and utilized by the network node 1260. The apparatus-readable medium 1280 can be used to store any calculations performed by the processing circuitry 1270 and / or any data received via the interface 1290. In some embodiments, the processing circuitry 1270 and the apparatus-readable medium 1280 can be considered to be integrated.

[0253] The interface 1290 is used for wired or wireless communication of signaling and / or data between the network node 1260, the network 1206, and / or the WD 1210. As shown, the interface 1290 includes (one or more) ports / (one or more) terminals 1294 for sending data to and receiving data from the network 1206 via a wired connection, for example. The interface 1290 also includes a radio front-end circuit 1292, which can be coupled to the antenna 1262 or in some embodiments is part of the antenna 1262. The radio front-end circuit 1292 includes a filter 1298 and an amplifier 1296. The radio front-end circuit 1292 can be connected to the antenna 1262 and the processing circuitry 1270. The radio front-end circuit can be configured to condition the signals transmitted between the antenna 1262 and the processing circuitry 1270. The radio front-end circuit 1292 can receive digital data to be transmitted via a wireless connection to other network nodes or WDs. The radio front-end circuit 1292 can convert the digital data into a radio signal with suitable channel and bandwidth parameters using a combination of the filter 1298 and / or the amplifier 1296. The radio signal can then be transmitted via the antenna 1262. Similarly, when receiving data, the antenna 1262 can collect the radio signal, which is then converted into digital data by the radio front-end circuit 1292. The digital data can be passed to the processing circuitry 1270. In other embodiments, the interface can include different components and / or different combinations of components.

[0254] In some alternative embodiments, network node 1260 may not include a separate radio front-end circuit 1292, but rather the processing circuit 1270 may include the radio front-end circuit and may be connected to the antenna 1262 without a separate radio front-end circuit 1292. Similarly, in some embodiments, all or some of the RF transceiver circuit 1272 may be considered part of the interface 1290. In still other embodiments, the interface 1290 may include one or more ports or terminals 1294, the radio front-end circuit 1292, and the RF transceiver circuit 1272, as part of a radio unit (not shown), and the interface 1290 may communicate with a baseband processing circuit 1274, which is part of a digital unit (not shown).

[0255] The antenna 1262 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. The antenna 1262 may be coupled to the radio front-end circuit 1290 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 1262 may include one or more omnidirectional, sector, or panel antennas operable to transmit / receive radio signals in, for example, a range between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sector antennas may be used to transmit / receive radio signals from the device within a particular area, and panel antennas may be line-of-sight antennas for transmitting / receiving radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, the antenna 1262 may be separate from the network node 1260 and may be connectable to the network node 1260 via an interface or port.

[0256] The antenna 1262, the interface 1290, and / or the processing circuit 1270 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 wireless device, another network node, and / or any other network device. Similarly, the antenna 1262, the interface 1290, and / or the processing circuit 1270 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 wireless device, another network node, and / or any other network device.

[0257] The power supply circuit 1287 may include or be coupled to a power management circuit and may be configured to supply power to components of the network node 1260 for performing the functionality described herein. The power supply circuit 1287 may receive power from a power source 1286. The power source 1286 and / or the power supply circuit 1287 may be configured to provide power to various components of the network node 1260 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power source 1286 may be included within the power supply circuit 1287 and / or the network node 1260 or external to the power supply circuit 1287 and / or the network node 1260. For example, the network node 1260 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface such as a cable, and the external power source may supply power to the power supply circuit 1287. As another example, the power source 1286 may include a power source in the form of a battery or battery pack connected to or integrated within the power supply circuit 1287. The battery may provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0258] Alternative embodiments of the network node 1260 may include Figure 12 additional components other than those shown in, which may be responsible for providing certain aspects of the functionality of the network node, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1260 may include a user interface device to allow and / or facilitate the input of information into the network node 1260 and to allow and / or facilitate the output of information from the network node 1260. This may allow and / or facilitate a user to perform diagnostic, maintenance, repair, and other management functions on the network node 1260.

[0259] In some embodiments, a wireless device (WD, e.g., WD 1210) may be configured to transmit and / or receive information without direct human interaction. For example, the WD may be designed to transmit information to the network according to a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include but are not limited to smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premise equipment (CPEs), machine type communication (MTC) devices, Internet of Things (IoT) devices, vehicle-mounted wireless terminal devices, etc.

[0260] The WD may support device - to - device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle - to - vehicle (V2V), vehicle - to - infrastructure (V2I), vehicle - to - everything (V2X), and in this case may be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, the WD may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. The WD may be a machine - to - machine (M2M) device in this case, which may be referred to as an MTC device in the 3GPP context. As a specific example, the WD may be a UE that implements the 3GPP Narrow - Band Internet of Things (NB - IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or home or personal devices (e.g., refrigerators, TVs, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other device capable of monitoring and / or reporting its operating state or other functions associated with its operation. The WD as described above may represent a wireless - connected endpoint, and in this case the device may be referred to as a wireless terminal. Additionally, the WD as described above may be mobile, and in this case it may also be referred to as a mobile device or mobile terminal.

[0261] As shown, the wireless device 1210 includes an antenna 1211, an interface 1214, a processing circuit 1220, a device - readable medium 1230, a user - interface device 1232, an auxiliary device 1234, a power source 1236, and a power - supply circuit 1237. The WD 1210 may include multiple sets of one or more of the shown components for different wireless technologies supported by the WD 1210 (such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into the same or different chips or chip - sets as other components within the WD1210.

[0262] The antenna 1211 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to the interface 1214. In some alternative embodiments, the antenna 1211 may be separate from the WD 1210 and connectable to the WD 1210 via an interface or port. The antenna 1211, the interface 1214, and / or the processing circuit 1220 may be configured to perform any of the receiving or transmitting operations described herein as being performed by the WD. Any information, data, and / or signals may be received from a network node and / or another WD. In some embodiments, the radio - front - end circuit and / or the antenna 1211 may be regarded as an interface.

[0263] As shown, interface 1214 includes radio front-end circuitry 1212 and antenna 1211. The radio front-end circuitry 1212 includes one or more filters 1218 and amplifiers 1216. The radio front-end circuitry 1214 is connected to antenna 1211 and processing circuitry 1220 and can be configured to condition signals communicated between antenna 1211 and processing circuitry 1220. The radio front-end circuitry 1212 may be coupled to or be part of antenna 1211. In some embodiments, WD 1210 may not include a separate radio front-end circuitry 1212; instead, the processing circuitry 1220 may include the radio front-end circuitry and may be connected to antenna 1211. Similarly, in some embodiments, some or all of the RF transceiver circuitry 1222 may be considered part of interface 1214. The radio front-end circuitry 1212 may receive digital data to be transmitted via a wireless connection to other network nodes or WDs. The radio front-end circuitry 1212 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1218 and / or amplifiers 1216. The radio signal may then be transmitted via antenna 1211. Similarly, upon receiving data, antenna 1211 may collect radio signals, which are then converted into digital data by radio front-end circuitry 1212. The digital data may be communicated to processing circuitry 1220. In other embodiments, the interface may include different components and / or different combinations of components.

[0264] The processing circuitry 1220 may include one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or coded logic operable to provide WD1210 functionality alone or in conjunction with other WD 1210 components such as device-readable medium 1230. Such functionality may include any of the various wireless features or benefits discussed herein.

[0265] For example, the processing circuitry 1220 may execute instructions stored in the device-readable medium 1230 or in a memory within the processing circuitry 1220 to provide the functionality disclosed herein. More specifically, the instructions stored in medium 1230 (also referred to as a computer program product) may include instructions that, when executed by the processor 1220, may configure the wireless device 1210 to perform operations corresponding to the various exemplary methods (e.g., processes) described herein.

[0266] As shown, processing circuitry 1220 includes one or more of RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226. In other embodiments, the processing circuitry may include different components and / or different combinations of components. In certain embodiments, the processing circuitry 1220 of WD 1210 may include a system-on-a-chip (SOC). In some embodiments, the RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226 may be on separate chips or chip sets. In alternative embodiments, some or all of the baseband processing circuitry 1224 and application processing circuitry 1226 may be combined into one chip or chip set, and the RF transceiver circuitry 1222 may be on a separate chip or chip set. In yet some other alternative embodiments, some or all of the RF transceiver circuitry 1222 and baseband processing circuitry 1224 may be on the same chip or chip set, and the application processing circuitry 1226 may be on a separate chip or chip set. In yet some other alternative embodiments, some or all of the RF transceiver circuitry 1222, baseband processing circuitry 1224, and application processing circuitry 1226 may be combined in the same chip or chip set. In some embodiments, the RF transceiver circuitry 1222 may be part of the interface 1214. The RF transceiver circuitry 1222 may condition RF signals for the processing circuitry 1220.

[0267] In certain embodiments, some or all of the functionality described herein as being performed by the WD may be provided by processing circuitry 1220 executing instructions stored on a device-readable medium 1230, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1220 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 or not instructions stored on a device-readable medium are executed, the processing circuitry 1220 may be configured to perform the described functionality. The benefits provided by such functionality are not limited to only the processing circuitry 1220 or other components of the WD 1210, but are enjoyed by the WD 1210 as a whole and / or by the end user and the wireless network generally.

[0268] The processing circuitry 1220 may be configured to perform any determination, calculation, or similar operation described herein as being performed by the WD (e.g., certain obtaining operations). Such operations performed by the processing circuitry 1220 may include processing information obtained by the processing circuitry 1220 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored by the WD 1210, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of such processing.

[0269] The apparatus-readable medium 1230 may be operable to store a computer program, software, an application (including one or more of logic, rules, code, tables, etc.), and / or other instructions that can be executed by the processing circuitry 1220. The apparatus-readable medium 1230 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disc (CD) or a digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory apparatus-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuitry 1220. In some embodiments, the processing circuitry 1220 and the apparatus-readable medium 1230 may be considered to be integrated.

[0270] The user interface device 1232 may include components that allow and / or facilitate interaction between a human user and the WD 1210. Such interaction may take many forms, such as visual, auditory, tactile, etc. The user interface device 1232 may be operable to generate output to the user and allow and / or facilitate the user to provide input to the WD 1210. The type of interaction may vary depending on the type of user interface device 1232 installed in the WD 1210. For example, if the WD 1210 is a smart phone, the interaction may be via a touch screen; if the WD 1210 is a smart meter, the interaction may be through a screen that provides usage amounts (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1232 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 1232 may be configured to allow and / or facilitate input of information into the WD 1210 and be connected to the processing circuitry 1220 to allow and / or facilitate the processing circuitry 1220 to process the input information. The user interface device 1232 may include, for example, a microphone, a proximity or other sensor, a keypad / button, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 1232 is also configured to allow and / or facilitate output of information from the WD 1210 and allow and / or facilitate the processing circuitry 1220 to output information from the WD 1210. The user interface device 1232 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device 1232, the WD 1210 may communicate with an end user and / or a wireless network and allow and / or facilitate them to benefit from the functionality described herein.

[0271] The auxiliary device 1234 is operable to provide more specific functionality that may not generally be performed by the WD. This may include dedicated sensors for making measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 1234 may vary depending on the embodiment and / or scenario.

[0272] The power source 1236 may take the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power cell. The WD 1210 may further include a power circuit 1237 for delivering power from the power source 1236 to various parts of the WD 1210 that require power from the power source 1236 to perform any functionality described or indicated herein. The power circuit 1237 may include a power management circuit in certain embodiments. The power circuit 1237 may additionally or alternatively be operable to receive power from an external power source; in which case the WD 1210 may be connectable to an external power source (such as an electrical outlet) via an input circuit or interface (such as a power cable). The power circuit 1237 may also be operable in certain embodiments to deliver power from an external power source to the power source 1236. This may be used, for example, for charging the power source 1236. The power circuit 1237 may perform any conversion or other modification on the power from the power source 1236 to make it suitable for supplying the corresponding components of the WD 1210.

[0273] Figure 13 An embodiment of a UE in accordance with various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device (e.g., a smart sprinkler device controller) that is intended for sale to or operated by a human user but may not be or may not initially be associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operated by an end user but may be associated with or operate for the benefit of a user. The UE 13220 may be any UE identified by the Third Generation Partnership Project (3GPP), including an NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As shown in Figure 13 The UE 1300 shown in is an example of a WD configured for communication according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as the GSM, UMTS, LTE, and / or 5G standards of 3GPP. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 13is a UE, but the components discussed in this document are equally applicable to WD, and vice versa.

[0274] In Figure 13 , the UE 1300 includes a processing circuit 1301 that is operatively coupled to an input / output interface 1305, a radio frequency (RF) interface 1309, a network connection interface 1311, a memory 1315 (including a random access memory (RAM) 1317, a read-only memory (ROM) 1319, and a storage medium 1321, etc.), a communication subsystem 1331, a power supply 1333, and / or any other components or any combination thereof. The storage medium 1321 includes an operating system 1323, application programs 1325, and data 1327. In other embodiments, the storage medium 1321 may include other similar types of information. Some UEs may utilize Figure 13 all of the components shown in

[0275] In Figure 13 , the processing circuit 1301 may be configured to process computer instructions and data. The processing circuit 1301 may be configured to implement any sequential state machine that operates to execute machine instructions stored in the memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with suitable firmware; one or more stored programs, a general-purpose processor (such as a microprocessor or a digital signal processor (DSP)) together with suitable software; or any combination of the above. For example, the processing circuit 1301 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0276] In the depicted embodiment, the input / output interface 1305 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1300 may be configured to use an output device via the input / output interface 1305. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 1300. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1300 may be configured to use an input device via the input / output interface 1305 to allow and / or facilitate a user to capture information into the UE 1300. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video disc camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. The sensor may be, for example, an accelerometer, a gyroscope, an inclinometer, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0277] In Figure 13 it, the RF interface 1309 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 1311 may be configured to provide a communication interface to the network 1343a. The network 1343a may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1343a may include a Wi-Fi network. The network connection interface 1311 may be configured to include a receiver and a transmitter interface for communicating with one or more other devices via a communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 1311 may implement receiver and transmitter functionality suitable for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0278] The RAM 1317 can be configured to be connected to the processing circuit 1301 via an interface through the bus 1302 to provide storage or caching of data or computer instructions during the execution of software programs such as operating systems, application programs, and device drivers. The ROM 1319 can be configured to provide computer instructions or data to the processing circuit 1301. For example, the ROM 1319 can be configured to store invariant low-level system code or data for basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup, or receiving key strokes from a keyboard. The storage medium 1321 can be configured to include memories such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridge disks, or flash drives. In one example, the storage medium 1321 can be configured to include an operating system 1323, application programs 1325 (such as a web browser application, widget or gadget engine, or another application), and data files 1327. The storage medium 1321 can store any operating system or combination of operating systems from a variety of different operating systems or combinations of operating systems for use by the UE 1300. For example, the application programs 1325 can include executable program instructions (also referred to as computer program products) that, when executed by the processor 1301, can configure the UE 1300 to perform operations corresponding to the various exemplary methods (e.g., processes) described herein.

[0279] The storage medium 1321 can be configured to include a number of physical drive units such as redundant array of independent disks (RAID), floppy disk drives, flash memories, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high-definition digital versatile disc (HD-DVD) optical disc drives, internal hard disk drives, Blu-ray disc drives, holographic digital data storage (HDDS) optical disc drives, external miniature dual in-line memory modules (DIMMs), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memories (such as subscriber identity modules or removable user identity (SIM / RUIM) modules), other memories, or any combination thereof. The storage medium 1321 can allow and / or facilitate the UE 1300 to access computer-executable instructions, application programs, etc. stored on a temporary or non-temporary memory medium to offload data or upload data. An article of manufacture (such as an article of manufacture utilizing a communication system) can be tangibly embodied in the storage medium 1321, which can include a device-readable medium.

[0280] In Figure 13In [the figure], the processing circuit 1301 can be configured to communicate with the network 1343b using the communication subsystem 1331. The network 1343a and the network 1343b can be the same one or more networks or different one or more networks. The communication subsystem 1331 can be configured to include one or more transceivers for communicating with the network 1343b. For example, the communication subsystem 1331 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication (such as another WD, UE, or a base station of a radio access network (RAN)) according to one or more communication protocols (such as IEEE 802.13, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include a transmitter 1333 and / or a receiver 1335 to respectively implement transmitter or receiver functionality suitable for the RAN link (such as frequency allocation, etc.). In addition, the transmitter 1333 and the receiver 1335 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0281] In the illustrated embodiment, the communication functions of the communication subsystem 1331 can include data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth, near-field communication), location-based communication (such as using the Global Positioning System (GPS) to determine location), another similar communication function, or any combination thereof. For example, the communication subsystem 1331 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1343b can include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1343b can be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1313 can be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1300.

[0282] The features, benefits, and / or functions described herein can be implemented in one of the components of UE 1300 or divided across multiple components of UE 1300. Additionally, the features, benefits, and / or functions described herein can be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem 1331 can be configured to include any of the components described herein. Additionally, processing circuitry 1301 can be configured to communicate with any of such components via bus 1302. In another example, any of such components can be represented by program instructions stored in a memory, which, when executed by processing circuitry 1301, perform the corresponding functions described herein. In another example, the functionality of any of such components can be divided between processing circuitry 1301 and communication subsystem 1331. In another example, the non-computation-intensive functions of any of such components can be implemented in software or firmware and the computation-intensive functions can be implemented in hardware.

[0283] Figure 14 is a schematic block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which can include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or an apparatus (e.g., a UE, a wireless device, or any other type of communication device) or its components, and involves the implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0284] In some embodiments, some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1400 hosted by one or more of the hardware nodes 1430. Additionally, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be fully virtualized.

[0285] The functionality may be implemented by one or more applications 1420 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.), which operate to implement some of the features, functionality, and / or benefits of some of the embodiments disclosed herein. The applications 1420 run in a virtualized environment 1400 that provides hardware 1430 including processing circuitry 1460 and memory 1490. The memory 1490 contains instructions 1495 executable by the processing circuitry 1460, whereby the applications 1420 operate to provide one or more of the features, benefits, and / or functionality disclosed herein.

[0286] The virtualized environment 1400 may include general or special-purpose network hardware devices (or nodes) 1430 that include a set of one or more processors or processing circuitry 1460, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuitry, including digital or analog hardware components or specialized processors. Each hardware device may include a memory 1490-1, which may be non-permanent memory for temporarily storing instructions 1495 or software executed by the processing circuitry 1460. Each hardware device may include one or more network interface controllers (NICs) 1470 (also referred to as network interface cards), which include physical network interfaces 1480. For example, the instructions 1495 may include program instructions (also referred to as computer program products) that, when executed by the processing circuitry 1460, may configure the hardware node 1420 to perform operations corresponding to various exemplary methods (e.g., processes) described herein. Such operations may also be attributed to the (one or more) virtual nodes 1420 hosted by the hardware node 1430.

[0287] Each hardware device may also include a non-transitory, permanent machine-readable storage medium 1490-2 in which software 1495 and / or instructions executable by the processing circuitry 1460 are stored. The software 1495 may include any type of software, including software for instantiating one or more virtualization layers 1450 (also referred to as hypervisors), software for executing virtual machines 1440, and software that allows it to perform the functions, features, and / or benefits described with respect to some of the embodiments described herein.

[0288] The virtual machine 1440 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1450 or hypervisor. Different embodiments of instances of the virtual appliance 1420 may be implemented on one or more of the virtual machines 1440 and may be implemented in different ways.

[0289] During operation, processing circuitry 1460 executes software 1495 to instantiate a hypervisor or virtualization layer 1450, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 1450 may present a virtual operating platform to virtual machines 1440 that appears like networked hardware.

[0290] As shown in Figure 14 , the hardware 1430 may be a stand-alone network node with general or specific components. The hardware 1430 may include antennas 14225 and may implement some functions via virtualization. Alternatively, the hardware 1430 may be part of a larger hardware cluster (e.g., such as in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed via a management and orchestration (MANO) 14100 that, among other things, oversees the lifecycle management of applications 1420.

[0291] The virtualization of hardware is referred to as network function virtualization (NFV) in some contexts. NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage devices (which may be located in data centers and customer premise equipment).

[0292] In the context of NFV, virtual machines 1440 may be software implementations of physical machines that run programs as if they were executing on physical, non-virtual machines. Each of the virtual machines 1440 and that portion of the hardware 1430 that executes the virtual machine (whether it is hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 1440) form separate virtual network elements (VNEs).

[0293] Still in the context of NFV, virtual network functions (VNFs) are responsible for handling specific network functions running in one or more virtual machines 1440 on top of the hardware networking infrastructure 1430 and correspond to Figure 14 the applications 1420 in

[0294] In some embodiments, one or more radio units 14200 (each including one or more transmitters 14220 and one or more receivers 14210) may be coupled to one or more antennas 14225. The radio units 14200 may communicate directly with the hardware node 1430 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. Nodes arranged in this way may also communicate with one or more UEs (such as those described elsewhere herein).

[0295] In some embodiments, some signaling may be performed via control system 14230, which may alternatively be used for communication between hardware node 1430 and radio unit 14200.

[0296] Reference Figure 15 , according to an embodiment, a communication system includes a telecommunication network 1510, such as a 3GPP-type cellular network, which includes an access network 1511 (such as a radio access network) and a core network 1514. The access network 1511 includes a plurality of base stations 1512a, 1512b, 1512c, such as NB, eNB, gNB, or other types of wireless access points, each defining a corresponding coverage area 1513a, 1513b, 1513c. Each base station 1512a, 1512b, 1512c can be connected to the core network 1514 via a wired or wireless connection 1515. A first UE 1591 located in the coverage area 1513c can be configured to wirelessly connect to or be paged by the corresponding base station 1512c. A second UE 1592 in the coverage area 1513a can wirelessly connect to the corresponding base station 1512a. Although multiple UEs 1591, 1592 are shown in this example, the disclosed embodiments are equally applicable to cases where there is a single UE in the coverage area or where there is a single UE connected.

[0297] The telecommunication network 1510 is itself connected to a host computer 1530, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 1530 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 1521 and 1522 between the telecommunication network 1510 and the host computer 1530 may extend directly from the core network 1514 to the host computer 1530 or may be via an optional intermediate network 1520. The intermediate network 1520 may be one of a public, private, or managed network or a combination of more than one of a public, private, or managed network; the intermediate network 1520 (if any) may be a backbone network or the Internet; in particular, the intermediate network 1520 may include two or more subnets (not shown).

[0298] Figure 15The communication system as a whole enables connectivity between the connected UEs 1591, 1592 and the host computer 1530. The connectivity can be described as an over-the-top (OTT) connection 1550. The host computer 1530 and the connected UEs 1591, 1592 are configured to transfer data and / or signaling via the OTT connection 1550 using the access network 1511, the core network 1514, any intermediate network 1520, and possibly additional infrastructure (not shown) as intermediaries. The OTT connection 1550 can be transparent in the sense that the participating communication devices through which the OTT connection 1550 passes are not aware of the routing of the uplink and downlink communications. For example, the base station 1512 may not or need not be informed about the past routing of the incoming downlink communication having data originating from the host computer 1530 to be forwarded (e.g., handed over) to the connected UE 1591. Similarly, the base station 1512 need not know the future routing of the outgoing uplink communication originating from the UE 1591 towards the host computer 1530.

[0299] According to an embodiment, an example implementation of the UE, base station, and host computer discussed in the previous paragraphs will now be described with reference to Figure 16 In the communication system 1600, the host computer 1610 includes hardware 1615, which includes a communication interface 1616 configured to establish and maintain a wired or wireless connection to an interface of different communication devices of the communication system 1600. The host computer 1610 further includes a processing circuit 1618, which may have storage and / or processing capabilities. In particular, the processing circuit 1618 may include one or more programmable processors suitable for executing instructions, application-specific integrated circuits, field-programmable gate arrays, or a combination thereof (not shown). The host computer 1610 further includes software 1611, which is stored in or accessible by the host computer 1610 and executable by the processing circuit 1618. The software 1611 includes a host application 1612. The host application 1612 may be operable to provide services to a remote user, such as the UE 1630, which is connected via an OTT connection 1650 terminated at the UE 1630 and the host computer 1610. When providing services to the remote user, the host application 1612 may provide user data to be transferred using the OTT connection 1650.

[0300] The communication system 1600 may also include a base station 1620, which is provided in a telecommunication system and includes hardware 1625 that enables it to communicate with the host computer 1610 and the UE 1630. The hardware 1625 may include a communication interface 1626 for establishing and maintaining a wired or wireless connection for interfaces with different communication devices of the communication system 1600, and a radio interface 1627 for establishing and maintaining at least a wireless connection 1670 with the UE 1630 located in a coverage area (not shown in Figure 16 ) served by the base station 1620. The communication interface 1626 may be configured to facilitate the connection 1660 to the host computer 1610. The connection 1660 may be direct or it may go through the core network of the telecommunication system (not shown in Figure 16 ) and / or through one or more intermediate networks external to the telecommunication system. In the illustrated embodiment, the hardware 1625 of the base station 1620 may also include a processing circuit 1628, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions.

[0301] The base station 1620 also includes software 1621 stored internally or accessible via an external connection. For example, the software 1621 may include program instructions (also referred to as a computer program product), which when executed by the processing circuit 1628, may configure the base station 1620 to perform operations corresponding to the various exemplary methods (e.g., processes) described herein.

[0302] The communication system 1600 may also include the UE 1630 already mentioned, whose hardware 1635 may include a radio interface 1637 configured to establish and maintain a wireless connection 1670 with the base station serving the coverage area where the UE 1630 is currently located. The hardware 1635 of the UE 1630 may also include a processing circuit 1638, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) adapted to execute instructions.

[0303] The UE 1630 also includes software 1631 that is stored in or accessible by the UE 1630 and executable by the processing circuitry 1638. The software 1631 includes a client application 1632. The client application 1632 can be operable to provide services to a human or non-human user via the UE 1630 with the support of the host computer 1610. In the host computer 1610, the executed host application 1612 can communicate with the executed client application 1632 via the OTT connection 1650 terminated at the UE 1630 and the host computer 1610. When providing services to the user, the client application 1632 can receive request data from the host application 1612 and provide user data in response to the request data. The OTT connection 1650 can transmit both the request data and the user data. The client application 1632 can interact with the user to generate the user data it provides. The software 1631 can also include program instructions (also referred to as a computer program product) that, when executed by the processing circuitry 1638, can configure the UE 1630 to perform operations corresponding to the various exemplary methods (e.g., processes) described herein.

[0304] As an example, Figure 16 the host computer 1610, the base station 1620, and the UE 1630 shown in may be similar or identical to the host computer or base station described with respect to other figures herein. For example, the internal workings of these entities may be as shown in Figure 16 and, independently, the surrounding network topology may be the surrounding network topology shown in other figures herein.

[0305] In Figure 16 the OTT connection 1650 has been abstractly drawn to illustrate the communication between the host computer 1610 and the UE 1630 via the base station 1620 without explicitly mentioning any intermediate devices and the exact routing of messages via these devices. The network infrastructure can determine the routing, and it can be configured to hide the routing from the UE 1630 or from the service provider operating the host computer 1610 or from both. Although the OTT connection 1650 is active, the network infrastructure can further make a decision by which it dynamically changes the routing (e.g., on the basis of load balancing considerations or network reconfiguration).

[0306] The wireless connection 1670 between the UE 1630 and the base station 1620 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 1630 using the OTT connection 1650, in which the wireless connection 1670 forms the final segment. More precisely, the exemplary embodiments disclosed herein may improve the flexibility of end-to-end quality of service (QoS) (including their corresponding radio bearers) of data flows associated with data sessions between a network monitoring and a user equipment (UE) and another entity, such as an OTT data application or a service external to the 5G network. These and other advantages may facilitate more timely design, implementation, and deployment of 5G / NR solutions. Additionally, such embodiments may facilitate flexible and timely control of data session QoS, which may result in improvements in terms of capacity, throughput, latency, etc., as foreseen by 5G / NR and important for the growth of OTT services.

[0307] A measurement process may be provided for the purpose of monitoring data rate, latency, and other aspects of network operation improved by one or more embodiments. There may further be optional network functionality for reconfiguring the OTT connection 1650 between the host computer 1610 and the UE 1630 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 1650 may be implemented in the software 1611 and hardware 1615 of the host computer 1610 or in the software 1631 and hardware 1635 of the UE 1630 or both. In an embodiment, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 1650 passes; the sensors may participate in the measurement process by supplying values of the monitored quantities exemplified above or other physical quantities from which the software 1611, 1631 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1650 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect the base station 1620, and it may be unknown or imperceptible to the base station 1620. Such processes and functionality may be known and practiced in the art. In certain embodiments, the measurement may involve dedicated UE signaling that facilitates the measurement of throughput, propagation time, latency, etc. of the host computer 1610. The measurement may be implemented because the software 1611 and 1631 cause messages, particularly empty or "dummy" messages, to be transmitted using the OTT connection 1650 while they monitor propagation time, error, etc.

[0308] Figure 17is a flowchart showing an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 17 will be included in this section. In step 1710, the host computer provides user data. In sub-step 1711 (which may be optional) of step 1710, the host computer provides user data by executing a host application. In step 1720, the host computer initiates a transmission carrying the user data to the UE. In step 1730 (which may be optional), according to the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 1740 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0309] Figure 18 is a flowchart showing an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 18 will be included in this section. In step 1810 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1820, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be relayed via the base station. In step 1830 (which may be optional), the UE receives the user data carried in the transmission.

[0310] Figure 19 is a flowchart showing an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 19Reference to the accompanying drawings. In step 1910 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1920, the UE provides user data. In sub-step 1921 of step 1920 (which may be optional), the UE provides user data by executing a client application. In sub-step 1911 of step 1910 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates, in sub-step 1930 (which may be optional), the transmission of the user data to the host computer. In step 1940 of the method, the host computer receives the user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0311] Figure 20 is a flowchart showing an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify this disclosure, only references to Figure 20 the accompanying drawings will be included in this section. In step 2010 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 2020 (which may be optional), the base station initiates the transmission of the received data to the host computer. In step 2030 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0312] As described herein, a device and / or equipment may be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not exclude the possibility that the functionality of the device or equipment is not implemented in hardware but as a software module, such as a computer program or a computer program product including an executable software code portion for execution or running on a processor. Additionally, the functionality of the device or equipment may be implemented by any combination of hardware and software. The device or equipment may also be regarded as a component of multiple devices and / or equipment, whether they cooperate with each other functionally or are independent of each other. Furthermore, as long as the functionality of the device or equipment is retained, the device and equipment may be implemented in a distributed manner throughout the system. Such and similar principles are considered to be known to those skilled in the art.

[0313] In addition, functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device and can in fact be distributed among several physical devices.

[0314] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will also be understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0315] In addition, certain terms used in this disclosure (including the specification, the drawings, and their exemplary embodiments) may be used synonymously in some cases, including but not limited to, for example, data and information. It should be understood that while these words and / or other words that may be synonymous with each other may be used synonymously herein, there may be cases where such words are not intended to be used synonymously. Furthermore, to the extent that prior art knowledge has not been explicitly incorporated herein by reference above, it is hereby incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entirety.

[0316] Unless expressly stated to the contrary, as used herein, the phrases “at least one of” and “one or more of” followed by a conjunctive list of items (e.g., “A and B,” “A, B, and C”) are intended to mean “at least one item, where each item is selected from the list consisting of” the following items, which are the listed items. For example, “at least one of A and B” is intended to mean any one of the following: A; B; A and B. Similarly, “one or more of A, B, and C” is intended to mean any one of the following: A; B; C; A and B; B and C; A and C; A, B, and C.

[0317] Unless expressly stated to the contrary, as used herein, the phrase “a plurality of” followed by a conjunctive list of items (e.g., “A and B,” “A, B, and C”) is intended to mean “a plurality of items, where each item is selected from the list consisting of” the following items, which are the listed items. For example, “a plurality of A and B” is intended to mean any one of the following: more than one A; more than one B; or at least one A and at least one B.

[0318] The foregoing merely illustrates the principles of the present disclosure. In view of the teachings herein, various modifications and variations to the described embodiments will be apparent to those skilled in the art. Accordingly, it will be understood that those skilled in the art will be able to design many systems, arrangements, and processes that, although not explicitly shown or described herein, embody the principles of the present disclosure and are thus within the spirit and scope of the present disclosure. As those of ordinary skill in the art should understand, the various exemplary embodiments can be used together with each other, or can be used interchangeably with each other.

[0319] Exemplary embodiments of the present disclosure include, but are not limited to, the examples listed below, which are divided into groups of related embodiments.

[0320] Group A Embodiments

[0321] A1. A method performed by a wireless device, the method comprising:

[0322] Receiving control signaling from a network node indicating a parameter configuration for performing a transmission of a particular subset of one or more error control procedures according to the parameter configuration.

[0323] The method according to embodiment A1, wherein the one or more error control procedures in the particular subset include one or more error control procedures identified by one or more corresponding error control procedure identifiers, and wherein the control signaling indicates the one or more corresponding error control procedure identifiers.

[0324] The method according to embodiment A1, wherein the one or more error control procedures in the particular subset include any error control procedure of a particular type.

[0325] The method according to any one of embodiments A1 - A3, wherein the one or more error control procedures in the particular subset include any error control procedure that disables error control feedback, or any error control procedure that enables error control feedback.

[0326] The method according to any one of embodiments A1 - A4, wherein the parameter configuration includes a configuration of one or more power control parameters.

[0327] The method according to embodiment A5, wherein the one or more power control parameters include one or more of the following:

[0328] Nominal target received power;

[0329] Path loss compensation factor;

[0330] Incremental modulation and coding scheme;

[0331] Transmission power control accumulation;

[0332] A plurality of power control adjustment states maintained by the wireless device; or

[0333] A parameter that maps a transmission power control command field in downlink control information to an absolute or cumulative closed-loop power control value.

[0334] A7. The method according to any one of embodiments A1 - A6, wherein the parameter configuration includes a configuration of an actual transmission power level.

[0335] A8. The method according to embodiment A7, wherein the control signaling indicates the configuration of the actual transmission power level by indicating whether to perform transmission of the specific subset of one or more error control processes at the maximum transmission power.

[0336] A9. The method according to embodiment A7, wherein the control signaling indicates the configuration of the actual transmission power level by indicating which one of a plurality of possible actual transmission power levels to perform transmission of the specific subset of one or more error control processes.

[0337] A10. The method according to any one of embodiments A1 - A9, wherein the parameter configuration includes a configuration of one or more of the following:

[0338] Aggregation factor, which indicates the number of consecutive downlink time slots scheduled by downlink control information;

[0339] Transmission waveform type;

[0340] Modulation and coding scheme table;

[0341] Time domain resource allocation table;

[0342] Type of frequency resource allocation;

[0343] Block error rate target;

[0344] Physical resource block bundling configuration;

[0345] Type of physical downlink shared channel mapping; or

[0346] Physical uplink shared channel transmission scheme.

[0347] A11. The method according to any one of embodiments A1 - A10, wherein the one or more error control processes are controlled by a media access control (MAC) layer.

[0348] A12. The method according to any one of embodiments A1 - A11, wherein the one or more error control processes are one or more Hybrid Automatic Repeat reQuest (HARQ) processes.

[0349] A13. The method according to any one of embodiments A1 - A12, further comprising transmitting or receiving transmissions of the specific subset of the one or more error control processes according to the indicated parameter configuration.

[0350] A14. The method according to any one of embodiments A1 - A13, wherein the transmissions of the specific subset of the one or more error control processes will be performed via a non - terrestrial network.

[0351] A16. A method performed by a wireless device, the method comprising:

[0352] Transmitting or receiving transmissions of different subsets of one or more error control processes according to different parameter configurations.

[0353] A17. The method according to embodiment A16, wherein the different subsets include a subset of one or more error control processes with error control feedback disabled and a subset of one or more error control processes with error control feedback enabled.

[0354] A18. The method according to any one of embodiments A16 - A17, wherein the different parameter configurations include different configurations of one or more power control parameters.

[0355] A19. The method according to embodiment A18, wherein the one or more power control parameters include one or more of the following:

[0356] Nominal target received power;

[0357] Path loss compensation factor;

[0358] Incremental modulation and coding scheme;

[0359] Transmit power control accumulation;

[0360] A plurality of power control adjustment states maintained by the wireless device; or

[0361] A parameter for mapping a transmit power control command field in downlink control information to an absolute or cumulative closed - loop power control value.

[0362] A20. The method according to any one of embodiments A16 - A19, wherein the different parameter configurations include different configurations of actual transmit power levels.

[0363] A21. The method according to any one of embodiments A16 - A20, wherein the different parameter configurations include different configurations of one or more of the following:

[0364] Aggregation factor, which indicates the number of consecutive downlink time slots scheduled by downlink control information;

[0365] Transmission waveform type;

[0366] Modulation and coding scheme table;

[0367] Time domain resource allocation table;

[0368] Type of frequency resource allocation;

[0369] Block error rate target;

[0370] Physical resource block bundling configuration;

[0371] Type of physical downlink shared channel mapping; or

[0372] Physical uplink shared channel transmission scheme.

[0373] A22. The method according to any one of embodiments A16 - A21, wherein the one or more error control processes in each of the different subsets are controlled by a Medium Access Control (MAC) layer.

[0374] A23. The method according to any one of embodiments A16 - A22, wherein the one or more error control processes in each of the different subsets are one or more Hybrid Automatic Repeat reQuest (HARQ) processes.

[0375] A24. The method according to any one of embodiments A16 - A13, wherein the transmission is sent or received via a non - terrestrial network.

[0376] A25. A method performed by a wireless device, the method comprising:

[0377] Transmitting error control feedback for a set of downlink transmissions to a network node according to an error control feedback codebook, wherein for any downlink transmission of an error control process for which error control feedback is disabled, the error control feedback codebook encodes the feedback for the downlink transmission as a negative acknowledgement feedback.

[0378] A26. The method according to embodiment A25, wherein the downlink transmission is received by the wireless device via a non - terrestrial network.

[0379] A27. The method according to any one of embodiments A25 - A26, wherein the error control feedback is hybrid automatic repeat request (HARQ) feedback, and the error control process is an HARQ process.

[0380] A27A. The method according to any one of embodiments A25 - A27, further comprising generating the error control feedback according to the error control feedback codebook.

[0381] A28. A method performed by a wireless device, the method comprising:

[0382] Receiving a downlink control information message that schedules a downlink transmission for a specific error control process and includes a set of one or more fields, the interpretation of the set of one or more fields depending on whether error control feedback is enabled or disabled for the specific error control process.

[0383] A29. The method according to embodiment A28, wherein the one or more fields in the set include one or more of the following:

[0384] A downlink assignment indicator field;

[0385] A redundancy version field;

[0386] A feedback timing field; or

[0387] A physical uplink control channel resource indicator field.

[0388] A30. The method according to any one of embodiments A28 - A29, wherein when the error control feedback is disabled, the set of one or more fields indicates an aggregation factor that indicates a plurality of consecutive downlink time slots associated with the scheduled downlink transmission.

[0389] A31. The method according to any one of embodiments A28 - A29, wherein when the error control feedback is disabled, the set of one or more fields, in combination with an error control process number field in the downlink control information message, indicates an error control process number that identifies the specific error control process.

[0390] A32. The method according to any one of embodiments A28 - A31, further comprising interpreting the set of one or more fields depending on whether error control feedback is enabled or disabled for the specific error control process.

[0391] A33. The method according to any one of embodiments A28 - A32, further comprising receiving the downlink transmission according to the received downlink control information message.

[0392] A34. According to the method of any one of embodiments A28 - A33, wherein the downlink transmission is received by the wireless device via a non - terrestrial network.

[0393] A35. According to the method of any one of embodiments A28 - A34, wherein the error control feedback is hybrid automatic repeat request (HARQ) feedback, and the error control process is a HARQ process.

[0394] A36. A method performed by a wireless device, the method comprising:

[0395] Receiving control signaling from a network node, the control signaling indicating a parameter configuration according to which a transmission of a specific error control process or a specific type of error control process is to be performed.

[0396] A37. A method performed by a wireless device, the method comprising:

[0397] Receiving control signaling from a network node, the control signaling indicating a parameter configuration according to which a transmission is to be performed for any error control process for which error control feedback is disabled.

[0398] A38. A method performed by a wireless device, the method comprising:

[0399] Receiving control signaling from a network node, the control signaling indicating a parameter configuration according to which a transmission is to be performed for any error control process for which error control feedback is enabled.

[0400] A39. The method of any one of embodiments A1 - A38, further comprising:

[0401] Providing user data; and

[0402] Forwarding the user data to a host computer via the transmission to the base station.

[0403] Group B embodiments

[0404] B1. A method performed by a network node, the method comprising:

[0405] Transmitting control signaling indicating a parameter configuration from the network node to a wireless device, according to which a transmission of a specific subset of one or more error control processes is to be performed.

[0406] B2. The method according to embodiment B1, wherein the one or more error control processes in the specific subset include one or more error control processes identified by one or more corresponding error control process identifiers, and the control signaling indicates the one or more corresponding error control process identifiers.

[0407] B3. The method according to embodiment B1, wherein the one or more error control processes in the specific subset include any error control process of a specific type.

[0408] B4. The method according to any one of embodiments B1 and B3, wherein the one or more error control processes in the specific subset include any error control process that disables error control feedback or any error control process that enables error control feedback.

[0409] B5. The method according to any one of embodiments B1 - B4, wherein the parameter configuration includes the configuration of one or more power control parameters.

[0410] B6. The method according to embodiment B5, wherein the one or more power control parameters include one or more of the following:

[0411] Nominal target received power;

[0412] Path loss compensation factor;

[0413] Incremental modulation and coding scheme;

[0414] Transmit power control accumulation;

[0415] A plurality of power control adjustment states maintained by the wireless device; or

[0416] A parameter that maps the transmit power control command field in the downlink control information to an absolute or cumulative closed-loop power control value.

[0417] B7. The method according to any one of embodiments B1 - B6, wherein the parameter configuration includes the configuration of the actual transmit power level.

[0418] B8. The method according to embodiment B7, wherein the control signaling indicates the configuration of the actual transmit power level by indicating whether to perform the transmission of the specific subset of the one or more error control processes at the maximum transmit power.

[0419] B9. The method according to embodiment B7, wherein the control signaling indicates the configuration of the actual transmit power level by indicating which actual transmit power level among a plurality of possible actual transmit power levels to perform the transmission of the specific subset of the one or more error control processes.

[0420] B10. The method according to any one of embodiments B1 - B9, wherein the parameter configuration includes the configuration of one or more of the following:

[0421] Aggregation factor, which indicates the number of consecutive downlink time slots scheduled by downlink control information;

[0422] Type of transmission waveform;

[0423] Modulation and coding scheme table;

[0424] Time domain resource allocation table;

[0425] Type of frequency resource allocation;

[0426] Block error rate target;

[0427] Physical resource block bundling configuration;

[0428] Type of physical downlink shared channel mapping; or

[0429] Physical uplink shared channel transmission scheme.

[0430] B11. The method according to any one of embodiments B1 - B10, wherein the one or more error control processes are controlled by a Medium Access Control (MAC) layer.

[0431] B12. The method according to any one of embodiments B1 - B11, wherein the one or more error control processes are one or more Hybrid Automatic Repeat reQuest (HARQ) processes.

[0432] B13. The method according to any one of embodiments B1 - B12, further comprising transmitting or receiving a transmission of the specific subset of the one or more error control processes according to the indicated parameter configuration.

[0433] B14. The method according to any one of embodiments B1 - B13, wherein the transmission of the specific subset of the one or more error control processes will be performed via a non - terrestrial network.

[0434] B16. A method performed by a network node, the method comprising:

[0435] Transmitting or receiving a transmission of different subsets of one or more error control processes according to different parameter configurations.

[0436] B17. The method according to embodiment B16, wherein the different subsets include a subset of one or more error control processes with disabled error control feedback and a subset of one or more error control processes with enabled error control feedback.

[0437] B18. The method according to any one of embodiments B16 - B17, wherein the different parameter configurations include different configurations of one or more power control parameters.

[0438] B19. The method according to embodiment B18, wherein the one or more power control parameters include one or more of the following:

[0439] Nominal target received power;

[0440] Path loss compensation factor;

[0441] Incremental modulation and coding scheme;

[0442] Transmit power control accumulation;

[0443] A plurality of power control adjustment states maintained by the wireless device; or

[0444] A parameter that maps the transmit power control command field in the downlink control information to an absolute or cumulative closed - loop power control value.

[0445] B20. The method according to any one of embodiments B16 - B19, wherein the different parameter configurations include different configurations of actual transmit power levels.

[0446] B21. The method according to any one of embodiments B16 - B20, wherein the different parameter configurations include different configurations of one or more of the following:

[0447] Aggregation factor, which indicates the number of consecutive downlink time slots scheduled by the downlink control information;

[0448] Transmission waveform type;

[0449] Modulation and coding scheme table;

[0450] Time - domain resource allocation table;

[0451] Type of frequency resource allocation;

[0452] Block error rate target;

[0453] Physical resource block bundling configuration;

[0454] Type of physical downlink shared channel mapping; or

[0455] Physical uplink shared channel transmission scheme.

[0456] B22. The method according to any one of embodiments B16 - B21, wherein the one or more error control processes in each of the different subsets are controlled by a Medium Access Control (MAC) layer.

[0457] B23. The method according to any one of embodiments B16 - B22, wherein the one or more error control processes in each of the different subsets are one or more Hybrid Automatic Repeat reQuest (HARQ) processes.

[0458] B24. The method according to any one of embodiments B16 - B13, wherein the transmission is transmitted or received via a non - terrestrial network.

[0459] B25. A method performed by a network node, the method comprising:

[0460] Receiving error control feedback for a set of downlink transmissions from a wireless device according to an error control feedback codebook, wherein for any downlink transmission of an error control process for which error control feedback is disabled, the error control feedback codebook encodes the feedback for the downlink transmission as a negative acknowledgement feedback.

[0461] B26. The method according to embodiment B25, wherein the downlink transmission is transmitted by the network node via a non - terrestrial network.

[0462] B27. The method according to any one of embodiments B25 - B26, wherein the error control feedback is Hybrid Automatic Repeat reQuest (HARQ) feedback and the error control process is a HARQ process.

[0463] B27A. The method according to any one of embodiments B25 - B27, further comprising processing the received error control feedback according to the error control feedback codebook.

[0464] B28. A method performed by a network node, the method comprising:

[0465] Transmitting a downlink control information message to a wireless device, the downlink control information message scheduling a downlink transmission for a specific error control process and including a set of one or more fields, the interpretation of the set of one or more fields depending on whether error control feedback is enabled or disabled for the specific error control process.

[0466] B29. The method according to embodiment B28, wherein the one or more fields in the set include one or more of the following:

[0467] A downlink assignment indicator field;

[0468] A redundancy version field;

[0469] A feedback timing field; or

[0470] A physical uplink control channel resource indicator field.

[0471] B30. The method according to any one of embodiments B28 - B29, wherein when the error control feedback is disabled, the set of one or more fields indicates an aggregation factor, the aggregation factor indicating a plurality of consecutive downlink time slots associated with the scheduled downlink transmission.

[0472] B31. The method according to any one of embodiments B28 - B29, wherein when the error control feedback is disabled, the set of one or more fields together with an error control process number field in the downlink control information message indicates an error control process number identifying the specific error control process.

[0473] B32. The method according to any one of embodiments B28 - B31, further comprising encoding the set of one or more fields depending on whether error control feedback is enabled or disabled for the specific error control process.

[0474] B33. The method according to any one of embodiments B28 - B32, further comprising transmitting the downlink transmission according to the transmitted downlink control information message.

[0475] B34. The method according to any one of embodiments B28 - B33, wherein the downlink transmission is transmitted via a non - terrestrial network.

[0476] B35. The method according to any one of embodiments B28 - B34, wherein the error control feedback is hybrid automatic repeat request (HARQ) feedback and the error control process is a HARQ process.

[0477] B36. The method according to any one of embodiments B1 - B35, further comprising:

[0478] Obtaining user data; and

[0479] Forwarding the user data to a host computer or a wireless device.

[0480] Group C embodiments

[0481] C1. A wireless device configured to perform any one of the steps according to any one of the Group A embodiments.

[0482] C2. A wireless device comprising a processing circuit that performs any one of the steps according to any one of the Group A embodiments.

[0483] C3. A wireless device, comprising:

[0484] a communication circuit; and

[0485] a processing circuit configured to perform any one of the steps described in any one of the Group A embodiments.

[0486] C4. A wireless device, comprising:

[0487] a processing circuit configured to perform any one of the steps described in any one of the Group A embodiments; and

[0488] a power supply circuit configured to supply power to the wireless device.

[0489] C5. A wireless device, comprising:

[0490] a processing circuit and a memory, the memory containing instructions executable by the processing circuit, whereby the wireless device is configured to perform any one of the steps described in any one of the Group A embodiments.

[0491] C6. A user equipment (UE), comprising:

[0492] an antenna configured to transmit and receive wireless signals;

[0493] a radio front-end circuit connected to the antenna and the processing circuit and configured to condition signals transmitted between the antenna and the processing circuit;

[0494] the processing circuit configured to perform any one of the steps described in any one of the Group A embodiments;

[0495] an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit;

[0496] an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and

[0497] a battery connected to the processing circuit and configured to supply power to the UE.

[0498] C7. A computer program comprising instructions that, when executed by at least one processor of a wireless device, cause the wireless device to perform any one of the steps described in any one of the Group A embodiments.

[0499] C8. A carrier comprising the computer program according to embodiment C7, wherein the carrier is one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0500] C9. A radio network node configured to perform any one of the steps described in any one of Group B embodiments.

[0501] C10. A radio network node comprising a processing circuit, the processing circuit performing any one of the steps described in any one of Group B embodiments.

[0502] C11. A radio network node, comprising:

[0503] A communication circuit; and

[0504] A processing circuit configured to perform any one of the steps described in any one of Group B embodiments.

[0505] C12. A radio network node, comprising:

[0506] A processing circuit configured to perform any one of the steps described in any one of Group B embodiments; and

[0507] A power supply circuit configured to supply power to the radio network node.

[0508] C13. A radio network node, comprising:

[0509] A processing circuit and a memory, the memory containing instructions executable by the processing circuit, whereby the radio network node is configured to perform any one of the steps described in any one of Group B embodiments.

[0510] C14. The radio network node according to any one of embodiments C9 - C13, wherein the radio network node is a base station.

[0511] C15. A computer program comprising instructions which, when executed by at least one processor of a radio network node, cause the radio network node to perform any one of the steps described in any one of Group B embodiments.

[0512] C16. The computer program according to embodiment C14, wherein the radio network node is a base station.

[0513] C17. A carrier comprising the computer program according to any one of embodiments C15 - C16, wherein the carrier is one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium.

[0514] Group D Embodiments

[0515] D1. A communication system including a host computer, comprising:

[0516] Processing circuitry configured to provide user data; and

[0517] A communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0518] wherein the cellular network includes a base station having a radio interface and processing circuitry, and the processing circuitry of the base station is configured to perform any one of the steps of any one of the Group B embodiments.

[0519] D2. The communication system according to the previous embodiment further includes the base station.

[0520] D3. The communication system according to the previous two embodiments further includes the UE, wherein the UE is configured to communicate with the base station.

[0521] D4. The communication system according to the previous three embodiments, wherein:

[0522] The processing circuitry of the host computer is configured to execute a host application to provide the user data; and

[0523] The UE includes processing circuitry configured to execute a client application associated with the host application.

[0524] D5. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0525] Providing user data at the host computer; and

[0526] Initiating, at the host computer, a transmission to the UE via a cellular network including the base station, carrying the user data, wherein the base station performs any one of the steps of any one of the Group B embodiments.

[0527] D6. The method according to the previous embodiment further includes transmitting the user data at the base station.

[0528] D7. The method according to the previous two embodiments, wherein the user data is provided at the host computer by executing a host application, and the method further includes executing a client application associated with the host application at the UE.

[0529] D8. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and a processing circuit configured to perform any one of the first three embodiments.

[0530] D9. A communication system comprising a host computer, comprising:

[0531] A processing circuit configured to provide user data; and

[0532] A communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),

[0533] wherein the UE comprises a radio interface and a processing circuit, and components of the UE are configured to perform any one of the steps of any one of the Group A embodiments.

[0534] D10. The communication system according to the previous embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.

[0535] D11. The communication system according to the previous two embodiments, wherein:

[0536] The processing circuit of the host computer is configured to execute a host application to provide the user data; and

[0537] The processing circuit of the UE is configured to execute a client application associated with the host application.

[0538] D12. A method implemented in a communication system comprising a host computer, a base station, and a user equipment (UE), the method comprising:

[0539] At the host computer, providing user data; and

[0540] At the host computer, initiating a transmission to the UE via a cellular network comprising the base station, carrying the user data, wherein the UE performs any one of the steps of any one of the Group A embodiments.

[0541] D13. The method according to the previous embodiment, further comprising receiving the user data at the UE from the base station.

[0542] D14. A communication system comprising a host computer, comprising:

[0543] A communication interface configured to receive user data sourced from a transmission from a user equipment (UE) to a base station,

[0544] Wherein, the UE includes a radio interface and a processing circuit, and the processing circuit of the UE is configured to execute any one of the steps in any one of the Group A embodiments.

[0545] D15. The communication system according to the previous embodiment further includes the UE.

[0546] D16. The communication system according to the previous two embodiments further includes the base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward the user data carried by the transmission from the UE to the base station to the host computer.

[0547] D17. In the communication system according to the previous three embodiments:

[0548] The processing circuit of the host computer is configured to execute a host application; and

[0549] The processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing the user data.

[0550] D18. In the communication system according to the previous four embodiments:

[0551] The processing circuit of the host computer is configured to execute a host application, thereby providing request data; and

[0552] The processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0553] D19. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising:

[0554] At the host computer, receiving user data transmitted from the UE to the base station, wherein the UE executes any one of the steps in any one of the Group A embodiments.

[0555] D20. The method according to the previous embodiment further includes providing the user data from the UE to the base station.

[0556] D21. The method according to the previous two embodiments further includes:

[0557] At the UE, executing a client application to provide the user data to be transmitted; and

[0558] At the host computer, executing a host application associated with the client application.

[0559] The method according to the previous three embodiments further includes:

[0560] at the UE, executing a client application; and

[0561] at the UE, receiving input data for the client application, the input data being provided at the host computer by executing a host application associated with the client application,

[0562] wherein the user data to be transmitted is provided by the client application in response to the input data.

[0563] D23. A communication system includes a host computer, the host computer includes a communication interface, the communication interface is configured to receive user data sourced from a transmission from a user equipment (UE) to a base station, wherein the base station includes a radio interface and a processing circuit, and the processing circuit of the base station is configured to execute any one of the steps in any one of Group B embodiments.

[0564] D24. The communication system according to the previous embodiment further includes the base station.

[0565] D25. The communication system according to the previous two embodiments further includes the UE, wherein the UE is configured to communicate with the base station.

[0566] D26. The communication system according to the previous three embodiments, wherein:

[0567] the processing circuit of the host computer is configured to execute a host application;

[0568] the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

[0569] D27. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method includes:

[0570] at the host computer, receiving user data sourced from a transmission that the base station has received from the UE, wherein the UE executes any one of the steps in any one of Group A embodiments.

[0571] D28. The method according to the previous embodiment further includes receiving the user data at the base station from the UE.

[0572] D29. The method according to the previous two embodiments further includes, at the base station, initiating transmission of the received user data to the host computer.

Claims

1. A method for a wireless device, the method comprises: transmitting (250) to a network node in a wireless network hybrid automatic repeat request (HARQ) feedback for a set of downlink (DL) transmissions to be performed by the network node, wherein the HARQ feedback is based on a HARQ feedback codebook, the HARQ feedback codebook comprising: a first entry corresponding to a first HARQ process for which HARQ feedback is disabled, the first entry indicating that the HARQ feedback for the DL transmission associated with the first HARQ process is encoded as a negative acknowledgment; and a second entry corresponding to a second HARQ process for which HARQ feedback is enabled, the second entry indicating that the HARQ feedback for the DL transmission associated with the second HARQ process is encoded based on the decoding result of the DL transmission associated with the second HARQ process.

2. The method according to claim 1, wherein, the HARQ feedback codebook is a type 1 HARQ-ACK codebook.

3. The method according to any one of claims 1-2, further comprises: receiving (235) from the network node a set of downlink control information (DCI) via a physical downlink control channel (PDCCH), the set of downlink control information (DCI) indicating corresponding scheduling for the set of DL transmissions; and receiving (240) the set of DL transmissions from the network node via a physical downlink shared channel (PDSCH) according to the corresponding scheduling.

4. The method according to claim 3, wherein: the position of the first entry in the HARQ feedback codebook is based on a slot timing offset included in the DCI that schedules the DL transmission associated with the first HARQ process; and the position of the second entry in the HARQ feedback codebook is based on a slot timing offset included in the DCI that schedules the DL transmission associated with the second HARQ process.

5. A method for a network node in a wireless network, the method comprises: receiving (350) from a wireless device hybrid automatic repeat request (HARQ) feedback for a set of downlink (DL) transmissions to be performed by the network node, wherein the HARQ feedback is based on a HARQ feedback codebook, the HARQ feedback codebook comprising: a first entry corresponding to a first HARQ process for which HARQ feedback is disabled, the first entry indicating that the HARQ feedback for the DL transmission associated with the first HARQ process is encoded as a negative acknowledgment; and a second entry corresponding to a second HARQ process for which HARQ feedback is enabled, the second entry indicating that the HARQ feedback for the DL transmission associated with the second HARQ process is encoded based on the decoding result of the DL transmission associated with the second HARQ process.

6. The method according to claim 5, wherein, the HARQ feedback codebook is a type 1 HARQ-ACK codebook.

7. The method according to any one of claims 5-6, further comprises: Transmitting (335) a set of downlink control information (DCI) to the wireless device via a physical downlink control channel (PDCCH), the set of downlink control information (DCI) indicating corresponding scheduling for the set of DL transmissions; and Transmitting (340) the set of DL transmissions to the wireless device via a physical downlink shared channel (PDSCH) according to the corresponding scheduling.

8. The method according to claim 7, wherein: The position of the first entry in the HARQ feedback codebook is based on a slot timing offset included in the DCI that schedules the DL transmission associated with the first HARQ process; and The position of the second entry in the HARQ feedback codebook is based on a slot timing offset included in the DCI that schedules the DL transmission associated with the second HARQ process.

9. A wireless device (18, 400, 1210, 1300, 1630), comprising: Communication circuitry (420, 1214, 1311, 1331, 1637) configured to communicate with a network node (12, 500, 1260, 1430, 1620) in a wireless network (10); and Processing circuitry (410, 1220, 1301, 1638) operably coupled to the communication circuitry, whereby the processing circuitry and the communication circuitry are configured to perform the method according to any one of claims 1-4.

10. A wireless device (18, 400, 1210, 1300, 1630), comprising: A processor; and A memory storing instructions that, when executed by the processor, cause the wireless device to be arranged to communicate with a network node (12, 500, 1260, 1430, 1620) in a wireless network (10) via HARQ feedback and data transmissions associated with a plurality of hybrid automatic repeat request (HARQ) processes, and cause the wireless device to further be arranged to perform the method according to any one of claims 1-4.

11. A non-transitory computer-readable medium (430, 1230, 1315) storing computer-executable instructions (1325, 1631) that, when executed by the processing circuitry (410, 1220, 1301, 1638) of a wireless device (18, 400, 1210, 1300, 1630), configure the wireless device to perform the method according to any one of claims 1-4.

12. A computer program product comprising computer-executable instructions (1325, 1631) which, when executed by a processing circuit (410, 1220, 1301, 1638) of a wireless device (18, 400, 1210, 1300, 1630), configure the wireless device to perform the method according to any one of claims 1-4.

13. A network node (12, 500, 1260, 1430, 1620) in a wireless network (10), comprising: communication circuitry (520, 1290, 1470, 14200, 1627) configured to communicate with one or more wireless devices; and processing circuitry (510, 1270, 1460, 1628) operably coupled to the communication circuitry, whereby the processing circuitry and the communication circuitry are configured to perform the method according to any one of claims 5-8.

14. A network node (12, 500, 1260, 1430, 1620) in a wireless network (10), comprising: a processor; and a memory storing instructions which, when executed by the processor, cause the network node to be arranged to communicate with one or more wireless devices via HARQ feedback and data transmission associated with a plurality of HARQ processes, and cause the network node to be further arranged to perform the method according to any one of claims 5-8.

15. A non-transitory computer-readable medium (530, 1280, 1490) storing computer-executable instructions (1495, 1625) which, when executed by a processing circuit (510, 1270, 1460, 1628) of a network node (12, 500, 1260, 1430, 1620) in a wireless network (10), configure the network node to perform the method according to any one of claims 5-8.

16. A computer program product comprising computer-executable instructions (1495, 1625) which, when executed by a processing circuit (510, 1270, 1460, 1628) of a network node (12, 500, 1260, 1430, 1620) in a wireless network (10), configure the network node to perform the method according to any one of claims 5-8.

Images