Method for operating hybrid automatic repeat request without per hybrid automatic repeat request process

Abstract

A method by a wireless device includes receiving configuration information from a network node, the configuration information enabling hybrid automatic repeat request acknowledgement (HARQ ACK) and / or negative acknowledgement (HARQ NACK) feedback for a first set of HARQ processes and disabling HARQ ACK and / or HARQ NACK for a second set of HARQ processes. The wireless device constructs a first HARQ codebook of a first type based on a first set of HARQ process numbers of the first set of HARQ processes for which HARQ ACK and / or HARQ NACK feedback is enabled and sends HARQ ACK and / or HARQ NACK feedback based on the first HARQ codebook to the network node.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more particularly to systems and methods for operating HARQ with the Hybrid Automatic Repeat Request (HARQ) process disabled. Background Technology

[0002] In 3GPP Release 15, the first version of the 5G System (5GS) was developed. This is a next-generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine-type communications (mMTC). 5G includes a New Radio (NR) access layer interface and a 5G core network (5GC). The NR physical layer and higher layers are reusing parts of the Long Term Evolution (LTE) specification and adding necessary components as inspired by new use cases.

[0003] In Release 15, 3GPP began work on preparing NR for operation in non-terrestrial networks (NTNs). This work was carried out within the research project "NR to support Non-Terrestrial Networks" and resulted in 3GPP TR38.811. In Release 16, the work on preparing NR for operation in NTN networks continued with the research project "Solutions for NR to support Non-Terrestrial Networks." See RP-181370 for a study on the evaluation of solutions for NR to support non-terrestrial networks.

[0004] Satellite radio access networks typically include the following components:

[0005] ● Refers to satellites on space-based platforms.

[0006] ●A ground gateway that connects satellites to base stations or the core network, depending on the architecture chosen.

[0007] ● This refers to the feeder link between the gateway and the satellite.

[0008] ● Refers to the service link between the satellite and the UE.

[0009] Two popular architectures are the bend-pin transponder and the regenerative transponder architecture. In the first case, the base station is located on the ground behind the gateway, and the satellite operates as a repeater that forwards feeder link signals to the serving link and vice versa. In the second case, the satellite carries the base station, and the serving link connects it to the terrestrial core network.

[0010] Depending on their orbital altitude, satellites can be classified as low Earth orbit (LEO), medium Earth orbit (MEO), or geostationary orbit (GEO) satellites.

[0011] ●LEO: Typical altitudes range from 250 to 1,500 km, with orbital periods ranging from 90 to 120 minutes.

[0012] ●MEO: Typical altitudes range from 5,000 to 25,000 km, with orbital periods ranging from 3 to 15 hours.

[0013] ●GEO: At an altitude of approximately 35,786 km, with an orbital period of 24 hours.

[0014] Communication satellites typically generate several beams over a given area. The coverage area (footprint) of a beam is usually elliptical, which has traditionally been considered a small area. The coverage area of ​​a beam is also often referred to as a spot beam. A spot beam can move across the Earth's surface as the satellite moves, or it can be fixed to the Earth's surface to compensate for its motion using some beam pointing mechanism used by the satellite. The size of a spot beam depends on the system design and can range from tens of kilometers to thousands of kilometers.

[0015] Hybrid Automatic Repeat Request (HARQ) is one of the most important features of NR. Together with link adaptation via Channel State Information (CSI) feedback and HARQ Acknowledgment (HARQ ACK) / HARQ Negative Acknowledgment (HARQ NACK), HARQ enables efficient, reliable, and low-latency data transmission in NR.

[0016] Existing HARQ procedures at the Physical Layer (PHY) and Media Access Control (MAC) layers have been designed for terrestrial networks, where the backhaul time (RTT) propagation delay is typically limited to within 1 ms. Using HARQ protocols, the transmitter needs to wait for feedback from the receiver before sending new data. In the case of a HARQ NACK, the transmitter may need to retransmit the data packet. Otherwise, it can send new data. This stop-and-wait (SAW) process introduces inherent latency into the communication protocol, which can reduce link throughput. To mitigate this problem, existing HARQ procedures allow multiple HARQ procedures to be activated at the transmitter. That is, the transmitter can initiate multiple transmissions in parallel without waiting for HARQ completion. For example, using 16 HARQ procedures in the NR downlink (DL), a gNodeB (gNB) can initiate up to 16 new data transmissions without waiting for a HARQ ACK for the first packet transmission. Note that for terrestrial networks, there is a sufficient number of HARQ procedures where the propagation delay is typically less than 1 ms.

[0017] Figure 1 The HARQ protocol is described. As explained, various delays associated with the HARQ process can include: 1. Packets arriving at the receiver after a propagation delay Tp.

[0018] 2. The receiver sends feedback after processing / time slot delay T1.

[0019] 3. Feedback arrives at the data transmitter after the propagation delay Tp.

[0020] 4. The transmitter can send retransmissions or new data after the processing / slot delay T2.

[0021] To avoid HARQ pauses, the minimum number of HARQ processes required is ceil((2Tp+T1+T2) / Ts), where Ts refers to the time slot duration in NR.

[0022] Existing HARQ procedures in NR have been primarily designed for terrestrial networks, where propagation delays are typically limited to 1 ms. We now highlight the key problems of existing HARQ protocols with large propagation delays.

[0023] Existing HARQ mechanisms may be infeasible when the propagation delay is significantly greater than that supported by the allowed number of HARQ procedures. For example, consider a scenario where NR DL is to be used for satellite communications. In the GEO case, the RTT propagation delay could be approximately 500 ms. With 16 HARQ procedures supported in NR and a slot duration of 1 ms, the available peak throughput as a percentage of the total channel capacity is very low. Table 1 summarizes the available peak throughput for UEs using LEO, MEO, and GEO satellites.

[0024] Table 1: Number of HARQ procedures required in satellite networks. Peak throughput with 16 HARQ procedures and Ts = 1 ms is also listed.

[0025] satellite Total delay The required quantity for the HARQ process Available peak throughput (% of peak capacity) LEO ~50ms ～50 ～32％ MEO ~180ms ～180 ～8.9％ GEO ~600ms ～600 ～2.7％

[0026] Without a sufficient number of HARQ procedures, the absolute magnitude of the propagation delay can render closed-loop HARQ communication impractical.

[0027] The number of HARQ procedures supported by existing HARQ protocols is insufficient to absorb the potentially large propagation delays in non-terrestrial networks. For example, Table 1 shows that operating HARQ in the presence of large propagation delays requires a substantial increase in the existing number of HARQ procedures. Unfortunately, Rel-15 NR supports a maximum of 16 HARQ procedures in UL / DL, and supporting a larger number of HARQ procedures (especially at the UE) is challenging for at least the following reasons.

[0028] a. It requires large memory in both the transmitter and receiver.

[0029] b. It may be necessary to reduce the HARQ buffer size (and therefore the maximum supported TBS).

[0030] c. A large number of HARQ buffers implies a large number of HARQ receivers.

[0031] d. It increases the signaling overhead used for HARQ IDs. In NR, the HARQ procedure ID is indicated in the DCI, and currently there are 4 bits in the HARQ procedure number field to indicate this. Increasing the number of HARQ procedures to 500 will require approximately 9 bits (more than twice the current 4 bits in the HARQ procedure number field).

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

[0033] To adapt HARQ to non-terrestrial networks, one solution is to semi-statically enable / disable HARQ feedback. For this purpose, the following agreement was made in RAN2#107:

[0034] • It should be possible to semi-statically enable / disable HARQ feedback via RRC signaling.

[0035] • The enabling / disabling of HARQ feedback on a per-UE and per-HARQ procedure basis should be configurable.

[0036] According to the aforementioned agreement, if HARQ is disabled, there is no feedback for transmission. Furthermore, according to the aforementioned agreement, a UE can be configured with a mixture of HARQ procedures with feedback disabled and HARQ procedures with feedback enabled, as the configuration is on a per-UE and per-HARQ procedure basis.

[0037] In NR, when the UE receives the Physical Downlink Shared Channel (PDSCH) from the serving gNB at time slot n, if the PDSCH is successfully decoded, the UE will send a HARQ ACK to the gNB at time slot n+k on the PUCCH (Physical Uplink Control Channel) resources in the uplink. Otherwise, the UE will send a HARQ NACK to the gNB at time slot n+k to indicate that the PDSCH was not successfully decoded.

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

[0039] If code block group (CBG) transport is configured, HARQACK / NACK is reported instead for each CBG in the transport block (TB).

[0040] In the case of carrier aggregation (CA) and / or time division duplex (TDD) operation with multiple carriers, multiple aggregated HARQACK / HARQNACK bits need to be transmitted in a single physical uplink control channel (PUCCH).

[0041] In NR, up to four PUCCH resource sets can be configured for the UE. A PUCCH resource set with pucch-ResourceSetId = 0 can have up to 32 PUCCH resources, while for 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 time slot based on the number of aggregated UCI (Uplink Control Information) bits to be transmitted in the time slot. The UCI bits consist of HARQ ACK / HARQ NACK, Scheduling Request (SR), and Channel State Information (CSI) bits.

[0042] If UE transmits O UCI If there are 10 UCI information bits, the UE determines the PUCCH resource set as follows:

[0043] - The first set of PUCCH resources with pucch-ResourceSetId = 0 (if O UCI ≤2), including 1 or 2 HARQ-ACK bits and positive or negative SR at the time of SR transmission (if the HARQ-ACK and SR transmissions occur simultaneously), or

[0044] - A second set of PUCCH resources with pucch-ResourceSetId = 1 (if provided by a higher layer, if 2 < O) UCI If ≤N2), or

[0045] - A third set of PUCCH resources with pucch-ResourceSetId == 2 (if provided by a higher layer, if N2 < O) UCI (≤N3) or

[0046] - The fourth set of PUCCH resources with pucch-ResourceSetId=3 (if provided by a higher layer, if N3 < O) UCI (If ≤1706).

[0047] Among them, N1 < N2 < N3 is provided by higher layers.

[0048] For PUCCH transmissions with HARQ-ACK information, the UE determines the PUCCH resources 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.

[0049] If more than one DCI format 1_0 or 1_1 is received in the case of carrier aggregation (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.

[0050] NR Rel-15 supports two types of HARQ codebooks for HARQ ACK / HARQ NACK multiplexing of multiple PDSCHs for one or more component carriers (CCs): semi-static (Type 1) and dynamic (Type 2) codebooks. The UE can be configured to use any one of these codebooks for HARQ ACK / HARQ NACK feedback.

[0051] 1. NR type - 1 HARQ - ACK codebook determined

[0052] The time-dependent HARQ codebook (CB) size (DL-associated set) is determined based on the set of configurations for HARQ-ACK timing K1 and the TDD mode with a semi-static configuration in the TDD case. For the Physical Downlink Control Channel (PDCCH) received in slot n for PDSCH, K1 is signaled in the PDCCH and K1 indicates that the HARQACK / HARQ NACK feedback for PDSCH occurs in slot n+K1.

[0053] Figure 2 This example illustrates a Type 1 HARQ codebook for TDD mode, with a set of K1 values ​​from 1 to 5 and a configured time-domain resource allocation table or pdsch-TimeDomainAllocationList, but without non-overlapping PDSCH TDRA allocations; that is, only one PDSCH can be scheduled in a time slot. In this case, there are 5 entries in the HARQ codebook, one entry for each K1 value. For time slots without PDSCH transmission or for time slots where no PDSCH is detected, the corresponding entry in the codebook is filled with NACK.

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

[0055] 2. NR type - 2HARQ - ACK codebook determination

[0056] Unlike Type 1 HARQ codebooks, the size of a Type 2 HARQ codebook dynamically changes based on the number of DCIs (Distributed Control Indicators) released by a scheduled PDSCH or a semi-persistent scheduled (SPS) PDSCH, which are associated with the same PUCCH resources used for HARQ ACK / HARQ NACK feedback. The number of DCIs can be derived based on the counter downlink assignment indicator (DAI) field in the DCI, and in the case of DCI format 1-1, if more than one serving cell is configured, the number of DCIs can also be derived based on the total DAI field.

[0057] 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 time} up to the current serving cell and the current PDCCH monitoring time - where there are (one or more) pairs of PDSCH receptions or SPS PDSCH releases associated with DCI format 1_0 or DCI format 1_1.

