System and method for joint HARQ feedback for PDSCH transmission over multiple TRPs

Abstract

To provide systems and methods for joint HARQ feedback for PDSCH transmission over multiple TRPs.SOLUTION: A method performed by a wireless device for enabling transmission feedback includes: receiving 1302 a first TB (Transport Block) and a second TB; and determining 1304 the first TB and the second TB on the basis of, a Control Resource Set (CORESET) group identifier of a CORESET over which corresponding DCI (Downlink Control Information) scheduling the TB is received. In this way, a NR (New Radio) Release 15 procedure for type 1 HARQ codebook construction can be reused without increasing or with minimum increase of HARQ feedback overhead with a semi-static HARQ-ACK codebook.SELECTED DRAWING: Figure 13A

Description

[Technical Field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application No. 62 / 866,408, filed June 26, 2019, the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates to hybrid automatic repeat request (HARQ) feedback. [Background technology]

[0003] New Radio (NR) uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in both the downlink (i.e., from a network node, new radio base station (gNB), or base station to a user equipment (UE)) and the uplink (i.e., from a UE to a gNB). Discrete Fourier transform (DFT) spread OFDM is also supported in the uplink. In the time domain, the NR downlink and uplink are organized into equal-sized subframes of 1 ms each. The subframes are further divided into multiple slots, each of equal duration. The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf = 15 kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

[0004] Data scheduling in NR is typically slot-wise. Figure 1 shows an example of a 14-symbol slot. The first two symbols contain the Physical Downlink Control Channel (PDCCH), and the rest contain the Physical Shared Data Channel, which can be either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0005] NR supports various subcarrier spacings (also called numerologies). The supported subcarrier spacings are given by Δf = (15 × 2^μ) kHz (μ∈0,1,2,3,4), where Δf = 15 kHz is the basic subcarrier spacing. The slot duration at various subcarrier spacings is 1 / 2 μ is given by ms.

[0006] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. RBs are numbered starting with 0 at one end of the system bandwidth. The basic NR physical time-frequency resource grid is shown in Figure 2, where only one resource block (RB) in a 14-symbol slot is shown. One OFDM subcarrier in one OFDM symbol interval forms one resource element (RE).

[0007] Downlink transmissions are dynamically scheduled, i.e., in each slot, the gNB transmits downlink control information (DCI) on the PDCCH indicating where UE data should be sent and in which RBs within the current downlink slot the data should be transmitted. UE data is carried on the PDSCH.

[0008] For PDSCH scheduling in NR, two DCI formats, DCI format 1_0 and DCI format 1_1, are defined. DCI format 1_0 has a smaller size than DCI format 1_1 and can be used when the UE is not fully connected to the network, while DCI format 1_1 can be used to schedule multiple-input multiple-output (MIMO) transmissions using two transport blocks (TBs).

[0009] QCL and TCI conditions: Several signals can be transmitted from different antenna ports of the same base station antenna. When received at the UE, these signals may have identical characteristics on a large scale, e.g., in terms of Doppler shift and Doppler spread, mean delay spread, or mean delay. These antenna ports are called quasi-colocated (QCL). In general, two quasi-colocated antenna ports do not necessarily have to be physically co-located.

[0010] If the UE knows that two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the UE can estimate that parameter based on one of the antenna ports and use that estimate when received from the other antenna port. Typically, the first antenna port is represented by a measurement reference signal such as a Channel State Information Reference Signal (CSI-RS) or Synchronization Signal Block (SSB) (known as the source RS), and the second antenna port is a Demodulation Reference Signal (DMRS) (known as the target RS).

[0011] For example, if antenna ports A and B are QCL in terms of average delay, the UE can estimate the average delay from the signal received from antenna port A (known as the source reference signal (RS)) and assume that the signal received from antenna port B (the target RS) has the same average delay. This is useful for demodulation because the UE can know the channel characteristics in advance when attempting to measure the channel using DMRS, which can help the UE, for example, in selecting an appropriate channel estimation filter.

[0012] Information about what assumptions can be made about the QCL is signaled to the UE by the network. NR defines four types of QCL relationships between a transmitting source RS and a transmitting target RS: ●Type A: {Doppler shift, Doppler spread, mean delay, delay spread}. ●B type: {Doppler shift, Doppler spread} ●Type C: {average delay, Doppler shift} ●Type D: {Spatial Rx parameters}

[0013] QCL Type D was introduced to facilitate beam management with analog beamforming at higher carrier frequencies (e.g., 30 GHz) and is known as a spatial QCL. Currently, there is no strict definition of a spatial QCL, but the understanding is that if two transmit antenna ports are spatially QCLs, the UE can use the same Rx beam to receive them. While most of the discussion regarding beam management has centered on QCL Type D, it should be noted that it is also necessary to communicate the QCL Type A relationship with respect to RS to the UE so that all of the relevant large-scale parameters can be estimated.

[0014] Typically, this is achieved by configuring the UE with a tracking CSI-RS (TRS) for time / frequency offset estimation. To be able to use any QCL criterion, the UE needs to receive it with a sufficiently good signal-to-interference-plus-noise ratio (SINR). In many cases, this means that the TRS must be transmitted to a particular UE on an appropriate beam.

[0015] To introduce dynamics into beam and transmit receiving point (TRP) selection, the UE may be configured through radio resource control (RRC) signaling with N transmit configuration indication (TCI) states, where N is up to 128 in frequency range 2 (FR2) and up to 8 in FR1, depending on the UE capabilities.

[0016] Each TCI state includes QCL information, i.e., one or two source downlink (DL) RSs, and each source RS is associated with a QCL type. For example, a TCI state includes a pair of reference signals, each associated with a QCL type. For example, two different CSI-RSs {CSI-RS1, CSI-RS2} are configured in a TCI state as {qcl-Type1, qcl-Type2} = {TypeA, TypeD}. This means that the UE can derive the Doppler shift, Doppler spread, mean delay, and delay spread from CSI-RS1 and the spatial Rx parameters (i.e., the RX beam to use) from CSI-RS2.

[0017] Each of the N states in the list of TCI states can be interpreted as a list of N possible beams that may be transmitted from the network, or a list of N possible TRPs that may be used by the network to communicate with the UE.

[0018] A first list of available TCI states is configured for the PDSCH, while a second list for the PDCCH contains a pointer, called TCI State ID, to a subset of the TCI states configured for the PDSCH. The network then activates one TCI state for the PDCCH (i.e., provides a TCI for the PDCCH) and up to eight active TCI states for the PDSCH. The number of active TCI states supported by the UE depends on the UE capabilities, but the maximum value is eight. The TCI state used for the PDSCH is dynamically indicated in DCI 1_1.

[0019] Each configured TCI state contains parameters for quasi-co-located association between a source reference signal (CSI-RS or synchronization signal block (SSB)) and a target reference signal (such as a PDSCH / PDCCH DMRS port). The TCI state is also used to convey QCL information for CSI-RS reception.

[0020] CORESET and Search Space: The PDCCH has one or more Control Channel Elements (CCEs), as shown in Table 1 below. A CCE consists of six Resource Element Groups (REGs), where a REG is equal to one RB during one OFDM symbol. PDCCH aggregation levels supported by NR. [Table 1]

[0021] The set of PDCCH candidates that a UE should monitor is defined in terms of a PDCCH search space set. A search space set can be either a common search space (CSS) set or a UE-specific search space (USS) set. A UE can be configured with up to 10 sets of search spaces per bandwidth part to monitor PDCCH candidates.

[0022] The search space set is defined relative to a control resource set (CORESET). CORESET is a set of N RB CORESET resource blocks and N symb CORESET ∈{1,2,3} consecutive OFDM symbols. In NR Release 15, a UE may be configured with up to three CORESETs per bandwidth part. For each CORESET, the UE is configured by Radio Resource Control (RRC) signaling with a CORESET information element (IE) containing: ●CORESET index p (0≦ p ≦ 12) ● DM-RS scrambling sequence initialization value; Precoder granularity for several REGs in the frequency domain, allowing the UE to assume the use of the same DM-RS (Demodulation Reference Signal) precoder; ● Number of consecutive symbols; ● A set of resource blocks; ● CCE-to-REG mapping parameters; ● A list of up to 64 TCI states, which are configurable for CORESETp. These TCI states are used to provide the QCL relationship between source DL RSs in one RS set within the TCI state and PDCCH DMRS ports (DMRS ports of PDCCH received in one of the search spaces defined in CORESETp). The source DL RS(s) can be either CSI-RS or SSB; ●Indication of the presence or absence of the transmission configuration indication (TCI) field of DCI format 1_1 transmitted by the PDCCH in CORESETp.

[0023] For each search space set, the UE is configured with: ●Search space set index s (0=s≦40) ● Association between search space set s and CORESETp ●k s PDCCH monitoring period of slots and s PDCCH monitoring offset for slots PDCCH monitoring pattern in a slot, which indicates the first symbol of the CORESET in a slot for PDCCH monitoring. ● Duration T indicates the number of slots in which the search space set s exists. s (T s <k s slot) Number of PDCCH candidates M per CCE aggregation level L s (L) An indication of whether the search space set s is a CSS set or a USS set. DCI format for surveillance

[0024] For a search space set s, the UE

number

[0025] The UE first detects and decodes the PDCCH, and if the decoding is successful, it decodes the corresponding PDSCH based on the control information in the decoded PDCCH. If the PDSCH is successfully decoded, a HARQ (Hybrid ARQ) ACK is sent to the gNB via the Physical Uplink Control Channel (PUCCH). Otherwise, a HARQ Negative Acknowledgment (NACK) is sent to the gNB via the PUCCH to allow the UE to retransmit the data. If the PUCCH overlaps with a PUSCH transmission, HARQ feedback can also be carried on the PUSCH.

[0026] Uplink data transmissions are also dynamically scheduled using the PDCCH. Similar to the downlink, the UE first decodes the uplink grant in the PDCCH and then transmits data on the PUSCH based on the control information in the decoded uplink grant, such as modulation order, coding rate, and uplink resource allocation.

[0027] DCI format 1_1 is used for scheduling of PDSCH in one cell. The following information is transmitted by DCI format 1-1 with a cyclic redundancy check (CRC) scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), or the configured Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme (MCS)-C-RNTI: DCI format identifier ●Career indicator Bandwidth Part Indicator Frequency domain resource allocation Time Domain Resource Allocation (TDRA) - 0, 1, 2, 3, or 4 bits as defined in subclause 5.1.2.1 of 3GPP TS 38.214. The bit width of this field is determined as [log2(I)] bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if higher layer parameters are configured. Otherwise, I is the number of entries in the default table. Mapping between Virtual Resource Blocks (VRBs) and Physical Resource Blocks (PRBs) PRB bundle size indicator Rate matching indicator Zero Power (ZP) CSI-RS Trigger For Transport Block 1: Modulation and coding method - 5 bits (I MCS ) New Data Indicator (NDI) - 1 bit Redundant version - 2 bits (rv id ) For Transport Block 2 (present only if maxNrofCodeWordsScheduledByDCI equals 2): Modulation and coding method - 5 bits (I MCS ) New Data Indicator (NDI) - 1 bit Redundant version - 2 bits (rv id ) HARQ process number Downlink Allocation Index (DAI) ●Transmit power control (TPC) commands for scheduled PUCCH ●PUCCH resource indicator (PRI) ● As defined in subclause 9.2.3 of 3GPP TS 38.213, P DSCH-to-HARQ Feedback Timing Indicator (K1) - 0, 1, 2, or 3 bits. The bit width of this field is determined as [log2(I)] bits, where I is the number of entries in the upper layer parameter dl-DataToUL-ACK. Antenna ports as defined by 3GPP TS38.212 Table 7.3.1.2.2-1 / 2 / 3 / 4 - 4, 5, or 6 bits ● Transmission Configuration Indication (TCI) – 0 bit if the higher layer parameter tci-PresentInDCI is not enabled, otherwise 3 bits as defined in subclause 5.1.5 of 3GPP TS38.214. ●Sounding reference signal request ● Code Block Group (CBG) transmission information ●CBG flush-out information ● DMRS sequence initialization - 1 bit.

[0028] PDSCH resource allocation in the time domain

