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

Abstract

A system and method are provided for joint hybrid automatic repeat request (HARQ) feedback for Physical Downlink Shared Channel (PDSCH) transmissions across multiple Transmission Routers (TRPs). In some embodiments, the method for implementing transmission feedback, performed by a wireless device, 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) that schedules the received downlink control information (DCI). In this way, the New Radio (NR) Rel-15 procedure for constructing a Type 1 HARQ codebook can be reused with a semi-static HARQ-ACK codebook with the same or minimal increase in HARQ feedback overhead.

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application serial number 62 / 866408, filed on June 26, 2019, the disclosure of which is incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to Hybrid Automatic Repeat Request (HARQ) feedback. Background Technology

[0004] New Radio (NR) uses Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) in both the downlink (i.e., from network nodes, NR base stations (gNBs), or base stations to user equipment (UEs)) and uplink (i.e., from UEs to gNBs). Discrete Fourier Transform (DFT) Extended OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into 1ms subframes of equal size. Subframes are further divided into multiple time slots of equal duration. The time slot length depends on the subcarrier spacing. For a subcarrier spacing of ∆f = 15kHz, each subframe has only one time slot, and each time slot consists of 14 OFDM symbols.

[0005] Data scheduling in NR is typically based on time slots. Figure 1 An example with 14-symbol time slots is shown, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the remaining symbols contain the Physical Shared Data Channel—either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0006] NR supports different subcarrier spacing values. The supported subcarrier spacing values ​​(also known as different parameter sets) are determined by... Given, among which ∆f = 15kHz is the basic subcarrier spacing. The time slot duration under different subcarrier spacings is determined by... Provided.

[0007] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. RBs are numbered starting from 0, beginning at one end of the system bandwidth. The basic NR physical time-frequency resource grid is as follows: Figure 2 As shown, only one resource block (RB) within a 14-symbol slot is illustrated. One OFDM subcarrier during an OFDM symbol interval forms one resource element (RE).

[0008] Downlink transmission is dynamically scheduled; that is, in each time slot, the gNB transmits downlink control information (DCI) on the PDCCH, which specifies which UE will receive data and on which RBs in the current downlink time slot. UE data is carried on the PDSCH.

[0009] Two DCI formats are defined for scheduling PDSCH in NR: DCI format 1_0 and DCI format 1_1. DCI format 1_0 has a smaller size than DCI 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 with two transport blocks (TB).

[0010] QCL and TCI states: Several signals can be transmitted from different antenna ports of the same base station antenna. When these signals are received at the UE, they may have the same large-scale properties, such as in terms of Doppler shift and Doppler spread, average delay spread, or average delay. These antenna ports are called quasi-co-located (QCL). Typically, two quasi-co-located antenna ports are not necessarily physically quasi-co-located.

[0011] If the UE knows the QCL of two antenna ports relative to a certain parameter (e.g., Doppler spread), the UE can estimate that parameter based on one antenna port and use that estimate when receiving 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 a Synchronization Signal Block (SSB) (called the source RS), and the second antenna port is represented by a Demodulation Reference Signal (DMRS) (called the target RS).

[0012] For example, if antenna ports A and B are QCL with respect to the average delay, the UE can estimate the average delay based on the signal received from antenna port A (called 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 when attempting to measure the channel using DMRS, the UE can know the channel properties in advance, which can help the UE, for example, select a suitable channel estimation filter.

[0013] The network signals to the UE information about what assumptions can be made regarding QCL. In NR, four types of QCL relationships are defined between the source RS and the destination RS:

[0014] • Class A: {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0015] • Class B: {Doppler shift, Doppler spread}

[0016] • Class C: {Average Delay, Doppler Shift}

[0017] • Type D: {Space Rx parameter}

[0018] QCL type D was introduced to facilitate beam management using analog beamforming at higher carrier frequencies (e.g., 30 GHz) and was referred to as spatial QCL. Currently, there is no strict definition of spatial QCL, but it is understood that if two transmit antenna ports are in spatial QCL, the UE can use the same Rx beam to receive them. Note that for beam management, the discussion mainly revolves around QCL type D, but it is also necessary to convey the RS type A QCL relationship to the UE so that it can estimate all relevant large-scale parameters.

[0019] Typically, this is achieved by configuring a CSI-RS (TRS) for tracking time / frequency offset estimation for the UE. In order to use any QCL reference, the UE must 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 UE within the appropriate beam.

[0020] To introduce dynamism in beam and transmit receive point (TRP) selection, the UE can be configured via 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's capabilities.

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

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

[0023] A first list of available TCI states is configured for PDSCH, and a second list for PDCCH contains pointers to a subset of TCI states configured for PDSCH, referred to as TCI state IDs. The network then activates one TCI state for PDCCH (i.e., provides TCI for PDCCH) and up to eight active TCI states for PDSCH. The number of active TCI states supported by a UE is a UE capability, but the maximum is eight. The TCI states(s) used for PDSCH are dynamically indicated in DCI 1_1.

[0024] Each configured TCI state contains parameters for quasi-co-address association between the source reference signal (CSI-RS or Synchronization Signal Block (SSB)) and the target reference signal (e.g., PDSCH / PDCCH DMRS port). The TCI state is also used to transmit QCL information to receive CSI-RS.

[0025] CORESET and Search Space: The PDCCH consists of one or more Control Channel Elements (CCEs), as shown in Table 1 below. Each CCE consists of six Resource Groups (REGs), where a REG is equal to one RB during one OFDM symbol period.

[0026] Table 1: PDCCH aggregation levels supported by NR.

[0027]

[0028] The PDCCH search space set defines the set of PDCCH candidates for the UE to monitor. The search space set can be a common search space (CSS) set or a UE-specific search space (USS) set. Up to 10 search space sets per bandwidth segment can be configured for the UE to monitor PDCCH candidates.

[0029] The search space set is defined on the control resource set (CORESET). CORESET is composed of resources in the frequency domain. In each resource block and time domain It consists of {1, 2, 3} consecutive OFDM symbols. In NR Rel-15, the UE can be configured with up to 3 CORESETs per bandwidth portion. For each CORESET, the UE is configured by Radio Resource Control (RRC) signaling with CORESET Information Elements (IEs), including the following:

[0030] • CORESET Index p , ;

[0031] • Initialization values ​​for the DM-RS scrambling sequence;

[0032] • Precoder granularity of multiple REGs in the frequency domain, where the UE can assume that the same DM-RS (demodulation reference signal) precoder is used;

[0033] • Multiple consecutive symbols;

[0034] • A set of resource blocks;

[0035] • CCE to REG mapping parameters;

[0036] • A list of up to 64 TCI states can be configured in CORESET p. These TCI states are used to provide the QCL relationship between one or more source DL RSs in a set of RSs in the TCI state and the PDCCH DMRS ports (i.e., the DMRS ports used for PDCCH received in one of the search spaces defined on CORESET p). The one or more source DL RSs can be CSI-RS or SSB;

[0037] • An indication of whether the Transmission Configuration Indicator (TCI) field of DCI format 1_1 transmitted by PDCCH in CORESET p exists or does not exist.

[0038] For each search space set, the UE is configured with the following items:

[0039] • Search space set indexes s,

[0040] • The association between the search space set s and CORESET p

[0041] • k s The PDCCH monitoring cycle and o in each time slot s PDCCH monitoring offset in each time slot

[0042] • The PDCCH monitoring mode within a time slot indicates the first symbol(s) of CORESET(s) within the time slot used for PDCCH monitoring.

[0043] •T s < k s The duration of each time slot indicates the number of time slots in which the search space set s exists.

[0044] • Multiple PDCCH candidates for each CCE aggregation level L

[0045] • Indicator of whether the search space set 's' is a CSS set or a USS set

[0046] •DCI format to monitoring

[0047] For the search space set s, if Then the UE determines that it has a frame number The frame with time slot number There are one or more PDCCH monitoring opportunities within the time slot. From the time slot Initially, UE targets T s The search space set s of consecutive time slots is monitored for PDCCH, and not for the next k s -T s The search space set s of consecutive time slots is used to monitor PDCCH.

[0048] The UE first detects and decodes the PDCCH. If decoding is successful, it decodes the corresponding PDSCH based on the decoded control information in the PDCCH. When 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 so that data can be retransmitted to the UE. If the PUCCH and PUSCH transmissions overlap, the HARQ feedback can also be transmitted on the PUSCH.

[0049] Uplink data transmission also uses PDCCH dynamic scheduling. Similar to the downlink, the UE first decodes the uplink grant in the PDCCH, and then transmits data through PUSCH based on the decoded control information in the uplink grant, such as modulation order, coding rate, uplink resource allocation, etc.

[0050] DCI format 1-1 is used for PDSCH scheduling within a cell. The following information is transmitted via DCI format 1-1 with Cyclic Redundancy Check (CRC), which is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI), the Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI), or the Modulation and Coding Scheme (MCS)-C-RNTI:

[0051] • Identifier in DCI format

[0052] • Carrier indicator

[0053] • Bandwidth indicator

[0054] • Frequency domain resource allocation

[0055] • Time Domain Resource Assignment (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 follows: The value of I is the number of entries in the higher-level parameter pdsch-TimeDomainAllocationList if a higher-level parameter is configured; otherwise, I is the number of entries in the default table.

[0056] • Virtual Resource Block (VRB) to Physical Resource Block (PRB) Mapping

[0057] •PRB Bundle Size Indicator

[0058] • Rate Matching Indicator

[0059] • Zero Power (ZP) CSI-RS Trigger

[0060] For transport block 1:

[0061] • Modulation and coding scheme – 5-bit (I MCS )

[0062] • New Data Indicator (NDI) – 1 bit

[0063] • Redundant version – 2 bits (rv) id )

[0064] For transport block 2 (exists only if maxNrofCodeWordsScheduledByDCI equals 2):

[0065] • Modulation and coding scheme – 5-bit (I MCS )

[0066] • New Data Indicator (NDI) – 1 bit

[0067] • Redundant version – 2 bits (rv) id )

[0068] • HARQ process number

[0069] • Downlink Assignment Index (DAI)

[0070] • Transmit Power Control (TPC) commands used to schedule PUCCH

[0071] • PUCCH resource indicator (PRI)

[0072] • PDSCH to HARQ_feedback timing indicator (K1) – 0, 1, 2, or 3 bits, as defined in section 9.2.3 of 3GPP TS 38.213. The bit width of this field is determined as follows: Bit, where I is the number of entries in the higher-level parameter dl-DataToUL-ACK.

[0073] • (One or more) antenna ports – 4, 5, or 6 bits, as defined in Tables 7.3.1.2.2-1 / 2 / 3 / 4 of 3GPP TS38.212.

[0074] • Transport Configuration Indicator (TCI) – 0 bits, if the higher-layer parameter tci-PresentInDCI is not enabled; otherwise, 3 bits as defined in section 5.1.5 of 3GPP TS38.214.

[0075] • Request for reference signal detection

[0076] • Code Block Group (CBG) transmission information

[0077] • CBG dump clear information

[0078] • DMRS sequence initialization – 1 bit.

[0079] PDSCH resource allocation in the time domain