[0058] The total DAI value in DCI format 1_1 (when present) represents the total number of {serving cell, PDCCH monitoring time} up to the current PDCCH monitoring time m, where there are one or more pairs of PDSCH receptions or SPS PDSCH releases associated with DCI format 1_0 or DCI format 1_1, and the total DAI value in DCI format 1_1 (when present) is updated from PDCCH monitoring time to PDCCH monitoring time.

[0059] Figure 3 This illustrates an example of DAI allocation. As shown in the figure, the UE is configured with 2 serving cells and 4 PDCCH monitoring opportunities. Each scheduled DCI is represented by a filled box, and the corresponding counter DAI and total DAI value after each scheduled DCI are represented as (counter DAI, total DAI). The counter DAI is updated after each scheduled DCI, while only the total DAI is updated for each monitoring opportunity. Since only 2 bits are allocated for either the counter DAI or the total DAI in the DCI, modulo-4 arithmetic is used to wrap around the actual DAI value. If the number of consecutive undetected DCIs is less than 4, the UE can calculate the actual number of transmitted DCIs even if some DCIs are not detected.

[0060] For DCI format 1-1, only the DAI field exists when using type -2HARQ-ACK, and its width can be 0, 2, or 4 bits. For DCI format 1-0, the DAI field consists of 2 bits.

[0061] The DAI field can exist in DCI format 0_1 ​​for processing HARQ codebooks in the case of UCI transmitted on PUSCH.

[0062] ● First DAI: 1 bit is used for the type-1 HARQ-ACK codebook and 2 bits are used for the type-2 HARQ-ACK codebook.

[0063] ● Second DAI: 2 bits for type-2HARQ-ACK codebook with two HARQ-ACK subcodebooks; otherwise 0 bits.

[0064] 3. NR type - 3HARQ - ACK codebook determination

[0065] The codebook size used for NR Type-3 HARQ-ACK is fixed and determined by the total number of HARQ procedures and the number of configured cells. If the UE is configured with pdsch-HARQ-ACK-OneShotFeedback-r16 via RRC signaling at a higher layer, this codebook is used to provide feedback. The purpose of the Type-3 HARQ-ACK codebook is to provide feedback for all HARQ procedures at once across all active cells.

[0066] Feedback can be requested in DL DCI format 1_1. In response to the trigger, the UE reports HARQ-ACK feedback for all DL HARQ procedures. Alternatively, the format of CBG-based HARQ-ACK or TB-based HARQ-ACK feedback can be configured to be part of a one-time HARQ feedback for component carriers.

[0067] Additionally, to resolve any potential ambiguity between the gNB and the UE that might arise from possible false detections of one or more PDCCHs, the UE can be configured to report the latest New Data Indicator (NDI) value corresponding to the most recently received PDSCH for that HARQ procedure, along with the corresponding HARQ-ACK for the received PDSCH. From the gNB's perspective, if the NDI value matches the last transmitted value, it indicates that the reported HARQ-ACK feedback correctly corresponds to a HARQ procedure with pending feedback. Otherwise, a mismatch suggests the UE is reporting outdated feedback.

[0068] 4. Previous enhancements to NTN

[0069] Enhancements to certain previously proposed HARQ feedback procedures for NTN focus on the handling of disabled procedures in the Type-2 HARQ-ACK codebook. The proposed enhancements do not include information corresponding to HARQ procedures disabled in the Type-2 codebook and include non-incrementing downlink assignment index values ​​for such HARQ procedures. When scheduling disabled HARQ procedures, the actual DAI value can be transmitted in the DAI field, or the DAI field can be retained. The enhancements also include the possibility of omitting the DAI field in the DCI.

[0070] The enhancement further allows disabled HARQ procedures in the Type-1 HARQ codebook to be set to NACK.

[0071] Furthermore, even when the UE is configured with both feedback-disabled and feedback-enabled HARQ procedures, the UE procedures related to the Type-3 HARQ codebook remain undefined. Additionally, the effective use of the Type-3 codebook, along with Type-1 or Type-2 codebooks, and other features such as the use of DCI format 1_2 or the indication of non-numerical values ​​of the delay between the DCI of the PDSCH on the downlink and the HARQ feedback on the uplink, has not been resolved. Summary of the Invention

[0072] Certain aspects of this disclosure and embodiments thereof may provide solutions to these or other challenges. For example, according to certain embodiments, methods and systems are provided for constructing a type-3 HARQ codebook for a UE configured with a feedback-disabled HARQ procedure.

[0073] According to some embodiments, a method performed by a wireless device includes receiving configuration information from a network node that enables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first set of HARQ procedures. Each of the first set of HARQ procedures is identified by a corresponding number in the first set of HARQ procedures, and the configuration is configured therein. The configuration information also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second set of HARQ procedures. Each of the second set of HARQ procedures is identified by a corresponding number in the second set of HARQ procedures. The wireless device constructs a first type of first HARQ codebook based on the first set of HARQ procedure numbers for which HARQ ACK and / or HARQ NACK feedback is enabled, and transmits HARQ ACK and / or HARQ NACK feedback based on the first HARQ codebook to the network node.

[0074] According to some embodiments, a wireless device is adapted to receive configuration information from a network node enabling HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first set of HARQ procedures. Each of the first set of HARQ procedures is identified by a corresponding number in the first set of HARQ procedures, and the configuration is configured therein. The configuration information also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second set of HARQ procedures. Each of the second set of HARQ procedures is identified by a corresponding number in the second set of HARQ procedures. The wireless device is adapted to construct a first type of first HARQ codebook based on the first set of HARQ procedure numbers for the first set of HARQ procedures for which HARQ ACK and / or HARQ NACK feedback is enabled, and to transmit HARQ ACK and / or HARQ NACK feedback based on the first HARQ codebook to the network node.

[0075] According to some embodiments, a method performed by a network node includes transmitting configuration information to a wireless device that enables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first set of HARQ procedures. Each of the first set of HARQ procedures is identified by a corresponding number in the first set of HARQ procedures, and the configuration is configured therein. The configuration information also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second set of HARQ procedures. Each of the second set of HARQ procedures is identified by a corresponding number in the second set of HARQ procedures. The network node receives HARQ ACK and / or HARQ NACK feedback based on a first HARQ codebook from the wireless device. The first HARQ codebook belongs to a first type and is constructed based on the first set of HARQ procedure numbers for which HARQ ACK and / or HARQ NACK feedback is enabled.

[0076] According to some embodiments, a network node is adapted to transmit configuration information enabling HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first set of HARQ procedures to a wireless device. Each of the first set of HARQ procedures is identified by a corresponding number in the first set of HARQ procedures, and configured therein. The configuration information also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second set of HARQ procedures. Each of the second set of HARQ procedures is identified by a corresponding number in the second set of HARQ procedures. The network node is adapted to receive HARQ ACK and / or HARQ NACK feedback based on a first HARQ codebook from the wireless device. The first HARQ codebook belongs to a first type and is constructed based on the first set of HARQ procedure numbers for which HARQ ACK and / or HARQ NACK feedback is enabled.

[0077] Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that certain embodiments define UE procedures for a type 3 HARQ codebook when the UE is configured with two feedback-disabled HARQ procedures that are currently unknown at the current level of development. As another example, a technical advantage may be that certain embodiments reduce HARQ feedback overhead because the codebook size only considers the PDSCH associated with feedback-enabled HARQ procedures.

[0078] Another technical advantage may be that some embodiments provide the use of non-numerical values ​​for K1 and methods for reducing DCI overhead to efficiently handle HARQ feedback for HARQ processes with feedback disabled.

[0079] Another technical advantage is that certain embodiments decouple operations between enabled and disabled HARQ procedures by using DCI formats 0_0 / 0_1 and 1_0 / 1_1 and corresponding configurations for operations using enabled HARQ procedures and DCI format 0_2 / 1_2 having corresponding configurations for operations using disabled HARQ procedures.

[0080] Other advantages will be readily apparent to those skilled in the art. Certain embodiments may have one, some, or all of the advantages described. Attached Figure Description

[0081] To gain a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein:

[0082] Figure 1 The HARQ protocol was explained;

[0083] Figure 2 This illustrates an example of a Type 1 HARQ codebook used for example TDD patterns;

[0084] Figure 3 This illustrates an example DAI allocation;

[0085] Figure 4 An example wireless network according to certain embodiments is described;

[0086] Figure 5 Example network nodes according to certain embodiments are illustrated;

[0087] Figure 6 An example wireless device according to certain embodiments is described;

[0088] Figure 7 An example user equipment according to certain embodiments is described;

[0089] Figure 8 This describes a virtualization environment, according to certain embodiments, in which functionality implemented by some embodiments can be virtualized;

[0090] Figure 9 This describes a telecommunications network connected to a host via an intermediate network according to certain embodiments;

[0091] Figure 10 A generalized block diagram illustrating a host communicating with a user equipment via a base station over a partial wireless connection according to certain embodiments is provided.

[0092] Figure 11 This describes a method implemented in a communication system according to one embodiment;

[0093] Figure 12Another method for implementation in a communication system according to one embodiment is described;

[0094] Figure 13 Another method for implementation in a communication system according to one embodiment is described;

[0095] Figure 14 Another method for implementation in a communication system according to one embodiment is described;

[0096] Figure 15 Example methods performed by a wireless device according to certain embodiments are described;

[0097] Figure 16 An exemplary virtual computing device according to certain embodiments is described;

[0098] Figure 17 Example methods performed by network nodes according to certain embodiments are described; and

[0099] Figure 18 Another exemplary virtual computing device according to certain embodiments is described. Detailed Implementation

[0100] Some embodiments of the embodiments 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 being 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.

[0101] Generally, unless the context in which they are used implies a different meaning and / or clearly gives a different meaning, all terms used herein should be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to a / an / said element, device, component, part, step, etc. are openly interpreted as referring to at least one instance of said element, device, component, part, step, etc. Unless a step is explicitly described as following or preceding another step and / or it is implied that a step must follow or precede another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0102] In some embodiments, the more general term “network node” may be used and may correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or with another network node. Examples of network nodes include NodeBs, primary NodeBs (MeNBs), network nodes belonging to primary cell groups (MCGs) or secondary cell groups (SCGs), base stations (BSs), multi-standard radio (MSR) radio nodes such as MSR BSs, eNodeBs (eNBs), gNodeBs (gNBs), network controllers, radio network controllers (RNCs), base station controllers (BSCs), relays, donor nodes of control relays, base transceiver stations (BTSs), access points (APs), transmission points, transmission nodes, remote radio units (RRUs), remote radio heads (RRHs), nodes in distributed antenna systems (DASs), core network nodes (e.g., mobile switching centers (MSCs), mobility management entities (MMEs), etc.), operations and maintenance (O&M), operations support systems (OSSs), ad hoc networks (SONs), location nodes (e.g., evolved serving mobile location centers (E-SMLCs)), minimized drive tests (MDTs), test equipment (physical nodes or software), etc.

[0103] In some embodiments, the non-limiting terms User Equipment (UE) or Wireless Device may be used and may refer to any type of wireless device that communicates with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, personal digital assistants (PDAs), tablet computers, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), unified serial bus (USB) dongles, UE class M1, UE class M2, proximity service UEs (ProSe UEs), vehicle-to-vehicle UEs (V2V UEs), vehicle-to-everything (V2X UEs), etc.

[0104] Furthermore, terms such as base station / gNB and UE should be considered non-restrictive and do not specifically imply any hierarchical relationship between them; generally, "gNodeB" can be considered device 1 and "UE" can be considered device 2, and the two devices communicate with each other via a radio channel. And in the following text, transmitter or receiver can be either gNB or UE.

[0105] In the following embodiments, the term K1 is sometimes used to refer to the PDSCH-to-HARQ_Feedback timing indicator and the terms "non-numerical" and "not applicable" can be used interchangeably to indicate the value of K1 that will not be used by the UE.

[0106] According to certain embodiments, the methods, systems, and techniques disclosed herein may include some or all of the following features:

[0107] • The construction of the Type 3 HARQ codebook depends on whether the UE is scheduled using the PDSCH associated with the feedback-enabled HARQ procedure.

[0108] • The codebook is sized to include only the HARQ process for which feedback is enabled in order to save overhead.

[0109] According to certain embodiments, methods, systems, and techniques can use non-numerical values ​​of K1 to efficiently process HARQ feedback for both feedback-enabled and feedback-disabled HARQ processes.

[0110] • When used in conjunction with a Type 1 HARQ codebook, the indication of a non-numeric value for K1 can be used to dynamically enable or disable the HARQ process.