[0029] When a UE is scheduled to receive a PDSCH by a DCI, the time domain resource allocation (TDRA) field value m of the DCI provides the row index m+1 for the allocation table. The determination of the resource allocation table to be used is defined in subclause 5.1.2.1.1 of 3GPP TS38.214.v15.5.0, where either the default PDSCH time domain allocation A, B, or C according to tables 5.1.2.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4, and 5.1.2.1.1-5 is applied, or the higher layer configuration parameter pdsch-TimeDomainAllocationList in either pdsch-ConfigCommon or pdsch-Config is applied. Table 5.1.2.1.1-2 of 3GPP TS38.214 v15.5.0 is copied below: Table 5.1.2.1.1-2: Default PDSCH time domain resource allocation for normal CP A [Table 2]

[0030] The indexed row defines the slot offset K0, start symbol S, allocation length L and the PDSCH mapping type assumed for PDSCH reception when the default table is used. Either Type A (i.e., slot-based PDSCH transmission) or Type B (i.e., minislot-based PDSCH transmission) can be indicated. If pdsch-TimeDomainAllocationList is configured, it contains a list of PDSCH-Time Domain Resource Allocation Information Elements (IEs) as shown below, where the start symbol S and the allocation length L are jointly encoded into a start and length indicator SLIV, startSymbolAndLength. PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32) mappingType ENUMERATED {typeA, typeB}, startSymbolAndLength INTEGER (0..127) }

[0031] Valid S and L values ​​are shown in the table below. <Table 5.1.2.1-1> Valid S and L combinations (3GPP TS38.214 v15.5.0) [Table 3] Note that for Type A PDSCHs, the TDRAs in the pdsch-TimeDomainAllocationList or default table overlap, and only one PDSCH can be scheduled in one slot per cell in NR Release 15. For Type B PDSCHs, the TDRAs in the pdsch-TimeDomainAllocationList or default table may not overlap, so multiple PDSCHs may be scheduled in one slot. Figure 3 shows some examples, and in Figure 3D, two Type B PDSCHs are scheduled in a slot.

[0032] NR MIMO Data Transmission: NR data transmission over multiple MIMO layers is shown in Figure 4. Depending on the total number of MIMO layers, or rank, either one codeword (CW) or two codewords are used. In NR Release 15, one codeword is used when the total number of layers is four or less, and two codewords are used when the number of layers is more than four. Each codeword contains the coded data bits of a transport block (TB). After bit-level scrambling, the scrambled bits are represented as a complex-valued modulation symbol d for codeword q, q∈(0,1). (q) (0),...,d (q) (M symb (q) -1). Then, according to 3GPP TS 38.211 v15.5.0, table 7.3.1.3-1, the complex-valued modulation symbols are mapped to the following layers:

number

[0033] For demodulation purposes, a demodulation reference signal (DMRS), also called a DMRS port, is transmitted on each data layer.

number

number

[0034] The maximum number of TBs or codewords that can be scheduled in DCI format 1-1 is configured by the higher layer parameter maxNrofCodeWordsScheduledByDCI. Using this parameter, either 1 or 2 codewords can be configured. If the higher layer parameter maxNrofCodeWordsScheduledByDCI indicates that 2 codeword transmission is enabled, then I MCS = 26 and rv for the corresponding transport block id If I = 1, one of the two transport blocks is disabled by DCI format 1-1, where I MCS is the MCS (Modulation and Coding Scheme) index, and rv id are the redundancy versions, both indicated within DCI1_1. If both transport blocks are enabled, transport blocks 1 and 2 are mapped to codewords 0 and 1, respectively. If only one transport block is enabled, the enabled transport block is always mapped to the first codeword.

[0035] DMRS Code Division Multiplexing (CDM) Groups: The mapping of DMRS to resource elements is configurable in both the frequency domain and the time domain. In the frequency domain, there are two mapping types: configuration Type 1 or Type 2. For each OFDM symbol configured for DMRS, there are two Code Division Multiplexing (CDM) groups for Type 1 and three CDM groups for Type 2 DMRS. An example is shown in Figure 5, where one front-loaded DMRS symbol is configured.

[0036] The mapping of DMRS ports to CDM groups is shown in Tables 2 and 3 for configuration types 1 and 2.

[0037] Table 2: PDSCH DMRS port to CDM group mapping, configuration type 1. [Table 4] Table 3: PDSCH DMRS port to CDM group mapping, configuration type 2. [Table 5]

[0038] NR HARQ ACK / NACK feedback via PUCCH: When receiving a PDSCH in the downlink from the serving gNB in ​​slot n, if the PDSCH is successfully decoded, the UE feeds back a Hybrid Automatic Repeat Request (HARQ) ACK to the gNB in ​​slot n+k via PUCCH (Physical Uplink Control Channel) resources in the uplink. If the PDSCH is not successfully decoded, the UE sends a HARQ NACK to the gNB in ​​slot n+k to indicate that the PDSCH was not successfully decoded. If two TBs are carried by the PDSCH, a HARQ ACK / NACK is reported for each TB. As a result, if one TB is not successfully decoded, only that TB needs to be retransmitted by the gNB. Spatial bundling can also be configured, in which case the logical AND of the decoding status of TB1 and TB2 is fed back. k is also referred to as K1 in the 3GPP specifications.

[0039] For DCI format 1-0, k is indicated by the 3-bit PDSCH-to-HARQ timing indicator field. For DCI format 1-1, k is indicated by the 3-bit PDSCH-to-HARQ timing indicator field (if present) or by higher layers via radio resource control (RRC) signaling.

[0040] If code block group (CBG) transmission is configured, the HARQ ACK / NACK for each CBG in the TB is reported instead.

[0041] In case of carrier aggregation (CA) with multiple component carriers (CC) and / or time division duplex (TDD) operation, multiple aggregated HARQ ACK / NACK bits need to be transmitted in a single PUCCH resource.

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

[0043] If the UE transmits UCI information bits, the UE determines the PUCCH resource set as follows: ●First set: O UCI If ≦2, a set of PUCCH resources with pucch-ResourceSetId = 0, including one or two HARQ-ACK information bits and a positive or negative SR in one SR transmission occasion if the HARQ-ACK information and SR transmissions occur simultaneously. ●Second set: 2 <O UCI If ≦N2, a set of PUCCH resources with pucch-ResourceSetId=1 if provided by higher layers. ●Third set: N2 <O UCIIn the case of ≤ N3 and provided by the upper layer, a set of PUCCH resources with pucch-ResourceSetId = 2. ● The fourth set: N3 < O UCI In the case of ≤ 1706 and provided by the upper layer, a set of PUCCH resources with pucch-ResourceSetId = 3.

[0044] Here, N1 < N2 < N3 are provided by the upper layer.

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

[0046] In the case of CA and / or Time Division Duplex (TDD) when receiving multiple DCI formats 1_0 or 1_1, the determination of the PUCCH resource is that the UE detection Among the multiple received DCI formats 1_0 or DCI format 1-1, it is based on the PUCCH resource indicator (PRI) field in the last DCI format 1_0 or DCI format 1-1. The multiple received DCI formats 1_0 or DCI format 1_1 have the value of the PDSCH-to-HARQ_ feedback timing indicator field indicating the same slot for PUCCH transmission. For PUCCH resource determination, detection the multiple DCI formats made are first indexed in ascending order by the serving cell index in the same PDCCH monitoring occasion, and then indexed in ascending order by the PDCCH monitoring occasion index.

[0047] The 3-bit PRI field is mapped to a PUCCH resource in a PUCCH resource set containing up to 8 PUCCH resources. In the first set of PUCCH resources with pucch-ResourceSetId = 0, the number of PUCCH resources contained in the set R PUCCH If r is greater than 8, the UE uses index r to transmit HARQ-ACK information in response to detecting the last DCI format 1_0 or DCI format 1_1 in PDCCH reception among the DCI format 1_0 or DCI format 1_1 received by the UE, which have a value in the PDSCH-to-HARQ feedback timing indicator field indicating the same slot for PUCCH transmission. PUCCH (0≦r PUCCH ≦R PUCCH -1) is determined as follows:

[0048]

number

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

[0050] Determining the HARQ-ACK codebook for NR Type 1: The size of the HARQ codebook (CB) in the time direction (DL associated set) is determined based on the configured set of HARQ-ACK timing K1 and, in the case of TDD, the semi-statically configured TDD pattern.

[0051] Figure 6 shows an example of a TDD pattern with a set of K1 from 1 to 5 and a configured time domain resource allocation table or pdsch-TimeDomainAllocationList without non-overlapping PDSCH TDRA allocations, i.e., only one PDSCH can be scheduled in a slot. In this case, the HARQ codebook has five entries, one for each K1 value. For slots with no PDSCH transmission or where the PDCCH for PDSCH scheduling is not detected by the UE, the corresponding entry in the codebook is filled with a NACK ("N" in the figure), and for slots where a PDSCH is scheduled, the corresponding entry is filled with either an ACK or a NACK ("X" in the figure) depending on whether the PDSCH was successfully decoded or not.

[0052] If the UE supports reception of multiple unicast PDSCHs per slot, one HARQ codebook entry is reserved per slot for each non-overlapping time domain resource allocation in the pdsch-symbolAllocation table, otherwise one HARQ entry is reserved per slot.

[0053] For MIMO with up to two codewords, an additional entry is added for each K1 value. For multiple CCs, an additional entry in the HARQ codebook is added for each CC. In the component carrier dimension, the HARQ codebook size is given by the number of configured DL cells and the maximum number of HARQ feedback bits based on the configuration per DL cell (e.g., MIMO, spatial bundling, number of configured code block groups (CBGs) per TB). An example is shown in Figure 7, where a semi-static HARQ codebook for a UE consists of three cells, namely, cells 1 to 3. Cell 1 is configured with up to two TBs per PDSCH, cell 2 is configured with one TB per PDSCH, and cell 3 is configured with one TB and four CBGs. For each K1 value, the UE needs to feedback seven bits, namely, two bits for cell 1, one bit for cell 2, and four bits for cell 3 (not considering the potential multiple entries per slot based on the pdsch-symbolAllocation table). The rows and columns shown in the diagram are for illustrative purposes; the actual feedback is a single bit vector by arranging the bits in a particular order.

[0054] Non-coherent Joint Transmission (NC-JT) via Multiple Transmit-Receive Points or Panels (TRPs): NC-JT refers to MIMO data transmission via multiple TRPs, where multiple MIMO layers are transmitted via multiple TRPs. An example is shown in Figure 8, where data is transmitted to a UE via two TRPs, with each TRP carrying one TB mapped to one codeword. If the UE has four receive antennas but only two transmit antennas per TRP, the UE can support up to four MIMO layers, but each TRP can transmit up to two MIMO layers. In this case, transmitting data to the UE via two TRPs increases the peak data rate to the UE because up to four aggregated layers from the two TRPs are available. This is due to the increased throughput of the transmission. PhiThis is beneficial when the load, i.e., resource utilization, is low on each TRP. In this example, a single scheduler is used to schedule data over two TRPs. Within a slot, one PDCCH is transmitted from each of the two TRPs, each of which schedules one PDSCH. This is called a multi-PDCCH or multi-DCI scheme, and the UE receives two PDCCHs and their associated two PDSCHs from the two TRPs within a slot. The two PDSCHs are typically assigned the same time / frequency resources.

[0055] In another scenario, shown in Figure 9, an independent scheduler is used for each TRP. In this case, only semi-static to semi-dynamic coordination between the two schedulers is feasible due to the non-ideal backhaul, i.e., a backhaul with large delays and / or delay variations up to several milliseconds, comparable to or possibly even longer than the cyclic prefix length.

[0056] In the 3GPP RAN1 ad hoc meeting NR_AH_1901, it was agreed that separate ACK / NACK payloads / feedbacks for multiple received PDSCHs are supported for multi-PDCCH-based multi-TRP / panel downlink transmissions for enhanced mobile broadband (eMBB). Furthermore, it was agreed that for multi-DCI-based multi-TRP / panel transmissions, if the resource allocations of the PDSCHs overlap, the total number of CWs in the PDSCHs, each scheduled by one PDCCH, is limited to two.