[0080] When a UE is scheduled to receive PDSCH via DCI, the Time Domain Resource Assignment (TDRA) field value m of the DCI provides a row index m+1 to the allocation table. The determination of the resource allocation table used is defined in subclause 5.1.2.1.1 of 3GPP TS38.214 v15.5.0, where the default PDSCH time domain allocation A, B, or C is applied according to tables 5.1.2.1.1-2, 5.1.2.1.1-3, 5.1.2.1.1-4, and 5.1.2.1.1-5, or the parameter pdsch-TimeDomainAllocationList configured in higher-level pdsch-ConfigCommon or pdsch-Config is applied. Table 5.1.2.1.1-2 of 3GPP TS38.214 v15.5.0 is copied below.

[0081] Table 5.1.2.1.1-2: Default PDSCH time-domain resource allocation A for normal CP

[0082]

[0083] When using the default table, the indexed rows define the slot offset K0, the start symbol S, and the allocation length L, as well as the PDSCH mapping type assumed at the time of PDSCH reception. Type A (i.e., slot-based PDSCH transmission) or Type B (i.e., micro-slot-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 allocation length L are jointly encoded in startSymbolAndLength as a start and length indicator SLIV.

[0084]

[0085] Valid S and L values ​​are shown in the table below.

[0086] Table 5.1.2.1-1: Valid S and L combinations (3gpp TS38.214 v15.5.0)

[0087]

[0088] Note that for Class A PDSCHs, the TDRAs in the pdsch-TimeDomainAllocationList or the default table are overlapping, and only one PDSCH can be scheduled per cell per time slot in NR version 15. For Class B PDSCHs, the TDRAs in the pdsch-TimeDomainAllocationList or the default table can be non-overlapping, so more than one PDSCH can be scheduled in a time slot. Figure 3 shows some examples where... Figure 3 In D, two Class B PDSCHs are scheduled in a time slot.

[0089] NR MIMO Data Transmission: Figure 4 illustrates NR data transmission over multiple MIMO layers. Depending on the total number or rank of the MIMO layers, one codeword (CW) or two codewords are used. In NR version 15, one codeword is used when the total number of layers is equal to or less than 4, and two codewords are used when the number of layers is greater than 4. Each codeword contains the encoded data bits (TB) of the transport block. After bit-level scrambling, for codeword q( The scrambled bits are mapped to complex-valued modulation symbols. Then, according to Table 7.3.1.3-1 of 3GPP TS 38.211 v15.5.0, complex-valued modulation symbols are mapped to layers. superior.

[0090] For demodulation purposes, a demodulation reference signal (DMRS), also known as a DMRS port, is transmitted along each data layer. Vector block The following equation should be used to map to the DMRS antenna port:

[0091]

[0092] in According to Tables 7.3.1.2.2-1 / 2 / 3 / 4 in 3GPP TS 38.212 v15.5.0, the DMRS antenna port set is dynamically indicated in the DCI. And port to layer mapping.

[0093] The maximum number of TBs or codewords that can be scheduled in DCI format 1-1 is configured by the higher-level parameter `maxNrofCodeWordsScheduledByDCI`. This parameter allows you to configure one or two codewords. If the higher-level parameter `maxNrofCodeWordsScheduledByDCI` indicates that two codeword transmissions are enabled, then if I... MCS = 26 and if for the corresponding transport block rv id = 1, then one of the two transport blocks is disabled via DCI format 1-1, where I MCS It is the MCS (Modulation and Coding Scheme) index and rv id This is a redundant version, as indicated in DCI 1_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.

[0094] DMRS Code Division Multiplexing (CDM) Groups: The mapping from DMRS to resource elements can be configured in both the frequency and time domains. There are two mapping types in the frequency domain: configuration type 1 or type 2. For each OFDM symbol configured for DMRS, there are two CDM groups for type 1 and three CDM groups for type 2 DMRS. Figure 5 An example is shown where a front DMRS symbol is configured.

[0095] The DMRS port to CDM group mappings are shown in Tables 2 and 3 for configuration type 1 and type 2, respectively.

[0096] Table 2: PDSCH DMRS port to CDM group mapping, configuration type 1.

[0097]

[0098] Table 3: PDSCH DMRS port to CDM group mapping, configuration type 2.

[0099]

[0100] NR HARQ ACK / NACK feedback on PUCCH: When the UE receives the PDSCH in the downlink from the serving gNB in ​​time slot n, if the PDSCH is successfully decoded, the UE sends a Hybrid Automatic Repeat Request (HARQ) ACK to the gNB in ​​the uplink via the PUCCH (Physical Uplink Control Channel) resource in time slot n+k. Otherwise, the UE sends a HARQ NACK to the gNB in ​​time slot n+k to indicate that the PDSCH was not successfully decoded. If the PDSCH carries two TBs, a HARQ ACK / NACK is reported for each TB, such that if one TB is not successfully decoded, only that TB needs to be retransmitted by the gNB. Spatial bundling can be configured, in which case a logical AND (AND) is used to report the decoding status of TB1 and TB2. k is also called K1 in the 3GPP specification.

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

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

[0103] In the 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.

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

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

[0106] • If the HARQ-ACK message and the SR are transmitted simultaneously, if A positive or negative SR, consisting of one or two HARQ-ACK bits and an SR transmission timing, represents the first PUCCH resource set with pucch-ResourceSetId = 0, or...

[0107] •if This is the second PUCCH resource set, pucch-ResourceSetId = 1, if provided by a higher layer, or

[0108] •if This is the third PUCCH resource set with pucch-ResourceSetId = 2, if provided by a higher layer, or

[0109] •if , which is the fourth PUCCH resource set if provided by a higher layer, pucch-ResourceSetId = 3.

[0110] in, Provided by a higher level.

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

[0112] If more than one DCI format 1_0 or 1_1 is received in CA and / or Time Division Duplex (TDD) mode, the PUCCH resource determination is based on the PUCCH Resource Indicator (PRI) field 1-1 in the last DCI format 1_0 or DCI format 1-1 detected by the UE. The multiple received DCI formats 1_0 or DCI format 1_1 have values ​​in the PDSCH-to-HARQ_feedback timing indicator field, indicating the same time slot used for PUCCH transmission. For PUCCH resource determination, the detected DCI formats are first indexed in ascending order across serving cells for the same PDCCH monitoring time, and then indexed in ascending order across PDCCH monitoring time.

[0113] The 3-bit PRI field maps to PUCCH resources in a PUCCH resource set that has up to eight PUCCH resources. For the first PUCCH resource set where pucch-ResourceSetId = 0, the number of PUCCH resources in that set... When the value is greater than 8, the UE, in response to detecting the last DCI format 1_0 or DCI format 1_1 in DCI format 1_0 or DCI format 1_1 during PDCCH reception, determines the index according to the following formula. ( The PUCCH resources are used to carry HARQ-ACK information, wherein the UE receives the value of the PDSCH-to-HARQ_feedback timing indicator field in the same time slot as the PUCCH transmission, indicating the DCI format 1_0 or DCI format 1_1.

[0114]

[0115] Where, N CCE,p The number of CCEs in CORESET p for PDCCH reception in DCI format 1_0 or DCI format 1_1, as described in section 10.1 of 3GPP TS38.213 v15.4.0, n. CCE,p It is the index of the first CCE used for PDCCH reception, and It is the value of the PUCCH resource indicator field in DCI format 1_0 or DCI format 1_1.

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

[0117] NR Type-1 HARQ-ACK codebook determination: The HARQ codebook (CB) time size (DL association set) is determined based on the configured HARQ-ACK timing K1 set and the semi-statically configured TDD mode in the TDD case.

[0118] Figure 6An example of a TDD mode with a K1 set from 1 to 5 and a configured time-domain resource allocation table or pdsch-TimeDomainAllocationList is shown, where there is no non-overlapping PDSCH TDRA allocation, i.e., only one PDSCH can be scheduled in a time slot. In this case, there are 5 entries in the HARQ codebook, one for each K1 value. For time slots where no PDSCH transmission occurs or where the UE does not detect a PDCCH for PDSCH scheduling, the corresponding entry in the codebook is filled with NACK (“N” shown in the figure). For time slots where PDSCH is scheduled, the corresponding entry is filled with ACK or NACK (“X” shown in the figure) depending on whether the PDSCH was successfully decoded.

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

[0120] In the case of MIMO with up to two codewords, an additional entry is added for each K1 value. In the case of multiple CCs, an additional entry is added to the HARQ codebook 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 bits in the HARQ feedback based on the configuration per DL cell (e.g., MIMO, spatial bundling, number of code block groups (CBGs) configured per TB). Examples are shown below. Figure 7 As shown, the UE's semi-static HARQ codebook is configured with three cells, namely cells 1 to 3. Cell 1 is configured with up to 2 TBs per PDSCH, cell 2 with 1 TB per PDSCH, and cell 3 with 1 TB and 4 CBGs. For each K1 value, the UE needs to feed back 7 bits: 2 bits for cell 1, 1 bit for cell 2, and 4 bits for cell 3 (not considering the possible multiple entries per slot based on the pdsch-symbolAllocation table). The rows and columns shown in the figure are for illustrative purposes only; by arranging the bits in a specific order, the actual feedback is a single bit vector.

[0121] Non-coherent joint transmission over multiple Transmitter Receiving Points or Panels (TRPs) (NC-JT): NC-JT refers to MIMO data transmission over multiple TRPs, where different MIMO layers are transmitted on different TRPs. Figure 8An example is shown where data is sent to the UE via two TRPs, each carrying a TB mapped to a codeword. When the UE has four receive antennas and each TRP has only two transmit antennas, the UE can support up to four MIMO layers, but each TRP can transmit at most two MIMO layers. In this case, by sending data to the UE on both TRPs, the peak data rate to the UE can be increased because up to four aggregation layers from the two TRPs can be used. This is beneficial when the traffic load in each TRP is low, and therefore resource utilization is low. In this example, a single scheduler is used to schedule data on both TRPs. One PDCCH is transmitted from each of the two TRPs in a time slot, and one PDSCH is scheduled from each TRP. This is called a multi-PDCCH or multi-DCI scheme, where the UE receives two PDCCHs and two associated PDSCHs from the two TRPs in a time slot. The two PDSCHs are typically allocated the same time / frequency resources.

[0122] exist Figure 9 In another scenario, a separate scheduler is used in each TRP. In this case, due to the undesirable backhaul, i.e., the backhaul has large latency and / or latency variation that is comparable to or even longer than the loop prefix length—up to several milliseconds—semi-static to semi-dynamic coordination can only be performed between two schedulers.

[0123] An agreement was reached at the 3GPP RAN1 ad hoc meeting NR_AH_1901 to support separate ACK / NACK payloads / feedbacks for multiple received PDSCHs for multi-PDCCH-based multi-TRP / panel downlink transmissions used for enhanced mobile broadband (eMBB). Furthermore, it was agreed that for multi-DCI-based multi-TRP / panel transmissions, if PDSCH resource allocations overlap, the total number of CWs in the scheduled PDSCHs can be at most two, with each PDSCH scheduled by one PDCCH.

[0124] In 3GPP RAN1#96, it was agreed that for separate ACK / NACK payloads / feedbacks of receive PDSCH using multiple DCIs, the PUCCH resources for delivering ACK / NACK feedback can be time-domain multiplexed with a separate HARQ-ACK codebook (TDMed).

[0125] In RAN1#96bis, it was also agreed that for individual ACK / NACK payloads / feedbacks of received PDSCH using multiple DCIs, support will be provided for TDMed PUCCH transmission within the time slot to deliver at least individual ACK / NACK feedback for two TRPs using separate HARQ-ACK codebooks.

[0126] In RAN1#97, it was agreed that for individual ACK / NACK feedback for PDSCH received from different TRPs, the UE should be able to generate a separate ACK / NACK codebook identified by an index, if configured and applied across all CCs. The index used to generate the separate ACK / NACK codebook is the higher-layer signaling index for each CORESET. Furthermore, it was agreed that joint HARQ-ACK feedback for PDSCH received from different TRPs using multiple DCIs will also be supported.

[0127] Several challenges exist. For joint HARQ-ACK feedback to PDSCH received from different TRPs using multiple DCIs, it is necessary to determine how to construct a semi-static HARQ codebook. In particular, it is necessary to determine how to multiplex the A / N bits associated with the two PDSCHs. Summary of the Invention

[0128] A system and method are provided for joint hybrid automatic repeat request (HARQ) feedback for Physical Downlink Shared Channel (PDSCH) transmissions over multiple Transmission Reference Points (TRPs). In some embodiments, the method for implementing transmission feedback, performed by a wireless device, 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) that schedules the corresponding downlink control information (DCI) for receiving the TB. In this way, the New Radio (NR) Rel-15 procedure for constructing a Type 1 HARQ codebook can be reused with a semi-static HARQ-ACK codebook with the same or minimal increase in HARQ feedback overhead.

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

[0130] In some embodiments, the method further includes: before receiving the first TB and the second TB, receiving an indication of allocating two entries—a first entry and a second entry—in a Type 1 HARQ codebook for each set of configured K1 values ​​and overlapping PDSCH time-domain resource assignments.

[0131] In some embodiments, the method further includes: mapping the HARQ-ACK bits of the first TB to the first entry in a Type 1 HARQ-ACK codebook associated with the same K1 value and the same time-domain resource allocation, and mapping the HARQ-ACK bits of the second TB to the second entry in the Type 1 HARQ-ACK codebook.

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

[0133] In some embodiments, receiving the first TB and the second TB includes: receiving the first TB from a first Transmitting Receiver Point (TRP) and the second TB from a second TRP in a time slot, wherein the first TB and the second TB are scheduled with two DCIs (one DCI per TB) and with the same time-domain resource allocation and the same K1 value. In some embodiments, the indication to receive the allocation of the two entries can be explicit or implicit.

[0134] In some embodiments, receiving an instruction to allocate two entries includes receiving one or more of the following groups: a higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; a higher-level parameter indicating joint HARQ ACK feedback and a configuration of two CORESET groups, each having a different group identifier value for each CORESET used for HARQ-ACK reporting; and a configuration of a CORESET group, each having the same group identifier value for each CORESET used for HARQ-ACK reporting.

[0135] In some embodiments, if the first TB or the second TB is not received correctly, the first entry or the second entry is filled with NACK accordingly. In some embodiments, the transmission may also include the transmission of one or two TBs scheduled by a single DCI. In some embodiments, as indicated in the DCI, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2. In some embodiments, the radio device is a New Radio (NR) User Equipment (UE).

[0136] In some embodiments, determining the first TB and the second TB further includes determining the first TB and the second TB based on one or more of the following: DMRS code division multiplexing (CDM) group identifiers of one or more demodulation reference signal (DMRS) ports indicated in the corresponding DCI that schedules the TB; TB identifiers indicated in the corresponding DCI that schedules the TB; Transmission configuration indication (TCI) status identifiers indicated in the corresponding DCI that schedules the TB; TCI status identifiers of the CORESET that receive the corresponding DCI that schedules the TB; and scrambling identifiers of the PDSCH carrying the TB.

[0137] In some embodiments, a method for implementing transmission feedback performed by a base station includes: transmitting a first transport block TB and a second TB to a wireless device, wherein the first TB and the second TB are determined based on a CORESET group identifier of the corresponding DCI of the transport scheduling of the TB; and receiving a constructed Type 1 HARQ codebook from the wireless device.

[0138] In some embodiments, the method further includes: before transmitting the first TB and the second TB, transmitting to the radio device a configuration having a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell.

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

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

[0141] In some embodiments, the instruction to allocate two entries can be explicit or implicit. In some embodiments, the instruction to allocate two entries includes transmitting one or more of the following groups: a higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; a higher-level parameter indicating joint HARQ ACK feedback and a configuration of two CORESET groups, each with a different group identifier value for each CORESET used for HARQ-ACK reporting; and a configuration of a CORESET group, each having the same group identifier value for each CORESET used for HARQ-ACK reporting.

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

[0143] In some embodiments, the first TB and the second TB are also determined based on one or more of the following: DMRS CDM group identifiers of one or more DMRS ports indicated in the corresponding DCI for scheduling the TB; TB identifiers indicated in the corresponding DCI for scheduling the TB; TCI status identifiers indicated in the corresponding DCI for scheduling the TB; TCI status identifiers of the CORESET that receive the corresponding DCI for scheduling the TB; and scrambling identifiers of the PDSCH carrying the TB.

[0144] In some embodiments, the wireless device for implementing transmission feedback includes one or more processors and a memory. The memory stores instructions executable by the one or more processors, thereby enabling the wireless device to perform any of the methods described above.

[0145] In some embodiments, the base station for implementing transmission feedback includes one or more processors and a memory. The memory stores instructions executable by the one or more processors, thereby enabling the base station to operate to perform any of the methods described above. Attached Figure Description

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

[0147] Figure 1 The diagram illustrates a 14-symbol time slot, where the first two symbols contain the Physical Downlink Control Channel (PDCCH), and the remaining symbols contain the Physical Shared Data Channel—either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0148] Figure 2 The diagram illustrates a basic New Radio (NR) physical time-frequency resource grid;

[0149] Figure 3 Some examples of scheduling two Class B PDSCHs in a time slot are shown;

[0150] Figure 4 The illustration shows NR data transmission over multiple multiple-input multiple-output (MIMO) layers;

[0151] Figure 5 The diagram illustrates the mapping from the demodulation reference signal (DMRS) to resource elements, which is configurable in both the frequency and time domains.

[0152] Figure 6 The diagram illustrates a Time Division Duplex (TDD) mode with a set of K1s from 1 to 5 and a configured time-domain resource allocation table.

[0153] Figure 7The diagram illustrates a semi-static Hybrid Automatic Repeat Request (HARQ) codebook for a radio device configured with three cells (i.e., cells 1 to 3).

[0154] Figure 8 The illustration shows data sent to a wireless device via two Transmit Receive Points (TRPs), each TRP carrying a TB mapped to a codeword;

[0155] Figure 9 The diagram illustrates the independent schedulers used in each TRP;

[0156] Figure 10 The illustration shows an example of a cellular communication system that can implement embodiments of the present disclosure according to some embodiments of the present disclosure;

[0157] Figure 11 The illustration shows a wireless communication system, according to some embodiments of the present disclosure, represented as a 5G network architecture consisting of core network functions (NFs);

[0158] Figure 12 The illustrations depict service-based interfaces between NFs in the control plane, instead of..., according to some embodiments of this disclosure. Figure 11 The 5G network architecture uses a point-to-point reference point / interface.

[0159] Figure 13A and 13B Operation methods of a wireless device and a base station according to some embodiments of the present disclosure are shown respectively;

[0160] Figure 13C The illustration shows a wireless device configured with a K1 range of 1 to 5 according to some embodiments of the present disclosure, which receives one PDSCH from one TRP in a time slot or two PDSCH from two TRPs in a time slot.

[0161] Figure 14 Examples of transmitting PDCCH#1 and PDCCH#2 from TRP 1 and 2 respectively, according to some embodiments of this disclosure, are shown;

[0162] Figure 15 Examples of transmitting PDCCH#1 and PDCCH#2 from TRP 1 and 2 respectively, according to some embodiments of this disclosure, are shown;

[0163] Figure 16 The illustration shows CDM group 0, which sends a signal notification for PDSCH#1, and CDM group 1, which sends a signal notification for PDSCH#2, according to some embodiments of the present disclosure.

[0164] Figure 17The illustration shows two CORESET groups defined by a higher-level signaling index according to some embodiments of this disclosure;

[0165] Figure 18 The illustration shows a cell with one TB and two CORESET groups according to some embodiments of the present disclosure;

[0166] Figure 19 The illustration shows one embodiment of a user equipment (UE) according to some embodiments of the present disclosure;

[0167] Figure 20 This is a schematic block diagram illustrating a virtualized environment according to some embodiments of the present disclosure, some of which implement virtualized functions;

[0168] Figure 21 The illustration shows exemplary communication systems according to some embodiments of the present disclosure;

[0169] Figure 22 The figures illustrate some embodiments according to the present disclosure. Figure 21 An example implementation of the UE, base station, and host computer according to an embodiment;

[0170] Figures 23 to 26 This is a flowchart illustrating a method implemented in a communication system according to some embodiments of the present disclosure; and

[0171] Figures 27 to 29 A flowchart illustrating some methods implemented in a communication system according to some embodiments of the present disclosure is provided. Detailed Implementation

[0172] The embodiments described below illustrate information that enables those skilled in the art to practice the embodiments and explain the best mode for practicing the embodiments. Upon reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and recognize the application of these concepts not specifically mentioned herein. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0173] Radio node: As used in this article, a “radio node” is a radio access node or wireless device.

