TYPE 2 HARQ CODEBOOK DETERMINATION IN PRESENCE OF PDCCH REPETITIONS

Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first Physical Downlink Control Channel (PDCCH) occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected Downlink Control Information (DCI); and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes.

TECHNICAL FIELD

The present disclosure relates to codebook determination.

BACKGROUND

NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both downlink (i.e., from a network node, gNB, or base station, to a user equipment or UE) and uplink (i.e., from UE to gNB). DFT spread OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally sized subframes of 1 ms each. A subframe is further divided into multiple slots of equal duration. The slot length depends on subcarrier spacing. For subcarrier spacing of Δf=15 kHz, there is only one slot per subframe, and each slot consists of 14 OFDM symbols.

Data scheduling in NR is typically in slot basis, an example is shown inFIG.1with a 14-symbol slot, where the first two symbols contain Physical Downlink Control Channel (PDCCH) and the rest contains physical shared data channel, either Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH).

Different subcarrier spacing values are supported in NR. The supported subcarrier spacing values (also referred to as different numerologies) are given by Δf=(15×2μ)kHz where μ∈0,1,2,3,4. Δf=15 kHz is the basic subcarrier spacing. The slot durations at different subcarrier spacings is given by ½μms.

In the frequency domain, a system bandwidth is divided into resource blocks (RBs), each corresponding to twelve contiguous subcarriers. The RBs are numbered starting with 0 from one end of the system bandwidth. The basic NR physical time-frequency resource grid is illustrated inFIG.2, where only one resource block (RB) within a 14-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

Downlink transmissions can be either dynamically scheduled in which the gNB transmits a DL assignment via Downlink Control Information (DCI) over PDCCH (Physical Downlink Control Channel) to a UE for each PDSCH transmission, or Semi-Persistent Scheduled (SPS) in which one or more DL SPS are semi-statically configured and each can be activated or deactivated by a DCI.

There are three DCI formats defined for scheduling PDSCH in NR, i.e., DCI format 1_0, DCI format 1_1, and DCI format 1_2. DCI format 1-0 has a smaller size and can be used when a UE is not fully connected to the network while DCI format 1_1 and DCI format 1_2 can be used for scheduling MIMO (Multiple-Input-Multiple-Output) transmissions with up to 2 transport blocks (TBs). The DCI formats are referred to as DL DCI formats.

A UE monitors a set of PDCCH candidates for potential PDCCHs. A PDCCH candidate consists of L∈[1,2,4,8,16] control-channel elements (CCEs) in a Control Resource Set (CORESET). A CCE consists of 6 resource-element groups (REGs) where a REG equals one RB during one OFDM symbol. L is referred to as the CCE aggregation level.

The set of PDCCH candidates is defined in terms of PDCCH search space (SS) sets. A SS set can be a Common Search Space (CSS) set or a UE Specific Search Space (USS) set. A UE can be configured with up to 10 SS sets per bandwidth part (BWP) for monitoring PDCCH candidates.

Each SS set is associated with a CORESET. A CORESET consists of NRBCORESETresource blocks in the frequency domain and NsymbCORESET∈{1,2,3} consecutive OFDM symbols in the time domain. In NR Rel-15, a UE can be configured with up to 3 CORESETs per bandwidth part.

For each SS set, a UE is configured with the following parameters:a PDCCH monitoring periodicity of ksslots and a PDCCH monitoring offset of osslotsa PDCCH monitoring pattern within a slot, indicating first symbol(s) of the CORESET within a slot for PDCCH monitoringa duration of Ts<ksslots indicating a number of slots that the search space set existsa number of PDCCH candidates Ms(L)per CCE aggregation level L

A UE determines a PDCCH monitoring occasion on an active DL BWP from the PDCCH monitoring periodicity, the PDCCH monitoring offset, and the PDCCH monitoring pattern within a slot. For search space set s, the UE determines that a PDCCH monitoring occasion(s) exists in slot ns,fμin frame nfif (nf·Nslotframe,μ+ns,fμ−os) mod ks=0, where Nslotframe,μis the number of slots per radio frame. The UE monitors PDCCH candidates for search space set s for Tsconsecutive slots, starting from slot ns,fμ, and does not monitor PDCCH candidates for search space set s for the next ks−Tsconsecutive slots.

A UE detects PDCCH in each PDCCH monitoring occasion. If a PDCCH is detected, the UE decodes the corresponding PDSCH based on the decoded control information in the PDCCH.

In Rel-16, to better support multiple PDCCH monitoring occasions in a slot, new PDCCH monitoring capabilities are defined at least in terms of the maximum number of non-overlapping CCEs for channel estimation. The new limit is discussed based on the concept of PDCCH monitoring span. In short, the PDCCH monitoring span definition provides a set of rules for UE and gNB to have the same understanding on PDCCH monitoring span pattern in a slot based on CORESET/search space configuration and UE capability signaling related to PDCCH monitoring. The UE signals a candidate value set which contains parameters related to span gap X (minimum gap in OFDM symbols between two consecutive spans) and span length Y in OFDM symbols. Together with the CORESET/search space configuration, the monitoring span pattern can then be derived. The span pattern may contain multiple spans in a slot is repeated over multiple slots.

When a PDCCH is detected by the UE, the decoding status of its scheduled PDSCH is sent back to the gNB in the form of Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) over a Physical Uplink Control Channel (PUCCH) resource. If the PUCCH overlaps with a PUSCH transmission by the same UE, HARQ ACK feedback can also be conveyed on PUSCH.

Similarly, when a DL SPS deactivation DCI or a DCI for Secondary cell (SCell) dormancy is received by the UE, a HARQ ACK is sent by the UE to acknowledge the reception of the DCI.

If the UE detects a DCI format scheduling a PDSCH reception ending in slot n or if the UE detects a DCI indicating a SPS PDSCH release or SCell dormancy through a PDCCH reception ending in slot n, the UE provides corresponding HARQ-ACK information in a PUCCH transmission in slot n+k, where k is indicated by a PDSCH-to-HARQ-timing-indicator field in the DCI format, if present, or provided by dl-DataToUL-ACK. k is also referred to as K1. For DCI format 1-0, k can be one of {1, 2, 3, 4, 5, 6, 7, 8}. For DCI format 1-1 and DCI format 1_2, k can be one of a set of values configured in dl-DataToUL-ACK. The set of values can be in the range of {0, 1, . . . , 15}. Up to eight values can be configured in the set.

In case of carrier aggregation (CA) with multiple carriers and/or TDD operation, multiple aggregated HARQ ACK/NACK bits may be sent in a single PUCCH resource.