[0057] In 3GPP RAN1#96, it was agreed that for separate ACK / NACK payloads / feedback for received PDSCHs where multiple DCIs are used, the PUCCH resources carrying the ACK / NACK feedback can be time-domain multiplexed (TDMed) using separate HARQ-ACK codebooks. In RAN1#96bis, it was further agreed that for separate ACK / NACK payloads / feedback for received PDSCHs where multiple DCIs are used, support is provided for TDMed PUCCH transmissions within a slot to carry at least separate ACK / NACK-only feedback using separate HARQ-ACK codebooks for the two TRPs.

[0058] In RAN1#97, it was agreed that for separate ACK / NACK feedback for PDSCHs received from different TRPs, the UE must be able to generate separate ACK / NACK codebooks identified by an index if the index is configured and applied across all CCs. The index used to generate the separate ACK / NACK codebooks is a higher layer signaling index per CORESET. Furthermore, it was agreed that joint HARQ-ACK feedback for PDSCHs received from different TRPs where multiple DCIs are used is also supported.

[0059] Currently, several challenges exist: It is necessary to determine how to construct a semi-static HARQ codebook for joint HARQ-ACK feedback for PDSCHs received from different TRPs when multiple DCIs are used. In particular, it is necessary to determine how to multiplex the A / N bits associated with two PDSCHs. Summary of the Invention

[0060] Physics via multiple TRPs DaSystems and methods are provided for joint hybrid automatic repeat request (HARQ) feedback for downlink shared channel (PDSCH) transmissions. In some embodiments, a method performed by a wireless device to enable transmission feedback includes receiving a first transport block (TB) and a second TB and determining the first TB and the second TB based on a CORESET group identifier of a control resource set (CORESET) in which corresponding downlink control information (DCI) scheduling the TB is received. In this manner, New Radio (NR) Release 15 procedures for Type-1 HARQ codebook construction can be reused without increasing, or with minimal increase in, HARQ feedback overhead using a semi-static HARQ-ACK codebook.

[0061] In some embodiments, the method also includes receiving, before receiving the first TB and the second TB, a configuration with a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time domain resource allocations per slot in the serving cell.

[0062] In some embodiments, the method also includes, before receiving the first TB and the second TB, receiving an indication to allocate two entries, a first entry and a second entry, to a Type-1 HARQ codebook for each configured K1 value and each set of overlapping PDSCH time domain resource allocations.

[0063] In some embodiments, the method also includes mapping HARQ-ACK bits for the first TB to a first entry and mapping HARQ-ACK bits for the second TB to a second entry within a Type 1 HARQ-ACK codebook associated with the same K1 value and the same time domain resource allocation.

[0064] In some embodiments, the method also includes reporting the constructed Type-1 HARQ codebook.

[0065] In some embodiments, receiving the first TB and the second TB includes receiving the first TB from a first transmit reception point (TRP) and receiving the second TB from a second TRP in a slot, where the first TB and the second TB are scheduled with two DCIs, one for each TB, the same time domain resource allocation, and the same K1 value. In some embodiments, receiving the indication to allocate two entries may be explicit or implicit.

[0066] In some embodiments, receiving an indication to allocate two entries includes receiving one or more of the following group: an upper layer parameter maxNrofCodeWordsScheduledByDCI=2; an upper layer parameter indicating joint HARQ ACK feedback and a configuration of two CORESET groups, each having a different group identifier value per CORESET for the HARQ-ACK report; and a configuration of one CORESET group, each having the same group identifier value per CORESET for the HARQ-ACK report.

[0067] In some embodiments, if the first TB or the second TB is not received, the first entry or the second entry is filled with a NACK, respectively. In some embodiments, the transmitting can further include transmitting one or two TBs scheduled by a single DCI. In some embodiments, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2, as indicated in the DCI. In some embodiments, the wireless device is a New Radio (NR) user equipment (UE).

[0068] In some embodiments, determining the first TB and the second TB also includes determining the first TB and the second TB based on one or more of the group consisting of: a demodulation reference signal (DMRS) code division multiplexing (CDM) group identifier of one or more DMRS ports indicated in the corresponding DCI scheduling the TB; a TB identifier indicated in the corresponding DCI scheduling the TB; a transmission configuration indication (TCI) state identifier indicated in the corresponding DCI scheduling the TB; a TCI state identifier of the CORESET through which the corresponding DCI scheduling the TB will be received; and a scrambling identifier of the PDSCH carrying the TB.

[0069] In some embodiments, a method performed by a base station to enable transmission feedback comprises transmitting a first TB and a second TB to a wireless device, the first TB and the second TB being determined based on a CORESET group identifier of the CORESET via which corresponding DCI scheduling the TBs will be transmitted; and receiving a constructed Type 1 HARQ codebook from the wireless device.

[0070] In some embodiments, the method also includes transmitting to the wireless device, before transmitting the first TB and the second TB, a configuration with a list of PDSCH time domain resource allocations per slot in the serving cell and / or a set of PDSCH-to-HARQ feedback timing K1 values.

[0071] In some embodiments, the method also includes, before transmitting the first TB and the second TB, transmitting an indication to the wireless device to allocate two entries, a first entry and a second entry, in a Type-1 HARQ codebook for each of the configured K1 values ​​and each set of overlapping PDSCH time domain resource allocations.

[0072] In some embodiments, transmitting the first TB and the second TB includes transmitting the first TB from a first TRP and transmitting the second TB from a second TRP in a slot, wherein the first TB and the second TB are scheduled with two DCIs, one for each TB, with the same time domain resource allocation and the same K1 value.

[0073] In some embodiments, sending the indication to allocate two entries may be explicit or implicit. In some embodiments, sending the indication to allocate two entries includes sending one or more of the following groups: an upper layer parameter maxNrofCodeWordsScheduledByDCI=2; an upper layer parameter indicating joint HARQ ACK feedback; a configuration of two CORESET groups, each having a different group identifier value per CORESET for the HARQ-ACK report; or a configuration of one CORESET group, each having the same group identifier value per CORESET for the HARQ-ACK report.

[0074] In some embodiments, if the first TB or the second TB is not received, the first entry or the second entry is filled with a NACK, respectively. In some embodiments, the transmitting can further include transmitting one or two TBs scheduled by a single DCI. In some embodiments, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2, as indicated in the DCI. In some embodiments, the base station is an NR gNB.

[0075] In some embodiments, the first TB and the second TB are further determined based on one or more of the group consisting of: a DMRS CDM group identifier of one or more DMRS ports indicated in the corresponding DCI scheduling the TB; a TB identifier indicated in the corresponding DCI scheduling the TB; a TCI state identifier indicated in the corresponding DCI scheduling the TB; a TCI state identifier of the CORESET via which the corresponding DCI scheduling the TB is received; and a scrambling identifier of the PDSCH carrying the TB.

[0076] In some embodiments, a wireless device for enabling transmit feedback includes one or more processors and a memory, the memory storing instructions executable by the one or more processors such that the wireless device is operable to perform any of the methods described above.

[0077] In some embodiments, a base station for enabling transmission feedback includes one or more processors and a memory, the memory storing instructions executable by the one or more processors such that the base station is operable to perform any of the methods described above. [Brief explanation of the drawings]

[0078] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure.

[0079] [Figure 1] shows a 14-symbol slot, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the Physical Shared Data Channel, either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0080] [Figure 2] Figure 1 shows the basic New Radio (NR) physical time-frequency resource grid.

[0081] [Figure 3] 1 shows some examples where two Type-B PDSCHs are scheduled in a slot.

[0082] [Figure 4] indicates NR data transmission over multiple multiple-input multiple-output (MIMO) layers.

[0083] [Figure 5] shows the mapping of demodulation reference signals (DMRS) to resource elements that are configurable in both the frequency and time domains.

[0084] [Figure 6] indicates a time division duplex (TDD) pattern with a set of K1 from 1 to 5 and a configured time domain resource allocation table.

[0085] [Figure 7] 1 shows a semi-static hybrid automatic repeat request (HARQ) codebook for a wireless device configured with three cells, namely cells 1 to 3.

[0086] [Figure 8], denotes data transmitted to a wireless device via two transmit receive points (TRPs), each carrying one TB that is mapped to one codeword.

[0087] [Figure 9] indicates the independent scheduler used in each TRP.

[0088] [Figure 10] 1 illustrates an example of a cellular communication system in which embodiments of the present disclosure may be implemented, in accordance with some embodiments of the present disclosure.

[0089] [Figure 11] 1 illustrates a wireless communication system represented as a 5G network architecture including a core network function (NF) according to some embodiments of the present disclosure.

[0090] [Figure 12] 1 illustrates a 5G network architecture that uses service-based interfaces between NFs in the control plane instead of the point-to-point reference points / interfaces used in the 5G network architecture of FIG. 11 , in accordance with some embodiments of the present disclosure.

[0091] [Figure 13A] and [Figure 13B] 1A-1D illustrate methods of operation of a wireless device and a base station, respectively, in accordance with some embodiments of the present disclosure.

[0092] [Figure 13C] indicates a wireless device configured with K1 in the range of 1 to 5, and receiving one PDSCH from one TRP in a slot or two PDSCHs from two TRPs in a slot, according to some embodiments of the present disclosure.

[0093] [Figure 14] 1 illustrates an example in which PDCCH #1 and PDCCH #2 are transmitted from TRP1 and 2, respectively, in accordance with some embodiments of the present disclosure.

[0094] [Figure 15] 1 illustrates an example in which PDCCH #1 and PDCCH #2 are transmitted from TRP1 and 2, respectively, in accordance with some embodiments of the present disclosure.

[0095] [Figure 16] 1 illustrates CDM group 0 signaled for PDSCH #1 and CDM group 1 signaled for PDSCH #2, in accordance with some embodiments of the present disclosure.

[0096] [Figure 17] 1 illustrates two CORESET groups defined by higher layer signaling indexes according to some embodiments of the present disclosure.

[0097] [Figure 18] 1 illustrates a cell configured with one TB and two CORESET groups according to some embodiments of the present disclosure.

[0098] [Figure 19] 1 illustrates an embodiment of a user equipment (UE) in accordance with some embodiments of the present disclosure.

[0099] [Figure 20] 1 is a schematic block diagram illustrating a virtualization environment in which functionality implemented by some embodiments of the present disclosure may be virtualized, according to some embodiments.

[0100] [Figure 21] 1 illustrates an exemplary communication system according to some embodiments of the present disclosure.

[0101] [Figure 22]22 illustrates an example implementation according to one embodiment of the UE, base station, and host computer of FIG. 21 in accordance with some embodiments of the present disclosure.

[0102] [Figure 23] , [Figure 24] , [Figure 25] , and [Figure 26] 1 is a flowchart illustrating a method performed in a communication system according to some embodiments of the present disclosure.

[0103] [Figure 27] , [Figure 28] , and [Figure 29] 1 shows a flowchart illustrating some methods implemented in a communication system according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0104] The embodiments described below represent information that will enable those skilled in the art to implement the embodiments and show the best modes for implementing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not specifically addressed herein. It is to be understood that these concepts and applications are within the scope of this disclosure.

[0105] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless device.

[0106] Radio Access Node: As used herein, a "radio access node" or "radio network node" is any node in a radio access network of a cellular communications network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, base stations (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, Home eNBs, etc.), and relay nodes.

[0107] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (PGW), a Service Capability Publication Function (SCEF), a Home Subscriber Server (HSS), etc. Other examples of core network nodes include nodes that implement an Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Publication Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), etc.

[0108] Wireless Device: As used herein, a "wireless device" is any type of device that accesses (i.e., is served by) a cellular communications network by wirelessly transmitting and / or receiving signals to a radio access node. Some examples of wireless devices include, but are not limited to, user equipment devices (UE) and machine type communications (MTC) devices in 3GPP networks.

[0109] Network Node: As used herein, a "network node" is any node that is part of the radio access network or core network of a cellular communications network / system.

[0110] It should be noted that the description provided herein focuses on 3GPP cellular communication systems, and therefore 3GPP terminology or terminology similar to 3GPP terminology is often used, however, the concepts disclosed herein are not limited to 3GPP systems.

[0111] In the description herein, reference may be made to the term "cell," but it should be noted that, particularly with respect to 5G NR concepts, beams may be used in place of cells, and therefore the concepts described herein are equally applicable to both cells and beams.