[0174] Radio Access Node: As used herein, a “radio access node” or “radio network node” is any node in the radio access network of a cellular communication network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, base stations (e.g., New Radio (NR) base stations (gNBs) in 3GPP 5G NR networks, or enhanced or evolved Node Bs (eNBs) in 3GPP LTE networks), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), and relay nodes.

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

[0176] Wireless device: As used herein, a “wireless device” is any type of device that accesses a cellular communication network (i.e., is served by it) by wirelessly transmitting and / or receiving signals to or from one or more radio access nodes. Some examples of wireless devices include, but are not limited to, user equipment (UE) devices and machine-type communication (MTC) devices in 3GPP networks.

[0177] Network node: As used in this article, a “network node” is any node that is part of a radio access network or the core network of a cellular communication network / system.

[0178] Note that the descriptions presented herein focus on 3GPP cellular communication systems, and therefore 3GPP terminology or similar terms are frequently used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0179] Note that the term “cell” may be used in the description of this article; however, in particular for the 5G NR concept, a beam can be used instead of a cell, so it is important to note that the concept described here applies equally to both cells and beams.

[0180] Figure 10An example of a cellular communication system 1000 that can implement embodiments of the present disclosure is illustrated. In the embodiments described herein, the cellular communication system 1000 is a 5G system (5GS) including an NR RAN. In this example, the RAN includes base stations 1002-1 and 1002-2, which are referred to as gNBs in 5G NR, controlling corresponding (macro)cells 1004-1 and 1004-2. Generally, base stations 1002-1 and 1002-2 are collectively referred to herein as base station 1002 and are individually referred to as base station 1002. Similarly, generally, (macro)cells 1004-1 and 1004-2 are generally collectively referred to herein as (macro)cell 1004 and are individually referred to herein as (macro)cell 1004. The RAN may also include a plurality of low-power nodes 1006-1 to 1006-4 controlling corresponding small cells 1008-1 to 1008-4. Low-power nodes 1006-1 to 1006-4 may be small base stations (e.g., pico or femto base stations) or remote radio head ends (RRHs), etc. It is worth noting that, although not shown, one or more of small cells 1008-1 to 1008-4 may alternatively be provided by base station 1002. Low-power nodes 1006-1 to 1006-4 are generally referred to herein collectively as low-power node 1006 and are individually referred to as low-power node 1006. Similarly, small cells 1008-1 to 1008-4 are generally referred to herein collectively as small cell 1008 and are individually referred to as small cell 1008. The cellular communication system 1000 also includes a core network 1010, which is referred to as the 5G core (5GC) in 5GS. Base station 1002 (and optionally low-power node 1006) is connected to the core network 1010.