In NR, up to four PUCCH resource sets can be configured to 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 up to 8 PUCCH resources. A UE determines the PUCCH resource set in a slot based on the number of aggregated UCI (Uplink Control Information) bits to be sent in the slot. The UCI bits consists of HARQ ACK/NACK, scheduling request (SR), and channel state information (CSI) bits.

For a PUCCH transmission with HARQ-ACK information, a UE determines a PUCCH resource after determining a PUCCH resource set. The PUCCH resource determination is based on a 3-bit PUCCH resource indicator (PRI) field in a DL DCI format.

If more than one DL DCI formats are received in the case of CA and/or TDD, the PUCCH resource determination is based on a PRI field in the last DCI among the multiple received DL DCIs that the UE detects. The multiple received DCIs have a value of a PDSCH-to-HARQfeedback timing indicator field indicating a same slot for the PUCCH transmission. For PUCCH resource determination, the detected DCI formats are first indexed in an ascending order across serving cell indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across PDCCH monitoring occasion indexes.

NR Rel-15 supports two types of HARQ codebooks, i.e., semi-static (type 1) and dynamic (type 2) codebooks, for HARQ Ack multiplexing for multiple serving cells in case of carrier aggregation (CA) or multiple DL slots in case of TDD. A UE can be configured to use either one of the codebooks for HARQ Ack/Nack feedback.

Type 1 HARQ codebook (CB) is determined based on a set of semi-statically configured parameters. The codebook size corresponds to the maximum number of HARQ Ack bits that may need to be fed back and it does not change dynamically. Therefore, the feedback overhead can be large.

Unlike Type 1 HARQ codebook, the size of Type 2 HARQ codebook changes dynamically based on the actual number of PDSCH receptions or SPS PDSCH releases or SCell dormancy associated with a same PUCCH resource for HARQ Ack feedback. For this purpose, a counter DAI (Downlink Assignment Indicator) field in the DCIs and in case of DCI format 1-1 and DCI format 1_2, also a total DAI field (if more than one serving cell are configured) are defined.

A value of the counter DAI field in DCI formats denotes the accumulative number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s), SPS PDSCH release, or SCell dormancy associated with the DCI formats that is present up to the current serving cell and current PDCCH monitoring occasion, first in ascending order of serving cell index c and then in ascending order of PDCCH monitoring occasion index m, where 0≤m<M and M is total number of PDCCH monitoring occasions.

The value of the total DAI, when present, in DCI formats denotes the total number of {serving cell, PDCCH monitoring occasion}-pair(s) in which PDSCH reception(s) or SPS PDSCH release or SCell dormancy associated with the DCI formats that is present, up to the current PDCCH monitoring occasion m and is updated from PDCCH monitoring occasion to PDCCH monitoring occasion.

An example is shownFIG.3, where a UE is configured with two serving cells and three PDCCH monitoring occasions. The corresponding counter DAI and total DAI values in each scheduled DCI are shown. The counter DAI is updated after every scheduled DCI while total DAI is only updated every monitoring occasion. Since only two bits are allocated for either counter DAI or total DAI in DCI, the actual DAI values are wrapped round with a modulo 4 operation. A UE can figure out the actual number of DCIs transmitted even though some DCIs are undetected, if the undetected consecutive DCIs are smaller than four.

For HARQ-ACK information transmitted in a PUCCH in slot n, the UE determines the HARQ-ACK information bits, õ0ACK, õ1ACK, . . . , õOACK−1ACK, associated with dynamic scheduled PDSCHs or SPS PDSCH release or SCell dormancy, in the order of first in ascending order of serving cell index and then in ascending order of PDCCH monitoring occasion index m. For the example shown inFIG.3and if one TB is enabled for both cells, the õ0ACK, õ1ACK, . . . , õOACK−1ACK(where OACK=5) are shown inFIG.4.

PDSCH transmission with multiple panels or transmission points (TRPs) has been introduced in NR Rel-16, in which a transport block may be repeated over multiple TRPs to increase PDSCH reliability.

In NR Rel-17, it has been proposed to enhance PDCCH reliability with multiple TRPs by repeating a PDCCH over different TRPs. An example is shown inFIG.5, where a PDCCH is repeated over two TRPs at different times, both containing the same DCI. The DCI can be a DL DCI or a UL DCI.

The PDCCH are repeated in two PDCCH candidates each associated with one of the two TRPs. The two PDCCH candidates are linked, i.e., the location of one PDCCH candidate can be obtained from the other PDCCH candidate. When performing PDCCH detection, a UE may detect PDCCH individually in each PDCCH candidate or jointly by soft combining of the two linked PDCCH candidates.

Improved systems and methods for codebook determination are needed.

SUMMARY

Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first Physical Downlink Control Channel (PDCCH) occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected Downlink Control Information (DCI); and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes.

Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. A method is proposed to construct the codebook in the presence of PDCCH repetitions. The method comprises one or more of: defining a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying at the UE the first PDCCH occasion for each detected DCI; and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In some embodiments, the codebook comprises a Type 2 HARQ ACK codebook. In some embodiments, the counter field comprises a counter DAI field.

DETAILED DESCRIPTION

Transmission/Reception Point (TRP): In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation or a TCI state in some embodiments. In some embodiments, a TRP may be using multiple TCI states. In some embodiments a TRP may be a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element. In some embodiments, in Multiple Transmit/Receive Point (multi-TRP) operation, a serving cell can schedule UE from two TRPs, providing better PDSCH coverage, reliability and/or data rates. There are two different operation modes for multi-TRP: single- Downlink Control Information (DCI) and multi-DCI. For both modes, control of uplink and downlink operation is done by both physical layer and MAC. In single-DCI mode, UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, UE is scheduled by independent DCIs from each TRP.

FIG.6illustrates one example of a cellular communications system600in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system600is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations602-1and602-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC), controlling corresponding (macro) cells604-1and604-2. The base stations602-1and602-2are generally referred to herein collectively as base stations602and individually as base station602. Likewise, the (macro) cells604-1and604-2are generally referred to herein collectively as (macro) cells604and individually as (macro) cell604. The RAN may also include a number of low power nodes606-1through606-4controlling corresponding small cells608-1through608-4. The low power nodes606-1through606-4can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells608-1through608-4may alternatively be provided by the base stations602. The low power nodes606-1through606-4are generally referred to herein collectively as low power nodes606and individually as low power node606. Likewise, the small cells608-1through608-4are generally referred to herein collectively as small cells608and individually as small cell608. The cellular communications system600also includes a core network610, which in the 5G System (5GS) is referred to as the 5GC. The base stations602(and optionally the low power nodes606) are connected to the core network610.

The base stations602and the low power nodes606provide service to wireless communication devices612-1through612-5in the corresponding cells604and608. The wireless communication devices612-1through612-5are generally referred to herein collectively as wireless communication devices612and individually as wireless communication device612. In the following description, the wireless communication devices612are oftentimes UEs, but the present disclosure is not limited thereto.