[0112] FIG. 10 illustrates an example of a cellular communication system 1000 in which embodiments of the present disclosure can be implemented. In the embodiments described herein, the cellular communication system 1000 is a 5G system (5GS) that includes an NR RAN. In this example, the RAN includes base stations 1002-1 and 1002-2, referred to as gNBs in 5G NR, that control corresponding (macro) cells 1004-1 and 1004-2. The base stations 1002-1 and 1002-2 are generally referred to herein collectively as base stations 1002 and may also be individually referred to as base stations 1002. Similarly, the (macro) cells 1004-1 and 1004-2 are generally referred to herein as (macro) cells 1004 and individually as (macro) cells 1004. The RAN may also include several low-power nodes 1006-1 through 1006-4 that control corresponding small cells 1008-1 through 1008-4. The low power nodes 1006-1 to 1006-4 may be small base stations (such as pico or femto base stations) or RemoteThe small cells 1008-1 through 1008-4 may be radio frequency heads (RRHs), or the like. Notably, although not shown, one or more of the small cells 1008-1 through 1008-4 may alternatively be provided by the base station 1002. The low power nodes 1006-1 through 1006-4 are generally referred to herein collectively as low power nodes 1006 and individually as low power nodes 1006. Similarly, the small cells 1008-1 through 1008-4 are generally referred to herein as small cells 1008 and individually as small cells 1008. The cellular communication system 1000 also includes a core network 1010, which in 5GS is referred to as 5G Core (5GC). The base station 1002 (and optionally the low power nodes 1006) are connected to the core network 1010.

[0113] Base station 1002 and low power node 1006 serve wireless devices 1012-1 through 1012-5 in corresponding cells 1004 and 1008. Wireless devices 1012-1 through 1012-5 are referred to herein collectively as wireless devices 1012 and individually as wireless devices 1012. Wireless devices 1012 may also be referred to herein as UEs.

[0114] 11 illustrates a wireless communication system represented as a 5G network architecture consisting of core network functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 11 can be seen as one particular implementation of the system 1000 of Figure 10.

[0115] The 5G network architecture shown in Figure 11 includes, from the access side, a radio access network (RAN) or access network (AN) and multiple user equipments (UEs) connected to either an access and mobility management function (AMF). Typically, the R (AN) includes a base station, such as an evolved Node B (eNB) or a 5G base station (gNB). From the core network side, the 5G core NF shown in Figure 11 includes a network slice selection function (NSSF), an authentication server function (AUSF), a unified data management function (UDM), an AMF, a session management function (SMF), a policy control function (PCF), and an application function (AF).

[0116] The representation of reference points in the 5G network architecture is used to develop detailed call flows in the exemplary standardization. The N1 reference point is defined to carry signals between the UE and the AMF. The reference points connecting the AN and the AMF and between the AN and the UPF are defined as N2 and N3, respectively. There is a reference point N11 between the AMF and the SMF, which means that the SMF is at least partially controlled by the AMF. N4 is used by the SMF and the UPF, so that the UPF is configured using control signals generated by the SMF and the UPF can report its status to the SMF. N9 is a reference point for connections between different UPFs, and N14 is a reference point connecting different AMFs. N15 and N7 are defined because the PCF applies policies to the AMF and the SMF, respectively. N12 is required for the AMF to authenticate the UE. N8 and N10 are defined because the AMF and the SMF require UE subscription data.

[0117] The 5G core network aims to separate the user plane and the control plane. The user plane carries user traffic, and the control plane carries signaling in the network. In Figure 11, the UPF is in the user plane, and all other NFs, namely the AMF, SMF, PCF, AF, AUSF, and UDM, are in the control plane. Separating the user plane and the control plane ensures that each plane resource can be scaled independently. Also, the UPF can be located separately from the control plane functions in a distributed manner. In this architecture, the UPF may be located very close to the UE to shorten the round-trip time (RTT) between the UE and the data network for some applications that require low latency.

[0118] The core 5G network architecture consists of modularized functions. For example, AMF and SMF are independent functions in the control plane. Separating AMF and SMF enables independent evolution and scaling. Other control plane functions, such as PCF and AUSF, can be separated as shown in Figure 11. The modularized function design allows the 5G core network to flexibly support various services.

[0119] Each NF interacts directly with another NF. Messages can be routed from one NF to another using intermediate functions. In the control plane, a set of interactions between two NFs is defined as a service so that it can be reused. This service allows for modularity support. The user plane supports interactions such as forwarding operations between different UPFs.

[0120] FIG. 12 illustrates a 5G network architecture that uses a service-based interface between NFs in the control plane instead of the point-to-point reference points / interfaces used in the 5G network architecture of FIG. 11. However, the NFs described above with reference to FIG. 11 correspond to the NFs illustrated in FIG. 12. Services, etc., that an NF provides to other authorized NFs may be exposed to authorized NFs through the service-based interface. In FIG. 12, a service-based interface is indicated by the letter "N" followed by the name of the NF. For example, "Namf" for an AMF service-based interface, "Nsmf" for an SMF service-based interface, etc. The Network Publication Function (NEF) and Network Function (NF) Repository Function (NRF) of FIG. 12 are not illustrated in FIG. 11 above. However, it should be understood that, although not explicitly illustrated in FIG. 11, all NFs illustrated in FIG. 11 can interact with the NEFs and NRFs of FIG. 12 as needed.

[0121] Some features of the NFs shown in Figures 11 and 12 can be described in the following way: The AMF provides UE-based authentication, authorization, mobility management, etc. The AMF is independent of radio access technology, so even UEs using multiple access technologies are essentially connected to a single AMF. The SMF is responsible for session management and assigns an Internet Protocol (IP) address to the UE. It also selects and controls the UPF for data transfer. If a UE has multiple sessions, a different SMF is assigned to each session to manage them individually, and in some cases, different functions can be provided for each session. The AF provides information about packet flows to the PCF, which is responsible for policy control, to support Quality of Service (QoS). Based on this information, the PCF determines policies for mobility and session management to ensure the AMF and SMF operate appropriately. The AUSF supports authentication functions for UEs, etc., and therefore stores data for authentication of UEs, etc., while the UDM stores UE subscription data. The Data Network (DN) is not part of the 5G core network and provides Internet access, operator services, etc.

[0122] An NF may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, e.g., a cloud infrastructure.

[0123] In RAN1#97, it was agreed that for separate ACK / NACK feedback for physical downlink shared channels (PDSCHs) received from different TRPs, the UE must be able to generate separate ACK / NACK codebooks identified by an index if the index is configured and applied to all CCs. The index used to generate the separate ACK / NACK codebooks is a higher layer signaling index per control resource set (CORESET). Furthermore, it was agreed that joint HARQ-ACK feedback for multiple PDSCHs received from different TRPs using multiple DCIs is also supported.

[0124] Currently, several challenges exist: it is necessary to determine how to construct a semi-static HARQ codebook for joint HARQ-ACK feedback for multiple PDSCHs received from different transmit / receive points (TRPs) where multiple DCIs are used, and in particular, how to multiplex the A / N bits associated with two PDSCHs.

[0125] Systems and methods are provided for joint hybrid automatic repeat request (HARQ) feedback for PDSCH transmissions over multiple TRPs. In some embodiments, a method performed by a wireless device to enable transmission feedback includes receiving a first transport block (TB) and a second TB and determining the first TB and the second TB based on a CORESET group identifier for a CORESET through which corresponding downlink control information (DCI) scheduling the TBs is received. In this manner, NR Release 15 procedures for Type-1 HARQ codebook construction can be reused with no or minimal increase in HARQ feedback overhead using a semi-static HARQ-ACK codebook.

[0126] 13A and 13B illustrate methods of operation of a wireless device and a base station, respectively, according to some embodiments of the present disclosure. As shown in FIG. 13A, the wireless device receives a configuration (configuration information) optionally with a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time domain resource allocations per slot in the serving cell (step 1300). The wireless device receives a first TB and a second TB (e.g., carried in a component carrier (CC)) (step 1302). The wireless device determines the first TB and the second TB based on one or more indications. As shown in FIG. 13A, the TBs are vinegar The corresponding DCI to be scheduled is received via a CORESET, and the first and second TBs are determined based on a CORESET group identifier of the CORESET (step 1304). The wireless device optionally reports the constructed Type-1 HARQ codebook (step 1306). In this way, the NR Release 15 procedure for constructing a Type-1 HARQ codebook can be reused without increasing or with a minimal increase in HARQ feedback overhead using a semi-static HARQ-ACK codebook.

[0127] As shown in FIG. 13B, the base station optionally transmits a configuration including a list of PDSCH time domain resource allocations per slot in the serving cell and / or a set of K1 values, which are PDSCH-to-HARQ feedback timings, to the wireless device (step 1308). The base station transmits a first TB and a second TB to the wireless device, where the first TB and the second TB are determined based on a CORESET group identifier of the CORESET through which the corresponding DCI scheduling the TB is transmitted (step 1310). The base station receives the constructed Type-1 HARQ codebook from the wireless device (step 1312). In this way, the NR Release 15 procedures for constructing a Type-1 HARQ codebook can be reused without increasing or with a minimal increase in HARQ feedback overhead using a semi-static HARQ-ACK codebook.

[0128] Certain aspects of the present disclosure and their embodiments may provide solutions to these and other problems. In some embodiments, the method acknowledges that (a) even with multiple PDCCH scheduling from two TRPs, a total of two TBs are schedulable in a slot, and / or (b) fully overlapping time domain resources are used by the PDSCHs from the two TRPs. Some embodiments include the following.

[0129] In the case of implicit joint A / N feedback signaling, a cell where joint A / N feedback is used is configured with a maximum of two TBs, and therefore, per K1 value and set of overlapping TDRAs, two entries are reserved for the semi-static HARQ-ACK codebook for that cell.

[0130] In the case of explicit joint A / N feedback signaling, the K1 value and the number of entries per set of overlapping TDRAs for the semi-static HARQ-ACK codebook for a cell are determined by the number of CORESET groups configured in that cell.

[0131] The mapping of the A / N bits for a received TB to one of the two entries may be according to one of the following: a DMRS CDM group identifier of one or more DMRS ports indicated in the corresponding DCI scheduling the TB; a TB identifier indicated in the corresponding DCI scheduling the TB; a CORESET group identifier of the CORESET via which the corresponding DCI scheduling the TB is received; a TCI state identifier indicated in the corresponding DCI scheduling the TB; a TCI state identifier of the CORESET via which the corresponding DCI scheduling the TB is received; and a scrambling identifier of the PDSCH carrying the TB.

[0132] At least one wireless node having two transmission points (TRPs) and at least one user device (UE)A method for constructing a Type-1 HARQ-ACK codebook for joint HARQ ACK reporting with multi-DCI-based PDSCH transmissions from multiple TRPs in a wireless network having The method includes: configuring, by the radio node, a UE with a set of K1 values ​​of PDSCH-to-HARQ feedback timing and a list of PDSCH time domain resource allocations per slot in a serving cell; indicating, by the radio node, to the UE to allocate two entries in a Type-1 HARQ codebook for each configured K1 value and each set of overlapping PDSCH time domain resource allocations, a first entry and a second entry; and transmitting, by the radio node, to the UE in the slot, a first TB (Transport Block) from a first TRP and a second TB from a second TRP, wherein the first TB and the second TB are scheduled using two DCIs, one for each TB, and with the same time domain resource allocation and the same K1 value.

[0133] The UE receives first and second TBs, and determines the first or second TB by the UE, based on one or more of the following: a DMRS CDM group identifier of one or more DMRS ports indicated in a corresponding DCI scheduling the TB, a TB identifier indicated in a corresponding DCI scheduling the TB, a CORESET group identifier of the CORESET over which the corresponding DCI scheduling the TB is received, a TCI state identifier indicated in the corresponding DCI scheduling the TB, a TCI state identifier of the CORESET over which the corresponding DCI scheduling the TB is received, and a scrambling identifier of a PDSCH carrying the TB.