[0111] According to certain embodiments, the methods, systems, and techniques can provide novel uses of existing functionality to reduce DCI overhead:

[0112] • DCI format 0_2 / 1_2 can be used to specifically schedule disabled HARQ procedures.

[0113] • The HARQ process number, DAI, and RV fields can be excluded by properly configuring the parameters in the DCI message.

[0114] • The TDRA table in DCI format 2_1 can be used to schedule PDSCH using the disabled HARQ procedure.

[0115] Type-3 HARQ codebook processing for disabled procedures: Because the Type-3 HARQ codebook includes feedback for all HARQ procedures, the UE knows the size of the portion of the HARQ codebook occupied by enabled HARQ procedures and the size of the portion occupied by disabled HARQ procedures based on configuration information from higher layers. Considering that no information needs to be sent for disabled HARQ procedures, some embodiments propose that the Type-3 HARQ codebook only include feedback for enabled HARQ procedures. In many scenarios where the NTN can operate with very few HARQ procedures enabled, this can lead to a significant reduction in overhead when using the Type-3 HARQ codebook.

[0116] Below are examples of pseudocode variations that can be implemented according to this embodiment:

[0117]

[0118]

[0119]

[0120]

[0121]

[0122]

[0123]

[0124] Operations of Type 3 HARQ codebook along with Type 1 codebook

[0125] These embodiments can be useful when the type 3 HARQ codebook is prepared for primary use. The type 1 HARQ codebook is configured to be very small.

[0126] According to some embodiments, for example, when a HARQ procedure is scheduled to be enabled, a non-numerical K1 value is indicated in the DCI, which prompts the UE to discard the HARQ procedure. HARQ feedback is then obtained by later triggering feedback against a type 3 HARQ codebook. By operating in this way, HARQ feedback overhead can be minimized in scenarios where the network is operating with very few HARQ procedures enabled.

[0127] Operations of Type 1 HARQ codebook

[0128] When operating on a Type 1 HARQ codebook for NTN, the UE only reports the HARQ-ACK information for the corresponding PDSCH reception in the HARQ-ACK codebook transmitted by the UE in the time slot indicated by the value of the PDSCH-to-HARQ_Feedback timing indicator when the HARQ procedure corresponding to PDSCH reception is enabled.

[0129] If the UE receives a DL DCI indicating a disabled HARQ procedure, the UE may not generate corresponding HARQ-ACK information for the PDSCH scheduled by the DCI. In other words, the PRI and K1 fields in the DCI are ignored. If the UE reports HARQ-ACK information for the PDSCH received corresponding to the disabled HARQ, the UE sets the value of each corresponding HARQ-ACK information bit to NACK.

[0130] According to some embodiments, if all HARQ procedures in the HARQ process corresponding to the scheduled PDSCH in the DL association set are disabled, then Type 1 HARQ codebooks are not transmitted in the PUCCH resources corresponding to the DL association set. Since the gNB knows the already scheduled HARQ procedures, the gNB does not expect the UE to transmit any HARQ codebooks on the PUCCH; that is, there is no misalignment between the gNB and the UE.

[0131] Dynamic Disabling of HARQ Procedures When Using Non-Numerical K1 Values ​​with Type 1 Codebooks According to some embodiments, the enabled or disabled HARQ procedures can be dynamically changed. This differs from the embodiments described above, and as in the previous embodiments, according to some embodiments, this is achieved by leveraging the fact that the UE discards HARQ feedback received with non-numerical K1 values ​​when configured with a Type 1 HARQ codebook.

[0132] An exemplary example of such operation can be described below. The UE operates using a Type 1 codebook of a fixed size, as configured by a higher layer. The UE may be initially configured with all HARQ procedures that are currently enabled. When scheduling PDSCH reception for the UE, if the network chooses to dynamically disable the HARQ procedure corresponding to the PDSCH being scheduled, the gNB may set the PDSCH-to-HARQ_Feedback timing indicator value in the DCI to an inapplicable value (-1) derived from the value configured by a higher layer in dl-DataToUL-ACK. Since no timing information is provided for this HARQ procedure, the UE will discard the feedback information that effectively disables the HARQ procedure for this particular PDSCH reception.

[0133] Using a non-numerical K1 value along with the DAI value to manage feedback for HARQ procedures with a Type 2 HARQ codebook: As mentioned above, it has been proposed as an enhancement to NTN to report the true DAI value in the DAI field when operating with a Type-2 HARQ codebook and when a disabled HARQ procedure is scheduled. However, some ambiguity may exist when all HARQ procedures currently scheduled to the UE are disabled. The UE may not be able to distinguish whether the indicated DAI value reflects a DCI of a PDSCH that was missed by the UE, where the scheduled PDSCH corresponds to an enabled HARQ procedure, or the UE may not be able to distinguish whether the indicated DAI value is meaningless because scheduling with an enabled HARQ procedure does not have any incomplete feedback to report. Therefore, according to some embodiments, it may be necessary to signal to the UE that the DAI value should be ignored in some instances. In a particular embodiment, this is achieved by using an inapplicable value for the PDSCH-to-HARQ_Feedback timing indicator (referred to as the non-numerical K1 value). That is, when the UE schedules PDSCH using a non-numerical K1 value and a disabled HARQ when operating with a type 2 HARQ codebook, the DAI value is ignored.

[0134] When scheduling using a disabled HARQ process, DCI format 1_2 is used to reduce DCI overhead. In some embodiments, DCI format 1_1 is used for enabled HARQ processes and DCI format 1_2 is used for disabled HARQ processes. In a particular embodiment, the DAI and redundant version fields can be configured to have zero bits in DCI format 1_2 to save overhead. In a particular embodiment, the HARQ process number can also be set to zero by configuring the higher-level parameter harq-ProcessNumberSizeForDCI-Format1-2 to 0 bits. Alternatively, the corresponding field can be retained in the DCI to indicate the corresponding HARQ process number. The DAI field can be set to zero bits by not configuring the higher-level parameter downlinkAssignmentIndexForDCI-Format1-2. The redundant version is set to zero bits by configuring the higher-level parameter numberOfBitsForRV-ForDCI-Format1-2 to zero bits.

[0135] Of course, when scheduling PDSCH using DCI format 1_2, the UE automatically assumes the use of the redundant version 0 and that no feedback is necessary for PDSCH. Therefore, according to some embodiments, novel scheduling methods can be used to reuse existing functionality, where enabled and disabled HARQ procedures are used for scheduling using DCI formats 1_1 and 1_2 respectively.

[0136] If the UE is configured with a Type-2 HARQ-ACK codebook, by using DCI 1_2 to schedule the PDSCH using a disabled HARQ procedure with a 0-bit DAI field, the UE will not generate any HARQ codebook for the PDSCH corresponding to the disabled HARQ procedure following the Rel-16 procedure. By using DCI format 1_0 / 1_1 for the PDSCH using an enabled HARQ procedure, the corresponding CB will be generated and transmitted on the associated PUCCH.

[0137] When scheduling is performed using a disabled HARQ procedure and operations are performed using a type 1 HARQ codebook, DCI format 1_2 is used to reduce HARQ feedback overhead.

[0138] According to certain embodiments, if the UE is configured with a Type-1 HARQ-ACK codebook, pdsch-TimeDomainAllocationListForDCI-Format1-2 can be used to schedule PDSCH using a disabled HARQ procedure that can be excluded from the construction of a semi-static (Type-1) HARQ codebook. In this sense, the Type-1 HARQ codebook will not carry the overhead caused by PDSCH in the case of disabled HARQ.

[0139] Figure 4 Wireless networks according to some embodiments are described. While the subjects described herein can be implemented using any suitable components in any appropriate type of system, similar to... Figure 4 The example wireless networks described herein are illustrated with respect to embodiments of the wireless networks disclosed herein. For simplicity, Figure 4 The wireless network depicted only includes network 106, network nodes 160 and 160b, and wireless device 110. In practice, the 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, service provider, or any other network node or terminal device. Among the described components, network node 160 and wireless device 110 are depicted with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access and / or use of services provided by or via the wireless network.

[0140] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems and / or can interface with any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems. In some embodiments, a wireless network can be configured to operate according to a specific standard or other type of predefined rules or procedures. Therefore, specific embodiments of a wireless network can 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 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0141] Network 106 may include one or more backhaul networks, core networks, IP networks, shared switched telephone networks (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.

[0142] Network node 160 and wireless device 110 include various components described in more detail below. These components work together to provide functionality for the network node and / or wireless device, such as providing wireless connectivity in a wireless network. In various embodiments, the 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 transmission of data and / or signals, whether via wired or wireless connections.

[0143] Figure 5Example network node 160 according to certain embodiments is illustrated. As used herein, a network node refers to a device capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations may be classified based on the coverage they provide (or, in other words, their transmit power levels), and base stations may then also be referred to as femtobases, picobases, microbases, or macrobases. A base station may be a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) portions of a distributed radio base station such as a centralized digital unit and / or a remote radio unit (RRU) sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio device. The distributed radio base station portion can also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), network controllers (such as a radio network controller (RNC) or base station controller (BSC)), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. 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 set of devices) capable of, configured to, arranged to, and / or operable to enable and / or provide access to a wireless network for wireless devices or to provide some service to wireless devices already connected to the wireless network.

[0144] exist Figure 5 In the network node 160, processing circuitry 170, device-readable medium 180, interface 190, auxiliary equipment 184, power supply 186, power circuitry 187, and antenna 162 are included. Although in Figure 5The network node 160 illustrated in the example wireless network may represent an apparatus including the illustrated combination of hardware components, but other embodiments may include network nodes having different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 160 are depicted as a single box within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components that make up a single illustrated component (e.g., device-readable medium 180 may include multiple separate hard disk drives and multiple RAM modules).

[0145] Similarly, network node 160 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some scenarios where network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, separate network node in some instances. In some embodiments, network node 160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by RATs). Network node 160 may also include multiple sets of various illustrated components for integrating different wireless technologies (such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) into network node 160. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 160.

[0146] Processing circuit 170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by processing circuit 170 may include processing information acquired through processing circuit 170 by, for example, converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0147] Processing circuitry 170 may include: a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device or resource; or a combination of hardware, software, and / or coded logic operable to provide the functionality of network node 160, either alone or in combination with other network node 160 components, such as device-readable medium 180. For example, processing circuitry 170 may execute instructions stored in device-readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system-on-a-chip (SoC).

[0148] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, RF transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units such as radio units and digital units. In alternative embodiments, some or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit.

[0149] In some embodiments, processing circuitry 170 may execute some or all of the functionalities described herein as provided by a network node, base station, eNB, gNB, or other such network device by executing instructions stored on device-readable medium 180 or in memory within processing circuitry 170. In alternative embodiments, processing circuitry 170 may provide some or all of the functionalities, such as by hard-wiring, without executing instructions stored on separate or discrete device-readable medium. In any of those embodiments, processing circuitry 170 may be configured to perform the described functionalities regardless of whether instructions stored on device-readable storage medium are executed. The benefits provided by such functionalities are not limited to processing circuitry 170 alone or to other components of network node 160, but are generally enjoyed by network node 160 as a whole and / or by end users and wireless networks.

[0150] Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications, and / or other instructions that can be executed by processing circuitry 170 and utilized by network node 160, including one or more of logic, rules, code, tables, etc. Device-readable medium 180 may be used to store any calculations performed by processing circuitry 170 and / or any data received via interface 190. In some embodiments, integration of processing circuitry 170 and device-readable medium 180 may be considered.

[0151] Interface 190 is used for wired or wireless transmission of signaling and / or data between network node 160, network 106, and / or wireless device 110. As illustrated, interface 190 includes one or more ports / terminals 194 for transmitting and receiving data from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuitry 192 that may be coupled to antenna 162 or, in some embodiments, may be part of antenna 162. Radio front-end circuitry 192 includes a filter 198 and an amplifier 196. Radio front-end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front-end circuitry may be configured to modulate the signal transmitted between antenna 162 and processing circuitry 170. Radio front-end circuitry 192 can receive digital data to be transmitted via a wireless connection to other network nodes or wireless devices. Radio front-end circuitry 192 may use a combination of filter 198 and / or amplifier 196 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via antenna 162. Similarly, when data is received, antenna 162 can collect radio signals and then convert the radio signals into digital data via radio front-end circuitry 192. The digital data can then be transmitted to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0152] In some alternative embodiments, network node 160 may not include a separate radio front-end circuitry 192; instead, processing circuitry 170 may include radio front-end circuitry and may be connected to antenna 162 without a separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered part of interface 190. In other embodiments, interface 190 may include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0153] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals in, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from devices within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals along a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be detachable from network node 160 and can be connected to network node 160 via an interface or port.