There currently exist certain challenges. In the presence of Physical Downlink Control Channel (PDCCH) repetition, how to construct Type 2 Hybrid Automatic Repeat Request (HARQ) Acknowledgement (ACK) codebook is an issue. For instance, consider an example where PDCCH #1 scheduling a PDSCH is repeated in PDCCH monitoring occasions m=0 and m=1, and there are other PDSCHs scheduled by PDCCHs in PDCCH monitoring occasion m=0, assume that PDCCH #1 is only detected in PDCCH monitoring occasion m=1. If the existing procedure for Type 2 HARQ ACK codebook construction is applied (i.e., the HARQ ACK bits are arranged first in ascending order of serving cell index and then in ascending order of PDCCH monitoring occasion index), the counter DAI and total DAI in DCI #1 in PDCCH monitoring occasion m=1 would result in an incorrect number of HARQ ACK bits and also incorrect mapping between the PDSCHs and the HARQ ACK bits. Improved systems and methods for codebook determination are needed.

Systems and methods for codebook determination are provided herein. In some embodiments, a method performed by a wireless device for constructing a codebook includes: defining a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying the first PDCCH occasion for each detected DCI; and constructing a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs. In this way, Type 2 HARQ ACK codebook construction is enabled in the presence of PDCCH repetitions with minimum specification changes.

In one embodiment, the counter DAI in a DCI is incremented only at the first PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the first PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs early in time. Only the first PDCCH occasion is considered for incrementing counter DAI and total DAI in subsequent DCIs.

The PDCCH monitoring occasions described in this invention disclosure can be either in a slot or a monitoring span. The different PDCCH monitoring occasions can be in different slots/monitoring spans or the same slot/monitoring span.

An example is shown inFIG.7, where there are three DCIs transmitted in two serving cells and two PDCCH monitoring occasions. The DCIs are used to schedule three PDSCHs, PDSCHs #1 to #3. It is assumed that the HARQ-Acks associated with the PDSCHs are to be transmitted in a same PUCCH or PUSCH in an uplink slot. DCI #1 is carried in PDCCH #1, which is repeated in both PDCCH monitoring occasions m=0 and m=1. In this case, the first PDCCH occasion of PDCCH #1 is the one in PDCCH monitoring occasion m=0 and the second PDCCH occasion of PDCCH #1 is in PDCCH monitoring occasions m=1. The counter DAI and the total DAI in DCI #1 are incremented in the first PDCCH occasion in PDCCH monitoring occasions m=0. In the second occasion in PDCCH monitoring occasions m=1, the same DCI #1 is transmitted, thus the counter and total DAIs are unchanged. For DCI #3, its counter DAI and total DAI are incremented without considering the PDCCH #1 repetition, i.e., the second occasion of PDCCH #1 in PDCCH monitoring occasion m=1 is not counted.

Type 2 HARQ Codebook Construction in Presence of PDCCH Repetitions

In one embodiment, the counter DAI in a DCI is incremented only at the first PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the first PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs early in time. Only the first PDCCH occasion is considered for incrementing counter DAI and total DAI in subsequent DCIs.

If a PDCCH is repeated within a same PDCCH monitoring occasion in different PDCCH candidates of a same or different CORESETs or in a same or different SS sets, the first PDCCH occasion can be defined as one ofa linked PDCCH candidate with a lower (or higher) PDCCH candidate index,a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID, ora linked PDCCH candidate in a SS set with a lower (or higher) SS set ID.

In the UE side, for each detected DCI, the associated first PDCCH occasion is determined. The existing Type 2 HARQ codebook procedure is then applied by considering only the determined first PDCCH occasion.

Using the example shown inFIG.7, let us assume DCI #1 is detected in the second PDCCH occasion in PDCCH monitoring occasions m=1 but not in the first occasion in PDCCH monitoring occasion m=0. Both DCI #2 and DCI #3 are detected. Based on the linkage of PDCCH candidates for PDCCH repetition, the UE can determine that the first PDCCH occasion for DCI #1 is in PDCCH monitoring occasions m=0. For DCIs #2 and #3, they are not repeated and thus the corresponding first occasions are the ones over which they are detected. The Type 2 HARQ codebook is then constructed based on the determined first PDCCH occasions as shown inFIG.8.

Assuming that only a single codeword is configured in the two serving cells, the resulting HARQ ACK information bits õ0ACK, õ1ACK, . . . , õOACK−1ACK, for a total number of OACK=3 HARQ-ACK information bits in a PUCCH, are shown inFIG.9.

The embodiment may be described by changes (highlighted in bold) in the existing pseudo code for Type 2 HARQ-Ack codebook below.---start of proposed changes in 38.213 v16.4.0 section 9.1.3.1---

If the UE transmits HARQ-ACK information in a PUCCH in slot n and for any PUCCH format, the UE determines the õ0ACK, õ1ACK, . . . , õOACK−1ACK, for a total number of OACKHARQ-ACK information bits, according to the following pseudo-code:

Set m = 0 - PDCCH with DCI format scheduling PDSCH reception, SPSPDSCH release or SCell dormancy indication monitoring occasionindex: lower index corresponds to earlier PDCCH monitoringoccasionSet j = 0Set Vtemp= 0Set Vtemp2= 0Set Vs= ∅Set NcellsDLto the number of serving cells configured by higher layersfor the UEif, for an active DL BWP of a serving cell, the UE is not providedcoresetPoolIndex or is provided coresetPoolIndex with value 0 forone or more first CORESETs and is provided coresetPoolIndex withvalue 1 for one or more second CORESETs, and is providedACKNackFeedbackMode = JointFeedback, the serving cell iscounted two times where the first time corresponds to the firstCORESETs and the second time corresponds to the secondCORESETSif the UE indicates type2-HARQ-ACK-Codebook, a serving cell iscounted NPDSCHMOtimes where NPDSCHMOis the number of PDSCHreceptions that can be scheduled for the serving cell by DCI formatsin PDCCH receptions at a same PDCCH monitoring occasion basedon the reported value of type2-HARQ-ACK-Codebookif PDCCH repetition is configured, for each detected DCI the firstPDCCH occasion is determined. The pseudo-code is applicable toPDCCHs in the first PDCCH occasions.Set M to the number of PDCCH monitoring occasion(s)while m < MSet c = 0 - serving cell index: lower indexes correspond to lowerRRC indexes of corresponding cellwhile c < NcellsDLif PDCCH monitoring occasion m is before an active DL BWPchange on serving cell c or an active UL BWP change on thePCell and an active DL BWP change is not triggered in PDCCHmonitoring occasion mc = c + 1;elseif there is a PDSCH on serving cell c associated with PDCCHin PDCCH monitoring occasion m, or there is a PDCCHindicating SPS PDSCH release or SCell dormancy on servingcell c, and if the PDCCH corresponds to a first PDCCHoccasion in case of PDCCH repetitionif VC-DAI,c,mDL≤ Vtempj = j + 1end ifVtemp= VC-DAI,c,mDLif VT-DAI,mDL= ∅Vtemp,2= VC-DAI,c,mDLelseVtemp= VT-DAI,mDLend ifif harq-ACK-SpatialBundlingPUCCH is not provided and theUE is configured by maxNrofCodeWordsScheduledByDCIwith reception of two transport blocks for at least oneconfigured DL BWP of at least one serving cell,o~2·TD·j+2⁢(VC-DAI,c,mDL-1)ACK=HARQ-ACK⁢information⁢bitcorresponding to the first transport block of this cello~2·TD·j+2⁢(VC-DAI,c,mDL-1)+1ACK=HARQ-ACK⁢information⁢bitcorresponding to the second transport block of this cellVs= Vs∪ {2 · TD· j + 2(VC-DAI,c,mDL− 1), 2 · TD· j +2(VC-DAI,c,mDL− 1) + 1}elseif harq-ACK-SpatialBundlingPUCCH is provided to the UEand m is a monitoring occasion for PDCCH with a DCI formatthat supports PDSCH reception with two transport blocks andthe UE is configured by maxNrofCodeWordsScheduledByDCIwith reception of two transport blocks in at least one configuredDL BWP of a serving cell,o~TD·j+VC-DAI,c,mDL-1ACK=binary⁢AND⁢operation⁢of⁢theHARQ-ACK information bits corresponding to the firstand second transport blocks of this cellVs= Vs∪ {TD· j + VC-DAI,c,mDL− 1}elseo~TD·j+VC-DAI,c,mDL-1ACK=HARQ-ACK⁢information⁢bitof this cellVs= Vs∪ {TD· j + VC-DAI,c,mDL− 1}end ifend ifc = c + 1end ifend whilem = m + 1end whileVtemp=(j⁢mod⁡(4TD))×(4TD)+Vtempif UE does not set Vtemp2= VDAIULand TD= 2Vtemp2= Vtempend ifj=⌊j×TD4⌋if Vtemp2< Vtempj = j + 1end ifif harq-ACK-SpatialBundlingPUCCH is not provided to the UE andthe UE is configured by maxNrofCodeWordsScheduledByDCI withreception of two transport blocks for at least one configured DL BWPof a serving cell,OACK= 2 · (4 · j + Vtemp2)elseOACK= 4 · j + Vtemp2end ifõiACK= NACK for any i ∈ {0,1, . . . , OACK− 1}\Vs---unchanged text omitted ------end of proposed changes --------

Alternative Embodiment for Type 2 HARQ Codebook Construction in Presence of PDCCH Repetitions

In an alternative embodiment, the counter DAI in a DCI is incremented only at the last PDCCH occasion in case of PDCCH repetition. If a PDCCH is repeated in two PDCCH monitoring occasions, the last PDCCH occasion is defined as the one in the PDCCH monitoring occasion that occurs latest in time. Only the last PDCCH occasion is considered for incrementing counter DAI and total DAI.

An example is shown inFIG.10, where there are three DCIs transmitted in two serving cells and two PDCCH monitoring occasions. The DCIs are used to schedule three PDSCHs, PDSCHs #1 to #3. DCI #1 is carried in PDCCH #1, which is repeated in both PDCCH monitoring occasions m=0 and m=1. In this case, the last PDCCH occasion of PDCCH #1 is the one in PDCCH monitoring occasion m=1 and the first PDCCH occasion of PDCCH #1 is in PDCCH monitoring occasions m=0. The counter DAI and the total DAI in DCI #1 are incremented in the last PDCCH occasion in PDCCH monitoring occasions m=1. In the first occasion in PDCCH monitoring occasions m=0, the same DCI #1 is transmitted, thus the counter and total DAIs are unchanged. For DCI #2, its counter DAI and total DAI are incremented without considering the PDCCH #1 repetition, i.e., the first occasion of PDCCH #1 in PDCCH monitoring occasion m=0 is not counted.

In the UE side, for each detected DCI, the associated last PDCCH occasion is determined. The existing Type 2 HARQ codebook procedure is then applied by considering only the determined last PDCCH occasions.

Using the example shown inFIG.10, let us assume DCI #1 is detected in the first PDCCH occasion in PDCCH monitoring occasions m=0 but not in the last occasion in PDCCH monitoring occasion m=1. Both DCI #2 and DCI #3 are also detected. Based on the linkage of PDCCH candidates for PDCCH repetition, the UE can determine that the last PDCCH occasion for DCI #1 is in PDCCH monitoring occasions m=1. For DCIs #2 and #3, they are not repeated and thus the corresponding last occasions are the ones over which they are detected. The Type 2 HARQ codebook is then constructed based on the determined last PDCCH occasions as shown inFIG.11.

Assuming that only a single codeword is configured in the two serving cells, the resulting HARQ ACK information bits õ0ACK, õ1ACK, . . . , õOACK−1ACK, for a total number of OACK=3 HARQ-ACK information bits in a PUCCH, are shown inFIG.12.

The embodiment may be described by changes (highlighted in bold) in the existing pseudo code for Type 2 HARQ-Ack codebook below.

---start of proposed changes in 38.213 v16.4.0 section 9.1.3.1---

If the UE transmits HARQ-ACK information in a PUCCH in slot n and for any PUCCH format, the UE determines the õ0ACK, õ1ACK, . . . , õOACK−1ACK, for a total number of OACKHARQ-ACK information bits, according to the following pseudo-code:

Set m = 0 - PDCCH with DCI format scheduling PDSCH reception,SPS PDSCH release or SCell dormancy indication monitoringoccasion index: lower index corresponds to earlier PDCCHmonitoring occasionSet j = 0Set Vtemp= 0Set Vtemp2= 0Set Vs= ∅Set NcellsDLto the number of serving cells configured by higher layersfor the UEif, for an active DL BWP of a serving cell, the UE is not providedcoresetPoolIndex or is provided coresetPoolIndex with value 0 forone or more first CORESETs and is provided coresetPoolIndexwith value 1 for one or more second CORESETs, and is providedACKNackFeedbackMode = JointFeedback, the serving cell iscounted two times where the first time corresponds to the firstCORESETs and the second time corresponds to the secondCORESETSif the UE indicates type2-HARQ-ACK-Codebook, a serving cellis counted NPDSCHMOtimes where NPDSCHMOis the number ofPDSCH receptions that can be scheduled for the serving cell byDCI formats in PDCCH receptions at a same PDCCH monitoringoccasion based on the reported value oftype2-HARQ-ACK-Codebookif PDCCH repetition is configured, for each detected DCI the lastPDCCH occasion is determined. The pseudo-code is applicable toPDCCHs in the last PDCCH occasions.Set M to the number of PDCCH monitoring occasion(s)while m < MSet c = 0 - serving cell index: lower indexes correspond to lowerRRC indexes of corresponding cellwhile c < NcellsDLif PDCCH monitoring occasion m is before an active DL BWPchange on serving cell c or an active UL BWP change on thePCell and an active DL BWP change is not triggered in PDCCHmonitoring occasion mc = c + 1;elseif there is a PDSCH on serving cell c associated with PDCCHin PDCCH monitoring occasion m, or there is a PDCCHindicating SPS PDSCH release or SCell dormancy on servingcell c, and if the PDCCH corresponds to a last PDCCHoccasion in case of PDCCH repetitionif VC-DAI,c,mDL≤ Vtempj = j + 1end ifVtemp= VC-DAI,c,mDLif VT-DAI,mDL= ∅Vtemp,2= VC-DAI,c,mDLelseVtemp= VT-DAI,mDLend ifif harq-ACK-SpatialBundlingPUCCH is not provided andthe UE is configured bymaxNrofCodeWordsScheduledByDCI withreception of two transport blocks for at least oneconfigured DL BWP of at least one serving cell,o~2·TD·j+2⁢(VC-DAI,c,mDL-1)ACK=HARQ-ACK⁢information⁢bitcorresponding to the first transport block of this cello~2·TD·j+2⁢(VC-DAI,c,mDL-1)+1ACK=HARQ-ACK⁢information⁢bitcorresponding to the second transport block of this cellVs= Vs∪ {2 · TD· j + 2(VC-DAI,c,mDL− 1), 2 · TD· j +2(VC-DAI,c,mDL− 1) + 1}elseif harq-ACK-SpatialBundlingPUCCH is provided to the UEand m is a monitoring occasion for PDCCH with a DCI formatthat supports PDSCH reception with two transport blocks andthe UE is configured by maxNrofCodeWordsScheduledByDCIwith reception of two transport blocks in at least one configuredDL BWP of a serving cell,o~TD·j+VC-DAI,c,mDL-1ACK=binary⁢AND⁢operation⁢of⁢theHARQ-ACK information bits corresponding to thefirst and second transport blocks of this cellVs= Vs∪ {TD· j + VC-DAI,c,mDL− 1}elseo~TD·j+VC-DAI,c,mDL-1ACK=HARQ-ACK⁢information⁢bitof this cellVs= Vs∪ {TD· j + VC-DAI,c,mDL− 1}end ifend ifc = c + 1end ifend whilem = m + 1end whileVtemp=(j⁢mod⁡(4TD))×(4TD)+Vtempif UE does not set Vtemp2= VDAIULand TD= 2Vtemp2= Vtempend ifj=⌊j×TD4⌋if Vtemp2< Vtempj = j + 1end ifif harq-ACK-SpatialBundlingPUCCH is not provided to the UE andthe UE is configured by maxNrofCodeWordsScheduledByDCI withreception of two transport blocks for at least one configured DLBWP of a serving cell,OACK= 2 · (4 · j + Vtemp2)elseOACK= 4 · j + Vtemp2end ifõiACK= NACK for any i ∈ {0,1, . . . , OACK− 1}\Vs

FIG.13Aillustrates a method performed by a wireless device for constructing a codebook. The method includes one or more of: defining (step1300A) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (step1302A) the first PDCCH occasion for each detected DCI; and constructing (step1304A) a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs.

FIG.13Billustrates a method performed by a wireless device for constructing a codebook. The method includes: receiving PDCCHs associated with the first and second sets of DCI formats (step1300B); determining a first PDCCH monitoring occasion among the multiple PDCCH monitoring occasions for each of the at least one PDCCH (step1302B); constructing the HARQ-ACK codebook by ordering the HARQ-ACK information associated with each PDCCH according to the associated PDCCH monitoring occasion index, wherein for each of the at least one PDCCH the associated PDCCH monitoring occasion is the first PDCCH monitoring occasion (step1304B); and transmitting, to the base station, the HARQ-ACK information in the codebook (step1306B).

FIG.14Aillustrates a method performed by a base station for constructing a codebook. The method includes one or more of: defining (step1400A) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (step1402A) the first PDCCH occasion for each DCI; and increment (step1404A) a counter based on the first PDCCH occasion of all PDCCHs with a counter field in the corresponding DCIs.

FIG.14Billustrates a method performed by a base station for constructing a codebook. The method includes: determining a first PDCCH monitoring occasion among the multiple PDCCH monitoring occasions (step1400B); incrementing the counter at the first PDCCH monitoring occasion and indicating the counter value in a counter field in the DCI (step1402B); transmitting, to the wireless device, the DCI in the PDCCH in the multiple PDCCH candidates (step1404B); receiving, from the wireless device, HARQ-ACK information associated with the PDCCH (step1406B).

FIG.15is a schematic block diagram of a radio access node1500according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node1500may be, for example, a base station602or606or a network node that implements all or part of the functionality of the base station602or gNB described herein. As illustrated, the radio access node1500includes a control system1502that includes one or more processors1504(e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory1506, and a network interface1508. The one or more processors1504are also referred to herein as processing circuitry. In addition, the radio access node1500may include one or more radio units1510that each includes one or more transmitters1512and one or more receivers1514coupled to one or more antennas1516. The radio units1510may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s)1510is external to the control system1502and connected to the control system1502via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s)1510and potentially the antenna(s)1516are integrated together with the control system1502. The one or more processors1504operate to provide one or more functions of a radio access node1500as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory1506and executed by the one or more processors1504.

FIG.16is a schematic block diagram that illustrates a virtualized embodiment of the radio access node1500according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

As used herein, a “virtualized” radio access node is an implementation of the radio access node1500in which at least a portion of the functionality of the radio access node1500is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node1500may include the control system1502and/or the one or more radio units1510, as described above. The control system1502may be connected to the radio unit(s)1510via, for example, an optical cable or the like. The radio access node1500includes one or more processing nodes1600coupled to or included as part of a network(s)1602. If present, the control system1502or the radio unit(s) are connected to the processing node(s)1600via the network1602. Each processing node1600includes one or more processors1604(e.g., CPUs, ASICs, FPGAs, and/or the like), memory1606, and a network interface1608.