[0134] The UE maps HARQ-ACK bits for the first TB to the first entry and maps HARQ-ACK bits for the second TB to the second entry, where the first entry and the second entry are in a Type-1 HARQ-ACK codebook associated with the same K1 value and the same time domain resource allocation, and the UE reports the constructed Type-1 HARQ codebook to the radio node. In the method of 1, the indicating can be either explicit or implicit by configuring an upper layer parameter maxNrofCodeWordsScheduledByDCI = 2 or by configuring different group identifier values ​​for two CORESET groups per CORESET for HARQ-ACK reporting.

[0135] In the first method, if the first TB or the second TB is not received, the first entry or the second entry is filled with a NACK, respectively. In the first method, the transmitting may further include transmitting one or two TBs scheduled by a single DCI. In the first or fourth methods, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2, as indicated in the DCI.

[0136]

[0013] Various embodiments addressing one or more of the problems disclosed herein are proposed herein. In some embodiments, a method performed by a wireless device for providing transmission feedback includes receiving a first transport block (TB) and a second TB, and determining the first TB and the second TB based on one or more of the group consisting of: a demodulation reference signal (DMRS) code division multiplexing (CDM) group identifier of one or more DMRS ports indicated in corresponding downlink control information (DCI) scheduling the TB, a TB identifier indicated in the corresponding DCI scheduling the TB, a CORESET group identifier of a control resource set (CORESET) via which the corresponding DCI scheduling the TB is received, a TCI state identifier indicated in the corresponding DCI scheduling the TB, a TCI state identifier of the CORESET via which the corresponding DCI scheduling the TB is received, and a scrambling identifier of a PDSCH carrying the TB.

[0137] Certain embodiments may provide one or more of the following technical advantages: NR Release 15 procedures for Type-1 HARQ codebook construction can be reused with a semi-static HARQ-ACK codebook without increasing or with minimal increase in HARQ feedback overhead.

[0138] In some embodiments, the method also includes receiving a configuration with a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time domain resource allocations per slot in a serving cell before receiving the first TB and the second TB.

[0139] In some embodiments, the method also includes receiving, before receiving the first TB and the second TB, an indication to allocate two entries, a first entry and a second entry, in a Type-1 HARQ codebook for each of the configured K1 values ​​and each of the sets of overlapping PDSCH time domain resource allocations.

[0140] In some embodiments, the method also includes mapping HARQ-ACK bits for the first TB to the first entry and mapping HARQ-ACK bits for the second TB to the second entry, which are entries in the Type-1 HARQ-ACK codebook and associated with the same K1 value and the same time-domain resource allocation. In some embodiments, the method also includes reporting the constructed Type-1 HARQ codebook.

[0141] In some embodiments, receiving the first TB and the second TB comprises receiving the first TB from a first TRP and the second TB from a second TRP in a slot, wherein the first TB and the second TB are scheduled using two DCIs, one for each TB, and using the same time domain resource allocation and the same K1 value.

[0142] In some embodiments, receiving an indication to allocate two entries may be explicit or implicit. In one embodiment, receiving the indication to allocate two entries includes receiving a higher layer parameter maxNrofCodeWordsScheduledByDCI = 2 and / or configuring two CORESET groups with different group identifier values ​​per CORESET for HARQ-ACK reporting.

[0143] In some embodiments, if the first TB or the second TB is not received, the first entry or the second entry is filled with a NACK, respectively. In some embodiments, the transmitting may further include transmitting one or two TBs scheduled by a single DCI. In some embodiments, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2, as indicated in the DCI. In some embodiments, the wireless device is a New Radio (NR) user equipment (UE).

[0144] In some embodiments, a method performed by a base station for receiving transmission feedback comprises transmitting a first TB and a second TB to a wireless device and receiving a constructed Type 1 HARQ codebook from the wireless device.

[0145] In some embodiments, the method also includes transmitting a configuration to the wireless device with a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time domain resource allocations per slot in a serving cell before transmitting the first TB and the second TB.

[0146] In some embodiments, the method also includes, before transmitting the first TB and the second TB, transmitting an indication to the wireless device to allocate two entries, a first entry and a second entry, to a Type-1 HARQ codebook for each of the configured K1 values ​​and each set of overlapping PDSCH time domain resource allocations.

[0147] In some embodiments, transmitting the first TB and the second TB comprises transmitting the first TB from a first TRP and the second TB from a second TRP in a slot, wherein the first TB and the second TB are scheduled using two DCIs, one for each TB, and using the same time domain resource allocation and the same K1 value.

[0148] In some embodiments, sending the indication to allocate two entries may be explicit or implicit. In one embodiment, sending the indication to allocate two entries includes sending a higher layer parameter maxNrofCodeWordsScheduledByDCI = 2 and / or configuring different group identifier values ​​for two CORESET groups per CORESET for HARQ-ACK reporting.

[0149] In some embodiments, the first entry or the second entry is filled with a NACK if the first TB or the second TB is not received, respectively. In some embodiments, the transmitting may further include transmitting one or two TBs scheduled by a single DCI. In some embodiments, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2, as indicated in the DCI. In some embodiments, the base station is an NR gNB.

[0150] Note that when transmitting multiple PDSCHs with multiple PDCCHs, the total number of TBs that can be scheduled in a time domain resource is two. In other words, only two PDSCHs, each with one TB, can be scheduled in a slot on the same time domain resource. If the UE is configured (either explicitly or implicitly) to use a Type-1 HARQ-ACK codebook (i.e., a semi-static HARQ codebook) for joint HARQ A / N on a CC, the UE may be configured (either explicitly or implicitly) with up to two TBs for the CC to construct a Type-1 HARQ-ACK codebook. If the UE is configured with the higher layer parameter maxNrofCodeWordsScheduledByDCI = 2, no additional signaling is required, as two TBs are assumed to construct a Type-1 codebook according to the Release-15 procedures. If the UE is configured with maxNrofCodeWordsScheduledByDCI = 1, additional indication / signaling is required to inform the UE that two TBs are required to build a Type 1 HARQ codebook for CC.

[0151] An example is shown in Figure 13C, where a UE is configured with K1 ranging from 1 to 5 and either receives one PDSCH from one TRP in a slot or two PDSCHs from two TRPs in a slot. The semi-static HARQ-ACK codebook consists of five entries, each associated with a K1 value, and two rows, each associated with a TB (note that the example in the figure is for illustrative purposes only; an actual codebook would be a long bit vector arranged in a predetermined order). If one PDSCH with two TBs is received in a slot (i.e., configured with maxNrofCodeWordsScheduledByDCI = 2), the first row is associated with TB1 and the second row is associated with TB2, regardless of which TRP the PDSCH is received from. For example, if a PDSCH with two TBs is received in the n-5th slot, with K1=5, the corresponding entry in the first row is associated with TB1, and the corresponding entry in the second row is associated with TB2, with K1=5. TB1 and TB2 are indicated in the corresponding DCI.

[0152] When a PDSCH having one TB is received, whether the TB is associated with an entry in the first row or the second row can be determined by the TRP from which the PDSCH is received, e.g., the first row is associated with TRP1 and the second row is associated with TRP2. For example, if a PDSCH having one TB is received from TRP1 in slot n-4, the TB is associated with the corresponding entry in the first row (K1=4), and the entry in the second row is filled with a NACK (because there is no PDSCH received from TRP2). In another example, if a PDSCH having one TB is received from TRP2 in slot n+4, then the TB is associated with the corresponding entry in the second row (K1=1), and the entry in the first row is filled with a NACK (because there is no PDSCH received from TRP1).

[0153] If two PDSCHs are received in a slot, for example, in slots n-3, n-1, n, n+1, n+3, and n+5, only one TB can be carried by each PDSCH, according to the agreement reached in 3GPP. In this case, the corresponding entry in the first row is associated with the first TB (TB1) received from TRP1, and the corresponding entry in the second row is associated with the second TB (TB2) received from TRP2. However, TRP1 and TRP2 are neither directly signaled to the UE nor specified in the 3GPP standard. Therefore, the first and second TBs, i.e., TB1 and TB2, need to be determined by one or more other parameters.

[0154] If no PDSCH is received in a slot, a NACK is written in the corresponding entries in both rows, e.g., no PDSCH is received in slot n-2, and a NACK is written in the corresponding entry for K=2.

[0155] In implicit signaling, joint HARQ A / N feedback is used when the CORESETs when PDCCHs for multi-TRP transmissions are received on a CC have the same upper layer configuration index per CORESET (i.e., constitute a single CORESET group), or when no upper layer index is configured per CORESET for multiple PDSCH transmissions with multiple PDCCHs. Note that when different upper layer configuration indexes are configured for the CORESETs (i.e., two different CORESET groups are configured), separate HARQ A / N feedback is used for multiple PDSCH transmissions scheduled by multiple PDCCHs. In this case, the upper layer configuration index per CORESET (which can be used to configure two CORESET groups versus a single CORESET group) is used to distinguish between using individual HARQ A / N feedback versus using joint HARQ A / N feedback.

[0156] In one embodiment, even if only one TB can be carried by the PDSCH or the UE can only receive up to four DL MIMO layers, the UE is configured with maxNrofCodeWordsScheduledByDCI = 2. In this case, two TB fields are used in DCI format 1_1, but only one TB is enabled. That is, the first or second TB is indicated in the corresponding DCI. For example, in FIG. 13C, TB1 is mapped to the first row and TB2 is mapped to the second row. For the corresponding transport block indicated in the DCI, MCS =26 and rv id If =1, TB is disabled.

[0157] If the UE can support more than four DL MIMO layers and DCI is received with two TBs enabled, the legacy TB to codeword mapping is used, i.e., TB1 is mapped to the first row and TB2 is mapped to the second row.

[0158] A drawback of this embodiment is that two TB fields of DCI format 1-1 are used, which increases the DCI overhead if one TB per PDSCH is always scheduled.

[0159] In another embodiment, joint HARQ ACK feedback with two TBs per CC may be indicated by configuring a single CORESET group, i.e., a single RRC configuration index value for all CORESETs. In this case, DCI overhead can be saved because only one TB field is needed in DCI format 1_1 when maxNrofCodeWordsScheduledByDCI = 1 is configured. When a PDSCH is received, it needs to be determined whether the corresponding TB is the first TB or the second TB.

[0160] When two PDSCHs are transmitted from two TRPs in completely overlapping time resources, the TCI states indicated in the corresponding DCIs should be different, and the TCI states can be used to indicate PDSCH 1 or PDSCH 2 (hence TB1 and TB2, respectively).

[0161] In NR, the TCI field in the DCI may indicate a TCI state (having a corresponding TCI state ID) that conveys QCL information for reception of the PDSCH DMRS. FIG. 14 shows an example in which PDCCH #1 and PDCCH #2 are transmitted from TRP1 and TRP2, respectively. As shown in FIG. 14, the DCI corresponding to PDCCH #1 that schedules PDSCH #1 may indicate one TCI state (e.g., having a TCI state ID of 3), and the DCI corresponding to PDCCH #2 that schedules PDSCH #2 may indicate another TCI state (e.g., having a TCI state ID of 6). In one variation of this embodiment, a rule is defined such that if the TCI state ID indicated in the DCI of the PDCCH is an odd number, the TB corresponding to the PDSCH is the first TB. If the TCI state ID indicated in the DCI of the PDCCH is an even number, the TB corresponding to the PDSCH is the second TB. More generally, if the TCI state ID indicated in the DCI of the PDCCH is i, the TB corresponding to the PDSCH is the [mod(i,m)]th TB, where m=2.

[0162] In another embodiment, the activated TCI state for the PDCCH carrying QCL information for reception of the PDCCH DMRS is used to indicate PDSCH1 or PDSCH2 (hence, TB1 and TB2, respectively). In NR, a list of TCI states can be configured in a CORESET, and one of the TCI states that provides a QCL relationship for the PDCCH DMRS for the PDCCH received in the CORESET is activated. Figure 15 shows an example in which PDCCH #1 and PDCCH #2 are transmitted from TRP1 and TRP2, respectively. As shown in Figure 15, PDCCH #1 is received in CORESET1 where the TCI state with ID = 3 is activated, and PDCCH #2 is received in CORESET2 where the TCI state with ID = 6 is activated. In this embodiment, a rule is defined such that if the activated TCI state ID corresponding to the CORESET carrying the PDCCH is odd, the TB corresponding to the PDSCH scheduled by that PDCCH is the first TB. If the activated TCI state ID corresponding to a CORESET carrying a PDCCH is even, the TB corresponding to a PDSCH scheduled by that PDCCH is the second TB. More generally, if the activated TCI state ID corresponding to a CORESET carrying a PDCCH is i, the TB corresponding to the PDSCH is the [mod(i,m)]-th TB, where m=2.