[0154] Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0155] Power circuitry 187 may include or be coupled to power management circuitry and is configured to supply power to components of network node 160 for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and / or power circuitry 187 may be configured to supply power to various components of network node 160 in a manner suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power source 186 may be included in or outside power circuitry 187 and / or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electrical outlet) via input circuitry or interface such as a cable, thereby supplying power to power circuitry 187. As another example, power source 186 may include a power source in the form of a battery or battery pack, connected to or integrated into power circuitry 187. The battery can provide backup power in the event of an external power failure. Other types of power sources, such as photovoltaic devices, may also be used.

[0156] Alternative embodiments of network node 160 may include, except Figure 5 Additional components beyond those shown herein may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, network node 160 may include a user interface device to allow information to be input to network node 160 and to allow information to be output from network node 160. This allows a user to perform diagnostic, maintenance, repair, and other management functions for network node 160.

[0157] Figure 6Example wireless device 110 according to certain embodiments is described. As used herein, a wireless device means a means capable of, configured to, arranged to, and / or operable for wireless communication with network nodes and / or other wireless devices. Unless otherwise noted, the term wireless device may be used interchangeably with user equipment (UE) herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. In some embodiments, a wireless device may be configured to transmit and / or receive information without direct human interaction. For example, a wireless device may be designed to transmit information to the network at a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of wireless devices include, but are not limited to, smartphones, mobile phones, cell phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless terminals, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, etc. Wireless devices can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for direct-link communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case, can be referred to as D2D communication devices. As another specific example, in the Internet of Things (IoT) scenario, a wireless device can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another wireless device and / or network node. In this context, a wireless device can be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a wireless device can be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, a wireless device can refer to a vehicle or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation. A wireless device as described above can refer to an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above can be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

[0158] As described, wireless device 110 includes an antenna 111, an interface 114, processing circuitry 120, a device-readable medium 130, a user interface device 132, auxiliary devices 134, a power supply 136, and power circuitry 137. Wireless device 110 may include one or more sets of the components described to support various wireless technologies supported by wireless device 110, 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 chipsets, just like other components within wireless device 110.

[0159] Antenna 111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 114. In some alternative embodiments, antenna 111 may be detachable from wireless device 110 and may be connected to wireless device 110 via an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receive or transmit operation described herein as being performed by a wireless device. Any information, data, and / or signals may be received from a network node and / or another wireless device. In some embodiments, radio front-end circuitry and / or antenna 111 may be considered as an interface.

[0160] As illustrated, interface 114 includes radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front-end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to modulate the signal transmitted between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to a portion of antenna 111 or may be a portion of antenna 111. In some embodiments, wireless device 110 may not include a separate radio front-end circuitry 112; instead, processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered part of interface 114. Radio front-end circuitry 112 can receive digital data to be transmitted via a wireless connection to other network nodes or wireless devices. Radio front-end circuitry 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 111. Similarly, when data is received, antenna 111 can collect radio signals and then convert the radio signals into digital data via radio front-end circuitry 112. The digital data can then be transmitted to processing circuitry 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0161] Processing circuitry 120 may include a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of one or more of these, or a combination of hardware, software, and / or coded logic operable to provide the functionality of wireless device 110, either alone or in combination with other wireless device 110 components such as device-readable medium 130. Such functionality may include any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device-readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

[0162] As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, processing circuitry may include different components and / or different combinations of components. In some embodiments, processing circuitry 120 of wireless device 110 may include a System-on-a-Chip (SOC). In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or chipsets. In alternative embodiments, a portion or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into a single chip or chipset, and RF transceiver circuitry 122 may be on a separate chip or chipset. In still other alternative embodiments, a portion or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or chipset, and application processing circuitry 126 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be integrated into the same chip or chip assembly. In some embodiments, the RF transceiver circuitry 122 may be part of interface 114. The RF transceiver circuitry 122 may modulate RF signals for use by processing circuitry 120.

[0163] In some embodiments, some or all of the functionality described herein as being performed by a wireless device can be provided by executing instructions stored on a device-readable medium 130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided, for example, by hard-wiring, without executing instructions stored on a separate or discrete device-readable storage medium. In any particular embodiment of those particular embodiments, the processing circuitry 120 can be configured to perform the described functionality regardless of whether instructions stored on the device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuitry 120 alone or to other components of the wireless device 110, but are generally enjoyed by the wireless device 110 as a whole and / or by the end user and the wireless network.

[0164] Processing circuitry 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by a wireless device. Such operations performed by processing circuitry 120 may include processing information acquired by processing circuitry 120 by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored by wireless device 110, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0165] Device-readable medium 130 may be operable to store one or more computer programs, software, applications, and / or other instructions executable by processing circuitry 120, including logic, rules, code, tables, etc. Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., optical disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory means that stores information, data, and / or instructions that can be used by processing circuitry 120. In some embodiments, integration of processing circuitry 120 and device-readable medium 130 may be considered.

[0166] User interface device 132 can provide components that consider human user interaction with wireless device 110. Such interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 132 can be operated to generate output to the user and allow the user to provide input to wireless device 110. The type of interaction can vary depending on the type of user interface device 132 installed in wireless device 110. For example, if wireless device 110 is a smartphone, the interaction can be via a touchscreen; if wireless device 110 is a smart meter, the interaction can be via a screen providing usage information (e.g., gallons used) or a speaker providing an audible alarm (e.g., if smoke is detected). User interface device 132 can include input interfaces, means and circuitry, as well as output interfaces, means and circuitry. User interface device 132 is configured to allow information to be input to wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface device 132 can include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 132 is also configured to allow output of information from wireless device 110 and to allow processing circuitry 120 to output of information from wireless device 110. User interface device 132 may include, for example, a speaker, display, oscillating circuitry, USB port, headphone jack, or other output circuitry. Using one or more input and output interfaces, means, and circuitry of user interface device 132, wireless device 110 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.

[0167] The auxiliary device 134 is operable to provide more specific functionality that can typically not be performed by a wireless device. This may include specialized 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 134 may vary depending on the embodiment and / or scenario.

[0168] In some embodiments, power source 136 may be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power cell, may also be used. Wireless device 110 may further include power circuitry 137 for delivering power from power source 136 to various parts of wireless device 110 that require power from power source 136 to perform any functionality described or indicated herein. Power circuitry 137 may include power management circuitry in some embodiments. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in this case, wireless device 110 may be connectable to an external power source (such as an electrical outlet) via input circuitry or an interface such as a power cable. Power circuitry 137 may also be operable to deliver power from an external power source to power source 136 in some embodiments. This may be, for example, charging power source 136. Power circuitry 137 may perform any formatting, conversion, or other modification on the power from power source 136 to make the power suitable for the respective components of wireless device 110 that are powering it.

[0169] Figure 7 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device intended to be sold to or operated by a human user but may not or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device not intended to be sold to or operated by an end user but may be associated with a user or operated for the user's benefit (e.g., a smart meter). UE200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 5 As described herein, UE 200 is an example of a radio device configured to communicate according to one or more communication standards such as GSM, UMTS, LTE, and / or 5G standards published by the 3GPP (3rd Generation Partnership Project). As previously mentioned, the terms radio device and UE can be used interchangeably. Accordingly, although... Figure 7 This is for UEs, but the components discussed in this article also apply to wireless devices, and vice versa.

[0170] exist Figure 7In this embodiment, UE 200 includes processing circuitry 201 operatively coupled to input / output interface 205; radio frequency (RF) interface 209; network connectivity interface 211; memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221, etc.; communication subsystem 231; power supply 233; and / or any other component; or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may use... Figure 7 The components shown can be all or only a subset of the components. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0171] exist Figure 7 In this embodiment, processing circuitry 201 can be configured to process computer instructions and data. Processing circuitry 201 can be configured to implement any sequential state machine that operates to execute machine instructions stored in 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 along with appropriate firmware; one or more stored programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP), along with appropriate software; or any combination of the above. For example, processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0172] In the depicted embodiments, the input / output interface 205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 200 can be configured to use an output device via the input / output interface 205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 200 can be configured to use an input device via the input / output interface 205 to allow the user to capture information into the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a navigation pad, a scroll wheel, a smart card, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0173] exist Figure 7 In this configuration, RF interface 209 can be configured to provide communication interfaces to RF components such as transmitters, receivers, and antennas. Network connectivity interface 211 can be configured to provide communication interfaces to network 243a. Network 243a can include wired and / or wireless networks such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 243a may include a Wi-Fi network. Network connectivity interface 211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices on the communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, etc. Network connectivity interface 211 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). Transmitter and receiver functionality can share circuit components, software, or firmware, or alternatively, transmitter and receiver functionality can be implemented separately.

[0174] RAM 217 can be configured to be connected to processing circuitry 201 via bus 202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 219 can be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 can be configured to store immutable low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. Storage medium 221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable cartridge disk, or flash drive. In one example, storage medium 221 can be configured to include operating system 223, application 225 such as a web browser application, a widget or gadget engine, or another application, and data file 227. Storage medium 221 can store any of the various operating systems or combinations of operating systems available for use by UE 200.

[0175] Storage medium 221 can be configured to include multiple physical drive units such as a redundant array of independent disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital universal disc (HD-DVD) optical disc drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory such as a subscriber identification module or a removable subscriber identity (SIM / RUIM) module, other memory, or any combination thereof. Storage medium 221 can allow UE 200 to access computer-executable instructions, applications, etc., stored on a transient or non-transient storage medium to offload or upload data. Articles of manufacture, such as those utilizing a communication system, can be tangibly included in storage medium 221, which may include a device-readable medium.

[0176] exist Figure 7In this configuration, processing circuitry 201 can be configured to communicate with network 243b using communication subsystem 231. Networks 243a and 243b can be the same network or multiple networks, or different networks or multiple networks. Communication subsystem 231 can be configured to include one or more transceivers for communicating with network 243b. For example, communication subsystem 231 can be configured to include one or more remote transceivers for communicating with one or more devices, such as another wireless device, UE, or radio access network (RAN) base station, according to one or more communication protocols such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMAX, etc. Each transceiver can include transmitter 233 and / or receiver 235 to respectively implement transmitter or receiver functionality suitable for the RAN link (e.g., frequency allocation, etc.). Furthermore, transmitter 233 and receiver 235 of each transceiver can share circuit components, software, or firmware, or alternatively, transmitter 233 and receiver 235 of each transceiver can be implemented separately.

[0177] In the illustrated embodiments, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may 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 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of the UE 200.

[0178] The features, benefits, and / or functions described herein can be implemented in one component of the UE 200 or partitioned across multiple components of the UE 200. Furthermore, the features, benefits, and / or functions described herein can be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 231 can be configured to include any component described herein. Additionally, the processing circuitry 201 can be configured to communicate with any component of such a component via bus 202. In another example, any component of such a component can be represented by program instructions stored in memory, which, when executed by the processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any component of such a component can be partitioned between the processing circuitry 201 and the communication subsystem 231. In yet another example, non-computationally intensive functions of any component of such a component can be implemented in software or firmware, and computationally intensive functions can be implemented in hardware.

[0179] Figure 8 This is a schematic block diagram illustrating a virtualization environment 300 in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus that may include a virtualized hardware platform, storage device, and networking resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or to apparatuses (e.g., UEs, wireless devices, or any other type of communication device) or components thereof, and virtualization relates to the implementation of at least a portion of its functionality as one or more virtual components (e.g., by means of one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0180] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more hardware nodes in hardware node 330. Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0181] The functionality can be implemented by operating one or more applications 320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.) that implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. Applications 320 run in a virtualized environment 300 that provides hardware 330 including processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360, according to which application 320 operates to provide one or more of the features, benefits, and / or functions disclosed herein.