In this example, functions1610of the radio access node1500described herein are implemented at the one or more processing nodes1600or distributed across the one or more processing nodes1600and the control system1502and/or the radio unit(s)1510in any desired manner. In some particular embodiments, some or all of the functions1610of the radio access node1500described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s)1600. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s)1600and the control system1502is used in order to carry out at least some of the desired functions1610. Notably, in some embodiments, the control system1502may not be included, in which case the radio unit(s)1510communicate directly with the processing node(s)1600via an appropriate network interface(s).

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node1500or a node (e.g., a processing node1600) implementing one or more of the functions1610of the radio access node1500in a virtual environment according to any of the embodiments described herein is provided.

In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

FIG.17is a schematic block diagram of the radio access node1500according to some other embodiments of the present disclosure. The radio access node1500includes one or more modules1700, each of which is implemented in software. The module(s)1700provide the functionality of the radio access node1500described herein. This discussion is equally applicable to the processing node1600ofFIG.16where the modules1700may be implemented at one of the processing nodes1600or distributed across multiple processing nodes1600and/or distributed across the processing node(s)1600and the control system1502.

FIG.18is a schematic block diagram of a wireless communication device1800according to some embodiments of the present disclosure. As illustrated, the wireless communication device1800includes one or more processors1802(e.g., CPUs, ASICs, FPGAs, and/or the like), memory1804, and one or more transceivers1806each including one or more transmitters1808and one or more receivers1810coupled to one or more antennas1812. The transceiver(s)1806includes radio-front end circuitry connected to the antenna(s)1812that is configured to condition signals communicated between the antenna(s)1812and the processor(s)1802, as will be appreciated by on of ordinary skill in the art. The processors1802are also referred to herein as processing circuitry. The transceivers1806are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device1800described above may be fully or partially implemented in software that is, e.g., stored in the memory1804and executed by the processor(s)1802. Note that the wireless communication device1800may include additional components not illustrated inFIG.18such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device1800and/or allowing output of information from the wireless communication device1800), a power supply (e.g., a battery and associated power circuitry), etc.

FIG.19is a schematic block diagram of the wireless communication device1800according to some other embodiments of the present disclosure. The wireless communication device1800includes one or more modules1900, each of which is implemented in software. The module(s)1900provide the functionality of the wireless communication device1800described herein.

With reference toFIG.20, in accordance with an embodiment, a communication system includes a telecommunication network2000, such as a 3GPP-type cellular network, which comprises an access network2002, such as a RAN, and a core network2004. The access network2002comprises a plurality of base stations2006A,2006B,2006C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area2008A,2008B,2008C. Each base station2006A,2006B,2006C is connectable to the core network2004over a wired or wireless connection2010. A first UE2012located in coverage area2008C is configured to wirelessly connect to, or be paged by, the corresponding base station2006C. A second UE2014in coverage area2008A is wirelessly connectable to the corresponding base station2006A. While a plurality of UEs2012,2014are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station2006.

The telecommunication network2000is itself connected to a host computer2016, 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. The host computer2016may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections2018and2020between the telecommunication network2000and the host computer2016may extend directly from the core network2004to the host computer2016or may go via an optional intermediate network2022. The intermediate network2022may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network2022, if any, may be a backbone network or the Internet; in particular, the intermediate network2022may comprise two or more sub-networks (not shown).

The communication system ofFIG.20as a whole enables connectivity between the connected UEs2012,2014and the host computer2016. The connectivity may be described as an Over-the-Top (OTT) connection2024. The host computer2016and the connected UEs2012,2014are configured to communicate data and/or signaling via the OTT connection2024, using the access network2002, the core network2004, any intermediate network2022, and possible further infrastructure (not shown) as intermediaries. The OTT connection2024may be transparent in the sense that the participating communication devices through which the OTT connection2024passes are unaware of routing of uplink and downlink communications. For example, the base station2006may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer2016to be forwarded (e.g., handed over) to a connected UE2012. Similarly, the base station2006need not be aware of the future routing of an outgoing uplink communication originating from the UE2012towards the host computer2016.

Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference toFIG.21. In a communication system2100, a host computer2102comprises hardware2104including a communication interface2106configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system2100. The host computer2102further comprises processing circuitry2108, which may have storage and/or processing capabilities. In particular, the processing circuitry2108may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer2102further comprises software2110, which is stored in or accessible by the host computer2102and executable by the processing circuitry2108. The software2110includes a host application2112. The host application2112may be operable to provide a service to a remote user, such as a UE2114connecting via an OTT connection2116terminating at the UE2114and the host computer2102. In providing the service to the remote user, the host application2112may provide user data which is transmitted using the OTT connection2116.

The communication system2100further includes a base station2118provided in a telecommunication system and comprising hardware2120enabling it to communicate with the host computer2102and with the UE2114. The hardware2120may include a communication interface2122for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system2100, as well as a radio interface2124for setting up and maintaining at least a wireless connection2126with the UE2114located in a coverage area (not shown inFIG.21) served by the base station2118. The communication interface2122may be configured to facilitate a connection2128to the host computer2102. The connection2128may be direct or it may pass through a core network (not shown inFIG.21) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware2120of the base station2118further includes processing circuitry2130, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station2118further has software2132stored internally or accessible via an external connection.

The communication system2100further includes the UE2114already referred to. The UE's2114hardware2134may include a radio interface2136configured to set up and maintain a wireless connection2126with a base station serving a coverage area in which the UE2114is currently located. The hardware2134of the UE2114further includes processing circuitry2138, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE2114further comprises software2140, which is stored in or accessible by the UE2114and executable by the processing circuitry2138. The software2140includes a client application2142. The client application2142may be operable to provide a service to a human or non-human user via the UE2114, with the support of the host computer2102. In the host computer2102, the executing host application2112may communicate with the executing client application2142via the OTT connection2116terminating at the UE2114and the host computer2102. In providing the service to the user, the client application2142may receive request data from the host application2112and provide user data in response to the request data.

The OTT connection2116may transfer both the request data and the user data. The client application2142may interact with the user to generate the user data that it provides.

It is noted that the host computer2102, the base station2118, and the UE2114illustrated inFIG.21may be similar or identical to the host computer2016, one of the base stations2006A,2006B,2006C, and one of the UEs2012,2014ofFIG.20, respectively. This is to say, the inner workings of these entities may be as shown inFIG.21and independently, the surrounding network topology may be that ofFIG.20.

InFIG.21, the OTT connection2116has been drawn abstractly to illustrate the communication between the host computer2102and the UE2114via the base station2118without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE2114or from the service provider operating the host computer2102, or both. While the OTT connection2116is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection2126between the UE2114and the base station2118is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE2114using the OTT connection2116, in which the wireless connection2126forms the last segment. More precisely, the teachings of these embodiments may improve the e.g., data rate, latency, power consumption, etc. and thereby provide benefits such as e.g., reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection2116between the host computer2102and the UE2114, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection2116may be implemented in the software2110and the hardware2104of the host computer2102or in the software2140and the hardware2134of the UE2114, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection2116passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software2110,2140may compute or estimate the monitored quantities. The reconfiguring of the OTT connection2116may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station2118, and it may be unknown or imperceptible to the base station2118. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating the host computer2102's measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software2110and2140causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection2116while it monitors propagation times, errors, etc.