[0163] Furthermore, different DMRS CDM groups can be used to indicate PDSCH1 or PDSCH2 (hence, TB1 and TB2, respectively). In one embodiment, the first and second TBs are determined by the DMRS CDM group, i.e., the first TB (TB1) is associated with a PDSCH having CDM group "λ=0," and the second TB (TB2) is associated with a PDSCH having CDM group "λ=1" or "λ=2." An example is shown in FIG. 16, where CDM group 0 is signaled for PDSCH #1 and CDM group 1 is signaled for PDSCH #2. According to this embodiment, the first TB (TB1) is associated with PDSCH #1, and the second TB (TB2) is associated with PDSCH #2. The CGM group numbers or indices are identifiable from the DMRS ports signaled in the corresponding DCI.

[0164] In DMRS type 2, there are three DMRS CDM groups. Therefore, rules can be defined such that one of the TBs is associated with a PDSCH but its DMRS belongs to one CDM group, and another TB is associated with a PDSCH but its DMRS belongs to one or both of the remaining two CDM groups. Consider the following example:

[0165] If the DMRS of PDSCH #1 belongs to CDM group 0, TB1 is associated with PDSCH #1. If the DMRS of PDSCH #2 belongs to CDM group 1, 2, or both, TB2 is associated with PDSCH #2.

[0166] In 3GPP RAN1#97, it was agreed to introduce multiple PDSCH scrambling identifiers for the case of multiple PDCCHs scheduling multiple PDSCHs. Each PDSCH scrambling identifier is used to generate a PDSCH scrambling sequence for one of the PDSCHs. In one embodiment, the first and second TBs are determined by the PDSCH scrambling identifier. For example, if the PDSCH scrambling identifier is odd, the PDSCH is associated with the first TB. If the PDSCH scrambling identifier is even, the PDSCH is associated with the second TB.

[0167] In addition to the CDM group or TCI state of the PDSCH, other parameters or characteristics associated with the PDSCH, PDCCH, or DCI conveyed in the DCI can be used to associate the PDSCH with the TB (and therefore with the HARQ entry in the codebook). For example, the TCI state of the scheduling DCI can be used. Alternatively, an explicit bit in the DCI indicating the TB may be envisaged. The numbering of the PDCCH candidates in the search space (e.g., based on the first CCE used by the PDCCH) can be used to associate the scheduled PDSCH with the TB.

[0168] If only one PDCCH is received that schedules a PDSCH with two TBs, the Rel-15 behavior of mapping TB feedback to a position in the HARQ codebook is used.

[0169] Previously, it was assumed that at most one PDSCH from a TRP is received by the UE per slot. This can be relaxed in a similar way to Release 15, where each TRP is associated with a (same or different) PDSCH time domain resource allocation table. As in Release 15, this table overlaps for the UL symbol(s). PPruning is performed to remove overlapping entries with DSCH allocations. For each pruned entry, one HARQ entry is reserved. To extend this principle to multiple TRPs, the individual time domain resource allocation tables of both TRPs are combined to create a combined PDSCH time domain resource allocation table. For each element of this combined table, two entries (one for each TB) are reserved.

[0170] Joint A / N Feedback - Explicit Signaling: In this embodiment, it is assumed that the UE is explicitly signaled via higher layer signaling to use joint HARQ A / N feedback for multiple PDSCH transmissions over multiple TRPs with multiple PDCCHs. Each CORESET is configured with a higher layer configuration index. CORESETs with the same higher layer index form a CORESET group, and therefore the higher layer index becomes the CORESET group index. Each CORESET group is associated with one TRP. For two TRPs, two CORESET groups can be defined by using the higher layer index.

[0171] In this case, when two CORESET groups are configured for a UE within a CC, two TBs are used in constructing the Type 1 HARQ-ACK codebook for the CC. In this case, if maxNrofCodeWordsScheduledByDCI = 1 is configured, only one TB field is required in DCI format 1-1, thereby saving DCI overhead. When two PDSCHs, each carrying one TB and with overlapping TDRA, are received in a slot, the first and second TBs can be determined by the CORESET group index of the CORESET through which the corresponding PDCCH is received. For example, the first TB is associated with the first CORESET group index for the PDSCH scheduled by the PDCCH received in the CORESET, and the second TB is associated with the second CORESET group index for the PDSCH scheduled by the PDCCH received in the CORESET.

[0172] An example in which two CORESET groups are defined by higher layer signaling indexes is shown in Figure 17. Because PDCCH #1 is received in CORESET1 belonging to CORESET group 0, the first TB (TB1) is associated with PDSCH #1. Similarly, because PDCCH #2 is received in CORESET3 belonging to CORESET group 1, the second TB (TB2) is associated with PDSCH #2.

[0173] If maxNrofCodeWordsScheduledByDCI = 2 is configured and only one PDCCH scheduling a PDSCH is received with two codewords, the NR Release 15 behavior of mapping TB feedback to a position in the HARQ codebook is used. If maxNrofCodeWordsScheduledByDCI = 2 is configured, one TB is enabled, and one PDCCH scheduling a PDSCH is received, in one embodiment the NR Release 15 behavior of mapping TB feedback to a position in the HARQ codebook is used. Alternatively, the first or second TB is determined by the CORESET group index of the CORESET via which the corresponding PDCCH is received.

[0174] When one CORESET group is configured, the number of TBs for constructing the Type 1 HARQ-ACK codebook is determined according to the MIMO configuration maxNrofCodeWordsScheduledByDCI, and the legacy NR Release 15 behavior applies.

[0175] An example is shown in Figure 18, where the cell is configured with one TB (i.e., maxNrofCodeWordsScheduledByDCI = 1) and two CORESET groups. The HARQ-ACK codebook consists of two rows (for illustration purposes, the actual codebook is a long bit vector). Each row is associated with a TB scheduled by a PDCCH received in one of the two CORESET groups.

[0176] 19 is a schematic block diagram of a radio access node 1900 according to some embodiments of the present disclosure. The radio access node 1900 may be, for example, a base station 1002 or 1006. As shown, the radio access node 1900 has a control system 1902, which has one or more processors 1904 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 1906, and a network interface 1908. The one or more processors 1904 are also referred to herein as processing circuits. Additionally, the radio access node 1900 has one or more radio units 1910, each having one or more transmitters 1912 and one or more receivers 1914 coupled to one or more antennas 1916. The radio units 1910 may refer to or be part of radio interface circuitry. According to some embodiments, the radio unit 1910 is external to the control system 1902 and is connected to the control system 1902, for example, via a wired connection (e.g., an optical cable). However, according to some other embodiments, the radio unit(s) 1910 and potentially the antenna(s) 1916 are integrated with the control system 1902. The one or more processors 1904 operate to provide one or more functions of the radio access node 1900, as described herein. According to an embodiment, the functions are implemented in software that is stored, for example, in memory 1906 and executed by the one or more processors 1904.

[0177] 20 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1900 in accordance with some embodiments of the present disclosure. This description is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have a similar virtualization architecture.

[0178] As used herein, a “virtualized” radio access node is an implementation of a radio access node 1900 in which at least a portion of the functionality of the radio access node 1900 is implemented as virtual component(s) (e.g., via virtual machine(s) running on physical processing node(s) in network(s)). As shown, in this example, the radio access node 1900 has a control system 1902 and one or more radio units 1910, where the control system 1902 has one or more processors 1904 (e.g., CPU, ASIC, FPGA, etc.), memory 1906, and network interface 1908, as described above, and the radio units 1910 have one or more transmitters 1912 and one or more receivers 1914 coupled to one or more antennas 1916. The control system 1902 is connected to the radio unit(s) 1910 via, for example, an optical cable or the like. The control system 1902 is connected via a network interface 1908 to one or more processing nodes 2000 that are coupled to or incorporated as part of a network(s) 2002. Each processing node 2000 has one or more processors 2004 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 2006, and a network interface 2008.

[0179] In this example, the functionality 2010 of the radio access node 1900 described herein may be implemented in one or more processing nodes 2000, or may be distributed in any desired manner between the control system 1902 and one or more processing nodes 2000. According to some particular embodiments, some or all of the functionality 2010 of the radio access node 1900 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 2000. As will be appreciated by those skilled in the art, additional signaling or communication between the processing node 2000 and the control system 1902 may be used to perform at least some of the desired functionality 2010. Notably, according to some embodiments, the control system 1902 may not be included, in which case the radio unit 1910 communicates directly with the processing node 2000 via an appropriate network interface.

[0180] In some embodiments, a computer program product is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of the radio access node 1900, or a node (e.g., processing node 2000) that implements one or more functions 2010 of the radio access node 1900 in a virtual environment according to any of the embodiments described herein. According to some embodiments, a carrier is provided that carries the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0181] 21 is a schematic block diagram of a radio access node 1900 according to some other embodiments of the present disclosure. The radio access node 1900 comprises one or more modules 2100, each of which is implemented in software. The modules 2100 provide the functionality of the radio access node 1900 as described herein. This description is equally applicable to the processing node 2000 of FIG. 20, where the module 2100 may be implemented in one of the processing nodes 2000, or Complex The processing nodes 2000 may be distributed across multiple processing nodes 2000 and / or across processing nodes 2000 and control systems 1902.

[0182] 22 is a schematic block diagram of a UE 2200 according to some embodiments of the present disclosure. As shown, the UE 2200 includes one or more processors 2202 (e.g., a CPU, an ASIC, an FPGA, and / or the like), a memory 2204, and one or more transceivers 2206, each having one or more transmitters 2208 and one or more receivers 2210 coupled to one or more antennas 2212. The transceivers 2206 include radio front-end circuitry connected to the antennas 2212 configured to condition signals communicated between the antennas 2212 and the processor 2202, as will be understood by those skilled in the art. The processor 2202 is also referred to herein as a processing circuit. The transceiver 2206 is also referred to herein as a radio circuit. According to some embodiments, the functionality of the UE 2200 described above may be implemented, fully or partially, in software, for example, stored in the memory 2204 and executed by the processor 2202. The UE 2200 may include, for example, one or more user interface components (e.g., input / output interfaces including a display, buttons, a touch screen, a microphone, a speaker, etc.) and / or any other components for enabling input of information to the UE 2200 and / or output of information from the UE 2200, a power supply (e.g., batteryNote that the circuit may include additional components not shown in FIG. 22, such as a power supply (and associated power circuitry).

[0183] In some embodiments, a computer program product is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functions of the UE 2200 according to any of the embodiments described herein. According to some embodiments, a carrier is provided that carries the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0184] 23 is a schematic block diagram of a UE 2200 according to some other embodiments of the present disclosure. The UE 2200 includes one or more modules 2300, each implemented in software. The modules 2300 provide the functionality of the UE 2200 described herein.

[0185] Referring to Figure 24, according to an embodiment, a communications system includes a telecommunications network 2400, such as a 3GPP-type cellular network, including an access network 2402, such as a RAN, and a core network 2404. The access network 2402 has multiple base stations 2406A, 2406B, 2406C, such as NBs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area 2408A, 2408B, 2408C. Each base station 2406a, 2406b, 2406c can be connected to the core network 2404 via a wired or wireless connection 2410. A first UE 2412 located in the coverage area 2408c is configured to be wirelessly connected to or paged by the corresponding base station 2406c. A second UE 2414 within the coverage area 2408a can be wirelessly connected to the corresponding base station 2406a. Although multiple UEs 2412, 2414 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is present within the coverage area and is connected to a corresponding base station 2406.

[0186] The telecommunications network 2400 is itself connected to a host computer 2416, which may be implemented in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or processing resources within a server farm. The host computer 2416 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 2418 and 2420 between the communications network 2400 and the host computer 2416 may extend directly from the core network 2404 to the host computer 2416 or may go through any intermediate network 2422. The intermediate network 2422 may be one or a combination of public, private, or hosted networks, and the intermediate network 2422, if any, may be a backbone network or the Internet. In particular, the intermediate network 2422 may include two or more subnetworks (not shown).