[0182] The virtualization environment 300 includes general-purpose or special-purpose network hardware devices 330, which include a collection of one or more processors or processing circuits 360. These processors or processing circuits 360 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 a dedicated processor. Each hardware device may include a memory 390-1, which may be a non-permanent memory for temporarily storing instructions 395 or software executable by the processing circuits 360. Each hardware device may include one or more network interface controllers (NICs) 370, also referred to as network interface cards, which include a physical network interface 380. Each hardware device may also include a non-transitory, permanent, machine-readable storage medium 390-2 in which software 395 and / or instructions executable by the processing circuits 360 are stored. Software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also referred to as a hypervisor), software for executing virtual machine 340, and software that allows it to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0183] Virtual machine 340 includes virtual processing, virtual memory, virtual networking or interface, and virtual storage device, and can be run through a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of virtual device 320 can be implemented on one or more virtual machines in virtual machine 340, and can be implemented in different ways.

[0184] During operation, the processing circuitry 360 executes software 395 to instantiate a hypervisor, sometimes referred to as a virtual machine monitor (VMM) or virtualization layer 350. The virtualization layer 350 can present a virtual operating platform to the virtual machine 340 that appears to be networked hardware.

[0185] like Figure 8 As shown, hardware 330 can be a standalone network node with general-purpose or special-purpose components. Hardware 330 may include antenna 3225 and may utilize virtualization to implement some functions. Alternatively, hardware 330 may be part of a larger hardware cluster (such as in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed via management and coordination (MANO) 3100, which in particular also oversees the lifecycle management of application 320.

[0186] Hardware virtualization is sometimes referred to as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices into industry-standard high-capacity server hardware, physical switches, and physical storage devices that can be located in data centers and customer premises.

[0187] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each virtual machine in virtual machine 340, and the portion of hardware 330 that executes that virtual machine, whether dedicated to that virtual machine or shared by that virtual machine with other virtual machines in virtual machine 340, forms a separate virtual network element (VNE).

[0188] Still within the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running in one or more virtual machines 340 on top of the hardware networking infrastructure 330 and corresponds to Figure 8 Application 320.

[0189] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio unit 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0190] In some embodiments, signaling may be affected when using control system 3230, which may alternatively be used for communication between hardware node 330 and radio unit 3200.

[0191] Figure 9 This describes a telecommunications network connected to a host via an intermediate network according to some embodiments.

[0192] refer to Figure 9According to an embodiment, the communication system includes a telecommunications network 410, such as a 3GPP-type cellular network, which includes an access network 411, such as a radio access network, and a core network 414. The access network 411 includes multiple base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to the core network 414 via a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 in coverage area 413a can wirelessly connect to the corresponding base station 412a. Although multiple UEs 491, 492 are described in this example, the disclosed embodiments are equally applicable to situations where a single UE is in a coverage area or where a single UE is connected to the corresponding base station 412.

[0193] Telecommunications network 410 is itself connected to host 430, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Host 430 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. Connections 421 and 422 between telecommunications network 410 and host 430 may extend directly from core network 414 to host 430, or via optional intermediate network 420. Intermediate network 420 may be one or more of public, private, or hosted networks; intermediate network 420 (if any) may be a backbone network or the Internet; in particular, intermediate network 420 may include two or more subnetworks (not shown).

[0194] Figure 9The communication system as a whole enables connectivity between connected UEs 491, 492 and host 430. This connectivity can be described as an over-the-top (OTT) connection 450. Host 430 and connected UEs 491, 492 are configured to transmit data and / or signaling via OTT connection 450 using access network 411, core network 414, any intermediate network 420, and possible additional infrastructure (not shown) as intermediaries. OTT connection 450 can be transparent in the sense that the participating communication devices traversing it are unaware of the routing of uplink and downlink communications. For example, it may not be necessary to inform base station 412 of past routing of incoming downlink communications, where data originating from host 430 will be forwarded (e.g., handed over) to connected UE 491. Similarly, base station 412 does not need to know the future routing of outgoing uplink communications originating from UE 491 toward host 430.

[0195] Figure 10 This describes a host that communicates with a user equipment via a base station over a partial wireless connection, according to some embodiments.

[0196] Now refer to Figure 10 This section describes an example implementation of the UE, base station, and host discussed in the preceding paragraphs according to an embodiment. In the communication system 500, the host 510 includes hardware 515, which includes a communication interface 516 configured to establish and maintain wired or wireless connections with different communication devices of the communication system 500. The host 510 further includes processing circuitry 518, which may have storage and / or processing capabilities. In particular, the processing circuitry 518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host 510 further includes software 511, which is stored in or accessible by the host 510 and executable by the processing circuitry 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to remote users of the UE 530, such as those connected via an OTT connection 550 terminated at the UE 530 and the host 510. When providing services to remote users, host application 512 can provide user data transmitted using OTT connection 550.

[0197] The communication system 500 further includes a base station 520 provided in a telecommunications system and including hardware 525 that enables it to communicate with the host 510 and the UE 530. Hardware 525 may include a communication interface 526 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 500, and for establishing and maintaining connections with at least the coverage area served by the base station 520 (not in...). Figure 10 The radio interface 527 of the UE 530's wireless connection 570 (shown in the diagram) is also shown. The communication interface 526 can be configured to facilitate a connection 560 to the host 510. The connection 560 can be direct or it can be via the core network of a telecommunications system (not shown in the diagram). Figure 10 (as shown in the diagram) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 525 of base station 520 further includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

[0198] The communication system 500 further includes the previously mentioned UE 530. Its hardware 535 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area currently in which the UE 530 is located. The hardware 535 of the UE 530 further includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) suitable for executing instructions. The UE 530 further includes software 531, which is stored in or accessible by the UE 530 and executable by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 may be operable to provide services to human or non-human users via the UE 530 with the support of the host 510. In the host 510, a executing host application 512 may communicate with the executing client application 532 via an OTT connection 550 terminated at the UE 530 and the host 510. When providing a service to a user, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both request data and user data. Client application 532 can interact with the user to generate the user data it provides.

[0199] It is noted that Figure 10 The host 510, base station 520, and UE 530 described herein can be respectively connected to Figure 9The host 430, base stations 412a, 412b, and 412c are similar to or identical to one of the UEs 491 and 492. That is, the internal workings of these entities can be as follows: Figure 10 As shown, and independently, the surrounding network topology can be Figure 9 The network topology.

[0200] exist Figure 10 The OTT connection 550 has been abstractly depicted to illustrate communication between host 510 and UE 530 via base station 520, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from UE 530, the service provider operating host 510, or both. When OTT connection 550 is active, the network infrastructure can further make decisions, through which it dynamically changes the routing (e.g., based on load balancing considerations or network reconfiguration).

[0201] The wireless connection 570 between UE 530 and base station 520 is based on the teachings of embodiments described throughout this disclosure. One or more embodiments in various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, wherein wireless connection 570 forms the final segment. More precisely, the teachings of these embodiments can improve data rates, latency, and / or power consumption and thereby provide benefits such as reduced user wait times, relaxed limitations on file size, better responsiveness, and extended battery life.

[0202] For the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments, a measurement process may be provided. In response to changes in the measurement results, optional network functionality for reconfiguring the OTT connection 550 between host 510 and UE 530 may further exist. The measurement process and / or network functionality for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of host 510, or in the software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 550 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities that the software 511, 531 may calculate or estimate the monitored quantities from. Reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect base station 520, and may be unknown or undetectable to base station 520. Such processes and functionalities are known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling that facilitates the measurement of throughput, propagation time, latency, etc., by the host 510. Measurements can be performed because while software 511 and 531 monitor propagation time, errors, etc., software 511 and 531 use OTT connection 550 to facilitate message transmission, particularly empty or "dumb" messages.

[0203] Figure 11 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 9 and Figure 10 The described hosts, base stations, and UEs. For the sake of simplicity in this disclosure, only references will be included in this section. Figure 11 The diagram shows the steps. In step 610, the host provides user data. In sub-step 611 of step 610 (which may be optional), the host provides user data by executing a host application. In step 620, the host initiates a transmission carrying user data to the UE. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the host-initiated transmission to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host.

[0204] Figure 12 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 9 and Figure 10The described hosts, base stations, and UEs. For the sake of simplicity in this disclosure, only references will be included in this section. Figure 12 The diagram shows the method. In step 710, the host provides user data. In an optional sub-step (not shown), the host provides user data by executing a host application. In step 720, the host initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may pass through a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0205] Figure 13 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 9 and Figure 10 The described hosts, base stations, and UEs. For the sake of simplicity in this disclosure, only references will be included in this section. Figure 13 The diagram shows the steps. In step 810 (which may be optional), the UE receives input data provided by the host. Alternatively, in step 820, the UE provides user data. In sub-step 821 of step 820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step 810 (which may be optional), the UE executes a client application that provides user data as a response to the received input data provided by the host. 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 the transmission of user data to the host in sub-step 830 (which may be optional). In step 840 of the method, the host receives user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0206] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system may include, as referenced... Figure 9 and Figure 10 The described hosts, base stations, and UEs. For the sake of simplicity in this disclosure, only references will be included in this section. Figure 14 The diagram shows the steps. In step 910 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host. In step 930 (which may be optional), the host receives the user data carried in the transmission initiated by the base station.

[0207] Figure 15A method 1000 performed by a wireless device 110 according to certain embodiments is described. At step 1002, the wireless device receives configuration information from a network node 160. The configuration information enables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first group of HARQ procedures. Each of the first group of HARQ procedures is identified by a corresponding number in the first group of HARQ procedures. The configuration information also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second group of HARQ procedures. Each of the second group of HARQ procedures is identified by a corresponding number in the second group of HARQ procedures. At step 1004, the wireless device 110 constructs a first HARQ codebook of a first type based on the first group of HARQ procedure numbers for which HARQ ACK and / or HARQ NACK feedback is enabled in the first group of HARQ procedures. At step 1006, the wireless device 110 sends HARQ ACK and / or HARQ NACK feedback based on the first HARQ codebook to the network node 160.

[0208] In a particular embodiment, the first HARQ codebook of the first type is not constructed based on a second set of HARQ procedures that disable HARQ ACK and / or HARQ NACK feedback.

[0209] In a particular embodiment, the first HARQ codebook includes a type 3 HARQ codebook, and the wireless device 110 receives a DCI that triggers type 3 HARQ feedback.

[0210] In another specific embodiment, a type 3 HARQ codebook is used in conjunction with a type 1 HARQ codebook.

[0211] In a particular embodiment, PDSCH reception corresponding to a specific HARQ procedure for which HARQ feedback is enabled is scheduled using an indication of an inapplicable value in the PDSCH-to-HARQ_feedback timing indicator field in the DCI that triggers HARQ ACK and / or HARQ NACK feedback. HARQ ACK and / or HARQ NACK feedback for the specific HARQ procedure is then obtained by triggering feedback for the type 3 HARQ codebook.

[0212] In a particular embodiment, based on the DCI that triggers HARQ ACK and / or HARQ NACK feedback, the wireless device 110 determines the transmission resources for sending HARQ ACK and / or HARQ NACK feedback. The transmission resources are then used to send the HARQ ACK and / or HARQ NACK feedback to the network node.

[0213] In another specific embodiment, the resources include PUCCH resources for sending HARQ ACK and / or HARQ NACK feedback, and the PUCCH resources are determined based on the PUCCH resource indicator field in the DCI that triggers the HARQ feedback.