[0181] Base station 1002 and low-power node 1006 provide services to radio devices 1012-1 to 1012-5 in corresponding cells 1004 and 1008. Radio devices 1012-1 to 1012-5 are generally referred to herein as radio device 1012 and are referred to individually as radio device 1012. Radio device 1012 is sometimes also referred to herein as UE.

[0182] Figure 11 The diagram illustrates a wireless communication system represented as a 5G network architecture consisting of core network functions (NFs), where interactions between any two NFs are represented by point-to-point reference points / interfaces. Figure 11 Can be regarded as Figure 10 A specific implementation of System 1000.

[0183] From the access side, Figure 11The illustrated 5G network architecture includes multiple User Equipment (UEs) connected to a Radio Access Network (RAN) or Access Network (AN), as well as Access and Mobility Management Functions (AMF). Typically, the RAN includes base stations, such as evolved Node Bs (eNBs) or 5G base stations (gNBs). From the core network side, Figure 11 The 5G core NF shown includes Network Slice Selection Function (NSSF), Authentication Server Function (AUSF), Unified Data Management (UDM), AMF, Session Management Function (SMF), Policy Control Function (PCF), and Application Function (AF).

[0184] The reference points in the 5G network architecture are used to develop detailed call procedures in the standardization process. Reference point N1 is defined to carry signaling between the UE and the AMF. Reference points N2 and N3 are defined for connections between the AN and AMF, and between the AN and the UPF, respectively. Reference point N11 exists between the AMF and SMF, meaning the SMF is at least partially controlled by the AMF. N4 is used by both the SMF and UPF, allowing the UPF to be configured using control signals generated by the SMF, and the UPF to report its status to the SMF. N9 is a reference point for connections between different UPFs, and N14 is a reference point for connections between different AMFs. N15 and N7 are defined because the PCF applies policies to the AMF and SMF, respectively. The AMF requires N12 to authenticate the UE. N8 and N10 are defined because the AMF and SMF require the UE's subscription data.

[0185] The 5G core network is designed to separate the user plane and the control plane. The user plane carries user services, while the control plane carries signaling within the network. Figure 11 In this architecture, the UPF resides in the user plane, while all other NFs—AMF, SMF, PCF, AF, AUSF, and UDM—are in the control plane. Separating the user plane and control plane ensures that resources on each plane scale independently. It also allows the UPF to be deployed separately from control plane functions in a distributed manner. In this architecture, the UPF can be deployed very close to the UE to reduce the round-trip time (RTT) between the UE and the data network for applications requiring low latency.

[0186] The core 5G network architecture consists of modular functions. For example, AMF and SMF are independent functions in the control plane. Separate AMF and SMF allow for independent evolution and scaling. Other control plane functions such as PCF and AUSF can also be separated, such as... Figure 11 As shown. The modular functional design enables the 5G core network to flexibly support various services.

[0187] Each NF interacts directly with another NF. Intermediate functions may be used to route messages from one NF to another. In the control plane, a set of interactions between two NFs is defined as a service, thus enabling its reuse. This service implementation supports modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0188] Figure 12 The diagram illustrates the use of service-based interfaces between NFs in the control plane instead of... Figure 11 The 5G network architecture uses a point-to-point reference point / interface. However, the reference... Figure 11 The above NF corresponds to Figure 12 The NF shown. Services provided by an NF to other authorized NFs (one or more) can be exposed to the authorized NFs through service-based interfaces. Figure 12 In this context, service-based interfaces are represented by the letter "N" followed by the name of the NF, for example, Namf is a service-based interface for AMF, Nsmf is a service-based interface for SMF, and so on. Figure 12 The Network Open Function (NEF) and Network Function (NF) Repository Function (NRF) features are not discussed above. Figure 11 As shown in the image. However, it should be clarified that... Figure 11 All NFs described in the text can be used as needed. Figure 12 The interaction between NEF and NRF, despite Figure 11 It is not explicitly stated in the document.

[0189] Figure 11 and 12 Some characteristics of the NF shown can be described as follows: The AMF provides UE-based authentication, authorization, mobility management, etc. Even UEs using multiple access technologies are essentially connected to a single AMF because the AMF is independent of the access technology. The SMF is responsible for session management and assigns Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF used for data transmission. If a UE has multiple sessions, a different SMF can be assigned to each session to manage them individually, and each session may provide different functions. The AF provides information about packet flows to the PCF, which is responsible for policy control, to support Quality of Service (QoS). The PCF uses this information to determine policies regarding mobility and session management to ensure the proper operation of the AMF and SMF. The AUSF supports authentication functions for UEs, etc., and therefore stores data used for authenticating UEs, etc., while the UDM stores the UE's subscription data. The Data Network (DN) (not part of the 5G core network) provides Internet access or operator services, etc.

[0190] NF can be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualization function instantiated on a suitable platform (e.g., cloud infrastructure).

[0191] In RAN1#97, it was agreed that for separate ACK / NACK feedback for Physical Downlink Related Channels (PDSCH) received from different TRPs, the UE should be able to generate a separate ACK / NACK codebook identified by an index, if configured and applied across all CCs. The index used to generate the separate ACK / NACK codebook is the higher-level signaling index for each Control Resource Set (CORESET). Furthermore, it was agreed that joint HARQ-ACK feedback for PDSCH received from different TRPs using multiple DCIs will also be supported.

[0192] Several challenges exist. For joint HARQ-ACK feedback for PDSCH received from different Transmitter Receiver Points (TRPs) using multiple DCIs, it is necessary to determine how to construct a semi-static HARQ codebook. In particular, it is necessary to determine how to multiplex the A / N bits associated with the two PDSCHs.

[0193] A system and method are provided for joint hybrid automatic repeat request (HARQ) feedback for PDSCH transmissions across multiple TRPs. In some embodiments, the method for implementing transmission feedback, performed by a wireless device, 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 the CORESET that schedules the corresponding downlink control information (DCI) for receiving the TB. In this way, the NRRel-15 procedure for constructing a type 1 HARQ codebook can be reused with a semi-static HARQ-ACK codebook with the same or minimal increase in HARQ feedback overhead.

[0194] Figure 13A and 13B The diagrams illustrate operation methods of wireless devices and base stations according to some embodiments of the present disclosure. For example... Figure 13AAs shown, the radio device optionally receives a configuration of a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell (step 1300). The radio device receives (e.g., in component carriers CC) a first TB and a second TB (step 1302). The radio device determines the first TB and the second TB based on one or more indications. As shown in FIG13A, the first TB and the second TB are determined based on the CORESET group identifier of the corresponding DCI of the received scheduling of the TB (step 1304). In this way, the NR Rel-15 process for constructing a Type 1 HARQ codebook can be reused with a semi-static HARQ-ACK codebook with the same or minimal increase in HARQ feedback overhead.

[0195] like Figure 13B As shown, the base station optionally transmits to the radio device a configuration having a set of PDSCH to HARQ feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell (step 1308). The base station transmits a first TB and a second TB to the radio device (step 1302), wherein the first TB and the second TB are determined based on the CORESET group identifier of the corresponding DCI of the transmission scheduler for the TB (step 1310). The base station receives the constructed Type 1 HARQ codebook from the radio device (step 1312). In this way, the NR Rel-15 process for constructing the Type 1 HARQ codebook can be reused with a semi-static HARQ-ACK codebook with the same or minimal increase in HARQ feedback overhead.

[0196] Certain aspects of this disclosure and its embodiments may provide solutions to the above or other challenges. In some embodiments, the method recognizes that (a) a total of 2 TB can be scheduled in a time slot even in the case of multiple PDCCH scheduling from two TRPs and / or (b) PDSCH from two TRPs use completely overlapping time-domain resources. Some embodiments include:

[0197] In the case of implicit joint A / N feedback signaling, the cell to use joint A / N feedback is configured with up to 2 TB, so two entries for each K1 value and a set of overlapping TDRAs are reserved for the cell's semi-static HARQ-ACK codebook;

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

[0199] The mapping of the A / N bits of the received TB to one of two entries can be based on one of the following: the DMRS CDM group identifier of one or more DMRS ports indicated in the corresponding DCI of the scheduling TB; the TB identifier indicated in the corresponding DCI of the scheduling TB; the CORESET group identifier of the CORESET of the corresponding DCI of the receiving scheduling TB; the TCI status identifier indicated in the corresponding DCI of the scheduling TB; the TCI status identifier of the CORESET of the corresponding DCI of the receiving scheduling TB; and the scrambling identifier carrying the PDSCH of the TB.

[0200] This document describes a Type 1 HARQ-ACK codebook construction method for joint HARQ ACK reporting of multi-DCI-based PDSCH transmissions from multiple TRPs in a wireless network consisting of radio nodes with at least two transmission point TRPs and at least user equipment (UE). The method includes: the radio nodes configuring a set of PDSCH-to-HARQ feedback timing K1 values ​​and a list of PDSCH time-domain resource allocations for each time slot in the serving cell for the UE; the radio nodes instructing the UE to allocate two entries—a first entry and a second entry—in the Type 1 HARQ codebook for each configured K1 value and each set of overlapping PDSCH time-domain resource allocations; and the radio nodes transmitting a first transport block (TB) from the first TRP and a second TB from the second TRP to the UE in a time slot, wherein the first and second TBs are scheduled with two DCIs (one DCI per TB) and with the same time-domain resource allocation and the same K1 value; and...

[0201] The UE receives a first TB and a second TB; and the UE determines the first TB or the second TB based on one or more of the following: the DMRS CDM group identifier of one or more DMRS ports indicated in the corresponding DCI of the scheduling TB; the TB identifier indicated in the corresponding DCI of the scheduling TB; the CORESET group identifier of the CORESET of the corresponding DCI of the receiving scheduling TB; the TCI status identifier indicated in the corresponding DCI of the scheduling TB; the TCI status identifier of the CORESET of the corresponding DCI of the receiving scheduling TB; and the scrambling identifier of the PDSCH carrying the TB.