[0187] The communication system of FIG. 24 generally provides connectivity between connected UEs 2412, 2414 and a host computer 2416. The connectivity may be described as an over-the-top (OTT) connection 2424. The host computer 2416 and connected UEs 2412, 2414 are configured to communicate data and / or signals via the OTT connection 2424 using the access network 2402, the core network 2404, any intermediate networks 2422, and possible further infrastructure (not shown) as intermediaries. The OTT connection 2424 may be transparent in the sense that participating communication devices through which the OTT connection 2424 passes are unaware of the routing of uplink and downlink communications. For example, the base station 2406 does not need to be informed of the past routing of incoming downlink communications with data originating from the host computer 2416 to be forwarded (e.g., handed over) to the connected UE 2412. Similarly, the base station 2406 does not need to be aware of the future routing of outgoing uplink communications from the UE 2412 towards the host computer 2416 .

[0188] In accordance with the UE, base station, and host computer embodiments discussed in the previous paragraphs, reference will now be made to Figure 25. In communication system 2500, host computer 2502 includes hardware 2504, which includes a communication interface 2506, which interfaces with various communication interfaces in communication system 2500. deviceThe host computer 2502 is configured to set up and maintain wired or wireless connections with the interface. The host computer 2502 further includes processing circuitry 2508, which may have storage and / or processing capabilities. In particular, the processing circuitry 2508 may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The host computer 2502 further includes software 2510, which is stored on or accessible to the host computer 2502 and executable by the processing circuitry 2508. The software 2510 includes a host application 2512. The host application 2512 may be operable to provide services to a remote user, such as a UE 2514, connecting via an OTT connection 2516 terminated at the host computer 2502. In providing services to the remote user, the host application 2512 may provide user data to be transmitted using the OTT connection 2516.

[0189] The communication system 2500 further includes a base station 2518 provided within the communication system and having hardware 2520 that enables communication with the host computer 2502 and the UE 2514. The hardware 2520 may be used to communicate with other communication systems of the communication system 2500. device25 )。 The base station 2518 may have a communication interface 2522 for setting up and maintaining wired or wireless connections with other interfaces, as well as a wireless interface 2524 for setting up and maintaining at least a wireless connection 2526 with UEs 2514 located in a coverage area (not shown in FIG. 25 ) served by the base station 2518. The communication interface 2522 may be configured to facilitate a connection 2528 to the host computer 2502. The connection 2528 may be direct, may pass through a core network of the communication system (not shown in FIG. 25 ), and / or may pass through one or more intermediate networks external to the communication system. According to the illustrated embodiment, the hardware 2520 of the base station 2518 further includes processing circuitry 2530, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Additionally, the base station 2518 includes software 2532 stored internally or accessible via an external connection.

[0190] The communications system 2500 further includes the previously mentioned UE 2514. The hardware 2534 of the UE 2514 may include a wireless interface 2536 configured to set up and maintain a wireless connection 2526 with a base station serving the coverage area in which the UE 2514 is currently located. The hardware 2534 of the UE 2514 further includes processing circuitry 2538, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The UE 2514 further includes software 2540, which may be stored within or accessible to the UE 2514 and executable by the processing circuitry 2538. The software 2540 includes a client application 2542. The client application 2542, with support from the host computer 2502, is operable to provide services to a human or non-human user via the UE 2514. In the host computer 2502, a running host application 2512 may communicate with a running client application 2542 via an OTT connection 2516 terminating at the UE 2514 and the host computer 2502. In providing services to a user, the client application 2542 receives requests from the host application 2512. request Receive the data, request The client application 2542 may interact with the user and generate the user data provided by the user.

[0191] It should be noted that the host computer 2502, base station 2518, and UE 2514 shown in Figure 25 may be similar to or identical to the host computer 2416, one of the base stations 2406A, 2406B, 2406C, and one of the UEs 2412, 2414 of Figure 24, respectively. That is, the internal operation of these entities may be as shown in Figure 25 or may be independent therefrom, and the surrounding network topology may be that of Figure 24.

[0192] 25, the OTT connection 2516 is depicted abstractly to show communication between the host computer 2502 and the UE 2514 via the base station 2518, and the precise routing of messages through these devices, without explicit reference to any intermediate devices. The network infrastructure may make routing decisions that may be configured to hide them from the UE 2514, from the service provider operating the host computer 2502, or both. While the OTT connection 2516 is active, the network infrastructure may further decide to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0193] The wireless connection 2526 between the UE 2514 and the base station 2518 follows the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2514 using the OTT connection 2516, of which the wireless connection 2526 forms the final leg. More precisely, the teachings of these embodiments may improve, for example, data rates, latency, power consumption, etc., thereby providing benefits such as reduced user latency, relaxed file size restrictions, better responsiveness, and extended battery life.

[0194] A measurement procedure may be provided to monitor data rates, latencies, and other factors that are improved by one or more embodiments. Furthermore, depending on the variability of the measurement results, the host computer 2502 and UE There may be optional network functionality for reconfiguring the OTT connection 2516 between the host computer 2502 and the UE 2514. The measurement procedures and / or network functionality for reconfiguring the OTT connection 2516 may be implemented in the software 2510 and hardware 2504 of the host computer 2502, or in the software 2540 and hardware 2534 of the UE 2514, or both. In some embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 2516 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities from which the software 2510, 2540 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2516 may include changes to message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 2518 and may be unknown or imperceptible to the base station 2518. Such procedure The measurements and functionality may be those known and practiced in the art. According to some embodiments, measurements may have unique UE signaling that facilitates measurements of host computer 2502 throughput, propagation time, latency, etc. Measurements may be performed by having software 2510 and 2540 send messages, particularly empty or "dummy" messages, using OTT connection 2516 while monitoring propagation time, errors, etc.

[0195] FIG. 26 is a flowchart illustrating a method performed in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 24 and 25. To simplify this disclosure, only the drawings that reference FIG. 26 are included in this section. In step 2600, the host computer provides user data. In sub-step 2602 of step 2600 (which may be optional), the host computer provides the user data by executing a host application. In step 2604, the host computer initiates a transmission carrying the user data to the UE. In step 2606 (which may be optional), the base station transmits the user data carried in the host computer-initiated transmission to the UE, in accordance with the teachings of embodiments described throughout this disclosure. In step 2608 (which may be optional), the UE executes a client application associated with the host application executed by the host computer.

[0196] FIG. 27 is a flowchart illustrating a method performed in a communication system, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 24 and 25. To simplify this disclosure, only the drawings that reference FIG. 27 are included in this section. In step 2700 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 2702, the host computer initiates a transmission carrying the user data to the UE. The transmitted signal may be passed through the base station in accordance with the teachings of the embodiments described throughout this disclosure. In step 2704 ( option In the transmission signal, the UE receives user data carried by the transmission signal.

[0197] FIG. 28 is a flowchart illustrating a method performed in a communications system according to one embodiment. The communications system includes a host computer, a base station, and a UE, which may be as described with reference to FIGS. 24 and 25. To simplify this disclosure, only the drawings that refer to FIG. 28 are included in this section. In step 2800 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2802, the UE provides user data. In sub-step 2804 (which may be optional) of step 2800, the UE provides the user data by executing a client application. In sub-step 2806 (which may be optional) of step 2802, the UE executes the client application, which provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE: It may be an option Sub-step 2808 initiates transmission of user data to the host computer. In method step 2810, the host computer receives the user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0198] Figure 29 is a flow chart illustrating a method performed in a communication system, according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to Figures 24 and 25. To simplify this disclosure, only the figures that reference Figure 29 are included in this section. In step 2900 (which may be optional), the base station receives user data from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2902 (which may be optional), Even if there is In step 2904 ( option In a transmission initiated by the base station, the host computer receives user data carried in the transmission.

[0199] Any suitable step, method, feature, function, or benefit disclosed herein may be performed via one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. The processing circuitry may include: Read-only The functional units may be configured to execute program code stored in the memory, which may have one or more types of memory such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory has program instructions for implementing one or more communication and / or data communication protocols, as well as instructions for performing one or more of the techniques described herein. In some implementations, processing circuitry may be used to cause each functional unit to perform a function corresponding to the respective functional unit in accordance with one or more embodiments of the present disclosure.

[0200] While processes in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.). Additionally, throughout the disclosure, the term "embodiment" may be understood to be interchangeable with the term "aspect."

[0201] Embodiment

[0202] Group A Embodiments

[0203] Embodiment 1: A method performed by a wireless device for providing transmission feedback, the method comprising: receiving a first TB (Transport Block) and a second TB; and determining the first TB and the second TB based on one or more of the group consisting of: corresponding Downlink Control Information (DCI) scheduling the TB; (DCI) ), as indicated by the option i. a DMRS (Demodulation Reference Signal) CDM (Code Division Multiplexing) group identifier for one or more DMRS ports; and ii. T B identifier; iii. a group identifier of a CORESET of a CORESET (Control Resource Set), optionally a group identifier of a CORESET via which a corresponding DCI scheduling the TB is received; iv. a TCI (Transmission Configuration Indication) state identifier, optionally a TCI state identifier indicated in the corresponding DCI scheduling the TB; v. a TCI state identifier of a CORESET, optionally a TCI state identifier via which a corresponding DCI scheduling the TB is received; and vi. a scrambling identifier of a PDSCH (Physical Downlink Shared Channel) carrying the TB.

[0204] Embodiment 2: The method of embodiment 1 further includes receiving, in a serving cell, a configuration including a set of PDSCH-to-HARQ (Hybrid Automatic Repeat Request) feedback timing K1 values ​​per slot and / or a list of PDSCH time domain resource allocations before receiving the first TB and the second TB.

[0205] Embodiment 3: The method of any one of embodiments 1 to 2, further comprising receiving, before receiving the first TB and the second TB, an indication to allocate two entries, a first entry and a second entry, to a Type-1 HARQ codebook for each of the configured K1 values ​​and each of the sets of overlapping PDSCH time domain resource allocations.

[0206] Embodiment 4: The method of any one of embodiments 1 to 3, further comprising: mapping HARQ-ACK bits for the first TB to the first entry and mapping HARQ-ACK bits for the second TB to the second entry, wherein the first entry and the second entry in the Type 1 HARQ-ACK codebook are associated with the same K1 value and the same time domain resource allocation.

[0207] Embodiment 5: The method of any one of embodiments 1 to 4, further comprising reporting the constructed Type-1 HARQ codebook.

[0208] Embodiment 6: A method according to any one of embodiments 1 to 5, wherein receiving the first TB and the second TB includes receiving the first TB from a first TRP and receiving the second TB from a second TRP in a slot, and the first TB and the second TB are scheduled using two DCIs, one for each TB, and using the same K1 value and the same time domain resource allocation.

[0209] Embodiment 7: The method of any one of embodiments 3 to 6, wherein receiving the indication to allocate two entries is either explicit or implicit.

[0210] Embodiment 8: The method of embodiment 7, wherein receiving the indication to allocate two entries includes receiving one or more of: a. an upper layer parameter maxNrofCodeWordsScheduledByDCI = 2; b. an upper layer parameter indicating joint HARQ ACK feedback; and c. a configuration of two CORESET groups, each having a different group identifier value per CORESET for HARQ-Ack reporting; and

[0211] Embodiment 9: The method according to any one of embodiments 1 to 8, wherein the first entry or the second entry is filled with a NACK when the first TB or the second TB is not received, respectively.

[0212] Embodiment 10: The method according to any one of embodiments 1 to 9, wherein the transmitting may further include transmitting one or two TBs scheduled by a single DCI.

[0213] Embodiment 11: The method of any one of embodiments 1 to 10, wherein the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2 as indicated in the DCI.

[0214] Embodiment 12: The method according to any one of embodiments 1 to 11, wherein the wireless device is a UE (User Equipment) of NR (New Radio).

[0215] Embodiment 13: The method of any of the preceding embodiments, further comprising providing user data and transferring the user data to the host computer via transmission to the base station.

[0216] Group B Embodiments