[0214] Figure 16 This describes the wireless network (e.g.) Figure 4 A schematic block diagram of a virtual device 1100 in a wireless network (shown in the diagram). This can be implemented in wireless devices or network nodes (e.g., Figure 4 The device is implemented in the wireless device 110 or network node 160 shown. Device 1100 is operable to perform reference... Figure 15 The example methods described herein, as well as any other processes or methods disclosed herein, are also included. It should also be understood that these processes are not necessarily performed solely by device 1100. Figure 15 The method. At least some of the operations of the method can be performed by one or more other entities.

[0215] The virtual device 1100 may include processing circuitry, which may include one or more microprocessors or microcontrollers and other digital hardware, including digital signal processors (DSPs), dedicated digital logic, etc. The processing circuitry may be configured to execute program code stored in 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 some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving module 1110, the constructing module 1120, the transmitting module 1130, and any other suitable unit of the device 1100 to perform corresponding functions according to one or more embodiments of this disclosure.

[0216] According to some embodiments, the receiving module 1110 may perform certain receiving functions of the receiving function of the device 1100. For example, the receiving module 1110 may receive configuration information from the network node 160. The configuration information enables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first group of HARQ procedures. Each of the first group of HARQ procedures is identified by a corresponding number in the first group of HARQ procedures. The configuration information also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second group of HARQ procedures. Each of the second group of HARQ procedures is identified by a corresponding number in the second group of HARQ procedures.

[0217] According to some embodiments, the construction module 1120 may perform certain construction functions in the construction functions of the device 1100. For example, the construction module 1120 may construct a first HARQ codebook of a first type based on a first set of HARQ process numbers for a first set of HARQ processes that enable HARQ ACK and / or HARQ NACK feedback.

[0218] According to some embodiments, the transmitting module 1130 may perform certain transmitting functions of the transmitting function of the device 1100. For example, the transmitting module 1130 may transmit HARQ ACK and / or HARQ NACK feedback based on a first HARQ codebook to a network node.

[0219] As used herein, the term module may have the conventional meaning in the field of electronic devices, electrical apparatus and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, units, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., as such as those described herein.

[0220] Figure 17 A method 1200 performed by network node 160 according to certain embodiments is described. At step 1202, network node 160 transmits configuration information to wireless device 110. The configuration information enables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first group of HARQ procedures. Each of the first group of HARQ procedures is identified by a corresponding number in the first group of HARQ procedures. The configuration also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second group of HARQ procedures. Each of the second group of HARQ procedures is identified by a corresponding number in the second group of HARQ procedures. At step 1204, network node 160 receives HARQ ACK and / or HARQ NACK feedback from wireless device 110 based on a first HARQ codebook. The first HARQ codebook belongs to a first type and is constructed based on the first group of HARQ procedures for which HARQ ACK and / or HARQ NACK feedback is enabled.

[0221] In a particular embodiment, the first HARQ codebook of the first type is not constructed based on a second set of HARQ procedures that disable HARQ ACK and / or HARQ NACK feedback.

[0222] In a particular embodiment, the first HARQ codebook is a type 3 HARQ codebook, and network node 160 transmits a DCI that triggers type 3 HARQ feedback.

[0223] In another specific embodiment, a type 3 HARQ codebook is used in conjunction with a type 1 HARQ codebook, and PDSCH reception corresponding to a specific HARQ procedure for which HARQ feedback is enabled is scheduled using an indication of an inapplicable value in the PDSCH-to-HARQ_feedback timing indicator field in the DCI that triggers HARQ ACK and / or HARQ NACK feedback. HARQ ACK and / or HARQ NACK feedback for the specific HARQ procedure is then obtained by triggering feedback for the type 3 HARQ codebook.

[0224] In a particular embodiment, network node 160 transmits a DCI that triggers HARQ ACK and / or HARQ NACK feedback to wireless device 110. The DCI indicates the transmission resources used to send HARQ ACK and / or HARQ NACK feedback, and uses the transmission resources to receive HARQ ACK and / or HARQ NACK feedback from the wireless device.

[0225] In a particular embodiment, the resources include PUCCH resources for transmitting HARQ ACK and / or HARQ NACK feedback by the wireless device, and the PUCCH resources are indicated based on the PUCCH resource indicator field in the DCI that triggers the HARQ feedback.

[0226] Figure 18 This describes the wireless network (e.g.) Figure 4 A schematic block diagram of a virtual device 1300 in a wireless network (shown in the diagram). This can be implemented in wireless devices or network nodes (e.g., Figure 4 The device is implemented in the wireless device 110 or network node 160 shown. Device 1300 is operable to perform reference... Figure 17 The example methods described herein, as well as any other processes or methods disclosed herein, are also included. It should also be understood that these processes are not necessarily performed solely by device 1300. Figure 17 The method. At least some of the operations of the method can be performed by one or more other entities.

[0227] The virtual device 1300 may include processing circuitry, which may include one or more microprocessors or microcontrollers and other digital hardware, including digital signal processors (DSPs), dedicated digital logic, etc. The processing circuitry may be configured to execute program code stored in 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 some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the transmission module 1310, the receiving module 1320, and any other suitable unit of the device 1300 to perform corresponding functions according to one or more embodiments of this disclosure.

[0228] According to some embodiments, the transmission module 1310 may perform certain transmission functions of the transmission functions of the device 1300. For example, the transmission module 1310 may transmit configuration information to the wireless device 110. The configuration information enables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a first group of HARQ procedures. Each of the first group of HARQ procedures is identified by a corresponding number in the first group of HARQ procedures. The configuration also disables HARQ ACK and / or HARQ NACK feedback on a per-HARQ basis for a second group of HARQ procedures. Each of the second group of HARQ procedures is identified by a corresponding number in the second group of HARQ procedures.

[0229] According to some embodiments, the receiving module 1320 may perform certain receiving functions of the receiving function of the device 1300. For example, the receiving module 1320 may receive HARQ ACK and / or HARQ NACK feedback based on a first HARQ codebook from the wireless device 110. The first HARQ codebook belongs to a first type and is constructed based on a first set of HARQ process numbers of a first set of HARQ processes that enable HARQ ACK and / or HARQ NACK feedback for it.

[0230] Example Implementation

[0231] Example 1: A method performed by a wireless device, the method comprising one or more of the following steps: receiving configuration information from a network node, the configuration information comprising: an indication to disable hybrid automatic repeat request acknowledgment and / or negative acknowledgment (HARQ ACK and / or NACK) feedback on a per hybrid automatic repeat request (HARQ) basis for a first group of HARQ procedures that disable HARQ ACK and / or NACK feedback; identifying each of a first subgroup of HARQ procedures by a corresponding one of the first group of HARQ procedure numbers; constructing a first type of first HARQ codebook based on the first group of HARQ procedure numbers for which HARQ ACK and / or NACK feedback is enabled; and sending HARQ ACK and / or NACK feedback based on the first HARQ codebook to the network node.

[0232] Example 2: The method as described in Example 1, wherein the first HARQ codebook includes a type 3 HARQ codebook, and the method further includes receiving downlink control information (DCI) that triggers type 3 HARQ feedback.

[0233] Example 3: The method as described in Example 2, wherein: a type 3 HARQ codebook is used in conjunction with a type 1 HARQ codebook; and PDSCH reception corresponding to a specific HARQ procedure for which HARQ feedback is enabled is scheduled using an indication of an inapplicable value in the PDSCH-to-HARQ_feedback timing indicator field in the DCI that triggers HARQ ACK and / or NACK feedback; and HARQ ACK and / or NACK feedback for the specific HARQ procedure is subsequently obtained by triggering feedback for the type 3 HARQ codebook.

[0234] Example 4: The method as described in any of Examples 1 to 3, wherein the configuration information includes enabling HARQ ACK and / or NACK feedback on a per-HARQ basis in a second set of HARQ procedures, and each of the second subgroup HARQ procedures is identified by a corresponding one of the second set of HARQ procedure numbers.

[0235] Example 5: The method as described in any of Examples 1 to 4 further includes: determining transmission resources for sending HARQACK and / or NACK feedback based on downlink control information (DCI) that triggers HARQACK and / or NACK feedback, and wherein the transmission resources are used to send HARQ ACK and / or NACK feedback to the network node.

[0236] Example 6: The method as described in Example 5, wherein: the resources include PUCCH resources for sending HARQ ACK and / or NACK feedback, and the PUCCH resources are determined based on the PUCCH resource indicator field in the DCI that triggers the HARQ feedback.

[0237] Example 7: A method performed by a wireless device for providing HARQ feedback using a Type 1 Hybrid Automatic Repeat Request (HARQ) codebook, the method comprising: determining that a HARQ procedure associated with a HARQ procedure identifier is enabled; receiving an indication to schedule PDSCH reception corresponding to the HARQ procedure using an inapplicable value of a PDSCH-to-HARQ_feedback timing indicator field in a DCI message; and discarding HARQ feedback for the PDSCH, thereby disabling HARQ feedback for the PDSCH reception.

[0238] Example 8: The method as described in Example 7, wherein determining that a HARQ procedure associated with a HARQ procedure identifier is enabled includes: receiving a message from a network node including a HARQ procedure identifier, the message indicating that a HARQ procedure associated with the HARQ procedure identifier is enabled.

[0239] Example 9: A method performed by a wireless device for providing HARQ feedback using a Type 2 Hybrid Automatic Repeat Request (HARQ) codebook, the method comprising: receiving a DCI message including a DAI field; interpreting the DAI field in the DCI message of a PDSCH corresponding to a scheduled or disabled HARQ procedure as the current true DAI value when the PDSCH-to-HARQ_feedback timing indicator field in the DCI message indicates an applicable value; and ignoring the DAI field in the DCI message of a PDSCH corresponding to a scheduled or disabled HARQ procedure when the PDSCH-to-HARQ_feedback timing indicator field in the DCI message indicates an inapplicable value (-1 in the parameter dl-DataToUL-ACK configured by a higher layer via RRC signaling).

[0240] Example 10: A method by a wireless device for providing HARQ feedback using a type 2 Hybrid Automatic Repeat Request (HARQ) codebook, the method comprising: obtaining information for scheduling the wireless device for PDSCH reception corresponding to at least one HARQ procedure using DCI format 1_1 when HARQ feedback is enabled; obtaining information for scheduling the wireless device for PDSCH reception corresponding to at least one HARQ procedure using DCI format 1_2 when HARQ feedback is disabled; and discarding HARQ feedback for any PDSCH scheduled using DCI format 1_2, wherein the HARQ procedure number, DAI, and RV fields are configured by a higher layer to have 0 bits in DCI format 1_2.

[0241] Example 11: A method performed by a wireless device for providing HARQ feedback using a Type 1 HARQ codebook, the method comprising: determining, when HARQ feedback is enabled, to schedule the wireless device using DCI format 1_1 for a PDSCH reception corresponding to at least one HARQ procedure; determining, when HARQ feedback is disabled, to schedule the wireless device using DCI format 1_2 for a PDSCH reception corresponding to at least one HARQ procedure, wherein the HARQ procedure number, DAI, and RV fields are configured by a higher layer to have 0 bits in DCI format 1_2, wherein the wireless device is configured to be scheduled using a TDRA table pdsch-TimeDomainAllocationListForDCI-Format1-2 used only for scheduling PDSCHs with disabled HARQ procedures, and wherein pdsch-TimeDomainAllocationListForDCI-Format1-2 is excluded in the Type-1 HARQ codebook construction.

[0242] Example Implementation 12: A method for constructing a Type-3 HARQ codebook in a UE, the method involving one or more of the following steps: the UE receives configuration information from the network from the gNB regarding HARQ ACK / NACK feedback enable / disable on a per-HARQ-procedure basis using a first subgroup of HARQ procedures that enables HARQ ACK / NACK feedback and a second subgroup of HARQ procedures that disables HARQ ACK / NACK feedback; the UE constructs a HARQ codebook based on the HARQ procedure number for which it enables HARQ ACK / NACK feedback; the UE determines the PUCCH resource for sending HARQ ACK / NACK feedback based on the PUCCH resource indicator field in the DCI that triggers Type-3 HARQ feedback; and feeds back HARQ ACK / NACK based on the constructed HARQ codebook.

[0243] Example 13: The method described in Example 12, wherein a type 3 HARQ codebook is used in conjunction with a type 1 HARQ codebook, and the PDSCH reception corresponding to the HARQ procedure for which HARQ feedback is enabled is scheduled using an indication of an inapplicable value in the PDSCH-to-HARQ_feedback timing indicator field in the DCI message, and then HARQ feedback for the HARQ procedure is obtained by triggering feedback for the type 3 HARQ codebook.

[0244] Example Implementation 14: A method for providing HARQ feedback using a Type 1 HARQ codebook, wherein the UE is configured with an enabled HARQ procedure number, the UE receives an indication of an inapplicable value in the PDSCH-to-HARQ_feedback timing indicator field in a DCI message to schedule a scheduling command for PDSCH reception corresponding to the HARQ procedure, the UE discards HARQ feedback for the PDSCH, thereby disabling HARQ feedback for this PDSCH reception.

[0245] Example Implementation 15: A method for providing HARQ feedback using a type 2 HARQ codebook, wherein when the PDSCH-to-HARQ_feedback timing indicator field in the DCI message indicates an applicable value, the UE interprets the DAI field in the DCI message of the PDSCH corresponding to the scheduled and disabled HARQ procedure as the current true DAI value; and when the PDSCH-to-HARQ_feedback timing indicator field in the DCI message indicates an inapplicable value (-1 in the parameter dl-DataToUL-ACK configured by a higher layer via RRC signaling), the UE ignores the DAI field in the DCI message of the PDSCH corresponding to the scheduled and disabled HARQ procedure.

[0246] Example Implementation 16: A method for providing HARQ feedback using a type 2 HARQ codebook, wherein: when HARQ feedback is enabled, the UE is scheduled using DCI format 1_1 for PDSCH reception corresponding to the HARQ procedure; when HARQ feedback is disabled, the UE is scheduled using DCI format 1_2 for PDSCH reception corresponding to the HARQ procedure; the HARQ procedure number, DAI, and RV fields are configured by a higher layer to have 0 bits in DCI format 1_2; and the UE discards HARQ feedback for any PDSCH scheduled using DCI format 1_2.

[0247] Example Implementation 17: A method for providing HARQ feedback using a Type 1 HARQ codebook, wherein: when HARQ feedback is enabled, the UE is scheduled using DCI format 1_1 for PDSCH reception corresponding to the HARQ procedure; when HARQ feedback is disabled, the UE is scheduled using DCI format 1_2 for PDSCH reception corresponding to the HARQ procedure; the HARQ procedure number, DAI, and RV fields are configured by a higher layer to have 0 bits in DCI format 1_2; the UE is configured to be scheduled using the TDRA table pdsch-TimeDomainAllocationListForDCI-Format1-2, which is only used for scheduling PDSCHs with disabled HARQ procedures; and pdsch-TimeDomainAllocationListForDCI-Format1-2 is excluded in the Type-1 HARQ codebook construction.

[0248] Example 18: A computer program including instructions that, when executed on a computer, perform any of the methods described in Examples 1 to 17.

[0249] Example 19: A computer program product comprising a computer program, the computer program including instructions that, when executed on a computer, perform any of the methods described in Examples 1 to 17.

[0250] Example 20: A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in Examples 1 to 17.

[0251] Example 21: A wireless device including processing circuitry configured to perform any of the methods described in Examples 1 to 17.

[0252] Example 22: A method performed by a network node, the method comprising one or more of the following steps: transmitting configuration information to a wireless device, the configuration information comprising: an indication to disable Hybrid Automatic Repeat Request Acknowledgment and / or Negative Acknowledgment (HARQ ACK and / or NACK) feedback on a per Hybrid Automatic Repeat Request (HARQ) basis for a first group of HARQ procedures that disable HARQ ACK and / or NACK feedback; identifying each of the first subgroup of HARQ procedures by a corresponding one of the first group of HARQ procedure numbers; and receiving HARQ ACK and / or NACK feedback from the wireless device based on a first HARQ codebook, wherein the first HARQ codebook belongs to a first type and is constructed based on the first group of HARQ procedure numbers for which HARQ ACK and / or NACK feedback is enabled.

[0253] Example 23: The method as described in Example 22, wherein the first HARQ codebook includes a type 3 HARQ codebook, and the method further includes receiving downlink control information (DCI) that triggers type 3 HARQ feedback.

[0254] Example 24: The method as described in Example 23, wherein: a type 3 HARQ codebook is used in conjunction with a type 1 HARQ codebook; and PDSCH reception corresponding to a specific HARQ procedure for which HARQ feedback is enabled is scheduled using an indication of an inapplicable value in the PDSCH-to-HARQ_feedback timing indicator field in the DCI that triggers HARQ ACK and / or NACK feedback; and HARQ ACK and / or NACK feedback for the specific HARQ procedure is subsequently obtained by triggering feedback for the type 3 HARQ codebook.

[0255] Example 25: The method as described in any of Examples 22 to 24, wherein the configuration information includes enabling HARQ ACK and / or NACK feedback on a per-HARQ basis in a second set of HARQ procedures, each in the second sub-group of HARQ procedures being identified by a corresponding one of the second set of HARQ procedure numbers.

[0256] Example 26: The method as described in any of Examples 22 to 25 further includes: transmitting downlink control information (DCI) that triggers HARQACK and / or NACK feedback to the wireless device, the DCI indicating transmission resources for sending HARQ ACK and / or NACK feedback, and wherein the transmission resources are used to receive HARQACK and / or NACK feedback from the wireless device.

[0257] Example 27: The method as described in Example 26, wherein: the resources include PUCCH resources for transmitting HARQACK and / or NACK feedback by the wireless device, and the PUCCH resources are indicated based on the PUCCH resource indicator field in the DCI that triggers the HARQ feedback.

[0258] Example 28: A method by a network node for receiving HARQ feedback using a Type 1 Hybrid Automatic Repeat Request (HARQ) codebook, the method comprising: transmitting a message indicating that a HARQ procedure associated with a HARQ procedure identifier is enabled to a radio device; transmitting a scheduling command indicating that the PDSCH received corresponding to the HARQ procedure is scheduled to be received using an inapplicable value of a PDSCH-to-HARQ_feedback timing indicator field in a DCI message to the radio device; and configuring the radio device to discard HARQ feedback for the PDSCH, such that HARQ feedback received for the PDSCH is disabled.

[0259] Example 29: A method by a network node for receiving HARQ feedback using a type 2 Hybrid Automatic Repeat Request (HARQ) codebook, the method comprising: configuring a radio device to interpret the DAI field in a DCI message corresponding to a scheduled or disabled HARQ procedure as the current true DAI value when the PDSCH-to-HARQ_feedback timing indicator field in the DCI message indicates an applicable value; configuring the radio device to ignore the DAI field in a DCI message corresponding to a scheduled or disabled HARQ procedure when the PDSCH-to-HARQ_feedback timing indicator field in the DCI message indicates an inapplicable value (-1 in the parameter dl-DataToUL-ACK configured by a higher layer via RRC signaling); and transmitting a DCI message including the DAI field to the radio device.

[0260] Example 30: A method by a network node for receiving HARQ feedback using a type 2 Hybrid Automatic Repeat Request (HARQ) codebook, the method comprising: scheduling information transmission of a wireless device to a wireless device for receiving a PDSCH corresponding to at least one HARQ procedure using DCI format 1_1 when HARQ feedback is enabled; scheduling information transmission of a wireless device to a wireless device for receiving a PDSCH corresponding to at least one HARQ procedure using DCI format 1_2 when HARQ feedback is disabled; and configuring the wireless device to discard HARQ feedback for any PDSCH scheduled using DCI format 1_2, wherein the HARQ procedure number, DAI, and RV fields are configured by a higher layer to have 0 bits in DCI format 1_2.

[0261] Example 31: A method by a wireless device for providing HARQ feedback using a Type 1 HARQ codebook, the method comprising: scheduling the wireless device using DCI format 1_1 for PDSCH reception corresponding to at least one HARQ procedure when HARQ feedback is enabled; and scheduling the wireless device using DCI format 1_2 for PDSCH reception corresponding to at least one HARQ procedure when HARQ feedback is disabled, wherein the HARQ procedure number, DAI, and RV fields are configured by a higher layer to have 0 bits in DCI format 1_2, wherein the wireless device is configured to be scheduled using a TDRA table pdsch-TimeDomainAllocationListForDCI-Format1-2 used only for scheduling PDSCHs with disabled HARQ procedures, and wherein pdsch-TimeDomainAllocationListForDCI-Format1-2 is excluded in the Type-1 HARQ codebook construction.

[0262] Example 32: A computer program including instructions that, when executed on a computer, perform any of the methods described in Examples 22 to 31.

[0263] Example 33: A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform any of the methods described in Examples 22 to 31.

[0264] Example 34: A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods described in Examples 22 to 31.

[0265] Example 35: A wireless device including processing circuitry configured to perform any of the methods described in Examples 22 to 31.

[0266] Example 36: A wireless device includes: a processing circuit configured to perform any step of any of the steps in any of the example embodiments of Example 1 to 21; and a power supply circuit configured to supply power to the wireless device.

[0267] Example 37: A network node includes: processing circuitry configured to perform any step of any of the steps in any of the example embodiments of Example 22 to 35; and power supply circuitry configured to power a wireless device.

[0268] Example 38: A wireless device comprising: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and connected to a processing circuit and configured to regulate signals transmitted between the antenna and the processing circuit; the processing circuit configured to perform any step of any of the steps in any of the example embodiments of Example 1 to 21; an input interface connected to the processing circuit and configured to allow information to be processed by the processing circuit to be input into the wireless device; an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the wireless device; and a battery connected to the processing circuit and configured to power the wireless device.

[0269] Example 39: A communication system including a host, the host comprising: processing circuitry configured to provide user data; and

[0270] A communication interface configured to forward user data to a cellular network for transmission to a wireless device, wherein the cellular network includes network nodes having a radio interface and processing circuitry, the processing circuitry of the network nodes being configured to perform any of the steps in any of the example embodiments as described in Example Embodiments 22 to 35.

[0271] Example 40: The communication system as described in the preceding embodiments further includes network nodes.

[0272] Example 41: The communication system as described in the preceding two embodiments further includes a wireless device configured to communicate with a network node.

[0273] Example 42: A communication system as described in the preceding three embodiments, wherein: the host's processing circuitry is configured to execute a host application to provide user data; and the wireless device includes processing circuitry configured to execute a client application associated with the host application.

[0274] Example 43: A method implemented in a communication system, the communication system including a host, a network node, and a wireless device, the method comprising: providing user data at the host; and initiating a transmission carrying the user data from the host to the wireless device via a cellular network including the network node, wherein the network node performs any step of any of the steps in any of the example embodiments of Example 22 to 35.

[0275] Example 44: The method described in the preceding embodiments further includes: transmitting user data at a network node.

[0276] Example 45: The method described in the preceding two embodiments, wherein user data is provided at the host by executing a host application, the method further comprising executing a client application associated with the host application at a wireless device.

[0277] Example 46: A wireless device configured to communicate with a network node, the wireless device including a radio interface and processing circuitry configured to perform the methods of the preceding three embodiments.

[0278] Example 47: A communication system includes a host, the host including: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a wireless device; wherein the wireless device includes a radio interface and processing circuitry, and components of the wireless device are configured to perform any step of any of the steps in any of the example embodiments as described in Example 1 to 21.

[0279] Example 48: A communication system as described in the preceding embodiments, wherein the cellular network further includes network nodes configured to communicate with wireless devices.

[0280] Example 49: A communication system as described in the preceding two embodiments, wherein: the host's processing circuitry is configured to execute a host application to provide user data; and the wireless device's processing circuitry is configured to execute a client application associated with the host application.

[0281] Example 50: A method implemented in a communication system, the communication system including a host, a network node, and a wireless device, the method comprising: providing user data at the host; and initiating a transmission carrying the user data from the host to the wireless device via a cellular network including the network node, wherein the wireless device performs any step as in any of the example embodiments of Example 1 to 21.

[0282] Example 51: The method described in the preceding embodiments further includes receiving user data from a network node at the wireless device.

[0283] Example 52: A communication system comprising a host, the host including: a communication interface configured to receive user data originating from a wireless device transmitted to a network node; wherein the wireless device includes a radio interface and processing circuitry, the processing circuitry of the wireless device being configured to perform any step of any of the steps in any of the example embodiments as described in Example 1 to 21.

[0284] Example 53: The communication system as described in the preceding embodiments further includes a wireless device.

[0285] Example 54: The communication system described in the preceding two embodiments further includes a network node, wherein the network node includes a radio interface configured to communicate with a wireless device and a communication interface configured to forward user data carried by transmissions from the wireless device to the network node to a host.

[0286] Example 55: A communication system as described in the preceding three embodiments, wherein: the host's processing circuitry is configured to execute a host application; and the wireless device's processing circuitry is configured to execute a client application associated with the host application, thereby providing user data.

[0287] Example 56: A communication system as described in the preceding four embodiments, wherein: the host's processing circuitry is configured to execute a host application to provide requested data; and the wireless device's processing circuitry is configured to execute a client application associated with the host application to provide user data in response to the requested data.

[0288] Example 57: A method implemented in a communication system, the communication system including a host, a network node, and a wireless device, the method comprising: receiving user data transmitted from the wireless device to the network node at the host, wherein the wireless device performs any step as in any of the example embodiments of Example 1 to 21.

[0289] Example 58: The method described in the preceding embodiments further includes providing user data to the network node at the wireless device.

[0290] Example 59: The method described in the preceding two embodiments further includes: executing a client application at a wireless device to provide user data to be transmitted; and executing a host application associated with the client application at a host.

[0291] Example 60: The method described in the preceding three embodiments further includes: executing a client application at a wireless device; and receiving input data from the client application at the wireless device, and providing the input data at a host by executing a host application associated with the client application; wherein user data to be transmitted is provided by the client application in response to the input data.

[0292] Example 61: A communication system including a host, the host including a communication interface configured to receive user data transmitted from a wireless device to a network node, wherein the network node includes a radio interface and processing circuitry configured to perform any step of any of the steps in any of the example embodiments of Example 22 to 35.

[0293] Example 62: The communication system as described in the preceding embodiments further includes network nodes.

[0294] Example 63: The communication system as described in the preceding two embodiments further includes a wireless device configured to communicate with a network node.

[0295] Example 64: A communication system as described in the preceding three embodiments, wherein: the host's processing circuitry is configured to execute a host application; and the wireless device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host.

[0296] Example 65: A method implemented in a communication system, the communication system including a host, a network node, and a wireless device, the method comprising: receiving, at the host, user data transmitted from a base station originating from the network node and already received from the wireless device, wherein the wireless device performs any step as in any of the steps of any of the example embodiments of Example 1 to 21.

[0297] Example 66: The method described in the preceding embodiments further includes receiving user data from a wireless device at a network node.

[0298] Example 67: The method described in the preceding two embodiments further includes initiating the transmission of received user data to the host at the network node.

[0299] Example 68: The method described in any of the preceding embodiments, wherein the network node includes a base station.

[0300] Example 69: The method described in any of the preceding embodiments, wherein the wireless device includes a user equipment (UE).

[0301] Modifications, additions, or omissions may be made to the systems and devices described herein without departing from the scope of disclosure. Components of the systems and devices may be integrated or separate. Furthermore, the operation of the systems and devices may be performed by more, fewer, or other components. Additionally, any suitable logic, including software, hardware, and / or other logic, may be used to perform the operation of the systems and devices. As used in this document, “each” means each member of a set or each member of a subset of a set.

[0302] The methods described herein may be modified, added to, or omitted without departing from the scope of disclosure. Methods may include more, fewer, or other steps. Furthermore, the steps may be performed in any suitable order.

[0303] Although this disclosure has been described with reference to certain embodiments, variations and substitutions of the embodiments will be apparent to those skilled in the art. Therefore, the above description of the embodiments does not limit this disclosure. Other changes, substitutions, and modifications are possible without departing from the spirit and scope of this disclosure.

Claims

1. A method by a wireless device, comprising: receiving configuration information from a network node, wherein the configuration information configures the wireless device to provide feedback for all HARQ processes at once across all activated cells, and includes an indication that: HARQ-ACK and / or HARQ-NACK feedback is enabled on a per-HARQ basis for a first set of hybrid automatic repeat request, HARQ, processes, each of the first set of HARQ processes is identified by a respective one of a first set of HARQ process numbers, and HARQ-ACK and / or HARQ-NACK feedback is disabled on a per-HARQ process basis for a second set of HARQ processes, each of the second set of HARQ processes is identified by a respective one of a second set of HARQ process numbers; constructing a type 3 HARQ codebook based on the first set of HARQ process numbers for the first set of HARQ processes for which HARQ-ACK and / or HARQ-NACK feedback is enabled, wherein the type 3 HARQ codebook is not constructed based on the second set of HARQ processes for which HARQ-ACK and / or HARQ-NACK feedback is disabled; sending HARQ-ACK and / or HARQ-NACK feedback based on the type 3 HARQ codebook to the network node.

2. The method of claim 1, wherein, The method further comprises receiving a downlink control information, DCI, triggering type 3 HARQ feedback.

3. The method of claim 2, wherein: the type 3 HARQ codebook is used together with a type 1 HARQ codebook; and Utilizing the DCI that triggers the HARQ ACK and / or HARQ NACK feedback PDSCH-to-HARQ_feedback The timing indicator field indicates an inapplicable value to schedule the physical downlink shared channel (PDSCH) reception corresponding to the specific HARQ procedure for which HARQ feedback is enabled; and HARQ-ACK and / or HARQ-NACK feedback for the particular HARQ process is obtained by subsequently triggering feedback for the type 3 HARQ codebook.

4. The method of any of claims 1 to 3, further comprising: determining a transmission resource for sending the HARQ-ACK and / or HARQ-NACK feedback based on the DCI triggering the HARQ-ACK and / or HARQ-NACK feedback, and wherein the HARQ-ACK and / or HARQ-NACK feedback is sent to the network node using the transmission resource.

5. The method of claim 4, wherein: the resource comprises a physical uplink control channel, PUCCH, resource for sending the HARQ-ACK and / or HARQ-NACK feedback, and the PUCCH resource is determined based on a PUCCH resource indicator field in the DCI triggering the HARQ feedback.

6. A computer program product comprising a computer program which comprises instructions which, when executed on a computer, perform any of the methods of claims 1 to 5.

7. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods of claims 1-5.

8. A method by a network node, comprising: transmitting configuration information to a wireless device, wherein the configuration information configures the wireless device to provide feedback for all hybrid automatic repeat request (HARQ) processes at once across all activated cells and includes an indication that: a first set of HARQ processes are enabled for per-HARQ feedback of hybrid automatic repeat request acknowledgement (HARQ-ACK) and / or negative acknowledgement (HARQ-NACK) feedback, each of the first set of HARQ processes is identified by a respective one of a first set of HARQ process numbers, and a second set of HARQ processes are disabled for per-HARQ process feedback of HARQ-ACK and / or HARQ-NACK feedback, each of the second set of HARQ processes is identified by a respective one of a second set of HARQ process numbers; and receiving, from the wireless device, HARQ-ACK and / or HARQ-NACK feedback based on a type 3 HARQ codebook, wherein the type 3 HARQ codebook is constructed based on the first set of HARQ process numbers for the first set of HARQ processes for which HARQ-ACK and / or HARQ-NACK feedback is enabled, and wherein the type 3 HARQ codebook is not constructed based on the second set of HARQ processes for which HARQ-ACK and / or HARQ-NACK feedback is disabled.

9. The method of claim 8, wherein, the method further comprising transmitting a downlink control information (DCI) that triggers type 3 HARQ feedback.

10. The method of claim 9, wherein: the type 3 HARQ codebook is used together with a type 1 HARQ codebook; and Utilizing the DCI that triggers the HARQ ACK and / or HARQ NACK feedback PDSCH-to-HARQ_feedback The timing indicator field indicates an inapplicable value to schedule the physical downlink shared channel (PDSCH) reception corresponding to the specific HARQ procedure for which HARQ feedback is enabled; and HARQ-ACK and / or HARQ-NACK feedback for the particular HARQ process is obtained by subsequently triggering feedback for the type 3 HARQ codebook.

11. The method of any of claims 8-10, further comprising: transmitting, to the wireless device, a DCI that triggers the HARQ-ACK and / or HARQ-NACK feedback, the DCI indicating transmission resources for sending the HARQ-ACK and / or HARQ-NACK feedback, and wherein the HARQ-ACK and / or HARQ-NACK feedback is received from the wireless device using the transmission resources.

12. The method of claim 11, wherein: the resources include a physical uplink control channel (PUCCH) resource for sending the HARQ-ACK and / or HARQ-NACK feedback by the wireless device, and the PUCCH resource is indicated based on a PUCCH resource indicator field in the DCI that triggers the HARQ feedback.

13. A computer program product comprising a computer program which comprises instructions which, when executed on a computer, perform any of the methods of claims 8 to 12.

14. A non-transitory computer-readable medium storing instructions which, when executed by a computer, perform any of the methods of claims 8 to 12.

15. A wireless device comprising: a processor; and a memory storing instructions which, when executed by the processor, cause the wireless device to be adapted to: receive, from a network node, configuration information, wherein the configuration information configures the wireless device to provide feedback for all hybrid automatic repeat request, HARQ, processes at one time across all activated cells, and comprises an indication that: HARQ acknowledgement, HARQ ACK, and / or negative acknowledgement, HARQ NACK, feedback is enabled on a per-HARQ basis for a first set of HARQ processes, each of the first set of HARQ processes being identified by a respective one of a first set of HARQ process numbers, and HARQ ACK and / or HARQ NACK feedback is disabled on a per-HARQ process basis for a second set of HARQ processes, each of the second set of HARQ processes being identified by a respective one of a second set of HARQ process numbers; for the first set of HARQ processes for which HARQ ACK and / or HARQ NACK feedback is enabled, construct a type 3 HARQ codebook based on the first set of HARQ process numbers, wherein the type 3 HARQ codebook is not constructed based on the second set of HARQ processes for which HARQ ACK and / or HARQ NACK feedback is disabled; send HARQ ACK and / or HARQ NACK feedback based on the type 3 HARQ codebook to the network node. the instructions, when executed by the processor, cause the wireless device to be further adapted to receive a downlink control information, DCI, triggering type 3 HARQ feedback.

16. The wireless device of claim 15, wherein, 17. The wireless device of claim 16, wherein: the type 3 HARQ codebook is used together with a type 1 HARQ codebook; and PDSCH-to-HARQ_feedback Utilizing the DCI that triggers the HARQ ACK and / or HARQ NACK feedback and The timing indicator field indicates an inapplicable value to schedule the physical downlink shared channel (PDSCH) reception corresponding to the specific HARQ procedure for which HARQ feedback is enabled; HARQ ACK and / or HARQ NACK feedback for the particular HARQ process is obtained by subsequently triggering feedback for the type 3 HARQ codebook. the instructions, when executed by the processor, cause the wireless device to be adapted to:

18. The wireless device of any one of claims 15 to 17, wherein, determine, based on a DCI triggering HARQ ACK and / or HARQ NACK feedback, a transmission resource for sending the HARQ ACK and / or HARQ NACK feedback, and wherein the HARQ ACK and / or HARQ NACK feedback is sent to the network node using the transmission resource.

19. The wireless device of claim 18, wherein: ​ The resources include a physical uplink control channel, PUCCH, a resource for transmitting the HARQ ACK and / or HARQ NACK feedback, and determining the PUCCH resources based on a PUCCH resource indicator field in the DCI triggering the HARQ feedback.

20. A network node, comprising: processing circuitry; and a device readable medium storing instructions that, when executed by the processing circuitry, adapt the network node to: transmit configuration information to a wireless device, wherein the configuration information configures the wireless device to provide feedback for all HARQ processes at one time across all activated cells and includes an indication that: a first set of hybrid automatic repeat request, HARQ, processes are enabled for per-HARQ feedback, each of the first set of HARQ processes identified by a respective one of a first set of HARQ process numbers, and a second set of HARQ processes are disabled for per-HARQ process feedback, each of the second set of HARQ processes identified by a respective one of a second set of HARQ process numbers; and receive, from the wireless device, HARQ ACK and / or HARQ NACK feedback based on a type 3 HARQ codebook, wherein the type 3 HARQ codebook is constructed based on the first set of HARQ process numbers for the first set of HARQ processes for which HARQ ACK and / or HARQ NACK feedback is enabled, and wherein the type 3 HARQ codebook is not constructed based on the second set of HARQ processes for which HARQ ACK and / or HARQ NACK feedback is disabled.

21. The network node of claim 20, wherein, The instructions, when executed by the processing circuitry, further adapt the network node to transmit downlink control information, DCI, triggering type 3 HARQ feedback.

22. The network node of claim 21, wherein: the type 3 HARQ codebook is used with a type 1 HARQ codebook; and Utilizing the DCI that triggers the HARQ ACK and / or HARQ NACK feedback PDSCH-to-HARQ_feedback The timing indicator field indicates an inapplicable value to schedule the physical downlink shared channel (PDSCH) reception corresponding to the specific HARQ procedure for which HARQ feedback is enabled; and HARQ ACK and / or HARQ NACK feedback for the particular HARQ process is obtained by subsequently triggering feedback for the type 3 HARQ codebook.

23. The network node of any of claims 20 to 22, wherein, The instructions, when executed by the processing circuitry, adapt the network node to: transmit, to the wireless device, DCI triggering the HARQ ACK and / or HARQ NACK feedback, the DCI indicating transmission resources for transmitting the HARQ ACK and / or HARQ NACK feedback, and wherein the HARQ ACK and / or HARQ NACK feedback is received from the wireless device using the transmission resources.

24. The network node of claim 23, wherein: The resources include a physical uplink control channel, PUCCH, resources for transmitting, by the wireless device, the HARQ ACK and / or HARQ NACK feedback, and The PUCCH resources are indicated based on a PUCCH resource indicator field in the DCI triggering the HARQ feedback.

Images