[0202] The UE maps the HARQ-ACK bits of the first TB to a first entry and the HARQ-ACK bits of the second TB to a second entry in a Type 1 HARQ-ACK codebook associated with the same K1 and the same time-domain resource allocation; and the UE reports the constructed Type 1 HARQ codebook to the radio node. The method, wherein the indication can be explicit or implicit, is achieved by configuring the higher-layer parameter maxNrofCodeWordsScheduledByDCI = 2; and configuring two CORESET groups, each with a different group identifier value for each CORESET used for HARQ-ACK reporting.

[0203] The method of 1, wherein if the first TB or the second TB is not correctly received, the first entry or the second entry is filled with NACK accordingly. The method of 1, wherein the transmission may further include transmitting one or two TBs scheduled by a single DCI. The methods of 1 and 4, wherein, as indicated in the single DCI, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2.

[0204] This document presents various embodiments that address one or more of the problems disclosed herein. In some embodiments, a method for implementing transmission feedback, performed by a wireless device, 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 following: a DMRS code division multiplexing (CDM) group identifier for one or more demodulation reference signal (DMRS) ports indicated in the corresponding downlink control information (DCI) of the scheduled TB; a TB identifier indicated in the corresponding DCI of the scheduled TB; a CORESET group identifier for the control resource set (CORESET) of the corresponding DCI of the received scheduled TB; a Transport Configuration Indication (TCI) status identifier indicated in the corresponding DCI of the scheduled TB; a TCI status identifier for the CORESET of the corresponding DCI of the received scheduled TB; and a scrambling identifier carrying the PDSCH of the TB.

[0205] Certain embodiments may provide one or more of the following technical advantages. The NRRel-15 process for constructing a type 1 HARQ codebook can be reused with a semi-static HARQ-ACK codebook with the same or minimal increase in HARQ feedback overhead.

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

[0207] In some embodiments, the method further includes: before receiving the first TB and the second TB, receiving an indication of allocating two entries—a first entry and a second entry—in a Type 1 HARQ codebook for each set of configured K1 values ​​and overlapping PDSCH time-domain resource assignments.

[0208] In some embodiments, the method further includes: mapping the HARQ-ACK bits of the first TB to a first entry in a Type 1 HARQ-ACK codebook associated with the same K1 value and the same time-domain resource allocation, and mapping the HARQ-ACK bits of the second TB to a second entry in the Type 1 HARQ-ACK codebook. In some embodiments, the method further includes reporting the constructed Type-1 HARQ codebook.

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

[0210] In some embodiments, receiving an instruction to allocate two entries can be explicit or implicit. In some embodiments, receiving an instruction to allocate two entries includes: receiving the higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; and / or configuring two CORESET groups, each CORESET group having a different group identifier value for each CORESET used for HARQ-ACK reporting.

[0211] In some embodiments, if the first TB or the second TB is not received correctly, the first entry or the second entry is filled with NACK accordingly. In some embodiments, the transmission may also include the transmission of one or two TBs scheduled by a single DCI. In some embodiments, as indicated in the DCI, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2. In some embodiments, the radio device is a New Radio (NR) User Equipment (UE).

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

[0213] In some embodiments, the method further includes: before transmitting the first TB and the second TB: transmitting to the radio device a configuration having a set of PDSCH-to-HARQ feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell.

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

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

[0216] In some embodiments, the instruction to allocate two entries can be explicit or implicit. In some embodiments, the instruction to allocate two entries includes: transmitting the higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; and / or configuring two CORESET groups, each with a different group identifier value for each CORESET used for HARQ-ACK reporting.

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

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

[0219] Figure 13C An example is shown where the UE is configured with a K1 range from 1 to 5 and receives one PDSCH from one TRP in a time slot or two PDSCHs from two TRPs in a time slot. The semi-static HARQ-ACK codebook then consists of five entries, each associated with a K1 value and two rows (note that the example in the figure is for illustration only; the actual codebook is a long bit vector arranged in a specific predefined order), and each row is associated with a TB. If a PDSCH with two TBs is received in a time slot (i.e., with maxNrofCodeWordsScheduledByDCI configured = 2), the first row is associated with TB1, and the second row with TB2, regardless of which TRP the PDSCH was received from. For example, if a PDSCH with two TBs is received in time slot n-5, the entry corresponding to K1=5 in the first row is associated with TB1, and the entry corresponding to K1=5 in the second row is associated with TB2. TB1 and TB2 are indicated in their respective DCIs.

[0220] If a PDSCH with a TB is received, whether that TB is associated with an entry in the first or second row can be determined by the TRP from which the received PDSCH originated. For example, the first row might be associated with TRP1 and the second row with TRP2. For instance, if a PDSCH with a TB is received from TRP1 in slot n-4, that TB is associated with the corresponding entry in the first row (K1=4), and the entries in the second row are filled with NACK (because no PDSCH was received from TRP2). In another example, if a PDSCH with a TB is received from TRP2 in slot n+4, then that TB is associated with the corresponding entry in the second row (K1=1), and the entries in the first row are filled with NACK (because no PDSCH was received from TRP1).

[0221] If two PDSCHs are received in time slots, such as time slots n-3, n-1, n, n+1, n+3, and n+5, then according to the 3GPP agreement, each PDSCH can only carry one TB. In this case, the corresponding entry in the first line is associated with the first TB (TB1) received from TRP1, and the corresponding entry in the second line 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 specification. Therefore, the first and second TBs, i.e., TB1 and TB2, need to be determined by one or more other parameters.

[0222] If no PDSCH is received in a time slot, the corresponding entries in both rows are filled with NACK. For example, if no PDSCH is received in time slot n-2, the corresponding entry for K=2 is filled with NACK.

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

[0224] In one embodiment, the UE is configured with maxNrofCodeWordsScheduledByDCI = 2, even if the PDSCH can only carry one TB or the UE can only receive up to four DL MIMO layers. 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 Figure 13C In the DCI, TB1 is mapped to the first row, and TB2 is mapped to the second row. If for the corresponding transport block indicated in the DCI, I... MCS =26 and rv id = 1, then TB is disabled.

[0225] If the UE can support more than 4 DL MIMO layers and receive DCI with two TBs enabled, then the traditional TB-to-codeword mapping is used, that is, TB1 is mapped to the first line and TB2 is mapped to the second line.

[0226] The disadvantage of this embodiment is that, since it uses two TB fields from DCI format 1-1, it will increase DCI overhead if each PDSCH always schedules one TB.

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

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

[0229] In NR, the TCI field in DCI can indicate the TCI status (with a corresponding TCI status ID), which conveys QCL information used to receive PDSCH DMRS. Figure 14 An example is shown where PDCCH#1 and PDCCH#2 are transmitted from TRP 1 and 2, respectively. Figure 14As shown, the DCI corresponding to PDCCH#1, which schedules PDSCH#1, can indicate a TCI state (e.g., with TCI state ID 3), while the DCI corresponding to PDCCH#2, which schedules PDSCH#2, can indicate another TCI state (e.g., TCI state ID 6). In a variant of this embodiment, a rule is defined such that if the TCI state ID indicated in the DCI of the PDCCH is odd, then the TB corresponding to the PDSCH is the first TB. If the TCI state ID indicated in the DCI of the PDCCH is even, then 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, then the TB corresponding to the PDSCH is the [mod(i,m)]th TB, where m=2.

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

[0231] Furthermore, different DMRS CDM groups can be used to indicate PDSCH1 or PDSCH2 (and thus TB1 and TB2, respectively). In one embodiment, the first and second TBs are determined by the DMRS CDM groups; that is, the first TB (TB1) is associated with a PDSCH having CDM group λ=0, while the second TB (TB2) is associated with a PDSCH having CDM group λ=1 or λ=2. An example is shown in Figure 16, where CDM group 0 is signaled for PDSCH#1 and CDM group 1 is signaled for PDSCH#2. Based on this embodiment, the first TB (TB1) is associated with PDSCH#1, and the second TB (TB2) is associated with PDSCH#2. The CGM group number or index can be identified based on the DMRS port(s)(one or more) signaled in the corresponding DCI.

[0232] For DMRS type 2, there are 3 DMRS CDM groups. Therefore, rules can be defined such that one TB is associated with a PDSCH that has its DMRS in one CDM group, while another TB is associated with a PDSCH that has its DMRS in one or both of the remaining two CDM groups. Consider the following example:

[0233] If the DMRS of PDSCH #1 is in CDM group 0, then TB 1 is associated with PDSCH #1. If the DMRS of PDSCH #2 is in CDM group 1, 2, or both, then TB 2 is associated with PDSCH #2.

[0234] In 3GPP RAN1#97, for scenarios where multiple PDCCHs schedule multiple PDSCHs, the introduction of multiple PDSCH scrambling identifiers was agreed upon. Each PDSCH scrambling identifier is used to generate a PDSCH scrambling sequence for one of the PDSCHs. In one embodiment, the first TB and the second TB 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.