[0217] Embodiment 14: A method performed by a base station for receiving transmission feedback, the method comprising: transmitting a first TB (Transport Block) and a second TB to a wireless device; and receiving a constructed type-1 Hybrid Automatic Repeat Request (HARQ) codebook from the wireless device.

[0218] Embodiment 15: The method of embodiment 14, further comprising transmitting, to the wireless device, a configuration with a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time domain resource allocations per slot in the serving cell before transmitting the first TB and the second TB.

[0219] Embodiment 16: The method of any one of embodiments 14 to 15, further comprising: before transmitting the first TB and the second TB, transmitting an indication to the wireless device to allocate two entries, a first entry and a second entry, in a Type 1 HARQ codebook for each of the configured K1 values ​​and each of the overlapping PDSCH time domain resource allocation sets.

[0220] Embodiment 17: A method according to any one of embodiments 14 to 16, wherein transmitting the first TB and the second TB comprises transmitting the first TB from a first TRP and transmitting the second TB from a second TRP, and the first TB and the second TB are scheduled using two DCIs, one for each TB, and using the same K1 value and the same time domain resource allocation.

[0221] Embodiment 18: The method according to any one of embodiments 14 to 17, wherein sending the indication to allocate two entries may be either explicit or implicit.

[0222] Embodiment 19: The method of embodiment 18, wherein transmitting the indication to allocate two entries includes transmitting one or more of: a. an upper layer parameter maxNrofCodeWordsScheduledByDCI = 2; b. an upper layer parameter indicating joint HARQ ACK feedback, and a configuration of two CORESET groups each having a different group identifier value per CORESET for HARQ-Ack reporting; and c. a configuration of one CORESET group each having the same group identifier value per CORESET for HARQ-Ack reporting.

[0223] Embodiment 20: The method of any one of embodiments 14 to 19, wherein the first entry or the second entry is filled with a NACK if the first TB or the second TB is not received, respectively.

[0224] Embodiment 21: The method of any one of embodiments 14 to 20, wherein the transmitting further comprises transmitting one or two TBs scheduled by a single DCI.

[0225] Embodiment 22: The method of any one of embodiments 14 to 21, wherein the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2 as indicated in the DCI.

[0226] Embodiment 23: The method according to any one of embodiments 14 to 22, wherein the base station is a New Radio (NR) gNB.

[0227] Embodiment 24: The method of any of the preceding embodiments, further comprising obtaining user data and transferring the user data to a host computer or a wireless device.

[0228] Group C Embodiments

[0229] Embodiment 25: A wireless device for providing transmission feedback, the wireless device having a processing circuit configured to perform any step in any of the embodiments of Group A, and a power supply circuit configured to provide power to the wireless device.

[0230] Embodiment 26: A base station for receiving transmission feedback, the base station having processing circuitry configured to perform any step in any of the embodiments of Group B, and power supply circuitry configured to provide power to the base station.

[0231] Embodiment 27: A UE (User Equipment) for providing transmission feedback, the UE having an antenna configured to transmit and receive radio signals, a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit configured to perform any of the steps in any of the embodiments of Group A, an input interface connected to the processing circuit and configured to enable input of information into the UE to be processed by the processing circuit, an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE, and a battery connected to the processing circuit and configured to provide power to the UE.

[0232] Embodiment 28: A communications system comprising a host computer, the host computer having processing circuitry configured to provide user data and a communications interface configured to transfer the user data to a cellular network for transmission to a UE (User Equipment), the cellular network having a base station, the base station having a radio interface and processing circuitry, the processing circuitry of the base station configured to perform any step in any of the Group B embodiments.

[0233] Embodiment 29: The communication system of the above embodiment, further comprising the base station.

[0234] Embodiment 30: The communication system of the previous two embodiments, further comprising the UE, wherein the UE is configured to communicate with the base station.

[0235] Embodiment 31: The communication system of any of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide the user data, and the UE has processing circuitry configured to execute a client application associated with the host application.

[0236] Embodiment 32: A method performed in a communications system having a host computer, a base station, and a UE (user equipment), the method comprising: providing user data at the host computer; and initiating transmission at the host computer carrying the user data to the UE over a cellular network including the base station, the base station performing any of the steps in any of the Group B embodiments.

[0237] Embodiment 33: The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

[0238] Embodiment 34: The method of the previous two embodiments, comprising: before The user data is provided at the host computer by executing the host application, and the method further includes executing at the UE a client application associated with the host application.

[0239] Embodiment 35: A UE (User Equipment) configured to communicate with a base station, said UE having a radio interface and processing circuitry configured to perform the methods of the previous three embodiments.

[0240] Embodiment 36: A communication system including a host computer having a processing circuit configured to provide user data and a communication interface configured to transfer the user data to a cellular network for transmission to a UE (User Equipment), the UE having a wireless interface and a processing circuit, and components of the UE configured to perform any step in any of the embodiments of Group A.

[0241] Embodiment 37: The communication system of the previous embodiment, wherein the cellular network further comprises a base station configured to communicate with the UE.

[0242] Embodiment 38: The communication system of the two preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide the user data, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0243] Embodiment 39: A method performed in a communication system having a host computer, a base station, and a UE (user equipment), the method comprising: providing user data at the host computer; and initiating transmission at the host computer carrying the user data to the UE via a cellular network including the base station, the UE performing any of the steps in any of the embodiments of Group A.

[0244] Embodiment 40: The method of the previous embodiment, further comprising receiving, at the UE, the user data from the base station.

[0245] Embodiment 41: A communications system including a host computer having a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the UE having a radio interface and processing circuitry, the processing circuitry of the UE configured to perform any step in any of the embodiments of Group A.

[0246] Embodiment 42: The communication system of the previous embodiment, further comprising the UE.

[0247] Embodiment 43: The communication system of the two preceding embodiments, further comprising the base station, wherein the base station has a radio interface configured to communicate with the UE and a communication interface configured to transfer the user data carried by a transmission signal from the UE to the base station to the host computer.

[0248] Embodiment 44: The communication system of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing the user data.

[0249] Embodiment 45: The communication system of any of the preceding four embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing request data, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing user data in response to the request data.

[0250] Embodiment 46: A method performed in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising receiving, at the host computer, user data transmitted from the UE to the base station, wherein the UE performs any step in any of the embodiments of Group A.

[0251] Embodiment 47: The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

[0252] Embodiment 48: The method of the previous two embodiments, further comprising: executing, at the UE, a client application thereby providing the user data to be transmitted; and executing, at the host computer, a host application associated with the client application.

[0253] Embodiment 49: The method of embodiment 3 further includes executing a client application at the UE and receiving input data for the client application at the UE, the input data being provided at the host computer by executing a host application associated with the client application, and the user data to be transmitted being provided by the client application in response to the input data.

[0254] Embodiment 50: A communications system including a host computer having a communications interface configured to receive user data derived from a transmission signal from a user equipment (UE) to a base station, the base station having a radio interface and processing circuitry, the processing circuitry of the base station configured to perform any step in any of the Group B embodiments.

[0255] Embodiment 51: The communication system of the above embodiment further comprises the base station.

[0256] Embodiment 52: The communication system of the previous two embodiments, further comprising the UE, wherein the UE is configured to communicate with the base station.

[0257] Embodiment 53: The communication system of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0258] Embodiment 54: A method performed in a communication system having a host computer, a base station, and a UE (user equipment), the method comprising receiving, at the host computer, user data from the base station derived from a transmission signal received by the base station from the UE, the UE performing any of the steps in any of the embodiments of Group A.

[0259] Embodiment 55: The method of the previous embodiment, further comprising receiving, at the base station, the user data from the UE.

[0260] Embodiment 56: The method of the previous two embodiments, further comprising initiating, at the base station, transmission of the received user data to the host computer.

[0261] In this disclosure, at least some of the following abbreviations may be used: In the event of a discrepancy between abbreviations, how it is used above shall prevail. If listed multiple times below, the first listing shall take precedence over any subsequent listings. 3GPP: Third Generation Partnership Project 5G: Fifth generation 5GC: Fifth Generation Core 5GS: Fifth Generation System ACK: Acknowledgement AF: Application Features AMF: Access and Mobility Features AN: Access Network AP: Access Point ASIC: Application Specific Integrated Circuit AUSF: Authentication Server Function CA: Carrier Aggregation CBG: Code Block Group CC: Component Carrier CCE: Control Channel Element CDM: Code Division Multiplexing CORESET: Control resource set CP-OFDM: Cyclic prefix-orthogonal frequency division multiplexing CPU: Central Processing Unit CRC: Cyclic Redundancy Check C-RNTI: Cell-Radio Network Temporary Identifier CSI-RS: Channel State Information-Reference Signal CS-RNTI: Configured Scheduling-Radio Network Temporary Identifier CSS: Common Search Space CW: Codeword DAI: Downlink Allocation Index DCI: Downlink Control Information DFT: Discrete Fourier Transform DL: Downlink DMRS: Demodulation Reference Signal DN: Data Network DSP: Digital Signal Processor eMBB: Enhanced Broadband eNB: Enhanced or evolved Node B FPGA: Field Programmable Gate Array FR: Frequency Range gNB: New Radio Base Station HARQ: Hybrid Automatic Repeat Request HSS: Home Subscriber Server IE: Information Element IP: Internet Protocol LTE: Long Term Evolution MCS: Modulation and Coding Scheme MIMO: Multiple Input Multiple Output MME: Mobility Management Entity MTC: Machine Type Communication NC-JT: Non-coherent joint transmission NDI: New Data Indicator NEF: Network Publishing Facility NF: Network Function NR: New Radio NRF: Network Repository Facility NSSF: Network Slice Selection Function OTT: Over-the-top PCF: Policy Control Facility PDCCH: Physical Downlink Control Channel PDSCH: Physical Downlink Shared Channel P-GW: Packet Data Network Gateway PRB: Physical Resource Block PRI: PUCCH resource indicator PUCCH: Physical Uplink Control Channel PUSCH: Physical Uplink Shared Channel QCL: Quasi-colocated QoS: Quality of Service RAM: Random Access Memory RAN: Radio Access Network RB: Resource Block RE: Resource element REG: Resource Element Group ROM: Read-Only Memory RRC: Radio Resource Control RRH: Remote Radio Head RTT: Round Trip Time SCEF: Service Capability Exposure Function SINR: Signal to Interference Plus Noise Ratio SMF: Session management function SR: Scheduling Request SSB: Synchronization signal block TB: Transport Block TCI: Transmit Configuration Indication TDD: Time division duplex method TDM: Time division multiplexing TDRA: Time Domain Resource Allocation TPC: Transmit Power Control TRP: Transmit / Receive Point (Transmit / Receive Point) TRS: Tracking Reference Signal UCI: Uplink Control Information UDM: Unified Data Management UE: User Equipment UL: Uplink UPF: User Plane Function USS: UE specific search space VRB: Virtual Resource Block ZP: Zero Power

[0262] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

[Claim 1] 1. A method performed by a wireless device for enabling transmission feedback, the method comprising: receiving 1302 a configuration including a set of PDSCH-to-HARQ (Physical Downlink Shared Channel to Hybrid Automatic Repeat Request) feedback timing K1 values ​​and a list of PDSCH time domain resource allocations for each slot in a serving cell, and receiving a first TB (Transport Block) and a second TB (Transport Block) in a first and a second PDSCH in the serving cell, respectively, after receiving an explicit indication allocating two entries, a first entry and a second entry, in a Type-1 HARQ-ACK codebook for each configured K1 value and each set of overlapping PDSCH time domain resource allocations; determining the first TB and the second TB based on a CORESET group identifier of a CORESET (Control Resource Set) in which corresponding DCIs (Downlink Control Information) scheduling the first TB and the second TB are received, and mapping HARQ-ACK bits of the first TB to the first entry and HARQ-ACK bits of the second TB to the second entry in the Type-1 HARQ-ACK codebook associated with the same K1 value and the same or overlapping PDSCH time domain resource allocation (1304); Receiving the first TB and the second TB includes receiving, within the slot, the first TB scheduled by a first DCI from a first transmit reception point (TRP) represented by a first CORESET group identifier, and the second TB scheduled by a second DCI from a second TRP represented by a second CORESET group identifier, wherein the first TB and the second TB have the same or the overlapping time domain resource allocation and the same K1 value.

Images