FIG.22is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference toFIGS.20and21. For simplicity of the present disclosure, only drawing references toFIG.22will be included in this section. In step2200, the host computer provides user data. In sub-step2202(which may be optional) of step2200, the host computer provides the user data by executing a host application. In step2204, the host computer initiates a transmission carrying the user data to the UE. In step2206(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step2208(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG.24is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference toFIGS.20and21. For simplicity of the present disclosure, only drawing references toFIG.24will be included in this section. In step2400(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step2402, the UE provides user data. In sub-step2404(which may be optional) of step2400, the UE provides the user data by executing a client application. In sub-step2406(which may be optional) of step2402, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step2408(which may be optional), transmission of the user data to the host computer. In step2410of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

EMBODIMENTS

Group A Embodiments

Embodiment 1: A method performed by a wireless device for constructing a codebook, the method comprising one or more of: defining (1300) a first PDCCH occasion among multiple PDCCH occasions associated with a PDCCH; identifying (1302) the first PDCCH occasion for each detected DCI; and constructing (1304) a codebook based on the first PDCCH occasion of all detected PDCCHs with a counter field in the corresponding DCIs.

Embodiment 2: The method of embodiment 1 wherein the codebook comprises a Type 2 HARQ ACK codebook.

Embodiment 3: The method of any of embodiments 1 to 2 wherein the counter field comprises a counter Downlink Assignment Indicator, DAI, field.

Embodiment 4: The method of any of embodiments 1 to 2 wherein the wireless device comprises a User Equipment, UE.

Embodiment 5: The method of any of embodiments 1 to 4, further comprising: receiving, from a network node, multiple search space sets and PDCCH repetition in a subset of the search space sets.

Embodiment 6: The method of any of embodiments 1 to 5, further comprising: monitoring the first and the second PDCCHs and if detected, decoding the corresponding PDSCH.

Embodiment 7: The method of any of embodiments 1 to 6, further comprising: determining a first PDCCH occasion for the first PDCCH when it is detected.

Embodiment 8: The method of any of embodiments 1 to 7, further comprising: constructing a Type 2 HARQ ACK codebook based on the first PDCCH occasion of the first PDCCH and/or the second PDCCH, and the decoding status of the first and the second PDSCH.

Embodiment 9: The method of any of embodiments 1 to 8 wherein receiving the multiple search space sets and the PDCCH repetition in a subset of the search space sets comprises: receiving multiple linked PDCCH candidates in a same or different search space sets over which a PDCCH may be repeated.

Embodiment 10: The method of any of embodiments 1 to 9 wherein the first PDCCH occasion corresponds to a linked PDCCH candidate that occurs first in time.

Embodiment 11: The method of any of embodiments 1 to 10 wherein the first PDCCH occasion corresponds to one of: a. a linked PDCCH candidate with a lower (or higher) PDCCH candidate index; b. a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID; and c. a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID.

Embodiment 12: The method of any of embodiments 1 to 11 wherein a value of the counter field in a DCI carried in a PDCCH repeated in multiple PDCCH occasions is determined based on the first PDCCH occasion in case of PDCCH repetition.

Embodiment 13: The method of any of embodiments 1 to 12 wherein constructing a Type 2 HARQ ACK codebook based on the first PDCCH occasion comprises allocating a HARQ ACK bit(s) to the first PDSCH scheduled by the first PDCCH transmitted in the first PDCCH occasion.

Embodiment 14: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

Embodiment 15: A method performed by a base station for updating a counter, the method comprising one or more of: defining (1400) a first PDCCH occasion among multiple PDCCH occasions associated with a DCI; identifying (1402) the first PDCCH occasion; and incrementing (1404) the counter at the first PDCCH occasion and indicating the counter value in a counter field in the DCI.

Embodiment 16: The method of embodiment 1 wherein the PDCCH schedules a PDSCH, a SPS release, or a Scell dormancy.

Embodiment 17: The method of any of embodiments 15 to 16 wherein the counter field comprises a counter Downlink Assignment Indicator, DAI, field.

Embodiment 18: The method of any of embodiments 15 to 17 wherein the base station comprises a gNB.

Embodiment 19: The method of any of embodiments 15 to 18, further comprising: configuring a wireless device with multiple search space sets and PDCCH repetition in a subset of the search space sets.

Embodiment 20: The method of any of embodiments 15 to 19, further comprising: scheduling a first PDSCH with a first PDCCH which is repeated in multiple PDCCH occasions and a second PDSCH with a second PDCCH without repetition.

Embodiment 21: The method of any of embodiments 15 to 20, further comprising: determining a first PDCCH occasion for the first PDCCH.

Embodiment 22: The method of embodiment 1 where the incrementing the counter comprises adding one to the counter.

Embodiment 23: The method of any of embodiments 15 to 22 wherein configuring the wireless device with the multiple search space sets and the PDCCH repetition in a subset of the search space sets comprises: configuring the wireless device with multiple linked PDCCH candidates in a same or different search space sets over which a PDCCH may be repeated.

Embodiment 24: The method of any of embodiments 15 to 23 wherein the first PDCCH occasion corresponds to a linked PDCCH candidate that occurs first in time.

Embodiment 25: The method of any of embodiments 15 to 24 wherein the first PDCCH occasion corresponds to one of: a. a linked PDCCH candidate with a lower (or higher) PDCCH candidate index; b. a linked PDCCH candidate in a CORESET with a lower (or higher) CORESET ID; and c. a linked PDCCH candidate in a SS set with a lower (or higher) SS set ID.

Embodiment 26: The method of any of embodiments 15 to 25 wherein a value of the counter field in a DCI carried in a PDCCH repeated in multiple PDCCH occasions is determined based on the first PDCCH occasion in case of PDCCH repetition.

Embodiment 28: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Group C Embodiments

Embodiment 29: A wireless device for constructing a codebook, the wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.

Embodiment 30: A base station for incrementing a counter, the base station comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; and power supply circuitry configured to supply power to the base station.

Embodiment 31: A User Equipment, UE, for constructing a codebook, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed 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 supply power to the UE.

Embodiment 32: 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 cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.

Embodiment 33: The communication system of the previous embodiment further including the base station.

Embodiment 34: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Embodiment 35: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

Embodiment 37: The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

Embodiment 38: The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Embodiment 39: A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.

Embodiment 40: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a User Equipment, UE; wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.

Embodiment 41: The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

Embodiment 42: The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE's processing circuitry is configured to execute a client application associated with the host application.

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

Embodiment 45: A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station; wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.

Embodiment 46: The communication system of the previous embodiment, further including the UE.

Embodiment 47: The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.

Embodiment 50: 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 to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

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

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

Embodiment 55: The communication system of the previous embodiment further including the base station.

Embodiment 57: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Embodiment 58: 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 originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.

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

Embodiment 60: The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.

Some embodiments of the present disclosure could be implemented using one or more of the following proposals.Proposal 1 Confirm the working assumption for PDCCH reliability enhancements with non-SFN schemes and Option 2+Case 1, i.e. support Alt3 (two SS sets associated with corresponding CORESETs).Proposal 2 When PDCCH repetition is enabled for the UE, the default is that two PDCCH candidates are linked. FFS whether more than two can be configured to be linkedProposal 3 Two blind decodes per PDCCH pair is counted towards BD limit for the UE when the PDCCH consists of two PDCCH candidates that are linked.Proposal 4 Support Alt.2 and use one of the linked PDCCH candidates in a CORESET having the lowest controlResourceSetId or a SS set with lowest searchSpaceId in the linked SS sets.Proposal 5 The PDCCH symbol occurring latest in time in a pair of linked PDCCH candidates is defined as the last symbol regardless of which PDCCH candidate(s) the UE actually have detected.Proposal 6 The DAI counter DAI is incremented only at the first time a PDCCH is transmitted (i.e., at the first PDCCH occasion) in a linked pair of PDCCH candidates.Proposal 7 The existing procedure for type 2 HARQ-ACK codebook construction is applied only for the first PDCCH occasion in case of PDCCH repetition regardless whether the PDCCH is actually detected in the first or/and the second PDCCH occasion.Proposal 8 In case the CORESET is not configured as unavailable for PDSCH and if a PDSCH scheduled by a pair of PDCCHs overlap with resources in the CORESETs containing the PDCCHs, PDSCH rate matching is done around the union of the linked PDCCH candidates and corresponding DM-RSProposal 9 DCI Format 2-2/2-3 are also supported by multi-TRP based PDCCH enhancements.Proposal 10 One of the two activated TCI states is used as the default TCI state, FFS whether the one is specified or indicated in a MAC CE activating the TCI states.Proposal 11 Consider finalizing PDCCH enhancement with intra-slot PDCCH repetition first.Proposal 12 For codebook/non-codebook based multi-TRP PUSCH, support two separate SRI fields in DCI, where the first SRI field indicates the SRI(s) corresponding to the first TRP and the second SRI field indicates the SRI(s) corresponding to the second TRP.Proposal 13 For codebook based multi-TRP PUSCH, support two separate TPMI fields in DCI, where the first TPMI field indicates the TPMI corresponding to the first TRP and the second TPMI field indicates the TPMI corresponding to the second TRP. The number of layers indicated in the first TPMI field and the second TPMI field are the same.Proposal 14 For per TRP closed-loop power control for PUSCH, Option 3 is supported where a second TPC field is added in DCI formats 0_1/0_2.Proposal 15 Dynamic switching between PUSCH transmission to a single-TRP and multi-TRP should be supported, i.e. each PUSCH transmission is either targeting reception at one or at two TRPs.Proposal 16 Two SRI/TPMI fields are supported for PUSCH repetition towards m-TRP.Proposal 17 To dynamically indicate PUSCH transmission towards a single-TRP or multiple-TRPs, each SRI/TPMI field contains a codepoint that indicates whether the SRI/TPMI field is disabled or not.Proposal 18 For CG PUSCH transmission towards multiple TRPs, support Alt.1.Proposal 19 Reuse the same RV mapping method as in PUSCH repetition Type A for PUSCH repetition Type BProposal 20 Consider allowing back-to-back scheduling of PUSCH repetitions via multiple DCIs over multiple TRPs in NR Rel-17.Proposal 21 To improve A-CSI reliability, support A-CSI multiplexing on at least two PUSCH occasions towards different TRPs in NR Rel-17.Proposal 22 Intra-slot beam hopping (Scheme 2) is not supported in NR Rel-17.Proposal 23 Support Multi-TRP intra-slot repetition (Scheme 3) in NR Rel-17Proposal 24 Both short and long PUCCH formats are supported for Intra-slot repetitionProposal 25 For per TRP closed-loop power control for PUCCH, support either Option 3 (two TPC fields in DCI 1_1/1_2) or Option 4 (one codepoint in TPC field indicating two TPC values) in NR Rel-17.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).3GPP Third Generation Partnership Project5G Fifth Generation5GC Fifth Generation Core5GS Fifth Generation SystemACK AcknowledgementAF Application FunctionAMF Access and Mobility FunctionAN Access NetworkAP Access PointASIC Application Specific Integrated CircuitAUSF Authentication Server FunctionBWP Bandwidth PartCCE Control Channel ElementsCG Configured GrantCORESET Control Resource SetCP-OFDM Cyclic Prefix Orthogonal Frequency Division MultiplexingCPU Central Processing UnitCSI Channel State InformationCSI-RS Channel State Information Reference SignalCSS Common Search SpaceDAI Downlink Assignment IndexDCI Downlink Control InformationDFT Discrete Fourier TransformDL DownlinkDMRS Demodulation Reference SignalDN Data NetworkDSP Digital Signal ProcessoreNB Enhanced or Evolved Node BFPGA Field Programmable Gate ArraygNB New Radio Base StationgNB-DU New Radio Base Station Distributed UnitHARQ Hybrid Automatic Repeat RequestHSS Home Subscriber ServerIoT Internet of ThingsIP Internet ProtocolLTE Long Term EvolutionMME Mobility Management EntityMTC Machine Type CommunicationNACK Negative AcknowledgementNEF Network Exposure FunctionNF Network FunctionNR New RadioNRF Network Function Repository FunctionNSSF Network Slice Selection FunctionOFDM Orthogonal Frequency Division MultiplexingOTT Over-the-TopPC Personal ComputerPCF Policy Control FunctionPDCCH Physical Downlink Control ChannelPDSCH Physical Downlink Shared ChannelP-GW Packet Data Network GatewayPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelQCL Quasi Co-LocatedQoS Quality of ServiceRAM Random Access MemoryRAN Radio Access NetworkRB Resource BlockRE Resource ElementREG Resource Element GroupROM Read Only MemoryRRH Remote Radio HeadRS Reference SignalRTT Round Trip TimeSCEF Service Capability Exposure FunctionSMF Session Management FunctionSPS Semi-Persistent ScheduledSR Scheduling RequestSRS Sounding Reference SignalSS Search SpaceSSB Synchronization Signal BlockTCI Transmission Configuration IndicatorUDM Unified Data ManagementUE User EquipmentUPF User Plane FunctionUSS UE Specific Search Space