[0235] In addition to the CDM group or TCI state of the PDSCH, other parameters or characteristics associated with the PDSCH, PDCCH, or DCI transmitted in the DCI can be used to associate the PDSCH with the TB (and 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 can be envisioned. The number of the PDCCH candidate 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.

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

[0237] Up to this point, it has been assumed that at most one PDSCH from a TRP is received by the UE in each time slot. This can be relaxed in a manner similar to Rel-15: each TRP is associated with a (same or different) PDSCH time-domain resource allocation table. As in Rel-15, this table is pruned to remove overlapping entries and PDSCH allocations that overlap with (one or more) UL symbols. For each pruned entry, one HARQ entry is retained. To extend this principle to multiple TRPs, a combined PDSCH time-domain resource allocation table for two TRPs is created as a union of the individual time-domain resource allocation tables. For each element of the union, two entries are retained (one entry per TB).

[0238] 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 on multiple TRPs with multiple PDCCHs. Each CORESET is configured with an index configured at a higher layer. CORESETs with the same higher-layer index form a CORESET group, and the higher-layer index is therefore the CORESET group index. Each CORESET group is associated with one TRP. For two TRPs, two CORESET groups can be defined using the higher-layer index.

[0239] In this scenario, when two CORESET groups are configured for the UE in the CC, two TBs are used during the construction of the Type 1 HARQ-ACK codebook for the CC. In this case, if maxNrofCodeWordsScheduledByDCI=1 is configured, only one TB field is needed in DCI format 1-1, thus saving DCI overhead. When two PDSCHs are received in a time slot, each carrying one TB and having overlapping TDRAs, the first and second TBs can be determined by the CORESET group index of the CORESET receiving the corresponding PDCCH. For example, the first TB is associated with a PDSCH scheduled by a PDCCH received in a CORESET with the first CORESET group index, while the second TB is associated with a PDSCH scheduled by a PDCCH received in a CORESET with the second CORESET group index.

[0240] Figure 17An example is shown where two CORESET groups are defined by a higher-level signaling index. Since PDCCH#1 is received in CORESET 1, which belongs to CORESET group 0, the first TB (TB 1) is associated with PDSCH#1. Similarly, PDCCH#2 is received in CORESET 3, which belongs to CORESET group 1, and then the second TB (TB 2) is associated with PDSCH#2.

[0241] If maxNrofCodeWordsScheduledByDCI=2 is configured and only one PDCCH with a PDSCH scheduled to have two codewords is received, then the NR Rel-15 behavior of mapping TB feedback to positions in the HARQ codebook is used. In one embodiment, if maxNrofCodeWordsScheduledByDCI=2 is configured and one PDCCH with a PDSCH scheduled to have one TB enabled is received, then the NR Rel-15 behavior of mapping TB feedback to positions in the HARQ codebook is used. Alternatively, the first or second TB is determined by the CORESET group index of the CORESET receiving the corresponding PDCCH.

[0242] If a CORESET group is configured, the number of TBs is determined based on the MIMO configuration maxNrofCodeWordsScheduledByDCI for the type 1 HARQ-ACK codebook construction, and the traditional NR Rel-15 behavior applies.

[0243] Figure 18 An example is shown where the cell configuration has one TB (i.e., maxNrofCodeWordsScheduledByDCI = 1) and two CORESET groups. The HARQ-ACK codebook consists of two lines (note that this is for illustration; the actual codebook is a long bit vector), each line associated with the TB scheduled for the PDCCH received in one of the two CORESET groups.

[0244] Figure 19This 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 includes a control system 1902, which includes one or more processors 1904 (e.g., a central processing unit (CPU), application-specific integrated circuit (ASIC), 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 circuitry. Furthermore, the radio access node 1900 includes one or more radio units 1910, each radio unit including one or more transmitters 1912 and one or more receivers 1914 coupled to one or more antennas 1916. The radio unit 1910 may be referred to as radio interface circuitry or a portion thereof. In some embodiments, the radio units(s) 1910 are external to the control system 1902 and are connectable to the control system 1902 via, for example, a wired connection (e.g., optical fiber). However, in some other embodiments, one or more radio units 1910 and possibly one or more antennas 1916 are integrated with the control system 1902. One or more processors 1904 operate to provide one or more functions of the radio access node 1900, as described herein. In some embodiments, one or more functions are implemented in software, which is stored, for example, in memory 1906 and executed by one or more processors 1904.

[0245] Figure 20 This is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1900 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualization architectures.

[0246] As used herein, a “virtualized” radio access node is an implementation of radio access node 1900, wherein at least a portion of the functionality of radio access node 1900 is implemented as one or more virtual components (e.g., via one or more virtual machines executing on one or more physical processing nodes in one or more networks). As illustrated, in this example, radio access node 1900 includes a control system 1902, which includes one or more processors 1904 (e.g., CPU, ASIC, FPGA, etc.), memory 1906, and a network interface 1908, as well as one or more radio units 1910, each including one or more transmitters 1912 and one or more receivers 1914 coupled to one or more antennas 1916, as described above. Control system 1902 is connected to radio units 1910 via, for example, fiber optic cables. Control system 1902 is connected to one or more processing nodes 2000 via network interface 1908, which are coupled to or included as part of network 2002. Each processing node 2000 includes one or more processors 2004 (e.g., CPU, ASIC, FPGA, etc.), memory 2006, and network interface 2008.

[0247] In this example, the functionality 2010 of the radio access node 1900 described herein is implemented at one or more processing nodes 2000 or distributed across the control system 1902 and one or more processing nodes 2000 in any desired manner. In some specific embodiments, some or all of the functionality 2010 of the radio access node 1900 described herein is implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more processing nodes 2000. As will be understood by those skilled in the art, additional signaling or communication between one or more processing nodes 2000 and the control system 1902 is used to perform at least some of the desired functionality 2010. It is noteworthy that in embodiments, the control system 1902 may be omitted, in which case the one or more radio units 1910 communicate directly with the one or more processing nodes 2000 via one or more appropriate network interfaces.

[0248] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functionality of a node (e.g., a processing node 2000) that enables radio access node 1900 to perform one or more of the following functions in a virtual environment according to any embodiment described herein: functions 2010 of radio access node 1900. In some embodiments, a carrier including the above-described computer program product is provided. The carrier is one of electronic signals, optical signals, radio signals, or computer-readable storage media (e.g., a non-transitory computer-readable medium such as memory).

[0249] Figure 21 This 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 includes one or more modules 2100, each implemented in software. The modules(one or more) 2100 provide the functionality of the radio access node 1900 described herein. This discussion also applies to... Figure 20 The processing node 2000, wherein the module 2100 may be implemented at one of the processing nodes 2000 or distributed on multiple processing nodes 2000 and / or distributed on (one or more) processing nodes 2000 and control system 1902.

[0250] Figure 22 This 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., CPU, ASIC, FPGA, etc.), a memory 2204, and one or more transceivers 2206. Each transceiver 2206 includes one or more transmitters 2208 and one or more receivers 2210 coupled to one or more antennas 2212. The transceiver(s) includes radio front-end circuitry connected to the antenna(s) 2212, configured to modulate signals transmitted between the antenna(s) 2212 and the processor(s) 2202, as will be understood by those skilled in the art. The processor 2202 is also referred to herein as processing circuitry. The transceiver 2206 is also referred to herein as radio circuitry. In some embodiments, the functionality of the UE 2200 described above may be implemented entirely or partially in software, which is stored, for example, in the memory 2204 and executed by the processor(s) 2202. Note that the UE 2200 may include... Figure 22Additional components not shown in the figure, such as one or more user interface components (e.g., input / output interfaces including displays, buttons, touch screens, microphones, speakers, etc.) and / or any other components used to allow information to be input to and / or output from the UE 2200, power supplies (e.g., batteries and associated power circuitry), etc.

[0251] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functionality of the UE 2200 according to any of the embodiments described herein. In some embodiments, a carrier including the computer program product described above is provided. The carrier is one of electronic signals, optical signals, radio signals, or computer-readable storage media (e.g., a non-transitory computer-readable medium such as memory).

[0252] Figure 23 This 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. Modules 2300 provide the functionality of the UE 2200 described herein.

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

[0254] Telecommunications network 2400 is itself connected to host computer 2416, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. Host computer 2416 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 2418 and 2420 between telecommunications network 2400 and host computer 2416 may extend directly from core network 2404 to host computer 2416, or via optional intermediate network 2422. Intermediate network 2422 may be one or more of public, private, or hosted networks; intermediate network 2422, if present, may be a backbone network or the Internet; in particular, intermediate network 2422 may include two or more subnets (not shown).

[0255] Figure 24 The communication system as a whole enables connectivity between the connected UEs 2412 and 2414 and the host computer 2416. This connectivity can be described as an over-the-top (OTT) connection 2424. The host computer 2416 and the connected UEs 2412 and 2414 are configured to transmit data and / or signaling via the OTT connection 2424, using the access network 2402, core network 2404, any intermediate network 2422, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 2424 can be transparent in the sense that the participating communication devices are unaware of the routes of uplink and downlink communications. For example, the base station 2406 may not be informed or need not be informed of the past routes of incoming downlink communications, where data originating from the host computer 2416 is to be forwarded (e.g., handed over) to the connected UE 2412. Similarly, base station 2406 does not need to know the future route of outgoing uplink communication originating from UE 2412 toward host computer 2416.

[0256] According to the embodiments, reference will now be made to Figure 25Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs are described. In communication system 2500, host computer 2502 includes hardware 2504, which includes a communication interface 2506 configured to establish and maintain wired or wireless connections to interfaces with different communication devices of communication system 2500. Host computer 2502 further includes processing circuitry 2508, which may have storage and / or processing capabilities. In particular, processing circuitry 2508 may include one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) suitable for executing instructions. Host computer 2502 further includes software 2510, which is stored in or accessible by host computer 2502 and executable by processing circuitry 2508. Software 2510 includes host application 2512. Host application 2512 is operable to provide services to remote users, such as UE 2514 connected via OTT connection 2516 terminated between UE 2514 and host computer 2502. When providing services to remote users, host application 2512 can provide user data transmitted using OTT connection 2516.

[0257] The communication system 2500 further includes a base station 2518, which is provided in the telecommunications system and includes hardware 2520 enabling it to communicate with the host computer 2502 and the UE 2514. Hardware 2520 may include a communication interface 2522 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 2500, and for establishing and maintaining connections with the coverage area served by the base station 2518. Figure 25 The UE 2514 (not shown) has at least a radio interface 2524 for a wireless connection 2526. The communication interface 2522 can be configured to facilitate connection 2528 to the host computer 2502. Connection 2528 can be direct, or it can be via the core network of the telecommunications system (…). Figure 25 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 2520 of base station 2518 further includes processing circuitry 2530, which may include one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) suitable for executing instructions. Base station 2518 further has software 2532 stored internally or accessible via an external connection.

[0258] The communication system 2500 also includes the previously mentioned UE 2514. The hardware 2534 of UE 2514 may include a radio interface 2536 configured to establish and maintain a wireless connection 2526 with a base station serving the coverage area where UE 2514 is currently located. The hardware 2534 of UE 2514 also includes processing circuitry 2538, which may include one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) suitable for executing instructions. UE 2514 also includes software 2540, which is stored in or accessible by UE 2514 and executable by processing circuitry 2538. Software 2540 includes a client application 2542. Client application 2542 may be operable to provide services to human or non-human users via UE 2514 with the support of host computer 2502. In host computer 2502, the executing host application 2512 can communicate with the executing client application 2542 via OTT connection 2516 terminated between UE 2514 and host computer 2502. When providing services to a user, client application 2542 can receive request data from host application 2512 and provide user data in response to the request data. OTT connection 2516 can transmit both request data and user data. Client application 2542 can interact with the user to generate the user data it provides.

[0259] Notice, Figure 25 The host computer 2502, base station 2518, and UE 2514 shown may be similar to or equivalent to the following: Figure 24 The host computer 2416, one of base stations 2406A, 2406B, and 2406C, and one of UEs 2412 and 2414. That is to say, the internal workings of these entities can be as follows: Figure 25 As shown, and independently, the surrounding network topology can be Figure 24 The network topology.

[0260] exist Figure 25 In this diagram, OTT connection 2516 is abstractly depicted to illustrate communication between host computer 2502 and UE 2514 via base station 2518, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the route, which can be configured to either the service provider operating host computer 2502 or hide the route from both. When OTT connection 2516 is active, the network infrastructure can make further decisions, through which it dynamically changes the route (e.g., based on network reconfiguration or load balancing considerations).

[0261] The wireless connection 2526 between UE 2514 and base station 2518 is based on the teachings of embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 2514 using OTT connection 2516, wherein wireless connection 2526 forms the final segment. More precisely, the teachings of these embodiments can improve, for example, data rates, latency, power consumption, etc., thereby providing benefits such as reduced user wait time, relaxed file size limits, better responsiveness, and extended battery life.

[0262] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. Optional network functionality may also be available for reconfiguring the OTT connection 2516 between host computer 2502 and UE 2514 in response to changes in measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 2516 may be implemented in software 2510 and hardware 2504 of host computer 2502, or in software 2540 and hardware 2534 of UE 2514, or both. In embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 2516 passes; the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which the monitored quantities can be calculated or estimated by software 2510, 2540. Reconfiguration of the OTT connection 2516 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect base station 2518 and may be unknown or imperceptible to base station 2518. Such processes and functionalities are likely known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling, thereby facilitating the host computer 2502 to measure throughput, propagation time, latency, etc. Measurements can be achieved by software 2510 and 2540 using OTT connection 2516 to transmit messages, particularly empty or "pseudo" messages, while it monitors propagation time, errors, etc.

[0263] Figure 26 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced. Figure 24 and 25 Those described. For the sake of simplicity in this disclosure, this section will only include those... Figure 26Referring to the accompanying drawings. In step 2600, the host computer provides user data. In sub-step 2602 of step 2600 (which may be optional), the host computer provides user data by executing a host application. In step 2604, the host computer initiates a transmission carrying user data to the UE. In step 2606 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 2608 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0264] Figure 27 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced. Figure 24 and 25 Those described. For the sake of simplicity in this disclosure, this section will only include those... Figure 27 Refer to the accompanying drawings. In step 2700 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 2702, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission can be carried out via a base station. In step 2704 (which may be optional), the UE receives the user data carried in the transmission.

[0265] Figure 28 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced. Figure 24 and 25 Those described. For the sake of simplicity in this disclosure, this section will only include those... Figure 28 Referring to the accompanying drawings. 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 of step 2800 (which may be optional), the UE provides user data by executing a client application. In sub-step 2806 of step 2802 (which may be optional), the UE responds to the received input data provided by the host computer by executing the client application that provides user data. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific method used to provide user data, in sub-step 2808 (which may be optional), the UE initiates the transmission of user data to the host computer. In step 2810 of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the host computer receives the user data transmitted from the UE.

[0266] Figure 29 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced. Figure 24 and 25 Those described. For the sake of simplicity in this disclosure, this section will only include those... Figure 29 Refer to the accompanying drawings. In step 2900 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 2902 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 2904 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0267] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a number of such functional units. These functional units may be implemented via processing circuitry and other digital hardware, which may include one or more microprocessors or microcontrollers, and the digital hardware may include digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more technologies described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0268] While the processes in the figures may illustrate a particular sequence of operations performed by certain embodiments of this disclosure, it should be understood that such sequence is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.). Furthermore, throughout this disclosure, the term "embodiment" may be understood to be replaced by the term "aspect". Example

[0269] Group A Examples

[0270] Example 1: A method for providing transmission feedback, performed by a wireless device, the method comprising: 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 following: i. a DMRS code division multiplexing (CDM) group identifier of one or more demodulation reference signal (DMRS) ports optionally indicated in the corresponding downlink control information (DCI) of the scheduled TB; ii. a TB identifier optionally indicated in the corresponding DCI of the scheduled TB; iii. a CORESET group identifier of the control resource set (CORESET) optionally received in the corresponding DCI of the scheduled TB; iv. a Transmission Configuration Indication (TCI) status identifier optionally indicated in the corresponding DCI of the scheduled TB; v. a TCI status identifier of the CORESET optionally received in the corresponding DCI of the scheduled TB; and vi. a scrambling identifier of the physical downlink shared channel (PDSCH) carrying the TB.

[0271] Example 2: The method described in Example 1 further includes: before receiving the first TB and the second TB, receiving a configuration having a set of PDSCH to Hybrid Automatic Repeat Request (HARQ) feedback timing K1 values ​​and / or a list of PDSCH time domain resource allocations for each time slot in the serving cell.

[0272] Example 3: The method of any one of Examples 1 to 2 further includes: receiving, before receiving the first TB and the second TB, an indication of allocating two entries—a first entry and a second entry—in the Type 1 HARQ codebook for each set of configured K1 values ​​and overlapping PDSCH time-domain resource assignments.

[0273] Example 4: The method of any one of Examples 1 to 3 further includes: mapping the HARQ-ACK bits of the first TB to the first entry in the Type 1 HARQ-ACK codebook associated with the same K1 value and the same or overlapping PDSCH time-domain resource allocation, and mapping the HARQ-ACK bits of the second TB to the second entry in the Type 1 HARQ-ACK codebook.

[0274] Example 5: The method described in any one of Examples 1 to 4 further includes: reporting the constructed Type 1 HARQACK codebook.

[0275] Example 6: The method of any one of Examples 1 to 5, wherein receiving the first TB and the second TB includes receiving the first TB from the first TRP and the second TB from the second TRP in a time slot, wherein the first TB and the second TB are scheduled with two DCIs (one DCI for each TB) and with the same time domain resource allocation and the same K1 value.

[0276] Example 7: The method described in any one of Examples 3 to 6, wherein the instruction to receive the allocation of two entries can be explicit or implicit.

[0277] Example 8: The method described in Example 7, receiving an instruction to allocate two entries includes receiving one or more of the following: a. a higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; b. a higher-level parameter indicating joint HARQ ACK feedback, and a configuration of two CORESET groups, each CORESET group having a different group identifier value for each CORESET used for HARQ-ACK reporting; c. a configuration of a CORESET group, each CORESET group having the same group identifier value for each CORESET used for HARQ-ACK reporting.

[0278] Example 9: The method of any one of Examples 1 to 8, wherein if the first TB or the second TB is not received correctly, the first entry or the second entry is filled with NACK accordingly.

[0279] Example 10: The method described in any one of Examples 1 to 9, wherein the transmission may further include transmitting one or two TBs scheduled by a single DCI.

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

[0281] Example 12: The method described in any one of Examples 1 to 11, wherein the wireless device is a New Radio (NR) User Equipment (UE).

[0282] Example 13: The method described in any of the foregoing embodiments further includes: providing user data; and forwarding the user data to a host computer via transmission to a base station.

[0283] Group B Implementation Examples

[0284] Example 14: A method for receiving transmission feedback executed by a base station, the method comprising: transmitting a first TB and a second TB to a wireless device, wherein a constructed Type 1 Hybrid Automatic Repeat Request (HARQ) codebook is received from the wireless device.

[0285] Example 15: The method described in Example 14 further includes: before transmitting the first TB and the second TB: a configuration for transmitting to the radio device a set of PDSCH to HARQ feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell.

[0286] Example 16: The method of any one of Examples 14 to 15 further includes: before transmitting the first TB and the second TB, transmitting to the wireless device an indication of allocating two entries—a first entry and a second entry—for each set of configured K1 values ​​and overlapping PDSCH time-domain resource assignments in a Type 1 HARQ codebook.

[0287] Example 17: The method of any one of Examples 14 to 16, wherein transmitting the first TB and the second TB includes: transmitting the first TB from the first TRP and the second TB from the second TRP in a time slot, wherein the first TB and the second TB are scheduled with two DCIs (one DCI for each TB) and with the same time domain resource allocation and the same K1 value.

[0288] Example 18: The method described in any of Examples 14 to 17, wherein the instruction to transmit the allocation of two entries can be explicit or implicit.

[0289] Example 19: The method described in Example 18, wherein transmitting an instruction to allocate two entries includes transmitting one or more of the following: a. a higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; b. a higher-level parameter indicating joint HARQACK feedback, and a configuration of two CORESET groups, each CORESET group having a different group identifier value for each CORESET used for HARQ-ACK reporting; c. a configuration of a CORESET group, each CORESET group having the same group identifier value for each CORESET used for HARQ-ACK reporting.

[0290] Example 20: The method of any one of Examples 14 to 19, wherein if the first TB or the second TB is not received correctly, the first entry or the second entry is filled with NACK accordingly.

[0291] Example 21: The method described in any one of Examples 14 to 20, wherein the transmission may further include transmitting one or two TBs scheduled by a single DCI.

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

[0293] Example 23: The method described in any one of Examples 14 to 22, wherein the base station is a New Radio Network (NRgNB).

[0294] Example 24: The method described in any of the foregoing examples further includes: obtaining user data; and forwarding the user data to a host computer or a wireless device.

[0295] Group C Implementation Examples

[0296] Example 25: A wireless device for providing transmission feedback, the wireless device comprising: processing circuitry configured to perform any step of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.

[0297] Example 26: A base station for receiving transmission feedback, the base station comprising: processing circuitry configured to perform any step of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station.

[0298] Example 27: A user equipment (UE) for providing transmission feedback includes: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and processing circuitry and configured to modulate signals transmitted between the antenna and processing circuitry; processing circuitry configured to perform any step of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow information to be input into the UE for processing by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to power the UE.

[0299] Example 28: A communication system including a host includes: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of the base station being configured to perform any step of any of the Group B embodiments.

[0300] Example 29: The communication system according to the previous example also includes a base station.

[0301] Example 30: The communication system according to the first two examples further includes a UE, wherein the UE is configured to communicate with the base station.

[0302] Example 31: A communication system according to the first three examples, wherein: the processing circuitry of the host computer is configured to execute a host application to provide user data; and the UE includes processing circuitry configured to execute a client application associated with the host application.

[0303] Example 32: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the base station performs any step of any of the Group B embodiments.

[0304] Example 33: The method according to the previous example further includes transmitting user data at the base station.

[0305] Example 34: The method according to the first two examples, wherein user data is provided at the host computer by executing a host application, the method further includes executing a client application associated with the host application at the UE.

[0306] Example 35: A user equipment (UE) configured to communicate with a base station, the UE including a radio interface and processing circuitry configured to perform the methods described in the first three examples.

[0307] Example 36: A communication system including a host computer, comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the UE includes a radio interface and processing circuitry, and components of the UE are configured to perform any step of any of the Group A embodiments.

[0308] Example 37: The communication system according to the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0309] Example 38: The communication system according to the first two examples, wherein: the processing circuit of the host computer is configured to execute a host application to provide user data; and the processing circuit of the UE is configured to execute a client application associated with the host application.

[0310] Example 39: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data to the UE via a cellular network including the base station at the host computer, wherein the UE performs any step of any of the Group A embodiments.

[0311] Example 40: The method according to the previous example further includes receiving user data from the base station at the UE.

[0312] Example 41: A communication system including a host computer, comprising: a communication interface configured to receive user data transmitted from a user equipment (UE) to a base station; wherein the UE includes a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any step of any of the Group A embodiments.

[0313] Example 42: The communication system according to the previous example further includes a UE.

[0314] Example 43: The communication system according to the first two examples further includes a base station, wherein the base station includes a radio interface and a communication interface configured to communicate with the UE, and is configured to forward user data carried in the transmission from the UE to the base station to the host computer.

[0315] Example 44: The communication system according to the first three examples, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0316] Example 45: A communication system according to the preceding four examples, wherein: the host's processing circuitry is configured to execute a host application to provide requested data; and the UE's processing circuitry is configured to execute a client application associated with the host application to provide user data in response to the requested data.

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

[0318] Example 47: The method according to the previous example further includes providing user data to the base station at the UE.

[0319] Example 48: The method according to the preceding two examples further includes: at the UE, executing a client application to provide user data to be transmitted; and at the host computer, executing a host application associated with the client application.

[0320] Example 49: The method according to the first three examples further includes: executing a client application at the UE; and receiving input data from the client application at the UE, and providing the input data at a host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data.

[0321] Example 50: A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from a user equipment (UE) to a base station, wherein the base station includes a radio interface and processing circuitry configured to perform any step of any of the Group B embodiments.

[0322] Example 51: The communication system according to the previous example further includes a base station.

[0323] Example 52: The communication system according to the first two examples further includes a UE, wherein the UE is configured to communicate with a base station.

[0324] Example 53: A communication system according to the first three examples, wherein: the processing circuitry of the host computer is configured to execute a host application; 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.

[0325] Example 54: A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method comprising: at the host computer, receiving from the base station user data transmitted from the base station that has been received from the UE, wherein the UE performs any step of any of the Group A embodiments.

[0326] Example 55: The method according to the previous example further includes receiving user data from the UE at the base station.

[0327] Example 56: The method described in the preceding two examples further includes, at the base station, initiating the transmission of received user data to the host computer.

[0328] At least some of the following abbreviations may be used in this disclosure. In the event of any inconsistency between the abbreviations, the usage above shall prevail. If listed multiple times below, the first listing shall take precedence over any (one or more) subsequent listings.

[0329] • 3GPP Third Generation Partner Program

[0330] • 5G (Fifth Generation)

[0331] • 5GC fifth-generation core

[0332] • 5GS Fifth Generation System

[0333] • ACK confirmation

[0334] • AF Application Functions

[0335] • AMF Access and Mobility Functions

[0336] • AN Access Network

[0337] • AP Access Point

[0338] • ASIC (Application-Specific Integrated Circuit)

[0339] • AUSF Authentication Server Functionality

[0340] • CA carrier aggregation

[0341] • CBG code block group

[0342] • CC component carrier

[0343] • CCE Control Channel Element

[0344] • CDM (Code Division Multiplexing)

[0345] • CORESET Control Resource Set

[0346] • CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0347] • CPU (Central Processing Unit)

[0348] • CRC Cyclic Redundancy Check

[0349] • C-RNTI Temporary Identifier for Cell Radio Networks

[0350] • CSI-RS Channel State Information Reference Signal

[0351] • CS-RNTI configured temporary identifier for the dispatch radio network

[0352] • CSS Public Search Space

[0353] • CW code

[0354] • DAI Downlink Assignment Index

[0355] • DCI Downlink Control Information

[0356] • Discrete Fourier Transform (DFT)

[0357] • DL downlink

[0358] • DMRS demodulation reference signal

[0359] • DN Data Network

[0360] • DSP Digital Signal Processor

[0361] • eMBB Enhanced Mobile Broadband

[0362] • eNB (Enhanced or Evolved Node B)

[0363] • FPGA (Field Programmable Gate Array)

[0364] • FR frequency range

[0365] • gNB New Radio Base Station

[0366] • HARQ (Hybrid Automatic Repeat Request)

[0367] • HSS (Home Subscriber Server)

[0368] • IE Information Elements

[0369] • IP Internet Protocol

[0370] • LTE Long Term Evolution

[0371] • MCS modulation and coding scheme

[0372] • MIMO (Multiple-Input Multiple-Output)

[0373] • MME (Mobility Management Entity)

[0374] • MTC Machine Type Communication

[0375] • NC-JT Incoherent Joint Transmission

[0376] • NDI New Data Indicator

[0377] • NEF Network Open Functionality

[0378] • NF Network Functions

[0379] • NR New Radio

[0380] • NRF Network Functions Repository Functions

[0381] • NSSF network slice selection function

[0382] • OTT over-the-top

[0383] • PCF policy control function

[0384] • PDCCH (Physical Downlink Control Channel)

[0385] • PDSCH (Physical Downlink Shared Channel)

[0386] • P-GW Packet Data Network Gateway

[0387] • PRB Physical Resource Block

[0388] • PRI PUCCH resource indicator

[0389] • PUCCH (Physical Uplink Control Channel)

[0390] • PUSCH Physical Uplink Shared Channel

[0391] • QCL Quasi-co-located

[0392] • QoS (Quality of Service)

[0393] • RAM (Random Access Memory)

[0394] • RAN Radio Access Network

[0395] • RB resource block

[0396] • RE Resource Elements

[0397] • REG Resource Element Group

[0398] • ROM (Read-Only Memory)

[0399] • RRC Radio Resource Control

[0400] • RRH Remote Radio Header

[0401] • RTT round trip time

[0402] • SCEF service capability exposure function

[0403] • SINR (Signal Interference-to-Noise Ratio)

[0404] • SMF Session Management Function

[0405] • SR scheduling request

[0406] • SSB Synchronization Signal Block

[0407] • TB transfer block

[0408] • TCI Transport Configuration Instructions

[0409] • TDD (Time Division Duplex)

[0410] • TDM (Time Division Multiplexing)

[0411] • TDRA Time Domain Resource Allocation

[0412] • TPC transmit power control

[0413] • TRP Transmitter / Receiver Point

[0414] • TRS Tracking Reference Signal

[0415] • UCI uplink control information

[0416] • UDM Unified Data Management

[0417] • UE (User Equipment)

[0418] • UL uplink

[0419] • UPF User Plane Functions

[0420] • USS UE specific search space

[0421] • VRB (Virtual Resource Block)

[0422] • ZP Zero Power

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

Claims

1. A method for implementing transmission feedback, performed by a wireless device, the method comprising: Configuration for receiving (1300) a set of Physical Downlink Shared Channel (PDSCH) to Hybrid Automatic Repeat Request (HARQ) feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell; Receive an instruction to allocate two entries for each set of configured K1 values ​​and overlapping PDSCH time-domain resource assignments in the Type 1 HARQ codebook, the two entries being a first entry and a second entry; Receive the first transport block TB and the second transport block TB in the component carrier CC (1302); Based on the CORESET group identifier of the control resource set CORESET of the corresponding downlink control information DCI received and scheduled by the TB, the first TB and the second TB are determined (1304); as well as The HARQ-ACK bits of the first TB are mapped to the first entry in the Type 1 HARQ-ACK codebook associated with the same K1 value and the same or overlapping PDSCH time-domain resource allocation, and the HARQ-ACK bits of the second TB are mapped 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. Receiving the first TB and the second TB includes receiving, in a time slot, the first TB scheduled by the first DCI from the first transmission receiving point TRP represented by the first CORESET group identifier and the second TB scheduled by the second DCI from the second TRP represented by the second CORESET group identifier, wherein the first TB and the second TB have the same or overlapping time domain resource allocation and the same K1 value.

2. The method of claim 1, further comprising: The type 1 HARQ ACK codebook constructed in report (1306).

3. The method as described in claim 1, wherein, The instruction to receive the allocation of the two entries can be explicit or implicit.

4. The method of claim 3, wherein, Receiving the instruction to allocate the two entries includes receiving one or more of a group consisting of: The higher-level parameter maxNrofCodeWordsScheduledByDCI = 2; The configuration of higher-level parameters for the joint HARQ ACK feedback and two CORESET groups, each with a different group identifier value for each CORESET used for HARQ-ACK reporting; and A configuration of a CORESET group, wherein each CORESET group has the same group identifier value for each CORESET used for HARQ-ACK reporting.

5. The method of claim 1, wherein, If the first TB or the second TB is not received correctly, the first entry or the second entry is filled with a negative acknowledgment (NACK), respectively.

6. The method of claim 1, wherein, The transmission may also include the transmission of one or two TBs scheduled by a single DCI.

7. The method of claim 6, wherein, As indicated in the single DCI, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2.

8. The method of claim 1, wherein, The wireless device is a New Radio (NR) User Equipment (UE).

9. The method of claim 1, wherein, 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 following: The DMRS code division multiplexing (CDM) group identifier of one or more demodulation reference signal (DMRS) ports indicated in the corresponding DCI of the scheduling TB; The TB identifier indicated in the corresponding DCI that schedules the TB; The transmission configuration indication TCI status identifier is indicated in the corresponding DCI of the scheduling TB; Receive the TCI status identifier of the CORESET of the corresponding DCI for scheduling the TB; and The scrambling identifier of the PDSCH carrying the TB.

10. A method for implementing transmission feedback, performed by a base station, the method comprising: Configuration to transmit (1308) to the radio device a set of PDSCH to Hybrid Automatic Repeat Request (HARQ) feedback timing K1 values ​​and / or a list of PDSCH time-domain resource allocations for each time slot in the serving cell; The wireless device is given an indication that two entries are assigned to each set of configured K1 values ​​and overlapping PDSCH time-domain resource assignments in the Type 1 HARQ codebook, the two entries being a first entry and a second entry. Transmit (1310) a first transport block TB and a second TB to the wireless device, wherein the first TB and the second TB are determined based on the CORESET group identifier of the control resource set CORESET corresponding to the downlink control information DCI that schedules the TB; and Receive the type 1 hybrid automatic repeat request (HARQ) ACK codebook constructed by (1312) from the wireless device. The transmission of the first TB and the second TB includes transmitting, in the time slot, the first TB, scheduled by the first DCI, originating from the first transmission receiving point TRP represented by the first CORESET group identifier, and the second TB, scheduled by the second DCI, originating from the second TRP represented by the second CORESET group identifier, wherein the first TB and the second TB have the same or overlapping time domain resource allocation and the same K1 value.

11. The method of claim 10, wherein, The instruction to allocate the two entries can be explicit or implicit.

12. The method of claim 11, wherein, The instruction to transmit the two entries includes: transmitting one or more of a group consisting of: The upper-level parameter maxNrofCodeWordsScheduledByDCI = 2; The configuration of higher-level parameters for the joint HARQ ACK feedback and two CORESET groups, each with a different group identifier value for each CORESET used for HARQ-ACK reporting; A configuration of a CORESET group, wherein each CORESET group has the same group identifier value for each CORESET used for HARQ-ACK reporting.

13. The method of claim 10, wherein, If the first TB or the second TB is not received correctly, the first entry or the second entry is filled with a negative acknowledgment (NACK), respectively.

14. The method of claim 10, wherein, The transmission may also include the transmission of one or two TBs scheduled by a single DCI.

15. The method of claim 14, wherein, As indicated in the single DCI, the first TB corresponds to transport block 1 and the second TB corresponds to transport block 2.

16. The method of claim 10, wherein, The base station is a New Radio (NR) gNB.

17. The method of claim 10, wherein, The first TB and the second TB are further determined based on one or more of the following: The DMRS code division multiplexing (CDM) group identifier of one or more demodulation reference signal (DMRS) ports indicated in the corresponding downlink control information (DCI) of the scheduling TB. The TB identifier indicated in the corresponding DCI that schedules the TB; The transmission configuration indication TCI status identifier is indicated in the corresponding DCI of the scheduling TB; Receive the TCI status identifier of the CORESET of the corresponding DCI for scheduling the TB; and The scrambling identifier of the PDSCH carrying the TB.

18. A wireless device (2200) for implementing transmission feedback, the wireless device (2200) comprising: One or more processors (2202); and The memory (2204) stores instructions executable by the one or more processors, thereby enabling the wireless device (2200) to perform the method of any one of claims 1-9.

19. A base station (1900) for implementing transmission feedback, the base station (1900) comprising: One or more processors (1904); and The memory (1906) includes instructions to cause the base station (1900) to perform the method of any one of claims 10-17.

Images